Always wanted to be able to pull all of the OS and ITM versions for every agent in your enterprise in one single action... On this installment of the SPUFI series, I will show you exactly how to do that. This is another powerful way to obtain great information from your TEMS outside the GUI.
If you missed part one on how to use the tool here is a quick link: ---> Link to blog one in the SPUFI series
The goal is to be able to pull all the required information you would need to plan upgrades or do a site evaluation of all of your ITM agents in one quick command.
There are many reasons why you would use this method, here are a few:
You can use this method to sanity check which parts of your environment are running old code
You can check how many agents you have on a specific OS platform
You can use the data obtained through ITM to perform site audits of machine types, etc
I have used this in 8-10 different ways on customer sites to help them achieve business goals (Ranging from ITM purpose, to just plain business information collection)
Understanding the process
We will be using the KDSTSNS tool with some SQL to query the "Node Save"table on the HUB TEMS, specifically the TNODESAV table.
As in the first blog of the series explained how to query the TEMS, the below information explains how to interpret the output of the SQL, so you can utilise the information for you own means. I will start by breaking down what each column means in the table we are querying and they go through a
basic example of how the TEMS processes the start/stop records. This will give you the basics to go away and try it for yourself!
Each of the rows in the below table represents is a column in the TNODESAV table on the TEMS and its meaning. You will need to query this table
on the TEMS using SQL provided to retrieve the required data.
Now you know how to read the data, you need to understand the processing of the TEMS. Any agents that connects to the ITM infrastructure will have a corresponding row added to the TEMS TNODESAV table.
How to retrieve the key information
For the method of how to retrieve the data and where to put the files. This was covered in post one in the series: Link - Blog 1
You will need to execute this SQL:
Here is an example output from my test system:
You now have the methodology and the SQL to get the data you need. You could perform health checks, audits, plan upgrades, etc. You could also open up the resulting file in a spreadsheet editor. A quick text to columns and you can filter away on a single TEMS, host, OS type to really refine masses of information down to concise quality checks.
Hope this has been of use to you. If you have any questions or you would like me to build a test case to find a specific piece of information, please post below and I will respond to you.
Please feel free to link with me on
Check out all our other posts and updates:
Academy Blogs: http://ibm.co/1sPj9E8
Academy Videos: http://bit.ly/1wFKveY
Academy Google+: http://bit.ly/1sR5QTV
Academy Twitter Handle: http://bit.ly/1CknfoF