MONITOR SWAP MOUNT statement


The MONITOR SWAP MOUNT Statement Syntax is as follows: 

MOUNT

SWAPUNIT={(uuu1[,uuu2[,…]])|(uuuu1[,uuuu2[…]])}

MONITOR SWAP MOUNT Statement

One or more MOUNT SWAPUNIT= statements follow the MONITOR TYPE=SWAP statement. Each specifies an offline target device or set of devices to be monitored to see if one or more of them is selected as the target of a swap by an FDRPAS SWAP task on another system image.

The MONITOR task automatically terminates if it detects that all the devices you have specified on the MOUNT statement have been swapped or are no longer offline unless DYNMON=YES is specified on the MONITOR TYPE=SWAP statement. With dynamic monitoring, the devices to be monitored are obtained from the SWAP, SWAPDUMP, or SIMSWAPMON task.

Important

For Large Scale Swaps, it is expected that the monitor jobstreams will be embedded in the PASJOB DD statement of the SIMSWAPMON and SWAPDUMP jobs, so that the SIMSWAPMON and SWAPDUMP jobs will submit the jobstreams as just-in-time monitors. Within PASJOB, the user is expected to code:

 MOUNT SWAPUNIT=&&&&

The SIMSWAPMON or SWAPDUMP job will generate the list of SWAPUNITs.

MONITOR SWAP MOUNT statement operands

SWAPUNIT=

SU=

uuuu or uuuuu

Specifies the z/OS device addresses of the target devices to be monitored. The address can be specified as a 4-digit or 5-digit (hex) z/OS device address, or it can be specified as 1, 2, or 3 digits with a trailing asterisk (*); in this case all offline z/OS DASD addresses starting with the prefix specified are monitored. To monitor multiple devices or ranges of devices (by prefix), specify them in parentheses, separated by commas, but you cannot specify more than 255 sub-parameters (device addresses or address prefix ranges) within the parentheses. If you need to specify more than 255 addresses or prefixes, then you can use more than one MOUNT SWAPUNIT= statement. The total number of devices to monitor can be up to 8190. Only devices that are offline and accessible at the time the MONITOR task starts are monitored; if a device is placed offline or becomes accessible after the MONITOR task starts, it is not monitored.

Important

If the range to be monitored includes devices that are in your I/O configuration but do not really exist (are not in the hardware configuration of the DASD subsystem), you may receive this console message:

IOS002A dev, NO PATHS AVAILABLE

for each such device the first time that the MONITOR task is executed after an IPL. The messages can be ignored. They may occur only under certain releases of OS/390.

For example,

MOUNT SWAPUNIT=17C0                  - monitors one offline device 17C0
MOUNT SWAPUNIT=17C*                  - monitors offline devices in the range 17C0-17CF
MOUNT SWAPUNIT=17*                   - monitors offline devices in the range 1700-17FF
MOUNT SWAPUNIT=(17*,18*,19A*)        - monitors offline devices in the ranges
1700-17FF, 1800-18FF, and 19A0-19AF


 

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