For the general case you have proposed, no. There are several reasons.
- By "high level qualifiers" I presume you mean dataset names like high-level-qualifier.xxx. While it is true most dataset access is controlled by RACF profiles oriented towards the high level qualifier, not all access is controlled this way. Just knowing you have "access to the datasets with a specific high level qualifier dies not mean you have access to all the datasets in the high level qualifier.
- Just exactly what do you mean by "access?" RACF recognizes 5 types of "access" privilege: NONE, READ, UPDATE, CONTROL, and ALTER. Well, of course, NONE implies no access, which is alnost certainly not what you're looking for, but the other four imply some kind of "access." Which do you want?
- There are at least four ways you can get "access."
The main reason there is no general way to determine access for all posssible high level qualifiers is because there are so many ways to get access.
- "Universal" access, or UACC, which is used when RACF had no more direct way to determine access.
- Access by your userid in an access list.
- Access by your inclusion in a RACF "group" that is specified in an access list.
- Access by your userid having the OPERATIONS attribute. OPERATIONS is intended for users performing data management functions. OPERATIONS is not all powerful; users with OPERATIONS can be blocked, though this is uncommon.
You can check access yourself, at least to a limited degree, by using the RACF LISTDSD command:
LISTDSD DA('high-level-qualifier.*'') AUTHUSER
LISTDSD DA('high-level-qualifier.**'') AUTHUSER
If LISTDSD responds with NOT AUTHORIZED TO LIST xxx you almost certainly do not have any sort of access to the resource group. If the response is many lines of RACF gibberish, you probably have at least READ access to the resource group. Remember that access to a resource group does not mean you have access to all the resources in the group.