Command Reference › DUPMDISK Command › Definitions

Definitions

sourceentry

Specifies the USER, IDENTITY, or SUBCONFIG directory entry defining the minidisk to be used as the source. The directory entry must not be in HOLD status.

sourcedisk

Specifies the virtual address of the minidisk to be used as the source.

targetentry

Specifies the USER, IDENTITY, or SUBCONFIG directory entry that owns the new duplicate (target) minidisk. The directory entry must not be in HOLD status.

targetdisk

Specifies the virtual address of the new duplicate minidisk.

subpool

Specifies the subpool from which to allocate space for the duplicate (target) minidisk or the subpool list to search for space to allocate for the duplicate minidisk. The default is *MNGR, which searches the list of subpools in which the directory manager for this user ID can allocate space for the first subpool with enough space.

If you specify the subpool by name, that subpool must be defined in the DASD CONFIG file and included in your or the owning manager’s list of subpools in the VMSECURE MANAGERS file. ANYPOOL authorization overrides this restriction. The following predefined lists can be searched for an available subpool. The first subpool in the list with enough space to accommodate the duplicate minidisk is the one that is used:

CA VM:Secure searches subpools in a list according to the order in which the MANAGER record in the VMSECURE MANAGERS file specifies them. It does not include in the search any subpool that is defined with the EXPLICIT attribute.

volser

Specifies the volume serial number (volser) of the DASD volume on which to allocate the duplicate minidisk. The volume must be defined in the DASD CONFIG file and the subpool (specified on the subpool parameter) must be defined on one of the volume extents.

By default, CA VM:Secure determines volser based on the location of the allocation. If you specify volser as an equal sign, CA VM:Secure allocates the new minidisk from the same volume as the original one. However, if you specify a volser, you must also specify a location (loc).

loc

Specifies the location (starting cylinder or block) at which to allocate the duplicate minidisk on a given volume. This location can be any integer up to seven digits for number of cylinders or blocks.

If you specify the location, you must specify the volser parameter as a valid volume name or an equal sign. If you specify an equal sign, CA VM:Secure uses the starting location of the original minidisk, presumably on a different volume but of the same device type. If the volume name is unchanged, the allocation of the new minidisk fails, because the original minidisk still occupies that space.

By default, CA VM:Secure allocates the minidisk according to the algorithms defined for the applicable subpool.

Specifying an equal sign for both volser and loc causes the allocation of the new minidisk to fail, because the new minidisk still occupies that space.

DEVNO

Creates a permanent fullpack minidisk defined by a real device address. CA VM:Secure does not control this type of minidisk and does not map the internal minidisk structure. You must specify * for the loc parameter to use the subsequent parameters.

rdev

Specifies the real device address of the volume on which to define the minidisk. No validation of this address is done until the user logs on and CP verifies the presence of the minidisk. The rdev parameter is used in the position of the size parameter in other versions of the parameter list. If you do not specify an rdev value or if you specify an *, CA VM:Secure uses the virtual device address specified for targetdisk.

mode

Specifies the read/write mode for the duplicate minidisk when the user logs on. CP defines the valid modes, which are R, RR, W, WR, M, MR, and MW, each with an optional suffix of V, S, E, VS, VE, D, VD, SD, ED, VSD, and VED. The default mode is W.

rpw wpw mpw

Specifies the read, write, and multiple link passwords, respectively, for the duplicate minidisk.

Each password can be one to eight characters in length. These parameters do not have default values, and you cannot specify an asterisk for them. If one of the passwords is not specified, CA VM:Secure places no value on the generated MDISK statement for that password and does not allow anyone to link to that minidisk with the respective link mode.

(CA VM:Secure only) If PEF is installed on your system, CA VM:Secure encrypts the passwords.

[ Wait | NOWait]

[ MSG | NOMSG]

[ STACK [ FIFO | LIFO]]

[ FIFO]

[ LIFO]

[ FILE [ filename]]

These options are explained in the Common API Command Options.