> It seems that the ";wait=###" parameter does NOT work in
> batch.  Even if CIOR is used and thus the 'input' to the
> command is coming from a file.

Most CI timed reads are handled by the same procedure.
The one exception I can think of is the timed read for
a console reply via the INPUT...;CONSOLE command.
Ignoring this exception for the moment, this central
timed read routine just calls FCONTROL(stdin, 4, wait_val).
The FCONTROL call is skipped if the user is not interactive
(by the definition of the FRELATE intrinsic).  I believe
this code has not changed since the beginning of MPE/XL.
This code makes no assumption about the nature of the
STDIN file, which could be a terminal, disk or other.

Console INPUT is different in that it sends a message and the
MPE message send/receive mechanism supports a timeout value
unconditionally.

In general we try to make the CI behave the same in a job or a
session so that JCL can be created from interactive testing,
scripting etc.  However there are several (many?) long time
exceptions, including the YES/NO prompts on the PURGEACCT/GROUP/USER
commands, etc.

Hope this helps,
 Jeff Vance, CSY

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *