Messages pass from one state to another as a result of an event.
These events are typically generated by an API call. The possible
message events, as shown in Figure 4, are:
- putMessage
- Places a message on a queue. This does not require a
confirmID.
- getMessage
- Retrieves a message from a queue. This does not require a
confirmID.
- putMessage with confirmId>0
- Places a message on a queue. This requires a
confirmID. However, messages do not arrive at the receiving
end in the order of sending, but in the order of confirmation.
- confirmPutMessage
- A confirm for an earlier putMessage with a
confirmID>0.
- getMessage with confirmId>0
- Retrieves message from a queue. This requires a
confirmID.
- confirmGetMessage
- A confirm for an earlier getMessage with a
confirmID>0.
- browseWithLock
- Browses messages and lock those that match. Prevents messages from
changing while browse is in operation.
- unlockMessage
- Unlocks a message locked with a browsewithLock
command.
- undo
- Unlocks a message locked with a browse, undoes a getMessage
with a confirmID>0, or undoes a putMessage with a
confirmID>0.
- deleteMessage
- Removes a message from a queue.
© IBM Corporation 2002. All Rights Reserved