Comments on: Execute trigger only on update of selected fields

By: tomliotta

tomliotta — Tue, 04 Jan 2011 01:00:54 +0000

I open the output file

Ideally, you only open the output file the first time a change is discovered. Then you leave it open when you return from the trigger so you don’t open/close the file for every detected change.

Tom

By: r.otto

r.otto — Mon, 03 Jan 2011 10:41:36 +0000

Thank for your help.
I created a COBOL program that compares old and new fields on an update. If any of the fields that need to go to the Oracle system has changed I open the output file and write a record. If not I just end the program.

By: tomliotta

tomliotta — Mon, 27 Dec 2010 23:16:28 +0000

You can compare the specific fields from the before and after images in the trigger program…

That is indeed true. But it might be that that’s exactly what should be avoided.

…and saves the Oracle system from getting 1.5 million changes.

Then again, maybe that’s the critical piece of info — “Oracle”. Maybe the ’6 hours’ is mostly due to some element of network traffic over to the Oracle system. If the COBOL trigger program simply returns when the only changes are to the ‘workfields’, a lot of delay might be eliminated.

Tom

By: splat

splat — Mon, 27 Dec 2010 17:39:12 +0000

You can compare the specific fields from the before and after images in the trigger program, exiting if there are no differences between them. The trigger program is still run, but updates will only occur when your specified fields show a change. I did something similar a few years ago. One thing to consider is when or if you need to open any files – if you’re not going to update anything, there’s not benefit in having that overhead.

By: tomliotta

tomliotta — Thu, 23 Dec 2010 23:07:27 +0000

And it still takes 6 hours even if the trigger is disabled? You can use the CHGPFTRG command to disable and re-enable a trigger.

Tom

By: r.otto

r.otto — Thu, 23 Dec 2010 14:57:37 +0000

We are not programming in SQL ourselves. This was originated by someone who was hired by another department to design a system for them and he needed all changes to a membership file to keep his data up-to-date. The file has 1.5 million records and contains some workfields. Through SQL he generated the triggers and the trigger programs. Now if we update those workfields it takes about 6 hours to complete and he does not need those (and some other) fields. Without the trigger it takes some 20 minutes and saves the Oracle system from getting 1.5 million changes.
What we did is write a trigger program in COBOL but we would like it to be executed only when selected fields are updated or when a record is inserted.

By: tomliotta

tomliotta — Thu, 23 Dec 2010 00:44:14 +0000

Is it required that the trigger actually be removed? Why not just disable it? Also, if it must be removed, why not store the trigger definition somewhere, e.g., in a source member, and simply RUNSQLSTM to recreate and reapply it?

Tom