× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I was wondering how to get it to use the field default values, ie blanks.

On some ODBC drivers you can specify to use thje field default thereby
replacing NULLS with blanks.

I cannot see how this is done.

Darryl

On Fri, Oct 14, 2016 at 11:16 AM, CRPence <crpbottle@xxxxxxxxx> wrote:

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.


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


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.