×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Lol, RPG cycle to the rescue!
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Douglas Handy
Sent: Monday, July 13, 2009 2:01 PM
To: Midrange Systems Technical Discussion
Subject: 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.
midrange.com
