SQL error handling

[Buck <kc2hiz@xxxxxxxxx>]

I have a complex SQL UNION that is throwing SQLSTATE 22023.  This is a
result of blanks in a signed column in one of the 4 files being UNIONed.
     There were no instances of this reported until I applied Cume 9104
last week.  I agree that SQL should tell me about corrupted data.  I
also agree that I need to fix the data; unfortunately it will be weeks
before we find and fix every internally described program that touches
this file and at the moment, the database manager is omitting rows with
the bad columns which isn't particularly useful for my inquiry users.

I have searched the support web site for applicable PTFs.  If I could
find the PTF that changed the behaviour, I'd remove it.  It'll take me a
long, long time to read every cover letter of every PTF that got applied.

My immediate question: Can I handle SQL column errors more granularly
than having SQL discard the entire row?  I expect the answer is 'no' but
I thought I'd ask anyway.
  --buck