How to Promote a Test System › Review Potential Security Changes

Review Potential Security Changes

Before you continue, identify your site use case:

• Option A: You are using the same External Security Manager (ESM) database for the existing configuration and the new environment.
• Option B: You are using a new ESM for your new environment.

Reuse ESM

Resource definitions

This list assumes that you are using the same ESM database for the existing configuration and the new environment.

• User IDs: CHORADM / CHORTHD
• APPLIDs: Use the same APPLIDs for CA Chorus and discipline resources.
• PassTickets: Existing passtickets are sufficient provided the user IDs and APPLIDs are not changed.

CHORADM Access

If the new HLQ is not included in the existing rules that give CHORADM access to data sets, give CHORADM access to the same files (low-level name) under the new HLQ. For more information, see the ETJI095x security job. x equals A for CA ACF2, T for CA Top Secret, or R for IBM RACF. The file resides in CETJJCL of the currently installed system.

Note: After you review this topic, go to the applicable deployment procedure in this scenario.

New ESM

1. Locate the applicable ETJI095x security job. x equals A for CA ACF2, T for CA Top Secret, or R for IBM RACF. The file resides in CETJJCL of the currently installed system.

   Note: The security job files also reside on the CA Chorus product page under Content Type, Recommended Reading: ETJI095A for CA ACF2, ETJI095T for CA Top Secret, or ETJI095R for IBM RACF.

   Note: On CA Support Online, the links to the Version 4.0 security jobs are appended with two letters instead of one to differentiate these jobs from the Version 3.0 security jobs: ETJI095AC for CA ACF2, ETJI095TS for CA Top Secret, and ETJI095RA for IBM RACF.

2. Run the security job.
3. Verify that the new environment has the same BPX facilities as the original configured environment.

   Note: You may need to assign CA Chorus resources to users IDs who plan to access it in the new environment. For the steps to authorize users, see the Site Preparation Guide. You can add the authorizations after the new environment is up and running.

4. Confirm that the security requirements for the back-end systems are met. If you reuse the same back-end systems, no changes are necessary.
5. Start the applicable deployment procedure.