Changes to pc_tab_exp_field_extended.eng not taking effect
- Article Type: General
- Product: Aleph
- Product Version: 20
Description:
We have been trying to edit the table pc_tab_exp_field_extended.eng to change columns 4 and 5 for the bor_type 13 to 15, as shown in the attached document, but our changes are not taking effect.
Resolution:
Though the ./sta50/tab/pc_tab_exp_field_extended.eng has these lines:
BOR-TYPE ##### L FFA_UG_FT 13
BOR-TYPE ##### L FFA_UG_PT 14
BOR-TYPE ##### L FFA_UG_EV 15
the /tmp/utf_files/exlibris/aleph/u20_2/sta50/tab/pc_tab_exp_field_extended.eng -- which is what is actually being used -- has these lines:
BOR-TYPE ##### L FFA_UG_FT 13
BOR-TYPE ##### L FFA_UG_PT 14
BOR-TYPE ##### L FSA_UG_EV 15
I find that the ./sta50/tab/pc_tab_exp_field_extended.eng has an *earlier* timestamp:
-rw-rw-r-- 1 aleph exlibris 11332 Aug 15 10:38 pc_tab_exp_field_extended.eng
than the /tmp/utf_files/exlibris/aleph/u20_2/sta50/tab/pc_tab_exp_field_extended.eng:
-rw-rw-r-- 1 aleph exlibris 11311 Aug 15 10:52 pc_tab_exp_field_extended.eng
It seems that you copied the ./sta50/tab/pc_tab_exp_field_extended.eng from an earlier version. As described in KB 16384-4578, in such a case, the utf_files version will *not* be updated.
If you make the updates that you want to the ./sta50/tab/pc_tab_exp_field_extended.eng and save the file so that the timestamp is updated to today's date and time, you will find that the utf_files version is updated -- and your changes will display.
- Article last edited: 10/8/2013