Skip to main content
ExLibris
  • Subscribe by RSS
  • ExLibris Dev

    Error:missing program" message - **Comprehensive discussion of causes**

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

    Description:
    You see messages like this in a server, ue, or job log:
    "Error:missing program fix_doc..."
    "Error:missing program expand_doc..."
    "Error:missing program line..."
    "Error:missing program filing..."
    "Error:missing program b_manage_01_b..."

    Resolution:
    Certain ALEPH tables (e.g., tab_fix, tab_expand, tab_check_circ, tab_hold_request, tab_character_conversion_line) contain the names of actual programs to be executed. The system checks (in the ./aleph/exe executable directory) for the presence of *all* the programs listed in the table. The missing program may not be related to the particular function you are performing and that function may well be successful despite its absence. Examine the relevant table to see if the "missing program" is one which you needed to be executing.

    tab_filing is slightly different: the value which appears in column 3 is only part of the program name: the system takes column 3 and prefixes it with "filing_". Then it looks for filing_del_subfield, filing_to_blank, etc. (Note: the filing source programs are in the ./alephm/source/filing/ directory.)

    Likewise with tab_word_breaking: the value which appears in column 3 is only part of the program name: the system takes column 3 and prefixes it with "b_manage_01_b". Thus, if you have "to_lower" in column 3, it expects to find a program b_manage_01_b_to_lower . (Note: the b_manage_01_b source programs are in the ./alephm/source/butil/ directory.)

    Make sure that the name is typed correctly and that's properly aligned. (A space preceding the name can make it look for

    " expand_doc_type" instead of
    "expand_doc_type". )

    Or perhaps it is obsolete; in which case you should delete it. Or perhaps it is missing from the version and should be there; in this case, contact Customer Support.

    Another cause can be failing to include an "!" at the beginning of a line which you intend to be a comment. See KB 8192-2128. FAQ

    Additional Information

    faq


    • Article last edited: 10/8/2013
    //doorbell.io feedback widged