Re: V6.1 rejecting NULLS on inbound data from Web Methods.

So far, all I can establish is that WM is sending empty fields which I
think its converting to NULL. I saw this when starting debug on the server
job and then looking at the job log.

The table is an old table so its set by default to be NOT NULL.



On Thu, Oct 13, 2016 at 3:08 PM, CRPence <crpbottle@xxxxxxxxx> wrote:

On 13-Oct-2016 07:23 -0500, a4g atl wrote:

In our process to upgrade from v5.4 to 7.1, we upgraded first to
v6.1.

Nothing like forcing two times the fun ;-)

Most stuff worked but this one caught us by surprise. We have an
interactive call to our test system from web methods that fails with
a SQL0104 and message data truncation.

Well, the msg SQL0104 sqlcode=-104 is a Syntax error; with that error,
there is an expected token and position within the statement offered. That
combined with the statement that gets the error, and voilå; well on the way
to resolution. As to why a statement might have been able to get past
parsing and syntax checking in the past but does no longer, is a change to
the attributes for the table-reference, or a change to the SQL environment,
such as naming option or decimal separator.

As to the "data truncation" for which no message identifier is given,
there were in the past some issues whereby the SQL was *not properly*
notifying of SQLWARN warning conditions, and those were corrected as I
recall, with the DB2 for IBM i 6.1 SQL; and that the issue was in the Memo
To Users (MTU) for that release.

After much debugging, we were able to identify the interface did not
like NULLS. When replacing the NULLS with alpha characters it
worked.

How what the condition manifest; presumably some type of error, perhaps
in a log? Also, was the issue empty-strings vs actual NULL values; a quick
web search yielded some mention of an empty string being converted to NULL
by WM. If the target TABLE was defined with the NOT NULL attribute, and
NULL values were part of the results, then something like -407 msg SQL0407
suggesting NULL values were not allowed might be seen eventually for
/inbound data/?

Has anyone experienced this and how did you resolve it?

While I am quite sure *I* did not experience any issues, esp. with use
of the "Web Methods" feature that I do not use, for a lack of specific
details, I am unsure how most anyone could decide if "this" was something
they experienced; just sayin'

--
Regards, Chuck


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.