Overview of the REQUEUE command

You can requeue IMS messages by using input from the OLDS, the SLDS, data sets that have been unloaded from the message queue, data sets that have been extracted from the OLDS or the SLDS, or scrap files.

The examples in this section describe the following types of requeueing:

• Cold start after a normal IMS shutdown ( DUMPQ or PURGE).

• Cold start after an abnormal IMS shutdown and emergency restart (/ERE) failure.

The REQUEUE command lets you perform the following tasks:

• Automatically select the checkpoint used for requeueing if Message Advisor Checkpoint Tracking is active.

• Override the selected checkpoint by specifying a specific SNAPQ, PURGE, or DUMPQ checkpoint.

• Dynamically allocate log data set names obtained from RECON data sets.

  Note

  If any SLDS data set in the RECON has the error indicator on and the RECON contains a secondary SLDS, Message Advisor will attempt to use the secondary SLDS if its time stamps are valid.

• Override the log data set names by specifying an input data set name or the UNIT and VOLSER of an uncataloged system log data set (SLDS).

• Select or reject messages based on the following criteria:

  • Date and time ranges

  • Destinations (with masking allowed)

  • LU names (with masking allowed)

  • Origin (with masking allowed)

  • Destination type

  • Type of message (queue number)

• (optional) Re-establish conversations.

• (optional) Request requeueing of remote system messages.

This section contains the following topics:

• Requeuing user exit for the REQUEUE command
• Requeuing processing modes
• Automatic requeues for Message Advisor for IMS
• Processing rate