<snip> I'm just adding an STAE recovery rtn in case of an abend leave the word busy </snip>
If you have a "word" that can be left "busy" then your design ought to be re-thought. Your use of that phrase would usually indicate that one work unit is setting a word "busy" and other work units, seeing that the word is "busy" either wait or (worse) spin until the word is "not busy". "Wait" leads to a design that is not responsive; "spin" can lead to deadlock (in particular when on an image with only a single CPU, if the "holder" might be lower priority than the "requestor"). The approach mentioned by Jonathan Scott is one that is used in many cases within z/OS. Peter Relson z/OS Core Technology Design
