Load-Indexes Based on MainView Alarms

The Control-M for z/OS Workload Optimization feature gathers z/OS performance metrics sourced from RMF Monitor III and uses these metrics to set internal Load-Indexes. If you do not have access to RMF, you can alternatively use BMC's MainView Alarm Management, part of the BMC AMI Ops Automation suite, as the source for performance metrics.

If you use MainView, you can utilize MainView Alarms as the basis for one type of Load-Indexes in Control-M (alongside the other types of Load-Indexes that you can define in Control-M). These MainView Alarm-based Load-Indexes are automatically set by Control-M whenever an alarm is reported by MainView.

Ongoing monitoring of MainView Alarm-based Load-Indexes by Control-O or CMEM is controlled by the OPTMVLID parameter in the OPTIMIZE section in CTMPARM.

For more information, see Using Load-Indexes in workload optimization.

Note that the threshold severity levels of MainView Alarms differ from the threshold levels of Load-Indexes in Control-M. The following table maps MainView threshold values to Control-M threshold values.

Table 15a Prefixing Examples

Example:

Alarm DYCLIW06 of the iCap distributed alarms is used in a MainView-based Load-Index to enable Control-M to limit the submission of low-priority jobs when critical workload is at risk in the LPAR.

The following figure shows the definitions of Load-Index DYCLIW06, which is based on the iCap alarm of the same name.

Figure 1a Definitions of Load-Index DYCLIW06 to limit low-priority jobs

                   LOAD-INDEX: DYCLIW06                                        

COMMAND ===>                                                    SCROLL===> CRSR

+-----------------------------------------------------------------------------+

|                                                                             |

| Load-Index Name ==> DYCLIW06                                                |

|                                                                             |

| Description ==> MAINVIEW ALARMS WHEN CRITICAL WORK IS AT RISK IN THE LPAR   |

|                                                                             |

| Type        ==> M         (U-Util, 4-4HRA, E-External, M-MainView Alarm)    |

|                                                                             |

|                                                                             |

====== >>>>>>>>>>>>>>>>>>> END OF LOAD-INDEX DETAILS <<<<<<<<<<<<<<<<<<< ======

The following figure shows the definitions of a Workload Policy with threshold levels set by Load-Index DYCLIW06.

Figure 1b Definitions of Workload Policy with thresholds set by Load-Index DYCLIW06

                        POLICY: LOW_PRIORITY_JOBS                              

COMMAND ===>                                                    SCROLL===> CRSR

+-----------------------------------------------------------------------------+

|                                                                             |

| WORKLOAD POLICY NAME LOW_PRIORITY_JOBS                STATUS ACTIVE   (A/I) |

|                                                                             |

| =========================================================================== |

| POLICY FILTER (UPDATED ON 28.02.22 13:14 BY USER U05B     )                 |

| =========================================================================== |

| MEMNAME                                                                     |

| APPL      REP*                                                              |

| GROUP                                                                       |

| SCHED TAB                                                                   |

| APPL TYPE                                                                   |

| SCHENV                                                                      |

| =========================================================================== |

| POLICY RULES  (UPDATED ON 28.02.22 13:14 BY USER U05B     )                 |

| =========================================================================== |

| R U L E   T Y P E S:    |  P E R I O D  T Y P E S:                          |

|                         |                                                   |

| R - RESOURCE LIMIT      |  1 - DAYS                   4 - WEEK DAYS RANGE   |

| J - JOBS LIMIT          |  2 - BETWEEN DATES          5 - SPECIFIC DATES    |

|                         |  3 - BETWEEN DATES AND TIME 6 - ADVANCED SCHED    |

| =========================================================================== |

| RULE TYPE JOB                    PERIOD TYPE 1 - Days                       |

| DESCRIPTION DELAY LOW-PRIORITY JOBS WHEN CRITICAL WORK IS AT RISK           |

| LIMIT 0000 WHEN LOAD-INDEX DYCLIW06             AT LEVEL CRITICAL AND ABOVE |

| BYPASS LIMIT FOR JOBS WITH     MINUTES OR LESS BEFORE DUE IN                |

| ON WEEKDAYS ALL                         (OR ALL)                            |

|        EACH DAY, FROM TIME      UNTIL TIME                      (HH:MM)     |

| =========================================================================== |

| RULE TYPE JOB                    PERIOD TYPE 1 - Days                       |

| DESCRIPTION LIMIT LOW-PRIORITY JOBS WHEN CRITICAL WORK IS AT RISK           |

| LIMIT 0010 WHEN LOAD-INDEX DYCLIW06             AT LEVEL HIGH     AND ABOVE |

| BYPASS LIMIT FOR JOBS WITH     MINUTES OR LESS BEFORE DUE IN                |

| ON WEEKDAYS ALL                         (OR ALL)                            |

|        EACH DAY, FROM TIME      UNTIL TIME                      (HH:MM)     |

| =========================================================================== |

| RULE TYPE                        PERIOD TYPE   (1-6 or ? for selection)     |

| =========================================================================== |

====== >>>>>>>>>>>>>>>>>>>> END OF POLICY DEFINITION <<<<<<<<<<<<<<<<<<<< =====