Re: [EXTERNAL] Re: detecting "bad data" using an sql statement

Hey Justin

There are all manner of ways for data to be put into a table and be corrupt - I can think of some option on CPYF that would do it.

So it is not just native RPG I/o that can put data into a table, or SQL INSERT or UPDATE - there are other mechanisms.

There IS a difference in the timing of when this is checked, a difference between SQL and RPG.

Cheers
Vern

On 1/12/2018 1:22 PM, Justin Taylor wrote:

I don't know how that's possible. You mind sharing for posterity?


Copying the data into a clone of the original table should choke on the invalid data. It might stop on each bogus row, which would be a pain if there are a lot of them.

Since this is the RPG list, you could write an RPG program using I-specs with your column(s) as character. Manually move the input field into a numeric field and trap for the decimal data error.



-----Original Message-----
From: Jay Vaughn [mailto:jeffersonvaughn@xxxxxxxxx]
Sent: Friday, January 12, 2018 12:39 PM
To: RPG programming on the IBM i (AS/400 and iSeries) <rpg400-l@xxxxxxxxxxxx>
Subject: Re: [EXTERNAL] Re: detecting "bad data" using an sql statement

Yeah that's been determined Justin. Now we are cleaning up. Any suggestions to a solution to my query?