LIST or DECOMP all ACF2 rules for a certain type code
search cancel

LIST or DECOMP all ACF2 rules for a certain type code

book

Article ID: 25884

calendar_today

Updated On:

Products

ACF2 ACF2 - z/OS ACF2 - MISC

Issue/Introduction

How can all the ACF2 rules for a specific type code be LISTed or DECOMPed into a PDS?

Resolution

Using the ACF command in TSO, both the LIST and the DECOMPILE can be accomplished. The following is an example using the type code CKC.

Enter the following to LIST all of the rules:

 ACF                                                                  
 SET RESOURCE(CKC)                                                        
 LIST LIKE(-)  

or to decompile all the rules into a PDS:

 ACF 
 SET RESOURCE(CKC)
 DECOMP LIKE(-) INTO('MY.PDS')                            

If there is no dataset called MY.PDS, then ACF2 will allocate a PDS called MY.PDS and decompile each rule into separate members in the PDS. If you specify no member name, ACF2 uses the $KEY and $MEMBER values of the rule set to determine the member name. If the rule set has a $MEMBER control statement, the $MEMBER value is used as the member name. If the rule set has no $MEMBER control statement, the $KEY of the rule set is used as the member name. If the $KEY value is invalid as a member name, ACF2 automatically generates a member name in the format @nnnnnnn (where nnnnnnn is a numeric from 0000001 to 9999999). Also, if the quote marks are not used for the dataset name, ACF2 will use the issuers TSO prefix setting to decide on the high level qualifier. So if the logonid of the user is SECURITY and the user's LOGONID has DFT-PFX(SECURITY), then the PDS name would be SECURITY.MY.PDS. If the user has DFT-PFX() the dataset name would be MY.PDS.