Skip to main content
ExLibris
  • Subscribe by RSS
  • Ex Libris Knowledge Center

    cir-10 Duplicate Courtesy Notices And Incorrect Recipients

    • Article Type: General
    • Product: Aleph
    • Product Version: 20, 21, 22, 23

    Problem Symptoms:

    The print daemon sometimes emails notices produced by the cir-10 (Courtesy notice) Service to the wrong patron, and also sometimes produces duplicate notices.  This happens with large files (at the end of the semester when lots of items are coming due and when "All" is checked for the cir-10 Sublibraries option).  That is, when large output files are being produced, such as, a 50 Meg. file, with 774 notices.

    Case 1: There are no "Splitting" messages in the log and no "perl ... split" lines in the proc.

    Case 2: The p_cir_10 process log contains the error message: "Library_Notice-Courtesy_NNNNNNNN size is NNNNNNNNNN. Splitting... Processing.." and the $aleph_proc/p_cir_10 proc has "perl $aleph_proc/split_xml_file" lines.

    Resolution:

    Case 1:
    An examination of the $data_print xml file showed that the file had the correct email-address/patron-name associations.  It seemed that the pc/print daemon was being overwhelmed.  

        a) reboot the pc running the print daemon nightly,

        b) add memory to the pc,

        c) reduce the size of the files by doing smaller groups of sublibraries at a time rather than "All",

        d) possibly add CPU/processing power or get a more powerful pc.
    Case 2: 
    [The ./aleph/proc/split_xml_file.pl was splitting input files over 8mb; hange it to not do this.]
      1.Make a backup of $aleph_dev/aleph/proc/p_cir_10

      2. Remove the following lines from $aleph_dev/aleph/proc/p_cir_10:

         * perl $aleph_proc/split_xml_file.pl $data_print/$p_file_out.$p_target 10000 $p_target

         * perl $aleph_proc/split_xml_file.pl $data_print/$p_file_out 10000 $p_target

      3. Restart the PC Server.
     

    Additional Information

    For Case 2.... There is no need to replace the deleted lines. No splitting is needed because the output file is comprised of many separate XML files. The system knows how to separate and properly handle many logical XML files within a single physical file.
     

    Category: Circulation (500)


    • Article last edited: 17-May-2016