IBM E16RMLL-I - Tivoli Storage Manager, Implementation Manual

Page: 522 / 828

492
IBM Tivoli Storage Manager Implementation Guide
memory and writing the recovery log data. For backup
direct to tape, this includes flushing the tape buffers.
Sleep Sleeping time.
Thread Wait Time spent waiting on another thread.
Other Time spent on any other task not mentioned above. If you
see a high number here, you should look at the statistics
reported by other threads, since this does not necessarily
indicate a problem with this particular thread.
Please note that the trace facilities can be changed at any time by development
without notification.
15.1.3 Tivoli Storage Manager server performance tracing
The Tivoli Storage Manager server can collect instrumentation statistics for a
period of time.
From a performance standpoint, do not activate the trace settings if you are in a
stable environment and are not experiencing problems. Trace routines require
processing time and could slow down the response times of your workstation
applications. If a problem occurs, you can always activate the trace routines to
gather trace information for diagnostic purposes. Call your Tivoli Service
Representative for assistance in diagnosing Tivoli Storage Manager problems.
Tivoli Storage Manager server performance instrumentation shows threads with
disk, tape, or network I/O operations during the observation period. To activate
performance instrumentation, use the
instrumentation begin
command, as in
Example 15-12.
Example 15-12 Start server performance instrumentation
tsm> INSTrumentation Begin [Maxthread=number]
By default, a maximum number of 1024 threads can be instrumented. To end
performance instrumentation, enter the
instrumentation end command, as in
Example 15-13.
Example 15-13 Stop server performance instrumentation
tsm> INSTrumentation End > <valid_path_and_filename>
Attention: Using these tracing facilities is done at your own risk.