Access level
How much a user may do to a resource: nothing, read it, change it, or take full control of it.
Also written UACC, universal access, READ UPDATE ALTER
Why it matters. Every RACF rule is a level. The right level lets people work and no more.
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
PERMIT 'profile.name' ID(userid|group) ACCESS(level) [CLASS(class)] PERMIT 'profile.name' ID(userid|group) DELETE
- ID
- Who gets the access: a user ID or a group.
- ACCESS
- The level: NONE, READ, UPDATE, CONTROL or ALTER. Program profiles can also use EXECUTE.
- CLASS
- The kind of resource. DATASET is the default.
- DELETE
- Remove the person or group from the access list.
- WHEN
- Allow the access only in a set situation, such as from a named program.
- GENERIC
- Treat the name as a generic profile.
Try it PERMIT
- 1
Show the rule for ZBANK.DEV, with its access list.
LISTDSD DA('ZBANK.DEV.**') GENERIC AUTHUSER - 2
Lower ZBDEV to READ, so the team can look but not change.
PERMIT 'ZBANK.DEV.**' ID(ZBDEV) ACCESS(READ) - 3
Check the access list again.
LISTDSD DA('ZBANK.DEV.**') GENERIC AUTHUSER
Remember
- The levels, from least to most: NONE, READ, UPDATE, CONTROL, ALTER.
- Each level includes the ones below it.
- Give the lowest level that does the job.
The usual mistake
PERMIT 'ZBANK.DEV.**' ID(ZBDEV) ACCESS(ALTER) so it always works
ALTER lets people delete and rename datasets, and change who else has access to the profile. More access than the job needs is a risk.
ACCESS(UPDATE) to change data, ACCESS(READ) to look
On real z/OS
MF/OS has the five levels for datasets and some general resources. Conditional access with WHEN(PROGRAM) isn't implemented. On real RACF, a change to a class held in storage may need a SETROPTS refresh to take effect, and MF/OS applies changes at once. A real PERMIT is silent, and the MF/OS note is its own.
Where can I practise Access level?
Right here, at ZedBank. You take a junior job at a simulated bank and use Access level 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.
- Dataset profileA security rule describing which datasets it covers and who is allowed to do what to them.
- PERMITThe command that grants or removes a user or group's access to a protected resource.
- RACF groupA named collection of users, used to grant access to many people at once rather than one at a time.
- RACF user IDA person or program's identity on the system. Short, unique, and the basis of every access decision.