David,

I understand your frustration to a certain extent.  But what do you mean
with "change the rules on installation"?  Ever since V3 GA the installation
rules for the Sun clients have been identical.  The only change introduced
with 3.1.0.6 was that the package structure was simplified by removing the
wrapper script from /opt/IBMadsm-c and move the real binaries that used to
be in the sol251 or sol26 subdirectory (for V3, there never was a solaris
subdirectory), to the installation base directory.  This was done
specifically to make the Sun packages become more consistent with the
other UNIX ADSM client packages.

I'm sorry to hear that this internal change that did not affect the
installation procedure nor the usage of the ADSM client on Sun apparently
broke some of your scripts that obviously relied on the internal package
structure of the ADSM client.  Maybe if you could be a little more
specific as to what problems the new package structure caused for you
we would be able to help.

Anyway, I agree that modifying the internal package structure as part
of a PTF release was not a good idea.  We'll take care to not let this
happen again in future PTF's.

David Hendrix wrote:
>I am getting really tired of IBM CONSTANTLY changing binary/directory
>locations for Solaris clients.  How about this chronology:
>
>Version 1: /opt/IBMadsm-c
>
>Version 2: /opt/IBMDSMba5 ap5 blah, blah blah
>
>Version 3: /opt/IBMadsm-c/solaris
>
>Version 3.1.0.6: /opt/IBMadsm-c/solaris isn't there anymore.
>
>This is ludicrous!  HP hasn't changed.  AIX hasn't changed.  For some
>reason, those in the solaris camp can't quite decide WHERE they want to put
>the software.  Get your act together and stop changing these locations.  It
>makes my job that much harder because you change the rules on installation,
>which then screws up all my scripts.
>
>Can you tell I'm upset IBM?!  It's one of those small things which bugs me
>to no end.

Best regards,

Christian Bolik
IBM SM IT Software Development ADSM, Mainz