A fix is available
Closed as program error.
The Manage Situations dialog only shows stopped situations. This happens when the KFW_REPORT_ROW_LIMIT variable is set to a low value, such as 1000. RECREATE INSTRUCTIONS: 1) issue the query: KfwSQLClient -e "SELECT SITNAME, LCLTMSTMP, NODE, DELTASTAT, GBLTMSTMP, TYPE, ORIGINNODE, ATOMIZE, FULLNAME FROM O4SRV.ISITSTSH WHERE (GBLTMSTMP > 0)"|wc -l result = 21 2) in the TEP -> UNIX LOGS -> Managed Situations -> i can see Started and STOPPED situations 3) changed the KFW_REPORT_ROW_LIMIT from 100.000 to 10 4) restart the TEPS 5) in the TEP -> UNIX LOGS -> Managed Situations -> i can see ONLY STOPPED situations 6) changed the KFW_REPORT_ROW_LIMIT back to the default 100.000 7) restart the TEPS 8) in the TEP -> UNIX LOGS -> Managed Situations -> i can see AGAIN Started and STOPPED situations
Manage Situations window only shows stopped situations when KFW_REPORT_ROW_LIMIT is set to a low value. The Manage Situations window only shows stopped situations. This happens when the KFW_REPORT_ROW_LIMIT variable is set to a low value.
The code was changed not to limit the return rows against the query in the Managed Situations window. The fix for this APAR is contained in the following maintenance packages: | fix pack | 6.3.0-TIV-ITM-FP0003
Reported component name
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
Fixed component ID
Applicable component levels