Re: Pending Joblog invalid create date -- MIDRANGE-L

Subject: Re: Pending Joblog invalid create date
From: Rob Berendt <rob@xxxxxxxxx>
Date: Wed, 12 Apr 2017 14:02:14 -0400
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

That cume is REALLY old. Think Julian date. 15142 = 142nd day of 2015.
The current cume is almost 1.5 years newer, 16320. I suspect we're down
to one, maybe two, more cumes to go before the end of support of 7.1 on
April 30, 2018.

Even though the job is already 'ended' you can run this:
ENDJOB (mydeadjob) LOGLMT(0)
and that should blast the joblog.

We too have ran
CHGSYSVAL SYSVAL(QLOGOUTPUT) VALUE(*PND)

See also
Remove Pending Job Log (QWTRMVJL) API
https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_73/apis/qwtrmvjl.htm

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Pending Joblog invalid create date , Rob Berendt

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.