Reference Guide › Command Reference › ADDMDISK Command

ADDMDISK Command

Use the ADDMDISK command to add a minidisk definition within a USER, IDENTITY, or SUBCONFIG directory entry.

To create a permanent minidisk:

ADDMdisk entry ["Parms"] [("Options"]

Parms:

 {vaddr | *}
[{subpool | *}
[{size | *}
[{devtype | *}
[{volser | *}
[{loc | *} 
[{mode | *}
[rpw[wpw [mpw ]]]]]]]]]

Options:

[AUnit unitsize]
[FILE [filename]]
[MSG | NOMSG]
[STACK [FIFO | LIFO]]
[FIFO]
[LIFO]
[BLKsize blksize]
[Format  | NOFormat]
[Label [label]]
[Wait | NOWait]
[Cache | NOCache]
[MDC | NOMDC | RECORDMDC]
[SYSCtl | DEVCtl | NOCtl]
[PAValias {vdev | vdev1-vdev2 | vdev.numdevs} ... ]
[WRKALleg | NOWRKALleg]

Note: Options can be entered in any order.

To create a permanent fullpack minidisk defined by a real device address:

ADDMdisk entry vaddr DEVNO ["Parms"] [("Options"]

Parms:

{rdev | *}
[{devtype | *}
[*
[*
[{mode | *}
[rpw [wpw [mpw ]]]]]]]

Options:

[FILE [filename]]
[MSG | NOMSG]
[STACK [FIFO | LIFO]]
[FIFO]
[LIFO ]
[Cache | NOCAche]
[MDC | NOMDC | RECORDMDC]
[SYSCtl | DEVCtl | NOCtl]
[PAValias { vdev | vdev1-vdev2 | vdev.numdevs} ... ]
[WRKALleg | NOWRKALleg]

Note: Options can be entered in any order.

To create a temporary minidisk:

ADDMdisk entry {vaddr | *} TDSK [“Parms”] [("Options"]

Parms:

{size | *} [devtype |*]

Options:

[AUnit unitsize]
[FILE [filename]]
[MSG | NOMSG]
[STACK [ FIFO | LIFO]]
[FIFO ]
[LIFO ]

Note: Options can be entered in any order.

To create a virtual minidisk in storage:

ADDMdisk entry {vaddr|*} VDSK ["Parms"] [("Options"]

Parms:

{size | *}
[FB-512 
[* 
[* 
[{mode | *}
[rpw [ wpw [ mpw ]]]]]]]

Options:

[AUnit unitsize]
[FILE [filename]]
[MSG | NOMSG]
[STACK [FIFO|LIFO]]
[FIFO ]
[LIFO ]

Note: Options can be entered in any order.

Authorizations

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

Either you or the directory manager that will own the directory entry must be authorized to allocate from the subpool in which you specify the minidisk to be created. 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.

You must have NOFORMAT ADD authorization through a GRANT NOFORMAT ADD record in the AUTHORIZ CONFIG file to create a minidisk without formatting it.

Definitions

entry

Specifies the directory entry which will contain the minidisk. The directory entry must not be in HOLD status.

vaddr

Specifies the virtual address of the new minidisk. The default is 191.

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 both the volser and loc parameters to use the subsequent parameters.

rdev

Specifies the read 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 vaddr.

subpool

Specifies the subpool from which to allocate space for the new minidisk or the subpool list to search for space to allocate for the new 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 new 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.

TDSK

Creates the minidisk in the system temporary disk (T‑DISK) space. You can specify the device type of the T‑DISK in the devtype parameter. Otherwise, CA VM:Director uses the default value that the DEVTYPE record specifies in the VMDIRECT MANAGERS file for the owning manager.

VDSK

Creates the minidisk in the system’s virtual disk (V‑DISK) space. You must specify FB‑512 or * for devtype and * for both volser and loc to use the subsequent parameters.

size

Specifies the size of the minidisk. CA VM:Director interprets size differently, depending on the devtype and AUNIT command specifications. It evaluates the following possibilities in the order presented:

devtype

Specifies the new minidisk’s device type, for example, 3380 or 3390. All device types CA VM:Director supports are valid, including those defined in the DASD CONFIG file by means of the DEVTYPE record. By default, CA VM:Director determines devtype based on the location of the allocation.

The devtype parameter is a determinant in calculating the size of the new minidisk. For more information, see the description of the size parameter, above.

volser

Specifies the volume serial number (volser) of the DASD volume on which to allocate the new 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’s extents. By default, CA VM:Director determines volser based on the location of the allocation.

loc

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

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

mode

Specifies the read/write mode for the new 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 MR.

rpw wpw mpw

Specifies the read, write, and multiple link passwords, respectively, for the new 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.

[AUnit unitsize]

Specifies an alternate allocation unit size to use to calculate the size of the new minidisk. When this option is used, CA VM:Director interprets the value for the size parameter as the number of blocks of the size unitsize. It then uses this number to calculate the actual allocation size for the type of device used.

Possible values for unitsize are 512, 1024, 2048, 4096, 1K, 2K, and 4K. The default for unitsize is the specified or default value for BLKSIZE.

[BLKsize blksize]

Specifies the CMS block size to use when formatting the new minidisk. Possible values for blksize are 512, 1024, 2048, 4096, 1K, 2K, and 4K. By default, CA VM:Director uses the value specified for AUNIT; if no value is specified for AUNIT, it uses the default block size defined for the device type.

You cannot specify BLKSIZE for minidisks allocated to T‑DISK or V‑DISK. If the NOFORMAT option is specified, CA VM:Director ignores the BLKSIZE option.

[CAche | NOCAche]

Enables (CACHE) or disables (NOCACHE) minidisk caching at the control unit. CA VM:Director puts the specified option on a MINIOPT record for the minidisk.

You can combine these options with the MDC and NOMDC options to get the desired level of caching. These options cannot be used with the DASDOPT record options SYSCTL, DEVCTL, and NOCTL.

[Format | NOFormat]

Formats (FORMAT) or does not format (NOFORMAT) the new minidisk after allocating it. If you format a minidisk at virtual address 191, CA VM:Director copies a sample PROFILE EXEC, if available, to the minidisk upon completion.

You must have NOFORMAT ADD authorization to specify NOFORMAT. CA VM:Director ignores the FORMAT and NOFORMAT options for minidisks defined on T‑DISK or V‑DISK.

[Label [label]]

Specifies the minidisk label to give the new minidisk during formatting. The default is DSKnnnn. CA VM:Director replaces nnnn with the device number.

If you specify the NOFORMAT option, CA VM:Director ignores the LABEL option.

[MDC | NOMDC | RECORDMDC]

MDC enables full track minidisk cache for the minidisk. NOMDC disables full track minidisk cache. RECORDMDC specifies that the minidisk will use record level minidisk caching.

CA VM:Director puts the specified option on a MINIOPT record for the minidisk.

These options cannot be used with the DASDOPT record options SYSCTL, DEVCTL, and NOCTL.

Note: For more information about MINIOPT and DASDOPT record options, see the IBM CP Planning and Administration guide for the z/VM release you are running.

[NOWRKALleg | WRKALleg]

WRKALLEG causes the working allegiance to be simulated on the minidisk. NOWRKALLEG causes no simulated working allegiance for the minidisk.

CA VM:Director puts the specified option on a MINIOPT record if specified for a permanent minidisk or on a DASDOPT record if the minidisk starts at cylinder 0 or is defined with DEVNO.

[PAValias {vdev | vdev.numdevs | vdev1-vdev2} …]

Defines a single virtual device (vdev) or multiple virtual devices which represent alias Parallel Access Volumes for a non-fullpack minidisk base Parallel Access Volume.

CA VM:Director puts the specified option on a MINIOPT record if specified for a permanent minidisk or on a DASDOPT record if the minidisk starts at cylinder 0 or is defined with DEVNO.

[SYSCtl | DEVCtl | NOCtl]

Specifies the kinds of I/O commands that can be issued against this minidisk:

CA VM:Director puts the specified option on a DASDOPT record for the minidisk.

Use these options only for full‑pack minidisks. They cannot be used with the MINIOPT record options CACHE, NOCACHE, MDC, NOMDC and RECORDMDC.

Note: For more information about MINIOPT and DASDOPT record options, see the IBM CP Planning and Administration guide for the VM release you are running.

[FILE [filename]]

[MSG | NOMSG]

[STACK [FIFO | LIFO]]

[FIFO]

[LIFO]

[Wait | NOWait]

These options are explained in Common API Command Options.