You can enter line comand S on any of the DM Primary Display screens to access the Monitored Job Details panel.
This display shows, on a single screen, a summary of all the current monitor data for the requested job step. The data includes:
The following example shows an example of the Monitored Job Details panel.
PMA 85---- PMA - Monitored Job Details ---------------------------------------- COMMAND ===> Jobname Procstep Stepname PGM/JCL PGM/Appl Date Time SAMPJOB1 RUNAJOBD APCSAMP 15/01/11 06:06:28 IO CPU Elapsed 15 Minute History Actual 127129 1.29 00:02:07 IO/Min CPU/Min Level Average 114000 2.00 00:06:00 059059 00.000 -01 Runaway. 393000 7.00 00:15:00 065067 00.000 -02 Max Thresh. 0 0.00 00:00:00 (ANY) N/A -03 Min Thresh. 0 0.00 00:00:00 (ALL) N/A -04 N/A -05 Average and Runaway values based on: 5 RUNS N/A -06 N/A -07 Job Status: PMA MONITORING Step Number: 001 N/A -08 N/A -09 N/A -10 Monitor Scope N/A -11 Job Step: INCLUDED Program: INCLUDED N/A -12 N/A -13 PMA Scope N/A -14 Job Step: INCLUDED Program INCLUDED N/A -15
The following list describes each of the fields in the various sections of the Monitored Job Details panel.
Name of the job
Name of the step that invoked the procedure
Name of the step that invoked the program
Program name from the JCL
Program name of the application
Date that the step started
Time that the step started
The values in this section are expressed in the following formats:
Measured values for the step, so far
Average values for the step from the job file
N/A is displayed if there is no step history.
Point at which the step becomes eligible for a runaway alert
Values at which the step becomes eligible for a threshold alert.
Maximum threshold options can be one of the following:
Minimum threshold values the step must exceed to be eligible for a runaway alert.
Minimum threshold options can be one of the following:
n RUNS, where n is the number of times that the step SMF data has previously been processed by Performance Management Assistant.
The averages and variances are adjusted by the data from each new run that is processed. Because of this adjustment, the runaway values evolve to take account of the normal behavior of the step. Dynamic alert checking is not done for the first 3 runs of a step in order to allow sufficient history to accumulate.
History table, which displays the number of I/Os (nnnnnn) and the milliseconds of CPU (ss.mmm) that are consumed during each of the previous 15 minutes of a step.
The table is arranged top down, with the newest entry first. The Level indicator shows the age of each entry in minutes (-nn).
Status of the job/step within the Server.
It can be one of the following:
Specifies whether the job step and program are included or excluded.
Both the job step and program must be included before the Server can trigger an alert.
Specifies whether the job step and program are included or excluded.
Both the job step and program must be included for Server monitoring to take place.
Note: Even if the Monitor Scope is set to include both the job step and program, if either the job step or program is excluded from the Scope, monitor alerts will not be activated.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |