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

[rob@xxxxxxxxx]

One suggestion, if it is that much of a bear to get a lock, add an 
extremely basic program as a trigger, and have it call your other 
programs.  That way the lock won't be a problem when you have to 
add/modify programs.  And, until you get this working, I'd leave your 
*inlr on upon exit until you get it thoroughly stress tested.  That way 
the current version of the program gets loaded.

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





"James H H Lampert" <jamesl@xxxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
12/01/2004 08:18 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
<midrange-l@xxxxxxxxxxxx>
cc

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


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.