Re: AW: Don't believe SQL debug joblog

On 1/8/2015 1:03 AM, Birgitta Hauser wrote:

If you convert a fixed length character field by using the scalar function
COALESCE, the result is returned as VARCHAR.

Yes, due to a string constant being considered a varying-length
character string (per SQL Reference, Constants). If they'd say VARCHAR
it would be clearer, and I left feedback.

When fetching this result into a fixed length field, data conversion occurs.
So message SQL7919 is correct.
Explicitly casting the result of COALESCE into a fixed length character
removed the message.

BTW message SQL7919 is not even a warning but only an information message.

Yes.

The reason I was in debug was that the code did a FETCH and then a check
for SQLSTATE='00000'. It wasn't; it was 01004 (truncation). The
problem with me following the joblog was that there were actually TWO
warnings, not one. One was the harmless SQL7919 and the other was
SQLSTATE 01004. The SQLSTATE did NOT put any message into the joblog;
there was only one joblog message and I stupidly assumed that it paired
up with the SQLSTATE 01004.

It didn't. SQLSTATE was my problem, and I should have ignored the
joblog. I should have known better.