Events
Events are occurrences in the system, such as messages, commands, and ALERTs, that are eligible to be automated.
In general, events are differentiated based on where they originated in the system. Some examples of events that are supported by MainView AutoOPERATOR are MVS write-to-operator messages (WTOs), CICS transient data queue (TDQ) messages, BBI-SS PAS Journal messages, and MVS commands. MainView AutoOPERATOR regards each of these events as a different event type and MainView AutoOPERATOR supports a total of 21 system-based events.
Which event types are available for automation on your system depends on your configuration of MainView AutoOPERATOR options and other BMC Software products. To help you determine which events might be available on your system, the following table describes:
- The event
- The origin or cause of the event
- The product option required for the event type to be eligible for automation
- Whether statistics are available for the event in the Event Activity Statistics application
For information about special circumstances that can affect event types, refer to Special-event-types.
Product requirements for event availability
Event type | Caused by | Product or option required | Event statistics available? |
---|---|---|---|
ALRT | the creation of an MainView AutoOPERATOR ALERTs MainView AutoOPERATOR ALERTs can be created by an MainView AutoOPERATOR EXEC or by the Rule Processor. | any MainView AutoOPERATOR | Yes |
ALRM | alarm messages created by the MainView Alarm Manager | any MainView AutoOPERATOR | Yes |
BRC | BAROC messages sent from BMC products | BMC Impact Integration for z/OS product and specified PRODUCT=IIZ in BBPARM member BBISSP00 | No |
CICS | CICS Intrapartition or Extrapartition Transient Data Messages These messages are processed by the MainView AutoOPERATOR for CICS Transient Data Program Exit CMRTDPXn, which runs when a message is passed through the XTDOUT exit in CICS Transaction Server. Restrictions: CICS can generate multiline messages queued to the transient data queue (application programs typically cannot do this generation). When any line of a multiline message is suppressed in the TDQ (XTDOUT) exit, all subsequent lines of the multiline message are discarded and not presented to the XTDOUT exit. This restriction is due to the design of the CICS XTDOUT exit. Therefore if a Rule fires that handles a CICS message and has 'Display at Destination = NO' specified, all remaining lines of the multiline message are discarded and not seen by the Rule Processor. For example, you cannot suppress a part of any multiline CICS message and still receive the rest of the multiline message in a Rule. | MainView AutoOPERATOR for CICS | Yes |
CICa | CICS Intrapartition or Extrapartition Multiline messages The CICa event type is a subset of the CICS event type. CICa events appear on Rule Processor panels when the selection criteria for a CICS-initiated Rule specifies MLTDQ = ALL. For more information: | MainView AutoOPERATOR for CICS | Yes |
CMD | commands processed by the MVS subsystem interface | MainView AutoOPERATOR for z/OS | Yes |
DB2 | IBM DB2 generated messages Messages are sent from a DB2 subsystem. Refer to Special-event-types for more information about this event type. | MainView for DB2 | Yes |
EOM | End-of-Memory (EOM) event that occurs after an address space ends An address space ends when a Started Task (STC) or TSO User (TSU) is stopped, canceled, or ends abnormally (abends). An address space does not end when a batch job terminates. It ends when the initiator is terminated. When a TSO user ID is canceled, the EOM event shows the TSO user session as NORMAL termination (instead of the ABNORMAL termination) because TSO recovers from the cancel request and does a normal logoff to end the session. | MainView AutoOPERATOR for z/OS | Yes |
EOS | End-of-Step (EOS) event that occurs whenever an address space changes steps | MainView AutoOPERATOR for z/OS | Yes |
EXT | externally generated messages External messages directed at the BBI-SS PAS using SUBSYS= parameter on a DD statement in JCL. Refer to Special-event-types for more information about this event type. | any MainView AutoOPERATOR | Yes |
HWTO | Historical WTO events Early WTOs and interim WTOs that were issued while MainView AutoOPERATOR was inactive For early HWTOs, you must have the MVS EXIT CNZ_MsgToSyslog exit. For more information, see the MainView AutoOPERATOR Customization Guide. | BMC MainView Automation Solution | No |
IMP | IMS type-2 (IMSplex) commands An OM Input user exit sends these commands before the IMS OM address space processes them. The requirements to receive these events are as follows:
| MainView AutoOPERATOR for IMS | Yes |
IMS | IMS MTO generated messages System messages sent to the IMS Master Terminal, and IMS commands and responses. | MainView AutoOPERATOR for IMS | Yes |
IMSa | IMS multisegment MTO messages (MLSEG) The IMSa event type is a subset event type of the IMS event type. IMSa events appear on Rule Processor panels when the selection criteria for a Rule initiated by IMS specifies MLSEG Minor = ALL. For more information: | MainView AutoOPERATOR for IMS | Yes |
IMSs | IMS multisegment MTO messages (MLSEG) The IMSs event type is a subset event type of the IMS event type. IMSs events appear on Rule Processor panels when the selection criteria for a Rule initiated by IMS specifies MLSEG Minor = SINGLE. For more information: | MainView AutoOPERATOR for IMS | Yes |
JRNL | BBI Journal generated messages These messages come from BBI products and the IMFEXEC MSG statement. | any MainView AutoOPERATOR | Yes |
MQS | events that originated as IBM MQ events For more information, refer to the MainView AutoOPERATOR for MQ Installation and User Guide. | MainView AutoOPERATOR for MQ | Yes |
MSG | WTOs and WTORs These messages originated as MVS WTOs (write-to-operator) and WTORs (write-to-operator with response). | MainView AutoOPERATOR for z/OS | Yes |
MSGa | multiline WTO (MLWTO) The MSGa event type is a subset event type of the MSG event type. MSGa events appear on Rule Processor panels when the selection criteria for a MSG-initiated Rule specifies MLWTO Minor = ALL. For more information: | MainView AutoOPERATOR for z/OS | Yes |
MSGs | multiline WTO (MLWTO) The MSGs event type is a subset event type of the MSG event type. MSGs events appear on Rule Processor panels when the selection criteria for a MSG-initiated Rule specifies MLWTO Minor =SINGLE. For more information: | MainView AutoOPERATOR for z/OS | Yes |
NVC | command events that originate from NetView | MainView AutoOPERATOR Access NV | Yes |
NVM | message events that originate from NetView | MainView AutoOPERATOR Access NV | Yes |
TIME | time-initiated events These Rules are fired based on the time of day. | any MainView AutoOPERATOR | No |
TLM | Time Limit (TLM) events occur when one of the following time limits expires:
There will be a TLM event when the time limit has expired as specified on the JOB statement, Step statement, or continuous wait time (JWT). | MainView AutoOPERATOR for z/OS | Yes |
VAR | the creation, deletion, or change in value of a variable in the SHARED variable pool | any MainView AutoOPERATOR | No |
As this table shows, MainView AutoOPERATOR keeps statistics for most event types that you can view with the Event Activity Statistics application. Use the Event Activity Statistics application to see easily which events occur more frequently and, therefore, might be good candidates for automation with Rules. For more information, refer to Using-the-Event-Activity-Statistics-application.