Re: Interactive Source Debugger - error?

At 08:40 12/05/1998 , Tim Truax wrote:
>I tried this same debugging session last night, but this time (shame on 
me) I
>made sure I read back thru the joblog, at it appears that about 7 messages 
back
>from this message -  "XXXPGM is not in the debug environment" - there were 
more
>serious errors about a specific file that was referenced by the RPG 
program not
>being locateable in the *LIBL.  But what the heck gives with getting the
>unrelated and confusing/misleading msg above?  Why doesn't it just put the 
REAL
>message (like the one related to the actual problem) at the bottom of your
>screen?  Maybe I am too new to the AS400 to fully understand this 
phenomena, 

Imagine having to write an error handler that needed to monitor several
thousand detailed error messages - what a pain!  Instead, the 400 breaks
messages into several types: 
*ESCAPE is a fatal error - these can be monitored
*DIAG is a detailed diagnostic message - not directly monitorable
and so on.  The way it works is that OS400 issues as many *DIAGs
as it can, then a very generic *ESCAPE message to let you know
the process died.  This way, you can MONMSG for a small number
of *ESCAPE messages, but do a RCVMSG to get the details if you
want.

In the case of debug, I think that the debugger is trapping 
the *ESCAPE message that the RPG runtime normally issues, and
then issuing an escape message of its own.  If you were to run
this outside of the debug environment, I;m sure it would make
more sense.

Buck Calabro
CommSoft, Albany, NY
mailto:mcalabro@commsoft.net


+---
| 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
+---