Re: This is confusing me. What are these lines of code doing?

[Booth Martin <booth@xxxxxxxxxxxx>]

I suspect my confusion was simple.  It appears I did understand the code 
but could not imagine any reason it was written the way it was written. 
 I F16'd the program for COLLTXT( and it was never used that way.  The 
only reference to the array is one instance of MOVE blanks to the array.

Experience has taught me that when I can't see why something is written 
the way it is written then I best be careful and not walk into a mess 
and make it even worse.

So I've learned to ask questions.  I think Shannon explained why it was 
written the way it was.  Multiple occurrence data structures always 
struck me as being a solution looking for a problem to solve.

Thanks to everyone that responded.  Now I feel confident about solving 
the problem I was assigned.



Jon Paris wrote:
> Does it make it any easier to understand if I show it RPG IV style rather
> than converted RPG III Booth?  
>
> This is what the structure looks like.  Any additional array elements should
> be added as shown.
>
>      D CollSO_DS       DS
>      D  CollTxt1                     60
>      D  CollTxt2                     60
>      D  CollTxt3                     60
>      D  CollTxt4                     60
>      D  CollTxt5                     60
>      D* Add additional elements of 60 here then change DIM
>      D  CollCode                      3
>
>      D CollTxt                       60    DIM(5) Overlay(CollSO_DS)
>
> I have to assume that the programmer wanted to reference the individual
> fields by name for some reason. Perhaps to output the data to a display
> file?  Build the data up as an array, but populate the display file without
> having to do the individual field moves.
>
>
> Jon Paris
> Partner400
>
> www.Partner400.com
> www.RPGWorld.com