All the more reason to use the SET OPTION. Many have gotten used to RPG compile options on the H spec. How tricky can it be to get used to SQL compile options on the SET OPTION? Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com Vernon Hamberg <vhamberg@xxxxxxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 10/28/2004 01:56 PM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> cc Fax to Subject Re: SQL problem Unless you are going to execute the commands on the production system, there should be no problem. Programs with embedded SQL do not need to be recompiled on the target system, only restored, if created at the appropriate release. So you also need to change the command on the V5R3 so that they use TGTRLS(*PRV) or TGTRLS(V5R2M0). This way you know whether anything you compile will not run at that release, even if you do recompile on the production system. HTH Vern At 12:46 PM 10/28/2004, you wrote: >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. -- 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.
This mailing list archive is Copyright 1997-2015 by MIDRANGE dot 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 here. If you have questions about this, please contact