Re: Bad numeric data

[Booth Martin <booth@xxxxxxxxxxxx>]

Perhaps a small RPG program defining the file as a program-described 
file with I-fields defining the columns in question? Instead of 
eternally described?  That allows you to look at the data as-is to help 
define the problem? Once the problem is defined you can look at your 
options for repairing the problem.

On 5/14/2015 10:42 AM, John McKee wrote:
> A field on a file on the remote 520 is defined as numeric 8 0.  Supposed to
> have date in form of CCYYMMDD.  I ran a query on the field.  Lots of bad
> values.  I was hoping to see what might be in the field.  Never worked with
> CAST in SQL.    Never needed to before.
>
> When I try this:
>
> select cast(xxxxxx as char(20) from xxxxxx. I get either some numeric value
> (usually a single 0) or the '+' sign with it repeated 20 times.
>
> An IBM query on the field showed the values as different - at least when
> sorted and grouped, each group had one record.
>
> I am not sure, yet, what value should be forced into the field to clean up
> the data.
>
> How do I add a where to the above select to only locate non-numeric values?
>
> John McKee