Put

This operation places specified messages on a specified queue. The queue can belong to a local or remote queue manager. Puts to remote queues can occur immediately, or at a later time, depending on how the remote queue is defined on the local queue manager.

If a remote queue is defined as synchronous, message transmission occurs immediately. If a remote queue is defined as asynchronous, the message is stored within the local queue manager. The message remains there until it is transmitted. The put message call may finish before the message is put. Refer to Message delivery for more information.

Note: In Java™, if the local queue manager does not hold a definition of the remote queue then it attempts to contact the queue synchronously. This does not apply to the C code base.

Assured delivery depends on the value of the confirmID parameter. Passing a non-zero value transmits the message as normal, but the message is locked on the target queue until a subsequent confirm is received. Passing a value of zero transmits the message without the need for a subsequent confirm. However, message delivery is not assured. Refer to Message delivery, for more information on assured and non-assured message delivery.

You can protect a message using message-level security.


Terms of use | WebSphere software

(c) Copyright IBM Corporation 2004, 2005. All rights reserved.