RE: multi-occurrence DS methods

Yes, that works even on v5r4, but I have to make this work on v5r1. The DIM
on a DS definition fails to compile.

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Alan Campin
Sent: Wednesday, September 25, 2013 12:19 PM
To: RPG programming on the IBM i (AS/400 and iSeries)
Subject: Re: multi-occurrence DS methods

Ran the following code without a hitch in V6R1 and V7R1. I think you have a
PTF issue.

d DataStructure...
d ds Dim(100)
d Qualified
d SubAField1...
d 2a Dim(10)
d SubAField2...
d 10a Dim(10)
d SubAField3...
d 15 6 Dim(10)

d x...
d s 10i 0
d y...
d s 10i 0
/Free

For x = 1 To %Elem(DataStructure);
For y = 1 to %Elem(DataStructure.SubAField1);
DataStructure(x).SubAField1(y) = 'AA';
EndFor;
For y = 1 to %Elem(DataStructure.SubAField2);
DataStructure(x).SubAField2(y) = 'BB';
EndFor;
For y = 1 to %Elem(DataStructure.SubAField3);
DataStructure(x).SubAField1(y) = 'CC';
EndFor;
EndFor;



On Wed, Sep 25, 2013 at 11:05 AM, Jon Paris <jon.paris@xxxxxxxxxxxxxx>wrote:

The big difference between the two is that if passed as a parm a DS
array will always reference the first char of element 1. With a MODS
the address passed depends on the occurrence in use as the time of the
call. So if using as a parm always make sure to set occurrence to 1 before

the call.

Beyond that making the change you describe should handle things.


On 2013-09-25, at 12:39 PM, Thomas Garvey <tgarvey@xxxxxxxxxx> wrote:

I have to retrofit a program so that it runs under v5r1 RPGLE
constructs (don't ask), and want to make sure the content of the
multi-occurring

data

structure is passed in the same way.

Here's how the DS is currently defined...
D DataStructure DS DIM(100) Qualified
D SubAfield1 2a DIM(10)
D SubAfield2 10a DIM(10)
D SubNField3 15 6 DIM(10)

On V5r1, the DIM on the DS line is not allowed.

I think I can achieve the same result by using the following

definition...

D DataStructure DS Occurs(100) Qualified
D SubAfield1 2a DIM(10)
D SubAfield2 10a DIM(10)
D SubNField3 15 6 DIM(10)

The difference in the ensuing C specs is that I can not directly
access

the

DataStructure elements as ...

DataStructure(x).SubAField1 = 'TG'

Instead I must refer to it as follows...

%occur(DataStructure) = x

DataStructure.SubAField1 = 'TG'


Am I correct? If this data structure is passed as a parameter,
would the data passed look the same to the receiving procedure in both

cases?

Thanks for any advice.

Tom Garvey

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

Jon Paris

www.partner400.com
www.SystemiDeveloper.com




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

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