Events

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:

• Selection Criteria fields

• CICa

• Creating a Rule for CICS multiline messages

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:

• The IMS OM address space runs on the same z/OS image as the MainView AutoOPERATOR PAS.

• You must specify the MainView AutoOPERATOR OM Input Exit (BMCAOOM) in the OM exit routine definitions list in the OM Proclib member: for example: EXITDEF=(TYPE=INPUT,EXITS=(BMCAOOM),COMP=OM.

• Include the MainView AutoOPERATOR load library in the STEPLIB of the IMS OM started task JCL.

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:

• Selection Criteria fields

• IMSa

• Example 1: creating a Rule with MLSEG Minor = ALL

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:

• Selection Criteria fields

• IMSs

• Example 2: creating a Rule where MLSEG Minor = SINGLE

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

events that originated as IBM MQ events

For more information, refer to the MainView AutoOPERATOR for MQ Installation and User Guide.

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:

• Selection Criteria fields

• MSGa

• Example 1: creating a Rule where MLWTO minor = ALL

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:

• Selection Criteria fields

• MSGs

• Example 2: creating a Rule where MLWTO minor = SINGLE

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:

• job processor time limit from the JOB statement

• step processor time limit from the EXEC statement of the default JES

• continuous wait time for a job from the JWT parameter in SMFPRMXX

  Wait time is defined as the time waiting while the application program is in control. For example, the time that it takes for a data set to be recalled does not count as wait time unless the recall is by way of dynamic allocation written in a user’s program.

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