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



kirkg@xxxxxxxxxxxxx wrote:
> 
> I don't have a lot of details but here goes.
> 
> I have a client with a very large program (OPM RPG) on a V4R5 730 with 1gb
> memory and 400+ gb of disk.
> The other day they made some additions to the code and it would not
> compile. Now they say all it said in the error
> message was the program failed to compile. I know there's a message
> somewhere but they can't find it.
> 
> The question to me was "How Big can a program be?" "Is there a limit to
> the lines in the source?" "Is there a limit in the size of the compiled
> pgm?"

OPM RPG has a limit of 999,999 lines in the source, and some other
maximum for total generated lines.  The listing would say if those
limits were overrun.

But there are also limits for the code that the compiler generates - a
maximum number of generated statements, names, labels etc.  These
generated things don't have a one-to-one relationship to your code, so
it's impossible to tell from looking at your code if it would blow one
of these limits.

Try converting the program to ILE RPG - there are limits there too, but
they are usually much harder to reach.  Next easiest is to split out
some part of the program that isn't doing any I/O, and call it from the
first program, passing parameters for any fields it uses.  Next easiest
is to create subroutines for any identical reused I/O opcodes and do
EXSR to the SUBR instead of say READ.


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.