TRANSFER Installation and Management Guide

Idle Sessions
Managing a TRANSFER System
068837, Update 1 to 013198 Tandem Computers Incorporated 11–7
Example
The following example uses the default PARAM values: the TSCHED
CHECKSESSIONHOUR PARAM is set to 0, meaning midnight, and the TWORK
IDLESESSIONDELAY PARAM is set to 24.
Friday
14:00 SMITH_JOHN logs on to TRANSFER.
16:00 JONES_MARY logs on to TRANSFER.
17:00 John goes home for the weekend, but he forgets to log off.
17:15 Mary goes home for the evening; she also forgets to log off.
Saturday
00:00 Both sessions have been idle for about seven hours. TSCHED sets their
session expiration times to the current timestamp (about midnight).
11:00 Mary begins using the same TRANSFER session that she left logged on last
night. TISERV sets her session expiration time to binary zeroes to show that
the session has been used again.
15:00 Mary goes home for the weekend and again forgets to log off.
Sunday
00:00 Mary’s session has been idle for nine hours and John’s for 31 hours. John’s
session expiration time contains a timestamp, so TSCHED knows that it is
idle. Because 31 hours is greater than the IDLESESSIONDELAY of 24 hours,
TSCHED ends John’s session. Mary’s session expiration time contains
binary zeroes, so TSCHED leaves her session alone.
Monday
00:00 Mary’s session has now been idle for 33 hours. Her session expiration time
contains a timestamp, so TSCHED knows that it is idle. Thirty-three hours is
greater than the IDLESESSIONDELAY of 24 hours, so TSCHED ends her
session.
PS MAIL 6530 has an autologoff feature that works independently of the TRANSFER
monitoring of idle sessions. See the description of the Minutes Before Automatic
Logoff feature on the PROFILE screen in the PS MAIL Manual for 6530 Terminals.