What parameter members have changed

The following table lists the new or changed parameters, (including the default setting, and a brief description) that are included in MainView AutoOPERATOR version 8.1. You can locate the complete definition and additional usage documentation in this manual for each of the parameters in either of the following chapters:

Note

The parameters for BBPARM member AAOPLX00 are not available for editing from the Dynamic Parameter Manager. The parameters in this member support the Rules Management application, which requires a COLD start to take effect.

Table 1. Added or changed parameters for MainView AutoOPERATOR version 8.1

BBPARM member name

Parameter

Brief description

AAOARP00

AROPTS=[TOM| ELU | RLU]

specifies that windows mode Automation Reporter will collect data about TOMEXECs (TOM), EXECs (ELU) or Rules (RLU)

When you specify one of the following options:

  • TOM: collects data about TOMEXEC EXECs

  • ELU: collects data about EXECs

  • RLU: collects data about Rules

    For the ELU and RLU options, you must define a CASPERM registry. For more information, see the MainView Administration Guide. If you do not have a CASPERM registry defined, you will get the AAOR0720I or the AAOR0820I messages

  • ALL: all collectors will collect data (but does not include the ELU or RLU options)

AAOEXP00

MSGID

updates the TSO user profile MainView AutoOPERATOR uses to turn on (and off) the TSO MSGID option

The MSGID parameter defaults to MSGID=Y, which means that if you used a TSO Segment in an external security manager (ESM) with PROFILE NOMSGID, you will find TSO messages now use the MSGID as the prefix. This might impact Rules automation if JRNL event Rules were written for messages that do not use MSGID as the prefix.

AAOPLX00

AO_NAME

specifies the name to identify this PAS within the AOPlex

AOPLEX_NAME

specifies the name of the AOPlex to which this PAS belongs

AOPLEX_XCF_GROUP

specifies the name of the XCF group that the AOPlex will use to communicate

REGISTRY_DSN

specifies the data set name of the linear VSAM data set allocated for use by this AOPlex

REGISTRY_WARNHWM

specifies the Registry high-water-mark percentage warning message threshold

USAGE_MODE_RULES

specifies to the PAS how to use the registry

AGSLOG

specifies whether the MainView AutoOPERATOR Generalized Services (AGS) messages are sent to a logger

AGSLOG_FAILOVER

specifies what happens to AGS messages when AGSLOG=YES, FORCEWTO=NO, and AGSJRNL=NO are specified and the logger is not available

FORCEWTO

specifies whether AGS product messages are sent to the PAS JES job log

AGSJRNL

specifies whether AGS product messages are sent to the BBI-SS journal

FORCE_CLASSIC_RSNAMES

specifies whether Rule Sets created in the registry by the user address space (UAS) follow the classic Rule Set naming that requires the name to start with RUL or AAORUL

AUDIT_STARTUP_RULESETS

causes message AGSIA4050I to be generated to the PAS syslog during a PAS COLD start to list the rulesets that the PAS will use and is similar to the PROCESS LIST= parameter in BBPARM member AOPRMxx

AAOPRM00

MAXDLYQ

The default setting for this parameter has been changed from 100 to 999.

MSGJOBNM

specifies how MainView AutoOPERATOR should derive batch, Started Task, and TSO job names for MSG events

The default for this option is changed in this version from ACTUAL to ORIGIN.

You should consider the impact of this change Rules might be affected. MSG event Rules that report the origin of a message as CONSOLE might suddenly find that value is changed and your automation might not perform as expected. If you are uncertain about the impact of this change, you should ensure that this parameter is specified as MSGJOBNM=ACTUAL.

RTCSCMD=MVS_startCommand_for _RTCS

specifies the MVS command start command for BMC Runtime Component System (RTCS)

UCCICTRN

specifies whether CICSTRAN transaction parameters will be translated to uppercase

WTOEARLY

specifies that early WTOs, captured by the QAOCNZ15 utility, are available as HWTO events to the Rule Processor

WTOINTRM

specifies that WTOs, captured during brief MainView AutoOPERATOR outages, are available as HWTO events to the Rule Processor

BBISSP00

DYNEXITS

specifies a one-character value to indicate which dynamic exits for MainView AutoOPERATOR for z/OS should be added and activated.

These exits are required for the EOS and TLM event type for Rules.

This parameter uses the following syntax:

DYNEXITS=[Y|N|E|T]

The default is Y.

  • Y: specifies all exits should be added and activated

  • N: specifies no exits should be added

  • E: specifies all exits should be added but only exits required for event type EOS should be activated

  • T: specifies all exits should be added but only exits required for event type TLM should be activated

You can use the command .D EXIT to display information about which exits are added and whether they are active or inactive.

Was this page helpful? Yes No Submitting... Thank you

Comments