Re: Any Combination of Settings to Get one Large Contiguous Job Log in V5R4 -- MIDRANGE-L

Subject: Re: Any Combination of Settings to Get one Large Contiguous Job Log in V5R4
From: CRPence <CRPbottle@xxxxxxxxx>
Date: Mon, 07 Jul 2008 08:10:46 -0500
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/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

rob@xxxxxxxxx wrote:

One of the main reasons that I started putting code in my programs to remove messages that I processed. <<SNIP>>

And your joblogs may be a LOT cleaner. This actually removed a thousand or so pages from one joblog.

<<SNIP>>

As I understood the job message queue, removing messages will not assist to prevent filling the queue. So although removing the unwanted messages [or filtering what messages are included in the spooled output via the LOG() parameter for jobs] can effect a much smaller spooled joblog, I do not think removing messages will have any affect on how [quickly] the job message queue will fill; that instead, a reduction of the number of messages actually sent to the *PGMQ must be reduced.?

Regards, Chuck

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2025 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.