Action Notifications

Although the MQSeries interface is asynchronous, the client can receive action notifications back from ITP/Server over a reply queue. In order to do this, the client has to set the ReplyToQMgr and ReplyToQ fields in the descriptor of the request message and set the type of the message to MQMT_REQUEST. Action notifications will have type MQMT_REPORT, format MQFMT_STRING and one of the following feedback codes:

• MQFB_PAN. A Positive Action Notification. These messages will be sent after the request has been processed successfully, but only if the MQRO_PAN option was used in the Report field of the request message descriptor. If sent, no more report messages will be sent for this particular request. Positive action notifications contain a string that indicates that the job has completed successfully.
• MQFB_NAN. A Negative Action Notification. These messages will be sent after a failure, but only if the MQRO_NAN option was used in the Report field of the request message descriptor. If sent, no more report messages will be sent for this particular request. Negative action notifications contain a Unicode message string that explains what went wrong.

Apart from these ITP/Server-related reports the options in the Report field of the request message descriptor may be used to control the following (refer to the MQSeries manuals for more information):

• Report messages generated by MQSeries, such as confirmation of delivery. Note however that these too will only be delivered after the job finishes and commits.
• The contents of MsgId and CorrelId fields in progress messages. These identifiers can be used to relate report messages to the original request.

Note

No negative action notifications will be sent if ITP/Server shuts down in a normal way. It will wait for running jobs to complete. Jobs that have not yet begun executing will be backed out to the request queue, so that they can be processed at another time.

Progress Messages

The MQSeries interface only logs progress messages. Unlike ITP/Document Services it does not return them to the client, because they are incompatible with syncpoint control. With syncpoint control, progress messages can only be delivered to the client at the end of a job, which defeats their purpose.