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

    Hundreds of usm50... files in xxx50 $data_print clogging up Task Manager

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

    Staff was starting to report that Aleph was crashing every time they tried to bring up the task manager so I did a huge clean up of abc50/print.

    Do an ls -l usm50*
    What are these files? What is producing them?
    They are bogging down the task manager so that it either takes forever to load or Aleph just crashes.

    We are getting hundreds of these usm50...circ_offic reports that we do not use. Is there a way to stop them from being generated? My circ librarians tell me they are automatically produced when a hold request is deleted before it is filled.

    I have shown examples of the letters to my circ librarians. They are not sent out by them. They just clog up the task manager making it difficult for them to get to the reports that they do care about. Is there any way to stop these from generating?

    tab39 is the Hold request daemon (ue_06) configuration file.

    We see in bcl50 tab39 that "circ_offic" appears in column 12 as the "Hold request not filled Print ID".

    Column 7 ("a switch which determines whether 'hold request not filled' letters will be printed") is set to "Y".

    I believe that changing this to "N" and stopping/restarting ue_06 will keep these letters from being produced.

    (Note: The distributed usm50 tab39 has "holdwait" in column 12.)

    • Article last edited: 10/8/2013
    • Was this article helpful?