Re: Does trying to add a trigger lock the file?

Agreed!  Heck, you can't even change the trigger program unless you remove it
from the files that trigger it.

The reason I brought this up is that some other processes using a related
logical is crying "unable to allocate object."  But I can't imagine the file
being locked by my program because my code would simply add the trigger and
exit if it ever exclusively locked the file.  Without the lock, it just loops
and tries again.

I may just rewrite it with the ALCOBJ command... intuitively, it seems like it
would abuse the system less, now that I think about it!

-William


> date: Wed, 1 Dec 2004 17:18:49 -0800 (PST)
> from: "James H H Lampert" <jamesl@xxxxxxxxxxx>
> subject: Re: Does trying to add a trigger lock the file?
> 
> > Hi All,
> >
> > I want to add a database trigger to a file. . . .  Adding a trigger
> > requires an *EXCL lock.  I'd like to retry adding the trigger until I do
> > it.
> . . .
> > Would this code cause other processes to time out due to an object lock
> > on the OECSSL file?
> 
> Probably not, but there's only one way to find out.
> 
> And I can say from direct experience that adding, removing, or DOING
> ANYTHING ELSE YOU CAN THINK OF to the trigger(s) on a file requires an
> *EXCL lock.
> 
> --
> JHHL
>