Using ACCOUNT Subcommands

When you maintain user IDs with the ACCOUNT command, you actually use the ACCOUNT subcommands. The subcommands you use most frequently are:

LIST – to display information about a user in the UADS.
ADD – to add a new user or add information about an existing user.
DELETE – to delete a user or delete information about a user.
CHANGE – to change existing information about a user

Each of these subcommands has positional parameters for specifying the information to be maintained. The order of the parameters is the same for each subcommand:

User ID
Password
Account number
LOGON procedure

Example
The ACCOUNT subcommand to add a user with user ID `USER5`, a password of `NEW5`, an account number of `7653`, and the LOGON procedure `PROC00`, is as follows: `ADD (user5 new5 7653 proc00)`

You can use the ADD, CHANGE, and DELETE subcommands to maintain either entire entries or parts of entries. When you are maintaining entire entries (adding, changing, or deleting user IDs), you need to supply only the user ID, in parentheses, with the subcommand. When you are maintaining parts of the entries, you must identify what parts of what entries you want to change.

When you use the ADD, CHANGE, or DELETE subcommand to modify part of an existing entry in the UADS, the subcommand is divided into two segments: positional parameters (the nodelist) and keyword parameters. Positional parameters indicate where the modification is to occur. Keyword parameters supply the information to be added, changed, or deleted.

Figure 1. A Subcommand for Modifying Part of a UADS Entry

In Figure 1, the positional parameters supply the user ID, password, and account number under which the modification is to occur. The way the keyword parameters are interpreted depends on the subcommand. If the subcommand is ADD, datanum is added as a LOGON procedure under the account number. If the subcommand is DELETE, datanum is a LOGON procedure to be deleted. If the subcommand is CHANGE, the account number is renamed to datanum.

For subcommands ADD and CHANGE, you can supply additional attributes. These attributes are described in Adding a User Definition.

Log on to TSO/E with a user ID that has account authority and allocate SYS1.UADS to the ddname SYSUADS as SHR in the LOGON procedure or in your TSO/E session.
If you are modifying an existing user ID, the user with that ID must be logged off. You might need to send a message to the user asking the user to log off.
Type ACCOUNT.
You then see the ACCOUNT mode message and can enter ACCOUNT subcommands.

To leave ACCOUNT: Type the END subcommand and press the Enter key.

For Help with ACCOUNT Subcommands

If you need help while under ACCOUNT, you can use the HELP subcommand of ACCOUNT to see information about a subcommand. To see all of the help information for a subcommand, enter:

help subcommand_name

For more information about using the HELP subcommand, see z/OS TSO/E System Programming Command Reference.