Previous Topic: Access Rule EntriesNext Topic: CMS File Rules


VM Pseudo-DSNs

When a virtual machine tries to access data, CA ACF2 for VM constructs a pseudo‑DSN as input into access validation. The pseudo‑DSN for minidisk and DASD volume accesses is described below.

When CA ACF2 for VM processes a LINK, ATTACH or DEDICATE it constructs a VM volume pseudo‑DSN.

owner.tccuu.VOLUME
owner

Specifies the data owner. For minidisk LINKs, the owner is the user ID that has the MDISK statement for the minidisk. For volume ATTACHES and DEDICATES, the owner is the value defined in the OPTS VMO record. SYSTEM is the default. The owner field is the key to the rule.

Specifies the volume type. V is for virtual volumes or minidisks. R is for real volumes.

ccuu

Specifies the VM directory address of the volume, for example, 0191.

VOLUME

Specifies the volume rule entry. The keyword volume indicates that the rule entry applies to a volume access through the LINK or ATTACH commands, or a VM directory LINK or DEDICATE access. For example, CA ACF2 for VM constructs pseudo‑DSNs as follows:

LINK MAINT 0191 AS 1AF1 RR
Rule key MAINT, pseudo DSN V0191.VOLUME, 
access read
LINK ACF2VM 201 AS 201 RR
Rule key ACF2VM, pseudo DSN V0201.VOLUME, 
access read
ATTACH 123 TO VSEIPO
Rule key SYSTEM (or other value if overridden), pseudo DSN R0123.VOLUME, 
access write. 
ATTACH 201 TO MVSTEST AS 3F21 R/O
Rule key SYSTEM (or other value if overridden), pseudo DSN R0201.VOLUME, 
access read.
DEDICATE 401
Rule key SYSTEM (or other value if overridden), pseudo DSN R0401.VOLUME, access write.