IMHO timeouts are a security issue, period. The resource issues of the 1960s and 19702 have not been relevant in a long time.
That said, I don't see sending a periodic Enter as a safe option. Isn't there something that you could sent that will have no effect on the session other than terminating and restarting the terminal wait? -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Nightwatch RenBand <[email protected]> Sent: Thursday, June 7, 2018 12:37 PM To: [email protected] Subject: Weird thought for ISPF enhancement I have long questioned the validity of TSO timeouts during normal working hours. I question whether the resource savings, outweigh the resource costs, including user time, of repeated logons and lost work. MY personal solution is to take advantage of the excellent scripting which comes with my 3270 emulation. Rocket Software BlueZone. It does logon, password must be manual of course, sets up all my screens just like I like, and then goes into a loop just less then the TSO timeout and does CURSOR and ENTER and goes back to sleep. When something goes wrong in a major system, I need my sessions UP and monitors RUNNING. ---------------------------------------------------------------------- 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
