Re: Finding invalid data in zoned numeric fields with SQL

This is a zoned field and not packed.

My bad. I didn't see where that was specified, and was just thinking
packed. I guess it comes from the S/32/4/6 days where blanks in a zoned
field became zero automatically, but blanks in a packed field produced the
error given.

Here's a thought: Use a RPG II in the S36EE to read the file and rewrite
to
a new native file (using program described files of course). In the
process
it will correct all the zone nibbles in zoned numeric fields. <gd&r>

Doug

PS - You can also use FIXNBR(*ZONED) with RPG IV, but that really isn't
quite the same thing as RPG II does.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.