×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I just yesterday removed a block of code from a trigger program, that
was apparently causing anomalous data to go into a file. When I left
last night, the file had been cleansed of the anomalous data.
This morning, there's more anomalous data in the file. And unless some
idiot is manually polluting the affected records, and manually setting
the last-changed user field on those records to what appears to be a
maintenance job's user profile, the trigger is what's doing it.
If I do a DSPOBJD on the trigger program, in library *ALL, I find three
copies of it.
Is there a way to determine which library a triggered file is getting
the trigger program from?
In a PRTTRGPGM of the library in question, I get (only the names have
been changed to protect the innocent):
. . . ------------Trigger . . .
. . . Library Program . . .
. . .
. . . FOOBAR FROBOZZ . . .
. . .
where FOOBAR is the same as the file's library, but does NOT contain one
of the three copies of FROBOZZ on the system.
Unfortunately, I can't simply do a RMVPFTRG followed by an ADDPFTRG,
because there are users with locks on the file being triggered.
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.
midrange.com
