Re: Trigger programme without a trigger.

[rob@xxxxxxxxx]

<snip>
But here's my question: if this were a trigger type of system, how did 
the error get there in the first place? 
</snip>
The point is, it wasn't a trigger type of system.  It was an I/O module 
type of system.  How did the bad data get in on an I/O module type of 
system?  Heck, maybe "Joe" got a month long vacation to whack animals in 
Africa, or got called up to duty in Iraq.  And during that time a merger 
happened and the person brought in bypassed the I/O module.  Again, no 
maliciousness on their part.  Just not a comprehension of why *ALLOBJ was 
needed, (which may have happened for numerous other reasons in their 
career and assumption was made it was because of those reasons).  While 
running a RMVPFCST or RMVPFTRG are a little more obvious they are there 
for data integrity reasons.

So, as you said, maybe a belt and suspenders approach even in an I/O 
module type of system is not a bad thing.

Rob Berendt