Field name

Description

TOP Scope of most important job steps:

Enter the number that you want PMA to use when identifying the top resource consuming job steps. This value affects the number of statistical alerts that are generated. The job steps belonging to the TOP Scope can be viewed easily by using Job Step Query Facility.

Within the scope of work that is defined through inclusions and exclusions of job names and programs, the scope can be further drastically reduced by using TOP Scope. The TOP Scope facility identifies the job steps consuming the greatest resources and limits the measurements to this group.

To define the use of the TOP Scope, there is only one parameter. This parameter is called TOP Scope of important steps and may contain a value from 0 - 99999. A value of 0 indicates that no statistical alerts should be generated by PMA. In all other cases, the TOP Scope defines how many important job steps should be statistically observed.

The TOP Scope results are generated at least twice a day under job step APCBAALM of job APCXJLIB and under job step APCXACAL of job APCXJSMF or optionally after changing the TOP Scope through the online dialog. To figure out the TOP Scope, PMA computes the importance of a job step by using the following algorithm:

importance = log2 (srvu) + log2 (# of executions per month) + log2 (elpsd)

Based on the results of this computation, the importance is computed for each job step of the job file and the top limited number of the most important steps are flagged. To review the results, simply select the TOP method of the Job Query Facility panel.

Note: The importance formula is equivalent to the product of average service units, the number of step executions, and average elapsed time.

The TOP Scope method uses the importance formula to select the top resource-consuming job steps up to the limit set in the TOP Scope = nnn parameter. Statistical alerts and measurements are limited to the members of this group of large consumers. USER alerts and MODC alerts can be subject to the TOP Scope by selecting the use TOP Scope option.

Delete job data if older than:

Enter the number of months that job step information should be kept. Job step information that is older than this number of months is deleted by maintenance job APCBJREO.

No. days PMA shall collect job step stats before doing alerts:

The parameter is used only during the product startup phase. It defines the number of days that statistics should be collected before PMA gives alerts. This limit means that the calculation should not give alerts before it has reached the time range from the first execution of job APCXJSMF to the day of first execution plus this number of days. A high value improves the statistical base for the job steps.

Measurement of modified programs:

Enter a value to determine whether PMA should request measurements for new modules or new and modified modules.

• Y  All modified and new programs should be measured.
• N  No alerts are created if a module has changed and load libraries are not scanned.
• B  Only brand new programs should be measured. This option drastically reduces the load library scan process.

use TOP Scope:

If a new or changed program is found, enter a value to indicate whether the TOP Scope processing logic should be used to determine whether a measurement should take place.

• Y   Measure only the changed or new programs that are executed in job steps belonging to the TOP Scope.
• N   Measure all changed or new programs regardless of the TOP Scope.

  Note: The combination of only brand new programs and use TOP Scope=N is invalid because no statistical average exists for the new programs or job steps.

MSG level for batch jobs:

When executing the batch jobs, messages can be generated at different levels on the statement APCREP:

0 - Only processing results are presented (that is, number of records processed, and so on.)

1 - Processing errors are presented.

2 - Processing errors and warnings are presented.

It is recommended that MSGlevel = 0 or 1 be used. Many messages might be generated when using MSGlevel = 2. The default value is 1.

Max number of measurements/day:

During installation, you can enter the maximum number of measurement requests that should be placed in the measurement queue. If PMA attempts to generate more than the maximum number of measurements you entered, an appropriate message is provided in the batch report output file APCREP (step APCBAALM of job APCXJLIB).

Type of runaway test (Perf. IX):

Enter the type of runaway test to be performed by job APCXJSMF. You can decide whether the runaway test should be done as in previous releases for the absolute values of elapsed time and service units, or whether you want to use performance indexes for runaway alerts.

Performance indexes are quotients measuring the absolute consumption values relative to either the IO consumption or to the elapse time.

Following values are possible:

• ASIS - Runaway testing is done with the same values (elapsed time, service units) as in the previous releases.
• IOIX - Runaway testing is done with the ratios elapsed time/IO consumption and service units/IO consumption.
• ALL - Runaway testing is done for all possible measurements; that is for absolute consumption values and for performance index (ratio) values. Setting this parameter to ALL has the same function as the previous two parameter settings (ASIS, IOIX) together.

Measurement duration

Enter values to determine the measurement duration to be assigned job steps based on the average elapsed time of the step to be measured. The settings define the three period-based measurement phases that can be applied to job steps, depending on their average elapsed time, as follows:

• Phase 1 < p1 min = t1 min - Short steps of less than p1 minutes. Average elapsed times are assigned a measurement duration value of t1 minutes.
• Phase 2 < p2 min = t2 min - Medium steps of greater than or equal to p1 minutes and less than p2 minutes. Average elapsed times are assigned a measurement duration value of t2 minutes.
• Phase 3 >= p2 min = t3 min - Long steps of greater than or equal to p2 minutes. Average elapsed times are assigned a measurement duration value of t3 minutes.

For steps with no valid average elapsed time, use de min 01-99. Steps that do not have a valid historical elapsed time will use this value. It can also be used as the time setting for one or more measurement phases or set as the value to be used for all Dynamic Alerts.

p1 and p2 must be in the range 01-99 and the p1 values must be less than the p2 value.

t1, t2 and t3 can be set to 01-99 minutes, to AV to use the step average elapsed, or set to DE to use the default value as set for jobs with no valid average time.

Additional Parameters for CA MAT ADD requests:

If the Server is not used, CA MAT parameters SAMPLES and NOLIMIT are required and are provided automatically by PMA. You can change the value of the SAMPLES parameter.

If used in a parallel sysplex environment, PMA should be run as in a single system environment because CA MAT version 2 takes care of spreading the measurement requests. In this case, enter the TARGSYS1(*) as an additional parameter.

No validity checks are performed on additional ADD parameters. If an invalid parameter exists, the generation of CA MAT invoke request is prevented.