Normally tracing is most useful when working with IBM support or development to diagnose a problem. The trace settings you need, and what components you need to trace depend on the nature of the problem.
Perhaps if you were to describe your TSM environment and the problem you are having, and include actual documentation showing the problem, someone on this list might already know what you are seeing, eliminating the need to trace at all. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. "Lepre, James" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 11/03/2004 07:20 Please respond to "ADSM: Dist Stor Manager" To [EMAIL PROTECTED] cc Subject Re: TRACING Version 5.2.2.2 -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of David E Ehresman Sent: Wednesday, November 03, 2004 8:17 AM To: [EMAIL PROTECTED] Subject: Re: TRACING The synax will differ depending on your version of TSM. >>> [EMAIL PROTECTED] 11/2/2004 11:56:10 AM >>> Hello All, I am having a difficult time setting up a trace. I need to trace a backup I am trying to perform because it keeps failing in the same place. I know I need to add something to the DSM.OPT file but I have forgotten what it is, and also is there something on the server side I need to do as well. Any help is always appreciated, and thank you in advance. Thanks James
