MONITOR CONFIRM statement

The MONITOR CONFIRM Statement Syntax is as follows: 

MONITOR CONFIRM statement

This statement initiates an FDRPAS MONITOR task that monitors for FDRPAS operations that specify CONFIRMSWAP=YES or CONFIRMSPLIT=YES. It must be the first statement in the input; only one MONITOR statement is allowed per execution.

A MONITOR TYPE=CONFIRMSWAP or TYPE=CONFIRMSPLIT statement must be followed by one or more MOUNT statements to identify the volumes whose progress is to be monitored. This FDRPAS job may be executed on any system that is involved in the swap of all of the volumes specified.

As soon as all the volumes specified are synchronized, the MONITOR task signals the SWAP task to complete the SWAP or SWAPDUMP of those volumes, all at once. If you submit this job before all of the volumes are ready to complete, it waits for all the volumes to enter that state. If you submit the job after all the volumes are ready to complete, it confirms the operation immediately. (Note that, depending on update activity, a given volume may enter the “ready to complete” state and then exit that state for a few seconds; the MONITOR task waits until all the volumes you specified are ready, which may take a few seconds to a few minutes.)

MONITOR CONFIRM statement operands

TYPE=

Must be specified on the MONITOR statement.

CONFIRMSPLIT

Initiates a MONITOR task that monitors the operation of a SWAPDUMP task for one or more volumes, and that automatically confirms and completes the FDRPAS operation on those volumes when all the volumes are synchronized and ready to complete.

CONFIRMSWAP

Initiates a MONITOR task that monitors the operation of a SWAP task for one or more volumes, and that automatically confirms and completes the FDRPAS operation on those volumes when all the volume are synchronized and ready to complete.

CONFMESS=

CM=

NO

FDRPAS confirms the volumes automatically as soon as they are all synchronized, without operator intervention.

YES

When all volumes specified in this CONFIRM step are synchronized, FDRPAS issues WTOR message FDRW07 to the system operator. If you reply “YES” to the message, then FDRPAS confirms the volumes. If you reply “NO”, this CONFIRM step terminates but the swaps are still active. This may be useful when a system automation product is used; it can wait for the FDRW07 message to know that the volumes are synchronized, perform other operations (such as quiescing some applications), and then reply to confirm the volumes.

Default: NO.

DURATION=

nnnn

Specifies the number of minutes that the CONFIRMSWAP task keeps checking to see whether the SWAP or SWAPDUMP operation has been initiated for every volume identified on the MOUNT statements. If all volumes have not been initiated within this period, the CONFIRMSWAP fails. If the CONFIRMSWAP task is submitted at the same time as the SWAP or SWAPDUMP jobs, then, depending on the number of volumes and systems involved, it may take anywhere from a few seconds to a minute or two for all of the SWAP or SWAPDUMP tasks to start. The default of 2 should be sufficient for all but extreme cases. If the CONFIRMSWAP fails, the reason is probably that one or more of the volumes specified in the CONFIRMSWAP step have been omitted from the SWAP or SWAPDUMP jobs; be sure to check for this before increasing the DURATION value.

Default: 2.

MAXCARDS=

nnnn

Specifies the maximum number of MOUNT statements that can be present in this FDRPAS step, from 1 to 9999.

Default: 250.