Open System Services Management and Operations Guide (G06.30+, H06.08+, J06.03+)

Components to Be Managed
You need to manage the software described in the following subsections:
• “Input/Output Utilities” (page 33)
• “OSS Security” (page 33)
• “OSS File-System Components” (page 33)
• “Interprocess Communication Facilities” (page 35)
Input/Output Utilities
Input/output utilities include:
• “OSSTTY Servers” (page 33)
• “Terminal Helper Servers” (page 33)
OSSTTY Servers
Guardian administrative applications or OSS applications at your site might require you to make
one or more copies of an OSSTTY server available for redirecting OSS standard files. The concept
of redirection is described in “Redirecting OSS Standard Files” (page 195); the command to start
a copy of OSSTTY is described in “Starting OSSTTY” (page 395). Other than deciding how many
copies of OSSTTY you need to run simultaneously, there are no management tasks associated with
OSSTTY.
Terminal Helper Servers
Both OSSTTY and Telserv terminal processes can perform nonblocking input and output through
the OSS file system because such communication is monitored and managed using a terminal
helper process.
A terminal helper process named $ZTTnn runs in each processor (nn indicates the processor
number). The terminal helper process starts automatically when the processor starts; if a terminal
helper process terminates abnormally, it takes down the processor in which it runs.
The processor running a terminal helper server process can be shut down without first stopping the
process, but you should stop all applications using that processor for terminal input or output first.
There are no management tasks associated with the terminal helper server processes.
OSS Security
Security for the OSS environment is configured and managed through the optionally licensed
Safeguard product. The use of Safeguard is described in “Managing Security” (page 216).
OSS File-System Components
The software components that work together to provide access to an OSS file are shown in Figure 3
(page 34). Many of these components are configured and managed using the interfaces described
in this guide.
Components to Be Managed 33