RACROUTE REQUEST=LIST: Build in-storage profiles

RACROUTE REQUEST=LIST builds in-storage profiles for RACF-defined resources. RACROUTE REQUEST=LIST processes only those resources described by class descriptors. Profiles built by RACROUTE REQUEST=LIST can be used by RACROUTE REQUEST=FASTAUTH, or by RACROUTE REQUEST=AUTH, to verify a user's access to a resource.

In-storage profiles are built from a profile on the RACF® database or from potentially several profiles on the database if resource member and grouping class profiles are utilized. Each resulting in-storage profile has a size limit of 65,535 bytes. See the topic in the z/OS Security Server RACF Security Administrator's Guide on "Limiting the Size of Your Access Lists" for a discussion on access lists and other contributors to the size of an in-storage profile.

The default is RELEASE=1.6.

The module calling the RACROUTE REQUEST=LIST macro must be one of the following:

Authorized (APF-authorized, in system key 0–7, or in supervisor state), or
Link-edited with the RENT (reentrant) option, and listed in the RACF authorized caller table.
Note: It is recommended that if you run programs that issue the RACROUTE REQUEST=LIST macro, you run those programs APF-authorized. See z/OS Security Server RACF System Programmer's Guide for information on the authorized caller table.

If the ACEE is below 16MB, any area chained off an ACEE, with the exception of generic profiles, is also placed below 16MB. Otherwise, the area is placed above 16MB. However, a caller executing in 31-bit mode might issue a REQUEST=LIST with LOC=ABOVE to have the profiles placed above 16MB if possible, even if the ACEE is below 16MB.

The caller cannot hold any locks when issuing RACROUTE REQUEST=LIST.