On 21/06/2022 1:07 am, Paul Gilmartin wrote:
On Mon, 20 Jun 2022 08:47:49 -0700, Charles Mills wrote:
...
The assembler routine will take as input a delay time in hundredths of a second
(because of STIMER), do a WAIT ECBLIST, and return one of
'T' -- the time expired
'P' -- the operator entered STOP
'F modify command operand' -- the operator entered MODIFY
What happens if the operator enters STOP during the (relatively minuscule)
fraction of time that Rexx, not Assembler is active?
In that case the EXTRACT ECB will be posted and the routine will stop
when it is re-entered and the ECB is tested. I've written something
similar myself for Lua. The differnce is Lua is object oriented and
holds state where REXX is not so it's a Frankenstien monster to create a
reusable context.
It's hard to justify why anybody would do it for REXX when you can just
code a C++ program using __console() and a std::thread.
Is there a need for persistent storage accessible by both Rexx and Assembler?
Is there a way for the operator to send SIGINT (Unix "Modify")? Can Rexx
catch it?
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
