Dataset profile
A security rule that names a group of datasets and says who may use them.
Also written generic profile, discrete profile, profile
Why it matters. When someone can't open a file, the dataset profile is the rule that said no.
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
ADDSD 'profile.name' [UACC(access)] [OWNER(id)] [WARNING]
LISTDSD DATASET('profile.name') [GENERIC] [AUTHUSER|ALL]- UACC
- The access for anyone not on the access list.
- OWNER
- Who looks after the profile.
- WARNING
- Allow the access but write a warning, to test a rule before it blocks anyone.
- AUDIT
- Which accesses to record.
- GENERIC
- On LISTDSD: find the generic profile that covers the name.
- AUTHUSER
- On LISTDSD: also show the access list.
Try it LISTDSD
- 1
Find the rule that protects the real dataset ZBANK.DEV.JCL.
LISTDSD DA('ZBANK.DEV.JCL') GENERIC AUTHUSER - 2
Make a new rule to protect everything under ZBANK.QA. Let nobody in by default.
ADDSD 'ZBANK.QA.**' UACC(NONE)
Remember
- A profile is a rule, not a dataset.
- A name with ** is generic: one rule covers many datasets.
- UNIVERSAL ACCESS (UACC) is what anyone not listed gets. NONE means closed.
The usual mistake
The profile is stored inside the dataset.
A profile lives in the security database, not in the dataset. Deleting the file doesn't delete a generic rule.
The profile is a separate rule in RACF that matches dataset names.
On real z/OS
Real RACF expects the first qualifier of a profile to be a user ID or group name, or to be covered by the naming convention table. MF/OS doesn't check this. MF/OS also treats every profile as generic, and has no discrete profiles.
Where can I practise Dataset profile?
Right here, at ZedBank. You take a junior job at a simulated bank and use Dataset profile 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.
- High-level qualifierThe first part of a dataset name, which usually identifies the owner and drives how security and storage rules apply.
- 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.
- Dataset nameThe full name of a dataset, written as dot-separated qualifiers of up to eight characters each.