RE: Compiling Trigger Program

We use one trigger program for all of our files. It's pretty basic and
hasn't had changes in a while, but I don't remember having any issues
with swapping it out in the middle of the day. If you mean locks that
would show in WRKOBJLCK - there are none on the program as I sit and
small F5, and I can see from our interface engine that the trigger is
steadily getting called and files going out. We do turn on *INLR




Kevin Bucknum
Senior Programmer Analyst
MEDDATA/MEDTRON
Tel: 985-893-2550

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
dlclark@xxxxxxxxxxxxxxxx
Sent: Tuesday, April 12, 2016 1:58 PM
To: Midrange Systems Technical Discussion
Subject: Re: Compiling Trigger Program

"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx> wrote on 04/12/2016
02:52:42 PM:

Well, you seem to be the only one. If you've found a secret to doing

it,

please share it with the rest of us.

Perhaps it just always happens to be that all such locks are
gone
by the time I am looking to replace it. Naturally, I have never tried
replacing it in the middle of the work day. ;-)


Sincerely,

Dave Clark
int.ext: 91078
direct: (937) 531-6378
home: (937) 751-3300

Winsupply Group Services
3110 Kettering Boulevard
Dayton, Ohio 45439 USA
(937) 294-5331



************************************************************************
*********************
This email message and any attachments is for use only by the named
addressee(s) and may contain confidential, privileged and/or proprietary

information. If you have received this message in error, please
immediately notify the sender and delete and destroy the message and all

copies. All unauthorized direct or indirect use or disclosure of this
message is strictly prohibited. No right to confidentiality or privilege

is waived or lost by any error in transmission.
************************************************************************
*********************