Detecting exception conditions
The threshold keywords are categorized into the general groups that are listed in below table.
Threshold Type | Threshold keywords |
---|---|
Free space | DOVF_FREESPACE_PERCENT |
FREESPACE_DOVF_IOVF | |
FREESPACE_RAA_DOVF | |
FREESPACE_RAA_IOVF | |
IOVF_FREESPACE_PERCENT | |
IOVF_USED_PERCENT | |
RAA_FREESPACE_PERCENT | |
RAP_OVERFLOW_PERCENT | |
I/O | RECORD_IO_AVERAGE |
RECORD_IO_MAXIMUM | |
ROOT_IO_AVERAGE | |
ROOT_IO_MAXIMUM | |
RAP usage | SYNONYM_CHAIN_LENGTH |
SYNONYM_CHAIN_MAXIMUM | |
SYNONYM_CHAIN_PERCENT | |
Overflow characteristic | RECORD_IOVF_PERCENT |
UOW_DOVF_PERCENT | |
UOW_IOVF_AVERAGE | |
UOW_IOVF_MAXIMUM | |
UOW_IOVF_PERCENT |
You can specify thresholds by placing the THRESHOLD subcommand within the GLOBAL command. These implicit threshold specifications are used by all analysis functions within the job step. To override the GLOBAL command, you can explicitly specify a THRESHOLD subcommand within the ANALYZE command. In the example shown in below figure, thresholds that are specified on the GLOBAL command are tested for all areas except area2 of database2. Specifying THRESHOLD without any keywords under the last ANALYZE command overrides the GLOBAL command, so no threshold checking is performed for area2.
//STEPLIB DD DISP=SHR,DSN=BMC.PFP.LOAD
// DD DISP=SHR,DSN=IMS.RESLIB
// DD DISP=SHR,DSN=IMS.RESLIB
//IMSACB DD DISP=SHR,DSN=IMSVS.ACBLIB---> IMSACB DD is not required in a managed ACB environment.
GLOBAL
REPORT
RECORD_PROFILE_ANALYSIS=NO
THRESHOLD
FREESPACE_RAA_DOVF=(25,25),
FREESPACE_RAA_IOVF=(50,50)
ANALYZE DBD=
database1
ANALYZE DBD=
database2,IAREA=(
area1,
area3,
area4)
ANALYZE DBD=
database2,IAREA=
area2
THRESHOLD
/*