To get the most detailed output from TSM, turn on accounting for the client machine.
-- Joshua S. Bassi Independent IT Consultant IBM Certified - AIX/HACMP, SAN, Shark Tivoli Certified Consultant- ADSM/TSM Cell (408)&(831) 332-4006 [EMAIL PROTECTED] -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]] On Behalf Of Hunley, Ike Sent: Monday, October 01, 2001 12:14 PM To: [EMAIL PROTECTED] Subject: Audit trail for TSM? This is probably ground many of you have walked, but I need to know. How do you get an audit trail of what TSM is doing? What if files that should archive, don't? Is there a way to know? Where do I begin to look? Ike -----Original Message----- From: Zlatko Krastev/ACIT [mailto:[EMAIL PROTECTED]] Sent: Sunday, September 30, 2001 7:43 AM To: [EMAIL PROTECTED] Subject: Re: AIX 4.3.3 - Probleme migration from TSM 4.1.2 to TSM 4.1.4.1 Check the level of tivoli.tsm.msg.en_US.server fileset. It must be 4.1.4.0. In fact only tivoli.tsm.license.rte and tivoli.tsm.msg.en_US.devices must stay at 4.1.0.0. All other have to be 4.1.4.0 and tivoli.tsm.server.com, tivoli.tsm.server.rte at 4.1.4.1. Look for the presense of file /usr/lib/nls/msg/en_US/dsmserv.cat It might be necessary to make a link /usr/lib/nls/msg/fr_FR/dsmserv.cat -> ./en_US/dsmserv.cat (or /usr/lib/nls/msg/$LANG/dsmserv.cat -> ./en_US/dsmserv.cat). Latter normally has to be done also for dsmlabel.cat, dsmserv.hlp, dsmc.hlp, etc. Zlatko Krastev IT Consultant Patrick Armusieaux <[EMAIL PROTECTED]> on 28.09.2001 15:45:23 Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: AIX 4.3.3 - Probleme migration from TSM 4.1.2 to TSM 4.1.4.1 Hi , I try to migrate from TSM 4.1.2 to TSM 4.1.4.1. The update process is executed normally but when whe start the server "dsmserv" we have this error : ANR0000E Unable to open language en_US for message formatting ANR0000E Unable to open message text file form message formatting Do you have encountered this problem and how resolve it ? Thank's Blue Cross Blue Shield of Florida, Inc., and its subsidiary and affiliate companies are not responsible for errors or omissions in this e-mail message. Any personal comments made in this e-mail do not reflect the views of Blue Cross Blue Shield of Florida, Inc.
