Scheduling Hot or First priority EXECs to the Hot priority queue

EXECs that are scheduled as Hot or First priority do not have separate EXEC threads that are available to run the EXECs.

When an EXEC is scheduled as either a Hot or a First priority EXEC, it is queued to the Hot queue and then runs on an EXEC thread from either the Normal or High priority queues.

Related topic

Scheduling-EXECs

  • The Hot priority queue schedules Hot priority EXECs by using FIFO queuing strategy to the first available EXEC thread from either the Normal or the High thread pool.

  • The Hot priority queue schedules First priority EXECs by using last in, first out (LIFO) queuing strategy to the first available EXEC thread from either the Normal or the High thread pool.

Important

Use the Hot and First priorities only for the most critical situations so that they can be as effective as possible.

To send an EXEC to the Hot priority queue, you must identify the EXEC in one of the following ways:

  • Use the PRI(HOT) or PRI(FIRST) keyword of the IMFEXEC SELECT or AOEXEC SELECT command.

    See SELECT for more information about the IMFEXEC SELECT command and to AOEXEC-SELECT.

  • Use the PRI(HOT) or PRI(FIRST) keyword of the AOSUBX command.

    See Syntax-for-invoking-AOSUBX for more information about the AOSUBX command keywords.

  • Use the PRI(HOT) keyword on the EXEC, ESCEXEC, and ESCCMD keywords of the IMFEXEC ALERT or AOEXEC ALERT commands.

    See ALERT for more information about the IMFEXEC ALERT command and to AOEXEC-ALERT.

  • Specify the HOT or FIRST on the REXX Exec or CLIST panel of the Rule Processor.

See Using-Rules-with-BMC-AMI-Ops-Automation for more information about using the Rule Processor.

 

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