Profile definition examples
This topic provides usage examples to assist you in defining profiles and setting up alarms.
Each Loop Check Profile displays the following dialog. You can use this dialog to define the loop criteria that creates an alarm for detecting looping IMS regions:
WTO and/or ABDUMP looping regions
Profile Identity
Profile Name:
Profile Desc:
Loop Criteria
Elapsed Transaction CPU Trigger..: (hh:mm:ss)
Current CPU Usage Percent Trigger: 95 (0-100) percent
I/O Rate per sec....: (0-9999) operand (= or >=)
DL/I Rate per sec...: (0-9999) operand (= or >=)
SQL Rate per sec....: (0-9999) operand (= or >=)
IMS Jobname: (Specific or generic)
IMS Application Region Job Names
Include:
Exclude:
Region Types (see help for types)
Include:
Exclude:
Transaction Names
Include:
Exclude:
LTERM Names
Include:
Exclude:
Program Names
Include:
Exclude:
Action(s)
WTO....: (Y -Yes)
STOP RGN ABDUMP: (Y -Yes, See help for ABDUMP warning)
-Do not use ABDUMP unless IMSID or CRC is unique!
Command prefix type: (I -IMSID(default) or C -CRC)
END to exit and save changes
CANcel to exit without saving changes
HELP to view related help
The following table describes scenarios and the loop criteria you can use to detect the loop:
Scenario | Loop criteria |
|---|---|
To detect any region that matches the selection criteria after 400 minutes | Set the following values in the definition criteria:
|
To detect any region that matches the selection criteria after it has used | Set the following values in the definition criteria:
|
Related topic