RE: Specifying a data structure on a prototype

Joe,
I think you understand what you need to do.
LIKEDS implicitly declares the data structure as QUALIFIED so there won't be
a name conflict with the original EDS you declare.
You could move/copy the input DS to the unqualified original EDS as the
first line of code. That would put it into a non-qualified DS.
I like the QUALIFIED feature myself, perhaps if you're adding values to
numeric fields you don't like to do this:

   myDS.mySubfield =  myDS.mySubfield + XYZ

I'm sure you remember that on V5R2 and later you can code the following
instead:

   myDS.mySubfield  +=  XYZ


-Bob Cozzi
www.RPGxTools.com
RPG xTools - Enjoy programming again.


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Joe Pluta
Sent: Saturday, January 21, 2006 10:16 PM
To: 'RPG programming on the AS400 / iSeries'
Subject: Specifying a data structure on a prototype

Maybe I'm just not getting it, but I haven't been able to figure out how to
define an externally described data structure as an input parameter in a
prototype.  With a *ENTRY PLIST, I could specify the data structure in my D
specs, then simply specify the name of the EDS in my PLIST.  Now, though, I
can't seem to figure out how to do that.  The closest I've been able to get
is to define the structure as LIKEDS and use qualified on the original EDS
(because otherwise the subfields would collide).  The downside to that is
having to use qualified names throughout the procedure, which isn't
necessarily a bad thing.  Another option is to make the EDS based, and then
the first statement in the procedure is to set the basing pointer to the
address of the parameter.  Both work, but neither is quite as clean as I
would like it.

 

Any suggestions?

 

Joe