× 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 don't know if the Redbook covered the idea of a "traffic cop" or "Mediator" that lets the trigger-functions run or temporarily stops them.
(For instance, best is if they feed a data-queue in a process that can be temporarily turned off.)

There is a good reason to stop the triggers at certain times.
When you are refreshing data from Production to your Test box, you will have mis-matched transactions,
so you do not want those giving you a "storm of error messages" and roll-back actions.

There is a great post at http://archive.midrange.com/midrange-l/200506/msg01053.html
that talks about the difference between a "Trigger Mediator" ( Good) and "Disabliing Triggers" (Bad )

- John Voris


. . . struggling with exception handling.
I'm following Trigger coding examples from the following redbook:
Examples show using the QMHSNDPM API to signal *ESCAPE type messages. That
was causing a spooled program DUMP with every data validation exception - I
finally figured out how to prevent that. . .

Nathan


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.