Welcome to the
Wonderful World of Situations Blog
John Alvord, IBM Corporation firstname.lastname@example.org Draft #1 – 6 August 2020 – Level 0.50000 Follow on twitter Inspiration Benchmarking ITM communication links is a tough job. You can validate many aspects using this document ITM Communications Validation But testing for throughput and capacity and errors is tough. Happily a former ITM developer implemented a techniqueContinue reading “Sitworld: Simple Network Testing”
John Alvord, IBM Corporation email@example.com Draft #5 – 20 August 2020 – Level 0.61000 Follow on twitter Inspiration Duplicate agent names in a ITM environment present a multi-dimensional horror. That is when two different agents with the same name are connecting to a remote or hub TEMS. Here are the bad things that can happen:Continue reading “Sitworld: Eliminating Duplicate Agents”
Version 0.51000 23 March 2020 John Alvord, IBM Corporation firstname.lastname@example.org Follow on twitter Inspiration ITM has an marvelous facility to store historical data. This facility includes logic to discard old data and summarize data into longer time periods. It is quite easy to get more data recorded but balancing that with the limited database storageContinue reading “Sitworld: Summarization and Pruning Audit”
John Alvord, IBM Corporation email@example.com Draft #1 – 1/16/2020 – Level 1.00000 Follow on twitter Inspiration I am often asked for advice on how to change an ITM process configuration. It could be something simple like adding a diagnostic trace definition. It could be more complex like adding EPHEMERAL:Y to a communication control. There areContinue reading “Sitworld: ITM Permanent Configuration Best Practices”
Table of Contents
TEP diagnostic capture
Checking for common ITM communication issues.
During my normal work. I see many interesting puzzles on how to accomplish useful work in IBM Tivoli Monitoring [ITM]. Often these revolve around situations. Over time I will present some basic education on the subject but first there are some interesting cases that will benefit from some interactions. So for the moment, I willContinue reading “Sitworld: Introduction”
Sometimes there is a mistake made in ITM Windows Agent configuration. It is made with good intentions but the result is an ITM Agent which constantly loses connection to the TEMS it is configured to and then reconnects over and over.
temsaud.crit: Early remote SQL failures [&syncdist_early]
Follow My Blog
Get new content delivered directly to your inbox.