The WCC is under the control of whatever program is doing the TPUT. If you know that you will run a long time with no terminal output then you can poll periodically, or rely on STAX. If the user is typing ahead at a furious rate then you might want to lock the keyboard at some point, but that should be rare.
CMS will display a "Not Accepted" status if the buffer is full. While I claim that CMS stands for Clumsy Monitor System, this is one area where it is cleaner than the TMP. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List [[email protected]] on behalf of Paul Gilmartin [[email protected]] Sent: Sunday, June 28, 2020 12:47 PM To: [email protected] Subject: Re: Use of BPXWUNIX and CP - a weekend quandary. On Sun, 28 Jun 2020 16:04:06 +0000, Seymour J Metz wrote: >Why not just set keyboard unlock in the WCC and do a TGET NOWAIT before each >TPUT? > Is the Write Control Character under control of the end user, or even of the OMVS developer? I sense a political battle: "What need ...?" Suppose there's extended computation with no terminal output? Should the terminal driver routinely do the TGET NOWAIT after every ENTER and save the data in the terminal input FIFO? (Lock the terminal on FIFO overflow.) What does CMS do? An example on MacOS: 596 $ sleep 10; while read I; do echo Saw $I; done; echo EOF first second third ^D Saw first Saw second Saw third EOF 597 $ -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
