Reference Guide › Utility Reference › VMXGNR Utility

VMXGNR Utility

Use the VMXGNR utility to generate the CA VM:Director directory database.

The syntax for the VMXGNR utility is:

VMXGNR fn ft fm targetfm exitname  [EXEC | TEXT]  [( NOPW]

Definitions

fn ft fm

Specifies the filename, filetype, and filemode of the current CP source directory file.

targetfm

Specifies the filemode of the target minidisk, DRCT. This minidisk must be linked read/write and must not contain any files.

exitname

Specifies the filename of the NEWUSER exit routine. (The filename of the prototype NEWUSER exit is VMXEXIT1.)

EXEC | TEXT

Indicates that the NEWUSER exit is an EXEC file or a TEXT file. TEXT is the default.

NOPW

Does not add password history special comments (*PW=) to each directory entry during the database generation process. If *PW= special comments already exist in the USER DIRECT file from previously used directory entries, NOPW leaves them there.

Description

The VMXGNR utility, located on the CA VM:Director 192 disk, generates the CA VM:Director directory database by copying your existing CP source directory to CA VM:Director database format.

Each user CP directory entry is placed in a separate file on the target minidisk, with the user ID as the filename and the directory manager user ID as the filetype. The VMXGNR utility checks to see that the target minidisk is labeled DRCT.

The VMXGNR utility places all CP directory statements that precede the GLOBALDEF, USER, or PROFILE statements (whichever comes first) in the DIRECT STATEMENT file on the CA VM:Director A–disk. This file is used by the CA VM:Director backup utility, VMXBKP01. All statements from the GLOBALDEF statement to the first USER or PROFILE statement are placed in the VMDIRECT GLOBALS file, with the exception of POSIXGROUP statements which are placed in the VMDIRECT POSIX file. (VMXGNR supports the POSIXGROUP, POSIXINFO, POSIXOPT, and POSIXGLIST directory statements.)

The VMXGNR utility adds password history special comments (*PW=) and edit special comments (*ED=) to directory entries when generating the database:

• The *PW= special comment contains the date (in the format yy/mm/dd) the user’s logon password was last changed, and a list of most recent logon passwords for this user ID. Initially, the date of the password change is set to the current date. Up to 57 characters are available for storing old passwords. When CA VM:Director initializes, the data on the *PW= special comment is saved for use by the QUERY command.
• The *ED= special comment contains the date, time, and user ID that performed the last update to a directory entry, and the name of the macro invoked to perform the last update.

The VMXGNR utility checks for parameters on ACCOUNT statements. If it finds no parameters, it deletes the ACCOUNT statement from the directory. When an ACCOUNT statement is deleted, the account number and distribution code default to the user ID.

The VMXGNR utility converts lowercase letters to uppercase on directory control statements. Lowercase letters on comment statements remain unchanged. Additionally, upper and lowercase is preserved on POSIXINFO, POSIXGLIST, and POSIXGROUP statements.

The VMXGNR utility deletes the DIRMAINT comment statement used for storing checksums because CA VM:Director does not maintain checksums. If you need to use DIRMAINT, run VMXBKP01 to create a directory source file of the CA VM:Director directory database; then use DIRMAINT to reinitialize the checksum statements.

Valid access modes for the LINK control statement in a directory entry are R, RR, W, WR, M, MR, and MW. If a V has been appended to the right of an access mode on a LINK statement, the VMXGNR utility removes the V to ensure that a valid access mode is specified.

The VMXGNR utility truncates directory records to a logical record length of 71.

The DIRECTORY control statement allows you to specify the CPUID and a system name for each of the processors that might share the CP source directory. The SYSAFFIN statement tailors which entries and which statements within those entries are used on each processor.

The VMXGNR utility uses these DIRECTORY control statements to generate a CA VM:Director directory database containing only those user IDs that should appear on the processor where the VMXGNR utility is running. It also includes only the appropriate statements within an entry.

The VMXGNR utility processes the DIRECTORY statements and looks for a match between the CPUIDs on those statements and the CPUID of the processor that is running. When it finds a match, it saves the associated system affinity name for use in processing any subsequent SYSAFFIN statements. You see an informational message that gives you the CPUID and model number of the running processor, and the system affinity name that the VMXGNR utility will use to generate the rest of the directory database. The CPUID of the host processor, not the one of the virtual machine running the VMXGNR command, is the one used for matching.

The VMXGNR utility deviates slightly from the IBM support of the DIRECTORY statements. These differences are as follows:

• If a SYSAFFIN statement refers to a system affinity name that you did not define on a DIRECTORY statement, the VMXGNR utility treats it as not matching the current system name and acts accordingly.
• Any duplicate CPUID specifications are ignored. This includes any duplication created by use of an asterisk as the first character of the CPUID.

Do not attempt to generate an encrypted database until you have successfully installed and tested CA VM:Director.

(CA VM:Secure only)To avoid the loss of your management scheme when you run the VMXGNR utility, code the NEWUSER exit to reflect your current management scheme. A non–zero return code from the NEWUSER exit indicates that the VMXGNR utility skipped the directory entry being processed. Do not initialize CA VM:Secure if any entries have been skipped. For more information, see the NEWUSER user exit.

To avoid the automatic insertion of *PW= special comments in user IDs, use the VMXGNR utility with the NOPW option to generate the database. If you allow the VMXGNR utility to insert *PW= special comments in all entries, and later determine that you have user IDs whose passwords do not need to be expired regularly, for instance, MAINT, edit the user directory entry and remove the *PW= special comment.

Comment statements that occur after the last directory control statement for User A and before the next USER directory statement for User B, are saved in User B’s directory entry, immediately after the USER statement. Therefore, make sure all comments pertaining to User A’s directory entry precede User A’s last directory control statement or that they are interspersed within the directory entry.

Before you generate your CA VM:Director directory database, ensure that the source directory file to be used by the VMXGNR utility, is current and the BKUP minidisk is empty.

Use this utility during CA VM:Director installation or during disaster recovery.

Example

To generate the CA VM:Director directory database from your USER DIRECT file, storing the results on your U–disk, enter:

vmxgnr user direct a u vmxexit1 exec