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

Vern,

So do you get the same 0-severity message on compile for both programs? Or
does the one with the logical fail to compile?

From the manual, "If ALWNULL(*NO) is specified, then you cannot process

records with null-value fields from externally
described files. If you attempt to retrieve a record containing null
values, no data in the record will be
accessible and a data-mapping error will occur."

So it would seem that successful compile with a run-time error is to be
expected. It also makes sense to me that you wouldn't see the run-time
error with the OAR handler as the handler is now responsible for data i/o
instead of the RPG / OS run time.

Charles

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

LOL - BTDT - no T-shirt

I replied to Charles after checking things again - the wild card here is
that I'm using an OAR handler - and I've not tried processing the tables
WITHOUT the handler.

OK, I took out the handler - compile still completed. But running the
program got an error due to the column that is null.

When run with the handler, it doesn't get an error - but that's probably
because I have to return the NULL-capability state for the fields.

More work to do!!

Thanks
Vern


On 10/15/2015 8:17 AM, darren@xxxxxxxxx wrote:

I am pretty sure that is not the case - because DSPFFD of the table

shows the fields as null-capable. DSPFFD of the logical shows the same
fields as null-capable.

Oh no! I just realized you told me that the fields were null capable, and
I suggested checking to make sure they were not. My own pet peeve of
support not reading my statement, and I do it to someone else.

Anyway, the difference might be in how you're defining the fields in your
program. I assume with the logical referencing program, that you're using
RPG's ability to define the fields automatically? In the program
referencing the SQL table, perhaps you're defining those explicitly
somehow. Your explicit definition might be bypassing the null capable
definition in the file. I read through your post, and to the best of my
knowledge, you didn't already state this one...

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