Defining Inclusions and Exclusions

Administration of the Central Component › Overview › Reducing the Scope of Work › Defining Inclusions and Exclusions

Defining Inclusions and Exclusions

Not all job steps in your batch production environment are interesting enough to be observed by PMA. Furthermore, some job steps should not be measured at all. For this reason, Performance Management Assistant uses a hierarchical concept to define the workload for Performance Management Assistant and for CA Mainframe Application Tuner. This hierarchy has 4 levels (each level reduces the workload and is the basis for the next level). See the following table.

Level	Description
1	Scope job name definitions: Generic job name definitions use both * and _ as wildcards. All job name definitions must be either inclusions or exclusions. Inclusions are recommended when defining job names. For example: PR* INCLUDED means that all job names other than those that begin with PR are implicitly excluded.
2	Scope program name definitions: Generic program name definitions use both * and _ as wildcards. All program name definitions must be either inclusions or exclusions. Exclusions are recommended when defining program names. For example: IEF* EXCLUDE IEB* EXCLUDE SORT EXCLUDE IDC* EXCLUDE This definition means that job steps within jobs defined in level 1 is not observed if those steps call a program defined in level 2.
3	CA MAT Scope: Job name definitions Generic definitions use both * and _ as wildcards. All definitions are exclusions only. For example: __KV* means that when KV is in the third and fourth positions of a job name, that job name is excluded from measurements.
4	CA MAT Scope: Program name definitions Generic definitions use both * and _ as wildcards. All definitions are exclusions only. For example: ___X01__ might mean that programs with a value of X01 in the fourth, fifth, and sixth positions of the program name indicate used one time only programs that should not be measured.

The levels of the hierarchy are treated as logical AND operations. The Scope defines the job steps for which statistical information should be gathered and calculated. These statistics are available under the JOBS option of the online dialog. For information about using the Job Query Facility, refer to the User Guide that corresponds with your measurement tool.

The CA MAT Scope decides which jobs and programs should be excluded from measurement. However, job statistics are still available.

In general, exclusions should be defined only when you are very sure that future measurements are not desired; for example, the job or program is to be replaced soon. As a rule, do not insert an exclusion after closing optimization efforts for a job or program because this action would prevent automatic measurement of program changes.

In summary, your scope of work definitions combined with your TOP Scope definitions work together to reduce measurements and alerts to only those that are really important.