TN3270 trx submission floods from Enter Keys being held down

[Kelly Bert Manning]

We have recurring floods of IMS and CICS transactions arriving from
individual TN3270 sessions. Typically it repeats 10 times per second
until the user wakes up and realizes that their enter key has been
held down by something. If they have their windows keyboard typematic
rate set at 10/second this generates 36,000 trx/hour from a single
session.

Typical scenario is someone rushing off to a meeting and jamming a keyboard
tray in without noticing an eraser, etc. jammed in, or fishing around on
their desk for something they need to take with them and not realizing that
they've shifted something so that it is pressing the Enter Key.

Another typical scenario is an occassional user who keeps a TN3270
session going but isn't a head down IMS or CICS user. They carry on
with other work and don't realize that something they shifted around
on their desk is pressing down the Enter Key.

Can this be avoided, to some extent, by turning off the "Type Ahead"
feature on TN3270 products such as Chameleon and Rumba?

It might still resubmit at whatever the round trip interval is, but at
least it wouldn't be filling up a TN3270 Type Ahead buffer. With any
luck response would be "slow" enough to let the keyboard buffer fill up
and make a noise that would attract the user's attention.

Could it also help in the scenario where users are in response mode and
hold down the Enter Key trying to get a faster response? One scenario
mentioned in IMS-L involved a user who submitted input data that
consistently caused an IMS MPP abend. When the TN3270 session remained
in Response Mode they held down the Enter Key to try and force the
host to respond. Instead they submmited hundreds of more trx that all
abended in exactly the same way.

Is there anything that can be done at the TN3270E server end to recognize
this type of flood of identical messages and cancel or alert it?