Re: More NULL variable trouble

"Wilt, Charles" wrote:

Having some more issues with respect to NULL variables and RPG.

I've got a module level DS defined LIKEREC.  Normally, since you have to
specify *INPUT or *OUTPUT, what I'll do is that in the procedure that
actually writes/updates the file I'll have another DS defined with the
appropriate *INPUT/*OUTPUT option.  Since I'm dealing with a PF, all
columns are INPUT/OUTPUT so all the procedure needs to do is

        EVAL LOCALDS = GLOBALDS;

Works fine, till now.  Apparently, the NULL indicators don't get updated
when EVAL'ing one null-capable DS into another.

I tried playing some games using based DS's, but that seem to really
screw stuff up.

Is there a good solution to this problem, or do I have to have either
two separate module level DS's, one defined *INPUT and one *OUTPUT, or
do I have to add a bunch of lines of code to set the %nullind of the
local DS fields according to the module level fields.

In V5R4, you'll be able to use EVAL-CORR which will assign
null-indicators for null-capable subfields, and OPTIONS(*NULLIND) on the
parameter so that the null-indicators will get passed with the data
structure parameter.

Prior to V5R4, I don't know of any way to handle it except adding the
bunch of %nullind assignments that you suggest.