×
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 3/26/2010 2:31 PM, James H. H. Lampert wrote:
At any rate, it was trivial to add a check for the existence of the
record before attempting to write it. Just did a SETLL on FOO, and
checked NOT %EQUAL(FOO) before writing to FOO.
A trigger error or RI violation or any other I/O error will also set 99.
Hopefully, the code doesn't simply ignore 99 and go on with life. The
point of this response is to note the above, plus the alternative (and
probably worse) solution of having the RPG program remove the CPF5026
messages from the job log, which would leave IN and messages relating to
genuine I/O errors.
I'd go for preemptively checking for duplicates myself.
--buck
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
