Re: multi-occurrence DS methods

On a V5R1 system you have to define using Occurs in both the caller and callee - _BUT_ omit the Occurs on the proto.

As far as RPG is concerned the Occurs just defines how many of these DS things there are. As I noted earlier - whatever occurrence is in effect at the time of the call is the one passed. So to pass all of them set Occurrence to 1 before the call - that's all.

On 2013-09-30, at 4:24 PM, "Thomas Garvey" <tgarvey@xxxxxxxxxx> wrote:

Didn't realize this was needed, but how do I pass DataStructure as a
procedure parameter, and defined it in the called procedure?

On v5r2 and up, I can pass DataStructure as follows (but not in v5r1, which
is what I need to do)...

D ProgCall PR ExtPgm('SomePgm')
D Parm1 likeds(someDS)
D Parm2 likeds(DataStructure) dim(100)

As I understand it, the DIM(100) is stated on the parm definition because
that attribute of the DataStructure can not be passed. OK, but since on
v5r1 I can't use the dim(100) statement, nor occurs(100), how do I get the
DataStructure, which has 100 occurrences, passed to the procedure?

And similarly, how do I define the same parameter in the called procedure,
since I can't use the Dim(100) or occurs(100) statement?

Yikes. Am I screwed here? Do I have to pass 100 parameters instead?


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

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.

Jon Paris

www.partner400.com
www.SystemiDeveloper.com