Creating appropriate ITM situation names to avoid future restrictions
AishaSaini 270007RH3Y Visits (13465)
It all starts with what you name your situations. If you do not have unique names you could potentially cause greater problems for yourself and your environment.
When creating the name of a situation the ITM6.3 FP02 manual says:
‘The situation name can contain any UTF-8 characters and can be up to 256 bytes long. The number of characters allowed varies depending on the characters used, because some UTF-8 characters require more than one byte.’ (Page 259)
Please note when creating situations TEPs does not officially support situations with the same name with different cases, for example let’s have two situations: NT_missing_calc and NT_Missing_calc.
Windows and TEPS will recognise them as the same. Despite Linux being case sensitive TEPS will also perceive them as the same. The situations will work as normal and can trigger, however, it has led to issues such as not appearing in Managed Situation. Managed Situation will only show one of the above situations (usually the first one that was created if not renamed). When creating situations it is very important to create unique distinguished names to avoid any restrictions.
How you would see the problem:
After testing using ITM6.3 FP02 on Windows and ITM6.3 FP03 on Linux I had the exact same results as is shown by:
(Here I am using ITM6.3 FP02 on Windows)
Both situations NT_missing_calc and NT_Missing_calc have been created.
Both situations trigger as normal.
Managed Situation is in alphabetical order and only one of the similar named situations has appeared.
Assume we have two situations A and B which trigger as normal but don’t appear in Managed Situation, where A and B have similar names.
Both situations should be appear and function properly. If not please contact IBM ITM for support.
Feel free to follow me on LinkedIn: