MQSeries in CALLS
API CALLS- MQCONN / MQCONNX / MQDISC
MQCONN connects the application to a named queue manager. If successful, a handle is returned that is passed to all subsequent MQ calls. MQCONNX is a variation of MQCONN, but it establishes a “trusted” connection to the queue manager. This means that the application bypasses an IPC layer that all MQI calls normally go through, and operations are processed more rapidly. The disadvantage of MQCONNX is that an errant MQ application can adversely affect the queue manager.
MQDISC disconnects an application from a queue manager.
Related:TIBCO Online Training -1
API CALLS- MQOPEN / MQCLOSE
Open or close an MQSeries object. Usually associated with opening and closing queues.
API CALLS- MQPUT / MQGET
Get or put messages to a previously opened queue.
API CALLS- MQBEGIN/ MQCMIT / MQBACK
These are the MQSeries unit-of-work (syncpoint) co-ordination verbs. They can be used if the application requires MQSeries to control units of work. If an external transaction manager is being used then the application would use the calls appropriate for that environment.
MQBEGIN marks the start of a unit of work. This is useful shorthand that means that every subsequent MQ operation will be processed under the same unit of work. The alternative to this is to include an option within each MQ operation that explicitly states that the operation is to included under syncpoint.
MQCMIT commits a unit of work, so all MQPUT and MQGET operations are physically, rather than logically executed.
MQBACK “rolls out” a unit of work, effectively undoing the last group of operations under syncpoint.
API CALLS- MQINQ / MQSET
MQINQ provides the application with a way to retrieve the attributes of an MQ object. They may be inspected, altered, and then applied to the object using the MQSET verb.