MONITOR SWAP examples

If the source volume is accessible to multiple systems, even if it is offline on some of those systems, an FDRPAS MONITOR task, as shown in the following examples, must be started on every one of those systems before an FDRPAS SWAP, SWAPDUMP, SIMSWAPMON, SWAPBUILDIX, or EXPANDVTOC task is started. If the source volume is in an EMC Symmetrix subsystem, the MONITOR tasks need to be started only on systems where the source volume is online. On other DASD subsystem types, the MONITOR tasks must execute on all systems with access to the source volume, even if it is offline.

The MONITOR tasks shown below are used with SWAP, SWAPDUMP, SIMSWAPMON, SWAPBUILDIX, and EXPANDVTOC operations. Although the text below refers to “SWAP tasks” the examples work with all these functions.

These MONITOR tasks can be started automatically by the main SWAP, SWAPDUMP, or SIMSWAPMON job if in GRS complexes or MIM complexes.

All examples in this section are found in the JCL library installed with FDRPAS. The member names are PA31023x.

Example - Dynamic monitoring

This FDRPAS MONITOR task dynamically monitors the volumes involved with a SWAP, SWAPDUMP, or SIMSWAPMON. This method only takes resources when a main swap process specifies a target device for a swap. Since a dynamic monitor only uses resources when swapping, it could be started at IPL time and remain available.

//MONITOR EXEC PGM=FDRPAS,REGION=0M//STEPLIB DD DISP=SHR,DSN=fdrpas.loadlib//SYSPRINT DD SYSOUT=*//FDRSUMM DD SYSOUT=*//SYSUDUMP DD SYSOUT=*//SYSIN DD * MONITOR TYPE=SWAP,DYNMON=YES/*

You should specify DYNMON=YES or monitor multiple units if you are going to execute SIMSWAPMON.

Example - Monitor a single target device

Monitor offline device 1AA3 as an FDRPAS target device. FDRPAS periodically checks this device to see if an FDRPAS SWAP task has started on another z/OS system image that is using the device as a target. If so, the MONITOR task assists the SWAP task by monitoring this system image for updates to the original volume during the copy process, and by switching all I/O activity to the new device when the swap is complete.

This type of MONITOR task automatically terminates once the SWAP or SIMSWAPMON job has completed processing the target device.

//MONITOR EXEC PASPROC//PAS.SYSIN DD * MONITOR TYPE=SWAP MOUNT SWAPUNIT=1AA3/*

Monitor a range of target devices - example #1

Monitor range 24E0-24EF of offline potential FDRPAS target devices (any devices in the range that are not offline or are not DASD are ignored). FDRPAS periodically checks each of those devices to see if an FDRPAS SWAP task has started on another system image that is using the device as a target. If so, it starts a separate MONITOR task to assist the SWAP task by monitoring this system image for updates to the original volume during the copy process, and by switching all I/O activity to the new device when the swap is complete. Once all swaps on this range of offline devices have been completed, you can terminate the MONITOR task with console command P MON2. However, if every offline device in the range is now online (completed swap) the MONITOR task terminates automatically.

If your systems are part of a sysplex (basic or parallel), you can use the console ROUTE command to start MONITOR tasks on all systems in the sysplex. This can considerably reduce the amount of typing required. For example:

starts the MONITOR task on all other systems in the sysplex (*OTHER assumes that you start the SWAP task on this system, use *ALL to start the MONITOR task on all systems).

If you have systems that are not part of the sysplex, you need to manually start the MONITOR task on each of them.

Monitor a range of target devices example #2

Monitor ranges (1A00-1AFF and 1B00-1BFF) of offline potential FDRPAS target devices (any devices in the range that are not offline or not DASD are ignored). FDRPAS periodically checks each of those devices to see if an FDRPAS SWAP task has started on another system image that is using the device as a target. If so, it starts a separate MONITOR task to assist the SWAP task by monitoring this system image for updates to the original volume during the copy process, and by switching all I/O activity to the new device when the swap is complete. As long as no more than 64 concurrent swaps are occurring on the monitored devices, all the separate MONITOR tasks are internal subtasks. The MONITOR task automatically terminates when it has been idle (not participating in any swaps) for a total of two hours (120 minutes).

This MONITOR task needs to be started on every system that has access to the volumes to be swapped before the SWAP task is started.

//MONITOR EXEC PGM=FDRPAS,REGION=0M//STEPLIB DD DISP=SHR,DSN=fdrpas.loadlib//SYSPRINT DD SYSOUT=*//SYSUDUMP DD SYSOUT=*//SYSIN DD * MONITOR TYPE=SWAP,DURATION=120 MOUNT SWAPUNIT=(1A*,1B*)/*