Explanation about these match output fields?

[dqm]

Hi all,

I'm looking for an in-depth explanation about these fields.

qsMatchPattern.
qsMatchLRFlag.
qsMatchExactFlag.

I've read the help and apart from saying qsMatchLRFlag can be 'L' or 'R' and qsMatchExactFlag can be 'X' it really isn't any help at all.

Google and the QS Redbook are no help either (you have to admire IBM for being able to keep this as black an art as they do in this day and age...), so here are some specific questions I have:
- What makes qsMatchLRFlag an 'L' versus an 'R'
- I'm assuming qsMatchExactFlag is only for exact matches where qsMatchDataID != qsMatchSetId
- How to read qsMatchPattern. Any info around what makes each digit a 3, 2, 1 or 0?

TIA.

[JRodriguez]

My two cents:

qsMatchLRFlag flag is set by cetain match types that allows you to perform left/right comparisons like D_INT. Let's say that a single house number is compared to two intervals. One interval represents the left side of the street and the other represents the right side of the street. If the number is found in the left then the flag will be populated with an "L"

Similar qsMatchExactFlag is set by match types where if a condition is not met then the full agreement weight is always assigned and the comparison is considered exact. i.e CNT_DIFF


Regarding your query about qsMatchPattern, I asked same question in IOD 2008 and I got following answer:

"Frequency and pattern data in match results are just for the consume of match stages, they have not used in any other place so think of this like a black box "

Hi all,

I'm looking for an in-depth explanation about these fields.

qsMatchPattern.
qsMatchLRFlag.
qsMatchExactFlag.

I've read the help and apart from saying qsMatchLRFlag can be 'L' or 'R' and qsMatchExactFlag can be 'X' it really isn't any help at all.

Google and the QS Redbook are no help either (you have to admire IBM for being able to keep this as black an art as they do in this day and age...), so here are some specific questions I have:
- What makes qsMatchLRFlag an 'L' versus an 'R'
- I'm assuming qsMatchExactFlag is only for exact matches where qsMatchDataID != qsMatchSetId
- How to read qsMatchPattern. Any info around what makes each digit a 3, 2, 1 or 0?

TIA.

[dqm]

Thanks for that info Julio.
Much appreciated.