AOEXEC SELECT

Specified only with the EXEC keyword

Specifying a priority value on the EXEC overrides the EXEC parameter in BBPARM member AAOEXP00.

Valid values are as follows:

NORM | N schedules the EXEC with a normal priority setting by using first in, first out (FIFO) queuing strategy. The EXEC is placed in the Normal priority queue and uses an EXEC thread from the MAXNORM thread pool.

HIGH | H: Schedules the EXEC with a high priority setting by using a FIFO queuing strategy. The EXEC is placed in the High priority queue and uses an EXEC thread from the MAXHIGH thread pool.

HOT | T: Schedules the EXEC as a hot EXEC by using a FIFO queuing strategy on the Hot priority queue. The next available EXEC thread from either the Normal or High priority EXEC thread pool is used to run the EXEC waiting on the Hot priority queue.

FIRST | F: Schedules the EXEC as a hot EXEC by using a last in, first out (LIFO) queuing strategy on the Hot priority queue. The next available EXEC thread from either the NORM or HIGH EXEC thread pool is used to run the EXEC waiting on the Hot priority queue.

SINGLE | S: Schedules the EXEC with the normal priority setting but allows only one instance of the EXEC to execute at a time, regardless of the number of available EXEC threads. For EXECs to be single-threaded using this option, the EXECs must have the same name and must specify SINGLE when scheduled. EXECs that have the same name and are scheduled without SINGLE specified are not single-threaded with EXECs that have SINGLE specified.

XSINGLE | X: Attempts to schedule the EXEC with the normal priority setting. However, if another instance of the EXEC that also specified XSINGLE is already running (or waiting to run), the scheduling request is rejected and message EM6111W is written to the BBI-SS journal.

Valid values are 0 to 99999 seconds.

The default value is 0 seconds, which means the command is executed with no delay. In addition, the DELAY|DLY parameter includes the following conditions:

• Responses are not available for delayed commands.  A non-zero delay request will fail with any other specification that requests command responses.
• You cannot specify a delay with the SHARE, TGTJNT, and WAIT(YES) parameters.
• When scheduling delayed EXEC to a remote PAS (with the TGTSS parameter), the delay will occur on the target PAS.
• The delay request is no longer valid after an IPL or bouncing the PAS.
• Delayed requests are not supported for local or remote PAS when running a version earlier than 8.3 of BMC AMI Ops Automation.

Valid values are either YES or NO.

WAIT(YES) causes the AOEXEC command to be suspended until the scheduled EXEC in the PAS has completed.

WAIT(NO) is returned as soon as OpsA processing determines if the EXEC to be scheduled actually exists.

When you specify the SHARE( ) or TGTJNT( ) parameter, WAIT(YES) function will be forced.

When WAIT(YES) is used, the return code that was passed in IMFEXEC EXIT is returned in IMFEXRC.

Generic wildcard characters are supported for this keyword. You can specify 1 to 4 asterisks (*) or plus signs (+).

• If you specify a single asterisk (*), any BBI-SS PAS found on the same LPAR might be used to process the EXEC. You can also specify SS(P*) and the EXEC can be processed by any BBI-SS PAS that begins with P.
  
  
• You can use also the plus sign (+) to indicate a positional wildcard such as SS(+++P). In this example, the EXEC can be processed on any BBI-SS PAS that ends in P.

Use the AOOPTION parameter to further filter on the wildcard value. By specifying a value with AOOPTION, you can route the EXEC to the BMC AMI OpsA BBI-SS PAS that is running a product option or group of product options.

AOOPTION is mutually exclusive with TGTSS and TGTJNT, and it is ignored on a fully qualified SSID specified with SS or SSID parameter.

Specifies the product options that must be active in the BMC AMI OpsA PAS. The following values are valid: ANV, CAO, IAO, IIZ, MAO, QAO, or TSH.

IIZ represents the BMC AMI OpsA BMC Impact Integration for z/OS product. The stand-alone BMC Impact Integration for z/OS product does not support AOAnywhere.

The specified product option must be active in the BMC AMI OpsA PAS.

The value specified with the AOOPTION parameter is valid only when the SSID parameter specifies a wildcard value.

AOOPTION cannot be specified if TGTSS or TGTJNT are also specified.

Is a JNT entry that identifies the SSID which processes this request

Use this parameter to specify a target that is running outside of the local MVS system where the AOEXEC EXEC is running. The specified target should match a TARGET=(tgtname) parameter in BBPARM member BBIJNT00.

The EXEC is scheduled on the subsystem that corresponds to the subsystem that is specified by the SS | SSID parameter of the JNT entry. You can also specify a TGTJNT subsystem that is an SSID with which the original subsystem communicates.

This keyword is mutually exclusive with the TGTSS() keyword.

When you enter a value for the TGTJNT() parameter, the value that you specify becomes the value of the IMFJTGT variable in the scheduled EXEC.

It must be in the same sysplex as the BBI-SS specified with the SSID() keyword, and both systems must have the same XCFGROUP specified in the BBPARM BBISSPxx.

When the AOEXEC command originates in a NetView EXEC, the router and local BMC AMI OpsA PAS must have an active, valid BMC AMI Ops Automation Access NV key.

The EXEC was canceled in BMC AMI OpsA.