Re: Trigger programme without a trigger.

No, you missed it Joe. That's not quite what he said. Let's say that the
data error was in an I/O module only type of system. And "Joe" is on
vacation or some such thing. CFO wants this problem fixed now. He calls
in the consultant, coworker or whatever. Grants them *ALLOBJ because
business rules require that this task gets resolved now. Since the I/O
module only type of system may not be glaringly apparent to this other
worker and doesn't require them to actually run a RMVPFTRG, RMVPFCST or
some such thing to forego the business rules enforced solely by the I/O
module then the person assigned to this can accidentally inject bad data
that was enforced solely by the I/O module.

Rob Berendt