Defining loop check profiles to reset the IMS region after a stop is in progress
Use the following procedure to define a loop check profile to reset the IMS region when a stop is in progress.
This profile creates an alarm that detects an IMS looping region where a STOP REGION ABDUMP is in progress, but has not completed. This alarm provides the ability to quiesce a region that has been looping for about 90 seconds or more. If desired, you can specify that the alarm:
- Write a WTO to the system console when a job matches all the criteria
- Trigger a reset to the slowest WLM service class
To define a loop check profile to reset the IMS region after a stop is in progress
- From the MainView for IMS easy menu (EZIMS), select IMS Easy Admin Menu.
- From the IMS Easy Admin Menu (EZIALPRF), select Solution Profiles.
- From the list of profiles for looping dependent regions, select Issue MSG and/or RESET Service Class.
The ILPCKPLQ view is displayed as shown in the following figure: On the COMMAND line, type ADD and press Enter.
The Loop Check Criteria Profile displays as shown in the following figure:
-------------------- Loop Check Criteria Profile - Add -------------------
COMMAND ===> SCROLL ===> CSR
MORE:+
WTO and/or RESET
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)
RESET WLM service class: (Specify lowest WLM service class)
Show Alarm Parameters: (Y -for debugging purposes)
END to exit and save changes
CANcel to exit without saving changes
HELP to view related help- Specify the profile's name, description (optional), and criteria:
- At Profile Name, enter a unique alphanumeric name for the profile, up to 12 characters, starting with an alphabetic or national character.
- (optional) At Profile Desc, enter a short description of the profile.
At Loop Criteria, define the criteria that must be met to trigger the alarm:
Loop Criteria
Description
Elapsed Transaction CPU Trigger
Identifies the minimum amount of transaction CPU usage time that a region must accumulate to be considered as a looping candidate
The value you specify must be in hh:mm:ss format. The time you specify applies to the currently active transactions, not total transaction CPU usage time for the region.Current CPU Usage Percent Trigger
Identifies the minimum CPU percentage that a region must be consuming to be considered a looping candidate
Valid values are integer values from 0 through 100.I/O Rate per sec
Identifies the minimum DL/I I/O rate per second that a region must achieve to be considered a looping candidate
Valid values are integer values from 0 through 9999.DL/I Rate per sec
Identifies the minimum DL/I call rate per second that a region must be doing to be considered a looping candidate
Valid values are integer values from 0 through 9999.SQL Rate per sec
Identifies the minimum SQL call rate per second that a region must be doing to be considered a looping candidate
Valid values are integer values from 0 through 9999.
- At IMS Jobname, specify the IMS job name for this profile.
- Under IMS Application Region Job Names, specify jobs to which this profile should or should not apply:
- At Include, enter up to five IMS application region job names to which this profile applies.
At Exclude, enter up to five IMS application region job names to which this profile does not apply.
- Under Region Types, specify the region types to which this profile should or should not apply:
- At Include, enter up to four region types to which this profile applies.
At Exclude, enter up to four region types to which this profile does not apply.
- Under Transaction Names, specify up to five IMS transaction names that identify jobs to which this profile should or should not apply:
- At Include, enter up to five transaction names to which this profile applies.
At Exclude, enter up to five transaction names to which this profile does not apply.
- Under LTERM Names, specify up to four IMS LTERM names that identify jobs to which this profile should or should not apply:
- At Include, enter up to four IMS LTERM names to which this profile applies.
At Exclude, enter up to four IMS LTERM names to which this profile does not apply.
- Under Program Names, specify up to five IMS program names that identify jobs to which this profile should or should not apply:
- At Include, enter up to four IMS LTERM names to which this profile applies.
At Exclude, enter up to four IMS LTERM names to which this profile does not apply.
- At Action(s), perform any of the following specifications:
(optional) At WTO, specify Y if you want the alarm to write a WTO to the system console when a job matches all of the criteria in this profile.
The WTO can be used by operations to take action or can be used by an automation product such as MainView AutoOPERATOR to take automated action on the job.
(optional) At RESET WLM service class, specify a WLM service class name that provides the lowest possible level of service.
This action quiesces the looping region. Additionally, the region's status is set to ABDUMP in progress until you stop IMS or otherwise cancel the region.
At the COMMAND line, type END to save the profile.
Saving the profile automatically enables it. You do not need to manually enable the profile. MainView for DBCTL creates an alarm based on the profile and based on a default alarm definition. Now, whenever a job meets all of the profile's criteria, MainView for DBCTL will take any actions defined in the profile and will generate an alert.
Related topic