Re: Runtime KLIST change?

[Jim Langston <jlangston@xxxxxxxxxxxxxxxx>]

If I had to do this I would just create two small files, with
nothing but the KLIST declarations.  Make two versions
of it, putting the correct version on each system.

Then in the program just #include the file.

That way your source code is identical, it's just the include
file that gets changed.

Regards,

Jim Langston

Frank Steinjan wrote:

> Hi Peter, hi Booth!
>
> It would be even for me interesting to know how this example will solve my
> problem? As I understood right the pointer only point to the first byte of 
>the DS
> which holds or references my record. What I wanted to do (or what I wanted to
> know is possible) is following, perhaps I described it wrong:
>
> I got two file:    file_a          and              file_b
>  with a key of       field_x                          field_y
>                            field_y
>
> the files are identical with the exception of that field_x!

<SNIP>

+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---