DSXchange

DivStand, Probably the missing records has been identified with another ISO country code .....different than MX By the way the Select stage is previous to 8.x, and has been deprecated in version 8.x. You could use switch, transform or filter stages as a replacement Using a transformer you could add ...

Did you type the metadata manually ... looks like you have different length .. now you have the inverse scenario... do a trim( ) on those fields having a warning or use same length in both input and output columns

Defining your column as Varchar avoid both scenarios ...

By default DS/QS used a null value(0x0) when extending or padding a string to a fixed length field (Char datatype), with this environment variable you can override the default value to any character. Most of the time you would like to use space(0x20) You should find this env variable under Parallel ...

What's your value for APT_STRING_PADCHAR? If is 0x0(ASCII nulls) which is the default then try with 0x20(Space) and let us know

Are those fields defined with char datatype? If yes just use varchar instead, that probably will help to avoid the warning messages

When i found matched records it is showing weight as 0 in the test results . A: The match commands are not set properly .... Whare can i set weights for all the fields in both data and reference columns . A: The weights will be calculated by QS tool automatically after filling up the proper values....

If is only 77777777 that you want to remove then

Convert("7",'', InputCol )

It will only remove the string if exist ...else your input value will return

What would you like to do with the Input Pattern that you posted?

Please post the business requirements ... or try to explain in more details what you did so we can be of more help ...

Ohh! you are only parallel then this will do the trick

Convert("0123456789",'', InputCol )

Also while standardizing your data you can assign the null class to numeric token....

Please post the unhandled Pattern, Pattern that you want to convert the unhandled pattern, and what you did to make this happen...

DivStand, How about posting one of those entries? As a general rule you would like to convert all unhandled pattern into pattern succesfully handled by the rule .... By the way, you can test the ressult of the Input pattern override functionality in the Rule Management GUI... one at a time is less p...

Oconv(InputCol, "MCA")

Well ...in version 8.1 if you have an entry like yours the job will fail, even in the Rule Management GUI

Which version are you working with?

Would you try to align each entry into one line? Probably that's the issue

Only for Standardization ...the 850 is used to indicate that uncertainty comparisons will be used so you don't need all permutation of the string

By the way each entry in your lookup table is in one line, right?

Like this:

"SITIO EJIDO" MXASENTA 850