Re: SETLOCK OBTAIN

2012-05-23 Thread Jim Mulder
> I have the following piece of code running on many SRBs to > give serialisation. > > SETLOCK OBTAIN, >TYPE=CML,ASCB=(11), PRIMARY ADDRESS SPACE >MODE=UNCOND, >REGS=USE, >RELATED=(*(S

Re: SETLOCK OBTAIN

2012-05-23 Thread Ron MacRae
Sorry should have added. My situation, multiple SRBs in a single address space, some of which might be non-dispatchable, doesn't appear to match any of the subcodes of the S073 abend. I suspect this will be some variant of s073 but not 100% sure. Ron. --

SETLOCK OBTAIN

2012-05-23 Thread Ron MacRae
Hi all, I have the following piece of code running on many SRBs to give serialisation. SETLOCK OBTAIN, TYPE=CML,ASCB=(11), PRIMARY ADDRESS SPACE MODE=UNCOND

Re: SETLOCK OBTAIN GLOBAL SPIN

2007-10-08 Thread Peter Relson
If there are CPU or other spin locks held after the release, the PSW will remain disabled. If the releaser requested that the system remain disabled after the release, the PSW will remain disabled. At some later point, the code will re-enable. Peter Relson z/OS Core Technology Design ---

Re: SETLOCK OBTAIN GLOBAL SPIN

2007-10-04 Thread Binyamin Dissen
On Thu, 4 Oct 2007 10:20:27 -0400 Bill Hecox <[EMAIL PROTECTED]> wrote: :>I was looking at dump recently and discovered the CPU was disabled following a :>SETLOCK OBTAIN,TYPE=IOSUCB :>SETLOCK RELEASE,TYPE=IOSUCB :>I would have thought the SETLOCK RELEASE would have put the

SETLOCK OBTAIN GLOBAL SPIN

2007-10-04 Thread Bill Hecox
Hi, I was looking at dump recently and discovered the CPU was disabled following a SETLOCK OBTAIN,TYPE=IOSUCB SETLOCK RELEASE,TYPE=IOSUCB I would have thought the SETLOCK RELEASE would have put the CPU back in the interrupts enabled state. Does anyone have any additional information on this