Import/Export Variable Help

[Dennis Willett]

I am using V4.3 of the RISC operating system on an AS400. I have 3 RPG
IV modules.
One module does date validation. The first module calls the date
validation module exporting field DATE_USA. It also calls the second
module. The second module also uses the date validation module. Here is
where the problem starts. Using debug I see the
DATE_USA field loaded in the second module, however when it gets to the
date validation module it has the value that was last assed in the first
module.

Why would the second modules value not be exported to the third module?

Any help would be appreciated.

Dennis

[Tom Davidson]

Without the code it's hard to tell, but it sounds as if the parmater is
passed by value (VALUE) keyword on the prototype.

Dennis Willett <will...@glasscity.net> wrote in article
<37DD3B2C...@glasscity.net>...

> I am using V4.3 of the RISC operating system on an AS400. I have 3 RPG
> IV modules.

[Dennis Willett]

This is a CALLB not a prototyped procedure.I am not sure what you mean by
defining as STATIC.

Dennis

LJ Samuelson wrote:

> Hard to tell without seeing the D-specs. Maybe you have it defined as
> static in one of the modules?
>
> FWIW, I do not like using import or export unless you have an extremely good
> reason, usually performance. And then only where a limited number of
> modules interface with one another and variables are not exposed to the
> outside world. One of the problems with RPG III was that every variable was
> global. Import/export proliferates that situation. Passing parameters is,
> IMHO, a much better way to do thing.
>
> Dennis Willett wrote in message <37DD3B2C...@glasscity.net>...

> >I am using V4.3 of the RISC operating system on an AS400. I have 3 RPG
> >IV modules.

> >One module does date validation. The first module calls the date
> >validation module exporting field DATE_USA. It also calls the second
> >module. The second module also uses the date validation module. Here is
> >where the problem starts. Using debug I see the

> >DATE_USA field loaded in the second module, however when it gets to the
> >date validation module it has the value that was last assed in the first
> >module.
> >