× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



At 08:40 12/05/1998 , Tim Truax wrote:
>Hi again,
>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, 

That's pretty typical. I've just accepted it. I don't think it's any better on 
other systems either. The problem is the complexity of delivering meaningful 
messages for error conditions that are pretty unpredictable. At least if you 
dig through the joblog, you can usually find out what the problem is.



Pete Hall
peteh@inwave.com 
http://www.inwave.com/~peteh/

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


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.