Reference Guide › Command Reference › DUPENTRY Command › Authorizations › New Minidisks

New Minidisks

CA VM:Director creates minidisks for the new user ID based on MDISK statements in the template user ID directory entry. The data from the template user ID minidisks is copied to the new user ID minidisks. Minidisk access passwords from the template are not carried forward to the new user ID.

Passwords for minidisk access may be added using the CHGMDISK, MANAGE, MAINT MANAGE, or USER commands.

Exceptions

There are certain definitions which may be present in a template user ID directory entry that are used to configure unique resources. For example, a DEDICATE statement specifies that a device is allocated for sole use of a specific virtual machine. This type of unique resource is not copied to the configuration of the user ID being created by this command, because the unique resource cannot be shared between the template user ID and the new user ID.

There are also status records present in the user directory entry for the template user ID which have no meaning in the new user ID. An example might be the record of the last time the template user ID was logged on.

This status information is not copied to the new user ID.

If you are using CA VM:Secure RULES, then no RULES for the template user ID are carried over to the new user ID. The appropriate access rules must be added manually for the new user ID.

Here is the list of the records or record parameters which receive special processing during execution of this command. These statements are not copied, but instead are omitted from the new user ID directory entry and documented by response message VMX0838I.

• A DEDICATE statement defines a device which is accessed by only a single user ID. Such a device is not sharable. An alternate device could be dedicated if necessary.
• A MACID parameter on a NICDEF statement defines a unique identifier for a virtual network interface card device. An alternate MACID should be assigned if needed.
• An APPCPASS statement is not carried over because the authorization it grants may not be appropriate.
• It is not possible to determine whether parameters defined on a MINIOPT or DASDOPT statement for a minidisk in the template user ID should be applied to the copy of the minidisk created by this command. These MINIOPT or DASDOPT statements are not carried over to the new image.
• Any minidisk defined with the END specification is not copied to the new user ID directory entry. Full volume minidisks should be added manually, if appropriate.
• MDISK passwords are removed with the exception for the case where the read password; the read and write password; or the read, write, and multiple passwords are set to 'ALL'.

Special comment records are used to record status for an individual user Special comment records are used to record status for an individual user Id and are not copied over to the new image.

The following comment records are not copied:

• *PWnn statements contain password phrase information.
• *ED= records contain a record of the last modification made to a directory entry.
• *EX= is present when the user ID password has expired.
• *FP= indicates that a user ID is enrolled in a Shared File System filepool.
• *HS= contains history status. A blank *HS= record is substituted for each *HS=.
• *LA= contains the time of the last AUTOLOG of a user ID.
• *LL= contains the time of the last LOGON of a user ID.
• *LT= contains the identifier of the last IPv6 terminal used to LOGON to the user ID.
• *NB= is set when the PASSWORD command is used with the BYONLY option.
• *SP= specifies that a PROFILE EXEC is to be created.
• *US= sets information passed to a POSTRULE User Exit.
• The date field is removed from any *PW= statements, in order to preserve the specification that previously used passwords are to be remembered for later processing by a PASSWORD User Exit. The date field records when the password was updated, and does not apply to the created user ID.