A report message informs applications about events such
as the occurrence of an error when processing a message.
You can use the MQMD Header Fields tab to
set reporting options that the queue manager will
use.
The following describes the reporting options available on
the MQMD Header Fields tab.
| Parameter | Description |
|---|---|
| Report | Select the check box to generate a report message. A report message informs applications about events such as the occurrence of an error when processing a message. The report can be generated by a queue manager, a message channel agent (if the agent cannot deliver the message), and an enterprise application (if the application cannot use the data in the message). |
| COA | Confirmation on arrival (COA) report
message. This value will indicate that
the message has reached its target
queue. It is generated by the queue
manager. Options are: None — Do not send this report. COA — Send the report without any of the original message data that the queue manager is reporting on. COA with Data — Send the report with the first 100 bytes of the original message data queue that the queue manager is reporting on. COA with Full Data — Send the report with the original message data that the queue manager is reporting on. |
| COD | Confirmation on delivery (COD)
report message. This value will
indicate that the message has been
retrieved by a receiving application.
It is generated by the queue
manager. Options are: None — Do not send this report. COD — Send the report without any of the original message data that the queue manager is reporting on. COD with Data — Send the report with the first 100 bytes of the original message data queue that the queue manager is reporting on. COD with Full Data — Send the report with the original message data that the queue manager is reporting on. |
| Exception | An exception report message. The
report is generated by the message
channel agent or the enterprise
application. Options are: None — Do not send this report. Exception — Send the report without any of the original message data that the message channel agent or the enterprise application is reporting on. Exceptionwith Data — Send the report with the first 100 bytes of the original message data queue that the message channel agent or the enterprise application is reporting on. Exceptionwith Full Data — Send the report with the original message data that the message channel agent or the enterprise application is reporting on. |
| Expiration | An expiry report message. This
indicates that an application attempted
to retrieve a message that had reached
its expiry threshold; the message is
marked to be discarded. This type of
report is generated by the queue
manager. Options are: None — Do not send this report. Expiration — Send the report without any of the original message data that the queue manager is reporting on. Expiration with Data — Send the report with the first 100 bytes of the original message data queue that the queue manager is reporting on. Expiration with Full Data — Send the report with the original message data that the queue manager is reporting on. |
| Reply to Queue | This is the name of the reply queue where you want the report messages sent. |
| Reply to Queue
Manager
|
Optional. This is the name of the queue manager who owns the reply to queue. |
| Expiry
|
This value specifies an interval of
time based on how long the reply
message is valid. Unlimited — Do not limit the time. You can also type a numeric value that will be set as the expiry interval of every message sent by the transport. |
| Priority
|
This value specifies the priority
for delivery of the reply
message. Priority As Defined — Take the default priority of the queue that the reply will be sent to. You can also select a numeric value (zero to 9) that will represent the priority that will be set on the message. |
| Message ID | This value specifies the WebSphere MQ messageID that will be set on any MQ message being sent out by the transport. The message ID of a WebSphere MQ message is typically a unique identifier of an MQ message. If left unspecified, it is generated by the WebSphere MQ API when putting a message on a queue. |
| Correlation ID | This value specifies the WebSphere MQ correlation ID that will be set on any WebSphere MQ message being sent out by the transport. |
| Persistence
|
Specifies the default persistence of
any WebSphere MQ message being sent out
by the transport. By default, the queue manager preserves all persistent messages, recovering them when necessary from the WebSphere MQ log files, when it is restarted. Non persistent messages are not preserved. Options are: Persistent As Defined — The message that is put on the remote queue by the transport will have the default persistence that is configured on the queue. Non Persistent — The message that is put on the remote queue by the transport will be non persistent. This means that if the queue manager stops and the message is still on the queue, it will not be available when the queue manager is restarted. The messages are not recoverable. Persistent — The message that is put on the remote queue by the transport will be persisted by the queue manager and written to logs and queue data files. This means that if the queue manager stops and the message is still on the queue, it will be available when the queue manager is restarted. |
The values specified on the MQMD Header
Fields tabs will be overridden by the extended
attribute configuration specified on a transport map
definition (the transport map uses a WebSphere MQ
transport). In other words, if the transport is processing
a message that originated from a transport map that had
certain extended attributes defined, then those transport
map values will override the transport extended attribute
values. For more information, see Transport maps.