NonStop S-Series Hardware Installation and FastPath Guide (G06.25+)

Glossary
HP NonStop S-Series Hardware Installation and FastPath Guide—529443-001
Glossary-75
OSCONFIG file
OSCONFIG file. In G-series release version updates (RVUs), a configuration file built during
system generation that contains only Software Problem Isolation and Fix Facility
(SPIFF) and Software Identification (SWID) tool records. In D-series and earlier RVUs,
the Configuration Utility Program (COUP) uses the $SYSTEM.SYSnn.OSCONFIG file
to store its configuration information.
OSI. See Open Systems Interconnection (OSI).
OSIMAGE. A file built during system generation that contains the complete image of the HP
NonStop™ operating system that runs in each processor in the system.
OSM. See HP NonStop™ Open System Management (OSM) Interface.
OSM Event Viewer. OSM replacement for the TSM Event Viewer.
OSM Low-Level Link. OSM replacement for the TSM Low-Level Link.
OSM Notification Director. OSM replacement for the TSM Notification Director.
OSM Service Connection. OSM replacement for the TSM Service Application.
OSS. See Open System Services (OSS).
OSS environment. See Open System Services (OSS) environment.
OSS Monitor. See Open System Services (OSS) Monitor.
OSS process ID. In the Open System Services (OSS) environment, the unique identifier
that identifies a process during the lifetime of the process and during the lifetime of the
process group of that process. See also PID.
OSS signal. See Open System Services (OSS) signal.
OSS user ID. See HP NonStop™ operating system user ID.
outage. Condition during which a computer system is not capable of doing useful work.
Outages can be planned or unplanned. From the end user’s perspective, an outage is
any time an application being used is not available. See also planned outage and
unplanned outage.
outage minutes. A metric for measuring outages that translates percentages into
minutes/year of downtime.
output destination. The resource to which Subsystem Control Facility (SCF) sends its
responses to commands. SCF can direct output to a disk file, an application process, a
terminal, or a printer. The initial output destination is determined by the form of the
RUN command used to initiate SCF. The output destination can be changed
dynamically during an SCF session.