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

    Certain job_list jobs do not run & produce no log in $alephe_scratch

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

    Description:
    Since the upgrade from v.16 to v.18, we have had trouble running p_cir_50 and 51 from the job_list.

    Yesterday (7/11 and today 7/12) the jobs produced empty output files and .scr lock files in ABC50 $data_scratch.

    Yesterday, I removed the .scr files and we were able to run the jobs manually. Here is what we see in $data_scratch:

    -rw-rw-r-- 1 aleph aleph 0 Jul 12 08:55 cir_51_1.scr
    -rw-rw-r-- 1 aleph aleph 0 Jul 12 08:55 cir_51_3.scr
    -rw-rw-r-- 1 aleph aleph 0 Jul 12 08:55 cir_51_2.scr
    -rw-rw-r-- 1 aleph aleph 0 Jul 12 09:25 cir_50_1.scr
    -rw-rw-r-- 1 aleph aleph 0 Jul 12 09:25 cir_50_3.scr
    -rw-rw-r-- 1 aleph aleph 0 Jul 12 09:25 cir_50_2.scr

    Resolution:
    I have found that the form of the entries in the /exlibris18/aleph/u18_1/alephe/tab/job_list is non-standard.

    This is this "non-standard" form:

    01 08:15:00 N csh -f /exlibris/aleph/a18_1/aleph/proc/p_cir_50 ABC50,BillsGen1,N,06^07^
    08^11^18^19,Y,,,00,00,00,Y,L,4

    ("N" in column 3 says that you do not want to use the batch queue.)

    This is what I consider to be the standard form for this same job:

    01 08:15:00 Y ABC50 p_cir_50 ABC50,BillsGen1,N,06^07^08^11^18^19,Y,,,00,00,00,Y,L,4


    It could be that the "non-standard" form should work, but rather than trying to figure that out, I have

    1) changed the "csh" job_list sections to the standard form

    2) util e/15/2 (Kill job daemon)

    3) util e/15/3 (Activate job daemon)

    This worked.

    Additional Information

    faq


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