Re: Disabling triggers, and can somebody here explain the "trigger library" parameter on ADDPFTRG, RMVPFTRG, and CHGPFTRG?

Apparently you can have multiple triggers on one particular table.
Perhaps at some time someone envisioned doing:
- TRIGLIB1 to update data in DIV1LIB
and so on.
Then, if DIV1LIB was restricted (month end or some such thing) then they
could disable the triggers updating that library.

Changing a trigger to disabled "may" have been primarily for the H/A
vendors (like Mimix). Disable a trigger on the 'backup' machine so that
it doesn't fire when updates are replicated from the primary. I know they
do disable triggers. Normally when they are doing this it's during a
switch so there should be no locks on the tables.

But, in your defense there is nothing listed in the "Restrictions" that
you need a lock on the table. And the only escape message documented is
the generic
CPF32C6 Trigger operation not successful.
leaving it up to you to look for informational and diagnostic messages to
determine why it really aborted.

The advantage of CHGPFTRG vs RMV/ADD PFTRG is that they're still tied to
the table and thus automated tools (like HA software) don't have to keep
track of triggers to add back in.

Rob Berendt