|
|
|
|
|
As part of the post-processing for each job, Control-M for z/OS determines the elapsed run time of the job. All accumulated information regarding job execution, including the elapsed run time, is written to the IOA Log file. If a STAT CAL calendar is specified in the job scheduling definition, unlike other calendars (DCAL, WCAL, or CONFCAL), it must exist in the IOA Calendar library at the time that the job is ordered or forced.
Periodically, a statistics utility may be used to scan and analyze the IOA Log file. This utility gathers information about the start time of each job, its elapsed run time, CPU utilization time, and so on. The utility places this information in the Statistics file, where averages of these values can be maintained for each job.
For more information on the Statistics file, see Statistics Screen.
When a job is ordered, Control-M takes the average run time of this job from Statistics file and places it in the job record in the Active Jobs file. Control-M then uses this average run time to calculate the anticipated ELAPSE time, that is, the job execution time, of the job, and hence the Due In time of the job.
If the STAT CAL parameter is not used to specify a periodic calendar, the statistics relating to a job are based on all run times of the job.
If the STAT CAL parameter is present, statistics for the job are based on an average of all runtimes for the indicated period on the date on which the job is ordered or forced.
Further information is available in the Active Jobs file Zoom screen (Screen 3.z), which contains the STAT CAL PERIOD field. This is a read-only field that may contain one alphabetical character when the job has run. This character identifies the actual days within the Control-M periodic calendar that were used in calculating statistics relating to the job.
By using the STAT CAL parameter together with the information displayed in the STAT CAL PERIOD field, you can obtain more precise statistical information about the running of the job, as shown in the following example.
Example for STAT CAL
Assume that a job runs daily, weekly, and monthly, and that the STAT CAL parameter identifies a periodic calendar that contains a number of months each specified in a manner similar to the following:
-----S--------------S-------------S-------------S-------------S-------------S---
1 2 3 4 5 6 7 8 9 + 1 2 3 4 5 6 7 8 9 + 1 2 3 4 5 6 7 8 9 +
09 D D W D D D D D W D D D D D W D D D D D W D D D D M
In this example, the job runs daily in Period D, weekly in Period W, and monthly in Period M.
If the job runs on the 3rd of the month, its statistics are collected for Period W. If it runs on the 6th of the month, its statistics are collected for Period D, and so on.
When displaying the Statistics Panel (Screen 3.S), the statistics for daily, weekly, and monthly runs of the job are grouped under the D, W, and M PER(iod), as appropriate.
Parent Topic |