× 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.



> When a RPG IV Program bombs, it tells me a statement number that does not
> coorespond with my RPG source code line number. Why is the number
> different?

Well.. let's presume you haven't reorganize the statement numbers of the source
;-) :
there are *two* "statement" numbers in RPG !V. - What you mean is probably not
the statement number (referring to the source) but the number each compiled
line gets during compilation. - You can realize it when you compile a PGM and
look at the "compilation list". (well... I should really try to get a list with
all the original english IBM terms  ;-)

What to avoid or how to compile... i cannot say because i havent have the
problem yet (probably because of always compiling with debug *SOURCE option),
but i guess a lotta other specialist will give you more precise hints. ;-)

Andreas K., Germany.

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the RPG/400 Discussion Mailing List!  To submit a new         *
* message, send your mail to "RPG400-L@midrange.com".  To unsubscribe   *
* from this list send email to MAJORDOMO@midrange.com and specify       *
* 'unsubscribe RPG400-L' in the body of your message.  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.