Maximum number of records limitations in SEU is only 32,764 records. Is there a way arround that?

35 pts.
Tags:
SEU
I am implementing the NESTING concept which requires me to add more lines of code to the same module. This makes the size of my module exceeds 32,764 lines which is the maximum allowed by SEU. Is there anything that I can change on the defaults of SEU to allow the physical number of lines to be greater than 32,764? Here is the error message I am getting in SEU: "Member CT110 in file NNNLIB/QCBLSRC exceeds 32764 records."

Answer Wiki

Thanks. We'll let you know when a new response is added.

Wow – I cannot image how this is a good thing.

1. Copy books — don’t know the limitations on Cobol precomiler/compiler
2. Calls

These could all be seperate modules built into a single program object.
Phil

——————————————
My issue with this question wasn’t with the editor it’s with the design.

It appears that this person is re-engineering a cobol program and creating a new program with over 32000 lines of source. We keep trying to find the funds to break some of our programs into smaller units.

Phil

Discuss This Question: 7  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
  • Cwc
    Aside from re-architecting the program (easier to say than actually doing, of course), what about using a newer editor, like RSE within Websphere?
    4,290 pointsBadges:
    report
  • Yorkshireman
    Surely you can nest tsource includes in Cobol? - added to the RPGLE precompiler ages ago. If so, then break up the huge source to sensible parts, and either have one object which includes all others, or daisy chain together.
    5,580 pointsBadges:
    report
  • Rlsantucijr
    Yes, using Remote System Explorer - IBM Websphere Development Studio Client for iSeries is the answer. Yes, using copylibs and also subroutines / subproprograms (sorry, I'm old school), will work also. I noticed you showed that the member was in QCBLSRC so I'm assuming you're using OPM COBOL (aka COBOL 400). You may run into a problem such as with OPM RPG (aka RPG 400) of the program being too big to compile. I'd suggest switching to CBLLE to be safe. It won't solve your 32,764 member size problem, but it might keep another problem from cropping into the picture.
    445 pointsBadges:
    report
  • WoodEngineer
    Dude . . . that would get you fired in my shop.
    6,650 pointsBadges:
    report
  • graybeard52
    Actually, we have run into both situations modifying Mapics code. SEU bombed out trying to a add a small mod to a program. Finally got the programmer to use RSE - I personally haven't used SEU for RPG for years now. The other situation was we exceeded the maximum number of variables for a program. Simply converted it to RPG-IV with DFTACTGRP and it worked fine. I agree it makes sense to split these programs up, but its a lot of work when dealing with 3rd party stuff written in the 80's.
    3,115 pointsBadges:
    report
  • graybeard52
    Hey, WoodEngineer, which action gets you fired? Fixing the program or using a non-deprecated editor ?
    3,115 pointsBadges:
    report
  • WoodEngineer
    Good question, Graybeard. Developing a program with that many lines of code in a single program is the offense.
    6,650 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