If you type DSPJOBLOG and Enter you only see the Job Log for your current
interactive job.

Was the job that errored out running interactively?
* If so and the operator signed off, there may be no joblog saved.

* If the Nightly job was a batch job --- use WRKJOB 'jobname'
   -If there is a single instance of that job in the system it will present
    the Work with Job menu for that job.
   -If there are multiple instances of the job a list of those jobs with
    the status and date is presented.  Select the instance with a '1' to
    see the Work with Job Menu for the job.

* You can also try the history log -- DSPLOG.  Use F4-Prompt to select
   the date and time range to start close to the error.

* If you run nightly work interactively you should consider doing a
   SIGNOFF *LIST when the Operator signs off-- forcing a joblog.
   You can control this with the LOG parm on the Job or on a Job

Jack Welch              ARIS, Inc.

> Last night one of our nightly jobs blew up.  The operator answered it and
> later logged off of the system.  This morning I tried to see what had
> happened.  When I used the DSPJOBLOG command it showed nothing.  When I
> pressed F10 (display detailed messages) it still showed nothing.  Is there
> a way that I can view a log all of the jobs that run through the system?
> _______________________________________________
> This is the COBOL Programming on the iSeries/AS400 (COBOL400-L) mailing
> list
> To post a message email: COBOL400-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit:
> or email: COBOL400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.