Diagnose CA Datacom/AD Problems

Troubleshooting › Diagnose CA Datacom/AD Problems

Diagnose CA Datacom/AD Problems

This section describes problems that you may encounter with CA Datacom/AD.

CA Datacom Server Job Fails with Message DSV00026E

The CA Datacom Server job or started task fails with a condition code of 16, and the following message is displayed:

DSV00026E-Database open failure. Server initialization ended

This occurs if you start CA Datacom Server before the CA Datacom/AD MUF is started or before the MUF has finished initializing.

Verify that the CA Datacom/AD MUF has started. Wait a short time, and then resubmit the CA Datacom Server job.

CA Datacom Server Job Fails with Message DSV00028E

The CA Datacom Server job or started task fails with the following message:

DSV00028E - Server ended, CCI failure in function: CCIRECV.1

This is caused by a duplicate APPLID value in the CA Datacom Server input parameters.

APPLID is a unique value that identifies the server job to CCI. This must be unique in the CCI system, and that depends upon your CCI environment.

This occurs where multiple CA Datacom Server jobs are in use.

Note: For information about how to resolve this situation, contact Technical Support.

CA Datacom Server Job Fails with Message DSV00092E

The CA Datacom Server job or started task fails with the following message:

DSV00092E-Duplicate SERVERNAME entered

This is caused by an error with CA Datacom Server input parameters—either SERVERNAME is duplicated, or both SERVERNAME and APPLID are duplicated.

SERVERNAME must be different for every copy of CA Datacom Server that is running.

APPLID is a unique value that identifies the server job to CCI. This value must be unique in the CCI system, and that depends upon your CCI environment.

This problem occurs only where multiple CA Datacom Server jobs are in use.

Note: For information about how to resolve this situation, contact Technical Support.

ReportCenter Java Task with Return Code 0137

ReportCenter Java Task terminates with return code 0137.

Syslog message CA CCI API ROUTINE FRR.

This may happen intermittently. To correct the problem:

Ensure that you are running CA Common Services for z/OS 2.2, SP03 or above.
If you are running CA Common Services for z/OS 2.2, SP03, obtain and apply the following POST SP03 HYPER FIXES: QO28980, QO28981, QO28982, QO28990, QO28996, QO29001, QO29004, QO29672, QO30518, QO30507, QO30510, QO30460, and PIB QI29627.

Report Generation Fails with Message NO CONNECTION HANDLE

Running a report fails with messages similar to the following:

java.sql.SQLException:
ca.datacom.db.DBSQLException
ca.datacom.db.DBSQLException
MAINFRAME SERVER ERROR:
NO CONNECTION HANDLE
No receiver online in Session(executeImmediate)in Query(prepare)

The CA Datacom Server job is down and no database connection is possible.

Resubmit the CA Datacom Server job, and then restart the ReportCenter Java Task.

Report Generation Fails with Message UNEXPECTED ENGINE ERROR

Running a report fails with messages similar to the following:

java.sql.SQLException
ca.datacom.db.DBSQLException
ca.datacom.db.DBSQLException
MAINFRAME SERVER ERROR: UNEXPECTED ENGINE ERROR
No receiver online in Session(executeImmediate)in Query(prepare)

A similar UNABLE TO ALLOCATE MEMORY message may also occur.

The CA Datacom/AD Multi-User Facility (MUF) has started with too small a region size.

With simple usage, the default size at installation time of 6144 will suffice; however, CA Datacom SQL usage generally requires a larger region size. Modify your CA Datacom/AD job/task to use a larger region size, and then restart CA Datacom/AD, CA Datacom Server, and the ReportCenter Java task.