I can't think of any reason to install 3.1.0.8 first. You should be able to
jump right to 3.7.2.19. Just be sure to review the accompanying README.1ST
file first. Probably the most obvious thing is starting with ADSM 3.1.0.5,
the client now uses the UNC name of your drives for the filespace names
instead of the volume labels. This (and other issues) are discussed in the
README.1ST file.

Regards,

Andy

Andy Raibeck
IBM Tivoli Systems
Tivoli Storage Manager Client Development
e-mail: araibeck AT tivoli DOT com
"The only dumb question is the one that goes unasked."


Maria Ragan <mragan AT BCO DOT COM>@VM.MARIST.EDU> on 03/20/2001 05:01:29 PM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

Sent by:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To:   ADSM-L AT VM.MARIST DOT EDU
cc:
Subject:  ADSM 3.1.0.3 to 3.7.2.19



Server:  AIX 4.3.2 TSM 3.7.2    Clients:  NT 4 ADSM 3.1.03

Any reason to upgrade our NT clients currently at ADSM v 3.1.03 to ADSM v
3.1.08 before upgrading to 3.7.2.19 as Tivoli support suggested?

Thanks,

Maria