WebSphere MQ-IMS bridge Messages (CSQ2...)
CSQ2001Icsect-name OTMA REJECTED MESSAGE - APPLICATION ERROR, SENSE CODE=code, XCFGNAME=gname XCFMNAME=mname TPIPE=tpipenameExplanation:Because of an application error, the MQ-IMS bridge received a negative acknowledgement (NAK) from OTMA when sending a message. The information provided in the message is:
- gname
- The XCF group to which the partner belongs.
- mname
- The member name of the partner.
- tpipename
- The name of the Tpipe used by the partner.
- code
- The IMS sense code returned by the partner (the first four characters are the sense code).
System Action:The message is put to the dead-letter queue, and processing continues.
System Programmer Response:Refer to the IMS/ESA Open Transaction Manager Access Guide for information about the sense code from IMS.
CSQ2002Ecsect-name OTMA CLIENT BID REJECTED, XCFGNAME=gname XCFMNAME=mname, SENSE CODE=codeExplanation:An OTMA client bid command from the MQ-IMS bridge was rejected. code is the associated IMS sense code. gname and mname identify the partner IMS system to which the command was directed.
System Action:No connection is made to the IMS system. Connections to other OTMA partners are unaffected.
System Programmer Response:Refer to the IMS/ESA Open Transaction Manager Access Guide for information about the sense code from IMS.
CSQ2003Ecsect-name OTMA REJECTED MESSAGE - SYSTEM ERROR, SENSE CODE=code, XCFGNAME=gname XCFMNAME=mname TPIPE=tpipenameExplanation:Because of a system-related error, the MQ-IMS bridge received a negative acknowledgement (NAK) from OTMA when sending a message. The information provided in the message is:
- gname
- The XCF group to which the partner belongs.
- mname
- The member name of the partner.
- tpipename
- The name of the Tpipe used by the partner.
- code
- The IMS sense code returned by the partner (the first four characters are the sense code).
System Action:If the problem was caused by an environmental error, the IMS bridge returns the message to the queue, and closes the queue.
If a severe error occurred, the message is returned to the queue, and the IMS bridge ends abnormally with completion code X'5C6' and reason code X'00F20059'.
System Programmer Response:Refer to the IMS/ESA Open Transaction Manager Access Guide for information about the sense code from IMS.
CSQ2004Ecsect-name ERROR USING QUEUE q-name, MQRC=mqrcExplanation:The MQ-IMS bridge was unable to open, close, get from, put to, or inquire about a queue.
If csect-name is CSQ2QCP0, the problem was with the message queue associated with IMS or the reply-to queue. If csect-name is CSQ2QCP1, the problem was with the reply-to queue. If csect-name is CSQ2PUTD, the problem was with the dead-letter queue.
System Action:If the problem was caused by an environmental error, processing continues.
If a severe error occurred, the IMS bridge ends abnormally with completion code X'5C6' and a reason code which shows the particular error.
System Programmer Response:Refer to Appendix A. API completion and reason codes for information about mqrc.
CSQ2005Icsect-name ERROR PROCESSING MESSAGE, FEEDBACK=code, XCFGNAME=gname XCFMNAME=mname TPIPE=tpipenameExplanation:The MQ-IMS bridge encountered an error while processing a message. code is the associated feedback code that will be set in the messagedescriptor. The information provided in the message is:
- gname
- The XCF group to which the partner belongs.
- mname
- The member name of the partner.
- tpipename
- The name of the Tpipe used by the partner.
- code
- The IMS sense code returned by the partner.
System Action:The message is not processed.
System Programmer Response:code is one of the following:
- 291 (MQFB_DATA_LENGTH_ZERO)
- A segment length field was zero in the application data of the message.
- 292 (MQFB_DATA_LENGTH_NEGATIVE)
- A segment length field was negative in the application data of the message.
- 293 (MQFB_DATA_LENGTH_TOO_BIG)
- A segment length field was too big in the application data of the message.
- 294 (MQFB_BUFFER_OVERFLOW)
- The value of one of the length fields would overflow the MQ message buffer.
- 295 (MQFB_LENGTH_OFF_BY_ONE)
- The length field was one byte too short.
- 296 (MQFB_IIH_ERROR)
- The MQMD specified MQFMT_IMS, but the message does not begin with a valid MQIIH structure.
- 298 (MQFB_NOT_AUTHORIZED_FOR_IMS)
- The user ID specified in the MQMD was denied access.
- 3xx
- IMS sense code xx (where xx is the decimal representation of the IMS sense code). Refer to the IMS/ESA Open Transaction Manager Access Guide for information about the sense code from IMS.
CSQ2006Icsect-name DEAD-LETTER QUEUE UNAVAILABLE, MQRC=mqrcExplanation:The MQ-IMS bridge was unable to put a message to the dead-letter queue.
System Action:If the message was being sent to IMS, it will be retained on the local IMS queue, and the queue will be disabled. If the message was coming from IMS, a NAK will be sent to IMS so that IMS will retain it and stop sending messages on the Tpipe.
System Programmer Response:If mqrc is 0, there is no dead-letter queue defined; you are strongly recommended not to use the MQ-IMS bridge unless you have a dead-letter queue defined. Otherwise, there is a problem obtaining the name of the queue from the queue manager; refer to Appendix A. API completion and reason codes for information about mqrc.
CSQ2009Icsect-name PREREQUISITE PRODUCTS FOR IMS BRIDGE NOT AVAILABLEExplanation:The MQ-IMS bridge cannot operate because:
- The version of z/OS or OS/390 being used is not correct
- The version of IMS being used is not correct
- OTMA support has not been enabled on IMS.
- An incorrect version of the system parameter module (CSQZPARM) is being used.
System Action:The MQ-IMS bridge does not start.
System Programmer Response:Refer to the WebSphere MQ for z/OS Concepts and Planning Guide for information about what product levels are required.
If required, recompile CSQZPARM with the correct libraries.
CSQ2010Icsect-name CONNECTED TO PARTNER, XCFGNAME=gname XCFMNAME=mnameExplanation:The MQ-IMS bridge successfully established a connection to the partner IMS system identified by gname and mname.
System Action:Processing continues; messages can be sent to the partner.
CSQ2011Icsect-name DISCONNECTED FROM PARTNER, XCFGNAME=gname XCFMNAME=mnameExplanation:The partner IMS system identified by gname and mname is no longer available, and the connection from the MQ-IMS bridge has ended.
System Action:Processing continues; messages can no longer be sent to the partner.
CSQ2012Icsect-name NO UTOKEN SECURITY REQUESTED FOR IMS SIGNON, XCFGNAME=gname XCFMNAME=mnameExplanation:The MQ-IMS bridge signed-on to the partner IMS system identified by gname and mname. No UTOKEN security was requested for this session.
System Action:Processing continues.
CSQ2013Ecsect-name NOT AUTHORIZED FOR IMS SIGNON, XCFGNAME=gname XCFMNAME=mnameExplanation:The MQ-IMS bridge tried to sign on to the partner IMS system identified by gname and mname. However, the queue manager not authorized to establish a connection to this IMS system.
System Action:No connection is made to the IMS system. Connections to other OTMA partners are unaffected.
CSQ2015Icsect-name IMS BRIDGE ALREADY SUSPENDED, XCFGNAME=gname XCFMNAME=mnameExplanation:A SUSPEND QMGR FACILITY(IMSBRIDGE) command was issued, but the MQ-IMS bridge to the partner IMS system identified by gname and mname is already suspended.
System Action:None.
CSQ2016Icsect-name IMS BRIDGE NOT SUSPENDED, XCFGNAME=gname XCFMNAME=mnameExplanation:A RESUME QMGR FACILITY(IMSBRIDGE) command was issued, but the MQ-IMS bridge to the partner IMS system identified by gname and mname is not suspended.
System Action:None.
CSQ2020Ecsect-name RESYNCHRONIZATION ERRORExplanation:A resynchronization error has occurred. The information provided by this message is:
IN TPIPE tpipename FOR QUEUE q-name, BY PARTNER, XCFGNAME=gname XCFMNAME=mname, QMGR SEND=sendseq PARTNER RECEIVE=otmarecvseq, QMGR RECEIVE=recvseq PARTNER SEND=otmasendseq, INDOUBT UNIT OF RECOVERY uridwhere:
- tpipename
- The name of the Tpipe which cannot be resynchronized
- q-name
- The name of the queue for this Tpipe
- gname
- The name of the XCF group to which the Tpipe belongs
- mname
- The name of the XCF member to which the Tpipe belongs
- sendseq
- The recoverable sequence number of the message last sent by MQ to the partner, in hexadecimal
- otmasendseq
- The recoverable sequence number of the message last sent by the partner to MQ, in hexadecimal
- recvseq
- The recoverable sequence number of the message last received by MQ from the partner, in hexadecimal
- otmarecvseq
- The recoverable sequence number of the message last received by the partner from MQ, in hexadecimal
- urid
- The identifier of an in-doubt unit of recovery; a value of 0 means that there is no in-doubt unit of recovery.
System Action:No messages are sent on the Tpipe.
System Programmer Response:Use the RESET TPIPE command to reset recoverable sequence numbers, to restart the Tpipe, and, if required, to resolve the unit of recovery.
CSQ2023Ecsect-name PARTNER, XCFGNAME=gname XCFMNAME=mname, CANNOT RESYNCHRONIZE, SENSE CODE=codeExplanation:MQ was unable to resynchronize with the partner. The information provided in the message is:
- gname
- The name of the XCF group to which the partner belongs.
- mname
- The member name of the partner who cannot resynchronize.
- code
- The IMS sense code returned by the partner (the first four characters are the sense code).
System Action:The connection to OTMA is stopped
System Programmer Response:See the IMS/ESA Open Transaction Manager Access Guide for information about the sense code from IMS. Resolve the problem and restart the OTMA connection.
CSQ2024Ecsect-name TPIPE tpipename IS UNKNOWN TO PARTNER, XCFGNAME=gname XCFMNAME=mnameExplanation:The Tpipe name was unknown to the partner. The information provided in the message is:
- tpipename
- The name of the Tpipe which the partner no longer recognizes.
- gname
- The XCF group to which the partner belongs.
- mname
- The member name of the partner who is resynchronizing
System Action:The associated unit of recovery is backed out and processing continues.
System Programmer Response:None.
CSQ2025Ecsect-name PARTNER, XCFGNAME=gname XCFMNAME=mname, CANNOT RESYNCHRONIZE TPIPE tpipename, SENSE CODE=codeExplanation:The partner was unable to resynchronize the Tpipe. The information provided in the message is:
- gname
- The XCF group to which the partner belongs.
- mname
- The member name of the partner who is resynchronizing.
- tpipename
- The name of the Tpipe which the partner cannot resynchronize.
- code
- The IMS sense code returned by the partner.
System Action:The Tpipe is stopped.
System Programmer Response:See the IMS/ESA Open Transaction Manager Access Guide for information about the sense code from IMS. Resolve the problem and restart or reset the Tpipe.
CSQ2026Icsect-name PARTNER, XCFGNAME=gname XCFMNAME=mname, HAS COLD-STARTED TPIPE tpipenameExplanation:The partner has cold started a Tpipe. The information provided in the message is:
- gname
- The XCF group of which the partner is a member.
- mname
- The member name of the partner who is resynchronizing.
- tpipename
- The name of the Tpipe which the partner has cold started.
System Action:All recoverable sequence numbers are reset to 1, and processing continues.
System Programmer Response:None.
CSQ2027Icsect-name TPIPE tpipename FOR PARTNER, XCFGNAME=gname XCFMNAME=mname, DOES NOT HAVE AN INDOUBT UNIT OF RECOVERYExplanation:MQ expected a Tpipe to have an in-doubt unit of recovery. The information provided by the message is:
- tpipename
- The name of the Tpipe for which there should be a unit of recovery still in doubt
- gname
- The XCF group to which the partner belongs.
- mname
- The member name of the partner for the Tpipe.
System Action:Processing continues.
System Programmer Response:Collect the following items, and contact your IBM support center.
- Console log
- MQ job log
- IMS job log
CSQ2028Icsect-name QUEUE MANAGER IS NOT CONNECTED TO PARTNER, XCFGNAME=gname XCFMNAME=mnameExplanation:MQ is not connected to the partner. The information provided in the message is:
- gname
- The group name of the partner.
- mname
- The member name of the partner.
System Action:The command is rejected.
System Programmer Response:Resubmit the command using the correct XCF group name when MQ is connected to the partner.
CSQ2029Icsect-name TPIPE tpipename NOT FOUND FOR PARTNER, XCFGNAME=gname XCFMNAME=mnameExplanation:The Tpipe could not be found. The information provided in this message is:
- tpipename
- The name of the Tpipe which could not be found.
- gname
- The XCF group of which the partner is a member.
- mname
- The member name of the partner for the Tpipe.
System Action:The command is rejected.
System Programmer Response:Resubmit the RESET TPIPE command with the correct Tpipe name.
CSQ2030Icsect-name TPIPE tpipename IS STILL OPEN FOR PARTNER, XCFGNAME=gname XCFMNAME=mnameExplanation:The Tpipe is still open. The information provided by this message is:
- tpipename
- The name of the Tpipe which is still open.
- gname
- The XCF group name.
- mname
- The member name of the partner for the Tpipe.
System Action:The command is rejected.
System Programmer Response:Resubmit the RESET TPIPE command with the correct Tpipe name.
CSQ2031Icsect-name TPIPE tpipename FOR PARTNER, XCFGNAME=gname XCFMNAME=mname, ACTION REQUIRED FOR INDOUBT UNIT OF RECOVERYExplanation:A Tpipe has an in-doubt unit of recovery, but no recovery action was specified. The information provided by the message is:
- tpipename
- The name of the Tpipe which has a unit of recovery still in doubt
- gname
- The XCF group to which the partner belongs.
- mname
- The member name of the partner for the Tpipe.
System Action:Processing continues.
System Programmer Response:Resubmit the RESET TPIPE command specifying an action (COMMIT or BACKOUT) for the in-doubt unit of recovery.