Community
Participate
Working Groups
Add the ability to parse a file where the same key occurs more than once in the message, for example, Dump File:/home/db2usr/sqllib/db2dump/855201.000 Data:SQLP_TENTRY Dump File:/home/db2usr/sqllib/db2dump/855201.000 Data:SQLP_ACB Dump File:/home/db2usr/sqllib/db2dump/855201.000 Data:SQLP_DBCB
Please provide more details. How is the key to be used? Is it to be stored? Thanks.
Here is more information from Rohit Shetty (rohit.shetty@in.ibm.com): In the hashmap that is used to store key-value pairs for the hashing feature in GLA(Parser) if the key occurrs more than once then only the last value for the pair is stored.In most of the cases this is fine but in some cases it is not what is expected.Is such situations i think it should return all the values for that particular key with a suitable seperator.ie.some seperator like “@@”. Another possible solution is retrieving these values as an array as they are In most of the cases put into EDE where we can use this as multiple values for the same element. Example of a log entry from DB2 containing such key/value pairs: PID:85520 TID:1 Node:000 Title: SQLCA sqlcaid : SQLCA sqlcabc: 136 sqlcode: -998 sqlerrml: 3 sqlerrmc: 2 0 sqlerrp : xa_commi€ sqlerrd : (1) 0x8012007E (2) 0x00000000 (3) 0x00000000 (4) 0x00000000 (5) 0x00000000 (6) 0x00000000 sqlwarn : (1) (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) sqlstate: Dump File:/home/db2usr/sqllib/db2dump/855201.000 Data:SQLP_TENTRY Dump File:/home/db2usr/sqllib/db2dump/855201.000 Data:SQLP_ACB Dump File:/home/db2usr/sqllib/db2dump/855201.000 Data:SQLP_DBCB ==> Here Dump File has multiple occurrances and only the last value is reflected when retrieved which conveys a different picture.
Themes: Simple to Use and Appeals to a Broader Community This improves the usability of GLA and enables the GLA to parse more kinds of logs with regex rules.
Retargetting as per discussions with submitter.
Please raise this to a P1
This may require new messages.
Reducing priority as requested by submitter
Setting target to future so it doesn't show up in 4.2 feature query.
Please set priority to P3, no longer high priority
Resolving this as WONTFIX because it is no longer required by the consumer that requested it.
Change target to 4.4.1 when the resolution happened.
Closing.