Sorry...The DS in question is the file information DS for the DSPF which
is declared in the callee. The file is defined globally and so is the
INFDS. When the procedure is called, the procedure uses a local
definition from the PI instead of the global.
I don't think I can declare an INFDS as a local variable for a DSPF
defined globally...but I'll give it a try come Monday.
I'm on V5R4 currently...I heard V6 will allow local declaration of files
which would, I think, make this problem go away.
Thanks...have a good weekend all...
- Steve
-----Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of DeLong, Eric
Sent: Friday, June 20, 2008 5:02 PM
To: RPG programming on the AS400 / iSeries
Subject: RE: Sharing Global Variables between Modules
Stephen,
Ok, so now I'm wondering why you don't simply pass the DS as a parm to
module CONTROLLER. By default, parms are passed by reference, meaning
that a pointer to storage defined in module VIEW is passed, which is
then used in called program as if it were declared locally.... This
sounds exactly like what you are asking for. Both VIEW and CONTROLLER
would be accessing the same memory locations.
I'll assume that your app is constructed from three modules: Program
PGM, Module VIEW, and Module CONTROLLER. For what you are doing, I
would declare all my DS storage in Program PGM, then pass this DS (by
reference) to both modules (CONTROLLER and VIEW) as needed.
hth,
Eric
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Coyle, Stephen F.
Sent: Friday, June 20, 2008 3:21 PM
To: RPG programming on the AS400 / iSeries
Subject: RE: Sharing Global Variables between Modules
I've never used the IMPORT/EXPORT on a DS before as I've heard bad
things about "hidden" interfaces.
Let me clarify the requirement...
One of the modules is the VIEW and it contains my DSPF.
The other module is the CONTROLLER.
Both modules declare the DS globally using a third part ERP /copy.
The DS in question is loaded in the view when it is initialized.
The controller needs access to the data in the loaded DS and may also
modify the DS content.
If the DS is modified in either module, the other module needs to know
this.
The problem I had was I would pass the global DS from the caller to the
callee. The callee would treat the passed parm as a local variable
(defined on the PI) instead of accessing it's global variable of the
same name.
I ended up moving copies of the DS around but thought pointers might be
a simpler solution.
Not sure if that is any clearer....
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Wilt, Charles
Sent: Friday, June 20, 2008 3:49 PM
To: RPG programming on the AS400 / iSeries
Subject: RE: Sharing Global Variables between Modules
They could be....
If one module has the DS specified with EXPORT and the other has the DS
specified with IMPORT.
But, generally speaking that's a bad idea that you should stay away from
if at all possible.
I'm afraid I don't quite understand what you have vs. what you are
asking for.
Each module has the DS, correct?
It currently isn't shared between modules?
Now you need it to be?
The question is why do you think you need this?
Eric is probably on the right track, take the DS out of the modules and
encapsulate it in its own
module along with appropriate accessor procedures. Now modify the
existing modules to use the
procedures from the new one.
However, I have to say, I'd be a little concerned. Depending on the
accessor functions you provide
for the DS data, this method may not be any better than just using
IMPORT/EXPORT to share the DS.
HTH,
Charles Wilt
--
Software Engineer
CINTAS Corporation - IT 92B
513.701.1307
wiltc@xxxxxxxxxx
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Coyle, Stephen F.
Sent: Friday, June 20, 2008 3:21 PM
To: RPG programming on the AS400 / iSeries
Subject: RE: Sharing Global Variables between Modules
Vern,
I understand I would not have to pass a global variable to
procedures contained in the same module.
These are calls between procedures in different modules. The
variable is declared in both modules as global.
These are not shared when both modules are bound into a
program...Correct?
This e-mail transmission contains information that is intended to be
confidential and privileged. If you receive this e-mail and you are not
a named addressee you are hereby notified that you are not authorized to
read, print, retain, copy or disseminate this communication without the
consent of the sender and that doing so is prohibited and may be
unlawful. Please reply to the message immediately by informing the
sender that the message was misdirected. After replying, please delete
and otherwise erase it and any attachments from your computer system.
Your assistance in correcting this error is appreciated.
midrange.com
