Technical Blog Post
Abstract
ITM Nuggets: SPUFI Use Case 2: Retrieve LIVE information on which situations are started, stopped, deleted, etc CLI
Body
On the third installment of the SPUFI series, we look at our second "use case". This blog will show you how to extract key information via the
command line from your TEMS relating to which situations are started, stopped, deleted or in error in you ITM infrastructure. This is a very
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: --->
Overall Goal
- You can use this method to sanity check which situations are active/evaluating and therefore you can get events from.
- You can check how many situations you have running on each HUB and RTEMS from a loading point of view.
- You can see if you have situations running on RTEMS that have no agents of that type connecting to them, or the reverse. You have agents connected to an RTEMS but situations that should be running have not be started there.
Understanding the process
Name of Column | Information held in that column |
DELTASTAT | Delta stat is a single letter that represents the status of that row (full table below) |
GBLTMSTMP | Time that the record was written |
NODE | This will be an endpoint name associated with that record |
ORIGINNODE | Name of the TEMS the agent directly reports to (also known as throughnode) |
SITNAME | Situation name that created the event |
FULLNAME | Situation full name if it has been given one (6.21 and beyond) |
The key to understanding the output is again the "Deltastat" column, it will have a single letter in it and this shows you the status of that situation.
DELTASTAT Column Value | Meaning of the letter |
S - Situation Started | The situation with the name on the same line has been started |
P - Situation Stopped | The situation with the name on the same line has been stopped |
D - Situation Deleted | The situation with the name on the same line has been deleted |
X - Error | The situation with the name on the same line has an error |
Now you know how to read the data, you need to understand the processing of the TEMS. Any action performed with a situation will insert a corresponding row to the TEMS ISITSTSH 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:
Note: Replace the 'S' with any delta stat letter you wish to pull information on. The example above will show you all situations that are started as its an 'S'
in the WHERE clause.
Result
Here is an example output from my test system:
I have pulled multiple criteria on this SQL call. This shows all the started and stopped situations in my environment. ('S' and 'P')
What next?
Link to all blogs in the "nuggets" series
Please feel free to link with me on
htt | |
htt | |
uk. |
Check out all our other posts and updates:
Academy Blogs: ht
Academy Videos:
Academy Google+:
Academy Twitter Handle:
UID
ibm11082697