AOEXEC BIM

This command uses the AOEXEC BIM EVENT function in a REXX EXEC to to send an event to a BMC Impact Manager (BIM) cell(s).

Command	Parameters
BIM EVENT	[CELLNAME( )] [CLASS( )] [JOURNAL] MSG( ) [SEVERITY( )] [SLOTSTEM( )] [SS \| SSID(subsystemIdentifier)] AOOPTION \| AOOPT(ANV, CAO, IAO, IIZ, MAO, QAO, or TSH) [TGTSS(targetSubsystemIdentifier)] [TGTJNT()] [UEID( )]

Parameter	Function	Notes
CELLName	Specifies the name of BIM cell or other BMC product with a cell adaptor	The name must be the same name that is specified with the TGTIP= parameter in BBPARM member AAOGMExx and the IIMDIRxx member. If you do not specify a value for the CELLName parameter, the command sends the event to all cells.
CLASS	Specifies the class for an event that is sent from a BMC AMI Ops Automation EXEC	The default class is MV_EVENT_EXEC. The MV_EVENT_EXEC class contains the following slots: mv_exec_name: name of the EXEC that is creating the event mv_exec_eid: name of the EXEC identifier
JOURNAL	Specifies that BMC AMI OpsA writes informational messages to the BBI Journal that describe this event	Warning By setting this keyword to YES, the volume of messages sent to the BBI Journal might be large.
MSG	Specify the name of the variable that contains the data that will be used by the BIM cell to populate the msg slot in the event	n/a
SEVERITY	Specify the severity of the event where valid values are: UNKNOWN OK INFO WARNING MINOR MAJOR CRITICAL	The default is severity setting is WARNING.
SLOTSTEM	Specifies a stem root name for the REXX slot stem variables	Specify a stem root name for the REXX stem variable. Two REXX stem variables are used: SLOTNAME – the maximum size of this value is 32 characters SLOTDATA – the maximum size of this value is 64k characters For example, if SLOTSTEM(MYSTEM) is specified, the variable names will resolve to MYSTEM.SLOTNAME. and MYSTEM.SLOTDATA. You can set up to 16 slots. The maximum length of the SLOTSTEM name is 8 characters. The value must conform to standard REXX variable naming rules. Compound REXX stem variables are not supported. You must create REXX stem variables that define each slot and a value for that slot, and a REXX variable that defines how many slots you are passing: name.0 contains the number of slots being passed name.SLOTNAME.n where n is the value of 1 through 16, and the variable is set to the slot name name.SLOTDATA.n, where n is the value of 1 through 16, and the variable is set to the slot value. An example when you use SLOTSTEM(MYSLOT), and you want to pass in 4 slots, you would create the following REXX stem variables: MYSLOT.0 = 4 MYSLOT.SLOTNAME.1 = SLOT1 MYSLOT.SLOTDATA.1 = valueSlot1 MYSLOT.SLOTNAME.2 = SLOT2 MYSLOT.SLOTDATA.2 = valueSlot2 MYSLOT.SLOTNAME.3 = SLOT3 MYSLOT.SLOTDATA.3 = valueSlot3 MYSLOT.SLOTNAME.4 = SLOT4 MYSLOT.SLOTDATA.4 = valueSlot4
SS \| SSID	Specifies the subsystem identifier of a local subsystem	If the TGTSS parameter is not specified, the command runs in the subsystem where the EXEC is scheduled. Generic wildcard characters are supported for this keyword. You can specify 1 to 4 asterisks () or plus signs (+). If you specify a single asterisk (), any BBI-SS PAS found on the same LPAR might be used to process the EXEC. You can also specify SS(P*) and the EXEC can be processed by any BBI-SS PAS that begins with P. You can use also the plus sign (+) to indicate a positional wildcard such as SS(+++P). In this example, the EXEC can be processed on any BBI-SS PAS that ends in P. Use the AOOPTION parameter to further filter on the wildcard value. By specifying a value with AOOPTION, you can route the EXEC to the BMC AMI OpsA BBI-SS PAS that is running a product option or group of product options. AOOPTION is mutually exclusive with TGTSS and TGTJNT, and it is ignored on a fully qualified SSID specified with SS or SSID parameter.
AOOPTION	Specifies the product options that must be active in the BMC AMI OpsA PAS. The following values are valid: ANV, CAO, IAO, IIZ, MAO, QAO, or TSH. IIZ represents the BMC AMI OpsA BMC Impact Integration for z/OS product. The stand-alone BMC Impact Integration for z/OS product does not support AOAnywhere processing.	The specified product option must be active in the BMC AMI OpsA PAS. The value specified with the AOOPTION parameter is valid only when the SSID parameter specifies a wildcard value. Note EXEC processing ignores the AOOPTION parameter when a non-wildcard SSID is specified in the SSID parameter. AOOPTION cannot be specified if TGTSS or TGTJNT are also specified.
TGTSS	Specifies the subsystem identifier of a local subsystem	If the TGTSS parameter is specified, the subsystem that is specified with the SS parameter is considered a router and the actual function is executed on the subsystem specified by TGTSS. If the TGTSS parameter is not specified, the command runs in the subsystem where the EXEC is scheduled. The EXEC must be in the same sysplex as the BBI-SS that is specified with the SSID() keyword, and both systems must have the same XCFGROUP specified in BBPARM member BBISSPxx. When the AOEXEC command originates from a NetView EXEC, the router and local BMC AMI OpsA PAS must have an active, valid BMC AMI Ops Automation Access NV key.
TGTJNT	A JNT entry that identifies the SSID which processes this request	Use this parameter to specify a different target from the target system where the EXEC is invoked. The specified TGTJNT() should match a TARGET=(tgtname) parameter that is entered in BBPARM member BBIJNT00. The EXEC is scheduled on the subsystem that corresponds to the subsystem that is specified by the SS \| SSID parameter of the JNT entry. The specified TGTJNT() may also be an SSID with which the original subsystem communicates. This keyword is mutually exclusive with the TGTSS() keyword. The target subsystem named in the TGTJNT entry must exist within the current sysplex.
UEID	Specify the Unique Event Identification (UEID) from the originating event	If you not set a UEID, the system will generate a UEID.

Condition codes are listed in the following table:

Value	Description
0	Processing completed.
12	No matching cell found. Processing failed. BMC AMI OpsA issues the message AX9010E NO MATCHING ACTIVE GME CONNECTION.
16	Syntax error. BMC AMI OpsA issues one of the following messages AY0902E <parsingErrorMssages> AX9011E MSG() MUST BE SPECIFIED
32	No XCF connection exists between the subsystem that was specified with the SS \| SSID() keyword and the subsystem that was specified by using the TGTSS() keyword. The target subsystem is most likely not active or not in the same sysplex as the originating subsystem.
36	The subsystem that was specified by using the SS \| SSID() keyword cannot be found on the local system.
40	Security definitions disallowed access to this function on the specified subsystem.
48	Incompatible AOAnywhere versions exist.
52	An attempt was made to execute this function under NetView without a valid Access NV product key.
54	AOEXEC was not invoked as a regular NetView command processor. ADDRESS LINKMVS or some other method might have been used to invoke it. AOEXEC must be defined in the DSICMD member of DSIPARM and run as a regular NetView command processor. See the for information about how to implement AOEXEC under NetView.
56	The BBI-SS PAS is not a BMC AMI OpsA system. If this BBI-PAS is meant to be a BMC AMI OpsA, ensure that the BMCPSWD DD of the PAS JCL contains valid BMC AMI OpsA keys and product=AAO is specified in BBPARM member BBISSP00.

Example

The following example shows how to use AOEXEC BIM command to send an event to all active GME connections.

RESP.0 = 0
MYUEID = ''
MYCLASS = ''

BIAGIOLIMSG = 'TEXT OF THE DATA TO SEND TO BIIZ'

MYSLOT.0 = 1
MYSLOT.SLOTNAME.1 = THISISMYSLOT
MYSLOT.SLOTDATA.1 = THISISTHESLOTDATA

"AOEXEC BIM EVENT ",
" SLOTSTEM(MYSLOT)",
" SEVERITY(MINOR)",
" MSG(BIAGIOLIMSG)",
" JOURNAL(Y)",
" SS("SS") TGTSS("TGTSS") "

SAY "RC= "RC

AOEXEC BIM

Example

On this page