×
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.
On Apr 20, 2010, at 1:00 PM, rpg400-l-request@xxxxxxxxxxxx wrote:
Thanks for the reply. I definitely need to clean up the data but
right now
it's more important to come up with a viable solution to this type of
problem. I have hundreds of old QS36F files, many which have blanks
in
numeric fields (some of them packed).
One possible approach I haven't seen here so far is to actually treat
the file as externally described - which it is - just the key fields
are separate and the rest of the record in as many big lumps as needed.
Then define an externally described DS (or use LIKEREC) against it.
Even on an externally described files decimal data errors can be
avoided on I/O by using Read into a DS (actually this would work for a
program described file too). That way the errors only occur if you
"touch" the field - not on the read. That means it can be trapped with
MONITOR and corrected at the point of failure. If the logic of the
code says that you don't touch the "bad" fields then this would deal
with it.
Jon Paris
www.Partner400.com
www.SystemiDeveloper.com
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
