NonStop S-Series Planning and Configuration Guide (G06.25+)

Table Of Contents
Glossary
HP NonStop S-Series Planning and Configuration Guide523303-015
Glossary-96
service side
TSM allow you to use the help of a service provider by configuring client software to
support remote notification and remote access.
service side. The side of a system enclosure that contains, behind an optional door,
processor multifunction (PMF) customer-replaceable units (CRUs) or I/O multifunction
(IOMF) CRUs, ServerNet expansion boards (SEBs), modular SEBs (MSEBs), and
ServerNet adapters. The service side is opposite the appearance side
. Cables are
accessed from the service side. System enclosures are typically arranged so that the
service side is the least visible side.
session. In the Open System Services (OSS) environment, a set of process groups
associated for job control purposes. A session can have a controlling terminal.
session leader. In the Open System Services (OSS) environment, the process that created
a session.
session lifetime. In the Open System Services (OSS) environment, the period that begins
when a session is created and ends when the lifetime of the last remaining process
group of the session ends.
setup configuration. A simple stand-alone network used to configure the OSM or TSM
environment. The setup configuration consists of the server, the primary system
console, an Ethernet switch or hub, and two local area network (LAN) cables. One
cable connects the primary system console to the switch or hub, and another cable
connects the switch or hub to a processor multifunction (PMF) customer-replaceable
unit (CRU) in group 01 of the server. When OSM or TSM configuration is complete, the
setup configuration can serve as the working network configuration. Variations of the
setup configuration can be constructed using additional cables and switches or hubs to
increase fault tolerance.
set-user-ID program. In the Open System Services (OSS) environment, a program file that
has the
S_ISUID bit set in its file mode.
shared memory. An interprocess communication mechanism that allows two or more
processes to share a given region of memory.
Shared Millicode Library. An intrinsic library containing privileged or TNS-derived millicode
routines used by many native-compiled programs and by emulated TNS programs.
This library includes efficient string-move operations, TNS floating-point emulation, and
various privileged-only operations. These routines are mode independent. They
comply with native calling conventions but can be directly invoked from any mode
without changing execution modes.
shared run-time library (SRL). A collection of procedures whose code and data can be
loaded and executed only at a specific assigned virtual memory address (the same
address in all processes). SRLs use direct addressing and do not have run-time
resolution of links to and from the main program and other independent libraries.
Contrast with dynamic-link library (DLL)
. See also TNS shared run-time library (TNS
SRL) and TNS/R native shared run-time library (TNS/R native SRL).