RE: Using the RPG Cycle

I seem to recall that these two aren't identical and the *inL1 won't operate as desired.

1.
if *inl1;
exsr L1TOTAL;
endif;

2.
CL1 exsr L1TOTAL




-----Original Message-----
From: dlclark@xxxxxxxxxxxxxxxx [mailto:dlclark@xxxxxxxxxxxxxxxx]
Sent: Friday, May 05, 2017 12:01 PM
To: RPG programming on the IBM i (AS/400 and iSeries) <rpg400-l@xxxxxxxxxxxx>
Subject: 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
--
int.ext: 91078
direct: (937) 531-6378
home: (937) 751-3300

Winsupply Group Services
3110 Kettering Boulevard
Dayton, Ohio 45439 USA
(937) 294-5331




*********************************************************************************************
This email message and any attachments is for use only by the named
addressee(s) and may contain confidential, privileged and/or proprietary information. If you have received this message in error, please immediately notify the sender and delete and destroy the message and all copies. All unauthorized direct or indirect use or disclosure of this message is strictly prohibited. No right to confidentiality or privilege is waived or lost by any error in transmission.
*********************************************************************************************