×
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.
.
The error msgCPF502B can *not* record the previous message in the
[few] cases whereby the trigger program can not actually be invoked. I
will not provide the sordid details, but suffice it to say that it is a
restriction that is unlikely to be lifted, without significant change to
the the DB I/O programs that can invoke a trigger program.
Some [, the most probable] examples that might prevent the trigger
program from activating due to a failed CALL from the DB I/O program
<see WRKMSGD for each, to learn the details of the condition>: MCH0801
MCH0802 MCH3401 [this could be for the program itself, or a dynamic
bound program] MCH1001
The condition MCH0802 describes the condition for the given example
CLP, since as coded, there were no parameters defined yet it would have
been called with two parameters being passed.
Regards, Chuck
-- All comments provided "as is" with no warranties of any kind whatsoever.
Don Cavaiani wrote:
This said to look at previous messages, but there were none??
Message . . . . : Error occurred in trigger program.
Cause . . . . . : The trigger program which was called as the result
of a database insert, update, delete, or read operation failed. See the
previous messages in the job log to determine the error.
<<SNIP>>
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
