Re: On-Error

This is a multipart message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
This will make the logic kind of confusing
Monitor;
  read (e) myfile;
  Select;
  When %status=NoError; // Good read
    ...
  When %status=EndOfFile; // Break out of loop
    ...
  When %status=RecordNotFound; // Strange
    ...
  EndSl;
  // Check for other errors
  On-Error TriggerErrBef; // Trigger error, maybe we don't have access?
    ...
  On-Error FileClosed; // Oops, need to open the file
    ...
  On-Error;  // Catch all for other errors
    ...
EndMon;

In this case you might have better served to stay with the Select.  Just
put the bulk of the On-Error's with the other When's, (or Other).

Why didn't they allow the sub 100's to be trapped for?

Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin




rob@dekko.com
Sent by: rpg400-l-admin@midrange.com
11/04/2002 03:47 PM
Please respond to rpg400-l

        To:     rpg400-l@midrange.com
        cc:
        Fax to:
        Subject:        Re: On-Error


This is a multipart message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
Thanks Barb.  That was clearly in the manual and I should have seen that:
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.

Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin
_______________________________________________
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l
or email: RPG400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.