Re: Commitment control

["R. Bruce Hoffman, Jr." <rbruceh@xxxxxxxxxxxxx>]

-----Original Message-----
From: Ron Hawkins <RON@CPUMMS.COM>
To: 'MIDRANGE-L@midrange.com' <MIDRANGE-L@MIDRANGE.COM>
Date: Sunday, March 05, 2000 6:54 PM
Subject: RE: Commitment control


>As long as we're talking commitment control, here's another question:
>
>Program A is a standalone program that uses commitment control. Reads one
record, updates various other files. Program B is a standalone program that
also uses commitment control. Reads one record, updates some other files.
Now maintenance comes along and wants/needs programA to call programB while
in the middle of its commit cycle.
>
>My question is this: When programB executes (in the same activation group)
and hits a commit statement, does it end the commit cycle from programA? In
other words, do I have to change the code in programB to not execute a
commit statment if coming from programA.
>


Yes. If you want just one transaction boundary to surround all of the
updates, then B should not issue the commit until/unless A has completed all
of the updates and then calls B.

===========================================================
R. Bruce Hoffman, Jr.
 -- IBM Certified AS/400 Professional System Administrator
 -- IBM Certified AS/400 Professional Network Administrator

"The sum of all human knowledge is a fixed constant.
    It's the population that keeps growing!"



+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---