RE: Trigger programme without a trigger.

[rob@xxxxxxxxx]

I think you also left off that a "traditional" RPG programmer often makes 
"assumptions" about WRITE or UPDATE errors and often doesn't check 
%status.  Oh, got an error on a WRITE?  Let's assume it was a duplicate 
key error.
Now, let's upgrade this programmer a little.  They now check %status. 
Trigger error?  How do I determine what the error was?  I have to check 
the job log, or program message queue, to see what exception message that 
the trigger program threw?  I'm too lazy for that and I've never had to do 
that on a S/34 therefore trigger programs are evil.  They require me to 
change!

Rob Berendt