Skip to Content

Minimizing EXEC processing time

In general, BMC recommends you use Rules to perform basic automation tasks whenever possible.

Rules are less prone to have errors and use less CPU than EXECs. The use of EXECs should be considered only after you have determined that the automation task cannot be accomplished with a Rule.

Related topic

Using-advanced-techniques-with-BMC-AMI-Ops-Automation-EXECs

For BMC AMI Ops Automation to perform automation efficiently with EXECs, the subsystem must be tuned to process EXECs as quickly as possible. The desirable level of throughput (or the number of EXECs processed per minute) for each site varies, depending on your automation requirements and the design of the EXECs.

You can do some things to ensure that EXECs run efficiently:

  • Fix the dispatching priority of the subsystem.

    The subsystem (SS) must be run at a fixed dispatching priority. The priority of the SS must be higher than (or equal to) the regions that BMC AMI OpsA is managing (for example: CICS, IMS, JES2). This setting ensures that BMC AMI OpsA can quickly respond to events in these regions.

  • Allocate the correct number of EXEC threads.

    Adjust the number of EXEC threads (with the MaxNorm and MaxHigh parameters in BBPARM member AAOEXP00) to the minimum number required to achieve the level of throughput that you want.

  • Use the z/OS Virtual Lookaside Facility (VLF) service.

    Using VLF allows BMC AMI OpsA to perform EXEC processing with a minimum of I/O activity, and reduced I/O activity leads to less system overhead and improved performance.

    See the IBM documentation MVS Initialization and Tuning Reference for information about the VLF service.

This section contains the following topics: 

 

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

BMC AMI Ops Automation 8.3.01