BUFFER (1-byte bit string×BUFLEN) - output

Area to contain the message data.

The buffer should be aligned on a boundary appropriate to the nature of the data in the message. 4-byte alignment should be suitable for most messages (including messages containing MQ header structures), but some messages may require more stringent alignment. For example, a message containing a 64-bit binary integer might require 8-byte alignment.

If BUFLEN is less than the message length, as much of the message as possible is moved into BUFFER; this happens whether or not GMATM is specified on the GMO parameter (see the GMOPT field described in MQGMO - Get-message options for more information).

The character set and encoding of the data in BUFFER are given (respectively) by the MDCSI and MDENC fields returned in the MSGDSC parameter. If these are different from the values required by the receiver, the receiver must convert the application message data to the character set and encoding required. The GMCONV option can be used with a user-written exit to perform the conversion of the message data (see MQGMO - Get-message options for details of this option).

Note:

All of the other parameters on the MQGET call are in the character set and encoding of the local queue manager (given by the CodedCharSetId queue manager attribute and ENNAT, respectively).

If the call fails, the contents of the buffer may still have changed.