These are various server SHow commands I’ve picked up from various sources. This is definitely not an exhaustive list, and these commands are added and dropped from TSM based on the version, these commands are not supported and may not work for you.

SHow ASQUEUED:
If you have a client session or process stuck, it may be waiting for a drive. You can use this command to see if there are sessions queued waiting for mount points.

SHow ASVOL:
If you are having problems with sessions or processes queued, or waiting for tape volumes, then this command will display the in-memory list of assigned volumes.

SHow CONFIG:
This is one of the long running commands that produce lots of output. It actually issues a set of QUERY and SHOW commands then uses these to build a quite comprehensive picture of the state of the server. This command is worth running as a diagnostic data gathering exercise, to be analysed when free time permits.

SHow CSVars:
Shows client schedule variables and statistics.

SHow DEDUPDeleteinfo:
Shows Deduplication thread information and current worker thread chunk statistics.

SHow DEDUPThread:
Shows information and statistics on Deduplication threads.

SHow DEVCLass:
Is also useful if you have problems with drives. It displays the status of each device class, including the status of allocated drives.

SHow LIBINVentory:
Shows current state of the library inventory for the library specified.

SHOW LIBINVentory [ LibraryName}

SHow LIBRARY:
Displays the current state of the specified library and all of its drives.

SHOW LIBRary [ libraryName ]

SHow LOCK:
Displays lock holders and waiters.

SHow LVM:
Shows logical volume manager info: server disk volumes.

SHow LVMCOPYTABLE:
Shows the LVM database and recovery log copy table status.

SHow LVMVOLS:
Shows database and recovery log volume usage.

SHow MEMTREnd:
This command will report the memory used by the server in megabytes, recorded at hourly intervals for the last 50 hours (this is a constant in the server code and is not user-configurable). The reported usage represents the amount of memory internal server routines request from the pseudo-kernel memory routines. It does NOT represent the total amount of memory the server is using. Nevertheless, it is still useful in determining the server’s memory usage trend.

SHow MP:
Useful for determining which volume is in-use by a given mount point and other attributes for the assigned mount points.

SHow PENDing:
Shows pending administrative and client schedules.

SHow RESQueue:
Displays the resource queue. The resource queue is used to monitor common resources on the server. Typically, this is useful for displaying information about transactions, locks, and other resources used by a storage agent on the database server that it is configured to use.

Show SLOTS:
This command displays the current state of the specified library’s slot information.

SHow SLOTS libraryName

SHow SSPool:
Displays information storage pools.

SHow SSSession:
Shows information about sessions using volumes in storagepools.

SHow TIME:
Shows the current server date and time.

SHow TXN:
Shows Transaction manager statistics.

SHow TXNTable
Displays information about transactions in-use on the server. This information is useful for diagnosing hangs or other transaction related failures while the transaction is still open on the server.

SHow VOLINUSE:
Displays information on a specified volume in the server’s in-use list. This command will display additional information that may be helpful including whether the volume is currently pending removal from the in-use list.

SHow VOLINUSE VolumeName [ REMOVE=YES ]

In order to check what level your clients are, your can run a simple select:

select node_name, -
cast (client_version as char)||'.'||-
cast (client_release as char)||'.'||-
cast (client_level as char)||'.'||-
cast (client_sublevel as char (2))-
CLIENT_LVL from nodes

Sometimes when you upgrade the server, you need a minimum level of client. Like the 6.1 server requires all clients to be at 5.5 or higher. To just see what clients are below a certain level, you can run:

select node_name, -
cast (client_version as char)||'.'||-
cast (client_release as char)||'.'||-
cast (client_level as char)||'.'||-
cast (client_sublevel as char (2))-
CLIENT_LVL from nodes where -
cast (client_version as char)||'.'||-
cast (client_release as char)||'.'||-
cast (client_level as char)||'.'||-
cast (client_sublevel as char (2))-
< '5.5.0.0'

IBM distributes the TSM clients in RPM format, but not in deb format for Debian based Linux distributions. The re are some TSM clients in deb format out there, but the latest I could find is version 5.4. I found that alien converts the RPM files decently enough.

First, install alien:

sudo apt-get install alien
Then, get all the RPMs you want to install in the same directory and run:
alien -k *.rpm
There is a problem with the install scripts that they didn't create a link on my systems:
ln -s /opt/tivoli/tsm/client/lang/EN_US/dsmclientV3.cat /opt/tivoli/tsm/client/ba/bin/EN_US/dsmclientV3.cat
After that, the client should work just as if installed on a Redhat based system.