High-level qualifier
The first part of a dataset name, which usually identifies the owner and drives how security and storage rules apply.
Also written HLQ
The high-level qualifier, universally shortened to HLQ, is the first segment of a dataset name: everything before the first full stop.
It carries more weight than the rest of the name. Security profiles are typically written against it, so granting someone access to a whole application's datasets is a single rule rather than hundreds. Storage rules often key off it too, deciding which disk pools a dataset lands on, whether it is backed up, and how long it is kept.
For personal work the HLQ is normally your own user ID, which is why ISPF adds it automatically to any dataset name you type without quotes. Application datasets use an HLQ agreed by the site, such as a project code or system name, and getting that right is how your dataset ends up in the right place with the right protection.
If you are ever unsure why you can read one dataset and not another with a nearly identical name, the high-level qualifier is almost always the answer.
Related terms
- 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.