Re: %ADDR (or BASED?) Problem?

Hi Michael,

The problem is that the fields in your display file are not contiguous.

In other words, since the fields in the array are all defined to be one
after the other in memory, the fields in the display file must also
be allocated one after the other in memory.  Why?  Because they're both
accessing the same data.

[SNIP]
>
> and in my program I have :
> D               E DS                  ExtName(@MSI4 )
>

It appears that you understood this when you were working with the
database file.   You have @MSI4 loading into a data structure to solve
this exact problem (presumably), but you did not do the same thing for the
display file.

Just do something like

     D                 ds
     D  dspq01
     D  dspq02
     D  dspq03
     D  dspq04
     D  dspq05
     D  dspq06

and that'll force them to all be contiguous.

[SNIP]
> Can anyone help me understand what is going wrong here and/or how to how
> to fix it? Does it have something to do with 8-byte boundaries for pointer
> addresses? Why does it only seem to affect the display file fields?
>

Pointers must be allocated on 16-byte boundaries, I believe, not 8.  But
that's the location of the POINTER, not the data it points to, and in
any case is not related to the problem here.

It only affects the display file because the database file was already
being loaded into a data structure, so the fields are already loading
into contiguous space.