Re: Possible error codes for monitor

Vern,

I differ. I at least make a token effort to determine what the error is
or trap more common errors. Like

monitor;
MyNbr=%dec(MyChar);
on-error InvalidNumeric;
InvalidNumeric(); // execute the invalid numeric subprocedure
on-error;
// catch all
AlertTheTroops();
endMon;

While you may think that the only possible error would be an invalid
numeric, you may decide to handle truncation, etc different. Things
change, like a new vendor package may change field sizes.

Also, OS changes occur. Like all those people who assumed that all write
errors were because of a duplicate record and then simply did a chain and
update to remedy it. Now they get errors like referential constraint
error, or trigger error, or ...

Notice the
on-error InvalidNumeric

Jon Paris whipped up a nice /copy of error codes at one time. I am sure
that Cozzi has his own somewhere. (There's a lot of that NIH syndrome
going around.)

I found a list of File Status Codes:
***************************************************************************
* File status codes *
***************************************************************************
/if not defined(FileStatusCodes)
/define FileStatusCodes
D NoError C 0
D EndOfFile C 11
D RecordNotFound C 12
D DuplicateKey C 1021
D ReferentialErr C 1022
D TriggerErrBef C 1023
D TriggerErrAft C 1024
D YouAreOld C 1031
D FileClosed C 1211
D FileOpen C 1215
D ImpOpenCloseEr C 1216
D ExpOpenCloseEr C 1217
D RecAlreadyLock C 1218
D UpdBeforeRead C 1221
D RefErrOnAlloc C 1222
D PermIOErr C 1251
D JobEndingCtl C 1282
/endif


Rob Berendt