Restrictions

The following restrictions apply when you are dequeueing or unloading and dequeueing messages:

  • Message Advisor does not dequeue messages in temporary queues.

  • You must stop the following destination types before running a DEQUEUE or an UNLOAD_DEQUEUE request:

    • VTAM subpool
    • MSNAME
    • Any device requiring session synchronization
    • A non-VTAM device
    • Any device requiring session backup
    • ISC links
    • MSC links
    • 2741 point-to-point
    • 2740 point-to-point
    • System 7
    • Local SYSIN and SYSOUT
    • System 3
    • 3600 devices
    • 3614 devices
    • 3790 devices
    • LU 6 devices
    • LU 4 devices
    • NTO devices
    • TPNAME
    • OTMA
    Warning

    If a DEQUEUE is performed on a SLUP device with FORCE=YES specified, then synchronization between the SLUP device and IMS may be lost. Manual intervention may be required to restart and resynchronize the SLUP device.

  • Message Advisor does not dequeue destinations that are in conversation.

    Note

    Conversation output that is pending transmission on an MSNAME is dequeued. Dequeueing the conversation requires the originating terminal, which is waiting for the output, to be forcibly exited from the conversation.

  • If you specify a DEQUEUE request with the DESTINATION= * keyword, it ignores master terminals. If you specify the keyword as DESTINATION=MASTER, the master terminal messages are dequeued.

    Note

    Dequeueing on a master, secondary master, WTOR, or on DFS-prefixed CNTs requires FORCE=YES.

Related topic

Dequeueing-messages

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*