Reference Guide › Command Reference › CHANGE Command

CHANGE Command

Use the CHANGE command to change the name of a USER, IDENTITY, or SUBCONFIG directory entry. Changing a USER or IDENTITY entry changes the user ID. The associated user ID must be logged off for the change to work.

CHANGE oldentry newentry

Definitions

oldentry

Specifies the name of the directory entry to change.

newentry

Specifies the new directory entry name which replaces the old name.

Description

CA VM:Director does the following when you change a user ID in a USER or IDENTITY entry:

• Checks for pre‑existing directory links to the new user ID and, if it finds any, automatically removes them

  Updates all directory links to minidisks owned by the old user ID to reflect the new user ID except links specified on the NOLINK record in the DASD CONFIG file

• (CA VM:Secure only) If your site uses the Rules Facility, updates all rules that refer to the original user ID to reflect the new user ID
• If the underlying file pool server supports renaming file spaces, renames the file spaces owned by the old user ID to reflect the new user ID

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

When the user ID being changed is enrolled in a CA VM:Director‑controlled SFS filepool, the CHANGE command runs on a servant machine. In this case, be sure the Servant Facility is enabled; if the Servant Facility is disabled, the CHANGE command fails.

If the command tries to rename file spaces but the underlying file pool server does not support this function, the change fails.

After changing a user ID, update the following to reflect the new user ID:

• Archived files (use the CA VM:Archiver reassign function)
• Backed up data (use the CA VM:Backup restore authorization user exit)
• Tapes (using the CA VM:Tape ASSIGN command)
• APPCPASS, CONSOLE, LOGONBY, SPECIAL, and XAUTOLOG records in the directory

You cannot change the CA VM:Director user ID or a user ID specified on an IGNORE record in the DASD CONFIG file with the CHANGE command.

The CHANGE command uses the CMS FILEPOOL EXEC to rename an individual file space within a file pool. Ensure that CA VM:Director has access to the MAINT 193 minidisk on which the FILEPOOL EXEC resides.

Example

To change director entry JSMITH to JSREID, enter:

vmdirect change jsmith jsreid

Return Codes and Error Messages

The table below lists return codes and error messages for the CHANGE command.

Note:

• For more information about changing a user ID directory manager, see the ASSIGN Command.
• For more information about using the Servant Facility, see the Administration Guide.