CA VM:Secure creates minidisks for a new entry based on MDISK and MDOPT statements in the skeleton or input file from which it builds the user ID’s directory entry.
MDISK statements define minidisks. MDOPT statements are special CA VM:Secure statements used to 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 skeleton or input file, it uses options specified on the ADDENTRY command and default values described in MDOPT Statements.
When ADDENTRY executes, CA VM:Secure passes the values specified on the command line, the MDISK statements, and the MDOPT statements to the ADDMDISK command, which creates the minidisks. Before it places the new directory entry in the source directory, CA VM:Secure replaces the MDISK statements in the entry with the actual MDISK statements that define the new minidisks and removes the MDOPT statements.
Only the ADDENTRY and REPENTRY commands recognize MDISK and MDOPT statements in skeleton or input files. Other CA VM:Secure commands that create user IDs from skeleton or input files ignore them.
CA VM:Secure supports a special format for MDISK statements when used with the ADDENTRY command. This special format lets CA VM:Secure automatically determine where to place each new minidisk. The parameters appear in the same order as in a regular MDISK statement, and their values are very similar to those on the ADDMDISK command.
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]]]
Parameter definitions are explained in ADDMDISK Command.
MDOPT “Mdoptparms”
Mdoptparms:
[Format | NOFormat]
[SUBpool {poolname | *}]
[BLKsize {blksize | *}]
[Label {label | *}]
[AUnit {unitsize | *}]
CA VM:Secure ignores the FORMAT, NOFORMAT, SUBPOOL, and LABEL options on MDOPT statements when creating minidisks on T-DISK or V-DISK. CA VM:Secure ignores all options on MDOPT statements when creating minidisks with the DEVNO parameter.
Note: MDOPT statements must precede MDISK statements. CA VM:Secure applies the options specified on a MDOPT statement to all MDISK statements that follow that statement until CA VM:Secure encounters an MDOPT statement with different options.
Specifies whether CA VM:Secure is to format the new minidisks defined in MDISK statements that follow. For these minidisks, this parameter overrides the FORMAT option on the ADDENTRY command.
Specifies the subpool from which CA VM:Secure is to allocate the 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.
Specifies the CMS block size CA VM:Secure uses when formatting new 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 NOFORMAT is specified on the ADDENTRY command or the MDOPT statement for a minidisk, CA VM:Secure ignores this parameter.
Specifies the minidisk label CA VM:Secure is to give new minidisks when it formats them. The default is DSKvaddr. CA VM:Secure replaces vaddr with the virtual device address.
NOFORMAT is specified on the ADDENTRY command or the MDOPT statement for a minidisk, CA VM:Secure ignores this parameter.
Specifies an alternate allocation unit size for CA VM:Secure to use when it calculates the size of the new minidisks. When this parameter 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.
Example:
The following directory entry BOBBY DIRECT exists on your read/write A-disk:
USER BOBBY BOBBY 5M 12M G 64 INCLUDE PROJ1 MDOPT FORMAT SUBPOOL MAIN LABEL BOB191 BLKSIZE 1024 MDISK 191 3380 * 1M * MR *ENROLL 100 2 FPMKTG
The following PROF1 directory profile also exists:
PROFILE PROF1 MACH ESA IPL CMS PARM AUTOCR * CONSOLE 009 3215 SPOOL 00C 2540 READER A SPOOL 00D 2540 PUNCH A SPOOL 00E 1403 A * * Get CMS disks * LINK MAINT 190 190 RR LINK MAINT 19E 19E RR LINK MAINT 19D 19D RR
To create user ID BOBBY and a 191 minidisk labeled BOB191 for BOBBY from subpool MAIN, and enroll him in filepool FPMKTG, enter:
vmsecure addentry bobby (noskel
The following table lists messages for errors that do not cause immediate termination but do prevent CA VM:Secure from creating a directory entry. CA VM:Secure validates as much of the directory entry as possible. The command exits with return code 54 and message 0633E.
|
Copyright © 2014 CA.
All rights reserved.
|
|