Previous Topic: DUPENTRY CommandNext Topic: New Minidisks


Authorizations

You must have both DUPENTRY authorization and DUPMDISK authorization through GRANT DUPENTRY, GRANT DUPMDISK, GRANT ADDMDISK, and GRANT NOFORMAT records in the AUTHORIZ CONFIG file.

In order to use the MANAGER option, you must have ASSIGN authorization through a GRANT ASSIGN record in the AUTHORIZ CONFIG.

DUPENTRY command authorization has two parameters, the template user ID and the duplicated user ID.

The two parameters follow the specifications documented in the Administration Guide, in the Authorizations chapter. Information for the GRANT and WITHHOLD configuration file records can be found in Configuration File Reference.

Definitions

userid1

Specifies the name of an existing user ID to be used as a pattern or template for creating a new user ID directory entry. The user ID must exist.

userid2

Specifies the name of a user ID to be created. The user ID must not exist.

[MANager mgrid]

Specifies the directory manager for the new user ID. The manager must be defined in the VMDIRECT MANAGERS file. If you do not specify this option, you become the manager of the new user ID. If '=' is specified, then the manager of userid1 becomes the manager of userid2.

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

These options are explained in Common API Command Options.

Description

The DUPENTRY command creates a directory entry for a new user ID based on an existing user ID, which is processed as a template or pattern. With some exceptions documented below, such as unique or dedicated resources, the new user ID is a duplicate of the template user ID.

The same devices and options are present, and the minidisks are exact copies of the disks in the template user ID.

When creating a directory entry for a user ID, CA VM:Director first creates a basic directory entry. If CA VM:Director detects errors it does not create the directory entry, and does not create any minidisks.

If CA VM:Director does not detect errors, it creates minidisks by duplicating the disks from the template user ID.

When creating the directory entry for the new user ID, CA VM:Director calls the NEWUSER User Exit.

Note: For more information about implementing the NEWUSER user exit, see User Exit Reference.

The DUPENTRY command calls the DUPMDISK command for each minidisk device in the template. New minidisks, each containing an exact copy of the data on each template minidisk, are created in the new user ID.

Note: When duplicating a user ID, the DUPENTRY command ignores any passwords specified on the USER statement in the template user ID and sets the initial logon password to be the same as the new user ID.

The password for the new user ID can be reset during initial LOGON or by using the PASSWORD, MANAGE, or MAINT MANAGE commands.

However, the special passwords LBYONLY or AUTOONLY are propagated to the new user ID, if found in the template.