Re: CPF5026 in ILE RPG trigger program eventually not getting caught?

[Buck <kc2hiz@xxxxxxxxx>]

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