Table of Contents
Advertisement
Schedule Randomization Percentage: 25
Table of Contents (TOC) Load Retention: 120 Minute(s)
00.00.00.00.95.0b.11.da.bb.57.08.63.09.2b.56.31
We recommend running the begin eventlogging command to make sure that all
defined receivers are active. Use this command to begin logging events to one or
more receivers. Event logging automatically begins when the server is started for
the console and activity log, and for any receivers that are started automatically
based on entries in the server options file. A receiver for which event logging has
begun is an active receiver. Example 13-10 shows you how to activate all defined
receivers.
Example 13-10 Activating defined receivers
tsm: ATLANTIC>
ANR1825I Event logging active for the CONSOLE receiver.
ANR1825I Event logging active for the ACTLOG receiver.
We recommend enabling nodename logging so that you can also monitor client
activity centrally in the server. Note that enabling client events to the activity log
will increase the Tivoli Storage Manager database utilization. You can set a
retention period for the log records by using the set actlogretention command.
406
IBM Tivoli Storage Manager Implementation Guide
Query Schedule Period: Client
Maximum Command Retries: Client
Retry Period: Client
Scheduling Modes: Any
Log Mode: Normal
Database Backup Trigger: Not Defined
BufPoolSize: 524,288 K
Active Receivers: CONSOLE ACTLOG
Configuration manager?: Off
Refresh interval: 60
Last refresh date/time:
Context Messaging: Off
Server-free Status: Not Supported
Server-free Batch Size:
Machine Globally Unique ID:
Archive Retention Protection: Off
Encryption Strength: AES
begin eventlogging
Advertisement
Table of Contents
