Telserv Manual

Starting the Telserv Process
Telserv Manual—427174-009
3-16
Altering and Stopping a Telserv Process
Whenever a takeover occurs, Telserv makes the configuration data (specified through
SCF or through a management program) available to the backup process taking
control. Thus, you need not reconfigure the Telserv process manually. Configuration
data, when input to the Telserv process, is saved to an ENSCRIBE, key-structured file.
When taking over, the backup process reads the file in order to replicate the
configuration of the original primary. This file, or configuration database, resides in the
same subvolume as the Telserv process program file.
Each process pair has its own configuration database with a unique file name. To
ensure uniqueness, the three-letter string ZTZ is prefixed to the process-pair name.
For example, a process pair with the name $ZTNT acquires a configuration database
named ZTZZTNT.
Telserv does not delete the configuration database when you stop the process. You
must therefore periodically remove unused databases. If you start a Telserv process
and a configuration database with a corresponding name already exists, Telserv
overwrites the original database.
Altering and Stopping a Telserv Process
Once a Telserv process has been started with the RUN command, you can display
information on the process, alter it, or stop it with the Telserv Subsystem Control
Facility (SCF) commands. You can alter, for example, the maximum number of
windows allowed, control the display of the service menu, and change the time after
which inactive windows (client sessions) are logged off. Section 4, Subsystem Control
Facility (SCF) for Telserv introduces the Telserv SCF interface.