Yes, the trigger program will slow down the processing- it is in the processing stream.
When the batch program requests the event of the trigger from the database and the trigger is before,
the database calls the trigger program and waits until it’s done before updating the record.
When the batch program requests the event of the trigger from the database and the trigger is after,
the database updates the file and then calls the trigger program and waits until it’s done before returning to the batch program.
I’m sure you’re right about *INLR and the overhead, if you are using this program a lot you will not want to set this on but remember this program will be locking the files and if you’re not careful records!
Phil
Discuss This Question: 7  Replies