I am not a big fan of stripping messages from a joblog scary or not. When it does actually fail, and at some time it likely will, you're missing part of the 'story' the joblog tells. If you've ever worked with JDA Software you'll know it's STUPID frustrating to read their joblogs because they do that. It's rather like a lot of stuff on social media, ONLY point out the part that supports your side of the story!

- Larry "DrFranken" Bolhuis

www.Frankeni.com
www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.

On 10/5/2017 9:58 AM, Rob Berendt wrote:
I suppose if you have a looping job which generates thousands of these you
might want to remove them from the joblog so you can focus on the more
critical messages.
Jim mentioned a message handler.
Some of us have written techniques in the past for ensuring messages are
dropped when we don't want them. For example, if we have a MONMSG in a
job to handle a particular exception then why leave that scary message in
the job log?

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.