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



I don't see the need to complicate things with pointers, a quick test
shows that this seems to give the desired result:

D PositionsDS DS
D 28A Overlay(PositionsDS)
D Inz('+
D ffooter+
D Ffooter+
D hheader+
D Hheader')
D Array Overlay(PositionsDS) Dim(4)
D Position 1A Overlay(Array)
D PosValue 6A Overlay(Array:*Next)

Trevor Briggs
Analyst/Programmer
Lincare, Inc.
(727) 431-1246
TBriggs2@xxxxxxxxxxx

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Rory Hewitt
Sent: Wednesday, August 07, 2013 1:19 PM
To: RPG programming on the IBM i (AS/400 and iSeries)
Subject: Re: Is this the simplest way to define corresponding arrays
inD-specs Ipostedan example of what I am trying to do (define
twocorresponding arrayswithinitialization values)
athttp://code.midrange.com/c7ffa28dce.htmlIsthe code shown in the
example the

Actually, a neater (V5R3-compatible!) version might be this:

D Positions Like(PositionsDS)
D Inz('+
D ffooter+
D Ffooter+
D hheader+
D Hheader')
D PositionsPtr * Inz(%addr(Positions)
D PositionsDS DS Based(PositionsPtr)
D Array Dim(4)
D Position 1A Overlay(Array)
D PosValue 6A Overlay(Array:*Next)




On Wed, Aug 7, 2013 at 10:15 AM, Rory Hewitt <rory.hewitt@xxxxxxxxx>
wrote:

Craig,

Would this work?

D Positions Like(PositionsDS)
D Inz('+
D fFhH+
D footerfooterheaderheader')
D PositionsPtr * Inz(%addr(Positions)
D PositionsDS DS Based(PositionsPtr)
D Position 1A Dim(4)
D PosValue 6A Dim(4)

Rory


On Wed, Aug 7, 2013 at 10:00 AM, Hiebert, Chris <
chris.hiebert@xxxxxxxxxxxxxx> wrote:

I've used this format in many programs.

D ItemTypes DS
D 7A INZ('CCredit')
D 7A INZ('DDebit ')
D ItemType 7A OVERLAY(ItemTypes) DIM(2)
D ItemTypeKey 1A OVERLAY(ItemType)
D ItemTypeDsc 6A OVERLAY(ItemType:*next)

I find it easier to interpret the data structure when each entry in
the
array has one INZ entry.
Since my data is related, this setup allows simple lookups.

VIDX = %LOOKUP(S0CITYPE:ItemTypeKey);
IF VIDX > 0;
S0CITYPED = ItemTypeDsc(vIdx);
ENDIF;

Chris Hiebert
Programmer/Analyst
Disclaimer: Any views or opinions presented are solely those of the
author and do not necessarily represent those of the company.

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of craig@xxxxxxxxxx
Sent: Wednesday, August 07, 2013 4:02 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: Is this the simplest way to define corresponding arrays in
D-specs Ipostedan example of what I am trying to do (define two
corresponding arrayswithinitialization values) at
http://code.midrange.com/c7ffa28dce.html Isthe code shown in the
example
the

I posted an example of what I am trying to do (define two
corresponding
arrays with initialization values) at

[1]http://code.midrange.com/c7ffa28dce.html

Is the code shown in the example the simplest/best way to define
and
initialize the arrays? If not, what is a better alternative (in
D-specs).

Thanks
Craig Pelkie

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




--
Rory Hewitt

http://www.linkedin.com/in/roryhewitt





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.