×
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.
Given a trigger program on a file, written in ILE RPG, that has a
statement to the effect of:
C WRITE FOO 99
(with *IN99 in the "LO" column, to catch exceptions)
(And don't blame me; I'd have certainly checked to see whether I was
trying to write a FOO record that already existed BEFORE trying to write
it, and I'm analyzing the code now, to determine exactly how to do so
without causing side effects)
Has anybody ever seen a case where a massive change to the file being
triggered, causing the above WRITE statement to throw hundreds (perhaps
thousands) of CPF5026s, and eventually the indicator would stop catching
them, and the program would simply blow up?
(Or now that I think about it, could it just have blown up because the
user's joblog got filled up with an insane number of CPF5026 errors?)
--
JHHL
As an Amazon Associate we earn from qualifying purchases.
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
