Re: Null Capable Fields

[boldt@xxxxxxxxxx]

Brian wrote:
>Here is a excerpt from the on-line AS/400 reference books (V4R4) on this
>subject:
>"If the file used for an externally described data structure has null-capable
>fields defined, the null attribute is not used in defining the RPG subfield."
>
>Is there a way to define fields internal to RPG programs as null capable?
>If not, is there a work around for this?

Sorry, no.

Our intention was that in the future, if there were enough demand,
we would possibly provide more support in this area.  Perhaps
something like a ALWNULL(*FULL) option.

The workaround is the brute force approach.  For each field declared
internally that you want to treat as null-capable, define an
indicator field that maintains the null attribute.   Then, every
time you copy a null-capable field, also copy that indicator value.

Cheers!  Hans

Hans Boldt, ILE RPG Development, IBM Toronto Lab, boldt@ca.ibm.com


+---
| 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
+---