Maintaining Access Rules with the ACF Command › Access Rule Components › Access Rule Entries › VSAM Allocation Protection Access Rules › Protecting VSAM Dataspaces

Protecting VSAM Dataspaces

Names are not given to VSAM dataspaces. When a VSAM dataspace or page space is created or deleted, CA ACF2 for VM validates access at the volume level. For dataspaces, VSAM generates an internal name, such as Z9999999x. CA ACF2 for VM recognizes the VSAM naming convention and generates a pseudo data set name in the format @volser.VOLUME or VOLUME.@volser. CA ACF2 for VM searches for a volume rule that allows access.

For example, both of the following access rule sets let user TLCSDH define or delete VSAM dataspaces on the volume VSAM01:

$KEY(@VSAM01)
 VOLUME UID(TFINTLCSDH) ALLOC(A)

‑or‑

$KEY(VOLUME)
 @VSAM01 UID(TFINPAYSDH) ALLOC(A)

The NOVOLRULE|VOLRULE operand of the RULEOPTS VMO record determines the format of the pseudo data set name that specifies VSAM dataspaces.