Reference Guide › Command Reference › REPENTRY Command › XSTORE Subcommand › MDISK and MDOPT Statements

MDISK and MDOPT Statements

CA VM:Secure creates, changes, or moves minidisks for a user ID based on MDISK and MDOPT statements in the new directory entry that is replacing the original directory entry.

MDISK statements define minidisks. MDOPT statements define options for minidisks. MDOPT statements precede MDISK statements; CA VM:Secure applies the options specified on an MDOPT statement to all MDISK statements that follow that statement until CA VM:Secure encounters an MDOPT statement with different options. In this way, the issuing user ID can specify unique options for each minidisk. If CA VM:Secure does not find an MDOPT statement in the directory entry, it uses options specified on the REPENTRY command and default values described in MDOPT Statements.

When replacing the directory entry, the REPENTRY command evaluates the MDISK statements in the original entry against the MDISK statements in the new entry and proceeds as indicated:

When REPENTRY executes, CA VM:Secure passes the values specified on REPENTRY, the MDISK statements, and the MDOPT statements to the ADDMDISK and CHGMDISK commands, which create, change, or move the minidisks. REPENTRY calls the DELMDISK command to delete minidisks.

CA VM:Secure cannot move a minidisk defined in system T‑DISK or V‑DISK space to permanent space, or conversely. CA VM:Secure can only redefine T‑DISK or V‑DISK minidisks with a different size or on a different device type.

MDISK Statements

Because CA VM:Secure can dynamically add or move a minidisk, CA VM:Secure supports a special format of the MDISK statement that allows it to automatically determine where to place the new minidisk. The parameters appear in the same order as in a true MDISK record and their values are very similar to those on the ADDMDISK and CHGMDISK commands.

To create a permanent minidisk, a temporary minidisk, or a virtual minidisk, you use the following formats:

Mdisk vaddr [{devtype | *} [{start | *} [{size | *} [{volid | *} ["Parms"]]]]]
Mdisk vaddr {devtype | *} TDSK [size | *]  
Mdisk vaddr FB-512 VDSK [{size | *} ["Parms"]] 
Mdisk vaddr {devtype | *} DEVNO [{rdev | *} ["Parms"]]

Parms:

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

To change or move a permanent minidisk, a temporary minidisk, or a virtual minidisk, you use the following formats:

Mdisk vaddr [{devtype|=|*} [{start|=|*} [{size|=|*} [{volid|=|*} ["Parms"]]]]]
Mdisk vaddr [{devtype|=|*} [{TDSK | =} [{size | = | *}]]]
Mdisk vaddr FB-512 VDSK [{size|=|*} ["Parms"]]

Parms:

{mode | = | *} [{rpw | =} [{wpw | =} [mpw | =]]]

To change the minidisk label or passwords but not move the minidisk, the issuing user enters an equal sign or the original value for each of the devtype, start, size, and volid fields.

Note: For parameter definitions, see the ADDMDISK Command.

MDOPT Statements

CA VM:Secure uses MDOPT statement options when it creates, changes, or moves minidisks. This section shows the format of and option definitions for MDOPT statements. CA VM:Secure ignores the FORMAT | NOFORMAT, SUBPOOL, and LABEL options when creating or changing minidisks on T-DISK or V-DISK. For more information about MDOPT statement options, see the definitions for equivalent options in ADDMDISK Command in this chapter.

CA VM:Secure removes all MDOPT statements from the new directory entry before it places the entry in the source directory.

MDOPT “Parms”

Parms:

[Format | NOFormat]
[SUBpool {poolname | *}]
[BLKsize {blksize | *}]
[Label {label | *}]
[AUnit {unitsize | *}]
[STEM stemname[.]]

[Format | NOFormat]

Specifies whether CA VM:Secure is to format the new and original minidisks. For these minidisks, this option overrides the FORMAT option on the REPENTRY command.

[SUBpool poolname]

Specifies the subpool from which CA VM:Secure is to allocate new minidisks. The default for poolname 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. To specify a subpool list, use one of the variable subpool categories listed in the table, Variable Subpool Categories, in the section Subpool Categories earlier in this chapter.

[BLKsize [blksize]]

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

If you specify NOFORMAT on the REPENTRY command and the MDOPT statement, CA VM:Secure ignores this option.

[Label [label]]

Specifies the minidisk label that CA VM:Secure is to give minidisks when it formats them. The default is DSKvaddr. CA VM:Secure replaces vaddr with the virtual device address.

If you specify NOFORMAT on the REPENTRY command and the MDOPT statement, CA VM:Secure ignores this option.

[AUnit [unitsize]]

Specifies an alternate allocation unit size for CA VM:Secure to use when it calculates the size of new minidisks. When this option is used, CA VM:Secure interprets the value for size on MDISK statements 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.

[STEM stemname[.]]

Specifies the name of REXX stem variable array containing the statements which define the directory entry contents. Any filetype or filemode parameters are ignored. The array contains the directory entry definition, so no disk file is referenced. The number of statements in the directory entry is defined in element stemname.0, stemname.1 contains the first statement in the directory entry, and so on. The stem must be defined in the same REXX program which calls the REPENTRY command, before the command is called.

Return Codes and Error Messages

The table that follows shows errors that do not cause immediate termination, but do prevent CA VM:Secure from updating minidisks. The command exits with return code 54 and message 633E.

REPENTRY Command: Error Messages (No Immediate Termination)

The following table describes the messages:

The table, REPENTRY Command: Return Codes and Error Messages (Immediate Termination), lists errors that cause immediate termination and shows the return code for each.

REPENTRY Command: Return Codes and Error Messages (Immediate Termination)

The following table describes the return codes and the associated error messages:

Note:

• For explanations of the message routing and disconnect options, see Common API Command Options.
• For MDISK statement parameter definitions, see ADDMDISK Command. (They are equivalent to the ADDMDISK command parameters)
• For NOFORMAT authorizations, see Authorizations for Command Processing table in the chapter "Authorizations" of the Administration Guide.
• For complete descriptions of all messages listed in this section, see the Message Reference Guide.