RE: Passing unwanted parameters

["Kurt Anderson" <kurt.anderson@xxxxxxxxxxxxxx>]

If you don't specify the Dtaara it's using the LDA, right?  So what you
were wanting to do with UDS w/o specifying the Data Area, you could do
with Dtaara(*LDA) instead, which would allow you to do the INs and OUTs.
 
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Rory Hewitt
Sent: Tuesday, January 13, 2009 2:19 PM
To: RPG programming on the IBM i / System i
Subject: Re: Passing unwanted parameters

Scott,

Actually, I discovered that if you define the data area with the
following
definition in both caller *and* the called program, then it can be both
read
*and* written in the called program:

D ExtraParm      UDS            32    Dtaara(EXTRAPARM)

However, if you define it without the DTAARA keyword in the called
program,
then it gets read in automatically, but you can't use the OUT opcode on
it,
since the program thinks it's not a data area.

For some reason, I thought that the IN and OUT opcodes worked on UDS's
which
didn't specify the DTAARA keyword, but apparently not.

Rory


On Tue, Jan 13, 2009 at 11:52 AM, Scott Klement
<rpg400-l@xxxxxxxxxxxxxxxx>wrote:

> Hmmm... I didn't think you could read a data area that's locked by the
> caller?  Am I misremembering?