Troubleshooting › Identify and Resolve the Problem › CAICCI Troubleshooting Checklist

CAICCI Troubleshooting Checklist

The following items may help you identify the problem.

1. Is the CAICCI subsystem operational?

   For example, if you are receiving message CAS9626I, check to see if the CAICCI subsystem is operational.

2. Have the CAICCI parameters been updated? Are they being referenced by the ENF procedure?

   See the chapter Common Communications Interface in this guide for instructions and examples.

3. Obtain the necessary traces to use in debugging.

   CCIPC TRACE

   Enable trace box from CAICCI/PC Configurator Properties dialog. You can also enable additional SSL tracing at the direction of CA Support by checking the DumpSSL box. The trace output goes to the directory specified on the Trace tab of the Configurator Properties dialog.

   CAICCI MVS LOCAL TRACE

   The following z/OS commands are issued from the console:

   F ENF,CCI(LWTL)  * Activate trace 
   F ENF,CCI(NLWTL) * Deactivate trace
   

   CAICCI MVS REMOTE TRACE

   This z/OS command is issued from the console immediately after the error occurs:

   F ENF,CCI(PRINTT) 
   

   The trace will be written to a TRCPRINT DD that will be dynamically allocated by ENF.

   Note: If ENF is running as a subsystem, it is necessary to specify a TRCPRINT DD statement in the ENF procedure with LRECL=133.

   You cannot specify a SYSOUT data set in this case, and if you specify a catalogued data set, it must be catalogued in the master catalog.

   CAICCI MVS TCP/IP PROTOCOL TRACES

   The following z/OS commands should be issued from the z/OS console, substituting the name of the started task (CCITCP, CCISSL, CCITCPGW or CCISSLGW) for NNNNNN:

   F NNNNNN,T,SYSPRINT * Activate the trace
   F NNNNNN,NOTRACE    * Deactivate the trace
   

   Note: Be sure that a SYSPRINT DD is specified in the proc for the started task. Shut down the started task afterwards to obtain all messages. Request the entire job output.

   CAICCI MVS COMPONENT TRACE

   The following z/OS command, issued from the z/OS console, will activate CAICCI Component Tracing:

   TRACE CT,,COMP=CACCI,PARM=CTECCI00
   

   CTECCI00 is shipped in CAI.CAW0OPTN and must be moved to an MVS PARMLIB data set. As provided in the Option Library, the CTECCI00 member starts tracing and forwarding output to an External Writer. A sample PROC, CCIXWTR, is provided in CAI.CAW0PROC, which invokes the IBM external writer ITTTRCWR. This proc must be placed into SYS1.PROCLIB and be customized to define the external trace data set(s).

   The External Writer copies the Component Trace output into the external trace data sets. The trace records within the data sets can later be processed and examined using a specialized CAICCI formatter running under IPCS.

   An SVC dump of Data Space #CCICT# which belongs to the CAMASTER address space (DSPNAME=CAMASTER.#CCCICT#) can also obtain the Component Trace records.

   Currently CAICCI Component Trace only traces local CCI processing.