RE: MONITOR not catching MCH3601

I'm wondering if Monitor won't catch MCH errors. Or should I avoid
generalizing like that?

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Wednesday, October 29, 2008 2:47 PM
To: RPG programming on the AS400 / iSeries
Subject: Re: MONITOR not catching MCH3601

Is this help from Monitor applicable?

*ALL
Handles both program-error and file-error codes, from 00100 to 09999.
This
is the default.
Status codes outside the range of 00100 to 09999, for example codes from
0
to 99, are not monitored for. You cannot specify these values for an
on-error group. You also cannot specify any status codes that are not
valid for the particular version of the compiler being used.

Although if it's this, it should be covered
00222 Pointer or parameter error

Regarding API's, especially list APIs. I seem to recall a Barbara tip
from a couple years ago that when using list apis a common error like
you're having occurs on a loop to process each entry. Something people
often did, which mostly worked, but occasionally bombed like you're
getting. To fix it you just set your looping up differently. Sort of
like the debate on whether to use a priming read. Getting kind of busy
and a quick scan of some source files for Barbara wasn't turning it up.
Hope that's a start.

Rob Berendt