Skip to main content
Ex Libris Knowledge Center

Customization of pc_b_eng and error_eng files in version 17-up **MASTER RECORD**

  • Article Type: General
  • Product: Aleph
  • Product Version: 17
  • Relevant for Installation Type: Dedicated-Direct; Direct; Local;


In version 16.02, the pc_b_eng files were in the u-tree $alephe_root.

In version 17, the pc_b_eng .xml files (the GUI Services submission screens) are moved from the u-tree /alephe to the the a-tree /aleph.

Similarly, the ./alephe/error_eng files have been moved to ./aleph/error_eng.

Why have these been moved to the a-tree where, presumably, we can't modify them?

Resolution:
[Note: in the following resolution, "pc_b_eng files" refers to *all* of the files, both files for individual submission screens and menu files.]

17.01 rep_ver 9512 says this: "$alephe_root/pc_b_eng moved to $aleph_root/pc_b_eng. However, if files exist in $alephe_root/pc_b_eng, they will still have precedence over the 'aleph' files. This will allow customization.".

Thus, you could copy the $aleph_root/pc_b_eng files which you want to modify into the $alephe_root/pc_b_eng directory.

The same is true of the $aleph_root/error_eng and the $alephe_root/error_eng.

For more on this topic, see the "Error Messages" and "Services" sections on page 4 of the the attached "Upgrade Express 16.02-17.01 General Implementation Notes".

Note that this is *not* true of the pc_b_help_eng files. (See KB 16384-41729 for info on the GUI Services Help files.)

If your u-tree ./alephe/error_eng or ./alephe/pc_b_eng contain files from the old version, we suggest,

for pc_b_eng/:

* move the ./alephe/pc_b_eng/ to ,/alephe/pc_b_eng.old/
* create an empty ./alephe/pc_b_eng/
* for each file in pc_b_eng.old/ which you actually changed (if any), copy the new version of the file from ./aleph/pc_b_eng to ./alephe/pc_b_eng/
* reconcile the new version of the file with what you have in ,/alephe/pc_b_eng.old/ . (This means either reapplying the changes you made to this version or, if you believe there were no changes to this file between the two versions, you can copy your changed version from ,/alephe/pc_b_eng.old/ to ,/alephe/pc_b_eng/, as is.)
* do util x/7 to clear the utf_files.
* restart the pc_server (util w/3/3)
* the preceding procedure will allow the as-delivered current version of the a-tree ./aleph/pc_b_eng/ file to be used in the majority of cases where you do not have a local, customized u-tree alephe version.


or, for error_eng/:

* move the ./alephe/error_eng/ to ./alephe/error_eng.old/
* create an empty ./alephe/error_eng/
* for each file in error_eng.old which you actually changed, copy the new version of the file from ./aleph/error_eng/ to ./alephe/error_eng/.
* reconcile the new version of the file with what you have in ,/alephe/error_eng.old/. (This means either reapplying the changes you made to this version or, if you believe there were no changes to this file between the two versions, you can copy your changed version from ,/alephe/error_eng.old to ,/alephe/error_eng/, as is.)
* do util x/7 to clear the utf_files.
* restart the pc_server (util w/3/3)
* the preceding procedure will allow the as-delivered current version of the a-tree ./aleph/error_eng/ file to be used in the majority of cases where you do not have a local, customized u-tree alephe version.

Additional Information

faq, pc_b_eng, error_eng, customisation, customize

Category: System management


  • Article last edited: 10/8/2013