BRETT PATERSON

Maxava Monitor Mi8 - IBM i - Create Rule – Pools Rule

Overview

These are the steps to create a Pools rule on the Mi8 Monitor.

Reason for rule

The intention of this rule is to alert when any of the selected rule key conditions are met (see point 11). 
See the end of this document for examples.

Prerequisites

A template must already have been created (see Maxava Monitor Mi8 - Create Template).
Full functionality is available from IBM i V6R1 onwards. Limited functionality may be available prior to this level.

How to Create a Rule

1. Click on the  icon at top left, then  , followed by  .
   Alternatively click on  , then  .
2. Click on Rules > New Rule > Edit Rule .
   
   
3. Rule Title: Unique identifier for the rule.
4. My Description: Description for the rule.
5. Event Template: Select the appropriate Event Template from the drop down list. The Template will
   influence when a rule will be active. At least one template must be available to create a rule (see Maxava Monitor Mi8 - Create Template).
6. System Type: Select IBM i from the drop down list.
7. System: Select the appropriate System from the drop down list.
8. Rule Active: Set this to ON for the rule to be active immediately after adding. Leave set to OFF if the rule will be edited further.
9. Select Escalations: Select an escalation or leave as NONE. This is not a prerequisite and Escalations may be added later. See "Maxava Monitor Mi8 - Create Escalation” to create escalations.
10. Rule Class: Select POOLS from the drop down list.
11. Rule Key: Select the appropriate Rule Key from the drop down list.
    The definitions of the Rule Keys are:
           a.Pool Size: The amount of main storage, in kilobytes, in the pool.
           b.Res Size: The amount of storage, in kilobytes, in the pool reserved for system use. e.g. For               save/restore operations.  The system calculates this amount by using storage pool sizes and             activity levels.
           c.Max Active Jobs: The maximum number of jobs that can be active in the pool at any one                   time.       
           d.DB Faults: The rate, in page faults per second, of database page faults against pages                       containing either database data or access paths. A page fault is a program notification that                 occurs when a page that is marked as not in main storage is referred to by an active                         program. An access path is the means by which the system provides a logical                                   organization to the data in a database file. For example, a value of 123 in binary would                       be 12.3 page faults per second.     
          e.DB Pages: The rate, in pages per second, at which database pages are brought into the                    storage pool. A page is a 4096-byte block of information that is transferable between                          auxiliary storage and main storage. For example, a value of 123 in binary would be 12.3                      pages per second.
           f.Non-DB Faults: The rate , in page faults per second, of nondatabase page faults against                    pages other than those designated as database pages. For example, a value of 123 in binary              would be 12.3 page faults per second.
            g.Active_Wait: The rate, in transitions per minute, of transitions of threads from an active                     condition to a waiting condition. For example, a value of 123 in binary would be 12.3                           transitions per minute.
             h.Wait_ineligible: The rate, in transitions per minute, of transitions of threads from a waiting                condition to an ineligible condition. For example, a value of 123 in binary would be 12.3                       transitions per minute.
             i.Active_ineligible: The rate, in transitions per minute, of transitions of threads from an                       active condition to an ineligible condition. For example, a value of 123 in binary would be                    12.3 transitions per minute.
             j.Paging_Option: Whether the system will dynamically adjust the paging characteristics of                  the storage pool for optimum performance.
12. Rule Selector: Enter the appropriate Pool, or ** for all.
13. Description: Leave as default.
14. Case: Select appropriate option.
15. Threshold Warn: Enter the required value that will trigger a Warning Alert.
16. Delay Warn (Mins): Enter the delay, in minutes, before the Warning Alert is issued.
17. Threshold Critical: Enter the required value that will trigger a Critical Alert.
18. Delay Critical (Mins): Enter the delay, in minutes, before the Critical Alert is issued.
19. Click on RULE TIME SETTINGS.
20. Time Zone: Select the appropriate Time Zone from the drop down list.
21. Select Hours Range: Select the hours the rule will take effect. Please note time is represented in 1 hour blocks e.g. MIDNIGHT will cover 00:00am to 00:59am, 1AM will cover 1:00am to 1:59am and so on.
22. Select Date Range: Select the dates the rule will be in effect. 
23. Select Days to Run: Select the days of the week the rule will be in effect.
24. Select Months to Run: Select the months the rule will be in effect.
25. Click on the  button and the message  will display.

Examples of the Rule

Example 1
Notify when the number of jobs in all pools exceeds 250 and remains so for 5 minutes. Becomes a critical notification (turns RED) when the number of jobs in all pools exceeds 350 .
This rule is based on the Sydney Time Zone, all hours, 1st and 31st , all months.

Example 2
Notify when main storage in pool *BASE is less than 1GB (1000000KB).
Becomes a critical notification ( turns red) if it remains so for 2 minutes.
Takes effect in the Queensland Time Zone, all hours, all dates, all days, all months.