Re: Q about RPG II level break usage

[aec <cfuture@xxxxxxxxxxx>]

Been a very long time for me too, butI think that what those I-specs do 
in RPG2 is it reads the same record position into all those different 
fields. If I remember correctly, each of those different field names 
used different storage locations. IF so, and that's IF I remember it 
correctly, it might be a "clever" way of moving that same input 
character into different fields instead of using MOVE.

Alan



On 2/2/18 6:45 AM, Craig Pelkie 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