Re: monmsg question

[Simon Coulter <shc@xxxxxxxxxxxxxxxxx>]

On 17/11/2006, at 9:49 AM, Jerry Draper wrote:

> I have a CL that does a monmsg at the top of my CL after the DLC's 
> which
> I thought would apply all the way to the end of the CL eliminating the
> need to MONMSG each command.  I want this CL to finish without halting.
>
> Jerry
>
>
>   MONMSG     MSGID(CPF9000 CPF3000)


This is working as designed (and as documented). It's just not doing 
what you hope.

You need two zeros to indicate generic monitoring. Thus CPF0000 will 
catch everything, CPF9000 will only catch messages beginning with 
CPF90, and CPF3000 will only catch messages beginning with CPF30.

Your code is failing for two reasons:
        1) CPF3779 is not in the range monitored by a generic CPF3000
	2) Unmonitored exception CPF3779 causes function check CPF9999 which 
is not in the range monitored by CPF9000

You can fix your problem by:
        a) monitoring for CPF3700
        b) monitoring for CPF9999
        c) both of the above
        d) monitoring for CPF0000 (which would be sloppy without a GOTO)

Many people use CPF0000 as the catch-all global monitor. I prefer 
CPF9999 instead. Accomplishes the same end but gives me better 
diagnostic information about where in the program the failure occurred.


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

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