APAR status
Closed as program error.
Error description
* Environment: ITM 6.2 / 6.2.1 single box installation * Problem Description: Situation no longer firing under a particular scenario * Detailed Recreation Procedure: 1) Create a situation like the following one: [root@nc114079]/opt/IBM/ITM/bin# tacmd viewsit -s my_user_sit Name : my_user_sit Description : Type : UNIX OS Formula : *IF *VALUE User.Login_Name_U *EQ 'db2inst1' Sampling Interval : 0/0:15:0 Run At Start Up : Yes Distribution : nc114079:KUX ... Add a Display Item to this situation. 2) Start the situation and verify it is working as expected (mine fired at 17.35) 3) Modify the same situation and add a situation comparison condition like below: [root@nc114079]/opt/IBM/ITM/logs# tacmd viewsit -s my_user_sit Name : my_user_sit Description : Type : UNIX OS Formula : *IF *VALUE User.Login_Name_U *EQ 'db2inst1' *AND *SIT Weekday *EQ *TRUE Sampling Interval : 0/0:15:0 Run At Start Up : Yes Distribution : nc114079:KUX ..... (I did this at 17.37) 4) You might want to verify that the Display Item defined in step (1) is no longer defined because of the "error" KFWITM052E The Display Item Feature cannot be used with this Situation because it includes attributes from more than one Group: "Weekday and User". 5) Restart the situation and verify that this is not firing anymore and the user is not notified of any problem. * Related Files and Output: - ECUREP Dir : /ecurep/pmr/6/9/69159,057,649/support_files File: mylogs.zip The UX agent log files show that the "Agent" is sending "1" row when evaluating User.Login_Name_U *EQ 'db2inst1' and then "1" row when evaluating Weekday -> kuxagent log: -------------------------------------------------------------- ... (2009.069 17.37.13-5:kraadspt.cpp,270,"sendDataToProxy") Sending 1 rows for my_user_sit OMUNX.UNIXUSER, <30409247,51381209>. ... (2009.069 17.37.13-5:kraadspt.cpp,270,"sendDataToProxy") Sending 1 rows for Weekday KPX.LOCALTIME, <30409245,30409688>. ... -> tems log: (2009.069 17.37.13-7:ko4sit.cpp,690,"Situation::slice") Sit my_user_sit: Hub-interest - sending S record. (2009.069 17.37.13-7:ko4sit.cpp,1722,"Situation::updateHub") Entry (2009.069 17.37.13-7:ko4sit.cpp,1745,"Situation::updateHub") Exit (2009.069 17.37.13-7:ko4sit.cpp,696,"Situation::slice") Sit my_user_sit: Scheduling to watch for reports. * Approver BS
Local fix
Problem summary
When adding attribtues to a situation definition there is an advanced button that allows for a "display item" to be set. This option should not be allowed if the situation definition is one that contains an embedded situation. The monitoring server will not fire the situation correctly if this is set.
Problem conclusion
Several checks in the situation editor have been added to enforce rules covering the use of embedded situations and display items in the same situation formula. 1. Added a check when the advanced tab is selected in the situation editor to check the situation formula to see if it contains an embedded situation. If an embedded situation is found, the "display item" tab is disabled and a message appears in the "Advanced Situation Options" dialog explaining why the option is disabled (greyed out). 2. If a situation is created and the attribute contains a "display item" and the user attempts to add an embedded situation to the formula, only the "Attribute Selection" dialog will be displayed. The user will not be able to select an embedded situation for inclusion in the situation formula. 3. If the user opens a previously saved situation which contains an embedded situation and display item, when trying to save the situation, the user will receive an error message in the status area of the situation editor dialog explaining why this situation formula cannot be saved. 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
IZ48008
Reported component name
TEP
Reported component ID
5724C04EP
Reported release
620
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-04-01
Closed date
2009-07-01
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