Air Cleaner User Manual

4. The priority, context, and persistence of each message are not changed.
5. The command performs no data conversion and calls no exits.
6. Confirm-on-delivery (COD) report messages are not generated but
confirm-on-arrival (COA) report messages are. This means that more than one
COA report message can be generated for a message.
7. The MOVE QLOCAL command transfers the messages in batches. At
COMMIT time, if the trigger conditions are met, trigger messages are
produced. This may or may not be at the end of the move operation.
Note: Before the transfer of messages begins this command verifies that the
number of messages on the source queue, when added to the number
of messages on the target queue, will not cause MAXDEPTH on the
target queue to be exceeded.
If the MAXDEPTH of the target queue were to be exceeded, no
messages are moved.
8. The MOVE QLOCAL command can change the sequence in which messages
can be retrieved. The sequence remains unchanged only if:
v You specify TYPE(MOVE) and
v The MSGDLVSQ parameter of the source and target queues is the same.
9. Messages are moved within one or more syncpoints. The number of messages
in each syncpoint is determined by the queue manager.
10. If anything prevents the moving of one or more messages, the command stops
processing. This can mean that some messages have already been moved,
while others remain on the source queue. Some of the reasons that prevent a
message being moved are:
v The target queue is full.
v The message is too long for the target queue.
v The message is persistent, but the target queue cannot store persistent
messages (for example, because the queue is shared).
v The page set is full.
MOVE QLOCAL
Chapter 2. The MQSeries commands 227
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|