General Parameters
When you use the Select line command to select General Parameters, the following panel is displayed.
COMMAND ===> TGT --- BBSYSA
DATE --- YY/MM/DD
Member Current TIME --- 08:47:29
AOOPTION ===> (Enter ? for Option list)
SUPREPLY ===> NO Suppress Replies to WTO/R
IMFJNUM ===> V V IMFJNUM variable length
MAXDLYQ ===> 100 Max queued DELAYed Requests
MSGJOBNM ===> ORIGIN Origin of job name
SPLXVARS ===> N Sysplex variables (Y/N)
SPLXPREF ===> AOSPLX_ Sysplex variables prefix
SPLXSTR ===> BMCAB Coupling Fac structure name
TOMAUDIT ===> N N Write JRNL msg for TOM events
UCCICTRN ===> Y Uppercase CICSTRAN parms (Y/N)
WTOEARLY ===> N Early (IPL) WTOs
WTOINTRM ===> Y Y Interim WTOs
Descriptions of the fields on this panel follow:
Field name | Description |
|---|---|
AOOPTION | Allows you to limit the licensed BMC AMI Ops Automation product components that are started during BBI-SS PAS initialization When this parameter is not specified, all BMC AMI OpsA components with valid BMC passwords are activated at the time of BBI-SS PAS startup. Enter a '?' next to the keyword to display a list of the current options that you can edit. Default value is blank; valid values are ANV, TSH, CAO, IAO, SHA, QAO, MAO. For example, for you might enter all of your BMC passwords into a data set that is used by all your PASes. However, you don't want all your PASes to activate all the BMC AMI OpsA product components. In this case, you can use AOOPTION to prevent differentBMC AMI OpsA product components from activating in specific PASes. For best results, perform a cold start of the BBI-SS PAS after you make changes to the AOOPTION parameter. |
SUPREPLY | Suppresses commands that are sent as replies to WTOR in the BBI Journal Default value is NO; valid values are YES or NO. Specify YES to have commands suppressed from view in the BBI Journal; for example, if you specify YES, and an EXEC issues a 'R 33,XYZ', the BBI Journal displays this reply as 'R 33,*SUPPRESSED*'. Note that only the local journal will still display the command as 'R 33,XYZ'. |
IMFJNUM | Specifies whether the variable IMFJNUM will be 5 digits in length with leading zeros or a variable length number without leading zeros You must specify IMFJNUM=V to support JES job numbers greater than 99,999. Default value is V; possible values are 5 or V. Refer to IMFJNUM-option-and-seven-digit-JES-job-numbers for more information. |
MAXDLYQ | Specifies the maximum concurrent number of delayed requests from Rules The default is 999; valid values are 0 to 999. Specifying zero means no maximum is set. The maximum value is 999 or half the value of the MAXPQE parameter that is specified in the BBPARM member BBISSPxx member, whichever value is lower. A delayed request may be for a command or message. When the number of concurrent DELAYED requests reaches 60 percent of the MAXDLYQ threshold, the following message is issued: DY6160W xxxxxx Delayed Requests queued When the number of concurrent DELAYED requests reaches 75 percent of the MAXDLYQ threshold, the following message is issued: DY6175W xxxxxx Delayed Requests queued If the MAXDLYQ value is reached, no additional requests can be queued until the number drops below the specified threshold and the following message is issued: DY6199E Maximum Delay Request queued The MAXDLYQ threshold calculations are re-adjusted when the AAOPRMxx member is reset. The threshold is calculated every time a DELAYED request is queued. Delayed actions are not retained over a warm or cold restart of the BBI-SS PAS. Therefore if outstanding delayed actions exist when the BBI-SS PAS is restarted, those delayed actions are lost and are not re-queued when the BBI-SS PAS restarts. You can use the BBI command .DISPLAY DLY before you restart the BBI-SS PAS to review any delayed actions that have not yet been completed. Determine whether you should delay restarting the BBI-SS PAS or, restart the BBI-SS PAS but note that you need to reissue the delayed actions when the BBI-SS PAS restarts. |
MSGJOBNM | Specifies how BMC AMI OpsA should derive batch, Started Task, and TSO job names for MSG events The job name or the IMFOJOB variable can be used in the Rule Processor Selection Criteria panel while defining Rules. The following values are possible: ACTUAL: Use the job name as it is derived from the address space that creates the event. There are situations where this value might not match the address space that initiated the event (WTO). For example some JES3 messages will have a value of 'CONSOLE'. ORIGIN: Use the job name as it is derived from the MVS control block (WQE). Specifying ORIGIN would result in a more accurate name of the issuer of the WTO. ORIGIN is the default value. |
SPLXVARS | Specifies that the BBI-SS PAS supports sysplex variables Default value is N; valid values are Y(yes) or N(no). |
SPLXPREF | Specifies the prefix that denotes that the SHARED variable name is a sysplex variable Default value is AOSPLX_; valid values are 1 to 16 alphanumeric characters long. If you use the default setting, an example of a sysplex variable name would be AOSPLX_DB2STATUS |
SPLXSTR | Specifies the name of the XCF Structure that stores the sysplex variables The XCF Structure resides in a Coupling Facility. Valid values can be 1 to 8 alphanumeric characters long. SPLXSTR uses the default value of the XCFGROUP option in BBISSPxx. BMC recommends that you avoid coding user-specified values for the XCFGROUP= and SPLXSTR= parameters and use the default values. The default value for XCFGROUP= is BMCAB and the default XCF Structure name will be MVAO_BMCAB. |
UCCICTRN | Specifies whether CICSTRAN transaction parameters will be translated to uppercase This specification applies to CICSTRAN when executed from anywhere except the TS Command Execution Application (which supports mixed case specification of parameters). The following values are valid: N: specifies that CICSTRAN parameters are not translated to uppercase Y: specifiesthat CICSTRAN parameters are translated to uppercase The default value is Y. |
WTOEARLY | Specifies that early WTOs, captured by the QAOCNZ15 utility, are available as HWTO events to the Rule Processor This parameter is valid only when the BMC AMI Ops Automation for Data Centers solution is active in the BMC AMI OpsA BBI-SS PAS. |
WTOINTRM | Specifies that WTOs captured during brief BMC AMI OpsA outages are available as HWTO events to the Rule Processor This option is ignored if the BMC AMI OpsA BBI-SS PAS abends or does not terminate normally. This parameter is valid only when the BMC AMI Ops Automation for Data Centers solution is active in the BMC AMI OpsA BBI-SS PAS. |
Related topic