Security Best Practices › Make RACF Changes

Make RACF Changes

Make RACF changes available to CA7ONL without a restart. CA WA CA 7 Edition calls made to RACF through CA Common Services do a FRACHECK. For this reason, restart CA7ONL to pick up changes to RACF security definitions.

We recommend that you change this processing so that a bounce of CA7ONL is not required after making any RACF changes. Change the FRACHECK to a RACHECK, which does not require a restart to refresh the security definitions. Change the RESTABLE (Resource Class Table) for PA@EL and SU@MIT in the CAS9 module CAS9SAFC from the following:

  DC C'PANEL ',C'PA@EL  ',X'00',X'80',X'00',X'00'
  DC C'SUBMIT',C'SU@MIT ',X'00',X'80',X'00',X'00'

To the following:

  DC C'PANEL ',C'PA@EL  ',X'00',X'00',X'00',X'00'
  DC C'SUBMIT',C'SU@MIT ',X'00',X'00',X'00',X'00'

After you update CAS9SAFC, reassemble and link-edit it using the CAS9 SAMPJCL member CAS9CSSF. Next, reinitialize the CAS9 module CAISSF with the following command in CAIRIM:

CAIRIM REFRESH(SSF)

Business Value:

This best practice enables continuous processing.

Additional Considerations:

Sites can decide to use other resource classes (CALENDAR, RESOURCE, and others) instead of the defaults. Examine your initialization file SECURITY statement, and change RESTABLE appropriately.