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

Did you check the job log to see if the abend is as you suspected, the message queue filling up and not extending? That's what I think would have happened as well.

-Kurt

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of James H. H. Lampert
Sent: Friday, March 26, 2010 1:06 PM
To: RPG programming on the IBM i / System i
Subject: CPF5026 in ILE RPG trigger program eventually not getting caught?

Has anybody else seen anything like this:

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