RE: Special file parameter issue

This is a key reason that it's a good idea to keep parameters as read-only
(VALUE or CONST), and to only use them as source to EVAL. If they're to be
two-way, then perhaps they should be set explicitly via EVAL, perhaps just
before RETURN.

myKeyData = parmKey ;
myDate = parmDate;

... code

parmReturn = returnValue ;


The whole process just gets so much simpler (at the cost of a couple more
variables) when you do that.

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"I find television very educating. Every time somebody turns on the set I go
into the other room and read a book."
-- Groucho Marx

This started to dawn on me just before your message showed up.

I moved on to the delete op code and I think I'm seeing the same thing.
I doesn't appear that the record portion is passed on a delete
operation either. I guess key information will need to be passed as
additional parms to specify which record to delete. Same thing if I
want to mimic a Chain or do any kind of record positioning.

Rick

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-
bounces@xxxxxxxxxxxx] On Behalf Of Scott Klement
Sent: Thursday, September 23, 2010 2:15 PM
To: RPG programming on the IBM i / System i
Subject: Re: Special file parameter issue

Hi Rick,

A WRITE statement in RPG will move the fields from your RPG program to
the file (or SPECIAL file program in this case.)

A READ statement does the opposite, it moves the fields from the file
(or SPECIAL program) to your RPG.

Therefore changing the fields before a READ doesn't make sense. But it
does make sense that the field values you change prior to a READ won't
be reflected in the SPECIAL program. After all... READ doesn't send
data out to the special program! It just gets data as input from that
program.