Reference Guide › Command Reference › REPENTRY Command

REPENTRY Command

Use the REPENTRY command to replace a USER, IDENTITY, SUBCONFIG, or PROFILE directory entry.

To replace a user directory entry:

REPEntry "Parms" [("Options"]

Parms:

entryname [{filetype | * | DIRECT} [filemode| * | A]]

Options:

[FILE [filename]]
[Format | NOFormat]
[MSG | NOMSG]
[STACK [FIFO | LIFO]]
[FIFO]
[LIFO]
[Wait | NOWait]

Note: Options can be specified in any order.

To replace a directory profile:

REPEntry "Parms" (PROFILE ["Options"]

Parms:

filename [{filetype | * | DIRECT} [filemode | * | A]]

Options:

[FILE [filename ]]
[MSG | NOMSG]
[STACK [FIFO | LIFO]]
[FIFO]
[LIFO]

Note: Options can be specified in any order.

Definitions

name [filetype [ filemode]]

Specifies the user ID whose directory entry to replace, and name of the copy of the directory entry. The user ID must be an active user ID.

The default file specification for the new directory entry is "name DIRECT A". An asterisk means the same as specifying DIRECT.

If you specify a filemode, it must be one of your currently accessed minidisks. (If you include this REPENTRY command in a program, the filemode must be that of a accessed minidisk in the submitting user ID. If you specify an asterisk for filemode, the command uses the normal CMS search order to find the file.

name [filetype [filemode]] (PROFile

Specifies the directory profile whose directory entry CA VM:Director is to replace and the filetype and filemode of the new directory entry.

The default file specification for the new directory entry is "name DIRECT A."

If you specify a filemode, it must be one of your currently accessed minidisks. (If you include this REPENTRY command in a program, the filemode must be of a minidisk that the user ID that submits the program for execution currently has accessed.)

If you specify an asterisk for filemode, the command uses the normal CMS search order to find the file.

[Format | NOFormat]

Formats (FORMAT) or does not format (NOFORMAT) new minidisks after allocating them, original minidisks after moving them, and deleted minidisks after deleting them. You must have the appropriate NOFORMAT authorization to specify NOFORMAT. (If you include this REPENTRY command in a program, the user ID that submits the program for execution must have the appropriate NOFORMAT authority.)

Deleted or moved minidisks are formatted using a blocksize of 4K, and their labels are changed to ERASED.

CA VM:Director applies the option selected here to all minidisks specified on this command. The FORMAT or NOFORMAT options on an MDOPT statement can override that status for specific new or original minidisks. (MDOPT statements cannot control the action to take on deleted minidisks.)

CA VM:Director ignores these options for minidisks defined on T‑DISK or V‑DISK.

[FILE [filename]]

[MSG | NOMSG]

[STACK [FIFO | LIFO]]

[FIFO]

[LIFO]

[Wait | NOWait]

These options are explained in the Common API Command Options.

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:Director 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:Director deletes the minidisks. If the minidisks are on packs that are under CA VM:Director control, CA VM:Director 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:Director 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:Director 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:Director 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:Director continues, updating as many minidisks as possible.

When the issuing user ID replaces the directory entry for a directory profile, CA VM:Director does not call user exits or allow minidisks. CA VM:Director 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.