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:
|
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. |
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 MainView AutoOPERATOR 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 (unless overridden by the command or option that schedules the EXEC) See Setting-priority-EXECs for more information about this panel. |
(PTF BQO3933 applied) EXEC | Enables you to display another panel where you can define the names of EXECs that always run on High priority threads at the defined priority (unless explicitly overridden in the command or option that schedules the EXEC) The optional PRI keyword identifies the execution priority for the EXEC. See Setting-priority-EXECs for more information. |