TSM server and client messages provide a record of TSM activity that you, as an administrator, may use to monitor TSM. You can log server messages and most client messages as events to one or more repositories called receivers. You can log the events to any combination of the following receivers:
In addition, you can filter the types of events to be enabled for logging. For example, you might enable only severe messages to the event server receiver and one or more specific messages, by number, to another receiver. Figure 62 shows a possible configuration in which both server and client messages are filtered by the event rules and logged to a set of specified receivers:
Figure 62. Event Logging Overview
To control event logging do the following:
You can issue the BEGIN EVENTLOGGING and END EVENTLOGGING commands to begin and end logging for one or more receivers.
Note: | At server start-up event logging begins automatically to the TSM server console and activity log and for any receivers that are started based on entries in the server options file. See the appropriate receiver sections for details. |
You can enable or disable specific events or groups of events by receiver by issuing the ENABLE EVENTS and DISABLE EVENTS commands. When you enable or disable events, you can specify the following:
For example, to enable event logging to a user exit for server messages with a severity of WARNING, enter:
enable events userexit warning
Notes:
Logging events to the TSM server console and activity log begins automatically at server startup. To enable all error and severe client events to the console and activity log, issue the following command:
enable events console,actlog error,severe nodename=*
Note: | Enabling client events to the activity log will increase the database utilization. You can set a retention period for the log records by using the SET ACTLOGRETENTION command (see Setting the Activity Log Retention Period). At server installation, this value is set to one day. If you increase the retention period, utilization is further increased. For more information about the activity log, see Using the Tivoli Storage Manager Activity Log. |
You can disable server and client events to the server console and client events to the activity log. However, you cannot disable server events to the activity log. Also, certain messages, such as those issued during server startup and shutdown and responses to administrative commands, will still be displayed at the console even if disabled.
You can log events to a file exit and a user exit:
Both file and user exits receive event data in the same data block structure (see Appendix A, User Exit and File Exit Receivers for details). Setting up logging for these receivers is also similar. Here are the steps involved:
To specify a binary version of the file named events.fexit, enter:
fileexit yes events.fexit appendTo avoid having a prefix appended to the file name, enclose the name in double quotation marks (").
To specify a readable text version of the file named events.ftexit, enter:
filetextexit yes events.ftexit appendTo avoid having a prefix appended to the file name, enclose the name in double quotation marks ("). For a description of the file format, see Readable Text File Exit (FILETEXTEXIT) Format.
userexit yes evntsuxt
For details about these server options, see Administrator's Reference.
begin eventlogging userexit
enable events userexit error,severe
You must specify the name of the user exit in the USEREXIT server option.
enable events file error nodename=msmith,hstanford,bkelly
You must specify the name of the file in the FILEEXIT server option.
When TSM forwards an event to the NetView receiver, a message is formatted for display with the MVS Write To Operator (WTO) multi-line support. This ensures that a multi-line message is forwarded as one entity to NetView.
Setting up logging for the NetView receiver requires the following steps:
ANE4001E AUTO(YES) ANR55* AUTO(YES)
For details about the MPFLSTxx member, see MVS Initialization and Tuning.
begin eventlogging netview
enable events netview all
TSM includes the Tivoli receiver, a Tivoli/Enterprise Console (T/EC) adapter for sending TSM events to the TE/C. This section describes what you must do to set up Tivoli as a receiver for event logging:
enable events tivoli severe,error
techostname 9.114.22.345 tecport 1555
tecbegineventlogging yes
Or
begin eventlogging tivoli
For details about the server options shown, see Administrator's Reference.
One or more servers can send server events and events from their own clients to another server for logging. Tivoli Storage Manager provides a receiver at the sending server that receives the enabled events and routes them to a designated event server. At the event server, an administrator can enable one or more receivers for the events being routed from other servers. Figure 63 shows the relationship of a sending TSM server and a TSM event server.
Figure 63. Server to Server Event Logging
The following scenario is a simple example of how enterprise event logging can work.
The administrator at each sending server does the following:
define server server_b password=cholla hladdress=9.115.3.45 lladdress=1505
define eventserver server_b
enable events eventserver severe,error,warning enable events eventserver severe,error nodename=*
The administrator at the event server does the following:
fileexit yes events append
Then the administrator enables the events by issuing the ENABLE EVENTS command for each sending server. For example, for SERVER_A the administrator would enter:
enable events fileexit severe,error servername=server_a
Note: | By default, logging of events from another server is enabled to the event server activity log. However, unlike events originating from a local server, events originating from another server can be disabled for the activity log at an event server. |
One or more servers can send events to an event server. An administrator at the event server enables the logging of specific events from specific servers. In the previous example, SERVER_A routes severe, error, and warning messages to SERVER_B. SERVER_B, however, logs only the severe and error messages. If a third server sends events to SERVER_B, logging is enabled only if an ENABLE EVENTS command includes the third server. Furthermore, the SERVER_B determines the receiver to which the events are logged.
Attention: It is important that you do not set up server-to-server event logging in a loop. In such a situation, an event would continue logging indefinitely, tying up network and memory resources. TSM will detect such a situation and issue a message. Here are a few configurations to avoid:
The QUERY ENABLED command displays a list of server or client events that are enabled or disabled by a specified receiver. Because the lists of enabled and disabled events could be very long, TSM displays the shorter of the two lists. For example, assume that 1000 events for client node HSTANFORD were enabled for logging to the user exit and that later two events were disabled. To query the enabled events for HSTANFORD, enter:
query enabled userexit nodename=hstanford
The output would specify the number of enabled events and the message names of disabled events:
998 events are enabled for node HSTANFORD for the USEREXIT receiver. The following events are DISABLED for the node HSTANFORD for the USEREXIT receiver: ANE4000, ANE49999
The QUERY EVENTRULES command displays the history of events that are enabled or disabled by a specific receiver for the server or for a client node.
query enabled userexit nodename=hstanford