PutApplType (MQLONG)
This is the type of application that put the message, and is part of the origin context of the message. For more information about message context, see Overview for MQMD and Message context.
PutApplType can have one of the following standard types. We can also define your own types, but only with values in the range MQAT_USER_FIRST through MQAT_USER_LAST.
- MQAT_AIX
- AIX application (same value as MQAT_UNIX).
- MQAT_AMQP
- AMQP protocol application
- MQAT_BROKER
- Broker.
- MQAT_CICS
- CICS transaction.
- MQAT_CICS_BRIDGE
- CICS bridge.
- MQAT_CICS_VSE
- CICS/VSE transaction.
- MQAT_DOS
- IBM MQ MQI client application on PC DOS.
- MQAT_DQM
- Distributed queue manager agent.
- MQAT_GUARDIAN
- Tandem Guardian application (same value as MQAT_NSK).
- MQAT_IMS
- IMS application.
- MQAT_IMS_BRIDGE
- IMS bridge.
- MQAT_JAVA
- Java.
- MQAT_MVS
- MVS or TSO application (same value as MQAT_ZOS).
- MQAT_NOTES_AGENT
- Lotus Notes Agent application.
- MQAT_NSK
- HP Integrity NonStop Server application.
- MQAT_OS390
- OS/390 application (same value as MQAT_ZOS).
- MQAT_OS400
- IBM i application.
- MQAT_QMGR
- Queue manager.
- MQAT_UNIX
- UNIX application.
- MQAT_VOS
- Stratus VOS application.
- MQAT_WINDOWS
- 16-bit Windows application.
- MQAT_WINDOWS_NT
- 32-bit Windows application.
- MQAT_WLM
- z/OS workload manager application.
- MQAT_XCF
- XCF.
- MQAT_ZOS
- z/OS application.
- MQAT_DEFAULT
- Default application type.
This is the default application type for the platform on which the application is running.
Note: The value of this constant is environment-specific. Because of this, always compile the application using the header, include, or COPY files that are appropriate to the platform on which the application will run. - MQAT_UNKNOWN
- Use this value to indicate that the application type is unknown, even though other context information is present.
- MQAT_USER_FIRST
- Lowest value for user-defined application type.
- MQAT_USER_LAST
- Highest value for user-defined application type.
The following special value can also occur:
- MQAT_NO_CONTEXT
- This value is set by the queue manager when a message is put with no context (that is, the MQPMO_NO_CONTEXT context option is specified).
When a message is retrieved, PutApplType can be tested for this value to decide whether the message has context (it is recommended that PutApplType is never set to MQAT_NO_CONTEXT, by an application using MQPMO_SET_ALL_CONTEXT, 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. On IBM i, it is set to MQAT_OS400; the queue manager never uses MQAT_CICS on IBM i.
For the MQPUT and MQPUT1 calls, this is an input/output field if MQPMO_SET_ALL_CONTEXT is specified in the PutMsgOpts parameter. If MQPMO_SET_ALL_CONTEXT is not specified, this field is ignored on input and is an output-only field.
This is an output field for the MQGET call. The initial value of this field is MQAT_NO_CONTEXT.
Parent topic: Fields for MQMD