× 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.



Thanks Rob

You're right of course,
It's just my psychological aversion to seeing some hundred Jobs
in "JOBLOG PENDING" state.
It's a personal thing ...
and I also think it's not normal, there is a root cause somewhere.
(our Dev machine has only 2 such jobs - in ACTIVE state)

Gad





date: Thu, 7 Nov 2024 09:16:53 -0500
from: Rob Berendt <robertowenberendt@xxxxxxxxx>
subject: Re: QTSMTPCLTP job ending with CPC1213

Job log pending is not such a bad thing. Back in ancient versions a job
log pending meant a bad thing - that the job ended somewhat abnormally.
Nowadays it simply means that you think that looking at joblogs only via
spool files is stone knives and bearskins. And that you find being able to
query joblogs with services like QSYS2.JOBLOG_INFO() is much more
productive.

IBM has changed many job descriptions to LOGOUTPUT(*PND). I've changed our
system value QLOGOUTPUT to *PND.

After all, when you query a database file do you query it directly (it or
one of it's views, etc), or do you do a CPYF FROMFILE(MYLIB/MYFILE)
TOFILE(*PRINT) and then query that spool file?

On Thu, Nov 7, 2024 at 1:43?AM Gad Miron <gadmiron@xxxxxxxxx> wrote:

Thanks Rob

On a 2nd thought,
Perhaps a better option is to change the JOBD of QTSMTPCLTP so that
it will end totally and not stay in a "JOBLOG PENDING" limbo.

What do you think?

Gad





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-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.