Defining loop check profiles to stop a looping IMS region

Use the following procedure to define a loop check profile that can detect looping IMS regions or regions that are using excessive CPU. Based on your preferences, the product can then generate an alert or generate an alert and issue a STOP REGION ABDUMP command.

To define a loop check profile to stop a looping IMS region

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 STOP REGION ABDUMP.
The ILPCKPL 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 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)
-RESET is recommended, since CANCEL from this alarm
-will stop IMS with a U0113 ABEND
RESET WLM service class:          (Specify lowest WLM service class)
IMS STOP RGN CANCEL:              (Y -Yes, See help for U0113 warning)
-Do not use CANCEL unless IMSID or CRC is unique!
IMS Command prefix type:   (I -IMSID(default) or C -CRC)
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.

Note

If you want any of the loop criteria ignored, leave the field empty.

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:
1. At Include, enter up to five IMS application region job names to which this profile applies.
2. At Exclude, enter up to five IMS application region job names to which this profile does not apply.
  Note
  Specify full or generic names. For generic names, you can use a single trailing asterisk (*), but you cannot use the plus sign (+) wildcard.
  If you leave the Include field blank, the profile applies to all jobs except those that you list in the corresponding Exclude field.
  Example
  Assume that you want to apply a profile to all jobs that start with PROD except for those that start with PROD123. Enter PROD* in the Include field and PROD123* in the Exclude field.
Under Region Types, specify the region types that identify jobs to which this profile should or should not apply:
1. At Include, enter up to four region types to which this profile applies.
2. At Exclude, enter up to four region types to which this profile does not apply.
  Note
  Valid types are BMP, JBP, MPP, JMP, DBT, ODB, MDP, CON, TPI, NDP, FPU.
Under Transaction Names, specify up to five IMS transaction names that identify jobs to which this profile should or should not apply:
1. At Include, enter up to five transaction names to which this profile applies.
2. At Exclude, enter up to five transaction names to which this profile does not apply.
  Note
  For generic names, you can use a single trailing asterisk (*), but you cannot use the plus sign (+) wildcard.
Under LTERM Names, specify up to four IMS LTERM names that identify jobs to which this profile should or should not apply:
1. At Include, enter up to four IMS LTERM names to which this profile applies.
2. At Exclude, enter up to four IMS LTERM names to which this profile does not apply.
  Note
  For generic names, you can use a single trailing asterisk (*), but you cannot use the plus sign (+) wildcard.
Under Program Names, specify up to five IMS program names that identify jobs to which this profile should or should not apply:
1. At Include, enter up to four IMS LTERM names to which this profile applies.
2. At Exclude, enter up to four IMS LTERM names to which this profile does not apply.
  Note
  For generic names, you can use a single trailing asterisk (*), but you cannot use the plus sign (+) wildcard.
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.
Note
Security resource 'BBM.COMMON.OPERCMD.PA' must be defined to your ESM (IBM RACF product or CA Technologies CA ACF2 or CA Top Secret product) with proper authority to use the STOP REGION ABDUMP command.
At STOP RGN ABDUMP, specify Y if you want to have IMS issue a STOP REGION ABDUMP command when a job matches all of the criteria in this profile.
Warning
This command is prefixed by the IMS ID or CRC of the IMS the job you specified in step 6. If you have multiple IMS systems on the same LPAR with the same IMS ID or CRC, you should not use this option because it could cause the wrong IMS regions to be stopped.
For an MPP or JMP, the current transaction name will be added to the end of the command.
Tip
You can set a separate loop check alarm profile that will issue a STOP REGION CANCEL command if the ABDUMP command does not complete within approximately 30 to 45 seconds
At Command prefix type, depending on the IMS region that the job is connected to, specify whether the command is prefixed by the IMS ID or the CRC.
By default the IMS ID will be used. You should choose whichever option ensures that the command will only be processed by the IMS associated with the job that triggers the alarm.
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.

Defining loop check profiles to stop a looping IMS region

To define a loop check profile to stop a looping IMS region

On this page