MQseries

Distribution Lists

MQPUT can now be used to send copies of a single message to multiple destinations with assured delivery to each destination.

Distribution lists allow you to put a message to multiple destinations in a single MQPUT or MQPPUT1.

Multiple queues can be opened using a single MQOPEN

When an MQOPEN call is issued, generic information is taken from the Object Descriptor (MQOD)

If you specify MQOD_VERSION_2 in the Version field and when a message is put on the queues (MQPUT), generic information is taken from the Put Message Options structure (MQPMO) and the Message Descriptor (MQMD)

The specific information is given in the form of Put Message Records (MQPMR).

The Response Records (MQRR) can receive a completion code and reason code specific to each destination queue.

Handling Large Messages

MQSeries Version 5, the maximum message length is 100 MB, up from 4 MB

Channel auto-definition. This means that you don’t have to define a receiver channel

In a runmqsc session, type: alter qmgr chad(enable). This enables the channel auto-definition feature.

MQSeries Client for Java

This functions lets you write Java applets that can connect to a queue manager that runs in the same machine as the Web server.

· MQSeries Bindings for Java

This set of Java classes lets you write server applications using Java and MQSeries.

Authentication and encryption are supported for both MQSeries serverto-server and MQSeries client-to-server links.

The queue manager is both an XA resource manager and an XA resource coordinator

When the queue manager is acting as the XA coordinator it becomes possible to write a mixed MQI and SQL application and use the MQCMIT verb to commit or the MQBACK verb to roll back the changes to the queues and databases together.

You can use the transaction monitor only with a server application.

Continue ..............