Donna,

Your problems is caused by the ">*x" portion of the input statement.   When
the timeout occurs the entire 'input' command along with the 'text'
corresponding to 'hpcierr' 9003 gets written to the message file.  Thus the
next few loops are NOT going to 'time out' since the file contains data.

Since I don't know your process, I cannot say with certainty that you can
'remove' the ">*x" portion of the command (although in my test the 'time
out' work on every loop without the output redirection).  Perhaps you could
use the 'hpmsgfence' variable to control the 'error' output of your command
and still retain the same syntax.

Regards
Paul Christidis




hi again!

i'm stumped....  i've got a bit a ci script that should work
and actually sometimes works <sigh>

to describe the environment -- i've got a message file (file
x=...;semi;gmulti;acc=in) being watched by the following:
while 1=1
  setvar hpcierr 0
  input _s_rec;wait=60 <*x >*x
  if hpcierr = _s_time_out
  ....

_s_time_out is set to -9003 -- the number that hpcierr
should be set to if the input function times out.  the first
time thru the loop (allowing it to timeout), i get the
expected result hpcierr = _s_time_out = -9003.  the next
(and the next and the....) time thru the loop (still
allowing it to timeout), hpcierr is 0 and obviously not
equal to -9003 and things go sour.  shouldn't hpcierr always
be set if the input's wait time is met?              - d

--
Donna Garverick     Sr. System Programmer
925-210-6631        [log in to unmask]

>>>MY opinions, not Longs Drug Stores'<<<