Re: Trigger state: *DISABLED -- what the heck is that, and from what OS revision, and what do I do about it?

Triggers are always a lot fun no matter what even with a mediator. We are
doing major development work using triggers and so many issues have come up.


Just figuring out how to make commitment control to work under triggers and
JDBC took a week and a half.

Still something won't work and I will go into a screen look and realize the
trigger is turned off or that the mediator wasn't put on the file. Going to
get interesting when we get to production.


On Fri, Oct 16, 2009 at 12:51 PM, James H. H. Lampert <
jamesl@xxxxxxxxxxxxxxxxx> wrote:

Bob P. Roche wrote:

At least you don't have to remember all the steps to re apply your
trigger. Is it before or after, update, add, delete or please not a read
trigger. It's useful that way just re-enable

True, but that doesn't help much if you've got about a dozen or more
files involved. Easier to just write a CL program.

More to the point, if the triggers are merely "sleeping," then only a
DSPFD will tell you why they're not getting invoked (and I can't tell
you what gave me the impulse to try a DSPFD, either, beyond grasping at
straws). Nothing shows up in a PRTTRGPGM to indicate that they're
disabled. Sounds like a very easy way to send your IT staff on a one-way
trip to the rubber room.

--
JHHL
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.