cir_51 crashing at print file creation

Last updated
Save as PDF
Share
1. Share
2. Tweet
3. Share

Article Type: General
Product: Aleph
Product Version: 18.01

Description:
We can not get a cir_51 printout. The working files in the scratch folder are created to level .3.scr and then there is an execution code error during the [cobrun pc_print_form] of the [p_cir_51] script. This happens to the cir-50, cir-51, and cir-52 scripts.

The error message is:

Execution error : file '/exlibris/aleph/a18_2/aleph/exe/form_xml_translate_pc_tab_exp.gnt'
error code: 114, pc=0, call=1, seg=0
114 Attempt to access item beyond bounds of memory (Signal 11)

This is followed by a bunch of messages like this:

Info: Empty table /tmp/utf_files/exlibris/aleph/u18_2/abc50/tab/tab25.spa
Load: /tmp/utf_files/exlibris/aleph/u18_2/abc50/tab/edit_field.spa
Info: Empty table /tmp/utf_files/exlibris/aleph/u18_2/abc50/tab/edit_field.spa
Load: /tmp/utf_files/exlibris/aleph/u18_2/abc50/tab/edit_field.eng
Info: Empty table /tmp/utf_files/exlibris/aleph/u18_2/alephe/error_spa/format_due_date
Info: Empty table /tmp/utf_files/exlibris/aleph/u18_2/alephe/error_spa/global

Resolution:
It appears that this is happening because you have a number of patrons where you have set the language code to something other than ENG. The following SQL and result shows this:

abc50@ALEPH0> select z303_con_lng, count(*) from z303 group by z303_con_lng;

Z303_CON_LNG COUNT(*)
--- ----------
FRE 1
POR 1
SPA 27

It is, of course, perfectly fine to have different languages set, which is why Aleph provides this capability. However, if you support languages other than English, you need to provide a full set of tables in support of these languages. So, in addition to all of your ".eng" tables, you would need a full set of ".spa" tables (and ".fre" and ".por" as well). You would also need error message files in $alephe_root/error_spa, error_fre_ and error_por directories. You may choose to do this or you can change the language code for all of your patrons to ENG. Either way, the problem should disappear. If you need any help with whichever of these options you choose, please feel free to contact us.

Article last edited: 10/8/2013