Distributed Name Service (DNS) Management Programming Manual
DNS Subsystem Architecture
Introduction
1–4 46958 Tandem Computers Incorporated
LOAD ($altvol.ZDNS.LOAD). LOAD is a command file that can be read by
DNSCOM to load the DNS database with the definitions of some commonly used
Tandem subsystems and their object types.
DBDDLS ($altvol.ZDNS.DBDDLS). DBDDLS is a Data Definition Language (DDL)
source file that describes the DNS database.
DNS Configurations Each DNS database is associated with a DNS configuration that is created using
DNSCOM’s INITIALIZE DNS command. Each DNS configuration consists of:
A management application. Your application interacts with DNS
programmatically using the SPI buffers to open a name manager process and
send requests to that manager.
A DNS database file. Each DNS database consists of 16 key-sequenced files. The
files need not reside on the same disk volume.
A name manager process. Each DNS configuration has a name manager process.
The process name assigned to each name manager must be unique on each system.
Assigning a name to a name manager is discussed in the Distributed Name Service
(DNS) Management Operations Manual.
A queue file. The queue file acts as a buffer between the name manager and name
exporter process, assisting communication between the two.
A name exporter process (optional). If name definitions are to be replicated from
or to the DNS database (from or to other systems in your network), the
configuration must include a name exporter process. Like name managers, each
name exporter must be assigned a unique process name on each system.
Assigning a name to a name exporter is discussed in the Distributed Name Service
(DNS) Management Operations Manual.
A DNS configuration file. DNS uses the configuration file to categorize
information about the configuration, such as the name of each database file, the
name of the name manager process, and the name of the name exporter process.
The interactions among the various elements of the DNS subsystem are shown in
Figure 1-2.