• Article Type: General
• Product: Aleph
• Product Version: 19.01

Description:
Need help finding which record p_file_96 is processing when issuing the error messages:
Error: character X"46" is not defined in marc8_ext_rus_to_unicode.
Error: character X"43" is not defined in marc8_ext_rus_to_unicode."

If you happen to know what MARC elements I need to look for? I've never known how MARC8 denotes a tag as containing non-Latin data, except when there were 880 fields in CJK. Also, the extended Russian is a small table. The values 43 and 46 are in marc8_rus_to_unicode:

0446 43 CYRILLIC SMALL LETTER TSE
0444 46 CYRILLIC SMALL LETTER EF

So I wonder why these translations were not used before the ext_rus table was consulted?

Resolution:
I decrypted b_file_96_a.cbl and changed the "IF TRACE-COUNT > 1000" to "IF TRACE-COUNT > 0000", as described in Internal KB 16384- . (That KB is not published and this procedure can be performed by Ex Libris staff only.)

Thus, it logged the key of each record as it was being processed, which let the site see which record was the problem.

[From site:] I found the record, suspected it was bad cataloguing and asked our Cataloguing staff to look at it. She has fixed it on OCLC, so I’ve asked Acquisitions to notify YBP in the hopes that they will re-send the record with the added tags re-added, for price, barcode etc. (We have a way of loading a file while excluding a bad record, so the others should get loaded tomorrow morning.)

• Article last edited: 10/8/2013