RACF
The security manager. It decides who can sign on and who can use what.
Also written Resource Access Control Facility, security manager
Why it matters. Every sign-on and every file you open is checked by RACF first.
See it
RACF's list for the bank's customer file
Try the door as each of them.
- ZB0001Can change
- ZB0003Can read
- ZB0007No access
Pick a user ID and try. Can the one with no access get in anyway?
Syntax
LISTUSER userid
LISTGRP group
LISTDSD DATASET('profile.name') [GENERIC] [AUTHUSER]- LISTUSER
- Show a user: group, attributes, last access.
- LISTGRP
- Show a group: superior group, owner and members.
- LISTDSD
- Show the dataset profile that covers a name.
- GENERIC
- Find the generic profile that matches the name.
- AUTHUSER
- Also show who is on the access list.
Try it LISTUSER
- 1
Look at the user ID you are signed on as.
LISTUSER ZB0001 - 2
Look at the group SYS1.
LISTGRP SYS1 - 3
Look at the rule that protects ZBANK.DEV.JCL.
LISTDSD DA('ZBANK.DEV.JCL') GENERIC AUTHUSER
Remember
- RACF's data is mostly users, groups and profiles.
- Access goes to groups. Users join groups.
- Success is silent. Check with a LIST command.
The usual mistake
Giving access to each person, one by one
It is slow, and when people join or leave the list gets out of date.
PERMIT the group once, then CONNECT people to it
On real z/OS
Real RACF keeps a primary and a backup database, with copies held in storage, and uses many classes, SETROPTS options, and segments such as TSO and OMVS. MF/OS keeps users, groups and profiles in tables for each machine. The LPARs of one machine share them, and ZBPROD keeps its own. SETROPTS, RACLIST, segments and SMF auditing aren't modelled.
Where can I practise RACF?
Right here, at ZedBank. You take a junior job at a simulated bank and use RACF 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.
- RACF groupA named collection of users, used to grant access to many people at once rather than one at a time.
- Dataset profileA security rule describing which datasets it covers and who is allowed to do what to them.
- Access levelHow much a user may do to a resource: read it, change it, or control it, with each level including the ones below.
- SAFThe interface z/OS and its subsystems use to ask the security manager whether something is allowed.
- PERMITThe command that grants or removes a user or group's access to a protected resource.