Re: Suppress CPCA087 when copying

I'm not a big fan of absolutes.

If I have a loop and it does
DLTF QTEMP/BS
MONMSG CPF2105 EXEC(DO) /* file not found */
/* Clear the CPF2105 message from joblog */
ENDDO

Then I find that joblog much cleaner and the Escape messages left are
something I truly have to deal with.


Rob Berendt
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 2505 Dekko Drive Garrett, IN 46738 Ship to: Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com From: DrFranken <midrange@xxxxxxxxxxxx> To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>, Rob Berendt <rob@xxxxxxxxx> Date: 10/05/2017 10:30 AM Subject: Re: Suppress CPCA087 when copying Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx> 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?