Re: ILE Exporting Variables and *DUPVAR

On 3/15/2012 1:58 PM, Schmidtberger, Gregory P wrote:

I have several modules compiled into a service program. They each control inserts/updates/and deletes to specific tables. And all these modules export a data structure with exactly the same name. Because they all export a data structure with the same name I have compiled the service program with *DUPVAR. This service program is like a database service. And then I have an RPGLE program that binds to this service program and uses the exported sub procedures from those modules for database updates. This RPGLE program also IMPORTS the data structure being exported by the modules. All are compiled and bound correctly so it appears. When I tested this with a single module I was able to get to the imported data in that data structure. But I'm having a problem. Now that I have several modules compiled the imported data structure is always coming back to the RPGLE program empty. I would like to keep a single name for the exported data structure so that my upstream programs can always count

on importing a single data structure. Does anyone know if what I'm attempting to do should work or not? Or is the fact that all the modules exporting the same data structure name is causing a problem? Thanks.

Aside from aesthetics, does it really matter if you randomly choose the
one procedure to own the storage for this DS? That is, pick one
procedure to be labelled EXPORT and make the rest IMPORT. The compiler
will let any IMPORT procedure update/read the DS, won't it?
--buck