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

    GUI-submitted jobs don't run


    • Product: Aleph
    • Product Version: 20, 21, 22, 23
    • Relevant for Installation Type: Dedicated-Direct, Direct, Local, Total Care



    Jobs submitted from the GUI (such as print-03) seem to run and appear in $data_files/que_batch file, but don't produce any log or any output.  util c/1 shows that the lib_batch process is running. 



    The $data_files/lib_batch_log file shows this: 

    Tue Mar 08 11:02:08 aleph *** executing /exlibris/aleph/a20_1/aleph/proc/ with parameters 

    That is, it lacks the name of the procedure (following the "/proc/") which it should have been executing. 

    The que_batch file has this: 

    00224002016030800,,,JOHN p_print_03 XXX01,xxx01_bibs,ALL,,,,,,,,xxx01_marc,M2,,,,N, 

    The fact that this didn't trigger proper activity in the lib_batch_log indicated a problem with the batch que.   util c/3 wouldn't stop it, so we killed it as described in the article "util c/3 doesn't stop batch queue".
    We then took the parameters beginning with "XXX01,..." and submitted the job manually, like this: 

    csh -f $aleph_proc/p_print_03 XXX01,xxx01_bibs,ALL,,,,,,,,xxx01_marc,M2,,,,N, > & $alephe_scratch/xxx01_p_print_03.0308.log & 

    The $alephe_scratch/xxx01_p_print_03.0308.log shows that the job ran successfully and produced the expected ./xxx01/scratch/xxx01_marc output file. 

    Since this bib library was just being set up and used temporarily (to do this export), we didn't pursue the root cause of this problem.

    If *no* batch jobs run, see the article "Batch jobs don't run".



    • Article last edited: 09-Mar-2016