Re: Divide by zero and monitor group...

On 01-Jul-2015 20:25 -0600, Vernon Hamberg wrote:

On 7/1/2015 6:54 PM, Rich Marion wrote:

This is the main reason why I try to avoid MONITOR. It confused
other programmers where I work when they read through job logs.

There's a nice method for removing distracting messages - it
involves sending a message before whatever process you want to clean
up in, get a msg key from that one, then do another at the end - then
loop through the possible message keys (4-byte integer, basically) -
IBM has knowledge base article on it, I don't have the link right
now.

Vendors should be using this kind of technique to clean up their
logs - far too easy just to leave junk lying around!!

That methodology is for intended for messages sent to programs that are no longer on the stack.

The monitored messages will have been sent to the active program; naturally, that program is still on the stack :-) so either call the /remove message/ API for expected\handled message(s) to remove them or call the /move message/ API to bubble\percolate the messages up the stack.