Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
Reinhard Habichtsberg asked how to use SET LOCK MODE TO WAIT in ISQL ACE reports (saceprep/sacego). Jonathan Stowe said an ACE report can only hold a select statement. Art Kagel suggested linking an ESQL function into sacego. Reinhard linked one and called it in FIRST PAGE HEADER, but it ran after the selects, so it had no effect. Unresolved.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
Hi,
in SQL statements, esqlc programs, even in odbc connections
I can use "set lock mode to wait ...". Thereby the program does
not stop if a table is locked temporary.
I don´t know how to put this in ACE reports.
Any idea?
TIA,
Reinhard
↪ replying to Reinhard Habichtsberg
Jonathan Stowe — — source: Informix-list mailing list archive (1991-1998)
Reinhard Habichtsberg <Reinhard.Habichtsberg@unilux.de> wrote:
> Hi,
>
> in SQL statements, esqlc programs, even in odbc connections
> I can use "set lock mode to wait ...". Thereby the program does
> not stop if a table is locked temporary.
>
> I don´t know how to put this in ACE reports.
>
You cant do it in an ACE report - you can only have select statement.
/J\\
--
"Do you want to go to court today?" - BBC News Website
Jonathan Stowe <gellyfish@gellyfish.com wrote:
> Reinhard Habichtsberg <Reinhard.Habichtsberg@unilux.de> wrote:
> > Hi,
> >
> > in SQL statements, esqlc programs, even in odbc connections
> > I can use "set lock mode to wait ...". Thereby the program does
> > not stop if a table is locked temporary.
> >
> > I don´t know how to put this in ACE reports.
> >
>
> You cant do it in an ACE report - you can only have select statement.
>
That´s poor. Not the answer :-) but the fact :-( .
Isn´t there any workaround?
Reinhard
↪ replying to Reinhard Habichtsberg
Art S. Kagel — — source: Informix-list mailing list archive (1991-1998)
There might be a way to link an ESQL function into sacego which you can
call at the start of the report that will execute the SET LOCK MODE TO
WAIT... for you. I have not used ACE in a long time. Jonathan? Any
ideas in this vein?
Art S. Kagel
Reinhard Habichtsberg wrote:
>
> Jonathan Stowe <gellyfish@gellyfish.com wrote:
> > Reinhard Habichtsberg <Reinhard.Habichtsberg@unilux.de> wrote:
> > > Hi,
> > >
> > > in SQL statements, esqlc programs, even in odbc connections
> > > I can use "set lock mode to wait ...". Thereby the program does
> > > not stop if a table is locked temporary.
> > >
> > > I don´t know how to put this in ACE reports.
> > >
> >
> > You cant do it in an ACE report - you can only have select statement.
> >
> That´s poor. Not the answer :-) but the fact :-( .
> Isn´t there any workaround?
>
> Reinhard
Hi,
Jonathan Leffler <jleffler@earthlink.net> wrote
> The various workarounds invoking a stored procedure would probably
work.
> Otherwise, you can consider using SACEISOL="dirty read". Not the
same thing
> as setting the lock mode, of course, but it does prevent the
report from
> waiting on locks.
It works, thank you!
>
> "Art S. Kagel" wrote:
>
> > There might be a way to link an ESQL function into sacego which
you can
> > call at the start of the report that will execute the SET LOCK
MODE TO
> > WAIT... for you. I have not used ACE in a long time. Jonathan?
Any
> > ideas in this vein?
> >
> > Art S. Kagel
> >
One can link ESQL or C - functions to ACE. Unfortunately the "set
lock mode" -
statement which I call in FIRST PAGE HEADER section is IMHO executed
_after_ the select statements. so there is no effect.
Regards,
Reinhard
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.