RE: Error Message List

Jeff,
Communications is another animal entirely.  In RPG, always check the
major/minor return codes after every I/O operation.  These codes will help
narrow down the specific cause of the problem.  The codes are described in
the appropriate communications guide (ICF, Async, etc.)  In addition to the
major/minor return codes, check the file status code from the file
information data structure.

Very broadly, most messages that are fatal (i.e. escape messages) are too
generic to be of much help.  The preceding diagnostic messages are generally
the useful ones.  IBM provide the generic escape messages so that you don't
have to monitor for every possible individual detailed reason a process can
fail.    If your error recovery allows it, you can monitor for the "line
failed" message, close the ICFF, vary the line off/on, re-open and re-try
without ever knowing that DSR dropped before it was supposed to  It depends
on how intense your error recovery procedures need to be..

Buck Calabro
Aptis; Albany, NY

> -----Original Message-----
> From: jeff burcher 
> Sent: Monday, November 08, 1999 2:06 PM
> To:   MIDRANGE-L@midrange.com
> Subject:      RE: Error Message List
> 
> In some partial listings of error messages I have seen, they briefly
> explain
> WHY a certain error message would occur. This is helpful when the only
> Message description is "communications error" and the only helpful system
> advice is "to fix problem, change program".
> 
> Jeff Burcher
> 
+---
| 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
+---