At 18:57 -0600 on 11/29/2013, John McKown wrote about Curiosity: ETXR
exit code (ATTACHX macro):
I think the former. with ETXR#2 interrupting ETXR#1 is what really happens.
I can't think of a way, off hand to test this.
To test, attach a few subtasks (which have a dispatching Priority
lower than the main task) which each wait on their own ECB. Have the
main task post the ECBs (since it is the higher priority, all the
POSTs will fire before the WAITs get satisfied). Now do a STIMER for
45 seconds in the main task so the sub tasks can run and complete
(ie: exit when the ECB got POSTed). Have the EXTR run the CB chain
and report if there is more than one IRB. Log the results so you know
if one IRB waited to occur once the prior one was over or if there
was a chain of IRBs.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
