STO - Screen Time Out Sign off idle terminals without harming jobs that are running Get contol of all workstations. Don't let them be left unattended forever. Kill all terminals when you want to do a night backup. But all done cautiously. STO controls the operation of all terminals connected to an IBM AS/400 or S/36. Each terminal is given a time limit to remain inactive When this time is exceeded a terminal time out occurs and STO operates according to instructions you set up in a system control file. This action could be
			Do nothing
			Log the time out only
			Lock the terminal
			Cancel the job running
			Sign off the terminal
			Vary off the terminal
Important features of STO The most important feature is the ability to detect whether an on-line job is or is not running at the terminal. For example, if a time out occurs and the user is running a complex on-line job that does file updates and adds, you probably do not want to sign off the terminal but rather lock or disconnect it. Note - STO locks a terminal by holding it. The terminal cannot be used again until manually released by the system operator. However, if no on-line job is running, (e.g. the terminal is displaying a menu) you can safely sign off the terminal when a time out occurs. System overides With STO you define a general policy for your computer system indicating
	The polling interval for STO
	The time out value
	What STO should do when a time out occurs and no on-line job is running
	What STO should do when a time out occurs and an on-line job is running
and then you write a set of overrides to these defaults based on
		The workstation ID
		The user ID
		The program running and the Library used ^(1)
		The procedure running ^(2)
		The active command ^(1)
		The active menu ^(2)
^(1) STO/400 ^(2) STO/36 You can have an unlimited number of overrides. When a time out occurs at a terminal, STO finds out if an override exists for that workstation ID or User ID, or program running etc. If an override is found, the policy stipulated in the override is followed. If no override is found, the general policy is used. In this way you can set up different time outs for security sensitive applications and for general applications. Or to exclude certain terminals (e.g. the system console). Or to give programmers more lime than data entry operators etc. Audit trail Every time out is logged to an audit trail file. Periodically you can print an audit trail report showing a detailed description of the security violations found by STO. S/36 backup - STOKILL A common problem of the S/36 is the inability to run a backup and compress the system overnight because one user forgot to turn off his/her terminal. STO resolves this problem. A special procedure called STOKILL, when loaded, will sign oft all workstations except the one it was loaded from (or the system console if EVOKED or running from the job queue). For more information or a free demo with manual: download STO/400 (2.6 Mb) or contact us via the traditional communication channels: InterData Systems, Inc. 522 Balliol St. Toronto, On. Canada,   M4S 1E3 Phone: 1 (416) 932-8372 Fax: 1 (416) 352-5457 email: mail@interdatasystems.com