BBPARM member AAOGME00 parameters
- Identify which GME nodes receive messages from and send messages to BMC AMI Ops Automation
- Define the local GME node
- Control which instrumentation events are traced
Note
This member supports system variables substitution. For more information, see System variables substitution in parameter library members.
The following table lists the parameters for AAOGME00.
Parameter | Description |
---|---|
CONAUDIT=[YES| NO] | Optional parameter that activates or deactivates WTO for messages that indicate cell connection status Specifying YES causes the following messages to be issued as a single multiline WTO in addition to Journal messages:
The default is NO. |
DEBUGMSG=[YES | NO] | Optional parameter that specifies whether to display GME debug messages in the BBI Journal and in WTO format Valid values are YES and NO. The default value is NO. |
EVENTS=[YES | NO] | Optional for the Server BIM connection that specifies whether the connection sends incoming events to the Rule Processor Valid values are YES and NO. The default is YES. If you specify NO, there will be no BAROC events sent sent to the Rule Processor to drive BRC initiated Rules. This parameter is valid only on the server definition that is the TGTIP statement for the HOSTNAME definition. |
EXEC=[YES | NO ] | Optional parameter that specifies whether to allow the launching of EXECs from a BMC Impact Manager cell to run in the BMC AMI Ops Automation PAS. The default is YES. |
GMEACT=[YES | NO] | When used with the RESET PARM AAOGMEnn, RESYNC|RECYCLE command, activates or deactivates the GME facility Valid values are YES and NO. The default value is NO. |
HOSTNAME=[subsystem_ID_of_the BBI-SS_PAS] | Optional parameter that specifies the name of the local GME node and is used to identify this node to other nodes The default value is the SSID of the BBI-SS PAS. The value can consist of numeric and alphabetic characters, underscores (_), and periods (.), but the name must begin with an alphabetic character. The value cannot contain blanks and the maximum length is 48 characters. |
MVE_LINK=HOST:PORT | Optional parameter that specifies the host name where the MainView Explorer server is running and the port it is listening on The default is the IP address where BMC AMI Ops Automation is running and port 3940. You can specify the HOST address as a DNS name or an IP address. If HOST is specified, you must also specify the PORT. Valid values can be 3- to 48-characters in length. This information is used in the mv _ mve_hostand mv_mve_port slots of the BRC events. |
TGTBIMCF =[dataSet Name] | When defining BMC Impact Manager connections, is a required parameter that specifies the data set name of the BMC Impact Manager configuration file The maximum length is 44 characters; do not use quotation marks. For more information about how to specify this parameter when configuring BMC AMI Ops Automation to BMC Impact Manager, see Establishing a connection to a BMC Event Manager and see Steps 6 and 7. (PTF BQO3954 applied) |
TGTHB=[0 | nnn ] | Specifies the heartbeat interval of the remote GME in minutes and if this amount of time passes without any messages being received, the local node closes the connection Valid values are 0-999. The default value is 0, which disables the connection checking. This parameter is not applicable for connections to BMC Impact Manager. |
TGTIP=[networkAddress] | Required parameter for BMC Impact Manager connections where you specify the BMC Impact Manager cell name that is also specified in the BIM server directory data set. The BIM server directory data set is specified by the ServerDirectoryName= parameter in the BMC Impact Manager configuration file. For more information. see 2022-08-15_00-47-39_Configuring BMC II for z/OS. The cell name specified both here and in the BMC Impact Manager server directory data set must be specified in uppercase even though the actual cell name may contain mixed case characters. BMC AMI Ops Automation must be defined as a target when using BMC Impact Manager connections. This means that a TGTIP=xxxx,TGTBIMCF=yyyy specification is required for BMC Impact Manager connections; xxxx must be the same value that the HOSTNAME= parameter is using. For more information about this parameter when configuring BMC AMI Ops Automation to BMC Impact Manager, see Establishing a connection to a BMC Event Manager and see Steps 6 and 7. (PTF BQO3954 applied) |
TGTMXMSL=[32768 | nnnnn ] | Optional parameter that specifies the maximum message length accepted from the remote GME node Valid values are 0-32768. The default value is 32768. This parameter is not applicable for connections to BMC Impact Manager. |
TGTNAME=[name] | Is a 1 to 16 character name assigned to a BMC Impact Manager (BMC IM) connection The TGTNAME can be shared by multiple BMC IM connections and is used by BMC AMI Ops Automation Rules or EXECs to send events or publish ALERTs to a specific target system. In Rules and EXECs, you may use wildcards when specifying the target name for events and ALERTs. There is no default value. |
TGTRTC=[9999 | nnnn ] | Is the number of allowed connection retries if a failure occurs Valid values are 0-9999. A value of 0 disables the reconnection processing. A value of 9999 instructs GME to attempt to reconnect until it is successful. The default value is 9999. Certain platforms have a TCP/IP parameter that delays the closing of TCP/IP connections. In Solaris, this parameter is named tcp_close_wait_interval. GME/MVS cannot reconnect while the connection is in this close_wait state, because connectAAO sees it as a duplicate connection. For information regarding this parameter, see your platform-specific documentation. For BMC Impact Manager connections, this parameter affects the initial startup retry attempts. Subsequent retries after a failure do not check this parameter’s setting. |
TGTRTI=[3 | nnn ] | Interval (in minutes) between connection retry attempts Valid values are 0-999. A value of 0 disables the reconnection attempt. The default value is 3. Certain platforms have a TCP/IP parameter that delays the closing of TCP/IP connections. In Solaris, this parameter is named tcp_close_wait_interval. GME/MVS cannot reconnect while the connection is in this close_wait state, because connectAAO sees it as a duplicate connection. For information regarding this parameter, see your platform-specific documentation. |
TGTTYPE=[CELL | ADAPTOR | RESTAPI] | Optional for each BEM connection that specifies whether the ADAPTOR connection is to a BEM cell or to another BMC adapter The following values are valid:
The default value is CELL. The parameter is valid only for TGTIP definitions for the client cell definitions. |
TRACEAPP=ERROR | Minimum severity of application trace records to create Valid values are NONE, ERROR, WARN, INFO, or DEBUG and are specified separately for both the local and remote GME nodes. The default value is ERROR. |
TRACEBUF=[ 50 | nnnnn] | Amount of storage, in thousands of bytes, to allocate for the in-storage wraparound trace buffer The maximum value is 99999. The default value is 50. |
TRACEGME=[NONE| ERROR | WARN | INFO| DEBUG] | Minimum severity of GME trace records to create Valid values are NONE, ERROR, WARN, INFO, or DEBUG and are specified separately for both the local and remote GME nodes. The default value is ERROR. |
TRACELK=[YES | NO ] | Specifies whether to perform a DNS lookup when logging IP addresses in the Trace Table Valid values are YES and NO. Specifying TRACELK=YES may lengthen the response times because a DNS lookup involves a network communication. The default value is NO. |
TRACESEC=[NONE | ERROR | WARN | INFO| DEBUG | Minimum severity of security trace records to create Valid values are NONE, ERROR, WARN, INFO, or DEBUG and are specified separately for both the local and remote GME nodes. The default value is WARN. |
TRACEZN=[LOCAL | GMT] | Time zone to use for time stamps in the Trace Table Valid values are GMT and LOCAL. The default value is LOCAL. |
WTO=[Y | N] | Specifies whether BMC Impact Manager users can issue a write-to-operator message (WTO) through BMC AMI Ops Automation |
Comments
Log in or register to comment.