Re: Input inhibited

Craig,
I recently ran into a similar problem, and it had nothing to do with the type
of workstation.
Look in your display file for the INVITE keyword. This was used way back in
the past for multiple requester terminal (MRT) programs. It allows the program
to continue after issuing a read operation without actualy waiting for data.
Unless your program is actualy specifing the device that it is communicating
with, try removing the keyword and see if that fixes your problem.

Jeff Young
Sr. Programmer Analyst
IBM -e(logo) server Certified Systems Exper - iSeries Technical Solutions V5R2
IBM Certified Specialist- e(logo) server i5Series Technical Solutions Designer
V5R3
IBM Certified Specialist- e(logo)server i5Series Technical Solutions
Implementer V5R3









----- Original Message ----
From: Craig Jacobsen <CraigJacobsen@xxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Sent: Friday, June 1, 2007 9:04:02 AM
Subject: Input inhibited


I am working on an old workstation program where the input inhibited light
does NOT come on after a read while it builds the subfile. This allows the
user to hit enter and the program bombs out with I/O error CPF4737 (output
file not done). If enter is not hit, the subfile displays properly.

Is there a keyword or something I can do to make the input inhibited stay on
until the output is finished?

Thanks in advance,

Craig