Re: Externally-Described Field used as array name.

["Joep Beckeringh" <joep@xxxxxxxxxxxxxxxxxxx>]

Patrick,

When you overlay an array, the result is automatically an array as well.
What you can do is this:

D                 ds
DPdLb_fld
DPdLb01                               Overlay(PdLb_fld:*NEXT)
DPdLb02                               Overlay(PdLb_fld:*NEXT)
DPdLb03                               Overlay(PdLb_fld:*NEXT)
DPdLb                                 Like(PdLb01) Overlay(PdLb_fld) Dim(3)

You create a dummy field that contains the array (I think the compiler
calculates the length for you).  You make the individual fields overlay the
dummy field; you don't have to supply the definition if they are defined
elsewhere (externally described file); by using *NEXT you don't have to
worry about the positions either.  Lastly you create an array that overlays
the dummy field (and thus the individual fields) by not specifying *NEXT or
a position (or by specifying ':1').

Joep Beckeringh


----- Original Message -----
From: <PatrickConner@parkdalemills.com>
To: <rpg400-l@midrange.com>
Sent: Thursday, August 23, 2001 10:06 PM
Subject: Externally-Described Field used as array name.


> D                 ds
> DPdLb                                 Like(PdLb01) Dim(3)
> DPdLb01                               Overlay(PdLb)
> DPdLb02                               Overlay(PdLb:8)
> DPdLb03                               Overlay(PdLb:15)
>
>
>    932=I                             S   60   66 0WK1AVL
>    933=I                             S   67   73 0PDLB02
> ======>                                           aaaaaaaaaaaaaa
> *RNF4138 30 a      000016  Externally-Described Field used as array name.
> Definition
>                            specification is ignored.
>    934=I                             S   74   80 0WK2SHP
>
>
> Why?
>
> I think I understand that it is a memory address thing, but I'd like an
> clear explanation.
>
> Patrick Conner
> www.ConnecTown.com
> (828) 244-0822