Re: IMPORT exported RPG data structure

[Barbara Morris <bmorris@xxxxxxxxxx>]

Igor.Beslic@xxxxxxxxxxxx wrote:
> 
> I'm experimenting with EXPORTED DataStructures and I found I don't know
> how to properly do that. MODUL A is eporting DS and modul B is importing.
> There are two versions of modul B. One is working as I expected and
> another is working but obviosly DS structure is not resolved during bind
> time... I need opinion about examples listed down:

When you say it's not resolved, do you mean that the CRTPGM is failing,
or that the data structure does not have the correct value in the
importing module?

I'm guessing that you mean it does not have the correct value.  If so,
it is because you didn't define it the same in the importing module as
the exporting module.  You forgot to define the subfields in your first
case.  

> MODUL_B NON WORKING VERSION 
> ...
> D trans           DS                  IMPORT('TRANSAKCIJA')
>  /free
> ...

If you don't define any subfields, the compiler gives this structure a
length of 1, and does not define any subfields for it.

Try this, adding the LIKEDS keyword to define the imported data
structure properly:

     D trans           DS                  IMPORT('TRANSAKCIJA')
     D                                     LIKEDS(transaction)

IMPORT doesn't import the definition of the variable.  It only imports
the name.  The system would not care if you exported 'TRANSAKCIJA' as a
PACKED(5,2) and imported it as an array of CHAR(200) DIM(5000).  So you
have to make sure that the definitions match.  You might consider coding
the definitions in your /COPY file rather than duplicating them in each
source file.  The problems with having more than one definition for an
IMPORT/EXPORT variable are exactly the same as having more than one
definition for a prototypes.