Command Reference › REPENTRY Command › Description

Description

The REPENTRY command can replace directory entries for active user IDs only. If you want to replace the directory entry for a user ID on hold, you must first reactivate the user ID.

Any directory statement can appear in the new directory entry for a user ID, including MDISK statements. The REPENTRY command lets the issuing user ID create, change, move, and delete minidisks for a user ID. The issuing user ID must be separately authorized to use the ADDMDISK, CHGMDISK, and DELMDISK commands before CA VM:Secure will work with minidisks through the REPENTRY command.

If the new directory entry deletes minidisks that were in the old directory entry, then when you issue the REPENTRY command, CA VM:Secure deletes the minidisks. If the minidisks are on packs that are under CA VM:Secure control, CA VM:Secure deletes links to the deleted minidisks from the directory.

The REPENTRY command cannot change logon passwords; the original logon password is maintained in the new directory entry. Minidisk link passwords can be changed by replacing the masking strings with the new passwords. The string $NONE$, which indicates that the specified password is to be deleted, is reserved, and cannot be used as a link password on any MDISK statement.

To use the REPENTRY command, the issuing user ID must have previously executed a GETENTRY command that specified the LOCK option. Locking a directory entry or profile prevents anyone else from modifying it while the issuing user ID is working with it. If the issuing user ID decides not to update the entry or profile after all, running the UNLOCK command removes the lock.

The process of replacing the directory entry for a user ID occurs in two steps:

1. CA VM:Secure compares all statements from the new and original entry and calls the appropriate user exit routines for changed values. It compares the MDISK statements and saves all necessary information from any changed statements. CA VM:Secure then replaces the entire directory entry, retaining the original MDISK statements. If it detects any errors, it does not perform the second step.
2. CA VM:Secure tries to make all of the minidisk updates by moving, adding, or deleting all the minidisks identified during step 1. If it detects any errors, CA VM:Secure continues, updating as many minidisks as possible.

When the issuing user ID replaces the directory entry for a directory profile, CA VM:Secure does not call user exits or allow minidisks. CA VM:Secure updates the directory entry of every user ID that is linked to the original directory profile to use the new directory profile.

A BUILD statement may neither be added or removed when an IDENTITY entry is updated by REPENTRY.