Midrange News for the IBM i Community


Posted by: George Fuste
IBM i developer
Jacksonville, FL
Ending Commitment control
has no ratings.
Published: 30 Aug 2012
Revised: 23 Jan 2013 - 1783 days ago
Last viewed on: 11 Dec 2017 (2980 views) 

Using IBM i? Need to create Excel, CSV, HTML, JSON, PDF, SPOOL reports? Learn more about the fastest and least expensive tool for the job: SQL iQuery.

Ending Commitment control Published by: George Fuste on 30 Aug 2012 view comments(3)

I'm curious about ending commitment control.  A co-worker tells me you must do an ENDCMTCTL after a COMMIT to release any locks from the commitment control.

I understand that once a COMMIT is issued, the records are posted to the database and any READ/UPDATE locks are released.  Am I correct?

Thanks

George 

Return to midrangenews.com home page.
Sort Ascend | Descend

COMMENTS

(Sign in to Post a Comment)
Posted by: DaleB
Premium member *
Reading, PA
Comment on: Ending Commitment control
Posted: 5 years 3 months 12 days 12 hours 29 minutes ago

You are correct. ENDCMTCTL stops the commitment control environment. If nothing has changed since the last COMMIT or ROLLBACK (i.e., last boundary), there's nothing to release. If there are pending, uncommitted changes, then an ENDCMTCTL will send a message to an interactive job, or will do an implied ROLLBACK in a batch job.

Posted by: DaleB
Premium member *
Reading, PA
Comment on: Ending Commitment control
Posted: 5 years 3 months 12 days 12 hours 28 minutes ago

I should add that you should do an ENDCMTCTL. It just doesn't have anything to do with releasing locks after a COMMIT.

Posted by: GFuste
Premium member *
Jacksonville, FL
Comment on: Ending Commitment control
Posted: 5 years 3 months 8 days 13 hours 52 minutes ago

Thanks Dale!

GF