Source size limit in SQLRPGLE

346375 pts.
Tags:
RPGLE
SQLRPGLE
I've been having some problems compiling a 25,000 line program and I'm figuring that a line limit is causing all of my errors. Is there a limit to what the SQL pre-complier can handle for a SQLRPGLE source object?

Answer Wiki

Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Discuss This Question: 5  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • TomLiotta

    The limit will be highly variable based on how many SQL statements must be pre-compiled into HLL source.

    I've been having some problems compiling...

    What "problems" are you having? With 25,000 source lines, it's beyond any reasonable size and should be restructured. As SQL statements are replaced with RPG statements, the resulting statement count can increase quickly.

    If you generate the intermediate output from the pre-compiler into a permanent source file member, how many statements result?

    Tom

    125,585 pointsBadges:
    report
  • ToddN2000
    Like Tom suggested, 25,000 line is excessive for one program. Break the application up into smaller programs or procedures. Programs this large get to be a real nightmare to maintain. Is this code home grown or a pre-packaged bundle from a software vendor? I know from experience we have some vendor programs we needed to modify to suit our needs and we had about a 60% increase in the number of lines of code. It now stands at 29,951 lines. I do no think that size is you issue.
    11,295 pointsBadges:
    report
  • TomLiotta
    SEU has a 32K limit on source lines, but this isn't a SEU problem. Without knowing what the "problems" are, e.g., what error messages show, there's not much that can be said beyond general recommendations. -- Tom
    125,585 pointsBadges:
    report
  • ToddN2000
    Is your program using external source code like "COPYBOOKS" that are imported at compile time? Maybe the issue is these cannot be found due to the *LIBL during the object creation. What are the actual errors at the end of the compile listing? Post them an we can shed some more light on it for you.
    11,295 pointsBadges:
    report
  • TomLiotta

    The embedded SQL pre-compiler always uses a form of "COPYBOOKS", though they're not coded as such by the developer. They're better described as "macros".

    Every SQL statement is expanded into all of the HLL language statements necessary to complete the SQL function. That includes all data definitions used for everything SQL does. A very large program with some significant number of SQL embedded statements could have a large number of "copybook/macro" statements added by the pre-compiler.

    By specifying the TOSRCFILE() parameter on the CRTSQLxxx command, the generated source can be examined. That would at least give more info about what the actual problems are. Error message IDs would also be helpful.

    Tom

    125,585 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following