>
> Yes - that's why I recommended that others pursue that avenue.
> The most recent Technical Guide is at the top of the results...which
> you then click to and acquire a copy of the guide.
>
> I cite methods for going at documents, rather than detailed URLs, for
> several reasons...  First and foremost, URL elements internal to site
> locations can be highly volatile, and change over time.  Keep in mind
> that our postings are archived, and a detailed URL could well be
> useless to someone doing TSM problem research a month from now.
> Prescribing the most reliable method to get to the info, here and
> later, is the most generally useful.  My second reason, beyond
> showing methodology, is to expose contextual documentation beyond the
> single objective, for general awareness of the availability of such
> information as it aids better understanding of a complex product.  In
> this case, for example, one who hasn't looked much at the Redbooks
> will realize that the Technical Guide has been produced for numerous
> versions and releases of ADSM and TSM, where each provides a unique
> understanding of then-introduced features which carry forth through
> the most current incarnations of TSM.
>
>     Richard Sims

Well stated Richard.  It's the old "Give a man a fish... teach a man to
fish..." parable.  Practicing finding documentation (for any product or
vendor) when things aren't falling apart makes it much easier to find the
documentation when things are.

On the left side of the http://www.redbooks.ibm.com page, toward the bottom
of the button stack, is one titled "Mailing List."  Each Monday (usually)
you'll get an email detailing the new redbooks, drafts, redpieces, and
notices of residencies and workshops.


Nick Cassimatis