Tivoli Storage Manager Client log usage.

Answer

This document is designed to assist with understanding the different log files that each client application uses, and how to configure the log files for usage. In addition references are provided to assist in locating the full documentation when applicable.

The following is a list of client log files that the client applications write and a list of the applications that use these log files:

dsmerror.log - Used to log errors by each of the client applications:
dsmc, dsmadmc, dsmcad, dsmj, Web Client


dsmsched.log - Used to write client schedule information, and scheduler errors for applications:
dsmc scheduler, dsmcad.


dsmwebcl.log - Used to write Web Client messages and Client GUI messages for applications:
dsmcad, dsmj, Web Client.


dsmj.log - Used to log JAVA messages and errors of the Client GUI application: dsmj
Note: This log is not documented in the Backup-Archive Clients
installation and User's Guide, and is mainly used by Tivoli support to
diagnose JAVA errors.


dsmaudit.log - Optional log file used to trouble shoot problems related to incremental,
selective, archive, restore, or retrieve operations on files. This logging has
to be turned on by setting option auditlogging, and is used by the following
applications:
dsmc, dsmadmc, dsmj, Web Client

1. The dsmerror.log location and name can be set using option errorlogname in the dsm.opt, or dsm.sys
files. This option is best used when the root user will be the only user with access to the client applications, and the location of the error log is owned by the root user.

2. The dsmsched.log location and name can be set using option schedlogname on the command line, or
in the dsm.opt file or the dsm.sys file. This option is best used when the root user will be the only user with access to the client scheduler applications, and the location of the error log is owned by the root user.

3. Setting the DSM_LOG environment variable, will tell the client applications where to create and store the
client log files. For example in a UNIX client environment DSM_LOG could be set for each user that has a login to the system, so that each user when executing client applications dsmc, dsmj, Web Client, or dsmadmc, will create their own set of client logs in their home environment. Note: Client applications dsmcad, and dsmc scheduler can only be started by the root user.

For more information and examples on how to set DSM_LOG environment variable see the Backup-Archive Clients Installation and User's Guide, Chapter 2, section Setting Environment Variables.


4. All applications default to writing log files to the current directory if options errorlogname,
schedlogname, and environment variable DSM_LOG are NOT set.

dsmc - Writes error messages to the dsmerror.log (the default name), or the file name specified by the
option errorlogname.

dsmc sched - Writes the client scheduler messages and errors to the dsmsched.log, or the name
specified by schedlogname. Also writes errors messages to the dsmerror.log, or the name specified by option errorlogname.

dsmj - The Client GUI writes JAVA messages to the dsmj.log file, and errors messages to the
dsmerror.log, or the name specified by option errorlogname.
Log file dsmj.log can be used to debug JAVA errors reported by dsmj. In addition the Client GUI interfaces with the client agent daemon that writes messages to the dsmwebcl.log.

Web Client - Web client messages are written to the dsmwebcl.log through the client agent daemon, and
error messages are written to dsmerror.log (the default name), or the name specified by option errorlogname.


For more information see: Backup-Archive Clients Installation and User's Guide, Chapter 2, section Configuring the Web Client.


dsmcad - Is the Client Acceptor Daemon used to manager the Web Clients by starting the client agent
daemon and used to manage the scheduler. The client acceptor daemon can write the dsmwebcl.log, the dsmerror.log, and the dsmsched.log.