The following items may help you identify the problem.
- Is the CAW0LOAD in the z/OS LINKLIST or STEPLIB concatenation?
Add it if it is not.
- Are all of the required DCMs present in the CAIENF startup procedure?
If a required DCM is missing, add the DCM configuration statement to the CAIENF ENFPARMS data set. Some frequently-used DCMs are: CAS9DCM2, KO50DCM2, J152DCM2, and J161DCM2.
- Is the CA application initialization module available to CAIENF through the STEPLIB or the LINKLIST?
If it is not, make it available. Some frequently used application initialization modules are: TSSTCINT, ACFAEINT, and CAKSCINT.
- Check how and where the intercept module is being loaded.
- Is it loaded into the CICS private using the CICS STEPLIB or the CENFLIB DD statement?
- Is it loaded dynamically into the MVS CSA using the CICSREL parameter?
- Is it automatically activated using the MODE(CICS,ON) parameter?
- Is it manually activated with CICS(START,jobname,product)? This method is not supported for CA ACF2 and CA Top Secret.
- Is the module CAILPAM located in the CAI.CAW0LINK data set?
If CAILPAM is not in the system linklist, and the intercept module is being loaded in CICS private, then CAILPAM must be found in the CICS STEPLIB.
- Is the problem happening in all CICS regions?
If yes:
- Are all regions running the same release?
- What release of MVS and JES are running?
- Did it ever work? If it did, what changed?
If no:
- What regions does it work in?
- Check how the intercept module is being loaded.
- Are you getting any messages (like TSS/CICS Phase 1 Initialization... or ACFAE023 CA ACF2 CICS Waiting on CAIENF/CICS Initialization.)?
- DUMPT module=CASESSI csect=CASEWTO. You should see an eyecatcher for DFH1500, DFH1517, DFHSI1517, and DFHPA1108.
- DUMPT module=CASESSI csect=CASECICS. You should see an eyecatcher for DFH1517 and DFHSI1517.
- What does the ENF STATUS display indicate?
Is the CICS job name found in the list? Is the APPLID displayed? Is the auto install feature active?
