DB2 - Problem description
Problem IT21826 | Status: Closed |
EVMON_FORMAT_UE_TO_XML DOES NOT SORT PARTICIPANT PAST ACTIVITIESIN A USEFUL WAY | |
product: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problem description: | |
The output of EVMON_FORMAT_UE_TO_XML(), which is also called by db2evmonfmt tool, does not sort participant past activities in a useful way Per example, it is not sorted by activity ID: participant1.txt (99 hits) Line 93: Activity ID : 893 Line 124: Activity ID : 100 Line 159: Activity ID : 95 Line 295: Activity ID : 79 Line 431: Activity ID : 47 ... nor by "Stmt last use" : participant1.txt (99 hits) ... Line 1125: Stmt last use : 2016-12-16-00.09.13.288655 Line 1261: Stmt last use : 2016-12-16-00.09.13.256359 Line 1397: Stmt last use : 2016-12-16-00.09.13.188518 Line 1533: Stmt last use : 2016-12-16-00.09.13.148117 Line 1669: Stmt last use : 2016-12-16-00.09.13.098337 Line 1805: Stmt last use : 2016-12-16-00.09.13.021684 Line 1941: Stmt last use : 2016-12-16-00.09.13.322485 Line 2077: Stmt last use : 2016-12-16-00.09.13.244628 Line 2213: Stmt last use : 2016-12-16-00.09.13.284256 ... The current output of "Past Activities of Participant" that is reported by EVMON_FORMAT_UE_TO_XML() does not appear to have clear logical sequence. This APAR fix will have this information in a usable sorted manner that could help find the sequence of events that lead to an issue. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * all * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to version 11.1 mod 1 fp2 * **************************************************************** | |
Local Fix: | |
Solution | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : IT19113 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 04.08.2017 09.10.2017 09.10.2017 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |