Use the EDIT command to open a USER, IDENTITY, or SUBCONFIG directory entry source for editing or to create a USER or IDENTITY directory entry.
EDIT entry [prototype]
You must have EDIT authorization through a GRANT EDIT record in the AUTHORIZ CONFIG file.
The name of the directory entry you want CA VM:Director to create or modify.
The name of a prototype directory entry on which to base the new directory entry when you are creating a user ID. The prototype is required when you are creating a directory entry, and not allowed when you are editing an existing directory entry.
The EDIT command invokes your PROFILE XEDIT (if one exists) and allows you to modify an existing directory entry or to create a new directory entry for a user ID.
When you create a directory entry, you must use a prototype directory entry as the basis for the new one.
CA VM:Director copies the prototype directory entry to the new user ID name, then does the following to the copy (the new directory entry):
If the directory entry includes an account comment (*AC=), change the account numbers it specifies to suit the new user ID.
When you edit an existing directory entry, you can change any statement in the entry except MDISK or BUILD statements, as long as the change results in a directory entry that meets VM standards for directory control statements. MDISK statements for controlled volumes may not be added. MDISK statements may be deleted which causes the minidisk to be deleted. BUILD statements may neither be added nor deleted using EDIT.
(CA VM:Secure only) If PEF is installed at your site, you also cannot change logon passwords (which are encrypted). No error messages are generated if you try to change a logon password, but CA VM:Director saves the encrypted logon password and restores it to its original value when you exit the directory entry
Changing special comment records starting with "*PW00" records can produce have unpredictable results, including making it impossible to log on. Changing these records must be only done under the direction of Technical Support.
Important! The EDIT command cannot perform DASD management. Do not use it to add, remove, or change MDISK records that are under CA VM:Director control in the DASD CONFIG file.
If the directory entry contains an INCLUDE statement (to reference the statements of a directory profile in the directory entry), the EDIT command displays this INCLUDE statement but does not display the contents of the included directory entry. You can delete the INCLUDE statement so that the directory entry no longer references the directory profile.
You can also change the POSIX‑related statements: POSIXINFO, POSIXGLIST, and POSIXOPT.
Note: For syntax and usage information for the POSIXINFO, POSIXGLIST, and POSIXOPT directory control statements, see the IBM CP Planning and Administration guide for your release of VM.
If CA VM:Director detects syntax errors in the directory entry, it displays diagnostic messages and asks whether you want to fix the errors. If you choose not to correct the errors, the CP directory is not updated. If you enter the XEDIT SAVE command and then the QUIT or QQUIT command, the CP directory is updated.
You cannot issue the EDIT command from the CA VM:Director console.
Example
To edit the directory entry for user entry ERNIEP, enter:
vmdirect edit erniep
The directory entry for ERNIEP may look something like this:
USER ERNIEP RELIC 1M 3M 64 INCLUDE TESTPRO1 OPTION DEVINFO *FL= N ACCOUNT 58000099 POLO *PW= LINK TESTUSR1 191 19C RR
Note the INCLUDE statement, which references the directory profile TESTPRO1 but does not display the contents of this directory profile.
Note:
|
Copyright © 2014 CA.
All rights reserved.
|
|