DSXchange

I copied the ruleset MXADDR, did the requisite changes as mentioned by Stuart in the thread titiled "How do you make changes to USFIRSTN.TBL ? ", provisioned the ruleset.

But the job is not running.

It gives an error:

StandardizeAddr,0: Invalid Tbl Code
tblc.c l1506

Is there any step i have missed or
is there any more change needs to be done for the table codes, which is not mentioned in the steps.

Did you update the job with the new standardization Rule Set?

If yes ... try testing the rule set by itself using the Rule management GUI

JRodriguez wrote:Did you update the job with the new standardization Rule Set?

If yes ... try testing the rule set by itself using the Rule management GUI

Ofcourse i did. Only then the error is coming.

JRodriguez wrote:Did you update the job with the new standardization Rule Set?

If yes ... try testing the rule set by itself using the Rule management GUI

When we open the Rule Window for test, an error pops up:

"standardization process failed. Invalid tabl code. The above error occured in the following line of file C:\IBM\Information Server1\Clients\Classic\TempRules\MXADDR1AS.TBL"

and ironically the new generated reference table name is MXADDR1AS.TBL only

The original rule set name was MXADDR and i replaced this name everywhere in the ruleset by MXADDR1

Also, when i installed QS v8.0, it was not accopmnied by the Mexican Rulesets. But i had a notepad file for same separately. And i checked just now:

the ReadOnly status was "0" when i had imported the original ruleset(Which means that the ruleset is editable). Even then i was not able to edit the table MXADDRAS.TBL

Hence the change in the property Readonly doesnt seem to work. Please guide.

I noticed the file name is 9 characters long.

Try renaming the files to 8.3 format.
Not sure if it will help this problem, but I've had issues with this in the past, on version 8.
Problems where it worked fine in the test window, but jobs that used it would fail with an error related to the ruleset.

stuartjvnorton wrote:I noticed the file name is 9 characters long.

Try renaming the files to 8.3 format.
Not sure if it will help this problem, but I've had issues with this in the past, on version 8.
Problems where it worked fine in the test window, but jobs that used it would fail with an error related to the ruleset.

Are you saying about the length of the Table name.

So does it mean, that alnf with the original ruleset, all the table names and file names should also be < 8 characters?

stuartjvnorton wrote:I noticed the file name is 9 characters long.

Try renaming the files to 8.3 format.
Not sure if it will help this problem, but I've had issues with this in the past, on version 8.
Problems where it worked fine in the test window, but jobs that used it would fail with an error related to the ruleset.

Hi Stuart

I tried with renaming again and making it MADDR and replacing MEX with M, which ensures the file names everywhere to be <8 characters. but even now the same error is coming:

StandardizeAddr,0: Invalid Tbl Code
tblc.c l1506

Would you mind posting the entries that you added to this lookup table?

I remember having issues like this when the lookup table entries were not properly formatted. If you have a bad entry you could get an error specially when using CONVERT with the TKN argument. One way to know if that's your case will be commenting out one at a time the patterns actions that refers to this table in the pattern action file

i suppose that there is some issue with the RIGHTS to modify the reference file.

Are the entries in the ref. tbl validated by some rule in some other part of the rulset which need to be changed.

If anyone can help in this regards, help will be highly appreciated!

Working with the format


"5 REALES" MXASENTA 850

instead of

"5 REALES"
MXASENTA 850


For v8.0

Working with the format


"5 REALES" MXASENTA 850

instead of

"5 REALES"
MXASENTA 850


For v8.0

The reference files don't have to be 8 chars long IIRC, but the ruleset name (ie the name of all of the main ruleset files) needs to be 8 long.

As for the entries:

"CENTRO CEREMONIAL"
MXASENTA 850
"5 REALES"
MXASENTA 850
"ANDRES CUEXCONTITLAN"
"5 REALES" <-- Is this line a dupe? Doesn't look like it should be there.
MXASENTA 850

stuartjvnorton wrote:The reference files don't have to be 8 chars long IIRC, but the ruleset name (ie the name of all of the main ruleset files) needs to be 8 long.

As for the entries:

"CENTRO CEREMONIAL"
MXASENTA 850
"5 REALES"
MXASENTA 850
"ANDRES CUEXCONTITLAN"
"5 REALES" <-- Is this line a dupe? Doesn't look like it should be there.
MXASENTA 850

No there are colony/street names like "5 reales" in Mexico.
Even phrases like "5 de Mayo" can be a street name( it actually mean: 5th May)

divstands wrote:

stuartjvnorton wrote:The reference files don't have to be 8 chars long IIRC, but the ruleset name (ie the name of all of the main ruleset files) needs to be 8 long.

As for the entries:

"CENTRO CEREMONIAL"
MXASENTA 850
"5 REALES"
MXASENTA 850
"ANDRES CUEXCONTITLAN"
"5 REALES" <-- Is this line a dupe? Doesn't look like it should be there.
MXASENTA 850

No there are colony/street names like "5 reales" in Mexico.
Even phrases like "5 de Mayo" can be a street name( it actually mean: 5th May)

I'm not saying "5 REALES" isn't a valid place. I'm saying that piece of text shouldn't be there in that place.

It's supposed to look something like:
"CENTRO CEREMONIAL" MXASENTA 850
"5 REALES" MXASENTA 850
"ANDRES CUEXCONTITLAN" MXASENTA 850

ie:
"SOME PLACE IN MEXICO" MXASENTA 850

You have:
"CENTRO CEREMONIAL" MXASENTA 850
"5 REALES" MXASENTA 850
"ANDRES CUEXCONTITLAN" "5 REALES" MXASENTA 850

The last line is clearly not formatted correctly and would cause the error you are having.
So taking out the line I highlighted in the previous email should fix your problem.