×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Ryan,
You say transaction management, I say commitment control... <g> Just
as with shiny red fruits...
Here's where you start:
http://publib.boulder.ibm.com/infocenter/iseries/v5r4/index.jsp?topic=/r
zakj/rzakjcommitkickoff.htm
or
http://publib.boulder.ibm.com/infocenter/iseries/v5r4/topic/rzakj/rzakj.
pdf
http://publib.boulder.ibm.com/infocenter/iseries/v5r4/index.jsp?topic=/d
b2/rbafzmstisol.htm
-Eric
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Ryan Hunt
Sent: Monday, April 19, 2010 7:42 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Transaction Managment DB2/400
When I say transaction management, I mean:
Start a unit of work-->perform work-->check for errors (if none
found)-->commit work (else, rollback to start).
I'm hoping the list can provide me with two things.
1) a good reference for reading the details of transaction management on
DB2/400. I started doing some research and found lots on isolation
levels -
but that seems more about isolation of reads (whether reads can be
dirty,
etc.) rather than enforcing change control. (please note that I am
primarily an MS SQL DBA/Developer so I may have gleaned something
incorrect
from my reading).
2) a quick primer to get me started, for instance, the real code to
perform
this:
BEGIN TRANSACTION
UPDATE table1
set foo = x, bar = y
WHERE col1 = Z;
IF NO ERROR RETURNED THEN
COMMIT;
ELSE
ROLLBACK;
END IF;
Thanks much. RH
midrange.com
