What is the sort order for ACF2 SAFDEFs that are used for processsing of RACROUTE external security calls?

Products

• ACF2
• ACF2 - z/OS
• ACF2 - MISC

Issue/Introduction

What is the sort order for ACF2 SAFDEFs that are used for processing of RACROUTE external security calls?

 

Environment

Release: ACF2 for z/OS

Resolution

The ACF2 GSO SAFDEF records define the SAF environment and how ACF2 to processes a SAF call.

The ACF2 GSO SAFDEFs are loaded into storage in a specific order from the ACF2 INFOSTG database during ACF2 initialization and when a REFRESH of the GSO SAFDEF RECORDS is performed.

When a RACROUTE call is processed ACF2 will search for a SAFDEF that best matches the RACROUTE parameter list..

The sort sequence for ACF2 GSO SAFDEFs is as follows:  (alphabetical for each number)

1) ENFORCE - This is for internal SAFDEFs which require enforcing.  Enforced SAFDEFs for TOKEN extract processing are not displayed.


2) JOBNAME


3) USERID


4) PROGRAM


5) RB


6) REQSTOR - RACROUTE parameter


7) SUBSYS - RACROUTE parameter


8) REQUEST - RACROUTE parameter


9) SAFDEF - External


10) SAFDEF - Internal


11) SUBSYS - GSO


12) SUBSYS - ACF2

The SHOW SAFDEF sub-command issued under the ACF command will show the current order that the SAFDEF records will be done in, first to last.  The first one that matches the environment of the program, racroute parms, userid etc., will be used, not the last.  The order is sorted from the ACF2 code and the user defined records after an IPL, or when a REFRESH command is issued.

 

Additional Information

Details on ACF2 GSO SAFDEF records can be found in the CA ACF2 for z/OS documentation set online at techdocs.broadcom.com, section marked;   'Environments for SAF Calls (SAFDEF)'.