IBM MQ-IMS bridge Messages (CSQ2...)

CSQ2001I

csect-name OTMA REJECTED MESSAGE - APPLICATION ERROR, SENSE CODE=code, XCFGNAME=gname XCFMNAME=mname TPIPE=tpipename

Explanation

Because of an application error, the IBM® MQ-IMS bridge received a negative acknowledgment (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

For information about the sense code from IMS, see the IMS product documentation.

CSQ2002E: csect-name OTMA CLIENT BID REJECTED, XCFGNAME=gname XCFMNAME=mname, SENSE CODE=code
Explanation: An OTMA client bid command from the IBM 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: For information about IMS-OTMA sense codes, see OTMA sense codes for NAK messages.

CSQ2003E

csect-name OTMA REJECTED MESSAGE - SYSTEM ERROR, SENSE CODE=code, XCFGNAME=gname XCFMNAME=mname TPIPE=tpipename

Explanation

Because of a system-related error, the IBM MQ-IMS bridge received a negative acknowledgment (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. Depending on the error described by the sense code, the message send is retried or the queue is closed.

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

For information about IMS-OTMA sense codes, see OTMA sense codes for NAK messages.

CSQ2004E

csect-name ERROR USING QUEUE q-name, MQRC=mqrc (mqrc-text)

Explanation

The IBM 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.

If CSQ2PUTD fails to put a message in the dead-letter queue for some reason, the process which gets messages from the IMS bridge queue ends, and is only restarted by disabling and re-enabling the IMS Bridge queue, or by restarting the queue-manager.

If the reason code received is 2042, it is because the IBM MQ-IMS bridge requires exclusive input access (MQOO_INPUT_EXCLUSIVE) to the bridge queue if it is defined with QSGDISP(QMGR), or if it is defined with QSGDISP(SHARED) together with the NOSHARE option.

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 API completion and reason codes for information about mqrc (mqrc-textprovides the MQRC in textual form).

If csect-name is CSQ2PUTD, disable and re-enable the IMS bridge queue, and if that does not work, restart the queue-manager.

CSQ2005I

csect-name ERROR PROCESSING MESSAGE, FEEDBACK=code, XCFGNAME=gname XCFMNAME=mname TPIPE=tpipename

Explanation

The IBM MQ-IMS bridge encountered an error while processing a message. code is the associated feedback code that will be set in the message descriptor. 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.

If there is a loop of CSQ2005I messages causing FEEDBACK=292, see if there is a:

Looping application that is putting badly-formed messages.
Queue, for example the dead letter queue (DEADQ), that is not intended to be read by the IMS Bridge, but is using a STGCLASS with non-blank XCFGNAME and XCFMNAME parameters.

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.
299 (MQFB_DATA_LENGTH_TOO_SHORT): A segment length field was too short in the application data of the message.
3xx: IMS sense code xx (where xx is the decimal representation of the IMS sense code). For information about IMS-OTMA sense codes, see OTMA sense codes for NAK messages.

CSQ2006I: csect-name DEAD-LETTER QUEUE UNAVAILABLE, MQRC=mqrc (mqrc-text)
Explanation: The IBM 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 IBM 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 API completion and reason codes for information about mqrc (mqrc-text provides the MQRC in textual form).

CSQ2007I

csect-name PROCESSING HAS STOPPED FOR IMS BRIDGE QUEUE q-name, XCFGNAME=gname XCFMNAME=mname TPIPE=tpipename

Explanation

This message follows message CSQ2004E, for csect name CSQ2PUTD failing to put a message in the dead-letter queue. The process which gets messages from the IMS bridge queue ends. The information provided in the message is:

q-name: The name of the IMS bridge queue.

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

System action

Messages on this queue are no longer processed by the IMS bridge on this member.

System programmer response

To resume processing, GET-disable, and re-enable the IMS bridge queue or restart the Tpipe for the queue.

CSQ2009I

csect-name PREREQUISITE PRODUCTS FOR IMS BRIDGE NOT AVAILABLE

Explanation

The IBM MQ-IMS bridge cannot operate because:

The version of z/OS® 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 Planning your IBM MQ environment on z/OS for information about what product levels are required.

If required, recompile CSQZPARM with the correct libraries.

CSQ2010I: csect-name CONNECTED TO PARTNER, XCFGNAME=gname XCFMNAME=mname
Explanation: 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.

CSQ2011I: csect-name DISCONNECTED FROM PARTNER, XCFGNAME=gname XCFMNAME=mname
Explanation: The partner IMS system identified by gname and mname is no longer available, and the connection from the IBM MQ-IMS bridge has ended.
System action: Processing continues; messages can no longer be sent to the partner.

CSQ2012I: csect-name NO UTOKEN SECURITY REQUESTED FOR IMS SIGNON, XCFGNAME=gname XCFMNAME=mname
Explanation: The IBM 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.

CSQ2013E: csect-name NOT AUTHORIZED FOR IMS SIGNON, XCFGNAME=gname XCFMNAME=mname
Explanation: The IBM 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.

CSQ2015I: csect-name IMS BRIDGE ALREADY SUSPENDED, XCFGNAME=gname XCFMNAME=mname
Explanation: A SUSPEND QMGR FACILITY(IMSBRIDGE) command was issued, but the IBM MQ-IMS bridge to the partner IMS system identified by gname and mname is already suspended.
System action: None.

CSQ2016I: csect-name IMS BRIDGE NOT SUSPENDED, XCFGNAME=gname XCFMNAME=mname
Explanation: A RESUME QMGR FACILITY(IMSBRIDGE) command was issued, but the IBM MQ-IMS bridge to the partner IMS system identified by gname and mname is not suspended.
System action: None.

CSQ2020E

csect-name RESYNCHRONIZATION ERROR

Explanation

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 urid

where:

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 IBM MQ to the partner, in hexadecimal
otmasendseq: The recoverable sequence number of the message last sent by the partner to IBM MQ, in hexadecimal
recvseq: The recoverable sequence number of the message last received by IBM MQ from the partner, in hexadecimal
otmarecvseq: The recoverable sequence number of the message last received by the partner from IBM 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.

CSQ2023E

csect-name PARTNER, XCFGNAME=gname XCFMNAME=mname, CANNOT RESYNCHRONIZE, SENSE CODE=code

Explanation

IBM 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

For information about IMS-OTMA sense codes, see OTMA sense codes for NAK messages. Resolve the problem and restart the OTMA connection.

CSQ2024E

csect-name TPIPE tpipename IS UNKNOWN TO PARTNER, XCFGNAME=gname XCFMNAME=mname

Explanation

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

If the partner IMS system has been cold started then this message can be considered normal. If the IMS system has not been cold started consider this message as an alert and investigate the partner IMS system.

CSQ2025E

csect-name PARTNER, XCFGNAME=gname XCFMNAME=mname, CANNOT RESYNCHRONIZE TPIPE tpipename, SENSE CODE=code

Explanation

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 OTMA sense codes for NAK messages for information about the sense code from IMS. Resolve the problem and restart or reset the Tpipe.

CSQ2026I

csect-name PARTNER, XCFGNAME=gname XCFMNAME=mname, HAS COLD-STARTED TPIPE tpipename

Explanation

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.

CSQ2027I

csect-name TPIPE tpipename FOR PARTNER, XCFGNAME=gname XCFMNAME=mname, DOES NOT HAVE AN INDOUBT UNIT OF RECOVERY

Explanation

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

CSQ2028I

csect-name QUEUE MANAGER IS NOT CONNECTED TO PARTNER, XCFGNAME=gname XCFMNAME=mname

Explanation

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 IBM MQ is connected to the partner.

CSQ2029I

csect-name TPIPE tpipename NOT FOUND FOR PARTNER, XCFGNAME=gname XCFMNAME=mname

Explanation

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.

CSQ2030I

csect-name TPIPE tpipename IS STILL OPEN FOR PARTNER, XCFGNAME=gname XCFMNAME=mname

Explanation

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

The most likely cause of this message is that the RESET TPIPE command was issued with an incorrect Tpipe name or that the command was issued on the wrong queue manager in a queue sharing group. Resubmit the RESET TPIPE command with the correct Tpipe name.

CSQ2031I

csect-name TPIPE tpipename FOR PARTNER, XCFGNAME=gname XCFMNAME=mname, ACTION REQUIRED FOR INDOUBT UNIT OF RECOVERY

Explanation

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.

CSQ2040I

csect-name OTMA MESSAGE FLOOD STATUS=WARNING FOR PARTNER, XCFGNAME=gname XCFMNAME=mname

Severity

Explanation

This message is issued by the IBM MQ-IMS bridge in response to a notification from the partner IMS system, identified by gname and mname, that an OTMA message flood warning condition exists.

This message indicates that the IMS partner is currently unable to process the volume of transaction requests being sent to it via the IBM MQ-IMS bridge.

System action

Processing continues but the IBM MQ-IMS bridge will slow down the rate at which transaction requests are sent to allow the partner IMS system to process the accumulated backlog.

System programmer response

Review the status of the partner IMS system to determine if any action is required. You can use the /DISPLAY OTMA and /DISPLAY TMEMBER commands to do this.

Perform a check on the partner IMS system to determine if the message DFS1988W has been issued, identifying the severity of the warning condition.

CSQ2041I

csect-name OTMA MESSAGE FLOOD STATUS=FLOODED FOR PARTNER, XCFGNAME=gname XCFMNAME=mname

Severity

Explanation

This message is issued by the IBM MQ-IMS bridge in response to a notification from the partner IMS system, identified by gname and mname, that an OTMA message flood condition exists.

This indicates that the IMS partner is currently unable to process the volume of transaction requests being sent to it through the IBM MQ-IMS bridge. No further requests can be sent until the flood condition in IMS has been relieved.

System action

All TPIPEs to the identified partner IMS system are suspended until a notification is received from IMS indicating that the flood condition has been relieved.

Messages can still be put to any IBM MQ-IMS bridge queue with a storage class specifying the identified IMS partner but will remain there until the TPIPES can be resumed.

IBM MQ-IMS bridge queues for other IMS partners are unaffected.

System programmer response

Review the status of the partner IMS system and determine what action is required to relieve the IMS flood condition. You can use the /DISPLAY OTMA and /DISPLAY TMEMBER commands to do this.

Perform a check on the partner IMS system to determine if the message DFS1989E has been issued, identifying the flood condition.

CSQ2042I: csect-name OTMA MESSAGE FLOOD RELIEVED FOR PARTNER, XCFGNAME=gname XCFMNAME=mname
Severity: 0
Explanation: This message is issued by the IBM MQ-IMS bridge in response to a notification from the partner IMS system, identified by gname and mname, that an OTMA message flood, or flood warning, condition no longer exists.
System action: If this message follows CSQ2041I, all TPIPEs to the identified partner IMS system that were suspended in response to the flood condition are resumed. The IBM MQ-IMS bridge will gradually increase the rate at which transaction requests are sent until the maximum rate is achieved, or a subsequent flood condition is reported by the partner IMS system.
System programmer response: None required.