IBM E16RMLL-I - Tivoli Storage Manager, Руководство по внедрению

Страница: 726 / 828

696
IBM Tivoli Storage Manager Implementation Guide
Further, certain background Tivoli Storage Manager applications might fail to
start due to errors writing to dsmerror.log. When these errors occur, a number of
errors are recorded in the Windows event log (the System log on other
platforms). An example is an error indicating that dsmerror.log could not be
written to, as shown in Example 22-1.
Example 22-1 Scheduler service fails to start due to errors writing to dsmerror.log
C:\Program Files\Tivoli\Tsm\baclient>net start “TSM Sched”
The TSM Sched service is starting.
The TSM Sched service could not be started.
A service specific error occurred: 12.
Additional setup steps are required for non-root users to run Tivoli Storage
Manager applications or Tivoli Storage Manager for Data Protection applications.
You will receive the ANS1398E error if you attempt to run Tivoli Storage
Manager applications using an error log that has already been generated by root
that is left with default permissions. For data protection clients, you might only
receive a Tivoli Storage Manager API error.
Here is one method for setting up dsmerror.log for use by non-root users:
1. Set ERRORLOGNAME in dsm.sys. For example, enter errorlogname
/var/msgs/tsm/dsmerror.log.
2. Generate a starter dsmerror.log by issuing the dsmc query session
command.
3. Modify the permissions on dsmerror.log to allow writing by all users, for
example, by entering the
chmod 666 /var/msgs/tsm/dsmerror.log
command.
Discontinued client platform support
The following clients or client operating system levels were not migrated to V5.3.
The V5.2 clients that support these operating systems can be used with the V5.3
Tivoli Storage Manager servers.
򐂰
Macintosh 10.1, 10.2
򐂰
Linux IA64
򐂰
HP-UX 11.0
򐂰
Linux Red Hat Advanced Server 2.1
򐂰
SLES 7
򐂰
NetWare 6.0
򐂰
Solaris 7
򐂰
OS/400 V5R1 (API client)
򐂰
OS/390 V2R10 and z/OS V1R1, V1R2, and V1R3
򐂰
SGI