On 8/12/2017 2:20 PM, Charles Mills wrote:
Let me volunteer to be the dumb one here.

Note that use of transactional processing is inherently dual path.
You would still need the "other" path even if every machine in the world 
already supported TBEGIN.

A non-constrained transaction needs a fallback path to deal with anything other than CC=0 from TBEGIN. If you get CC=1 or CC=3 you really have no choice but to go to the fallback path. You could retry after CC=2, but you don't want to get into a loop doing so. So you really need to set a single-digit retry limit and go to the fallback path when it's reached.

Edward E Jaffe
Phoenix Software International, Inc
831 Parkview Drive North
El Segundo, CA 90245

Reply via email to