Re: Like keyword not keeping format

On 19 February 2018 at 11:19, Craig Richards <craig@xxxxxxxxxxxxxxxx> wrote:

But when the trigger fires and I execute an SQL insert in my RPG from
After.UniqueID into MessageID I see the following message in the joblog:

Message ID . . . . . . : SQL7939 Severity . . . . . . . : 00
Message type . . . . . : Information

Message . . . . : Data conversion required on INSERT or UPDATE.

-snip

I don't understand why there is conversion going on.
Am I missing something obvious?

Is the file being read and the file being updated the same files that
the compiler used? (Rule zero: check the library list)
What does the compiler listing cross reference say about the fields?
In particular, are there multiple definitions of either MESSAGEID or
UNIQUEID? Sub-procedure differs from main? (Rule one: trust the
compiler)
Is the program checking SQLSTATE after the INSERT/UPDATE? If so, is
there a deliberate reason to skip warnings like this?

I find some of these SQL errors hard to diagnose because there can be
multiple columns that have issues, and there's just one generic
SQLSTATE telling me that something went awry. It gets particularly
ugly when stored procedures, triggers, UDFs, and views of views are
involved. Is this particular program a simple TABLE to TABLE update
with no other Db2 functionality? I've scoured TRIGGER1 for hours when
it was really TRIGGER2 that had the issue. Doh!
--buck