Re: Triggers prevent requested operation

On 24/04/2007, at 12:54 PM, Captain Jerry wrote:

I have a Trigger on a file which fires on a Delete Record. All's well,
unless I do a Clear Physical File Member (CLRPFM) ~ The Trigger doesn't like
that.

It's not the TRIGGER that doesn't like it--it's the SYSTEM. The presumption is that IF you added a *DELETE trigger then you probably want it to fire for every record deletion. Because CLRPFM does not DELETE records but rather truncates the data space there is no physical delete operation thus the trigger won't fire. If the trigger isn't fired how can the trigger program perform whatever action you desire when a delete occurs. Nett result is that some operations are not allowed on a file that has a trigger.

#3 is my problem. How can I get around this? There must be a trick, but I
can't find one.

You can't CLEAR a file with a *DELETE trigger so do what the message help text tells you and remove the trigger, clear the file, and add the trigger back again. NOTE: I am not recommending this practice--simply telling you how you can accomplish it.


Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists

http://www.flybynight.com.au/
Phone: +61 3 9899 0985 Mobile: +61 0411 091 400 /"\
Fax: +61 3 9899 0985 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------