Hi Paul,

The ADSM 32-bit client PTF6 and ADSM for Windows NT full package PTF1
installs both have this capability.  There is actually a lot of new
functionality in the installs including the ability to install the
saclient and baclient in the same directory, upgrading or removing
previous installs (incl. pre-ptf5), user configurable options and
readme files, and automatic generation of response files for silent
installs.  Previous options files are now preserved.  The restrictions
regarding a separate install for the API component are removed and the
diskette images will be available as self-extracting zip files.

These items are currently being tested and documented.

As I mentioned in a previous note, we hear you, value your feedback
and are working to make ADSM more usable in your environments.

Regards,

Mike Collins
ADSM Development

Paul Zarnowski writes:
 > On Tue, 19 Nov 1996 12:08:34 -0500 Mike Dile said:
 > >Classification:
 > >Prologue: Mike Dile
 > >IBM Storage Systems Division
 > >ADSM Client Development
 > >Phone: (408)256-3637
 > >Internal: mikedile@ibmusm50
 > >Internet: mikedile AT us1.ibm DOT com
 > >Epilogue:
 > >
 > >Those server values are not accessible outside of IBM's firewall.
 > >They are still valid samples of what could be coded for those
 > >parameters in the options file.  Sorry for any confusion or concern
 > >these values caused.
 > >
 > >Regards,
 > >
 > >Mike Dile
 >
 > Actually, what I'd really like to be able to do is to preconfigure the
 > DSM.OPT file that we redistribute to our users.  We could preconfigure the
 > server address, network protocol, in fact everything except the nodename.
 > With the new install utility that comes with fix level 5, we can no longer
 > do this sort of pre-configuration.