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



On Fri, Apr 28, 2017 at 3:11 PM, <dlclark@xxxxxxxxxxxxxxxx> wrote:
So, in
RPG, if I have L1, L2, and L3 defined then I have to also define 4
different accumulator fields and accumulate them myself in c-specs?

Well, if you take a lawyerly reading of that, the answer is no,
because you don't have to define exactly four accumulators. You can
break without totaling, or you can total more than one value per
break. But if you want to accumulate anything, you have to explicitly
do it yourself. RPG will not auto-total anything.

OK, I got the following working. My question is, is this the best
that can be done from the perspective of using free-form as much as
possible?

Not sure. I think so, but it's a question for someone better at RPG
than I am to answer definitively.

Too bad IBM didn't give us special subroutine names for the
control levels like BEGSR *INL1, BEGSR *INL2, ... BEGSR *INLR so that we
could eliminate a few more fixed-format C-specs when using control breaks.
I wonder if they'd be amenable to accepting an RFE in this area?

I agree special subroutine names would have been nice, and there's no
reason you couldn't submit the RFE, but I think its chances of
acceptance would be minimal. I doubt IBM would want to invest ANY
resources to anything that might be an encouragement to use the cycle.

John Y.

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.