|
At my shop, somebody wrote a trigger program and then attached it to the
most-used file in the system.
That file is also used by the most-used program. It runs standalone and
also is called by maybe up to hundreds of other programs. Quite a "legacy".
I don't know what activation group attribute he used but it created
havoc for a few minutes. (I suspect *CALLER). Till somebody hit an
emergency virtual) STOP button.
I did a trigger program shortly afterward and they teamed me up with two
guys to look over my code and monitor the action.
I did the trigger-pair thing from a recent article. One "driver" that
does nothing but pass the parms through to the "workhorse" program. That
way you can replace the "workhorse" without disturbing the file or its
attached trigger file directly.
BUT before I did the trigger program, I ran X-Analysis to get ALL the
programs that did ANY updates/deletes/inserts to the file, and
considered their own activation groups. In this case (and most) you have
to compile the trigger program with *CALLER, or get your performance
killed and mutilated.
I also "walked the upstack" from those programs to check the activation
group. It looked like the programs had been called without regard for
consideration for the ACTGRP issues. After that havoc, though, they're
paying more attention. Some of those "upstack" programs I had to convert
from OPM RPG3 code. Glad to do it!
--Alan Cassidy
--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.