BBPARM member AAOEXP00 parameters
For information about BMC AMI OpsA EXECs, see Using-advanced-automation-with-BMC-AMI-Ops-Automation; for documentation about using the Dynamic Parameter Manager application to update the parameters in AAOEXP00, see Customizing-BMC-AMI-Ops-Automation-after-installation.
The following lists the parameters for AAOEXP00.
Parameter | Description |
|---|---|
APIAUTH = [RACF|ORIGIN] | Specifies the user ID that will be used when MV API calls are invoked from BMC AMI OpsA EXECs Valid values are ORIGIN specifies that the EXEC origin is used as user ID for MV API calls. For ALERT-initiated EXECs, the origin is the origin of the ALERT. For Rule-initiated EXECs, the origin is the SSID of the BBI-SS PAS started task. RACF specifies that the user ID associated with the BBI-SS PAS started task is used for MV API calls. |
AUDITMSG=[YES | NO] | Specifies whether to record in the BBI-SS PAS Journal all occurrences of BLDLs against the SYSPROC data set and all user-initiated EXEC requests |
AUDITRES=[YES | NO] | Specifies whether BBI Journal message EM0715I is written to the log when an EXEC issues IMFEXEC RES Use the messages to help identify which of your automation EXECs use IMFEXEC RES command. This can be especially helpful when the BMC AMI Ops SYSPROG Servicesproduct releases new versions that introduce changes to SYSPROG commands or services that might impact your automation. |
AUDITEXE=[YES | NO] | Specifies whether to record in the BBI-SS PAS Journal audit messages indicating when EXECs start and end. You can use the parameter for debugging purposes. If YES is specified, audit messages are issued for all EXECs. You can create a JRNL-initiated Rule if you want to selectively record audit messages for only some EXECs and not others. |
CICSECID=[ ORIGIN | RACF ] | Specifies whether the user ID or the current origin of the EXEC is used for security checking of a IMFEXEC CICS command that is used in a remote EXEC when it is scheduled by a local Rule-initiated EXEC Default value is ORIGIN, which is used if you do not specify a value for this keyword; valid values are ORIGIN or RACF Default value is ORIGIN, which is used if you do not specify a value for this keyword; valid values are as follows: ORIGIN specifies that the EXEC origin is the name of the originating BBI-SS PAS where the EXEC was scheduled and the name of that BBI-SS PAS is used during security checking. RACF specifies that the security ID of the BBI-SS PAS is used during security checking. In both cases, the user ID is used for security checking of CICS commands that are used in EXECs scheduled in a remote BBI-SS PAS that are called by a local EXEC. |
ELAPSLIM=[0 | nnnn ] | Is the elapsed time limit for all EXECs If an EXEC is still running after the number of minutes specified, it will be canceled. Cancellation messages are sent to the BBI Journal that say an EXEC has exceeded the ELAPSLIM limit. You can set elapsed time limits for an individual EXEC with the IMFEXEC CNTL ELAPSLIM() keyword. Valid values range from 0 to 9999 and the default is 0. |
EMLOG=[YES | NO] | Specifies whether messages from EXECs will be written to the EMLOG Valid values are YES or NO. The default is NO. When you specify EMLOG=YES, the windows-mode EMLOG view is available for viewing, sorting and filtering EXEC messages. In the EMLOG view, you can select to view (filter) all the messages from a specific EXEC. This filtering ability is not supported in the MVLOG view. Use the MVLOGSS parameter in BBPARM member BBISSP00 to specify the SSID of the BMC AMI Ops Logger where EMLOG records are sent. |
EXHMC=[YES | NO] | Specifies whether the IMFEXEC HMC command can be used in EXECs Valid values are YES or NO. The default is NO. Refer to Additional-EXEC-parameters for more information about the implication of using IMFEXEC HMC. |
EXABCNT=[5 | nn] | Is the maximum number of abends that a single EXEC can sustain before it is disabled Valid values range from 1 to 99. The default is 5. For example, if you specify EXABCNT=10 and an EXEC abends 10 times, the EXEC is disabled after the tenth abend. |
EXEC=[name] | Specifies the names of EXECs that are scheduled as High priority EXECs A High priority EXEC is any EXEC that is listed with the EXEC= keyword. This parameter can be repeated. |
EXEC=[name],PRI=[FIRST,HIGH,HOT,SINGLE,XSINGLE] | Specifies the names of EXECs that are scheduled with the priority that you specify. The default priority setting is HIGH. To specify an EXEC to be scheduled at one of the following priority levels, use the optional keyword PRI:
This parameter can be repeated. |
EXECXCF=[Y | N] | Specifies whether BMC AMI OpsA processing for IMFEXEC MSG, VDEL, VGET and VPUT, when TARGET() is specified, attempts to use XCF communication. Specifying EXECXCF=N indicates that only VTAM Link communication should be used. The default value is EXECXCF=Y. |
MAXTPUT=[ 0 | nnnnn] | Is the maximum number of TSO TPUTs allowed for each execution of an EXEC Valid values range from 0 to 32767 The default is 0, which means no checking is done. TPUTs for EXECs scheduled with the WAIT=YES parameter are counted separately from the scheduling EXEC. |
MAXHIGH=[5 | nn] | Is the maximum high priority EXECs to execute concurrently A high priority EXEC is any EXEC that is listed with the EXEC= keyword. |
MAXHIGHQ=[0 | nnn] | Is the maximum number of high priority EXECs that may be queued for execution Valid values range from 0 to 999. The default is 0, which means no checking is done. |
MAXHOTQ=[10 | nnn] | Is the maximum number of First or Hot priority EXECs that can be queued When the maximum is reached, no more EXECs with First or Hot priority specified are scheduled until the queue level drops below the maximum level set. Valid values range from 0 to 999. The default is 10, which means no checking is done and all Hot or First priority EXECs are queued. |
MAXNORM=[1 | nn] | Is the maximum normal priority EXECs to execute concurrently A normal priority EXEC is any EXEC not in the high priority list. |
MAXNORMQ=[0 | nnn] | Is the maximum number of normal priority EXECs that may be queued for execution Valid values range from 0 to 999. The default is 0, which means no checking is done. |
MSGID = [Y | N | I] | Updates the TSO user profile BMC AMI Ops Automation uses to turn on (and off) the TSO MSGID option The following lists the valid values:
The default setting is Y. |
OSPINUM=[0 | nnn] | Is the maximum number of OSPI ACBs defined If 0, the request for a session is aborted upon encountering the first ACB that cannot be opened due to a reason other than that it is in use. Specifying the correct number of ACB definitions here helps bypass problems where ACBs have become unusable due to some other reason. |
OSPIPRFX=[OSPI | name] | Is a four-character prefix to use when selecting an OSPI ACB from the pool of available ACBs |
PEREXLIM=[0 | nn ] | Specifies an optional CPU percentage usage for an EXEC If an EXEC’s CPU usage exceeds this percentage during any interval of 15 seconds after the EXEC begins, the EXEC is automatically terminated. With the default value of 0, no percentage limit is assigned. The CPU percentage is calculated based on the total CPU time available on 1 CPU within that 15 second interval. For example, 20% means 20% of 15 seconds. If the CPU time exceeds 3 seconds with any given 15 second interval, the EXEC will be terminated. |
PREFIX=[SSID | name] | Specifies a prefix to be used when allocating a data set in an EXEC if the data set name is not enclosed within quotation marks The prefix value is set at BBI-SS PAS initialization. This value cannot be dynamically changed. This prefix also serves as the user ID associated with jobs submitted by EXECs. If the default is not specified, it will be the same as the BBI-SS PAS ID. |
RESAUTH=[ORIGIN|RACF] | Specifies the user ID that will be used when SYSPROG Services are invoked from BMC AMI Ops Automation EXECs Valid values are as follows: ORIGIN specifies that the EXEC origin is used as user ID for Sysprog Services. For ALERT-initiated EXECs, the origin is the origin of the ALERT. An exception occurs when the EXEC origin contains the BBI-SS PAS SSID or the jobname of the BBI-SS PAS. In this case, the user ID that is associated with the BBI-SS PAS started task is used. RACF specifies that the user ID associated with the BBI-SS PAS started task is used for SYSPROG Services. |
SELLIM=[0 | nn] | Is the maximum number of active EXECs on a single thread Valid values range from 0 to 99. The default is 0, which means no checking is done. This parameter is designed to control recursive calls (where EXECA schedules EXECB, that schedules EXECC, and so on) that run out of control, potentially filling up the private storage in the BBI-SS PAS and causing automation to stop. |
SUBXAUTH= [DEFER | JOBNAME|RACF|USER] | DEFER: (default) the decision for using JOBNAME or user ID for the security check is deferred to the batch job (IMFSUBEX) execution time JOBNAME: the JOBNAME is used for the IMFSUBEX security checks. This parameter overrides the origin specified on the batch job. RACF: the user ID is used for the IMFSUBEX security checks. This parameter overrides the origin specified on the batch job USER: same as RACF |
TIMEXLIM=[00 | nnnn] | Specifies an optional CPU time limit for an EXEC If the time limit is exceeded, the EXEC is terminated automatically. With the default value of 0, no time limit is assigned. |
TSOTIME=[1200 | nnnn] | Specifies the time-out value (in seconds) for attached TSO commands A value of 0 disables timing. |
UCPARMS=[YES | NO] | Specifies whether EXEC parameters are translated to uppercase |
UNITNAME=[SYSALLDA | name] | Specifies an esoteric unit name to be used when you allocate a data set in an EXEC and the unit parameter is omitted If not specified, the default shown is used. |
WARNLVL1=[60 | nn] | Specifies a preliminary percentage of EXECs in a queue that, when met, causes a warning message (EM6100W) to be issued Valid values range from 0% to 99%. The default is 60%. Use this threshold to set the first percentage that triggers sending a warning message. |
WARNLVL2=[75 | nn] | Specifies a secondary percentage of EXECs in a queue that, when met, causes a warning message (EM6100W) to be issued Valid values range from 0% to 99%. The default is 75%. Use this threshold to set a second percentage that triggers sending a warning message. |