Re: Brainstorming

[CRPence <crp@xxxxxxxxxxxxxxxxxxxx>]

.
  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>>