WebSphere MQ CICS bridge abend codes

 

CKB0

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.

CKB1

Explanation:

An internal logic error has been detected in the CICS bridge monitor.

System Action:

Message CSQC750E is written to the CICS CSMT transient data queue and the CICS bridge monitor task is ended abnormally.

Programmer Response:

See the description of message CSQC750E for more information.

CKB2

Explanation:

The CICS bridge monitor has terminated with CICS bridge tasks still active.

System Action:

Message CSQC744E is written to the CICS CSMT transient data queue and the CICS bridge monitor task is ended abnormally.

Programmer Response:

See the description of message CSQC744E for more information.

CKB3

Explanation:

The CICS DPL bridge program has detected an error in a request message for this unit of work.

System Action:

All request messages for this unit of work are copied to the dead-letter queue with an MQFB_CICS_* reason code. Corresponding error messages are written to the CICS CSMT transient data queue. An MQCRC_BRIDGE_ERROR reply is sent to the reply-to queue if requested. The CICS bridge task is ended abnormally.

Programmer Response:

See the description of the accompanying messages for more information.

CKB4

Explanation:

The CICS bridge monitor or DPL bridge program abended due to an unexpected return code from an EXEC CICS API call.

System Action:

Message CSQC704E is written to the CICS CSMT transient data queue and the CICS bridge monitor or DPL bridge program is abnormally terminated.

Programmer Response:

See the description of message CSQC704E for more information.

CKB5

Explanation:

The CICS bridge monitor or DPL bridge program abended due to an unexpected return code from an MQ API call.

System Action:

Message CSQC710E is written to the CICS CSMT transient data queue and the CICS bridge monitor or DPL bridge program is abnormally terminated.

Programmer Response:

See the description of message CSQC710E for more information.

CKB6

Explanation:

The CICS bridge message handling program is unable to proceed because its COMMAREA is too small.

System Action:

The CICS bridge monitor is abnormally terminated.

Programmer Response:

Check that you are running consistent versions of the CICS bridge monitor program CSQCBR00, and the message handling program CSQCBTX.

CKB7

Explanation:

The CICS DPL bridge program abended before processing any messages for the unit of work.

System Action:

All request messages for this unit of work are left on the CICS bridge queue to be handled by the CICS bridge monitor.

Programmer Response:

See the description of the accompanying messages for more information.

CKB8

Explanation:

The CICS DPL bridge program abended during error processing.

System Action:

An unexpected error occurred during CICS DPL bridge error processing.

Programmer Response:

See the description of the accompanying messages for more information. If the problem reoccurs, contact your IBM support center.

MBRA

Explanation:

The type of EXEC CICS RECEIVE request does not match the next BRMQ vector.

System Action:

The transaction is abnormally terminated.

Programmer Response:

This indicates a programming error in creating the input vectors. Use CEDX, or another programming tool to understand the transaction's input requests. Check whether the RECEIVE requests are TC or BMS.

MBRB

Explanation:

The size of the EXEC CICS SEND MAP request is too large for the output buffer (the maximum size is 20 KB).

System Action:

The transaction is abnormally terminated.

Programmer Response:

This transaction cannot be run using this version of the CICS bridge exit. If ADSDs were requested, it might be possible to run the transaction using the bridge without ADSDs.

MBRC

Explanation:

An error occurred issuing an EXEC CICS SYNCPOINT request.

System Action:

The transaction is abnormally terminated.

Programmer Response:

This is probably a failure in a CICS resource. Look at the accompanying CICS messages.

MBRD

Explanation:

An error occurred issuing an EXEC CICS SYNCPOINT ROLLBACK request.

System Action:

The transaction is abnormally terminated.

Programmer Response:

This is probably a failure in a CICS resource. Look at the accompanying CICS messages.

MBRE, MBRF, MBRG

Explanation:

The CICS bridge exit received an unexpected return code from an MQ API call.

System Action:

The transaction is abnormally terminated. The request messages are moved to the dead-letter queue.

Programmer Response:

See the description of any accompanying MQ error messages for more information.

MBRH

Explanation:

MQCIH field ConversationalTask was set to MQCCT_NO, but the task was conversational.

System Action:

The transaction is abnormally terminated.

Programmer Response:

Either set this field to MQCCT_YES, or supply a BRMQ vector with the input data.

MBRI

Explanation:

The size of the request message is too large for the input buffer (the maximum size is 20 KB).

System Action:

The transaction is abnormally terminated. The request messages are moved to the dead-letter queue.

Programmer Response:

Split the message into multiple messages.

MBRJ

Explanation:

The contents of the MQCIH or BRMQ vectors are incorrect.

System Action:

The transaction is abnormally terminated.

Programmer Response:

Look at the AbendCode and the ErrorOffset in the MQCIH of the reply.

MBRK

Explanation:

The start data received by the CICS bridge exit is incorrect.

System Action:

The transaction is abnormally terminated.

Programmer Response:

This either indicates a storage overwrite, or an error in CKBR. Look at the dump to determine if this is a storage overwrite. If not, contact your IBM support center.

MBRM

Explanation:

The CICS bridge exit received invalid calling parameters from CICS.

System Action:

The transaction is abnormally terminated. The request messages are moved to the dead-letter queue.

Programmer Response:

This is probably the result of a storage overwrite. Look at the accompanying CICS dump to investigate the cause of the storage overwrite.

MBRN

Explanation:

The request message was truncated.

System Action:

The transaction is abnormally terminated.

Programmer Response:

Check the program that put the message onto the bridge queue.

MBRO, MBRP

Explanation:

The contents of the MQCIH or BRMQ vectors are incorrect.

System Action:

The transaction is abnormally terminated.

Programmer Response:

Look at the AbendCode and the ErrorOffset in the MQCIH of the reply.

MBRQ

Explanation:

A requested map did not have an associated ADSD.

System Action:

The transaction is abnormally terminated.

Programmer Response:

Look at the transaction dump to find the map in error. Regenerate the map using CICS Transaction Server V1.2 or later. If the source of the map is not available, it can be regenerated. See the CICS Transaction Server documentation for more details.

MBRS

Explanation:

The CICS bridge exit received an unexpected return code from an MQ API call to open a queue.

System Action:

The transaction is abnormally terminated. All request messages for this unit of work are left on the CICS bridge queue to be handled by the CICS bridge monitor.

Programmer Response:

See the description of any accompanying MQ error messages for more information.

MBR1, MBR2, MBR3, MBR6

Explanation:

The CICS bridge exit received invalid calling parameters from CICS.

System Action:

The transaction is abnormally terminated. The request messages are moved to the dead-letter queue.

Programmer Response:

This is probably the result of a storage overwrite. Look at the accompanying CICS dump to investigate the cause of the storage overwrite.

MBR7

Explanation:

The size of the EXEC CICS TC output request is too large for the output buffer (the maximum size is 20 KB).

System Action:

The transaction is abnormally terminated.

Programmer Response:

This transaction cannot be run using this version of the CICS bridge exit. The CICS bridge exit received invalid calling parameters from CICS.

System Action:

The transaction is abnormally terminated. The request messages are moved to the dead-letter queue.

Programmer Response:

This is probably the result of a storage overwrite. Look at the accompanying CICS dump to investigate the cause of the storage overwrite.

MBR8

Explanation:

The mapset name in the next BRMQ vector does not match the CICS request.

System Action:

The transaction is abnormally terminated.

Programmer Response:

This indicates a programming error in creating the input vectors. Use CEDX, or another programming tool to understand the transaction's input requests.

MBR9

Explanation:

The map name in the next BRMQ vector does not match the CICS request.

System Action:

The transaction is abnormally terminated.

Programmer Response:

This indicates a programming error in creating the input vectors. Use CEDX, or another programming tool to understand the transaction's input requests.

MQB1

Explanation:

The CICS bridge exit received an unexpected return code from an MQ API call when processing a backout request.

System Action:

The transaction is abnormally terminated. The request messages are moved to the dead-letter queue.

Programmer Response:

See the description of any accompanying MQ error messages for more information.

MQB2

Explanation:

The CICS bridge exit received an unexpected return code from an MQ API call when processing a commit request.

System Action:

The data is not committed. The transaction is abnormally terminated. The request messages are moved to the dead-letter queue.

Programmer Response:

See the description of any accompanying MQ error messages for more information.

MQB4

Explanation:

The CICS bridge exit was unable to reread messages from the bridge request queue during backout processing.

System Action:

The request messages are left on the CICS bridge queue with MQMD.BackoutCount set to 1.

Programmer Response:

See the description of any accompanying MQ error messages for more information.