IBM MQ CICS adapter abend codes
See the Transaction abend codes section of the CICS® documentation for further information.
- QAPI
Unrecognizable API call. All supported API calls are documented in the Function calls.
- System action
The task is ended abnormally.
- QCAL
The WebSphere® MQ CICS adapter has been invoked by CICS for an unknown reason.
- System action
The invoking task is ended abnormally.
- System programmer response
Contact your IBM® support center.
- QCMG
This abend code is issued because the WebSphere MQ CICS adapter error handler is unable to load the message text module CSQFCTAB or CSQCMTXT. This module must be defined as a program entry in CICS, and exists in the WebSphere MQ library under the DFHRPL DD statement in the CICS JCL.
- System action
The task invoking the message handler is ended abnormally.
- System programmer response
Check that the installation process was followed correctly.
- QDCL
An attempt to EXEC CICS LOAD the data conversion service modules was unsuccessful.
- System action
The task is ended abnormally.
- QGAL
CSQCCON had enabled CSQCTRUE with a global area smaller than that needed by CSQCTRUE. This could be due to a mismatch of version level between CSQCCON and CSQCTRUE.
- System action
The task is ended abnormally.
- QNST
A task has issued an API call that requires task switching, but there are no server subtasks available. This is because the subtasks have not yet started, or were not started successfully. (Message CSQC472I is issued for each subtask started; there should be eight of these.)
- System action
The task is ended abnormally.
This abend can also cause CICS to stop. This happens if either:- In-doubt units of work are being resolved at connect time. The connection process requires a server subtask to execute the resolutions, so if there are no subtasks available, the process stops with this reason code. This abend during the resynchronization process causes CICS to stop.
- The abend occurs in a program list table (PLT) program.
- System programmer response
-
Investigate why your system is running so slowly that the subtasks have not yet started.
- QTAL
CSQCCON had enabled CSQCTRUE with a task area smaller than that needed by CSQCTRUE. This could be due to a mismatch of version level between CSQCCON and CSQCTRUE.
- System action
The task is ended abnormally.