RE: RPGLE I/O opcodes with commit/rollback

"It's strange to me that you knew about it in SQL, but not in native I/O."

I learned about it in SQL about 10 - 15 years ago from non-iSeries work I
did so I looked and found it existed in iSeries SQL. I never thought to
look for a way to do it natively and since I never saw it...

-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Scott
Klement
Sent: Wednesday, November 18, 2015 3:33 PM
To: RPG programming on the IBM i (AS/400 and iSeries)
Subject: Re: RPGLE I/O opcodes with commit/rollback

Don't forget to put the COMMIT keyword on your F-spec! I've only noticed
mention of the opcodes for commit/rollback, not sure if someone mentioned
the F-spec keyword?

Anyway, John, if you started RPG in 1992, then these have probably been
there the entire time you've coded RPG. (I don't remember exactly when they
were added, but I know they were there in RPG III, so it's been there since
at least the early 90's)

In my experience, it used to be extremely rare that commitment control was
used at all in IBM i shops. (Not just with native I/O but with SQL as well.)
Usage has increased in recent years, but it's still not very common, which
is a shame.

It's strange to me that you knew about it in SQL, but not in native I/O.
My experience has been that any shop using commitment control uses it in
both places.


On 11/18/2015 2:21 PM, John R. Smith, Jr. wrote:

Wow, I have been doing RPG since 1992 and have been an RPG consultant

since

1999 so lots of different companies / coding styles in the past 20+ years
and have never seen those two opcodes. I guess I owe someone an apology

and

lunch for losing the bet.

Just out of curiosity, was the use of this very rare or have I just not
stumbled into the right companies that use it.