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


  • Subject: RE: RPG/RPT Compiler Limitations .. CPF6301
  • From: Kevin H <KevinH@xxxxxxxxxxx>
  • Date: Wed, 11 Apr 2001 18:24:17 -0400

the second of my replies that went missing.

thanks to all for your input and pointers.

ta
kmh

<<<<<<<<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>
sorry - i missed out some questions.

My machine is on the latest PTFs at Rel 4.5
the vendors machine is at 4.4, i believe latest or second to latest PTFs.

Remember, this is a really big program.
When i compile the RPT and tell it to generate a RPT source member,
that member exceeds 40 000 lines of code.


In the interrim I have found a work-around.

I took some logic where they called an external pgm 4 places in the pgm 
with a lot of parms,
then turned that into a subroutine.

the net result is 4 EXSR but only one CALL defined to the program.
This caused the program compilation to be successful.

Interesting.

I would be interested to see if you have any ideas .

tks
kevin



At 01:27 PM 4/11/2001, you wrote:
Are you up to date on PTFs?
What did you add that the compiler is unhappy about?
Perhaps I can duplicate it...?

+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-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 ...


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.