RE: Sharing variables between procedures

Qualified data structures and LIKEDS should (I hope) be an option to me in
the coming months.  I've been told a new box is probably coming by early
next year.  I suspect I will have much reading of the RPG manual to do when
that becomes a certainty.

IMPORT/EXPORT would show the relationship between the procedures if they
were in the same module.  I would use the same data structure name in each
procedure with the only difference being the EXPORT in the "main" procedure
and "IMPORT" in the "children".  I wouldn't consider using this option if
the procedures were not in the same module since one would then have to
search through the modules to figure out what the relationships are, and
that's painful.  Parameters are more obvious.  This, of course, is really
moot as IMPORT/EXPORT are meant to work with procedures that do not reside
in the same module. 

Donald R. Fisher, III
Project Manager
Roomstore Furniture Company
(804) 784-7600 extension 2124
DFisher@xxxxxxxxxxxxx


<clip>
What you really should do is use QUALIFIED data structures and LIKEDS()
parameters -- unfortunately, this requires V5R2.
<clip>
> It has the added benefit of showing the relationship between the "main"
> and "child" procedures.

I don't follow this.

<clip>
Frankly, defining your parameters as LIKEDS is a much better idea than
using pointers.   But, using a pointer is a parm is still much much better
than using import/export!!
<clip>