RE: Change commitment control after compilation

yes it is the same, I only prefer to have it in the source so I don't have to remember to change compile parameters and do prompt ;-)

Yes, Henrik. In fact my compiles set up as part of the header in my source with the command and parameters and all, enclosed with markers, using *%%% as left parenthesis and %%%* as a right parenthesis, run a generic PDM option or command to extract the embedded commands, put them in source in QTEMP with substitution, compile that and run it. Works great. That way, no messing around with compile command parameters. It uses PDM-like substitution, as in &&L for source library and &&O for object library, etc.

We're a tiny developer shop of 2 and can't justify the expense of third party change management.

I'd be glad to share the code, I brought it here with me. There was somebody else on this list (or the RPG list) that does the same.




-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Henrik Rützou
Sent: Wednesday, December 18, 2013 7:28 AM
To: RPG programming on the IBM i (AS/400 and iSeries)
Subject: Re: Change commitment control after compilation

Hi Peter

yes it is the same, I only preffer to have it in the source so I don't have to remember to change compile parameters and do prompt ;-)

The change thing is that I only have experienced this on some V6R1 systems - are you sure the commitment controle isn't active?

You can display it with DSPJOB opt 16


On Wed, Dec 18, 2013 at 1:12 PM, Colpaert, Peter <Peter.Colpaert@xxxxxxxxxxx

wrote:

Hi Henrik,

I solved it by recompiling our SQLRPGLE programs with parameter
COMMIT(*NONE). Which amounts to the same result, I think.

Luckily we discover this now, when only some 15 programs are impacted.

Met vriendelijke groeten / Best regards,

Peter Colpaert
Software Engineer - PLM Development Team IT Operations Cluster
Benelux, Philips IT

Philips Consumer Luminaires
Industrieterrein Satenrozen 11, 2550 Kontich, Belgium
Tel: (+32) 3/459 13 17
Email: Peter.Colpaert@xxxxxxxxxxx

Working from home on Wednesdays


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Henrik Rützou
Sent: woensdag 18 december 2013 13:06
To: RPG programming on the IBM i (AS/400 and iSeries)
Subject: Re: Change commitment control after compilation

Hi Peter,

I'm sitting with the same problem on only one V6R1 system. Suddenly
some SQLRPGLE failed.

The work around was to add this line to the SQLRPGLE programs and
recompile.

exec sql set option commit=*NONE;


________________________________
The information contained in this message may be confidential and
legally protected under applicable law. The message is intended solely
for the addressee(s). If you are not the intended recipient, you are
hereby notified that any use, forwarding, dissemination, or
reproduction of this message is strictly prohibited and may be
unlawful. If you are not the intended recipient, please contact the
sender by return e-mail and destroy all copies of the original message.
--
This is the RPG programming on the IBM i (AS/400 and iSeries)
(RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/rpg400-l.

--
Regards,
Henrik Rützou

http://powerEXT.com <http://powerext.com/>
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l.


--------------------------------------------------------------------------------
Confidentiality Notice: This email may contain confidential information or information covered under the Privacy Act, 5 USC 552(a), and/or the Health Insurance Portability and Accountability Act (PL 104-191) and its various implementing regulations and must be protected in accordance with those provisions. It contains information that is legally privileged, confidential or otherwise protected from use or disclosure. This e-mail message, including any attachments, is for the sole use of the intended recipient(s). Any unauthorized review, use, disclosure or distribution is prohibited. You, the recipient, are obligated to maintain it in a safe, secure and confidential manner. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Thank you.
--------------------------------------------------------------------------------