Type of application that put the message.
This is part of the origin context of the message. For more information about message context, see Overview; also see the WebSphere MQ Application Programming Guide.
MDPAT may have one of the following standard types. User-defined types can also be used but should be restricted to values in the range ATUFST through ATULST.
This is the default application type for the platform on which the application is running.
This value can be used to indicate that the application type is unknown, even though other context information is present.
The following special value can also occur:
This value is set by the queue manager when a message is put with no context (that is, the PMNOC context option is specified).
When a message is retrieved, MDPAT can be tested for this value to decide whether the message has context (it is recommended that MDPAT is never set to ATNCON, by an application using PMSETA, if any of the other context fields are nonblank).
When the queue manager generates this information as a result of an application put, the field is set to a value that is determined by the environment. Note that on i5/OS, it is set to AT400; the queue manager never uses ATCICS on i5/OS.
For the MQPUT and MQPUT1 calls, this is an input/output field if PMSETA is specified in the PMO parameter. If PMSETA is not specified, this field is ignored on input and is an output-only field.
After the successful completion of an MQPUT or MQPUT1 call, this field contains the MDPAT that was transmitted with the message. If the message has no context, the field is set to ATNCON.
This is an output field for the MQGET call. The initial value of this field is ATNCON.
Notices |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
js51118 |