Re: RPG and Commitment Control

[Charles Wilt <charles.wilt@xxxxxxxxx>]

STRCMTCTL along with COMMIT f-spec keyword is the _ONLY_ way to get
commitment control with RPG record access.

You're only other choice would be to replace RPG I/O op-codes with SQL.

Charles

On Mon, Nov 14, 2016 at 7:25 AM, Paul Bailey <PabloMotte+Midrange@xxxxxxxxx>
wrote:

> Hi,
>
> We are on v7r1 and I have been asked to make all the file adds/updates in
> one call of a particular program a single database transaction. The program
> is mostly RPGIII, with some RPGIV (with /FREE) thrown in to muddy the
> waters.
>
> I've searched and found an article by Paul Tuohy and another by Thomas
> Snyder where they talk about using the STRCMTCTL/ENDCMTCTL CL commands and
> the COMMIT f-spec keywords (with USROPN) to enable the RPG program to use
> COMMIT and ROLBK. This seems like a tonne of work!
>
> How would you try to convert this monolithic, multi-file updating, 25
> year-old program with the smallest amount of actual change to the code? Is
> the STRCMTCTL (et al.) setup still best practice for commitment control?
>
>
> -Paul.
> --
> 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.
>
> Please contact support@xxxxxxxxxxxx for any subscription related
> questions.