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



Hi Thomas

It's not a 7.3 change - it was done sometime after v5r4 - the thing now is, SQL assumes that literal values are VARCHAR, hence the mismatch message.

Does it cause the UPDATE to fail? I would not think so, it's just a nuisance, I hope.

HTH
Vern

On 1/8/2019 3:56 PM, Thomas Garvey wrote:
Hi,

I've got a program that is used to replace a particular value found in source members with another value.
It uses the SQL update command, as follows...
update QSQLSRC set srcdta=replace(srcdta,'oldvalue','newvalue')

This works fine on an old v5r4 box and the oldvalue and newvalue can have different lengths with no complaints
from SQL.
On a v7r3 box I get an SQL7939 message, saying 'Data conversion required on INSERT or UPDATE'.
The reason code is 3 (Reason 3 is that 'the INSERT or UPDATE value is a variable length string and column SRCDTA is not').

I can't see any difference in the files between the systems.  In fact,
the file on v7r3 is just a transferred copy of the file from v5r4.

What am I doing wrong, or what am I ignorant of here?

Best Regards,


Thomas Garvey




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.