RACF user ID
Your identity on the system: up to eight characters, and every access check starts with it.
Also written user ID, userid, TSO ID
Why it matters. RACF decides everything you can do from your user ID, and from the groups it belongs to.
Syntax
LISTUSER userid
ADDUSER userid [NAME('name')] [DFLTGRP(group)] [PASSWORD(pw)]- userid
- Up to eight characters. Leave it out to see your own.
- NAME
- The person's name, for reports.
- DFLTGRP
- The group the user starts in.
- PASSWORD
- The first password. It is marked expired, so it must be changed at first logon.
- SPECIAL / OPERATIONS / AUDITOR
- Attributes that give wide authority. Keep them rare.
Try it LISTUSER
- 1
Look at your own user ID, ZB0001.
LISTUSER ZB0001 - 2
Now look at the developer, ZB0003.
LISTUSER ZB0003 - 3
Look up an ID that doesn't exist: ZB9999.
LISTUSER ZB9999
Remember
- A user ID is up to eight characters, in capitals, and unique in that RACF database.
- Access depends on the ID and the groups it belongs to.
- Jobs and started tasks have user IDs too.
The usual mistake
My user ID works on every system.
Here each system keeps its own RACF list, and ZBPROD's list does not include ZB0001. (Some real sites share one RACF database across systems.)
Check with LISTUSER on that system. Ask for access if you need it.
On real z/OS
Real RACF also holds the TSO and OMVS segments, password and phrase rules, and MFA factors on the user. MF/OS stores the password safely and shows the usual LISTUSER layout, but doesn't store TSO or OMVS segments.
Where can I practise RACF user ID?
Right here, at ZedBank. You take a junior job at a simulated bank and use RACF user ID in real work, with Zed beside you. There's nothing to install.
Start at ZedBankRelated
- RACFThe security manager for z/OS, which decides who may sign on, read a dataset, or run a transaction.
- RACF groupA named collection of users, used to grant access to many people at once rather than one at a time.
- LogonSigning on to a mainframe system with a user ID and password to start an interactive session.
- Access levelHow much a user may do to a resource: read it, change it, or control it, with each level including the ones below.
- PERMITThe command that grants or removes a user or group's access to a protected resource.