High-level qualifier
The first part of a dataset name. It says whose the dataset is.
Also written HLQ
Why it matters. Security rules and storage rules start from the first qualifier. One rule can cover every file under it.
See it
Syntax
LISTCAT LEVEL(hlq) ADDSD 'HLQ.**' UACC(NONE)
- HLQ
- Everything before the first full stop.
- Your own files
- Start with your user ID. That is the default prefix.
- Alias
- A catalog entry that points an HLQ to the catalog holding its names.
- Profile
- A RACF rule such as HLQ.** covers every name below it.
Try it LISTCAT
- 1
List the files whose name starts with your user ID, ZB0001.
LISTCAT LEVEL(ZB0001) - 2
Now list the files that start with ZBANK, the bank's own name.
LISTCAT LEVEL(ZBANK)
Remember
- The HLQ is everything before the first full stop.
- For your own files it is your user ID.
- One security rule on the HLQ covers all the files under it.
The usual mistake
ALLOC DSN('KEEP.DEV.WORK') NEW
KEEP is not your first qualifier. RACF decides by that first part, so you may be refused.
Start your own files with your user ID: ZB0001.DEV.WORK
On real z/OS
The first qualifier also decides the catalog: the catalog has an alias for it. MF/OS has one catalog, CATALOG.ZBANK.MASTER, so aliases are not something you set up. In real shops, naming standards decide the second and third qualifiers as well.
Where can I practise High-level qualifier?
Right here, at ZedBank. You take a junior job at a simulated bank and use High-level qualifier in real work, with Zed beside you. There's nothing to install.
Start at ZedBankRelated
- Dataset nameThe full name of a dataset, written as dot-separated qualifiers of up to eight characters each.
- DatasetWhat a mainframe calls a file: a named collection of records with a defined structure, rather than a loose stream of bytes.
- Dataset profileA security rule describing which datasets it covers and who is allowed to do what to them.
- RACFThe security manager for z/OS, which decides who may sign on, read a dataset, or run a transaction.