Reference Guide › Command Reference › DUPMDISK Command

DUPMDISK Command

Use the DUPMDISK command to create an exact duplicate of a specified minidisk.

To create a duplicate minidisk:

DUPMdisk “Source” “Target” ["Parms"] [("Options"]

Source:

sourceentry sourcedisk

Target:

targetentry targetdisk

Parms:

"Mdisk Parms" | "Devno Parms"

Mdisk Parms:

 {subpool | *MNGR | *}
[{volser|=|*}
[{loc|=|*}
[{mode|=|W}
[{rpw|=}
[{wpw|=} 
[mpw|=]]]]]]

Devno Parms:

 DEVNO rdev
[*
[{mode|=|W}
[{rpw|=} 
[{wpw|=} 
[mpw|=]]]]]

Options:

[FILE [filename]]
[MSG | NOMSG]
[STACK [FIFO | LIFO]]
[FIFO]
[LIFO]
[Wait | NOWait]

Note: Options can be specified in any order.

Authorizations

You must have DUPMDISK authorization through a GRANT DUPMDISK record in the AUTHORIZ CONFIG file.

To use the DUPMDISK command on user IDs other than your own:

• For the sourceuser, you must have a GRANT DUPMDISK OVER userid TO userid record in the AUTHORIZ CONFIG file.
• For targetuser, you must have a GRANT ADDMDISK OVER userid TO userid record in the AUTHORIZ CONFIG file.

Note: For more information about Authorizations for selective User Ids, see the section, Granting Authorizations to Use Commands on Only Some User IDs in the chapter "Authorizations" of the Administration Guide.

Either you or the directory manager that will own the user ID must be authorized to allocate from the subpool in which you specify the minidisk to be duplicated. It is not required that both you and the owning manager be authorized. Alternately, either one of you can have ANYPOOL authorization, which allows you to allocate space from any subpool.

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 VMDIRECT 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:Director searches subpools in a list according to the order in which the MANAGER record in the VMDIRECT 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:Director determines volser based on the location of the allocation. If you specify volser as an equal sign, CA VM:Director 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:Director 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:Director 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:Director 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:Director 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:Director 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:Director encrypts the passwords.

[Wait | NOWait]

[MSG | NOMSG]

[STACK [FIFO | LIFO]]

[FIFO]

[LIFO]

[FILE [filename]]

These options are explained in the Common API Command Options.

Description

The DUPMDISK command lets you create an exact duplicate of a specified existing minidisk, or copy the contents of a source minidisk to a matching target minidisk. The resulting minidisk will be an exact duplicate of the input minidisk, having the same size, device type, label, and other attributes.

If any allocation parameters (subpool, volser, or loc) are specified, then a new target minidisk will be created. An error will occur if the target minidisk already exists.

If no allocation parameters are specified, and the target minidisk does not exist, then default values for the allocation parameters will be used to create the target minidisk.

If no allocation parameters are specified, and the target minidisk exists, then the data will be copied from the source minidisk to the target. An error will occur if the source and target minidisk device type and size do not match.

While the command can be used to duplicate a CMS minidisk, its real benefit is in cloning Linux images on VM. By first making a master image and then using the DUPMDISK command to duplicate the directory entry and the minidisks, you can quickly set up multiple identical Linux images.

When a CA VM:Director macro calls the DUPMDISK command, it stacks a record for the calling macro’s use when it successfully duplicates the minidisk. The stacked record is in last in, first out (LIFO) order and contains all the information necessary to build an MDISK record to describe the duplicated minidisk’s location. The stacked record has the following format:

vaddr devtype start size volser linkmode rpw wpw mpw

The start and size values are in blocks for FBA and cylinders for CKD devices.

(CA VM:Secure only) If PEF is installed, passwords are encrypted.

Examples

• To make an exact copy of BOBBY 291 to the MAIN 10 minidisk with read/write access, enter:

  vmdirect dupmdisk bobby 291 main 10 * * * mr
  

• To make an exact copy of BOBBY 291 to the MAIN 10 minidisk with read/write access, allocating from the default subpool of BOBBY’s directory manager, enter:

  vmdirect dupmdisk bobby 291 main 10 *mngr * * mr
  

• To make an exact copy of BOBBY 291 to the MAIN 10 minidisk on volume vmdsk1 at cylinder 15 with read/write access, enter:

  vmdirect dupmdisk bobby 291 main 10 * vmdsk1 15 mr
  

Return Codes and Error Messages

The following table lists return codes and error messages for the DUPMDISK command:

DUPMDISK Command: Return Codes and Error Messages

Note:

• For explanations of the message routing and disconnect options, Common API Command Options
• For more information about the EXPLICIT attribute, see SUBPOOL Record.
• For complete descriptions of all messages listed in this section, see the Message Reference Guide.