Re: Trigger Problem

["Mike Silvers" <msilvers@xxxxxxxxxxx>]

I was not really clear on that issue.  We do not open the window in this
program.  If specific criteria are met, we pass control to another program
and return from that program with *LR being on...so the display file is not
an issue.

Mike


----- Original Message -----
From: "Jim Langston" <jimlangston@conexfreight.com>
To: <RPG400-L@midrange.com>
Sent: Friday, May 25, 2001 1:58 PM
Subject: Re: Trigger Problem


> Ahhh, okay.
>
> Question though, is it "legal" to return to an RPG program that uses a
display
> file without setting on LR?  What happens to the display screen when the
program
> exits?  Obviously the display file is not being closed.  I'm not sure what
would
> happen when you tried to return to the program.
>
> Perhaps something there is causing the locking issues?
>
> Regards,
>
> Jim Langston
>
> Me transmitte sursum, Caledoni!
>
> Mike Silvers wrote:
> >
> > Yea..the program has a lock on it.  The complicated part here is the
program
> > is interactive and responds with a screen to the user if the record does
not
> > meet specific criteria.  For this reason, I have to use a data area and
the
> > program must be called.  By calling this program, it puts the rogram in
the
> > job stream of the interactive user and the window can be displayed.
> >
> > Mike
> >
> > ----- Original Message -----
> > From: "Jim Langston" <jimlangston@conexfreight.com>
> > To: <RPG400-L@midrange.com>
> > Sent: Friday, May 25, 2001 12:11 PM
> > Subject: Re: Trigger Problem
> >
> > > 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
> +---

+---
| 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
+---