Feedback or reason code.
This is used with a message of type MTRPRT to indicate the nature of the report, and is only meaningful with that type of message. The field can contain one of the FB* values, or one of the RC* values. Feedback codes are grouped as follows:
The range of system-generated feedback codes FBSFST through FBSLST includes the general feedback codes listed below (FB*), and also the reason codes (RC*) that can occur when the message cannot be put on the destination queue.
Applications that generate report messages should not use feedback codes in the system range (other than FBQUIT), unless they wish to simulate report messages generated by the queue manager or message channel agent.
On the MQPUT or MQPUT1 calls, the value specified must either be FBNONE, or be within the system range or application range. This is checked whatever the value of MDMT.
General feedback codes:
Message was discarded because it had not been removed from the destination queue before its expiry time had elapsed.
This can be used by a workload scheduling program to control the number of instances of an application program that are running. Sending an MTRPRT message with this feedback code to an instance of the application program indicates to that instance that it should stop processing. However, adherence to this convention is a matter for the application; it is not enforced by the queue manager.
IMS-bridge feedback codes: When the IMS bridge receives a nonzero IMS-OTMA sense code, the IMS bridge converts the sense code from hexadecimal to decimal, adds the value FBIERR (300), and places the result in the MDFB field of the reply message. This results in the feedback code having a value in the range FBIFST (301) through FBILST (399) when an IMS-OTMA error has occurred.
The following feedback codes can be generated by the IMS bridge:
A segment length was zero in the application data of the message.
A segment length was negative in the application data of the message.
A segment length was too big in the application data of the message.
The value of one of the length fields would cause the data to overflow the message buffer.
The value of one of the length fields was one byte too short.
The MDFMT field in MQMD specifies FMIMS, but the message does not begin with a valid MQIIH structure.
The user ID contained in the message descriptor MQMD, or the password contained in the IIAUT field in the MQIIH structure, failed the validation performed by the IMS bridge. As a result the message was not passed to IMS.
An unexpected error was returned by IMS. Consult the WebSphere MQ error log on the system on which the IMS bridge resides for more information about the error.
IMS-generated feedback codes occupy the range FBIFST (300) through FBILST (399). The IMS-OTMA sense code itself is MDFB minus FBIERR.
CICS-bridge feedback codes: The following feedback codes can be generated by the CICS bridge:
The application program specified in the message abended. This feedback code occurs only in the DLREA field of the MQDLH structure.
The EXEC CICS LINK for the application program specified in the message failed. This feedback code occurs only in the DLREA field of the MQDLH structure.
The CICS bridge task was unable to copy a reply to this request to the dead-letter queue. The request was backed out.
This feedback code occurs only in the DLREA field of the MQDLH structure.
This feedback code occurs only in the DLREA field of the MQDLH structure.
The unit of work was backed out, for one of the following reasons:
MQ reason codes: For exception report messages, MDFB contains an MQ reason code. Among possible reason codes are:
This is an output field for the MQGET call, and an input field for MQPUT and MQPUT1 calls. The initial value of this field is FBNONE.
Notices |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
js50956 |