Thanks so much the documentation for IEAVPSE2 says "NO LOCKS HELD"
Sent from my iPhone > On May 3, 2016, at 7:50 AM, Peter Relson <rel...@us.ibm.com> wrote: > > I'll point out that the very fact that a global SRB paused very likely > means that you did not consider the SRB itself truly to be global. The > system will no longer treat it as such after the pause. > > Chris mentioned the local lock. I'm not sure why. You can't pause a work > unit that is holding the local lock. Obviously some other running work > unit could hold the local lock and thus prevent an SRB scheduled with > LLOCK=YES from beginning. > > In the scenario posed > SRB 1 scheduled to address space A pauses > SRB 2 was scheduled to address space A (from anywhere) > SRB 2 will run, according to normal dispatch priority rules. > > Peter Relson > z/OS Core Technology Design > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
