Reference Guide › Command Reference › ASSIGN Command

ASSIGN Command

Use the ASSIGN command to assign a USER or IDENTITY entry to a new directory manager.

ASsign entry mgrid [newentry [account]]

Definitions

entry mgrid

Identifies the USER or IDENTITY directory entry and the new directory manager to be assigned.

[newentry [account]]

Specifies the new name assigned for the entry and the new one‑to‑eight‑character primary account number for the entry.

Description

The ASSIGN command assigns a USER or IDENTITY entry to a different directory manager from its current directory manager. It can also change the entry name and its primary account number. If you assign a new manager for an IDENTITY directory entry, the same new manager is assigned for each SUBCONFIG directory entry associated with that IDENTITY entry.

Important! Do not use the ASSIGN command with servant user IDs. The directory manager for the CA VM:Director service virtual machine and the servant virtual machines must be the same.

If you change the directory entry name through the ASSIGN command, CA VM:Director makes the change with these checks:

• Checks for pre‑existing directory links to the new user ID and, if it finds any, removes them
• Updates all directory links to the minidisks owned by the old user ID to reflect the new user ID
• Renames the file spaces owned by the old user ID to reflect the new user ID, if the underlying file pool server supports renaming file spaces
• (CA VM:Secure only) Updates all rules that refer to the original user ID to reflect the new user ID, if your site uses the Rules Facility

If CA VM:Director manages your SFS and you are changing the user ID name, then all file pools that CA VM:Director 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 new one to which you are changing this user ID name. 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 new user ID name, the command will fail.

If the user ID is an SFS user ID, the directory manager to which you are assigning the user ID must be an SFS manager and must have authority over any file pools and user storage groups in which the user ID is enrolled.

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

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 (use the VMTAPE ASSIGN command)
• APPCPASS, CONSOLE, LOGONBY, SPECIAL, and XAUTOLOG records in the directory

If you have local user ID and account number conventions that the NEWUSER user exit enforces, changes you make through the ASSIGN command must conform to these conventions.

You cannot assign the CA VM:Director user ID with the ASSIGN command.

The ASSIGN 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.

Examples

• To assign user ID FINANCE to directory manager ACCTMGR, enter:

  vmdirect assign finance acctmgr
  

• To assign user ID BOBBY under the new user ID PETER to directory manager ACCTMGR, enter:

  vmdirect assign bobby acctmgr peter
  

Note: For more information about SFS managers, see the chapter "Configuring CA VM:Director for SFS" in the Administration Guide.