topic Unable to see Extact definition in QKB which is available in Match code node in DataFlux in SAS Data Management

Unable to see Extact definition in QKB which is available in Match code node in DataFlux

Rama_V — Sun, 27 Oct 2019 00:14:39 GMT

Hi,

I have been able to see Exact definition available through Match Code Node in Data Flux Management Studio. It has given me good results which is what I wanted.

I was able to open QKB and investigate/Test available definitions like Name, Address etc. Unfortunately, I was unable to see the Exact definition in the QKB.

I would like to see what actions are taken to generate a particular match code.

Could anyone please point me to that definition?

Thanks,

Rama

Re: Unable to see Extact definition in QKB which is available in Match code node in DataFlux

mawarn — Wed, 30 Oct 2019 15:01:59 GMT

Sorry, but I need more information.

Are you looking for an Extract definition?
What locale are you using?
What match definition are you seeing it in?

Re: Unable to see Extact definition in QKB which is available in Match code node in DataFlux

Rama_V — Thu, 31 Oct 2019 00:20:13 GMT

Thanks for responding to my query.

1. No, I am using Exact definition. I used as it is available in Match codes node in Data Flux Management Studio.(attached the snapshot of job).

2. I am using English Australia(ENAUS) locale.

3. Exact definition( not sure this answers your question) I have attached the snapshot of the QKB opened in the English Australia locale.

As shown below Name Match definition snapshot, I was able to test ,check results at each step.

I would like to see the similar steps involved in creating match code using Exact definition.

Re: Unable to see Extact definition in QKB which is available in Match code node in DataFlux

mawarn — Thu, 31 Oct 2019 14:37:22 GMT

Ahh. I understand now. There isn't really an Exact definition in the QKB. Here is the explanation from the DM Studio User Guide Match Codes Node documentation.

If you specify the Exact value in the drop-down menu, however, a matchcode definition from the QKB is not supplied. Instead, a matchcode is generated that applies UPCASE processing and removes any whitespace from the input string.