Re: Using the RPG Cycle

"RPG400-L" <rpg400-l-bounces@xxxxxxxxxxxx> wrote on 05/03/2017 01:50:12
PM:

"RPG400-L" <rpg400-l-bounces@xxxxxxxxxxxx> wrote on 04/28/2017 03:11:46
PM:

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 went ahead and submitted an RFE for this, but I won't hold my
breath.

http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=104644


Well, IBM declined the RFE. Their response was that multiple
fixed-format C-specs are not required to handle any and all level breaks.
They said only a single L0 spec is required, which I didn't even know L0
existed. Here is an abbreviated portion of the previous code I posted
which shows what they suggested (and it tested out successfully).

exsr HEADINGS;

eval(h) VALU = COST * QUAN;
QUAN_L1 += QUAN;
VALU_L1 += VALU;
write DETAIL;

CL0 TOTALCALS TAG

if *inl1;
exsr L1TOTAL;
endif;
if *inlr;
exsr LRTOTAL;
endif;

begsr HEADINGS;
if *in90;
write PAGEHD;
write COLHD;
*in90 = *off;
endif;
endsr;

Sincerely,

Dave Clark