APAR status
Closed as program error.
Error description
ENVIRONMENT: ITM 6.2 FP01 on Windows 2003 PROBLEM DESCRIPTION: When a situation opens, the server updates items associated with the situation and their parents in all opened views. The server updates parents even if the associated child is not in the view. However: When a view is opened, the server doesn't update the parents if the child associated with the situation is not in the view. Why do we need this behaviour? In view TEST_2, if you add an Event Console, you see the Situation with "Impact" set to CHILD even if CHILD is not in the View. Our client needs such behaviour in order to give a view to some users, showing them alerts informing about the impacted element (CHILD for instance) but without giving them access the specific workspaces and information associated with the child. RECREATION STEPS: Steps to reproduce: 1. Create a situation that is always true: - Open the situation editor - Create a new situation under "All managed Systems" - Name it "TEST" - Select "Attribute Group" "Local Time" and "Attribute Item" "Hours" In formula enter: < 24 - Sampling every 30 sec. - Distributed to *HUB. - Stop the situation. 2. Create 2 logical views with a common Item: - Create a Logical View called TEST_1 (In the navigator click "Edit Navigator View" and Then "Create New Navigator View") - Add a Child Item to TEST_1 called ITEM - Add a Child item to ITEM called CHILD - Create another Logical View called TEST_2 - Drag and Drop CHILD from View TEST_1 to View TEST_2 - Delete child item CHILD from item ITEM in View TEST_2 You should obtain the following configuration: (see image INC_002.jpg) 3. Associate the situation: - In the "Navigator View" choose the Logical View TEST_1 - Edit properties for Item CHILD and assign *HUB to it - Edit situations for Item CHILD and associate the situation with it. 4. See the behaviour: (The situation should be stopped now) - Open logical views TEST_1 and TEST_2. - Start the situation. The situation is shown in both Logical Views: In TEST_1 for the 3 Items because it impacts CHILD In TEST_2 for the 2 items because it impacts an ITEM child item in another view. This is perfect. Close Logical View TEST_2. (Right click on TEST_2 in the Navigator and choose "Remove") Reopen TEST_2. This time the situation is not shown. That's the problem. Restart the situation and then it is shown again in both views. RELATED FILES/OUTPUT: n/a APPROVER: MB
Local fix
Workaround: The workaround to this problem is to remove the View and then select it again and the alert will not be displayed.
Problem summary
If a user has two custom topology views, each containing a node named ITEM that is shared between both topologies, any situations associated to ITEM will appear as alerts in both topologies. If in one of the topology views ITEM has a child node named CHILD, any situations associated to CHILD will roll up the topology branch and appear on the ITEM node also. However, in the topology where ITEM exists but CHILD does not, the situations associated to CHILD will not appear on the ITEM node.
Problem conclusion
Modified the snapshot code to iterate over all tree branches that have events, regardless of the topology the branch is located in. The fix for this APAR is contained in the following maintenance packages: | interim fix | 6.2.0.3-TIV-ITM-IF0001
Temporary fix
Comments
APAR Information
APAR number
IZ33610
Reported component name
TEMS
Reported component ID
5724C04MS
Reported release
620
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-09-30
Closed date
2009-06-29
Last modified date
2009-07-21
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
TEP
Fixed component ID
5724C04EP
Applicable component levels
R620 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSCTLMK","label":"ITM Tivoli Enterprise Portal V6"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"620","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
21 July 2009