Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, seeBMC AMI Ops Monitor for DBCTL 5.5.

Loop Check Profile alarm messages overview

The following scenarios provide examples of the alarm message process. For these scenarios, assume that the following conditions apply:

  • For each profile type (WTO/ABDUMP, WTO/RESET/CANCEL, and WTO/RESET), you have defined an alarm to generate an alert and take action when a potential loop is detected. 
  • One of your monitored IMS regions has met the loop criteria that you specified. 
  • The potentially looping region is not in a U0113 window. 

The alarms proceed as follows: 

First, the WTO/ABDUMP alarm triggers and issues a STOP REGION ABDUMP command. It then generates one of the following messages to alert you:

MPPSS00 SEV=CRI I14YGBG RgnName:I14YMP1 ID:1 IMS ID:I14Y Type:MPP TRAN:THISMINQ PGM:PHISMINQ Alarm criteria met
MPPSS00 SEV=CRI I14YGBG RgnName:I14YMP1 ID:1 IMS ID:I14Y Type:MPP TRAN:THISMINQ PGM:PHISMINQ Alarm criteria met (Persisting) 

Note

The preceding messages provide the following information: 

    • Profile name (MPPSS00)
    • IMS target name (I14YGBG)
    • Dependent region name (I14YMP1) 
    • Region ID number (I14Y) 
    • Region type (MPP) 
    • Transaction name (THISMINQ) 
    • Program name (PHISMINQ)

When the WTO/ABDUMP alarm issues the IMS /STOP REGION 1 ABDUMP THISMINQ command to IMS I14YGBG, this action should result in the U0474 – resolving the problem with no further action needed. This is because the region is not in a U0113 window and so the ABDUMP command was received and processed by IMS.

However with some types of loops, IMS will not receive or process the ABDUMP command. When this occurs, the WTO/RESET alarm can address the loop by resetting to the slowest WLM service class. 

When the WTO/RESET alarm triggers, after about 45 seconds the following message is issued:

MPPSS00 SEV=CRI I14YGBG RgnName:I14YMP1 ID:1 IMS ID:I14Y Type:MPP  TRAN:THISMINQ PGM:PHISMINQ Alarm criteria met, Continued Looping

Since the loop is persisting, the WTO/RESET alarm quiesces the looping region. After executing the RESET, the alarm then issues the following message to inform you that the region was slowed by the RESET command:

MPPSS00 SEV=CRI I14YGBG RgnName:I14YMP1 ID:1 IMS ID:I14Y Type:MPP  TRAN:THISMINQ PGM:PHISMINQ End of Alarm criteria met 

This action quiesces the loop for about 90 seconds or more. Furthermore, based on the WTO message the WTO/RESET alarm writes, you can now make use of other automation to take other actions, such as ABDDUMP or CANCEL.

Finally, when a looping region is persisting and the alarm determines that the region is in an U0113 window, you can use the WTO/RESET/CANCEL alarm. With this alarm, you can choose to:

  • Write a warning message and RESET the WLM class to quiesce the region
  • Write a warning message and CANCEL the region

Note

If the region had been in a U0113 window after the ABDUMP and you had an active alarm profile for that scenario, the alarm would generate a message starting with that profile name and ending with the action taken, as follows:

  • If the action specified for the alarm profile was CANCEL, the message would end with the CANCEL command and IMS would terminate with a U0113.
  • If the action specified was RESET, the message would end with the IBM MVS RESET command. This action would reduce the region’s CPU usage according to the service class that you specified.

Related topic

Profiles-for-Looping-Dependent-Regions

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*