×
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 20-Jun-08, at 1:00 PM, rpg400-l-request@xxxxxxxxxxxx wrote:
Has anyone had any experience handling decimal data errors at the
field
level? I know you can trap for the decimal data error that happens
when a
record is read
Assuming that the "correct" approach - i.e. fix the problem - is not
an option ...
You can't really handle them if you you allow them to happen on the
read as you are now in a series or evals generated by the compiler to
move the individual fields out of the buffer. Even if you could
identify which field was the problem, you are still in a situation
where some fields from the new record are populated and others are not
- so continuing the processing is not really possible.
The best solution is to use an externally described or LIKEREC DS to
describe the file and then use that as the result factor on the read/
chain/whatever. That will allow you to trap the error(s) on the
individual fields with MONITOR and to process them appropriately.
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
