Re: Does RPGLE handle NULL capability differently between DDS-based and SQL-based files?

Vern,

I'm not aware of any differences, and my understanding is it shouldn't.

Are you sure about what you are saying? Are you sure the table has allow
null?

Same *LIBL for both compiles? Same compile command, CRTBNDRPG vs CRTRPGMOD?

Check the compile listing to see actual options in effect for both
compiles. I'm wondering if you've got a RPGLEHSPEC data area affecting one
compile but not the other.

Charles



On Thu, Oct 15, 2015 at 8:43 AM, Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>
wrote:

Just ran into this and I' m not sure what I'm seeing.

I have a table (SQL) that I'm using in an RPGLE program. It has
null-capable columns in it. The compile went fine - I had no control option
and CRTBNDRPG ALWNULL parameter = *NO.

I have an LF (DDS) over the table that I'm using in another RPGLE program.
The compile fails, saying there are null=capable fields.Adding the ALWNULL
setting made it work.

So does RPG default to ALWNULL in some form with SQL tables? By design?

Curious I am!

Vern
--
This is the RPG programming on the IBM i (AS/400 and 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.