WebSphere MQ CICS adapter abend codes

 

QAPI
Explanation:

Unrecognizable API call. All supported API calls are documented in the WebSphere MQ Application Programming Reference.

System Action:

The task is ended abnormally.

Programmer Response:

See the WebSphere MQ Application Programming Reference manual for details of the API calls.

QCAL
Explanation:

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
Explanation:

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
Explanation:

An attempt to EXEC CICS LOAD the data conversion service modules was unsuccessful.

System Action:

The task is ended abnormally.

Programmer Response:

Ensure that the correct library concatenation has been specified in the CICS DFHRPL. Ensure that you have updated your CICS CSD to include CSQAVICM.

QGAL
Explanation:

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.

Programmer Response:

Check that the versions of CSQCCON and CSQCTRUE are compatible. If you are unable to solve the problem, contact your IBM support center.

QLOP
Explanation:

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:

  • MQRC_CONNECTION_BROKEN

  • MQRC_CONNECTION_NOT_AUTHORIZED

  • MQRC_CONNECTION_STOPPING

  • MQRC_Q_MGR_NAME_ERROR

  • MQRC_Q_MGR_NOT_AVAILABLE

  • MQRC_Q_MGR_STOPPING

Notes:

  1. This runaway mechanism can be activated only after the WebSphere MQ CICS adapter has been enabled once (the adapter is enabled if an attempt is made to connect to MQ). Before the adapter has been enabled, such a task will loop with completion code set to MQCC_FAILED and reason code MQRC_ADAPTER_NOT_AVAILABLE.

  2. The task will end abnormally even if a syncpoint is issued between successive MQ API calls.

System Action:

The task is ended abnormally.

Programmer Response:

Ensure that applications respond to this reason code by abending.

QNST
Explanation:

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 abend. 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 abends with this reason code. This abend during the resynchronization process causes CICS to abend.

  • The abend occurs in a program list table (PLT) program.

System Programmer Response:

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.

QTAL
Explanation:

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.

Programmer Response:

Check that the versions of CSQCCON and CSQCTRUE are compatible. If you are unable to solve the problem, contact your IBM support center.