A fix is available
APAR status
Closed as program error.
Error description
PROBLEM DESCRIPTION: Creating a situation in a situation group that is part of another situation group. Displaying situations for the group that has a nested situation group, will not display situations that are part of the nested situation group. RECREATE INSTRUCTIONS: 1) Create MSL MyLinuxServer and add LZ agent to it, lets say myserver:LZ 2) Create Situation MySituation to monitor lets say /opt > 90% 3) Create Situations Group MySitL1Group 4) Create another Situations Group MySitL2Group and add it as a member to MySitL1Group 5) Add MySituation to MySitL2Group 6) Distribute MySitL1Group to MyLinuxServer MSL 7) Select myserver:LZ in navigator, right-click -> "manage situations" 8) fail - the MySituation will NOT show up in the dialog I replicated this condition and observed that the tacmd listsit -m xxxx did not include situation MySituation. In the Agent operations log, the situation was seen to start.
Local fix
Use tacmd listsit to display all the situations that are part of any nested groups. Distributing each group individually will cause the situations to appear in the Manage Situations display.
Problem summary
In the Manage Situations dialog box, situations that are distributed to the selected agent via a nested situation group are not shown in the list of situations. Situation groups can be nested within other situation groups. If the parent situation group is distributed to a managed system or managed system list, the situations assigned to the nested group are not displayed in the Manage Situation dialog box.
Problem conclusion
The behavior has been corrected to recursively descend all nested situation groups when collecting the list of situations distributed to a managed system. The fix for this APAR is contained in the following maintenance packages: | fix pack | 6.2.2-TIV-ITM-FP0009
Temporary fix
Comments
APAR Information
APAR number
IV12563
Reported component name
TEP
Reported component ID
5724C04EP
Reported release
622
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-12-28
Closed date
2012-03-23
Last modified date
2012-06-28
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
R622 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":"622","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
28 June 2012