WebSphere MQ messages

 

WebSphere MQ messages are made up of two parts:

Figure 1 represents a message and shows how it is logically divided into message data and application data.

Figure 1. Representation of a message

The application data carried in a WebSphere MQ message is not changed by a queue manager unless data conversion is carried out on it. Also, WebSphere MQ does not put any restrictions on the content of this data. The length of the data in each message cannot exceed the value of the MaxMsgLength attribute of both the queue and queue manager.

On WebSphere MQ for AIX, WebSphere MQ for iSeries, WebSphere MQ for HP-UX, WebSphere MQ for Linux, WebSphere MQ for Solaris, and WebSphere MQ for Windows, the MaxMsgLength defaults to 100 MB (104 857 600 bytes).

If you are intending to use WebSphere MQ messages greater than 15 MB on i5/OS, see Building your application on i5/OS.

On WebSphere MQ for z/OS, the MaxMsgLength attribute of the queue manager is fixed at 100 MB and the MaxMsgLength attribute of the queue defaults to 4 MB (4 194 304 bytes) which we can change up to a maximum of 100 MB if required.

Make your messages slightly shorter than the value of the MaxMsgLength attribute in some circumstances. See The data in your message for more information.

You create a message when you use the MQPUT or MQPUT1 MQI calls. As input to these calls, you supply the control information (such as the priority of the message and the name of a reply queue) and your data , and the call then puts the message on a queue. See the Application Programming Reference for more information on these calls.

This chapter introduces WebSphere MQ messages, under these headings:

 

Parent topic:

Designing applications that use WebSphere MQ


fg10560_