Troubleshooting the CICS DA server installation

This information contains common problems that you might encounter when you run the CICS® DA server, and the causes. You must ensure that you run all the installation and configuration steps before you start the CICS DA server

Problems encountered when you start the server for the first time

If you missed out one or more of the installation and configuration steps, you might see one of the following symptoms:

Table 1. Server installation symptoms
Symptom Possible cause
The CICS DA server fails to start. A return code of 31 is shown in the server JESMSGLG. Program Control for CICS DA HFS is not established. Check that program control for CICS DA HFS programs is correctly established.
The CICS DA server fails to start. A return code of 32 is shown in the server JESMSGLG. The DLL libcphping.so cannot be found. The DLL libcphping.so is in the lib directory that is created during the SMP/E installation. For example, the default directory path is /usr/lpp/cicsda/v530/lib. The directory path must be included on the CPH_LIB environment variable in the cphenvar file, which is described in the task Configure CICS DA.
The CICS DA server starts but discovery and job retrieval fails with a not authorized message, such as CPHSV0020I User user is not authorized to invoke command command. Program Control for CICS DA load library is not established. Check that program control for CICS DA load library is correctly established.
A discovery operation completes but many of the CICSPlex SM resources are missing from the CICS DA model, and managed regions are reported as being unmanaged. There might be an authorization problem. Check that the CICS DA server ID has full authorization to access CICSPlex SM and all resources.
A discovery operation completes but managed servers are reported as being unmanagaed, and CPHRC0037I messages are seen in the discovery report. There might be an authorization problem. Check that PassTickets have been set up correctly, or if you are using passwords, check that the DA server ID password is correct.
Messages ICH420I or BPXP014I are shown in the CICS DA JESMSGLOG. Program Control for CICS DA load library is not established. Check that program control for CICS DA load library is correctly established.
Messages BPXM023I and CPHSV0025W Failed to generate PassTicket for client ID are shown in the CICS DA JESMSGLOG. PassTicket support is not set up correctly. Review Step 1 in the topic Authorize CICS DA users and ensure that the correct authorization is in place.
Messages BPXM023I and CPHSJ0000E Jobstep CPHOUT_DISCOVER of jobxxxxx could not be found, or did not complete within the time allowed prefix in the DA Connections dialog. are shown in the CICS DA JESMSGLOG. You might need to increase the retry count and wait times for the discovery jobs.
The server retry count and delay times for the discovery jobs are defined in the cphprops file on HFS:
com.ibm.cph.server.delay=10000
com.ibm.cph.server.retry=60
Note: The timeout values in the DA client connection window are for actions that are only run under the client's user ID, such as Clone.
If the job is taking a long time to be scheduled, or to complete, then you can define a different class in the job card. The job card is also defined in the cphprops file:
com.ibm.cph.server.jobcard=//JOBNAME JOB  ,'CICSDAXGENERATEDXJCL',CLASS=A,\
//         MSGCLASS=H

Problems encountered during production

If the CICS DA server encounters a problem during normal production, one or more error messages are displayed and recorded in the CICS Explorer® error log. The error messages are documented in the CICS Deployment Assistant User Guide in the CICS Explorer product. To view the messages, click Help > Help Contents on the CICS Explorer menu bar. Expand the CICS DA plug-in User Guide section in the Contents pane and navigate to Reference information > Messages . Review the message details and take the prescribed action.



troubleshooting.html | Timestamp icon Last updated: Friday, 11 December 2015