Richard Sims has collated a large store of 'colloquial' TSM information into a document called the ADSM/TSM QuickFacts. The substance of the QuickFacts was used to flesh out the starting contents of this Wiki. View the original QuickFacts here;
Some of the information in the QuickFacts has been collected from the ADSM-L, a ListServ email discussion group providing support, general knowledge and discussion of the TSM products.
An indexed and HTML-ified version of the QuickFacts can be found at;
Included here is the pre-amble from the TSM QuickFacts. I'm including this here because I think it echo's many of the reasons I decided to put up the Wiki.
ADSM/TSM QuickFacts
in alphabetical order, supplemented thereafter by topic discussions
as compiled by Richard Sims (r b s @ b u . e d u),
Boston University (www.bu.edu), Office of Information Technology
On the web at http://people.bu.edu/rbs/ADSM.QuickFacts
Last update: 2005/06/21
This reference was originally created for my own use as a systems programmer's
"survival tool", to accumulate essential information and references that I knew
I would have to refer to again, and quickly re-find it. In participating in the
ADSM-L mailing list, it became apparent that others had a similar need, and so
it made sense to share the information. The information herein derives from many
sources, including submissions from other TSM customers. This, the information
is that which everyone involved with TSM has contributed to a common knowledge
base, and this reference serves as an accumulation of that knowledge, largely
reflective of the reality of working with the TSM product as an administrator.
I serve as a compiler and contributor. This informal, "real-world" reference is
intended to augment the formal, authoritative documentation provided by Tivoli
and allied vendors, as frequently referenced herein. See the REFERENCES area at
the bottom of this document for pointers to salient publications.
Command syntax is included for the convenience of a roaming techie carrying a
printed copy of this document, and thus is not to be considered definitive or
inclusive of all levels for all platforms: refer to manuals for the syntax
specific to your environment.
Upper case characters shown in command syntax indicates that at least those
characters are required, not that they have to be entered in upper case.
I realize that I need to better "webify" this reference, and intend to do so in
the future. (TSM administration is just a tiny portion of my work, and many
other things demand my time.)
In dealing with the product, one essential principle must be kept in mind, which
governs the way the product operates and restricts the server administrator's
control of that data: the data which the client sends to a server storage pool
will always belong to the client - not the server. There is no provision on the
server for inspecting or manipulating file system objects sent by the client.
Filespaces are the property of the client, and if the client decides not to do
another backup, that is the client's business: the server shall take no action
on the Active, non-expiring files therein. It is incumbent upon the server
administrator, therefore, to maintain a relationship with client administrators
for information to be passed when a filespace is obsolete and discardable, when
it has fallen into disuse.