I didn't follow the complete thread, but begin and end and some other
postings as well.
just some thaughts:
- the design with changing libl has it's weakness, if a cursor stays open in
between, or a prepare stays active, it won't work as expected.
- same might be true for the embedded SQL runtime (I've bugs like this in
the past - a hanging lazy close operation...)
The ACTGRP(*NEW) combined with commitscope ACTGRP, has the effect, that
every run of the programm is using it's own connection, starting without
open SQL ressources.
The same effect should happen with:
- disconnect the local connection (disconnect only works on a commit
boundary, better is release followed by rollback)
- change your libl
- reset your local connection
One other hint: The ACTGRP *NEW has one illness with commit controll - it's
ending the ACTGRP with a committ, rollback would be better, but for this you
would have to register an exitprogramm (CEE4RAGE could do this, you'll find
an example in nearly all sources of AppServer4RPG)
Dieter
As an Amazon Associate we earn from qualifying purchases.
This thread ...
Re: Possible SQL Activation Group Issues, (continued)
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
