The task will only be dispatched if the top RB is active. So unless someone
schedules, e.g., an IRB, the task will be inactive until the RB is active.
Nit: in MVS the word "suspend" has a technical meaning that doesn't apply here.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
19 9:07 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Question on Wait macro
It’s 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 didn’t read rig
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
wrote:
:>Its nothing in my
It’s 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 didn’t read right
Thanks
> On Apr 1, 2019, at 9:03 AM, Binyamin Dissen
>
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
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
I would think there is a new TCBRBP
> On Apr 1, 2019, at 8:44 AM, Tom Marchant
> <000a2a8c2020-dmarc-requ...@listserv.ua.edu> wrote:
>
>> On Mon, 1 Apr 2019 07:54:09 -0400, Joseph Reichman wrote:
>>
>> Just looking at the documentation for the wait macro it says “performance of
>> the
On Mon, 1 Apr 2019 07:54:09 -0400, Joseph Reichman 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
What do you think it would mean for the task to be active when
