How events work

• TSO users
• The system log or console
• MainView AutoOPERATOR
• Other automated-operations packages

The FLST/RLST statements for the function define the conditions to be acted upon and the ID of an event to be generated. The following figure shows the relationships of the various members that collectively generate an event.

The EVENTID keyword in an FLST or RLST function member defines the identification of the event. In the SMEVNTxx PARMLIB member, you define the entire event definition, including modifiable text with data substitution. An event definition specifies the message text to create for the event, the destinations where the event is sent, and other information.

The SMEVNTxx member is also used to activate internal system events that are generated automatically by MainView SRM Automation. These events are defined in System event definitions. You must create an entry in SMEVNTxx for any system event that you want to modify.

The SMEVNT member suffix is specified in the SMMSYSxx member by way of the EVNT keyword. SMMSYSxx is the MainView SRM system-configuration member and contains suffixes of most other PARMLIB members. For further information about generating events, see Basic event generation.

Event members

If the MainView Logger is installed, customized, active, and available to the MainView SRM address space, all events that are generated by the Automation component will be logged to the MainView Logger. The events that are logged can be viewed by using the links that are available on the Automation Main menu. The events will be logged to the main (or default) logspace that is defined to the MainView Logger. If you want to create a separate logspace for MainView SRM events, you can do so, but it is not required. If you do create a separate logspace for MainView SRM events, you must code the MVL_LSNAME keyword in the SMMSYSxx PARMLIB member identifying the logspace name MainView SRM is to use. The MainView Logger address space must be active before the SVOS address space becomes active to ensure that the MainView Logger receives all of the events that are generated by MainView SRM. If SVOS is activated after the MainView Logger address space or if the MainView Logger address space is cycled while SVOS is active, the SVOS address space will establish or reestablish the connection to the MainView Logger automatically.

See the Customizing after installation and the MainView Administration Guide for information about MainView Logger customization and usage.