RE: %elem and nested data structures

["Schmidt, Mihael" <Mihael.Schmidt@xxxxxxxxxxx>]

Silly ... yes ... I totally agree.

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Scott Klement
Sent: Thursday, November 05, 2009 8:23 PM
To: RPG programming on the IBM i / System i
Subject: Re: %elem and nested data structures

Hi Mihael,

It's always worked this way.  I've always worked around it by coding 
like this:

     dsply %char(%elem(top.eans));
     dsply %char(%elem(sub1.eans));
     dsply %char(%elem(sub2.eans));

Since top.sub.eans, by definition, will always have the same number of 
elements as sub1.eans, this should work fine.  It's silly that we have 
to do this, but that's the way it's been since this support was released

in V5R2, I don't even think about it anymore.


Schmidt, Mihael wrote:
>      D top             ds                  qualified
>      D  sub                                likeds(sub1)
>      D  eans                         13A   dim(10)
>
>      D sub1            ds                  qualified
>      D  sub                                likeds(sub2)
>      D  eans                         13A   dim(10)
>
>      D sub2            ds                  qualified
>      D  dan                           7P 0
>      D  ean                          13A
>      D  eans                         13A   dim(10)
>
>       /free
>        top.sub.sub.eans(1) = '1234567890123';
>        dsply %char(%elem(top.eans)); // works
>        dsply %char(%elem(top.sub.eans));  // does not work RNF0623E
>        dsply %char(%elem(top.sub.sub.eans));  // does not work
RNF0623E