Re: Problem with MONMSG

[Simon Coulter <shc@xxxxxxxxxxxxxxxxx>]

On 07/01/2010, at 6:29 AM, Mark Walter wrote:

> I ran this program interactively, and this is the exception message  
> that it threw. Nothing above that in the job log. And, as per the  
> online docs, this is a message that can be monitored for.

Yes, it can be monitored. Just some diagnostic questions:

	1) Does any code appear between the ALCOBJ and the MONMSG?
	2) Is the MONMSG actually inside a comment block?
	3) Is that the only ALCOBJ in the program?
	4) Does the exception message actually come from that program, at  
that line?
	5) Does the source change date match the program object dates?
	6) Did you copy and paste the code sample from the failing program?

Is your concern that the exception still occurs and appears in the job  
log or that the code inside the MONMSG does not run?

Regards,
Simon Coulter.
--------------------------------------------------------------------
   FlyByNight Software         OS/400, i5/OS Technical Specialists

   http://www.flybynight.com.au/
   Phone: +61 2 6657 8251   Mobile: +61 0411 091 400        /"\
   Fax:   +61 2 6657 8251                                   \ /
                                                             X
                 ASCII Ribbon campaign against HTML E-Mail  / \
--------------------------------------------------------------------