Bug 79029 - Add the ability to retrieve multiple values for the same hash key in a single log record
Summary: Add the ability to retrieve multiple values for the same hash key in a single...
Status: CLOSED WONTFIX
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: TPTP.monitoring (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 2000
: P2 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Dave Smith CLA
QA Contact:
URL:
Whiteboard:
Keywords: Documentation, PII
Depends on:
Blocks:
 
Reported: 2004-11-18 17:08 EST by Christine Knight CLA
Modified: 2010-06-03 15:10 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christine Knight CLA 2004-11-18 17:08:40 EST
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
Comment 1 Dave Smith CLA 2005-01-18 16:57:58 EST
Please provide more details.  How is the key to be used?  Is it to be stored?  
Thanks.
Comment 2 Dave Smith CLA 2005-02-07 02:35:24 EST
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.
Comment 3 Dave Smith CLA 2005-02-07 02:43:16 EST
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.
Comment 4 Dave Smith CLA 2005-05-12 14:41:19 EDT
Retargetting as per discussions with submitter.
Comment 5 Christine Knight CLA 2005-07-20 10:14:09 EDT
Please raise this to a P1
Comment 6 Dave Smith CLA 2005-09-09 13:08:28 EDT
This may require new messages.
Comment 7 Dave Smith CLA 2005-10-26 16:35:01 EDT
Reducing priority as requested by submitter
Comment 8 Dave Smith CLA 2006-01-25 12:29:07 EST
Setting target to future so it doesn't show up in 4.2 feature query.
Comment 9 Christine Knight CLA 2006-05-10 16:29:03 EDT
Please set priority to P3, no longer high priority
Comment 10 Dave Smith CLA 2007-08-09 17:01:00 EDT
Resolving this as WONTFIX because it is no longer required by the consumer that requested it.
Comment 11 Dave Smith CLA 2007-08-09 17:18:35 EDT
Change target to 4.4.1 when the resolution happened.
Comment 12 Alex Nan CLA 2008-06-24 18:00:37 EDT
Closing.