Using the Graphical Job Scheduling Monitor
Use
To display job scheduling information choose Tools
®
CCMS
®
Control/Monitoring
®
Job Scheduling Monitor. To have this display automatically updated every three minutes, select the Timer on button.
To
schedule and manage background jobs, return to the CCMS Jobs menu.
Changing the Monitor's Look
Reconfigure the
job scheduling monitor, including the chart's scale, gridlines, color, etc., from the Settings menu.Modify the time units used in the chart from the Time unit menu.
Reading the Monitor
In the far left of the monitor window, each available background work processes is shown and identified by the name of the appropriate host system. The
color of a job indicates its status. The length of a job symbol shows the amount of time actually required to process the job. Also shown is which background process handled the job.From left to right, the monitor shows:
- Left of the "current time" line are jobs that have either already been processed or are currently being processed
Based on which background processes are running which jobs, you can get a rough idea of the background work processes utilization factor. With automatic load distribution, background processing instances start a number of jobs awaiting processing corresponding to the number of free background processes. If the jobs waiting to be processed are always distributed over all instances and work processes and no work processes are left unused, then the background processing system is being fully utilized.
- Right of the "current time" are jobs that are waiting to be processed.
When jobs have already run at least once, the length of the job symbol indicates the estimated runtime for the job. The background processing system manages a statistics database, based on job names, which is used to generate these estimates. Smaller jobs and jobs for which no runtime statistics exist are shown by the monitor as a symbol with the minimum length.
In cases where jobs are repeated periodically, runtime estimates can, over time, reach a fairly high degree of precision. Actual runtimes that deviate considerably from expected runtimes may indicate
problems or program errors such as an infinite loop in a program.
You can move the start time window forward and backwards as required.