Meaningless error messages Was:SNA Codes

[Buck Calabro <mcalabro@xxxxxxxxxxxx>]

I would include such "meaningless" messages as an error trap of last
resort.  If you really, truly can't recover and you can't figure out why,
at least you can tell what piece of code failed by matching the error ID to
the code that can generate that ID.  It might be very helpful in debugging
even though it doesn't help the end user (programmer in this case.)

Buck Calabro
Billing Concepts, Albany NY

> -----Original Message-----
> From: Glenn Ericson 
> Sent: Monday, May 17, 1999 11:54 AM
> To:   MIDRANGE-L@midrange.com
> Subject:      Re: SNA Codes
> 
> >My question is this.  Why did the developers of SNA even bother coding
> for 
> >this error.  It seems
> >like a 10030000 is a generic "we can't really tell what the heck is
> wrong, 
> >but it's not working so we'll
> >spit out this error".
> 
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---