![]() |
![]() |
The server and client messages provide a record of TSM activity that you can use to monitor the server. 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 53 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 53. Event Logging Overview
Task | Required Privilege Class |
---|---|
Enable or disable events
Begin or end event logging | System |
To control event logging do the following:
When you enable or disable events, you can specify the following:
To enable or disable events, issue the ENABLE EVENTS and DISABLE EVENTS commands. For example,
enable events userexit error,severe
enable events userexit severe nodename=*
disable events userexit error
A receiver for which event logging has begun is an active receiver. To begin and end logging for one or more receivers, issue the BEGIN EVENTLOGGING and END EVENTLOGGING commands.
At server start-up event logging begins automatically to the 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. To begin logging events to receivers for which event logging is not started automatically, issue the BEGIN EVENTLOGGING command. You can also use this command after you have disabled event logging to one or more receivers. To end event logging for an active receiver issue the END EVENTLOGGING command.
For example,
begin eventlogging eventserver
end eventlogging eventserver
Logging events to the 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
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. Setting up logging for these receivers is also similar:
For example,
fileexit yes data.mt1.log replace filetextexit yes data.mt1.log replace
For example,
userexit yes evntsuxt assembler
enable events file error
enable events userexit error,severe
You can also enable events to one or more client nodes or servers by specify the NODENAME OR SERVERNAME parameter. See Enabling and Disabling Events for more information.
begin eventlogging userexit
See Beginning and Ending Event Logging for more information.
When you allocate the dataset for the FILEEXIT receiver, specify the following attributes:
When you allocate the dataset for the FILETEXTEXIT receiver, specify the following attributes:
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 warning,severe
TSM includes the Tivoli receiver, a Tivoli/Enterprise Console (T/EC) adapter
for sending events to the T/EC. You can specify the events to be logged
based on their source. The valid event names are:
Event Name | Source |
---|---|
TSM_SERVER_EVENT | TSM server |
TSM_CLIENT_EVENT | TSM clients |
TSM_APPL_EVENT | TSM application program interface |
TSM_TDP_DOMINO_EVENT | TDP for Domino |
TSM_TDP_EXCHANGE_EVENT | TDP for MS Exchange |
TSM_TDP_INFORMIX_EVENT | TDP for Informix |
TSM_TDP_ORACLE_EVENT | TDP for Oracle |
TSM_TDP_SQL_EVENT | TDP for MS SQL |
The application client must have enhanced T/EC support enabled in order to route the events to the T/EC. Because of the number of messages, you should not enable all messages from a node to be logged to the T/EC.
To set up Tivoli as a receiver for event logging:
To create a new rule base, do the following:
techost 9.114.22.345 tecport 1555
tecbegineventlogging yes
Or
begin eventlogging tivoli
See Beginning and Ending Event Logging for more information.
One or more servers can send server events and events from their own clients to another server for logging. The sending server receives the enabled events and routes them to a designated event server. This is done by a receiver that Tivoli Storage Manager provides. At the event server, an administrator can enable one or more receivers for the events being routed from other servers. Figure 54 shows the relationship of a sending TSM server and a TSM event server.
Figure 54. 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=*
begin eventlogging eventserver
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 file severe,error servername=server_a
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