Skip to Content
Information
Newer version of documentation BMC provides a newer version of the documentation for this version of the product. As a result, BMC no longer accepts comments in this space.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see bao8301.

Schedule EXECs on the EXECs Thresholds panel

With the EXEC Thresholds panel, you can specify the number of EXECs that can be scheduled to the High and Normal priority queues by using MAXNORM and MAXHIGH parameters. When the number of scheduled EXECs matches the values set in these parameters, all scheduling stops until the number of EXECs drops below the thresholds.

You can also specify two thresholds for the High and Normal queues that, when reached, issue warning messages telling you that the threshold has been reached. These thresholds are WARNLVL1 and WARNLVL2 and the values represent percentages of MAXNORMQ and MAXHIGHQ.

Examples of setting EXEC thresholds

For example, you can specify

MAXNORMQ ===> 150

MAXHIGHQ ===> 100

and

WARNLVL1 ===> 50

WARNLVL2 ===> 75

For the Normal queue, warning messages are sent when 75 EXECs are scheduled and again when 112 EXECs are scheduled.

WARNLVL1 50% OF 150 = 75
WARNLVL2 75% OF 150 = 112

For the High queue, warning messages are sent when 50 EXECs are scheduled and again when 75 EXECs are scheduled.

WARNLVL1 50% OF 100 = 50
WARNLVL2 75% OF 100 = 75

Scheduling of EXECs stops when the maximum values are reached. EXEC scheduling automatically resumes when the number of EXECs drops below the maximum. Refer to the descriptions of the MAXNORMQ, MAXHIGHQ, WARNLVL1, and WARNLVLV2 fields in EXEC Thresholds panel fields for more information.

Related topic

EXEC-Thresholds-panel




 

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

BMC AMI Ops Automation 8.3