|
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
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.