RE: More NULL variable trouble

Nope.
One of the shortcomings in RPG IV, in my opinion is that you can't use "new"
opcodes or built-in functions with TGTRLS(*PRV). Sometimes it may be warranted
but other times...

-Bob Cozzi
www.iSeriesTV.com
iPod your industry news instead of reading it.
Coming June 2006
Ask your friends to tune into iSeriesTV.com


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On
Behalf Of Wilt, Charles
Sent: Wednesday, May 31, 2006 11:39 AM
To: RPG programming on the AS400 / iSeries
Subject: RE: More NULL variable trouble

Thanks Barbara,

Guess I better check on the status of my v5r4 upgrade.

Can you use eval-cor with TGTRLS(*PRV)?

Thanks,

Charles Wilt
--
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121
  

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx 
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Barbara Morris
Sent: Tuesday, May 30, 2006 5:01 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: 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.

-- 
This is the RPG programming on the AS400 / iSeries (RPG400-L) 
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.