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.

Setting time and CPU limits for EXECs


The following list describes how to set CPU and time limits for EXECs.

  • Set the parameters in BBPARM member AAOEXP00 to control time and CPU limits for all EXECs:
    • PEREXLIM; determines a percentage of CPU used by an EXEC
    • TIMEXLIM; determines a CPU time limit used to run an EXEC
    • ELAPSLIM; determines the elapsed amount of time used to run all EXECs

  • Use the IMFEXEC CNTL statement and its parameters in an EXEC to control time and CPU limits for a specific EXEC:
    • PERLIM(xx)
    • TIMLIM(xx)
    • ELAPSLIM(xxxx)

If these parameters are specified in an EXEC with the IMFEXEC CNTL command, they override the parameters set on PEREXLIM, TIMEXLIM, and ELAPSLIM in BBPARM member AAOEXP00.

See CNTL for more information about IMFEXEC CNTL and its parameters.

When you specify the following, the EXEC runs until it exceeds 15% of the CPU during any 15 second interval. If the EXEC exceeds 15%, it is terminated automatically.

IMFEXEC CNTL PERLIM(15)

When you specify the following, the EXEC runs until it exceeds 10 CPU seconds. If the EXEC exceeds 10 CPU seconds, it is terminated automatically.

IMFEXEC CNTL TIMLIM(10)

When you specify the following, the EXEC runs until it exceeds 99 minutes from the time that the EXEC thread starts to run the EXEC. If the EXEC exceeds 99 minutes, it is canceled automatically and messages that the EXEC has exceeded its time limit are written to the BBI Journal.

IMFEXEC CNTL ELAPSLIM(99)

When an EXEC exceeds the limits you set, check to see if it is executing correctly or if it has gone into a loop. Use the EXEC Management Application to determine if EXECs are running closely to the limits you have set. BMC recommends that you set these parameters with nonzero values because a value of zero allows unlimited CPU or time consumption by an EXEC.

 

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

BMC AMI Ops Automation 8.3