Re: Trigger Problem

[Jim Langston <jimlangston@xxxxxxxxxxxxxxxx>]

The program itself has a lock on it?

Strange, I don't think I've seen that happen before.  Lots of people
are calling the same programs on our system with no locking issues of
the program objects themselves.

Of course it is possible there is some mechanism going on here that we
have just never used, so never ran into the locking issue.

Are you sure the lock is on the program and not a file that the program
is opening?

Regards,

Jim Langston

Me transmitte sursum, Caledoni!

Buck Calabro wrote:
> 
> Mike Silvers wrote:
> 
> >If we turn off the data area so the program that does
> >the work is not called anymore, the lock still exists.
> >This is the problem.  Does anyone have any
> >suggestions on how to resolve the locking issue
> >(other than having the users sign off -- that is
> >not an option)?
> 
> Add an option so that the "work" program can set LR on and free itself from
> storage.  Either have a third value in the data area, a separate data area,
> etc.  The point is to have a signal that the working program can read to
> terminate itself.
> 
> Buck Calabro
> Commsoft; Albany, NY
> "Nothing is so firmly believed as
>  that which we least know" -- Michel Montaigne
> Visit the Midrange archives at http://www.midrange.com
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---