As of ITM 6.2.1, there is a perceived capability to now rename situations within the editor.

However, the rename is actually a new attribute called ‘Full Name’ and only changes the TEPS display name for the situation; the EIF will still send the original situation name.

IBM responds this is “working as designed” — a load of crap if you ask me and a “feature” that should not have been introduced at all if it were to be so counter-intuitive.

Here’s IBM’s response:

Problem(Abstract)
Situation names that are less than 32 characters in length do not populate the “Fullname” field when running the ‘tacmd viewsit -s ‘ command.

Symptom
tacmd viewsit shows null Fullname Field

Cause
The Fullname field is only populated when the original situation name is 32 characters or greater or if a situation name is changed.

Resolving the problem
When a situation is created with a name less than 32 characters in length, the situation name is stored in the “Name” column. At this point, the “Name” column serves two purposes: a unique ID for the situation and the situation display name. The “Fullname” column is blank.

If an existing situation name is changed, the “Name” column still serves as the unique ID and will not be updated to reflect the situation name change.

The new situation name is stored in the “Fullname” column, the new name now assumes the role of situation display name. The length of the new name does not matter, the new name must be stored in the “Fullname” column, since the “Name” column containing the unique ID cannot be changed.

The only time we should expect the “Full Name” field to be populated is when the original situation name is 32 characters or greater or when a situation name has changed from it’s original name (regardless of the length of the new situation name).

Situation

An ITM6 Unix (UX) or Linux (LZ) agent detects that its remote filesystems are unavailable, a “stale” connection.

Automate an action to remount it if possible

Methodology

Two (2) ITM situations are created where

1. detects the mount point has become stale
   
2. the other is triggered by the “correlated situation” condition of #1 being tr
   

Situation #1 : Detect “Stale” remote FS

Simple enough – if “Space Available” fails collection, there is an issue

Situation #2 : Remount Situation

Formula Conditions

Use the “Situation Comparison” for a condition against the situation above

Take Action

Note: the lines are strung together on one line in the Take Action field, to make it more legible here, newlines are after the semicolons

f=”&{Linux_Disk.Mount_Point}” ;
u=`umount -f $f 2>&1 && echo $f`;
m=`mount $f 2>&1 && echo $f`;
echo -e “umount: $u\nmount:$m” | mail -s “ITM ACTION: Remount $f” junkmail@JdsMedia.net

Based on http://publib.boulder.ibm.com/infocenter/tivihelp/v24r1/index.jsp?topic=/com.ibm.itm.doc/itm_admin_6284.htm

The following table describes the meaning of the situation event statuses and the setting of the common slots in the generated Tivoli Enterprise Console event.
Read the rest of this entry »