Async I/O involves a couple of new system calls (new EMT codes) -- .reada, .writa, .astx .
The reada and writa calls take additional arguments in the firqb: fqfil is the AST
address, fqppn the AST argument, and fqnam1 the event flag number. I pulled that out of
the code so I don't have the details; it's in the V9.0 or later system calls
manual.
paul
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of
Johnny Billquist
Sent: Friday, April 13, 2012 12:18 PM
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Web-server under RSX-11M-PLUS
On 2012-04-13 17:20, Paul_Koning at
Dell.com wrote:
...
Oh yes, RSTS does have asynchronous I/O with ASTs, starting with V9.0.
They are only really async for selected devices: disk file I/O, and
streaming tapes (TS11 and TMSCP). That was done to make backup to streaming tapes run at
civilized performance.
Really? I didn't know that, but then I stopped using RSTS/E after V8, so things after
that are a bit more unknown to me. How did they implement it? The existing user operations
don't have any obvious place that AST hooks could fit, that I remember. Some spare
field in the FIRQB that could hold the AST address?
Johnny