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

I do - actually in both.

It turns out that I reported the wrong error - the 2nd program failed because, as I recall from so long ago this morning :) because I had a file name that I had not changed.

What we have found out is that we can compile a program that uses a file that has null-capable fields or columns - but it will get an error if one of those fields actually is null.

As you suggest, if I don't ever use a null-capable column, there is no problem.

The other thing I did not mention at first is that I am working with an OpenAccess-RPG handler. That does not change how the compiler works so far as null-capable fields are concerned. It does mean that one can have a database handler that does not tell the RPG runtime that a field is null - this would be a mistake (or maybe desired, to mask the challenge of handling null-capable fields?). If the runtime is not told about the null state, then it doesn't care.

Thanks
Vern

On 10/15/2015 1:26 PM, amunra@xxxxxx wrote:

Do you use directly null-capable columns in first programm?
*
Regards, Alex.
*
15.10.2015, 15:43, "Vernon Hamberg" <vhamberg@xxxxxxxxxxxxxxx>:

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: [1]RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: [2]http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: [3]RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at [4]http://archive.midrange.com/rpg400-l.

*

References

Visible links
1. mailto:RPG400-L@xxxxxxxxxxxx
2. http://lists.midrange.com/mailman/listinfo/rpg400-l
3. mailto:RPG400-L-request@xxxxxxxxxxxx
4. http://archive.midrange.com/rpg400-l