Technical data
Managing User Accounts
7.7 Maintaining User Accounts
• What to name the default records
How to Perform This Task
Once you define a user category and establish which record attributes are needed,
you can create the default record.
Examples
1. The following command creates a default record for a category of user that
requires a special captive account:
UAF> ADD DEFAULT2/LGICMD=ALT_COM_PROC/FLAGS=CAPTIVE -
_UAF> /DEVICE=USER3:/DIRECTORY=[PRODUCT]
The command in this example uses the system-supplied default record
DEFAULT to create the record DEFAULT2 and changes the LGICMD, login
flags, default device, and default directory fields.
2. You can then use the AUTHORIZE command COPY to create additional
records having the same attributes as DEFAULT2. The COPY command
creates a new UAF record that uses the specified default record except where
you explicitly override field values.
UAF> COPY DEFAULT2 PALOOKA/PASSWORD=W7YA84MI/UIC=[360,114]
This example uses DEFAULT2 as a template to create a duplicate record
for the user PALOOKA. Notice that only the password and UIC values are
changed.
7.7.5 Deleting a User Account
The main problem in deleting an account, especially an interactive or restricted
account, is deleting the files used by the account.
How to Perform This Task
The following steps are suggested:
1. Copy (or have the outgoing user of the account copy) any files of value to the
ownership of another account. Be sure to change the owner UIC of the files to
match the owner UIC of the new owner. You can also use the Backup utility
(BACKUP) to save the files to a backup tape or disk.
2. Change the password and log in as a user of that account if you are working
from a nonprivileged account. This avoids inadvertently deleting files that
might point to other files of different ownership.
3. Delete the account’s files and directories from the deepest level up to the top
level, using the following procedure:
a. Locate and examine all subdirectories using the DCL command
DIRECTORY [directory-spec . . . ], where directory-spec is the name of
the account’s default directory.
b. Delete the files in each subdirectory, and then delete the subdirectory.
Note that directory files are protected against owner deletion; therefore,
you must change the protection before deleting directory files.
c. Delete the account’s top-level directory. The command procedure in the
next example deletes an account’s files from the bottom level up. Do not,
however, execute this command procedure from a privileged account.
4. Exit from the user account and return to a privileged account. Remove the
user’s account, using the Authorize utility (AUTHORIZE).
Managing User Accounts 7–25










