Maintaining Access Rules with the ACF Command › Access Rule Components › Access Rule Entries › Access Rules for Minidisks

Access Rules for Minidisks

In a minidisk access rule, CA ACF2 for VM constructs a pseudo dsn. The dsn parameter includes the virtual address of the minidisk (preceded by V), followed by a period, followed by the constant, VOLUME. The VM user ID of the MDISK owner is specified in the $KEY or $PREFIX control statements.

The syntax of a minidisk access rule is:

               { UID(uid)              }
               { UNTIL(date)|FOR(days) }
 Vccuu.VOLUME  { READ(A|L|P)           }
               { WRITE(A|L|P)          }

The parameters for this access rule are defined below.

ccuu

Specifies the virtual address of the minidisk (such as 0190 or 0191).

UID(uid)

Indicates a pattern specifying the users where this rule applies.

UNTIL(date)

Specifies the date that the rule becomes invalid.

FOR(days)

Defines how many days that rule is in effect.

READ A|L|P, WRITE A|L|P

Defines precisely when and how this user can access this minidisk.

A sample rule letting all application programmers link to TLCAMS's 0191 minidisk for one week follows:

$KEY(TLCAMS)
 V0191.VOLUME UID(APP‑) FOR(7) READ(A)

The access specified is READ. By default, CA ACF2 for VM automatically prevents WRITE access. The FOR operand specifies that this rule remains in effect for seven days, beginning with the day that the rule is compiled. This minidisk rule lets users matching the UID mask APP- link to the virtual address 0191 minidisk minidisk TLCAMS owns. These users do not have access to any CMS files on that minidisk. You must write another access rule to allow access to a CMS file or group of files residing on the 0191 minidisk.

In access rules for CMS files, V must precede the virtual address of the minidisk where the file is located. Also, you must specify the filename and filetype for the CMS file access rules.