Re: Data structure overlay *next failure -- RPG400-L

Hi Alan

An example is when you have, say, 5 fields in a record that are defined to be adjacent, and you want to make an array of them. You can't assume that they are actually adjacent in memory, so you can put them into a DS like this, then overlay the array over them - something like that - Jon Paris has some examples, maybe even in this thread.

Hope that made sense!
Vern

----- Original Message -----
Did not know that.
When you say " you are trying to put fields from a file in some order" when would that be needed? Do you have an example?

Alan Shore
E-mail : ASHORE@xxxxxxxx
Phone [O] : (631) 200-5019
Phone [C] : (631) 880-8640

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Vernon Hamberg
Sent: Wednesday, June 19, 2013 9:27 AM
To: RPG programming on the IBM i (AS/400 and iSeries)
Subject: Re: Data structure overlay *next failure

You don't have to use sizes if, for example, you are trying to put fields from a file in some order - one of the uses of a DS.

On 6/19/2013 8:21 AM, Alan Shore wrote:

Maybe it's something that I didn't know about, but where are the sizes - well - for anything? Or is this some routine that I don't know about?

Alan Shore
E-mail : ASHORE@xxxxxxxx
Phone [O] : (631) 200-5019
Phone [C] : (631) 880-8640

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of darren@xxxxxxxxx
Sent: Wednesday, June 19, 2013 9:18 AM
To: midrange-RPG RPG message board
Subject: Data structure overlay *next failure

I'm having an issue creating arrarys over fields in a data structure. I have something like the following, but the *next function doesn't work with the arrays. They seem to get their own memory, rather than being overlaid on the XWrkC* fields. I've seen lots of overlay examples, but I don't see them specify the actual data structure name in the overlay *next command, so I'm wondering if there is some restriction I haven't seen yet, where you aren't supposed to overlay on the data structure itself, but only on the subfields. In this case, the fields are actually display file fields, but I've seen this behavior with independently declared fields as well.

D ParmDS DS INZ
D XEnd6 overlay(ParmDS)
D XWeeks overlay(ParmDS:*next)
D xFac overlay(ParmDS:*next)
D XBuyC overlay(ParmDS:*next)
D XPlnC overlay(ParmDS:*next)
D XPVnd overlay(ParmDS:*next)
D XDept overlay(ParmDS:*next)
D XITYP overlay(ParmDS:*next)
D XWrkC1
D XWrkC2
D XWrkC3
D XWrkC4
D XWrkC5
D XWrkC6
D XWrkCA Like(xWrkC1) Dim(6)
D overlay(ParmDS:*next)
D xItem1
D xItem2
D xItem3
D xItem4
D xItem5
D xItem6
D xItemA Like(xItem1) Dim(6)
D overlay(ParmDS:*next)

--
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.

Disclaimer: This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. Any views or opinions presented are solely those of the author and do not necessarily represent those of the company.

--
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.