×
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.
Check this link out:
http://publib.boulder.ibm.com/infocenter/iseries/v5r3/topic/db2/rbafzmstch2e
xpr.htm#wtco
Perhaps you need to cast one of the operands?
Elvis
Celebrating 10-Years of SQL Performance Excellence
http://centerfieldtechnology.com/training.asp
-----Original Message-----
Subject: CLOB Locator works fine on V5R2 but fails on V5R3
I have a procedure for which we use to put or get data from CLOB Locator. It
has been working fine for 2 - 3 years in V5R2. Our development box was
upgraded to V5R3 and it now fails with:
Message . . . . : Derived operands not valid for operator CONCAT. Reason
code 6.
Cause . . . . . : Either the derived operands are not compatible with
each
other or the operands are not compatible with operator CONCAT. The type
of
incompatibility is indicated by reason code 6. The reason codes and
their
meanings follow:
1 -- The operand is not character and not double-byte.
2 -- The operand is not numeric or numeric compatible. Numeric is not
compatible with date, time, timestamp, DBCS-only, non-Unicode graphic, or
binary string.
3 -- The operands must be the same type or compatible types.
4 -- The operand is a literal.
6 -- The result of the operation is greater than 32,766 bytes.
The sql it fails on is:
/End-Free
C/Exec SQL
C+ set :CLOBLocator = :CLOBLocator || substr(:clobString, 1, :length)
C/End-Exec
/Free
How can/should I be setting the value of a CLOBLocator with data that could
exceed the 32,766 limit?
Duane Christen
midrange.com
