Craig,
L3 (and L2 and L1) is set to on when the value in at least one of the L3
fields changes.
Regards,
Leo
On Feb 2, 2018 12:45, Craig Pelkie <craig@xxxxxxxxxx> wrote:
I'm working with some S/36 RPG II code shown below. I can "sort of"
understand the repeated definition of the field in column 66, to have
more
than one name for the same byte (although the field names in column 66
are
not otherwise used in the program).
I am unclear why the L3 indicator is defined more than once for the
fields.
It seems to me that a single definition of L3 would work the same.
Is this some level break idiom that I missed or am not remembering? The
programs are otherwise OK in terms of being straightforward to
understand
and work with (given that they are RPG II), so I think the original
programmer must have had some specific reason for coding like this.
<code>
IPRDIST NS 03 1 CP 2 CR 62
C3
I/COPY PAYLIB/QS36SRC,PRDIST
I 66 660GL2
L3
I 66 660GL2A
L3
I 66 660GL2B
L3
I 66 660GL2C
L3
I 66 660GL2D
L3
I 67
700DETAILL2
I 62 650GL1
L1
I 71 760DRRN
</code>
Craig Pelkie
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
https://archive.midrange.com/rpg400-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link:
http://amzn.to/2dEadiD
midrange.com
