Reference Guide › Command Reference › ADDENTRY Command

ADDENTRY Command

Use the ADDENTRY command to create a new USER, IDENTITY, SUBCONFIG, or PROFILE directory entry.

To create a directory entry for a new directory profile:

ADDEntry name [{filetype | *} [filemode | *]] ( PROFILE "Options"

Options:

[ACCount number]
[DIST code]
[FILE [filename]]
[MSG | NOMSG]
[STACK [FIFO | LIFO]]
[FIFO]
[LIFO]

Note: Options can be entered in any order.

To use a skeleton file to create a directory entry for a new user ID:

ADDEntry name [skelname | *] [("Options"] 

Options:

[ACCount number]
[DIST code]
[ENROLL]
[BLOcks number]
[STORGrp number]
[FILEPool poolname]
[IN identity]
[ON member]

[FILE [filename]][Format | NOFormat]
[MANager mgrid]
[MSG | NOMSG]
[STACK [FIFO | LIFO]]
[LIFO]
[FIFO]
[Wait | NOWait]

Note: Options can be entered in any order.

To create a directory entry for a new user ID, without using a skeleton file:

ADDEntry name [{filetype | *} [{* | filemode}]] ( NOSKel "Options"

Options:

[ACCount number]
[DIST code]
[ENROLL]
[BLOcks number]
[STORGrp number]
[FILEPool poolname]
[IN identity]
[ON member]
[IPLstmt]
[FILE [filename]]
[Format | NOFormat]
[MANager mgrid]
[MSG | NOMSG]
[STACK [FIFO |LIFO]]
[FIFO]
[LIFO]
[SUBPOOL poolname]
[Wait | NOWait]
[STEM stemname[.]]

Note: Options can be entered in any order.

Authorizations

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

If the skeleton file or input file used to create the directory entry specifies the creation of minidisks, you must have ADDMDISK authorization through a GRANT ADDMDISK record in the AUTHORIZ CONFIG file.

If the skeleton file or input file used to create a user ID enrolls that user ID in SFS, you must be an SFS manager authorized to allocate space in the target file pool and user storage group.

Definitions

name [skelname | *]

Creates a directory entry, of the specified name, based on the specified skeleton file.

The entry must not already exist. The default skeleton file is the new entry’s directory manager’s default skeleton file, as defined in the VMDIRECT MANAGERS file. If you do not specify a skelname, then CA VM:Director uses a default skeleton file for the manager who is issuing the ADDENTRY command. Specifying an ‘*’ is the same as specifying the default skeleton file name.

name [{filetype|*} [{filemode|*}]] (NOSKel

Creates a directory entry, of the specified name, based on the specified input file.

The entry must not already exist. The input file must have the same name as the entry; its default filetype is DIRECT, and its filemode must be one of your currently accessed minidisks; the default is A. An asterisk for filetype is the same as specifying DIRECT. An asterisk for filemode uses the normal CMS search order to find the file.

name [{ filetype|*} [{filemode|*}]] (PROFILE

Specifies the name of the directory profile to create and the filetype and filemode of the input file to use. The directory profile must not already exist.

CA VM:Director uses name as the filename of the input file. The default for filetype is DIRECT. The filemode must be one of the issuing user ID’s currently accessed minidisks; the default for filemode is A. An asterisk for filetype is the same as specifying DIRECT. An asterisk for filemode uses the normal CMS search order to find the file.

[ACCount number]

Specifies the primary account number for the new user ID or directory profile, overriding the primary account number specified by the skeleton file or input file.

[DIST code]

Specifies the distribution code for the new user ID or directory profile, overriding the distribution code specified by the skeleton file or input file.

[ENROLL]

[BLOcks number]

[STORGrp number]

[FILEPool poolname]

[IPLstmt]

Enrolls the user ID in SFS, allocating the specified number of 4K blocks to this user ID in the specified user storage group in the specified file pool. Specification of any of these options enrolls the user ID in SFS. The IPL statement can also be modified to identify the file pool to use at logon.

By default, CA VM:Director uses the default number of blocks, user storage group, and file pool defined for the new user’s SFS manager. The ADDENTRY command does not modify the IPL statement unless the IPLstmt option is specified on the command line or on the *ENROLL special comment in the skeleton or input file.

If you specify the IPLstmt option, you can identify a sample PROFILE EXEC file to copy to the minidisk or top‑level directory by placing the *SP= special comment in the skeleton or input file. If a sample profile is available or specified on a *SP= special comment, that profile is copied to the top‑level directory for the user as PROFILE EXEC. If there is already a PROFILE EXEC file in the user’s top‑level directory, a sample profile specified on a *SP= special comment is not copied.

[Format | NOFormat]

Formats (FORMAT) or does not format (NOFORMAT) the user’s new minidisks after allocating them. This option applies to all minidisks created by this command, unless overridden by an MDOPT statement in the directory entry.

You must have NOFORMAT ADD authorization to specify NOFORMAT. CA VM:Director ignores the FORMAT or NOFORMAT option when creating minidisks on T‑DISK or V‑DISK. The FORMAT or NOFORMAT option on an MDOPT statement can override these options for specific minidisks.

The NOFORMAT option is not valid with the WAIT | NOWAIT option.

[SUBPOOL poolname]

Specifies the default SUBPOOL name used to contain minidisks allocated during ADDENTRY. This option applies to all minidisks created by this command, unless overridden by an MDOPT statement in the directory entry.

You must have ANYPOOL authorization to specify SUBPOOL *ANY. CA VM:Director ignores the SUBPOOL option when creating minidisks on T-DISK or V-DISK. The SUBPOOL option on an MDOPT statement can override these options for specific minidisks.

[IN identity]

Specifies that a SUBCONFIG entry will be created using either an input file or a skeleton. A BUILD statement for the new SUBCONFIG entry will be added to the named identity directory entry. If IN is specified, then ON must also be specified.

[ON member]

Specifies that a SUBCONFIG entry will be created using either an input file or a skeleton. A BUILD statement for the new SUBCONFIG will specify the named member of an SSI complex. The member name must be ‘*’ if used in a non-SSI environment. If ON is specified, then IN must also be specified.

[MANager mgrid]

Specifies the directory manager for the new user ID; if the command also enrolls the user ID in SFS, this directory manager is also the user ID’s SFS manager. The manager must be defined in the VMDIRECT MANAGERS file. If you do not specify this option, you are the directory manager of the new user ID.

[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 ADDENTRY command, before the command is called.

[FILE [filename]]

[MSG | NOMSG]

[STACK [FIFO | LIFO]

[FIFO]

[LIFO]

[Wait | NOWait]

These options are explained in Common API Command Options.

Description

Issue the ADDENTRY command to create any type of directory entry. Create a USER, IDENTITY, or SUBCONFIG entry by specifying either a skeleton file or an input file to build the directory entry. You create a directory profile by using an input file to build the directory entry.

When creating a directory entry for a USER, IDENTITY, or SUBCONFIG, CA VM:Director first creates the entry and calls any applicable user exits. If CA VM:Director detects errors, it does not create the entry, does not create any minidisks, and does not enroll the user ID in any file pools. If CA VM:Director does not detect errors, it creates minidisks and enrolls the user in a file pool if specified.

If CA VM:Director manages your SFS, then all file pools that it manages must be active and available so that it can check them all for file space that may be owned by the same user ID name as the one you are adding. If any file pool managed by CA VM:Director is not available for checking, or if CA VM:Director finds any file space in an available file pool owned by the same user ID name, the command will fail.

If CA VM:Director creates a new 191 minidisk for a new user ID or enrolls the user ID in a file pool with the IPLstmt option, you can identify a sample PROFILE EXEC to copy to the minidisk or top‑level directory by placing the special comment record, *SP=, in the skeleton or input file.

When creating a directory entry for a directory profile, CA VM:Director does not call any user exits.

Note: When adding a USER or IDENTITY entry, the ADDENTRY command ignores any password specified on the USER statement and sets the initial logon password to be the same as the user ID.