The purpose of the monitoring program is to provide task-specific variables, from which the resource requirements of individual tasks can be determined.
This data can be used for the following purposes:
to determine which tasks most frequently use specific resources
to optimize operation by relocating loads
as input data for simulation models or analytic calculations.
SM2 writes this data to the SM2 output file, from which subsequent analysis is possible. As with SM2 reports, data cannot be output during the monitoring process.
When defining the monitoring program, the tasks to be monitored must be specified. Both user tasks and system tasks can be monitored. SM2 can monitor both current tasks already executing or further tasks created in the course of monitoring operations.
The support of RSC IOs (x86 servers) of TD devices is not possible, because there is no connection between RSC IOs and tasks. Instead of this the number of physical accesses to coded files are output.
Monitoring information can be written to the SM2 output file at two points in time:
At task termination time, if the task is terminated during monitoring.
At monitoring termination time, if the task is still executing when the monitoring program is terminated.
If the devices to be monitored are defined in the DEVICES operand of the SET-TASK-PARAMETERS statement, the number and service time of I/O operations for these devices are output for each task according to whether they are hardware- or software-related. Due to the time and effort involved in gathering this monitored data, this monitoring program should only be used for brief periods of time (e.g. one hour) or for a small number of tasks.For each task, it is possible to monitor up to 64 devices.
If the monitoring program is used for parallel access volumes (PAV), the following applies:
Base and alias devices can be selected.
If a base device is selected, the data refer also to the assigned alias devices.