× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



IBM confirmed the issue and is adding an APAR soon to address it.




From: Darren Strong <darren@xxxxxxxxx>
To: "RPG programming on the IBM i \(AS/400 and iSeries\)"
<rpg400-l@xxxxxxxxxxxx>
Date: 06/16/2017 11:43 AM
Subject: Re: OVERLAY with nested data structure
Sent by: "RPG400-L" <rpg400-l-bounces@xxxxxxxxxxxx>



I think part of my problem is that RDi 9.5.1.2 is complaining about the
overlay in a data structure definition. The compiler has no problem with
it though. The compiler was upset about the qualified keyword, so I was
hearing one thing and getting another. I supposed that's enough fuel for a

PMR.




From: Darren Strong <darren@xxxxxxxxx>
To: "RPG programming on the IBM i \(AS/400 and iSeries\)"
<rpg400-l@xxxxxxxxxxxx>
Date: 06/16/2017 11:33 AM
Subject: Re: OVERLAY with nested data structure
Sent by: "RPG400-L" <rpg400-l-bounces@xxxxxxxxxxxx>



Uh oh. I played with it some more, and it seems the "qualified" was the
invalid syntax. Once I removed "qualified" the compile proceeded. Sorry.

Was:
dcl-ds FullName qualified overlay(TtlSiz);
Should be:
dcl-ds FullName overlay(TtlSiz);


___________________________________
Darren Strong
Dekko



"RPG400-L" <rpg400-l-bounces@xxxxxxxxxxxx> wrote on 06/16/2017 11:27:37
AM:

From: Darren Strong <darren@xxxxxxxxx>
To: "midrange-RPG RPG message board" <rpg400-l@xxxxxxxxxxxx>
Date: 06/16/2017 11:27 AM
Subject: OVERLAY with nested data structure
Sent by: "RPG400-L" <rpg400-l-bounces@xxxxxxxxxxxx>

I'm trying out the new i7.3 TR2 stuff. I have a data structure like the



following that I'm trying to convert to nested, but I'm not allowed to
use
the overlay in a datastructure definition. I've pasted the error message



in the "Desired State" section below. Is there a way around this? This
example only shows one nested element, but my production program has
several. They were removed to simplify the example.


Current state:
dcl-ds CD_t qualified template;
Col like(CurCol_t);
Wid like(ColWid_t);
Hdg1 like(ColHdr_t);
Hdg2 like(ColHdr_t);
end-ds;

dcl-ds FullName1CD_t qualified template;
Col like(CurCol_t) INZ;
Wid like(ColWid_t) inz(46);
Hdg1 like(ColHdr_t) inz('');
Hdg2 like(ColHdr_t) inz('Employee');
end-ds;

dcl-ds T1 qualified;
TtlSiz;
FullName likeds(FullName1CD_t) inz(*likeds) overlay(TtlSiz);

arr likeds(CD_t) dim(T1Cnt) pos(1);
end-ds;

dcl-c T1Cnt %div(%size(T1.TtlSiz):%size(CD_t));


Desired State that gives the error:
dcl-ds CD_t qualified template;
Col like(CurCol_t);
Wid like(ColWid_t);
Hdg1 like(ColHdr_t);
Hdg2 like(ColHdr_t);
end-ds;

dcl-ds T1 qualified;
TtlSiz;
dcl-ds FullName qualified overlay(TtlSiz);
RNF0202: KEYWORD NOT ALLOWED FOR A NESTED DATA STRUCTURE SUBFIELD
Col like(CurCol_t) INZ;
Wid like(ColWid_t) inz(46);
Hdg1 like(ColHdr_t) inz('');
Hdg2 like(ColHdr_t) inz('Employee');
end-ds;
arr likeds(CD_t) dim(T1Cnt) pos(1);
end-ds;

dcl-c T1Cnt %div(%size(T1.TtlSiz):%size(CD_t));
--
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: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://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

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.