The following abend codes are in numeric order.
Reason:
The first argument passed in a CA Datacom/DB call by the application program is not within the CICS partition.
Action:
Correct the application code.
Reason:
The URT number requested through the DCCTFPR module is larger than the number of URTs specified for MAXURTS= when the DBCVTPR module was generated. If a user exit was used, an invalid URT number was returned in register 15. The URT number in error is contained in the seventh byte of the USER 188 TRACE entry.
Action:
Either correct the user exit or increase the MAXURTS= operand of the DBCVTPR module. For more information, see MAXURTS= in the System Reference Guide.
Reason:
In an entry to the DCCOCPR program through a LINK or XCTL, the first five characters of the command area were not correct.
Action:
Correct the command area in the communication area. For more information, see CICS Link in the System Reference Guide.
Reason:
A command did not exist in the DBINRPR.
Action:
Review the CICS DUMP and Trace table. Find out what the command was and confirm it is a legitimate command table command. Contact CA Support and have it added to the DBINRPR command table with its proper function.
Reason:
An initiation of DCCOCPR failed to provide input.
Action:
Review the CICS Trace Table. Correct the CICS system problem that caused the failure.
Reason:
DCCTFPR has changed the register values.
Action:
Check your DCCTFPR prefix and suffix routines and, if you are not using the supplied DCCTFPR, check your DCCTFPR module to verify that it restores registers before returning control.
Reason:
Internal error.
Action:
DC16 errors result from transaction multitasking errors that can occur if a transaction is force-purged while a request is active in CA Datacom and while the application also has an abend-handler routine in effect. A multitasking condition results when the abend-handler routine gets control and issues another CA Datacom request while the first request is active or processing.
Collect the SVC dump and contact CA Support.
Reason:
The transaction exceeded the CA Datacom/DB request threshold count.
Action:
Examine processing logic for errors and correct the program, if necessary.
If no program errors are found, use the DBOC GENOPTS command to increase the threshold count or to exempt the transaction from the threshold count limitation. For more information, see Changing Generation Options Online (DBOC GENOPTS) in the System Reference Guide. Recycle CA Datacom CICS Services with a newcopy of DBCVTPR to implement modifications to DBCVTPR. For more information about changing the REQTHD= parameter of the DBCVTPR macro, see the System Reference Guide.
Reason:
Internal error.
Action:
The DBCVTPR address is missing in the TRUE global work area which resulted in a fatal CA Datacom CICS Services error. Collect the SVC dump and contact CA Support.
Reason:
The Dynamic Plan Selection Table (DCTABPR) is not defined in RDO.
Action:
Define DCTABPR into the RDO definition.
Reason:
The plan exit defined in the Dynamic Plan Selection Table is not defined in RDO.
Action:
Define the program name for the plan exit into RDO.
Reason:
The Dynamic Plan Selection processing module (DCDYNPR) was called by an unknown caller.
Action:
Verify to see if any application program issued a call to DCDYNPR by accident. If the answer is No collect the dump and call CA Support.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|