> For performance, cobol typically requires a server round trip every time the screen changes. Round trips aren't the problem. Waiting for IO is. CICS solves t

> For performance, cobol typically requires a server round trip every time the screen changes. Round trips aren't the problem. Waiting for IO is. CICS solves this by not waiting for IO. It dumps the screen and moves on. Then it becomes the terminal's responsibility to wake CICS up with an attention key. If a front-end application is stuck waiting for terminal input, it's written wrong.