I'd like to convert an EXEC to be more pipe-centric. This
EXEC operates as a server, processing transactions received
as spool files. It uses WAKEUP (RDR ... to detect the
arrival of requests.
I hesitate to perform the simple-minded transformation to
ADDPIPE CMD WAKEUP (RDR | ... because the documentation for
WAKEUP mentions that WAKEUP steals the I/O new PSW, and I
suspect this may be incompatible with proper Pipeline
operation (is it?) (But I can find no mention of such an
incompatibility in the documentation of either Pipelines
or WAKEUP.)
Section "3.4.1 Waking Up Once a Minute" has an example:
LITERAL +delay | DUP * | DELAY
I could use this to drive a CP QUERY READER NOH. I'm a
little hesitant -- a long polling interval causes unwanted
latency and a short interval is likely to cause needless
paging I/O.
And section "3.4.4 Processing Messages" mentions using
STARMSG to process IMSG. I could use this to trap the
IMSG that occurs when a spool file arrives. Is this the
most practical way?
Thanks,
gil
