EXEC Parameters panel

Use the EXEC Parameters panel to view or modify values that determine how individual EXECs execute in your system. The following figure shows an example of the panel.

BMC Software ---------------- EXEC Parameters -----------------   BMC AMI OpsA
COMMAND ===>                                                 TGT --- BBSYSA
                                                             DATE --- YY/MM/DD
                                                             TIME --- 09:30:55
              Member         Current
TIMEXLIM ===>        1             0 Maximum CPU time limit for an EXEC
PEREXLIM ===>        1             0 Maximum CPU percentage usage for an EXEC
TSOTIME ===>        1          1000 Timeout value for attached TSO commands
ELAPSLIM ===>        0             0 Maximum elapsed time limit for an EXEC
UCPARMS ===> YES           NO        Translate EXEC parms to UPPERCASE
AUDITMSG ===> YES           YES       Write JRNL msg for BLDL and submit EXEC
AUDITEXE ===> NO            NO        Write JRNL msg for EXEC Start and End
OSPINUM ===>        0             2 Maximum # of OSPI ACBs
OSPIPRFX ===> OSPI          JO62      4 character OSPI ACB prefix
UNITNAME ===> SYSALLDA      SYSALLDA UNITNAME used for allocating a dataset
PREFIX   ===>               JO71      Prefix used for allocation a dataset
SUBXAUTH ===> DEFER         DEFER     RACF/JOBNAME/DEFER - IMFSUBEX security
APIAUTH ===> RACF          RACF      ORIGIN/RACF - Userid for MVAPI Execs
CICSECID ===> ORIGIN        ORIGIN    ORIGIN/RACF - Userid for CICS Commands
RESAUTH ===> ORIGIN        ORIGIN    ORIGIN/RACF - Userid for Sysprog Cmds
EXEC     ===>                         (Enter ? to see high priority EXECs)
Press END to save changes, CANCEL to cancel changes

Use this panel to continue setting parameters for how single EXECs execute on the system. As on the EXEC Thresholds panel, this panel provides two columns of data:

on the left, the value of the parameters in the AAOEXPxx member for the target BBI-SS PAS
You can enter your modifications on this side of the panel.
on the right, the value of the parameters that are currently in effect for the target BBI-SS PAS; these values cannot be edited

From this panel, you can specify a question mark ( ?) in the EXEC ===> field to display another panel where you can specify the names of EXECs that will always execute on High priority threads.

Refer to Setting-priority-EXECs for more information about specifying EXEC names for high-priority queuing.

EXEC Parameters panel fields

The following table describes the fields on the EXEC Parameters panel:

Field name	Description
TIMEXLIM	is the maximum CPU time limit allowed for an EXEC to use while executing Valid values range from 0 to 9999 and the default is 0. Set this parameter to ensure that any EXEC does not execute limitlessly.
PEREXLIM	is the maximum CPU percentage usage that is allowed for an EXEC to use while executing Valid values range from 0 to 99 and the default is 0. Set this parameter to ensure that any EXEC does not use a disproportionate amount of the CPU time.
TSOTIME	is the time-out value (in seconds) for attached TSO commands Valid values range from 0 to 9999 and the default is 1200. Set this parameter to limit the amount of time that a TSO command associated with an EXEC can use.
ELAPSIM	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.
UCPARMS	specifies that parameters passed to an EXEC must be converted to uppercase characters Valid values are YES and NO and the default is YES. All CLIST EXECs require uppercase characters for parameters.
AUDITMSG	specifies whether you want to record in the BBI-SS PAS Journal all occurrences of BLDLs against the SYSPROC data set and all user-initiated EXEC requests Valid values are YES and NO and the default is YES.
AUDITEXE	specifies whether you want to record in the BBI-SS PAS Journal audit messages indicating when EXECs start and end Valid values are YES and NO and the default is NO.
OSPINUM	specifies the maximum number of OSPI ACBs that is allowed Valid values range from 0 to 999 and the default is 0.
OSPIPRFX	specifies the default four-character OSPI ACB prefix Valid values are any four-character string and the default is OSPI.
UNITNAME	is the default UNITNAME that is used for allocating a data set Valid values are any eight-character string and the default is SYSALLDA.
PREFIX	is the prefix that is used for allocating a data set in an EXEC if the data set name is not enclosed in quotation marks Valid values are any seven-character string and the default is blank, which refers to the subsystem ID.
SUBXAUTH	specifies one of the following names: DEFER: defers the use of the job name or user ID for the security check to the batch job RACF: uses the RACF user ID for all batch job security checks USER ID: uses the user ID for all batch job security checks JOBNAME: uses the job name for all batch job security checks The default is DEFER.
APIAUTH	specifies the user ID to be used for MV API calls issued from EXECs with IMFEXEC MV commands Default value is RACF; valid values are as follows: ORIGIN specifies that the EXEC origin is used as user ID for MV API call. 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. For ALERT escalation-initiated EXECs, the origin is the jobname of the BBI-SS PAS. RACF the user ID associated with the BBI-SS PAS is used for MV API calls. Note This parameter applies only when you are using the IMFEXEC MV API (IMFEXEC MV commands) and does not apply to the BMC AMI Ops Extended API (IMFEXEC MVX commands).
CICSECID	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 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.
RESAUTH	specifies the user ID that will be used when SYSPROG Services are invoked from BMC AMI Ops Automation EXECs 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 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.
EXEC	enables you to display another panel where you can define the names of EXECs that will always run on High priority threads Refer to Setting-priority-EXECs for more information about this panel.

EXEC Parameters panel

EXEC Parameters panel fields

On this page