Tsm Show Slots Command
Tsm Show Slots Command Rating: 7,3/10 83 reviews
- Joined
- Feb 27, 2006
- Messages
- 12
- Reaction score
- 0
- Points
- 0
- Location
- Spain
- Website
- Visit site
Hi, guys.
Recently, I tried to checkin some volumes (according to library GUI, there were 6 free slots), but TSM said it was not possible, as library was full.
A little surprised, a took a 'Show slots', and I discovered that, all right, there was no free slot ('element').
I browsed the library GUI, and took notice of the missing element's number. Boy, they were missing: they are NOT in the 'show slots'. They simply doesn't exist for TSM. For instance: library shows an empty '4118' element but the 'show slots' says nothing of this element number (or another 5).
My question: is there any place to indicate TSM the existence of these 'elements'/'slots'? Is there any 'definition' file for the library? Any manual way of telling TSM about the real situation. I always assumed that TSM would 'talk' to the library thu the device drivers, and in fact this is the only way I recall, TSM taking notice of the library configuration and possibilities.
For the record: we have re-audited the library and restarted the TSM server, but to no avail. Library is fully licensed, and we're using a TSM 'enterprise license' duly registered. Can not say if this is a new situation or not, as this is the first time we run into this 'library full' situation. I'm trying not to go to a full re-definition of library, paths and drives, as this is cumbersome and, besides that, there is no guarantee whatsoever this could be solved that way. Finally, we do DRM, with lots of tapes coming and going, but I don't see how DRM has to do with the fact a 'show slots' is unable to 'see' the real library configuration.
Any idea or hint would be greatly appreciated.
Recently, I tried to checkin some volumes (according to library GUI, there were 6 free slots), but TSM said it was not possible, as library was full.
A little surprised, a took a 'Show slots', and I discovered that, all right, there was no free slot ('element').
I browsed the library GUI, and took notice of the missing element's number. Boy, they were missing: they are NOT in the 'show slots'. They simply doesn't exist for TSM. For instance: library shows an empty '4118' element but the 'show slots' says nothing of this element number (or another 5).
My question: is there any place to indicate TSM the existence of these 'elements'/'slots'? Is there any 'definition' file for the library? Any manual way of telling TSM about the real situation. I always assumed that TSM would 'talk' to the library thu the device drivers, and in fact this is the only way I recall, TSM taking notice of the library configuration and possibilities.
For the record: we have re-audited the library and restarted the TSM server, but to no avail. Library is fully licensed, and we're using a TSM 'enterprise license' duly registered. Can not say if this is a new situation or not, as this is the first time we run into this 'library full' situation. I'm trying not to go to a full re-definition of library, paths and drives, as this is cumbersome and, besides that, there is no guarantee whatsoever this could be solved that way. Finally, we do DRM, with lots of tapes coming and going, but I don't see how DRM has to do with the fact a 'show slots' is unable to 'see' the real library configuration.
Any idea or hint would be greatly appreciated.
- The volume A00004L3 in slot 4106 is in the library TS3310 but not in the TSM's inventory database. Please either check in this volume or remove it from the library. This is what i got when trying to check it out.
- Tsm Show Slots Command, quidco gambling cashback, casino financier manila, idaho gambling history.
In version 5.2.2 of the TSM server, the SHOW LANFREE command was added. This will evaluate all possible destination storage pools for this client node and report whether or not the storage pool is capable of LAN-free data movement operations. The syntax is SHOW LANFREE nodeName storageAgent. Return to list of show commands.
Disclaimer
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.
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 commands issued at the client and commands issued at the server.
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 these commands to find out what system facilities are installed, and which ones can be backed up with TSM. SYSTEMOBJECT is used for Windows 2000 and XP clients, and SYSTEMSTATE for Windows 2003 clients.
For Windows 2003 clients, 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
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.
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
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.
Commands to help manage the database and recovery log
Use this command to see if you need to increase your database buffer pool size.
Example output is
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
Example output is
The above output shows that there are 10 dirty buffers. You use another undocumented command 'FLUSH' to clear out the dirty buffers.
Use this command to displays the database transaction table. Sample output looks like
Tsm Show Slots Command Bot
This is showing that this transaction has 4 database tables open, that the transaction is valid, and that it is not writing log records.
Displays database global attributes.
Use this command to get details on the latest full and incremental database backup volumes.
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
SHOW LOGPINNED CANCEL
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 5.1.7.0 or above.
Example output is
SHOW LOGPINNED CANCEL
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 5.1.7.0 or above.
Example output is
The command tells you that the log is pinned by a backup.
You can use this command to display the recovery log global attributes, but it is less obvious what they all mean.
Use this command to see statistics on log usage.
An associated command is SHOW LOGRESET This command will RESET the log statistics back to 0.
Tsm Show Slots Command Block
SHOW LOCK
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
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.
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.
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
The 0. 9041317 is the Object ID. If you use the SHOW command
Storage pool and LAN free commands
Useful for displaying the states and attributes of defined storage pools.
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
SHOW SLOTS
This command Will list out the total number of usable slots in a SCSI library. The Full command is
You use this command to get statistics from the last migration process, for example -
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.
will display all the defined database object names, along with their numeric node identifier. Output looks like
Will display details of one of these nodes
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.