MQ Extended Put

This WebSphere MQ tool  executes the MQPUT call to put a message on a queue or distribution list. The queue or distribution list must already be open. See the MQPUT call documentation in your WebSphere MQ Application Programming Guide for more information.

The function of MQ Extended Put is identical to MQ Put, except that MQ Extended Put sends all MQPUT call input parameters while MQ Put sends only the most commonly used input parameters.

Inputs

Hconn

The connection handle to the Queue Manager. The MQConnect tool generates this connection handle. This value corresponds to the Hconn input parameter in the MQPUT call.

Hobj

The object handle identifying the queue from which a message is retrieved. The Hobj is generated by the MQ Open tool. This value corresponds to the Hobj parameter in the MQPUT call.

Note: The values of the following input parameters are defined in the MQPUT and MQMD sections of the WebSphere MQ Application Programming Guide.

Buffer Handle

If your message to put is a binary buffer constructed via the Buffer Tools, pass in the buffer handle here. Any non-zero number in the Buffer Handle implies a binary buffer.  Set the Buffer Handle to 0 for a text buffer.

Message

If your message to put is all textual, pass in a string containing the buffer contents here.   Note: The Buffer Tools also support constructing a textual buffer, but it is generally easier to use a string for this. See the cross-reference Note above.

Options (MQPMO)

See note above.

Content (MQPMO)

See note above.

Report

See note above.

MsgType

See note above.

Expiry

See note above.

Feedback

See note above.

Format

See note above.

Encoding

See note above.

CodedCharSetId

See note above.

Priority

See note above.

Persistence

See note above.

MsgId

See note above.

CorelId

See note above.

ReplyToQ

See note above.

ReplyToQMgr

See note above.

UserIdentifier

See note above.

AccountingToken

See note above.

ApplIdentityData

See note above.

PutApplType

See note above.

PutApplName

See note above.

PutDate

See note above.

PutTime

See note above.

ApplOriginData

See note above.

Outputs

MsgId

See note above.

CorelId

See note above.

ResolvedQName (MQPMO)

See note above.

ResolvedQMgrName (MQPMO)

See note above.

Reason Code

For each call, a completion code and a reason code are returned by the queue manager or by an exit routine, to indicate the success or failure of the call. This value corresponds to the Reason code parameter in the MQPUT call. The WebSphere MQ Application Programming Guide contains a list of reason codes and their meanings.

Exit Paths

Success

This step takes the Success exit path if the completion code indicates success.

Failure

This step takes the Failure exit path if the completion code indicates failure. The reason for tool failure is contained in the Reason Code parameter.