Re: SQL problem

You did a CHGCMDDFT in V5R3.  The defaults did not change - they just went 
back.

Instead use the SET OPTION, like
C/EXEC SQL 
C+ Set Option 
C+     Naming    = *Sys, 
C+     Commit    = *None, 
C+     UsrPrf    = *User, 
C+     DynUsrPrf = *User, 
C+     Datfmt    = *iso, 
C+     CloSqlCsr = *EndMod
C/END-EXEC 

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





"Muralidhar Narayana" <Muralidhar_Narayana@xxxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
10/28/2004 12:46 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
<midrange-l@xxxxxxxxxxxx>
cc

Fax to

Subject
SQL problem






There is a problem in my development system which was recently upgraded to 
V5R3 when I take option 15 beside a SQLRPGLE module

 

Commitment control . . . . . . . COMMIT         *CHG 

Close SQL cursor . . . . . . . . CLOSQLCSR      *ENDACTGRP

 

This causes errors when running programs as sql statment failure because 
either 

cursors are remained open from previous reads or commitment control is set 
on that file.

 

 The values should be actually (they used to be in V5R2)

 

Commitment control  . . . . . . . . . . . . . . . . . :   *NONE

Close SQL cursor  . . . . . . . . . . . . . . . . . . :   *ENDMOD

I came to know that this is because of the upgrade to V5R3. If we change 
the Command Defaults every time we perform an upgrade these commands will 
be changed to what the new release is set to. 

If we  change those defaults for CRTSQLRPG and CRTSQLRPGI, is this going 
to affect me ?

our production is V5R2, development is V5R3, when we move these to 
production am I going to have problem?

any other commands like these which have got changed due upgradation just 
like what I mentioned in above example?

Thanks for your help....

 

 


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.