RE: Overlaying a DS Array In a LIKEREC DS -- RPG400-L

True. But in this case, if I understand correctly, the OP is trying to overlay a portion of the DS he can't name that isn't starting in position 1. If you specify the starting location of the overlay the underlying names don't matter but you accomplish the same thing.

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Dennis Lovelady
Sent: Thursday, July 01, 2010 10:12 AM
To: 'RPG programming on the IBM i / System i'
Subject: RE: Overlaying a DS Array In a LIKEREC DS

You don't need to if it starts in position 1. There may be a preference or an in-shop standard that would cause you to want to, however.

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"Courage is walking naked through a cannibal village."
-- Leonard Louis Levinson

I think you need to specify where in the record to overlay. You can
overlay c or rec but in either case you will need to add the starting
position to your overlay definition.

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-
bounces@xxxxxxxxxxxx] On Behalf Of Eftimios Pantzopoulos
Sent: Thursday, July 01, 2010 12:32 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: Overlaying a DS Array In a LIKEREC DS

______________________________________________________________________
_
________________

Note: This e-mail is subject to the disclaimer contained at the bottom
of this message.
______________________________________________________________________
_
________________

I ended up using the based reference and that works fine. I've used
that solution in the past, but my colleagues aren't comfortable with
pointers and I was sure there was a solution that used the OVERLAY
keyword. Thanks for your help.

The second solution doesn't scan Simon. The editor highlights line1.18
& complains:

0001.14 d c ds qualified
0001.15 d rec likerec(rctldef)
0001.17 d array likeds(ctlds) dim(20)
0001.18 d overlay(c.rec.kpro1v)

The simple qualified name is not specified correctly.

It doesn't like the two qualifiers:

Message ID . . . . . . : RNF0623

Message . . . . : The simple qualified name is not specified
correctly.

Cause . . . . . : A simple qualified name is formed by specifying the
owning
data structure name followed by a period (.) followed by the
subfield name.
It cannot contain more than one period, and it cannot start or end
with a
period. The subfield-name part must be one of the subfields in the
data
structure.
Recovery . . . : Correct the simple qualified name. Compile again.

I tried removing the rec. out of desperation and it cleared the editor
syntax error, but failed on the compilation. I haven't posted the
compilation errors. I'm happy with the based solution.

______________________________________________________________________
_
________________

The information transmitted in this message and its attachments (if
any) is intended only for the person or entity to which it is addressed.
The message may contain confidential and/or privileged material. Any
review, retransmission, dissemination or other use of, or taking of
any action in reliance upon this information, by persons or entities
other than the intended recipient is prohibited.

If you have received this in error, please contact the sender and
delete this e-mail and associated material from any computer.

The intended recipient of this e-mail may only use, reproduce,
disclose or distribute the information contained in this e-mail and
any attached files, with the permission of the sender.

This message has been scanned for viruses.
______________________________________________________________________
_
________________
--
This is the RPG programming on the IBM i / System i (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.

Privileged and Confidential. This e-mail, and any attachments there
to, is intended only for use by the addressee(s) named herein and may
contain privileged or confidential information. If you have received
this e-mail in error, please notify me immediately by a return e-mail
and delete this e-mail. You are hereby notified that any
dissemination, distribution or copying of this e-mail and/or any
attachments thereto, is strictly prohibited.
--
This is the RPG programming on the IBM i / System i (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.

--
This is the RPG programming on the IBM i / System i (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.

Privileged and Confidential. This e-mail, and any attachments there to, is intended only for use by the addressee(s) named herein and may contain privileged or confidential information. If you have received this e-mail in error, please notify me immediately by a return e-mail and delete this e-mail. You are hereby notified that any dissemination, distribution or copying of this e-mail and/or any attachments thereto, is strictly prohibited.