Hi,
The default values for these parameters did not change.
If the default values in your former release where *NONE and *ENDMOD,
someone must have change it by using the command CHGCMDDFT.
To avoid problems with further releases or compilations, I'd add a SET
OPTION statement in each of your sources with embedded SQL to set the
compile options you want.
C/Exec SQL
C+ Set Option Commit = *NONE, CloSQLCsr = *ENDMOD
C/End-Exec
In either way CLOSQLCSR *ENDMOD is not the best solution, because all
SQL-ODPs (Open Data Path) get closed, that means the ODPs are not
reuseables. Each time the program or procedure will be executed a full
optimization (which is the most time consuming process while executing a SQL
statement) must be performed. When using *ENDACTGRP instead, an ODP can stay
opened, that means the next time the program or procedure will be executed
only the data in the OPD must be actualized, i.e. no full optimization is
necessary.
Mit freundlichen Grüßen / Best regards
Birgitta Hauser
"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"
-----Ursprüngliche Nachricht-----
Von: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] Im
Auftrag von donna lester
Gesendet: Tuesday, June 17, 2008 02:43
An: RPG programming on the AS400 / iSeries
Betreff: Re: CRTSQLRPGI
Thanks. Wwhat were the default values on V5R3? (*NONE & *ENDMOD) or (*CHG
& *ENDACTGRP)?
Simon Coulter <shc@xxxxxxxxxxxxxxxxx> wrote:
On 17/06/2008, at 8:49 AM, donna lester wrote:
A 15 and F4 next to an SQLRPGLE module shows default values as below:
Commitment control . . . . . . . COMMIT *CHG
Close SQL cursor . . . . . . . . CLOSQLCSR *ENDACTGRP
We are on V5R4.
The values should have been *NONE & *ENDMOD (I guess on V5R3),
would this cause any issues on new SQL modules if we compile
with default values of *CHG & *ENDACTGRP?
What exactly is the point of your question?
Depends on what you consider an "issue". Certainly the behaviour will
be different with different values. With the standard default values
you will need to have journalling active and you will need to issue
COMMIT statements else the system will roll-back any changes. Also
cursors won't be fully closed until the activation group ends.
Whether that is an issue depends on how you compiler your programs.
Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists
http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------
midrange.com
