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

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