BBPARM member AAOPRM00 parameters

BBPARM member AAOPRM00 is used by all BMC AMI Ops Automation products as a general purpose parameter member.

Important

This member supports system variables substitution. For more information, see System-variables-substitution-in-parameter-library-members.

The following table lists the parameters for AAOPRM00.

Parameter	Description
AOLOGACT=[NO \| YES]	Specifies whether the actions taken by a Rule will be sent to the Automation Logger application To send all actions taken by a Rule to the Automation Logger application, specify YES. Default value is NO; valid values are YES or NO.
AOLOGEV=[NONE \| ALL \| (event_type_1, event_type_2, ...)]	Specifies one or more types of events that will be sent to the Automation Logger application Default value is NONE; valid values are ALL (all events are logged), ALRM, ALRT, BRC, CICS, CMD, DB2, EOM, EOS, EXT, IMS, JRNL, MQS, NVC, NVM, TIME, TLM, VAR.
AOOPTION=xxx AOOPTION=(xxx,yyy,....zzz)	(optional) 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 Ops Automation components with valid BMC passwords are activated at the time of BBI-SS PAS start up. The format of the statement to activate one component is AOOPTION=xxx To activate more than one component: AOOPTION=(xxx,yyy) For example: AOOPTION=(IAO,CAO) For best results, perform a cold start of the BBI-SS PAS after you make changes to the AOOPTION parameter. The BMC AMI Ops Automation component abbreviations that are valid for this parameter are: ANV - BMC AMI Ops Automation Access NV TSH - BMC AMI Ops Automation TapeSHARE CAO - BMC AMI Ops Automation for CICS IAO - BMC AMI Ops Automation for IMS QAO - BMC AMI Ops Automation for MQ MAO - BMC AMI Ops Automation for z/OS Note You must specify the PRODUCT=AAO parameter in BBPARM member BBISSPxx to be able to activate any BMC AMI Ops Automation component.
AOREPLAY =[NO \| YES]	Specifies whether to send Event Replay records to the Logger where you can review (replay) them at a later time Default value is NO; valid values are YES or NO. This keyword is valid only if AOLOGEV is not set to NONE. Event Replay records will be saved only for the event types specified on the AOLOGEV statement. The MVLOGSS parameter in BBPARM member BBISSP00 specifies the SSID of the Logger for the EMLOG records.
BIIZJRNL=[Y \| N]	Specifies that messages that describe BMC Impact Integration for z/OS product (BiiZ) events are automatically sent to the BBI Journal The default is N (no). Specifying YES means that multiple diagnostic messages are written to the BBI Journal for events and ALERTs that are sent and published to a BMC Impact Manager (BMC IM) cell. The messages show diagnostic information about the event such as target, CLASS, severity, and other event information. It is also possible to write messages to the BBI Journal for individual events or ALERTs by specifying one of the following values: Y (for YES) in the Journal Detail field of the Rule definition JOURNAL(Y) in the following commands: IMFEXEC BIM EVENT AOEXEC ALERT IMFEXEC ALERT Note BMC warns that by setting this parameter to YES that the volume of messages sent to the BBI Journal might be large.
DBCTLCMD=[IMS \| MVS]	When specifying IMS (default value), requires the BMC AMI Ops Automation for IMS product to be active in the PAS, and the PAS is connected to IMS DBCTL With this setting, DBCTL commands (issued from the Command line or from EXECs or Rules) are processed as IMS commands and you do not need to specify a target. Generic DBCTL commands are also supported. You must specify DBCTLCMD=MVS when you want to issue commands to IMS DBCTL and the BMC AMI Ops Automation for IMS product is not active within the PAS. With this setting, DBCTL commands must be issued from EXECs using the IMFEXEC CMD TYPE(IMS) statement and in addition: the DBCTL keyword is required to identify the target commands are issued as MVS commands using the DBCTL command character When issuing DBCTL commands from Rules, you must specify the commands as MVS commands. You can also specify DBCTLCMD=MVS for compatibility with automation written earlier than MainView AutoOPERATOR version 7.2. This setting ensures that responses to IMFEXEC CMD statements are returned to the EXEC in the same format as earlier than version 7.2. You should try to migrate your EXECs to use the current settings as time permits. Note Specifying DBCTLCMD=MVS will disable some product functionality as described in the following list: Commands issued from the Journal command line require a target and their response is returned to the Local Log. Responses to commands issued with IMFEXEC CMD (with response) within an EXEC are returned in a different format. For more information, see Using-advanced-automation-with-BMC-AMI-Ops-Automation. DBCTL commands issued with IMFEXEC CMD requires the use of the DBCTL parameter to specify the target. IMS generic commands issued against DBCTL will fail. Any Rules written with an action to issue DBCTL commands must issue those commands as MVS-type commands with the DBCTL command recognition character.
DBCTLORG=[NO\|YES]	(optional) Specifies whether the Journal logs IMS DBCTL commands with the origin of who issued the commands Valid values are NO and YES: NO: (the default) the Journal logs IMS DBCTL commands with only the origin of the DBCTL job name. YES: the Journal logs IMS DBCTL commands with the origin as the name of the command issuer, in addition to logging the commands with the originating DBCTL job name. For commands that are issued from the User Address Space (UAS), the origin is the TSO user ID. For automation-issued commands, such as Rules and Rule-initiated EXECs, the origin is the event-originating job name. This parameter applies to the following types of IMS DBCTL commands that are: Issued from the Journal Line commands issued from IMS OPERATOR displays Issued by Rules and EXECs Issued from BMC AMI Ops Monitor for IMS views
DZDSN=[VSAM data set name]	Specifies the name of the VSAM data set generated by the BMC product BMC Discovery for z/OS The VSAM data set name contains the Configuration Alias names that are discovered on the z/OS image by the BMC Discovery for z/OS product. The BMC Impact Integration for z/OS product uses these names to populate SHARED variables such as the following where ssssssss resolves to the name of the server address space: QCIA.QSERVER.ssssssss resolves to the configuration item (CI) alias value. QCIN.QSERVER.ssssssss resolves to the CI name which is the same as CI alias. QCIO.QSERVER.ssssssss resolves to the CI object class. The BMC Impact Integration for z/OS product attempts to read the DZDSN value every hour.
HONORMPF=[YES \| NO]	Specifies if the Rules Processor application honors MPF suppression Default is N; valid values are Y(es) or N(o). The HONORMPF parameter setting determines whether messages are handled by the Rule Processor when MPF suppression is active.
IMFDATE	Specifies the format of the IMFDATE variable The following lists shows valid formats and an example of each: YYYY/MM/DD; 2050/10/23 YYYYMMDD; 20501023 DD/MM/YYYY; 23/10/2050 DDMMYYYY; 23102050 MMDDYYYY; 10232050 MM/DD/YYYY; 10/23/2050 MMMDDYYYY; OCT232050 DDMMMYYYY; 23OCT2050
IMFJNUM=[V \| 5]	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.
IMFORGN=[LTERM \| xxxxxxxx]	Specifies that the LOCAL variable IMFORGN is set to the IMS LTERM name for IMS command and response Default is the VTAM node name. Note The value of IMFORGN is sometimes used by security applications to check whether actions that are specified within an EXEC are allowed. Most actions within an EXEC are not individually checked for explicit authorization. Note that there are some exceptions such as SYSPROG Services commands, which are checked for proper authority before the SYSPROG Services commands can be issued. BMC recommends that you explicitly define the users who have authorization to schedule EXECs.
IMSAUTH=[NONE\|USER]	(optional) Specifies whether the User ID should be passed to IMS along with all IMS commands issued from BMC AMI Ops Automation Valid values are as follows: NONE: (default) the user ID is not passed with IMS commands USER: the user ID will be passed to IMS Standard IMS command security rules will be applied. For commands that are issued from the User Address Space (UAS), the user ID is the issuer of the command. For commands that are issued from automation such as Rules and EXECs, the user ID value is the user ID associated with the BMC AMI Ops Automation PAS. This parameter applies to: Type-2 (IMSplex) commands Type -1 for IMS DBCTL with DBCTLCMD=MVS commands issued from the Journal line commands from IMS OPERATOR displays commands issued by Rules and EXECs This parameter does not apply to IMS commands: Type-1 for IMS DBCTL with DBCTLCMD=IMS Type-1 for IMS DB/DC region Note This parameter is not related to BMC AMI Ops windows-mode or full-screen mode security.
IMSCMDCN=[NO \| YES]	Specifies whether a confirmation panel is displayed when an IMS action command is manually entered from BMC AMI Ops Automation views or from the Journal Valid values are NO and YES. NO: (default) no confirmation panel is displayed YES: specifies that a confirmation panel is displayed for all IMS action commands that are manually issued from BMC AMI Ops Automation views or from the Journal. A confirmation panel is displayed for both Type-1 and Type-2 commands. A confirmation panel is not displayed for non-action commands such as /DISPLAY and QUERY or for commands issued by automation (such as Rules or EXECs). You must ensure that the User Address Space (UAS) is locally connected to the BMC AMI Ops Automation PAS where this parameter is specified.
IMSPLAUD=[NO \| YES]	Specifies whether BMC AMI Ops Automation and BMC AMI Ops Monitor for IMS issue audit messages to the Journal for all IMSplex (type-2) commands. Valid values are NO and YES: NO: (the default) audit messages are not issued. YES: audit messages, containing the user ID, are issued to the Journal for all IMSplex commands. For commands that originate from the user address space (UAS), the user ID is the issuer of the command. For commands that BMC AMI Ops Automation automation (such as Rules and EXECs) issues, the user ID is the BMC AMI Ops Automation PAS user ID.
IMSOMEX=[NO \| YES]	(optional) Specifies whether this PAS should receive IMSplex (type-2) commands from the BMC AMI Ops Automation IMS OM Input user exit. Valid values are NO and YES: NO: The BMC AMI Ops Automation IMS OM Input user exit does not broadcast IMS Type-2 commands to this PAS. IMP event type Rules do not fire. YES: (the default) when the BMC AMI Ops Automation for IMS product is active, the BMC AMI Ops Automation IMS OM Input user exit broadcasts IMS Type-2 commands to this PAS and IMP event type Rules will capture and automate these commands.
IMSPLTIM=[30\| 5 - 9999]]	Specifies a user-defined timeout limit for waiting for a response from IMSplex commands that are issued from the Journal The default timeout limit is 30 seconds. Possible values range from 5 to 9999 seconds. The IMSplex command timeout limit represents the maximum time to wait for a response from IMS. If a response is received from all IMS regions of the IMSplex before the timeout is reached, the response is displayed and waiting is terminated. If a response is not received from all IMS regions of the IMSplex before the timeout is reached, a partial response is displayed and the IMS Operations Manager terminates execution of the IMSplex command.
IMSROUTE=[ALL\| LOCAL]	Specifies the default routing for IMSplex commands issued from the BMC AMI Ops Automation Journal, Rules, or EXECs Possible values are ALL and LOCAL. Default is ALL. ALL: IMSplex commands are sent to all IMS regions of the IMSplex. LOCAL: IMSplex commands, issued without a ROUTE() keyword are sent only to the IMS region connected to the BMC AMI Ops Automation PAS. This parameter does not apply when: the ROUTE() parameter is specified with an IMSplex command The IMSPLEX() parameter on an IMSplex command from EXEC specifies IMSplex that does not include the IMS region connected to the BMC AMI Ops Automation PAS.
IMSMSTIM=[5\| 1 - 999]	(optional) Specifies the maximum time to wait between receiving segments of IMS multisegment messages Arrival of the final segment terminates the wait and the message is processed by the Rules processor. If the time is exceeded without receiving a final segment from IMS, the wait is terminated and any future segments are ignored. The delay may occur due to system heavy workloads, a lower dispatching priority of the IMS issuing the message, or other IMS processing. The default timeout limit is 5 seconds. Possible values range from 1 to 999 seconds. Specify this parameter when: Rules automation is not processing the complete IMS multi-segment message(s). For example, if only the first message segment is logged on the Journal. EXECs do not receive the complete IMS command response and IMFCC is set to 8. Note Increasing the default value might create a delay of Rules-based automation for IMS multisegment messages.
IMSSHTIM=[2\| 1 - 999]	(optional) Specifies the internal time to wait for termination of the BMC AMI Ops Automation tasks in the IMS control region address space during IMS shutdown. The default timeout limit is 2 seconds. Possible values range from 1 to 999 seconds. Specify this parameter only if your IMS control region takes unusually long to terminate or frequently experiences abend sA03 at shutdown. Note Increasing the default value reduces the possibility of sA03 abends, but might delay the time it takes for IMS to shut down.
MAXDLYQ=[100\| nnn]	(optional) Specifies the maximum concurrent number of delayed requests from Rules A delayed request can be specified for a command or message. The default is 100; 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 specified in the BBPARM member BBISSPxx member, whichever is lower. 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.
MPFFILTR=(AUTO=YES \| NO \| token,SUP=YES \| NO)	Specifies whether BMC AMI Ops Automation checks WTOs for the MPF settings for the AUTO and SUP keywords Note This parameter cannot be used when HONORMPF is set to HONORMPF=YES. For information about how this parameter is set and how it affects automating WTOs, refer to Implementing-support-for-MPF.
MQALTUSR=[RACF \| user ID]	Specifies an AlternateUserid to be specified when issuing MQSC or PCF MQ commands from BMC AMI Ops Automation The user ID is used when MQ commands are issued from an EXEC or from a Rule. There is no default; valid values are as follows: RACF specifies that the security ID of the BBI-SS PAS is used as the AlternateUserid for commands. user ID specifies that a valid user ID is used as the AlternateUserid. This global parameter can be overridden with the ALTUSER() \| AU() parameter of the IMFEXEC CMD TYPE(MQS) command or as an action from a MQ initiated Rule. When you use this parameter the MQ PUT1 options will include MQOO_ALTERNATE_USER_AUTHORITY, MQPMO_DEFAULT_CONTEXT and MQPMO_ALTERNATE_USER_AUTHORITY and the AlternateUserid will be placed in the object descriptor. See Automating-IBM-MQ-events for more information about the IMFEXEC CMD TYPE(MQS) and issuing MQ commands from Rules.
MQAUPRMS=[Y \| N]	Specifies whether individual MQSC or PCF MQ commands that are issued from EXECs or Rules can use the ALTUSER parameter to override the global parameter MQALTUSR (when specified) and specify an AlternateUserid When no value is specified for the MQALTUSR parameter, this parameter allows or denies the use of AlternateUserid for MQ command. Default value is NO, which means that the ALTUSER value is ignored.
MQEV=[YES \| NO\| or any combination of SLIPRFMCVBX]	Specifies that BMC AMI Ops Automation for MQ should automatically enable instrumentation events for a queue manager during connection if it is not already enabled You can specify that all the events are enabled, that none of the events are enabled, or that selected event types are enabled. When you specify multiple event types, you must code them consecutively, without using blanks or commas (does not apply if you are specifying Y or N). Valid values are as follows: N: do not enable any events Y: enable all events S: enable start/stop (strstpev) events L: enable local (localev) events I: enable inhibit (inhibtev) events P: enable performance (perfmev) events R: enable remote (remoteev) events F: enable configuration (configev) events M: enable command (cmdev) events C: enable channel (chlev) events V: enable ssl (sslev) events B: enable bridge (bridgeev) events X: enable non-display command events (CMDEV(NODISPLAY)) The default value is NO.
MQEVLPRC= xxxxxxxx	Specifies the name of the IBM MQ Event Listener PROC Do not use this parameter if the IBM MQ Event Listener is not required. For more information about the IBM MQ Event Listener and coexistence of BMC AMI Ops Automation and other BMC Software products that require the IBM MQ event queues, see Automating-IBM-MQ-events.
MQGINHIB=[ xxxxxxxx \| JRNL]	Specifies the action BMC AMI Ops Automation should take when BMC AMI Ops Automation attempts to listen to a queue which is defined as GET(DISABLED) Possible settings are JRNL: Issue a message to the BBI Journal stating that BMC AMI Ops Automation cannot listen to the queue. WTO: Issue a write-to-operator (WTO) message stating that BMC AMI Ops Automation cannot listen to the queue. IGNORE: Take no action. ALTER: Alter the queue to GET(ENABLED). The default value is JRNL.
MQNSHARE=[ xxxxxxxx \| JRNL]	Specifies the action BMC AMI Ops Automation should take when BMC AMI Ops Automation attempts to listen to a queue which is defined as NOSHARE. Possible settings are JRNL: issue a message to the BBI Journal stating that BMC AMI Ops Automation cannot listen to the queue. WTO: issue a write-to-operator (WTO) message stating that BMC AMI Ops Automation cannot listen to the queue. IGNORE: take no action. ALTER: alter the queue to share. The default value is JRNL.
MSGJOBNM=[ACTUAL\| ORIGIN]	Specifies how BMC AMI Ops Automation 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 valid: 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. The default value is ORIGIN.
MVIMSDB=[MSG\|CMD]	(optional) Specifies whether IMS DBCTL commands issued from BMC AMI Ops Monitor for IMS Online windows mode views will result in a Journal message or actual command. The following values are valid: MSG: IMS DBCTL commands from BMC AMI Ops Monitor for IMS Online views sends the BBFPAC0XI message to the Journal. You must enable the RULIPX00 Rule set to detect this message and issue the IMS DBCTL command as an MVS command. CMD: BMC AMI Ops Automation issues the actual IMS DBCTL commands when they are entered from BMC AMI Ops Monitor for IMS Online views. All applicable AAOPRMxx parameters (such as DBCTLCMD) will apply. Note Changing the value of the MVIMSDB parameter requires that you restart the IMS DBCTL region. The default value is MSG.
QALIAS=[Y \| N]	Specifies whether BMC AMI Ops Automation for MQ should open and listen for messages on QALIAS type queues Note that if you specify an alias queue name in BBPARM AAOMQL00, in addition to specifying a base queue, any Rules that you have written for the same message for the base queue might also fire for the alias queue. For example, if the selection criteria for a Rule for messages going to the base queue does not specifically contain the queue name then the Rule might fire twice; once for the base queue and once for the alias queue.
RTCSCMD=MVS_startCommand_for _RTCS	Specifies the MVS command start command for BMC Runtime Component System (RTCS) This parameter requires that you have the BMC AMI Ops Automation for z/OS product component installed in the BBI-SS PAS. For example: RTCSCMD=S OSZINIT.RTCS Do not use quotes and the length of the command is limited to column 72. This line does not support comments or continuations. When BMC AMI Ops Automation for z/OS PAS is started and the RTCSCMD parameter is specified, BMC AMI Ops Automation tests for the presence of RTCS. If RTCS is absent, BMC AMI Ops Automation issues the MVS command to start RTCS specified with this parameter.
RULEPROT	Activates serialization on a Rule when it is edited, preventing multiple users from updating the same Rule, in the same BBI-SS PAS at the same time When the parameter is not specified, the default is NO. The following values are valid: NO: no serialization is performed when a Rule is edited YES: serialization is performed within the scope of each PAS to ensure only one user is updating a Rule in that PAS as the same time
RULESAVE	Specifies what happens when a Rule Set is saved from the Rule Processor Detail Control panel Valid options are as follows: FIRST (default): the Rule Set is automatically saved in the first data set of the BBIPARM DD concatenation, regardless of where it was read from ORIGINAL: the Rule Set is automatically saved in the data set that it was originally read from in the BBIPARM DD concatenation PROMPT: specify the data set (FIRST or ORIGINAL) to which to save the Rule Set
RULESCAN=[F\|A\|I]	Specifies the automation strategy of F (FIRST), A (ALL), or I (INDIVIDUAL) to determine how Rule Sets and Rules are searched to match events F\|FIRST: indicates only the first Rule with matching selection criteria is fired. A\|ALL: indicates Rules with matching selection criteria are fired. I\|INDIVIDUAL: indicates that each Rule Set can have its own (individual) automation strategy. Each Rule Set can be set with First, or All. The automation strategy specified here is used when the BBI-SS PAS is either warm or cold started.
RULESET= xx or RULESET=( xx,yy,...,zz)	Specifies one or more RULESETs to become active upon initialization of the BBI-SS PAS Format of the statement is RULESET= xx for one set, or RULESET= (xx,yy,...,zz ) for multiple sets. The two-character code is appended to AAORUL. You also can use the 5-character suffix (where the prefix is RUL); for example, RULESET=RUL xxxxx or RULESET=(RULxxxxx, RULyyyyy, RULzzzzz ). You can specify a long list of Rule Set names by continuing to the next line. Separate each Rule Set name with a comma.
(BMC.AMIOPS.SPE2404) RULETEST=[Y \| N]	Specifies whether to place all currently enabled Rules in a PAS into test mode When you do not specify a value, the default is NO. The following values are valid: NO: does not place all enabled Rules in the PAS into test mode (default) YES: places all enabled Rules in the PAS into test mode Rules fired in test mode do not perform any action specifications. If the Rule has an EXEC associated with it, the EXEC is scheduled and variable IMFRLSTA is set to TEST. When Rules fire in test mode, messages about the actions the Rule would take are written to the Automation Logger. The message IDs are prefixed with DX. For more information about messages, enter the command HELPMSG messageID* on the COMMAND line.
SPLXVARS=[Y\| N]	Specifies that the BBI-SS PAS supports sysplex variables Default values is N; valid values are Y(yes) or N(no).
SPLXPREF=[1- to 16-character_userSpecifiedPrefix]	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. You can specify only one prefix for the BMC AMI Ops Automation PAS and, all of the BMC AMI Ops Automation PASs that use the same SYSPLEX variables must also use the same prefix. If you use the default setting, an example of a sysplex variable name would be AOSPLX_DB2STATUS.
SPLXSTR=[structure name]	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 is MVAO_BMCAB.
SUPREPLY=[NO \| YES]	Suppresses commands that are issued as replies to WTORs (write-to-operator with reply) Specifying YES changes the text of the command issued by a terminal session (TS) user or EXEC. For example, if an EXEC issues the command R 33,XYZ the BBI-SS PAS Journal shows the command as R 33,SUPPRESSED Therefore, specify YES when you want to conceal text in the BBI-SS PAS Journal (such as the use of a password). The local Journal shows the original message. The default is NO.
UCCICTRN=[Y \| N]	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: specifies that 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 Ops Automation PAS.
WTOINTRM	Specifies that WTOs captured during brief BMC AMI Ops Automation outages are available as HWTO events to the Rule Processor This option is ignored if the BMC AMI Ops Automation 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 Ops Automation PAS.

BBPARM member AAOPRM00 parameters

On this page