Unrecognizable API call. All supported API calls are documented in the WebSphere MQ Application Programming Reference.
The task is ended abnormally.
See the WebSphere MQ Application Programming Reference manual for details of the API calls.
The WebSphere MQ CICS adapter has been invoked by CICS for an unknown reason.
The invoking task is ended abnormally.
Contact your IBM support center.
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.
The task invoking the message handler is ended abnormally.
Check that the installation process was followed correctly.
An attempt to EXEC CICS LOAD the data conversion service modules was unsuccessful.
The task is ended abnormally.
Ensure that the correct library concatenation has been specified in the CICS DFHRPL. Ensure that you have updated your CICS CSD to include CSQAVICM.
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.
The task is ended abnormally.
Check that the versions of CSQCCON and CSQCTRUE are compatible. If you are unable to solve the problem, contact your IBM support center.
A task has issued more than one API call after they have been returned with completion code MQCC_FAILED and one of the following reason codes:
The task is ended abnormally.
Ensure that applications respond to this reason code by abending.
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.)
The task is ended abnormally.
This abend can also cause CICS to abend. This happens if either:
Check the value of the CTHREAD parameter in CSQ6SYSP, and increase it if it is not large enough. If this is not the cause of the problem, investigate why your system is running so slowly that the subtasks have not yet started. See the WebSphere MQ for z/OS System Setup Guide for information about setting a value for CTHREAD.
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.
The task is ended abnormally.
Check that the versions of CSQCCON and CSQCTRUE are compatible. If you are unable to solve the problem, contact your IBM support center.
Notices |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
csqsao0447 |