×
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.
ADDPFTRG requires an exclusive lock on the *FILE temporarily, while it adds the trigger. You would need to check for locks when the ADDPFTRG runs.
Why run ADDPFTRG in a nightly scheduled job? Just add the trigger once, then, when needed, just disable or enable it via:
CHGPFTRG ... STATE(*ENABLED or *DISABLED)
HTH,
Mark S. Waterbury
On Tuesday, April 2, 2019, 10:00:11 AM EDT, Doug Englander <denglander@xxxxxxxxxxxxxxxxxxxxxxxx> wrote:
We have a situation where a trigger (via ADDPFTRG) is failing with CPF32C6, reason code 8. When we check WRKOBJLCK for the table, there is nothing listed for the file so it appears there is no lock. This seems to be the only message that ADDPFTRG throws. Does anyone know what caused this?
It looks like the trigger name is the issue, but this had been working in the past. This ADDPFTRG command is part of a nightly job that runs in Batch.
Thank you,
Doug
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
