Re: Trigger Anomaly

We recently upgraded to 7.3 TR2, so I wonder if it's a byproduct of that upgrade.

The situation comes from backing up a library on one machine and restoring on another and which is something we'll be doing regularly, so I'll just have to contact IBM and see where I go from here.  I'll get a chance to learn about opening incidents. :)

Hi, Joe,

What version/release of OS/400 or IBM i is this happening on?

Also, unless you  IPL frequently,  I would just go ahead and open a  PMR, as IBM may have seen t his before,  and  may already have PTFs available?    It is easy nowadays to open a Support Incident via the  web...

All the best,

Mark S. Waterbury

> On 10/24/2017 9:14 PM, Joe Pluta wrote:

Has anyone seen a case like the following?

I have a physical file.  If I look in iSeries Navigator (yes, old version) it says that the file has two triggers.  I look in SYSTRIGGER, and it also indicates that the file has two triggers. Both are for the same program for different events.

However, if I try to remove the trigger, I get CPF32C6 in response to CPD32E7.  The second level message text for CPD32E7 says the remove trigger operation failed for reason 14: the file has no triggers.  I do DSPFD and lo and behold, DSPFD says I have no triggers.

I add a trigger, SYSTRIGGER say three triggers, DSPFD says one trigger.  I RMVPFTRG TRG(*ALL) and it completes, but only removes the newly added trigger; the original two remain.  I try another RMVPFTRG and get the original error.

It seems like there is a lost connection somewhere.   However, RCLDBXREF OPTION(*CHECK) reports successfully verified.

I'm probably going to wait until next IPL, check again and then go to IBM, but just wondering if anybody noticed something I missed.

P. S. The program name on this has a "." in it, as in MYFILE.TRG in the same library as MYFILE.  But I have others with that same nomenclature and I was able to remove them successfully.