Managing CA Chorus Components › How to Start CA Chorus › Start CA Chorus for Security and Compliance Management Components › Start CA ACF2

Start CA ACF2

After you configure CA ACF2, you can start the product.

Before starting CA ACF2, verify the following:

• CAIRIM is installed. (CAIRIM is part of the CA Common Services.)
• The TSO procedure IKJACCNT is available. This procedure is the default used for your initial signon with the default user ID and default GSO TSO options.

Follow these steps:

1. Start CA ACF2 using one of these methods:
   • If you want to start CA ACF2 automatically and you have edited the CAISECXX member of CAI.CAACF.PARMLIB as described in CA ACF2 System Initialization, do the following:
     • Copy CAISECXX from CAI.CAACF.PARMLIB into the CAISECxx member of SYS1.PARMLIB.
     • Copy the CAIACFXX member from CAI.CAACF.PARMLIB into the CAIACFxx member of SYS1.PARMLIB. It contains the CA ACF2 startup parameters.

     You can proceed to item #3 at this point.

   • If you want to start CA ACF2 manually, add the S ACF2 command to the COMMNDxx member of SYS1.PARMLIB. Because CA ACF2 runs as a subsystem, it should be fully initialized before you process any job with JES2 or JES3.
2. Construct the initial set of Global System Options (GSO) records.

   During the initial IPL, CA ACF2 attempts to locate GSO records. When CA ACF2 detects that no records are present, it prompts the operator for continuation options as shown in the following sample. Reply as indicated to construct the initial set of GSO records. Subsequent CA ACF2 startups do not require operator intervention.

   ACF79505 INITIAL START IN PROGRESS FOR SYSTEM: sysid
   ACF79510 WARNING: NO GSO RECORDS FOUND FOR SYSTEM: sysid
   *10 ACF79517 CONTINUE GSO PROCESSING WITH DEFAULT VALUES?
   reply 10,u
   ACF79530 NO GSO RECORD FOUND FOR: recid SYSID: sysid
   *11 ACF79534 CONFIRM USE OF DEFAULTS FOR: recid SYSID: sysid
   reply 11,u
   ACF79507 GSO PROCESSING COMPLETED WITHOUT ERROR
   

   If you are migrating from a prior version, changes or additions to GSO options can result in warning message ACF79600, which indicates that the record is outdated. This message is normal. Change the records flagged to set the new or changed option as appropriate for the site. Refresh the GSO record to put the option into effect.

   Note: When a new field is added to an existing GSO record, the value of the new field is not necessarily the default value specified in the documentation. This is because when a new field is added to an existing GSO record, the new field assumes the value that is in the area of the record that it now represents. To ensure the default values are used for new fields, the record must be inserted by the current version of CA ACF2.

3. Start JES.

   JES2 needs only a warm start. JES3 requires a hot start.

4. Start TSO and log on to the system as ACFUSER or the site‑specified logonid supplied in job INITIAL.
5. Complete the following if you have a shared DASD environment.

   The CA ACF2 GSO BACKUP record should include the CPUID parameter to identify the single system responsible for backup processing. You can use the NOBACKUP parameter of the S ACF2 command to deactivate automatic backup processing on a given system. BACKUP is the default. For more information, see the chapter “Maintaining Global System Options Records” in the Administrator Guide.

You no longer need to identify the CA ACF2 subsystem name in IEFSSNxx in SYS1.PARMLIB. CA ACF2 intercepts the system security initialization module and dynamically installs its own subsystems by building subsystem control table (SSCT) entries.