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

    GUI-Services-submitted job doesn't work on one particular PC **MASTER RECORD**

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

    We are trying to run job xyz via the GUI Services. It runs OK on one PC, but on another, though we see see the message "Job submitted", the job does not appear to create any files because we do not see any files in the Scratch directory.

    There are two main possibilities:

    1. The job executes but fails to produce the expected output file (because of errors).

    2. The job fails to execute because ???

    #1. You need to look at the $alephe_scratch job log. (You say "the job does not appear to create any files because we do not see any files in the Scratch directory." Besides not seeing any output file, do you not see any job log either? Any job submitted via the GUI which executes should produce an abcnn_p_xxxxx.nnnn job log (where "abcnn" is the library; "p_xxxxx" , the job name; and "nnnn", the process number). For example: usm01_p_file_01.2463.

    If there's a job log but you do not see the output file,...

    * Is the "Print to ADM Lib" checkbox on the right, about halfway down, on the submission screen checked? This will cause the input file to be read from and the output file to be written to the abc50 library rather than abc01. KB 16384-39410 describes v20 rep_change 3290 which changes this text to "Read From/Print To ADM".

    * Is there an error in the job log, such as,

    I/O error : file 'TP1'
    error code: 3/5 (ANS85), pc=0, call=1, seg=0
    13 File not found

    indicating that the input file was not found.

    #2. If there is no $alephe_scratch job log (no abcnn_p_xxxxx.nnnn file), the job did not execute.

    Make certain (util c/1) that the batch queue of the library that you submitted the job to is running. See KB 5672 in regard to batch queue problems.

    Most of the GUI submission screens have a "Library" dropdown at the bottom. Make sure that the Library shown there is the library which you are intending to submit the job to. If not, it could be that the job is being submitted to a different library whose batch queue is not running and, therefore, the job never executes.

    Additional Information


    • Article last edited: 10/8/2013