Command Reference › ADDENTRY Command › Definitions

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 VMSECURE MANAGERS file. If you do not specify a skelname, then CA VM:Secure uses a default skeleton file for the manager who is issuing the ADDENTRY command. Specifying an ‘*’ is the same as specifying the default skelton 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:Secure 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.

[ ACIgroup groupname ]

(CA VM:Secure only) Specifies the security group to which to assign the new user ID or directory profile, overriding the security group specified by the skeleton file or input file. CA VM:Secure uses the GROUP user exit to validate groupname.

[ 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:Secure 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.

You must have NOFORMAT ADD authorization to specify NOFORMAT. CA VM:Secure 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.

[ 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 VMSECURE MANAGERS file. If you do not specify this option, you are the directory manager of the new user ID.

[ FILE [ filename ] ]

[ MSG | NOMSG ]

[ STACK [ FIFO | LIFO ]

[ FIFO ]

[ LIFO ]

[ Wait | NOWait ]

These options are explained in Common API Command Options.