|
Telnet jobs and our CGI jobs generate very large job logs, especially when they've been running for a week or longer. I've reduced the max to 8 mb and set QJOBMSGQFL to wrap. We're operating above 80% on DASD, which creeps up to nearly 90% if the system has not been IPL'ed in a week or longer. Anecdotally, the change seems to have helped; I haven't done any formal benchmarking.
Tom Liotta wrote:
Wayne McAlpine wrote:...take a look at system value QJOBMSGQMX. The default is 16MB but I've set ours at the minimum value of 8MB to conserve disk space.Perhaps like others, I don't _really_ know what that means. That is, does that actually "conserve" any space? At first thought, it'd seem that the only reasons it would would be because (1) a few jobs would end abnormally since they filled their allowed job message queue early or (2) you also have QJOBMSGQFL=*WRAP and you lose potentially critical messages.However, there is a possible alternative that 'job message queues' receive the full QJOBMSGQMX space allocation when each one is created. That would seem less likely to me.So, do you know what mechanism is "conserving" space for you? I guess first should be do you know that any space is conserved at all by this on your system?Tom Liotta
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
