|
I had one person that wanted me to change it to *WRAP. However it was later determined that his job was stuck in a nasty infinite loop and that was the "real" problem. If you do change it to *PRTWRAP I strongly suggest changing the job message queue size to some large number. You know how hard it is to scan 200 little bitty joblogs for the message in question? Saw one of these just today. And it wasn't for a very long time period. Which brings up another popular subject on this list. If you do a lot of MONMSG and the message is not germane to problem solving like CHKOBJ QTEMP/... MONMSG ... object does not exist so build it then put a RCVMSG in the DO for that MONMSG to delete the message so as to not clutter up the joblog. Not only does it make it smaller, but when I do scan the joblog for *ESCAPE I can get to the one I give a darn about. Rob Berendt
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.