IBM Support

OMEGAMON IMS ROHI and ROLO exceptions

Question & Answer


Question

What are the steps to set the ROHI (message region occupancy is > nn%) and ROLO (message region occupancy is

Answer

ROHI Displays when the message region occupancy is > nn%.
OMEGAMON calculates the occupancy factor by sampling each message region once every OMEGAMON cycle, to see if OMEGAMON has scheduled a transaction.
As this is a statistical method, the data is not significant until there is a relatively large number of samples. OMEGAMON bypasses this exception until it takes at least 120 samples.
Note: If OMEGAMON's interval setting is five seconds, there is a ten minute delay for OMEGAMON to calculate occupancy. OMEGAMON does not automatically treat WFI region occupancy as 100%, and only considers a WFI region occupied if the region is not in the waiting for input state.
For the occupancy factor calculation, OMEGAMON only maintains samples fewer than 60 minutes old. Therefore, the region occupancy is an average over the preceding hour. As message regions stop and restart, OMEGAMON begins the calculation again.
A sample exception message is ROHI MPP 'MESSAGE': Region Occupancy = 93.84% (High).

ROLO Displays when the message region occupancy is < nn%.
OMEGAMON calculates the occupancy factor by sampling each message region once every OMEGAMON cycle, to see if OMEGAMON has scheduled a transaction.
As this is a statistical method, the data is not significant until there is a relatively large number of samples.
OMEGAMON bypasses this exception until it takes at least 120 samples.
Note: If OMEGAMON's interval setting is five seconds, there is a ten minute delay for OMEGAMON to calculate occupancy.
OMEGAMON does not automatically treat WFI region occupancy as 100%, and only considers a WFI region occupied if the region is not in the waiting for input state.
For the occupancy factor calculation, OMEGAMON only maintains samples fewer than 60 minutes old. Therefore, the region occupancy is an average over the preceding hour. As message regions stop and restart, OMEGAMON begins the calculation again.
A sample exception message is ROHI MPP 'MESSAGE': Region Occupancy = 6.72% (Low).

Region occupancy is a somewhat tricky metric.
In order to compute it, sampling of the dependent regions has to happen over a period of time, and with a sufficient number of samples to be statistically valid. When a user first logs on to a session, the value of the "ocup" minor will show as "--init--" until a sufficient number of samples have been collected for the data to be statistically valid. This can take 10 minutes with an automatic update cycle of 5 seconds.

In addition, the exception settings are session specific. If you change any of the XACB values but don't save them in a profile, the default settings will be used the next time you log on.
Also, if the settings are changed in your session, they will not be seen in another person's session.

To set these exceptions:

1) Clear the classic screens and issue the XACB command as follow:

 XACB LIST=ROHI
 : ROHI
 + DISPLAY Parameters: THRESHOLD Parameters: XLF Parameters:
 : State=OFF Threshold=1 Auto=OFF
 : Group=IM Display=CLR2 Log=OFF
 : Bell=OFF Attribute=NONE Limit=0 (0)
 : BOX Parameters: CYCLE Parameters: Repeat=NO
 : Boxchar=NO BOX ExNcyc=0 Persist=0
 : Boxclr=NONE Stop=0 (0) SS=
 : Boxattr=NONE Cumulative=0
 XACB LIST=ROLO
 : ROLO
 + DISPLAY Parameters: THRESHOLD Parameters: XLF Parameters:
 : State=OFF Threshold=2 Auto=OFF
 : Group=IM Display=CLR2 Log=OFF
 : Bell=OFF Attribute=NONE Limit=0 (0)
 : BOX Parameters: CYCLE Parameters: Repeat=NO
 : Boxchar=NO BOX ExNcyc=0 Persist=0
 : Boxclr=NONE Stop=0 (0) SS=
 : Boxattr=NONE Cumulative=0

2) Change the state from OFF to ON for both (just overwrite the parameter' value).

3) Set the wanted threshold for both

4) Go back to the main menu and select "E EXCEPTIONS" and than "B SYSTEM", you will see the exceptions (you should wait some required time):

 > Systemwide Exceptions
 
 LXIMS OMEGAMON/IMS Exception Analysis
 + ARSP Average INPUT QUEUE TIME for GROUP PART
 + ARSP Average PROCESSING TIME for GROUP PART
 + ARSP Average RESPONSE TIME-0 for GROUP PART
 + ARSP Average RESPONSE TIME-1 for GROUP PART
 + LALO Control Region : LSQA assurance space, size=
 + VXLO VSAM Database: DI21PART DDName: DI21PART I/O R
 + VXLO VSAM Database: DI21PART DDName: DI21PARO I/O R
 + ROHI MPP 'IMSNMPR1': Region Occupancy = .00% (High
 + ROLO MPP 'IMSNMPR1': Region Occupancy = .00% (Low)

To see the Region Occupancy in OMEG Classic, go to the main menu, than select "W WORKLOAD" than "D REGIONS" than scroll down to the following:

ocup --n/a-- --n/a-- --n/a-- --n/a-- .00%

check the column related to your region.

To set the automatic update cycle, go to the main menu and select "P PROFILE" than "K AUTO ON", the screens will automatically refresh.

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SS5FZU","label":"IBM OMEGAMON for IMS on z\/OS"},"Platform":[{"code":"PF035","label":"z\/OS"}],"Component":"","Version":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
16 February 2018

UID

dwa1291330