Show commands


IBM provide the SHOW commands for their own use, for diagnostic gathering. Tivoli / IBM do not support the SHOW commands so it is no use raising problem reports with them if the results are not what you expect. Be aware that some of these commands are resource intensive and cannot be cancelled and some commands will try to fix problems; that is they may UPDATE the TSM database. If possible, try the commands on a test system before you use them in production. In general, you should not run SHOW commands unless you are familiar with that particular command, or TSM support personnel have asked you to run them.
Many of the older show commands are now official, as they have equivalent 'display' or 'validate' commands.

This is not an exhaustive list of SHOW commands because

  • I do not know them all
  • I have missed out some obscure commands (that is, the ones that I don't understand)

The list is split into 6.x commands issued at the client, 6.x commands issued at the server and 5.x commands.

Client Commands

Client commands can produce a lot of output that will scroll off the screen, so you may prefer to pipe them into a file. For example SHOW OPTTABLE > output.txt

Displays the active client options.
You can configure a client so it can get its option settings from either the client option file or from the server. This command will tell you which one is in use for this client.
Displays capabilities that this client has for this connection to the server. The client and server report and negotiate the capabilities that each has when a session is started by a client to a server. This show command reports the capabilities available by this server and client.
Use this to determine which trace options could be used for this client.
Use this command to find out what release and version of TSM is installed.
Displays information about the disk mappings in a Windows or a Netware Cluster.

The next five commands all apply to Windows clients

If you want to use extra capabilities like image backup, then they are provided by 'plug-ins'. You use this command to find out what plug-ins are available for this client.
TSM uses Subfile backups to backup only changed portions of files over slow network links. TSM knows what parts of a file have changed, by storing checksum information in a cache file on the client. This command will display information about the subfile cache, if the client is configured to use subfile backup.
You use this commands to find out what system facilities are installed, and which ones can be backed up with TSM.
Displays the SYSTEM SERVICES data that is available on this client. Useful to determine which SYSTEM SERVICES files are installed on this Windows client and those that could be backed up.

Server commands

Simply displays the server date and time.

Current Date and Time on the Server
04/17/2012 11:08:08

UTC (GMT) Date/Time is: 04/17/2012 10:08:08
Last Noted Date/Time is: 04/17/2012 10:45:51
Daylight Savings Time is in effect: YES

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 could be worth running as a diagnostic data gathering exercise in a problem situation.

Commands to help with session or tape drive problems

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.
Is also useful if you have problems with drives. It displays the status of each device class, including the status of allocated drives.
Useful for determining which volume is in-use by a given mount point and other attributes for the assigned mount points.
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.
This command will list out the total number of usable slots in a SCSI library. The Full command is

SHOW SLOTS libraryname

You can use this command to make sure that all your tapes are checked into your tape library. Start with the command below, where LIBRARY_NAME is your library name.

select count(*) from libvolumes where library_name='LIBRARY_NAME'

If the number this command produces looks to be too low, you can use the SHOW SLOTS LIBRARY_NAME command to examine what is in the library. If a slot contains a checked in tape, its status will be 'Allocated' while slots that have a status of 'Full' contain tapes that are not checked in.

A very useful command that shows the status of all libraries attached to a server, and all their drives. Some of the parameters include
busy; either 1 (busy) or 0 (not),
online; 0 means a drive is offline
polled; 1 means TSM can't use a drive, either because it has a problem, or because something else is using it

Commands to help manage the database and recovery log

This command shows client and admin schedule variables and statistics. An example is
Displays the next execution time for client and admin schedules.
Use this command to displays the database transaction table. Sample output looks like

This is showing that this transaction has 4 database tables open, that the transaction is valid, and that it is not writing log records.

Shows statistics for the transaction manager. This command can be used to find which thread or process is using excessive database locks. Start from the DB2 command line (the database section tells you how to open this) and run command

$ db2 get snapshot for all applications > snapshot.txt

Then from the DB2 command line run

SHOW TXNT > txnt.txt

Now search the snapshot.txt file for string 'Locks held by application' and look for an application that is holding a lot of locks, 1,000,000 or more could be considered excessive. When you find one, look up from this line a bit for a line that looks like

    Application handle            = 2109

Now check out your txnt.txt line, searching for '2109'. You should find the relevant application handle in there, in a section that looks like

Tsn=0:2142362, Resurrected=False, InFlight=True, Distributed=False, Persistent=True, Addr 13528572
Start ThreadId=49, Timestamp=11/07/15 09:24:42, Creator=bfdedup.c(10369)
Last known in use by ThreadId=47
Participants=1, summaryVote=ReadOnly
EndInFlight False, endThreadId 0, tmidx 0, processBatchCount 0, mustAbort False.
Participant DB: voteReceived=False, ackReceived=False
   DB: Txn 122590f32, ReadOnly(NO), connP=135220d04, applHandle=2109, openTbls=0:
   DB: --> RegSqlId=0x0100003D INSERT for table=BF.Queued.Chunks, executed(Yes).
   DB: --> RegSqlId=0x0100003E DELETE for table=BF.Dereferenced.Chunks, executed(No).

you can see that this process is running a DELETE on the table BF.Dereferenced.Chunks. This is part of the file expiration process, so you can either run file expiration more frequently to reduce the number of de-referenced chunks being processed in one operation, or you could increase the database lock list. IBM technote explains how to do this.

Displays database global attributes.
Use this command to get details on the latest full and incremental database backup volumes.
SHOW Archives Policy-set Node-name
Shows archives for the specified node within a policy set

Commands to help with session hangs

If your TSM server is running very slow it is worth trying this command. A TSM server uses locks to serialise updates to prevent corruption. You use this command to see what resources are locked.
The TSM server monitors resource usage and will cancel any resource users that are holding onto resources for too long. You use the SHOW RESQUEUE command to display the resource queue and it will display information about transactions, locks, and other resources. The only output I have ever seen for this command is

RESOURCE Timeout is 60 minutes.
Resource list is unlocked.
There are current no waiters.

Useful for diagnosing hangs or other general session problems while a session is still connected to the server. This is also useful in cases where a session is cancelled or terminated and still appears in QUERY SESSION.

*** Warning *** The SHOW SESSION command can crash a TSM server that is between code levels 5.5 and 6.3 IBM Technote swg1IC82490 refers

You use this command to get information about active server transactions. Transactions are the low level operations that actually read or update the database. This command can be useful for diagnosing hangs or other transaction related problems, but the command produces a lot of output, and many of the fields are a bit obscure. Partial output for one single transaction is shown below.
SHow INVObject 0 ObjectId
Use this command to show an inventory object, reporting its nodename, filespace, management class, and more. This command can be useful if you get errors with objects. For example, when exporting a server you may see a message like

ANR9999D xibf.c(664): Return code 87 encountered in writing object 0.9041317 to export stream.
ANR0661E EXPORT SERVER: Internal error encountered in accessing data storage.

The 0. 9041317 is the Object ID. If you use the SHOW command

SHow INVObject 0 9041317

The result below will tell you what the object is

OBJECT: 0. 9041317 (Backup):
Node: ACSN08 Filespace: /y2. /msg/rlds/ temp
Type: 2 CG: 1 Size: 0.0 HeaderSize: 0

State: 1 Type: 2 MC: 1 CG: 1
/y2 : / msg/rlds/ temp
Active, Inserted 08/01/03 07:58:58

Expiring object entry not found.

will display all the defined database object names, along with their numeric node identifier. Output looks like

Defined Database Object Names (Home Address):

Activity.Log(49), Activity.Summary(50),
Administrative.Attributes(37), Administrators(40), etc..

Storage pool and LAN free and library commands

Useful for displaying the states and attributes of defined storage pools.
SHow DAMAGED poolname
Contributed by Roy Adeyosoye, This command will list out all the files in a storage pool that are marked as damaged. Typical output looks like

Volume ID: 34281, Volume Name: QZ1720
Segment number: 1, Segment start: 1606,
Segment Size: 0.85470464
Found 4349 damaged bitfiles.

To fix them, run an audit command like



New with TSM 7.1.3, use this command to check on the free space position in a directory-container storage pool. A QUERY STGPOOL command will show the free space in the pool including freespace within allocated containers. This show command splits that free space up into free space within the file system and within the containers. Typical output is:

SD Pool PTFM-VE (25):
  Needs Refresh:          False
  Maximum Size:                0
  FsCapacity:          109025280 MB
  FsFreeSpace:                 0 MB
  CntrAllocSpace:      108980607 MB
  CntrUsedSpace:        72545862 MB
  CntrFreeSpace:        36434745 MB
  PoolCapacity:         08980607 MB
  PoolFree:             36434745 MB
  Reserved Space:              0 MB
  Last Space Check: 01/13/16 14:38:12

You use this command to get statistics from the last migration process, for example -


Statistics for last migration from pool BACKUPPOOL
  Start date/time: 05/26/04 02:30:21
  Elapsed time: 24128 seconds
  Total wait time: 17232 seconds
  Number of participating processes: 2
  Total duration of all processes: 48169 seconds
  Total physical files: 11934
  Total logical files: 316992
  Total bytes: 273999794176
  Average logical files per physical file: 26.6
  Average physical file size: 22421.5 KB
  Number of batch/file transactions ended: 782
  Number of batch transactions aborted: 0
  Number of file transactions started: 0
  Number of file transactions aborted: 0

SHOW LANFREE nodeName storageAgent.
This command was added with TSM version 5.2.2. It will check out all possible destination storage pools for a given client node and tell you if this storage pool can support LAN-free backup and restore.
It has been superceded by the official 'validate LANFREE nodeName storageAgent' command.
Show NODE number
Will display details of one of these nodes

Show Node 49

B-Tree ROOT node: PageAddr=49, Lsn=121563.242.2284, ObjName=Activity.Log LeftSib=-1, RightSib=-1, Continuation=-1 NumRecs=2, Free=994, NextSlot=163, DirOff=0, PartKeyLen=0 Level=2, NumCols=19, KeyCols=2, PartCols=0, NodeAttr=80 MaxCapacity=1004, Capacity=1004, Occupancy=10, LowOccupancy=334
  Record 0 (KeyLen=9, DataLen=4):
  Key: ->(,.....)(002D)< -
Record 1 (KeyLen=2, DataLen=4):
  Key: ->(+Infinite)(+Infinite)< -

gives details about the data in a tree
This command used to be used to fix problems where data is not being expired correctly. It has now been replaced by the command CLEANUP EXPTABLE [BEGINNODE=nn ENDNODE=NN]. You must discuss and agree with IBM before running this command, as it updates your database. Once you start this command it cannot be cancelled, and will prevent EXPIRE INVENTORY from running.
The Syntax of the command is

Show Versions nodename filespace_name HL_name LL_name

Where the HL_name and LL_name are optional and represent the directory path and filename.
This command shows the status of a file backup (active or inactive) the date it was created, the date it went inactive and other data. If the inactive date is 'Deactivated 1900-01-01 00:00:00.000000' then this backup has been marked as ready for deletion and will be deleted next time expiration runs.


You can use this command if your logfile is running out of space. The oldest active record in the log is 'pinning' the log. This command will tell you what task owns that oldest record. You could follow this up with
which will cancel whatever is holding the pinned record. This is one of those 'UPDATE' SHOW commands that you need to use with extreme care, and preferably after advice from Tivoli. However, if your log is rapidly filling up, will you have time to make that support call? It would be best to investigate and test this command before you need to use it in an emergency. The command is only available in TSM version to 5.5.
Example output is

Dirty page Lsn=4597153.124.2199, Last DB backup Lsn=4596680.43.3348, Transaction table Lsn=4597152.240.3249, Running DB backup Lsn=0.0.0, Log truncation Lsn=4596680.43.3348

Lsn=4596680.43.3348, Owner=DB, Length=194
  Type=Update, Flags=C2, Action=ExtInsert, Page=2171054,
  Tsn=0:818261705, PrevLsn=4596680.43.3137, UndoNextLsn=0.0.0,
  UpdtLsn=4596680.43.3137 ===> ObjName=AS.Segments, Index=26,
  RootAddr=14, PartKeyLen=3, NonPartKeyLen=4, DataLen=87

The recovery log is pinned by the last data base backup.
Space will not be freed until data base backup is run again.

The command tells you that the log is pinned by a backup.

Use this command to see if you need to increase your database buffer pool size.
Example output is
This command will display the status of the buffer pool variables and can be used to check for dirty buffer pages.
Example output is

Database buffer pool global variables:
  CkptId=1642081, NumClean=32880, MinClean=32784, NumTempClean=32880,
  BufPoolSize=32880, BufDescCount=33071, BufDescMaxFree=36168, DpTableSize=49161, DpCount=0, DpDirty=10, DpCkptId=1642081, DpCursor=64, NumEmergency=0 CumEmergency=0, MaxEmergency=0. BuffersXlatched=0, xLatchesStopped=False, FullFlushWaiting=False.

The above output shows that there are 10 dirty buffers. You use another undocumented command 'FLUSH' to clear out the dirty buffers.

Displays usage information for the recovery log and database
This command shows the status of the database and recovery log copy table and is included in SHOW LVM above.
This command shows logical volume manager data, including lots of information about TSM volumes.

The following commands came from the site belonging to Michael Malitz,

show dedupdeleteinfo
Displays the status of background deletion threads for dereferenced deduplicated objects. Issue this command to check the status of the background deletion process for deduplicated objects. When a file is deleted or moved out of a deduplicated storage pool, the extents are queued to a background processor for attempted removal from the storage pool. This command is useful for checking the backlog of queued extents and the status of each deletion thread.
show deduppending <stg–pool–name>
Shows the pending amount of data that will be removed.
show replication
Shows all known replication servers and their globally unique identifier (GUID) and all running replication processes. The processes might include the individual statistics of each file space and the status of each replication session. Issue this command if replication does not appear to be progressing or if replication is not working correctly.
show versionhistory
Displays the installed TSM version(s) on the TSM server.
show tocsets
A TOC set is used during file-level NDMP operations ( or BACKUPSETS ). During an NDMP backup with the TOC=YES parameter, a TOC is built in the server database. During a restore, one or more TOCs might be loaded into the server database to provide file and directory names to the client GUI. This command shows the status of the TOC set; for example, building or loading, and how much temporary database space is in use for each TOC set. You might issue this command if you are experiencing problems with an NDMP backup with the TOC=YES parameter, or have problems restoring files from an NDMP backup, or if TOC sets are being retained in the server database too long or not long enough.
show VM all
show all virtual machines in ESX(I) or vCenter from the DSMC – BA Client point of view.