Well, the earlier RBs are already suspended. The unsatisfied WAIT places the task in the non-dispatchable status.
It is possible to add an IRB to the task and the task would be dispatchable and the IRB would run. On Mon, 1 Apr 2019 09:07:18 -0400 Joseph Reichman <reichman...@gmail.com> wrote: :>Its nothing in my code just maybe I have a misunderstanding it was my understanding :>That a wait suspends the RB not the entire TCB that documentation seems to say otherwise the entire TCB is suspended unless I didnt read right :>> On Apr 1, 2019, at 9:03 AM, Binyamin Dissen <bdis...@dissensoftware.com> wrote: :>> What is your question? :>> Show your code that is affected by the issue you perceive. :>> On Mon, 1 Apr 2019 07:54:09 -0400 Joseph Reichman <reichman...@gmail.com> :>> wrote: :>> :>Just looking at the documentation for the wait macro it says performance of the active task I was under the impression that the task is active just the RB is suspended :>> :>Which is why it is place in bits 8 - 31 of the ECB -- Binyamin Dissen <bdis...@dissensoftware.com> http://www.dissensoftware.com Director, Dissen Software, Bar & Grill - Israel Should you use the mailblocks package and expect a response from me, you should preauthorize the dissensoftware.com domain. I very rarely bother responding to challenge/response systems, especially those from irresponsible companies. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN