LISTUSER
Shows what RACF knows about one user ID.
Also written LU
Why it matters. After you change a user, LISTUSER is how you check the change really happened.
Syntax
{LISTUSER | LU} [(userid ...) | *] [NORACF] [TSO] [OMVS] [CICS]- userid
- The user ID to show. Leave it out to show yourself. Put several in brackets.
- *
- Every user ID you are allowed to list.
- NORACF
- Leave out the base profile, so you see only the segments you ask for.
- TSO
- Also show the TSO segment: logon procedure, account number and similar.
- OMVS
- Also show the z/OS UNIX segment: user number (UID) and home directory.
- CICS
- Also show the CICS segment, if the profile has one.
Try it LISTUSER
- 1
Look at your own user profile in RACF.
LISTUSER - 2
Now look at the user ZB0002, who is already defined.
LISTUSER ZB0002 - 3
Ask about a user ID that doesn't exist: ZB0099.
LISTUSER ZB0099
Remember
- LISTUSER on its own shows you.
- Add a user ID to see someone else.
- Use it after ADDUSER or ALTUSER to check the change.
The usual mistake
LISTUSER NEW STARTER
The operand is a user ID, not a name. MF/OS reads each word as a separate user ID and finds none.
LISTUSER ZB0001
On real z/OS
MF/OS prints the base part of the profile in the real layout. The segment operands (TSO, OMVS, CICS and the rest) are not modelled, and a real profile can show more lines for them. MF/OS also reads extra words after the user ID as more user IDs.
Where can I practise LISTUSER?
Right here, at ZedBank. You take a junior job at a simulated bank and use LISTUSER in real work, with Zed beside you. There's nothing to install.
Start at ZedBankRelated
- RACF user IDA person or program's identity on the system. Short, unique, and the basis of every access decision.
- RACFThe security manager for z/OS, which decides who may sign on, read a dataset, or run a transaction.
- TSOTime Sharing Option: the interactive login environment on z/OS, where you get a command prompt and a session of your own.