RE: RPG IV not up to the task of reading and writing to DB files....

Barbara,

That's good news.  I did look at the v5r4 manual to see if there had
been any improvements, but I missed that.

Any clue as to how long we'll have to wait for full NULL support?

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: Thursday, May 18, 2006 5:54 PM
> To: rpg400-l@xxxxxxxxxxxx
> Subject: Re: RPG IV not up to the task of reading and writing 
> to DB files....
> 
> "Wilt, Charles" wrote:
> > 
> > Still, I have procedures that really need some way to 
> return or set a
> > reference variable to a NULL value.  Can't be done, there's no such
> > thing as a standalone null capable variable in RPG.
> > 
> 
> Starting in V5R4, you can code OPTIONS(*NULLIND) on a 
> parameter, and the
> null-indicator(s) for the parameter will get passed along 
> with the data
> (available for reference or CONST parameters).  There's no nullind
> support for return values, though; only parameters.
> 
> You still can't define a standalone null capable variable, but you can
> define an externally-described data structure and the alwnull fields
> will become null-capable subfields.  (This was available starting in
> V5R2, but it wasn't much use for parameters, since the null values
> didn't get passed along with the data structure.)
> 
> -- 
> 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.
> 
>