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



In general, I agree with the sentiment of not clearing messages from the
job log. Vern, here's an example I am currently dealing with. I'm using
CPYTOSTMF in a CL and it issues SQL7963 for every 24 rows it copies. Since
the one test I was running copied over 200k records, the job log wrapped.

- Dan

On Thu, Oct 5, 2017 at 10:42 AM, Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>
wrote:

+1

I appreciate when messages are removed that were only there as a result of
a CHKOBJ or some other thing that is used only for an internal status check
- CHKOBJ might not be the best example, but it's early!!

Vern


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.