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

On 14-Oct-2016 10:00 -0500, a4g atl wrote:

On 13-Oct-2016 14:08 -0500, CRPence wrote:

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

[…] call to our test system from web methods that fails with a
SQL0104 and message data truncation. […]

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/? […]

So far, all I can establish is that WM is sending empty fields which
I think it's 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.

Seems to match what I found in my cursory web-search+review; the implication, that the way WM will [has changed to] handle the empty-string data, by converting that to a NULL, would cause such a problem. But that does not explain a lack of message details for what presumably would have been seen in the joblog as something to do with NULL values [e.g. -407 aka msg SQL0407] versus something about either of a syntax error or a data truncation error.