On 9/21/2012 5:01 AM, Peter Relson wrote:
Of course Binyamin is right. Since the "runner" can get interrupted, then the runner needs to run within a transaction too. (Getting interrupted includes the z/OS LPAR getting interrupted by LPAR processing, which covers even the disabled PSW case)
There are existing search/update models in which the "runner" performs its search using only block-concurrent instructions (such as L) without serialization and then checks later whether a retry is needed. A good example is IEANTRT. That code is FAST because the "retrieve" function never serializes against the "update" function. -- Edward E Jaffe Phoenix Software International, Inc 831 Parkview Drive North El Segundo, CA 90245 310-338-0400 x318 [email protected] http://www.phoenixsoftware.com/
