RE: Input inhibited

The displays are using client access. The input inhibited does come on when
it starts writing to the display. It just takes awhile to gather info
before it starts outputting.



-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Al Mac
Sent: Friday, June 01, 2007 11:07 AM
To: Midrange Systems Technical Discussion
Subject: Re: Input inhibited

Is the problem with an old workstation & can you do a test to verify the
input inhibited light has not "burned out"? I don't remember if the "imput
inhibited" was always an icon on bottom of monitor.

If you change the user profile to KEY AHEAD, does it still bomb?

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

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.