ATM Configuration and Management Manual

Glossary
ATM Configuration and Management Manual—522307-003
Glossary-4
connection
CONFSAVE. See also system configuration database. In RVUs prior to the G-series,
the configuration file is either the OSCONFIG file used by the Configuration Utility
Program (COUP) or the CONFTEXT file used during system generation.
connection. (1) The path between two protocol modules that provides reliable stream
delivery service. (2) For OSM and TSM software, the logical link established between
the client software on a workstation and the server software on an NonStop S-series
system after a logon sequence has been performed. The two types of logical
connections are service connections and low-level links.
control and inquiry. The aspects of SCF object management related to the state or
configuration of an object. Such aspects include actions that affect the state or
configuration of an object, inquiries about the object, and commands pertaining to the
session environment (for example, commands that set default values for the session).
controller. See I/O controller or ServerNet addressable controller (SAC).
CRU. See customer-replaceable unit (CRU).
customer-replaceable unit (CRU). A unit that can be replaced in the field either by
customers or by qualified personnel trained by HP. CRUs are divided into the
categories of Class 1, Class 2, and Class 3 based on the risk of causing a system
outage if the documented replacement procedure is not followed correctly and how
much CRU-replacement training or experience is advisable. See also Class-1 CRU,
Class-2 CRU, Class-3 CRU, and field-replaceable unit (FRU).
cyclic redundancy check (CRC). The most widely used error detection code for ensuring
the integrity of transmitted data. The digits of the CRC are calculated by the sender for
each block of data sent and recalculated by the receiver. (It is a family of mathematical
functions involving computing the quotient and remainder of a polynomial division.) A
CRC is a form of checksum.
data forward count (DFC). The number of packets the adapter will receive before sending
them to the host.
data forward timer (DFT). The number of milliseconds the adapter will wait before packets
are sent to the host.
dynamic-link library (DLL). A collection of procedures whose code and data can be loaded
and executed at any virtual memory address, with run-time resolution of links to and
from the main program and other independent libraries. The same DLL can be used by
more than one process. Each process gets its own copy of DLL static data. Contrast
with shared run-time library (SRL). See also TNS/R library.
dynamic loading. Loading and opening dynamic-link libraries under programmatic control
after the program is loaded and execution has begun.
dynamic shared object (DSO). See dynamic-link library (DLL).