System Logs -- COBOL400-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: System Logs
From: "Phil Campbell" <pcampbell@xxxxxxxxxxxx>
Date: Fri, 21 Nov 2003 09:26:19 -0600
List-archive: <http://archive.midrange.com/cobol400-l>
List-help: <mailto:cobol400-l-request@midrange.com?subject=help>
List-id: COBOL Programming on the iSeries/AS400 <cobol400-l.midrange.com>
List-post: <mailto:cobol400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/cobol400-l>, <mailto:cobol400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/cobol400-l>, <mailto:cobol400-l-request@midrange.com?subject=unsubscribe>
Thread-index: AcN9PldIZtByTGBVRAKWnuWhSY8BSgzBUZ4g
Thread-topic: COBOL400-L Digest, Vol 1, Issue 277

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?

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: System Logs , welchj

This mailing list archive is Copyright 1997-2024 by midrange.com 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.