Asynchronous Terminals and Printer Processes Configuration and Management Manual
Table Of Contents
- What’s New in This Manual
- About This Manual
- 1 Configuration Quick Start
- 2 Overview of the ATP6100 Subsystem
- 3 Configuring the ATP6100 Subsystem
- 4 Printer Profiles and Default Modifiers
- 5 Terminal Profiles and Default Modifiers
- 6 ManagingATP6100Usingthe SubsystemControlFacility(SCF)
- 7 PTrace Facility for ATP6100
- A ATP6100 Subsystem Error Messages
- B SCF Command Summary for ATP6100
- ABORT LINE Command
- ABORT SU Command
- ACTIVATE SU Command
- ALTER LINE Command
- ALTER SU Command
- INFO LINE Command
- INFO SU Command
- LOAD LINE Command
- START LINE Command
- START SU Command
- STATS LINE Command
- STATS SU Command
- STATUS LINE Command
- STATUS SU Command
- STOP LINE Command
- STOP SU Command
- SUSPEND SU Command
- SWITCH PROC Command
- TRACE LINE Command
- VERSION PROC Command
- C Moving to G-Series or H-Series RVUs
- Glossary
- Index

Glossary
Asynchronous Terminals and Printer Processes Configuration and Management Manual—424280-003
Glossary-12
service connection
service connection. A connection between the TSM client software running on a TSM
workstation and the TSM server software running on a NonStop S-series server. A
service connection can be used only to communicate with the server when the
NonStop Kernel operating system is running. A service connection provides a
comprehensive service and maintenance picture of the server and is used to perform
most service management tasks.
site update tape (SUT). One or more tapes that contain each target system’s site-specific
subvolume and various products. Each product contains a softdoc and a complete set
of files. A SUT is delivered with every new NonStop system and can be ordered
whenever a new version of the system software is available. A full SUT contains the
current RVU of the operating system and all product software that has been ordered
with it. A partial SUT contains a subset of products for the current software RVU.
state. In Subsystem Control Facility (SCF) subsystems, one of the generally defined
possible conditions of an object with respect to the management of that object.
Examples of states are DEFINED, STARTED, and STOPPED.
static information. Information that represents the set of customer-replaceable units
(CRUs) on a NonStop system. Contrast with dynamic information.
SUBSYS object type. The Subsystem Control Facility (SCF) object type for most
subsystems that use SCF as the user interface.
subsystem. (1) A secondary or subordinate system, usually capable of operating
independently of or asynchronously with a controlling system. (2) A program or set of
processes that manages a cohesive set of Subsystem Control Facility (SCF) objects.
Each subsystem has a manager through which applications can request services by
issuing commands defined by that subsystem. See also subsystem manager.
Subsystem Control Facility (SCF). An interactive interface for configuring, controlling, and
collecting information from its subsystems.
Subsystem Control Point (SCP). The message router for all Subsystem Control Facility
(SCF) subsystems. There can be several instances of this process. Using the
Subsystem Programmatic Interface (SPI), applications send each command for a
subsystem to an instance of this process, which in turn sends the command to the
manager process of the target subsystem. SCP also processes a few commands itself.
It provides security features, version compatibility, support for tracing, and support for
applications implemented as process pairs.
subsystem manager. A process that performs configuration and management functions for
a Subsystem Control Facility (SCF) subsystem.
subvolume. A group of related files stored on a disk; all the files have the same volume and
subvolume name, but each file has a unique file identifier.
summary report. A brief informational listing of status or configuration information provided
by the Subsystem Control Facility (SCF) STATUS or INFO command.