Chapter 22. Tivoli Storage Manager upgrade considerations
695
V5.2 and V5.3 command-line administrative clients can administer Tivoli
Storage Manager V5.2 and V5.3 servers, and the V3.1 VM server.
The Motif native GUI on UNIX clients was not migrated to V5.3. The Java GUI
client should be used instead.
Error log behavior change
Beginning with V5.3, client applications will not run without a writable log. If you
start dsmadmc or dsmc as non-root, and if the option ERRORLOGNAME in
dsm.sys points to a file that is not writable by non-root users, error message
ANS1398E is displayed and the session does not start.
The following new rules apply (using dsmerror.log as an example, but all logs are
treated equally). The different error logs for the backup-archive client are
explained in “Environment variables” on page 113 under DSM_LOG:
1. If the log does not exist, it will be created as follows (with default
permissions):
– With the name and in the directory specified in the ERRORLOGNAME
option.
– If the ERRORLOGNAME option is absent, the log will be created with the
name dsmerror.log in the directory specified in the DSM_LOG
environment variable, if present.
– Otherwise, the log will be created with the name dsmerror.log in the
current working directory.
– Because default permissions are used, a log created by the root user
might not be writable by any other user. If this is the case, the root user
must set the proper permissions or ACLs to allow free use of the Tivoli
Storage Manager application by all users who need to use it.
2. If the log is successfully created, an error-free session will leave a zero-length
(empty) log file.
3. The client does not attempt to create logs in the root directory. ANS1398E is
displayed when the method in rule 1 directs the log file to be created in the
root directory.
4. If a log file exists and can be located using the method in rule 1, it will be used
(and it can be in the root directory if you choose). Furthermore, whatever
permissions you give that log file will be preserved by Tivoli Storage Manager.
We recommend that you create your log file before running the client, to make
sure all eligible users have write access to that log. Use the ERRORLOGNAME
option or the DSM_LOG environment variable to designate your predefined log
file.
Summary of Contents for E16RMLL-I - Tivoli Storage Manager
Page 2: ......
Page 23: ...Figures xxi 22 6 AIX lab environment 708...
Page 24: ...xxii IBM Tivoli Storage Manager Implementation Guide...
Page 32: ...2 IBM Tivoli Storage Manager Implementation Guide...
Page 44: ...14 IBM Tivoli Storage Manager Implementation Guide...
Page 94: ...64 IBM Tivoli Storage Manager Implementation Guide...
Page 96: ...66 IBM Tivoli Storage Manager Implementation Guide...
Page 126: ...96 IBM Tivoli Storage Manager Implementation Guide...
Page 298: ...268 IBM Tivoli Storage Manager Implementation Guide...
Page 354: ...324 IBM Tivoli Storage Manager Implementation Guide...
Page 356: ...326 IBM Tivoli Storage Manager Implementation Guide...
Page 423: ...Chapter 12 Scheduling 393 Week of Month Expire Never tsm quit...
Page 424: ...394 IBM Tivoli Storage Manager Implementation Guide...
Page 510: ...480 IBM Tivoli Storage Manager Implementation Guide...
Page 552: ...522 IBM Tivoli Storage Manager Implementation Guide...
Page 554: ...524 IBM Tivoli Storage Manager Implementation Guide...
Page 594: ...564 IBM Tivoli Storage Manager Implementation Guide...
Page 612: ...582 IBM Tivoli Storage Manager Implementation Guide...
Page 618: ...588 IBM Tivoli Storage Manager Implementation Guide...
Page 720: ...690 IBM Tivoli Storage Manager Implementation Guide...
Page 752: ...722 IBM Tivoli Storage Manager Implementation Guide...
Page 758: ...728 IBM Tivoli Storage Manager Implementation Guide...
Page 780: ...750 IBM Tivoli Storage Manager Implementation Guide...
Page 802: ...772 IBM Tivoli Storage Manager Implementation Guide...
Page 823: ...Index 793 Z z OS tape management 58 zOS 200...
Page 824: ...794 IBM Tivoli Storage Manager Implementation Guide...
Page 825: ...IBM Tivoli Storage Manager Implementation Guide...
Page 826: ......
Page 827: ......