Share This:

MainView Infrastructure 6.1 introduces you to two powerful new features: Threshold Advisor and Dynamic Threshold. Here we will discuss installation and customization:
Installation

MainView Infrastructure 6.1 will be installed on the mainframe as it always has been, using the OZI installer and integrated customization tool. The customization tool will have a new phase called Infrastructure Setup that will install MainView Infrastructure 6.1 and RTCS.

New for the MVI 6.1 installation are:

  1. An additional component called UIM - our web server address space, to be installed. 
  2. A requirement for a new product level RTCS registry file for each CAS with the DDNAME = CASPERM, that you will have to allocate, either in the OZI customization process or by the view CASPERM. 
  3. A new OZI customization question for installing the UIM component, so you can specify which CAS you want to be the target for Threshold information to be uploaded to, if you use the new Threshold Advisor product. You only need to target one CAS per CASPLEX (group of connected CASs) for Threshold Advisor to communicate with, and that CAS will be able to deploy Dynamic Thresholds to all other CASs that Threshold Advisor has elements for.

  You will also need to install on a Windows server, the MainView Threshold Advisor product, and the Capacity Database (CDB) web-services. The CDB is used in conjunction with MainView Threshold Advisor to store downloaded interval data, and to perform the necessary analytics to produce recommended threshold values. 

 

Once Threshold Advisor is installed, you should decide which set of MainView Best Practice metrics you want to work with to calculate recommended thresholds. Threshold Advisor will require 3 weeks of data before it can complete a study and recommend Thresholds, so my advice is to start this activity as soon as possible.

 

You can also perform the following activities to get ready for Phase 2:

  • Set up your business week by defining Calendar Periods for which you would like to calculate different Threshold values. These Calendar Periods would normally define times where your workload is noticeably different than at other times of the day, so you would expect that different Threshold Values would allow better management, i.e. fewer false alarms.

 

MVI 6.1

Threshold Advisor – suggested customization phase 1
  1. Select a data element (metric) that you are interested in. 
    1. One that changes significantly during the test period and one where it may vary across the entire range of Threshold Values (Info, Warn, Minor, Major, Critical). This would allow you to see the full range of results. 
    2. CPUBsy% may be a good one.
  2. Define a set of Thresholds on the metric at the View Level and watch the metric change colors as it varies across the range of values. You may need to pick Threshold Levels much lower than in production to see all of the severity levels, such as CPU = 10, 20, 30, 40, and 50. You will need this View Level Threshold established to verify that the Dynamic Threshold has overridden the View Level Threshold. 
    1. You could set all Threshold results to show the value as "green". 
    2. In Dynamic Thresholds, you could set all Threshold results to show as "red" and prove that the Dynamic Threshold has overridden the View Level Threshold.

  3. Define a set of Calendar Periods that you will use for testing. 

  1. Initially the test Calendar Periods should be short (2 – 5 minutes) so you can verify that different Threshold values are in effect for different Calendar Periods. It should not be necessary to wait for hours to observe this transition. 
  2. Later you may change the Calendar Periods to times that represent what you would actually like to use in your environment.

4. Define a Threshold Set on a data element (metric) you are interested in.

  1. Define a second Threshold Set with different Threshold Values that you can associate with a different Calendar Period. This will allow you to verify that you have Dynamic Thresholds in effect, and you have different Threshold Values in effect at different times of the day.

  5. Define a Threshold Selection and assign each Threshold Set to a different Calendar Period. 

6. Now you can verify several things:

  1. As you watch the transition of time from one Calendar Period to another, you should see different Threshold Values in effect if the Threshold Selection has been set up that way. 
  2. If the View Level Thresholds were set to always show "green", and the Dynamic Threshold is in effect and set to always show "red", then the metric on the view should now be red. This would show that the Dynamic Threshold is in effect and overriding the View Level Thresholds.

7. Validate that other views that contain this metric are "red".

  1. This will show that Dynamic Thresholds are active in ALL views.

  8. Go to one view with the metric and update the Threshold definition for the view so that it specifies that on this view, the View Threshold is to override the Dynamic Threshold. 

  1. Result: all views should have the metric showing as "red" from the Dynamic Threshold definition, but this view should show the metric as "green".

9. Repeat this test scenario for Alarms.

 

Threshold Advisor – Phase 2

By now, you will have collected 3 weeks of sampled data from MainView, for the Best Practice metrics that you selected.

  1. At this point you will run the statistical analysis of the data you have collected. 
  2. This will produce recommended Threshold Values for the metrics you selected, and they will be correct for the time periods you selected for your calendar periods. You will also receive reports and graphs showing the relationship of observations that were collected and the recommended Threshold Values. Use these to check that the Threshold Values produced made sense for your environment. 
  3. When you are sure the recommended Thresholds make sense, you can PUSH them to the mainframe from your PC (Threshold Advisor). 
  4. After the PUSH completes, go to the mainframe and from the MainView product, check to be sure the thresholds you PUSHed have arrived correctly.

 

Thanks to Rich Comeau fro providing this information.

 

I am looking forward to feedback on how you are using Threshold Advisor and Dynamic Thresholds.

 

Regards,

 

Martin