Re: Finding invalid data in zoned numeric fields with SQL

[Douglas Handy <dhandy@xxxxxxxxx>]

> select * from file where hex(decfield)  like '40%'
>
> Would that work for you?


It would be much safer to check the last byte for x40, or the entire length
of the field.  In your example, if the high order 2 digits were 40... you
would have a false match.  You need to check the last nibble of the final
byte, which normally is F for positive and D for negative number although
certain other values are permissible (if I mismember right, some mainframes
use C instead of D for negative numbers).  But a x40 in the final byte is a
pretty good indication the field was not initialized right.