PERMIT
Gives a user or group access to a profile.
Also written PE, grant access
Why it matters. A new rule starts closed. PERMIT is how the right people get in, and only them.
See it
RACF's list for the bank's customer file
You're ZB0001, with SPECIAL, so you can change it. Tap a level to change it, then try the door.
- ZB0001
- ZB0003
- ZB0007
Pick a user ID and try. Can the one with no access get in anyway?
Syntax
{PERMIT | PE} 'profile-name' ID(userid | group ...) [ACCESS(NONE | READ | UPDATE | CONTROL | ALTER)] [CLASS(class)]
PERMIT 'profile-name' ID(userid | group ...) DELETE
PERMIT 'profile-name' [RESET] [FROM('profile')]- 'profile-name'
- The rule to change. Use the profile's own name, not a dataset it covers.
- ID(name)
- Who gets the access: a user ID or a group. Without it, ACCESS and DELETE are ignored.
- ACCESS(level)
- How much. READ if you leave it out.
- DELETE
- Take the names in ID off the access list.
- CLASS(class)
- The class of the profile. DATASET if you leave it out.
- RESET
- Empty the whole access list first.
- FROM('profile')
- Copy the access list of another profile.
- WHEN(...)
- Make the access conditional, for example only when a given program runs.
Try it PERMIT
- 1
Let the group ZBDEV change the datasets under ZBANK.DEV. UPDATE is enough.
PERMIT 'ZBANK.DEV.**' ID(ZBDEV) ACCESS(UPDATE) - 2
Check the access list of the rule.
LISTDSD DA('ZBANK.DEV.**') AUTHUSER - 3
Take ZBDEV off the list again.
PERMIT 'ZBANK.DEV.**' ID(ZBDEV) DELETE
Remember
- ADDSD makes the rule. PERMIT adds names to it.
- ID is who. ACCESS is how much. Prefer a group.
- DELETE takes a name off the list.
The usual mistake
PERMIT 'ZBANK.DEV.**' ZBDEV ACCESS(UPDATE)
ZBDEV needs ID( ) around it. Without ID, RACF ignores ACCESS and changes nothing.
PERMIT 'ZBANK.DEV.**' ID(ZBDEV) ACCESS(UPDATE)
On real z/OS
MF/OS models ID, ACCESS, DELETE, CLASS, RESET and FROM. It refuses WHEN (conditional access) and says so. Real PERMIT prints nothing on success, so MF/OS adds a 'Mainframe101 sim:' note, and it applies the change to a generic profile at once, where a real system needs a refresh.
Where can I practise PERMIT?
Right here, at ZedBank. You take a junior job at a simulated bank and use PERMIT 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.
- Access levelHow much a user may do to a resource: read it, change it, or control it, with each level including the ones below.
- Dataset profileA security rule describing which datasets it covers and who is allowed to do what to them.
- RACF groupA named collection of users, used to grant access to many people at once rather than one at a time.
- Change controlThe process every change goes through before reaching production: reviewed, approved, scheduled and reversible.