Independent RACF system macros
This appendix contains independent RACF® system macros that can be used by other callers to invoke RACF or another external security product.
Attention: As of RACF 1.9,
new keywords are not supported on the independent invocation of these
macros. RACF supports the new
keywords only if you invoke the RACF system
macros, which provide more function, using the RACROUTE interface
documented in RACF system macros.
Table 1 identifies the RACROUTE macro request types that are replacements for the independent system macros described in this appendix. If you receive a return code or reason code from an independent system macro and cannot find a description of the code in this appendix, see the counterpart request type in RACROUTE.
RACROUTE REQUEST type | Independent RACF system macro |
---|---|
REQUEST=AUTH | RACHECK |
REQUEST=DEFINE | RACDEF |
REQUEST=EXTRACT | RACXTRT |
REQUEST=FASTAUTH | FRACHECK |
REQUEST=LIST | RACLIST |
REQUEST=STAT | RACSTAT |
REQUEST=VERIFY | RACINIT |
The following list provides a brief description of the independent RACF system macros.
- FRACHECK
- Used to provide authorization checking when a user requests access to a RACF-protected resource, similar to RACHECK. However, FRACHECK verifies access to only those resources that have RACF profiles brought into main storage by the RACLIST macro service.
- RACDEF
- Used to define, modify, or delete resource profiles for RACF.
- RACHECK
- Used to provide authorization checking when a user requests access to a RACF-protected resource.
- RACINIT
- Used to provide RACF user identification and verification.
- RACLIST
- Used to retrieve general-resource profiles and build an in-storage list for faster authorization checking. The list is attached to the ACEE.
- RACSTAT
- Used to determine whether RACF is active, and, optionally, to determine whether RACF protection is in effect for a given resource class. The RACSTAT macro can also be used to determine whether a resource-class name is defined to RACF.
- RACXTRT
- Used to retrieve or update specified resource-profile fields, or to encode data.
The user receives the RACF system macros as part of the MVS™ product, not as part of RACF. The MVS installation receives these macros even if it does not intend to install RACF.