DECnet-Plus_for_OpenVMS_____________________________
Installation and Basic Configuration
Order Number: AA-QPSUB-TE
November 1996
This book explains how to install and configure the
DECnet-Plus for OpenVMS software and how to perform
the postinstallation steps.
Revision/Update Information: This is a revised
manual.
Operating Systems: OpenVMS Alpha Version
7.1
OpenVMS VAX Version 7.1
Software Versions: DECnet-Plus for OpenVMS
Version 7.1
X.25 for OpenVMS Alpha
Version 7.1
Digital Equipment Corporation
Maynard, Massachusetts
________________________________________________________________
November 1996
Digital Equipment Corporation makes no representations
that the use of its products in the manner described in
this publication will not infringe on existing or future
patent rights, nor do the descriptions contained in this
publication imply the granting of licenses to make, use,
or sell equipment or software in accordance with the
description.
Possession, use, or copying of the software described in
this publication is authorized only pursuant to a valid
written license from Digital or an authorized sublicensor.
Digital conducts its business in a manner that conserves
the environment and protects the safety and health of its
employees, customers, and the community.
� Digital Equipment Corporation 1996. All rights reserved.
The following are trademarks of Digital Equipment
Corporation: Bookreader, DDCMP, DEC, DECdirect, DECnet,
DECNIS, DECserver, DECsystem, DECwindows, Digital,
DNA, InfoServer, OpenVMS, PATHWORKS, ULTRIX, VAX, VAX
DOCUMENT, VAXcluster, VAXstation, VMS, VMScluster, and
the DIGITAL logo.
The following are third party trademarks:
Macintosh is a registered trademark of Apple Computer, Inc.
MS-DOS is a registered trademark of Microsoft Corporation.
Multinet is a registered trademark of TGV, Inc.
OS/2 is a registered trademark of International Business
Machines Corporation.
OSF/1 is a registered trademark of Open Software
Foundation, Inc.
PATHways is a registered trademark of The Wollongong Group.
SCO is a trademark of Santa Cruz Operations, Inc.
TCPware is a registered trademark of Process Software
Corporation.
UNIX is a registered trademark in the United States and
other countries, licensed exclusively by X/Open Co. Ltd.
All other trademarks and registered trademarks are the
property of their respective holders.
_________________________________________________________________
Contents
Preface................................................... vii
Part I DECnet-Plus for OpenVMS Installation
1 Preparing to Install DECnet-Plus for OpenVMS
1.1 The POLYCENTER Software Installation
Utility....................................... 1-1
1.2 Inspecting the Distribution Kit............... 1-1
1.3 Time Required for Installation and
Configuration................................. 1-3
1.4 Prerequisite Software and Licenses............ 1-3
1.4.1 Software and Licenses..................... 1-3
1.4.1.1 DECnet and OSI Applications over
TCP/IP.................................. 1-4
1.4.2 Checking Licenses......................... 1-5
1.5 System Requirements........................... 1-5
1.5.1 Disk Space................................ 1-5
1.5.2 Required Memory........................... 1-7
1.5.3 Required System Parameters................ 1-7
1.5.3.1 SYSGEN Parameters for OpenVMS Cluster
Members................................. 1-8
1.6 Privileges and Rights Identifiers............. 1-8
1.7 Backing Up the System Disk.................... 1-9
1.8 Notifying Users............................... 1-9
iii
2 Pre-Installation Tasks
2.1 Information Required to Complete the
Installation Planning Checklist............... 2-1
2.2 Installation Planning Checklist............... 2-1
3 Installing DECnet-Plus for OpenVMS
3.1 Recommended Order for Installing Software..... 3-3
3.1.1 Installing DECnet-Plus for an OpenVMS
Alpha System.............................. 3-3
3.1.2 Installing DECnet-Plus for a VAX System... 3-6
3.2 Installing DECnet-Plus Using the POLYCENTER
Software Installation Utility................. 3-8
3.2.1 Sample DECnet-Plus for OpenVMS Alpha
Installation ............................. 3-8
3.2.2 Sample DECnet-Plus for OpenVMS VAX
Installation.............................. 3-9
3.3 Files Installed on Your System................ 3-11
Part II DECnet-Plus for OpenVMS BASIC Configuration
4 Configuration Options
4.1 Selecting a Configuration Option.............. 4-2
4.2 How to Run NET$CONFIGURE ..................... 4-4
4.2.1 Local and Global Symbols.................. 4-5
4.2.2 Running the Procedure from Different
Processes................................. 4-6
5 Using the FAST Configuration Option
5.1 Invoking the FAST Configuration Option........ 5-1
5.2 Changing a Current DECnet-Plus System
Configuration................................. 5-6
iv
6 Using the BASIC Configuration Option
6.1 Invoking the BASIC Configuration Option....... 6-1
6.2 Directory Name Services....................... 6-2
6.2.1 Node Full Name............................ 6-3
6.2.2 Specifying the Node Type.................. 6-5
6.2.3 Specifying Routing Information............ 6-5
6.2.4 Node Synonym.............................. 6-6
6.2.5 Specifying a DECnet Phase IV-Compatible
Address................................... 6-6
6.2.6 Specifying a Phase IV Prefix.............. 6-7
6.2.7 Configuring Network Addresses............. 6-7
6.2.8 DNA Address Format........................ 6-7
6.3 Configuring Devices........................... 6-7
6.3.1 Configuring an Alpha System .............. 6-8
6.3.2 Configuring a VAX System.................. 6-9
6.4 Configuring Transports........................ 6-11
6.5 Configuring Time Zone Differential Factors.... 6-11
6.6 Configuring an Event Dispatcher............... 6-11
6.7 Configuring an Application Database........... 6-11
6.8 Configuring a Cluster Alias .................. 6-12
6.9 Changing a Current DECnet-Plus System
Configuration................................. 6-18
7 Managing Name Services
7.1 Names Services Overview....................... 7-1
7.1.1 The Local Namespace ...................... 7-1
7.1.1.1 Creating a Local Namespace.............. 7-2
7.1.1.2 Managing the Local Namespace............ 7-2
7.1.2 The Digital Distributed Name Service
(DECdns).................................. 7-2
7.1.2.1 Creating a New Namespace................ 7-3
7.1.2.2 Creating a DECdns Namespace............. 7-4
7.1.3 Domain Name System........................ 7-7
7.1.4 Namespace Management...................... 7-8
7.2 Name Service Search Path...................... 7-8
7.2.1 Configuring the Search Path Information... 7-9
7.2.1.1 Naming Search Path in a Cluster......... 7-10
7.2.2 Displaying the Search Path Information.... 7-10
7.2.3 Modifying the Search Path Information..... 7-10
7.2.4 Creating a Site-Specific Search Path NCL
Script.................................... 7-11
7.2.5 Using the Search Path to Ease Migration... 7-12
v
7.2.6 Setting Up Naming Templates............... 7-12
7.3 Domain Synonyms............................... 7-13
7.3.1 Search Path Naming Template Support for
Domain Synonyms........................... 7-14
7.3.2 Local Aliases............................. 7-14
7.4 Node Synonym Directories...................... 7-15
7.4.1 Defining an Alternate Node Synonym
Directory................................. 7-15
7.4.2 When to Use the Logical Name.............. 7-15
7.5 Using a DNS Version 1 Namespace with DECdns
Version 2..................................... 7-16
7.5.1 Preparing a DNS Version 1 Namespace for
Use by DECdns Version 2................... 7-17
7.5.2 Using the DNS Version 1 Namespace......... 7-18
7.6 Registering a Node in the Namespace........... 7-19
7.6.1 Export/Import File Format................. 7-19
7.6.2 Problems Registering a Node............... 7-19
Part III Additional Installation Information
A The POLYCENTER Software Installation Utility
A.1 DCL Help with POLYCENTER...................... A-2
A.1.1 DCL Command Summary....................... A-3
A.2 Creating and Using a Product Configuration
File.......................................... A-6
A.2.1 Responding to Installation Questions...... A-8
A.3 Verifying Pre-installation Tasks.............. A-8
A.4 Resolving Conflicts........................... A-9
A.5 Determining Installation Progress............. A-9
A.6 Possible Installation Errors.................. A-10
A.7 Reporting Problems............................ A-10
B Installing DECnet-Plus for OpenVMS from an InfoServer
B.1 Steps to Installing the Software from an
InfoServer.................................... B-1
B.2 Install Commands.............................. B-2
vi
C System Files Loaded During Installation
Index
Figures
3-1 Installation and Configuration Flowchart
(Alpha Only).............................. 3-5
3-2 Installation and Configuration Flowchart
(VAX Only) ............................... 3-8
Tables
1-1 Disk Space Requirements - Optional
Software.................................. 1-6
1-2 Minimum System Parameters Required - Base
Software Installation..................... 1-7
2-1 Installation Planning Checklist........... 2-2
4-1 Choosing Your Configuration Option........ 4-3
A-1 DCL PRODUCT Commands and Qualifiers....... A-3
vii
_________________________________________________________________
Preface
This is the first installation book you should read in
order to successfully install DECnet-Plus for OpenVMS. It
also includes how to configure DECnet-Plus for OpenVMS
using the FAST and BASIC configuration options, and
information about name services.
The second installation book (DECnet-Plus for OpenVMS
Applications Installation and Advanced Configuration)
describes using the ADVANCED configuration option, and
how to install and configure:
o X.25 for OpenVMS Alpha
o VAX P.S.I. and VAX P.S.I. Access for OpenVMS VAX
o OSI layered software applications:
- File Transfer, Access, and Management (FTAM)
- Virtual Terminal (VT)
- OSI Applications Kernel (OSAK)
________________________ Note ________________________
DECnet-Plus for OpenVMS must be installed on your
system before you can install X.25, FTAM, VT, or OSAK
software.
______________________________________________________
vii
Intended Audience
This book is written for:
o OpenVMS system managers
o DECnet-Plus software installers
o Network planners and managers
Structure of This Book
This book has three parts:
Part I Describes the pre-installation and installation
steps necessary to install DECnet-Plus for OpenVMS.
Part Provides help to determine which configuration
II option to use: FAST, BASIC or ADVANCED. Describes
how to run a FAST configuration, and a BASIC
configuration including examples for an Alpha and a
VAX system. Also includes an overview of the naming
services you can select during configuration.
Part Includes a basic overview on the POLYCENTER
III Software Installation utility, an example of
installing DECnet-Plus for OpenVMS from an
InfoServer, and a list of system files loaded
during installation.
Terminology
The following terms are used interchangeably in this book:
o Alpha and AXP
o Transition and migration
o Phase IV and DECnet Phase IV
o End system and end node
o Intermediate system and router
o DECnet-Plus and Phase V
viii
Related Documents
The following books provide additional information:
o DECnet-Plus for OpenVMS Applications Installation and
Advanced Configuration
The second installation book to read in order to
successfully install and configure X.25 for OpenVMS
Alpha, P.S.I and P.S.I. Access for OpenVMS VAX, FTAM,
VT, and OSAK. It also includes how to configure DECnet-
Plus for OpenVMS using the ADVANCED configuration option
and how to modify a configuration.
o DECnet-Plus for OpenVMS Introduction and User's Guide
Introduces the DECnet-Plus for OpenVMS features and
tools, and how to use and manage a DECnet-Plus for
OpenVMS end system. Also provides a comprehensive
glossary of DECnet-Plus terminology.
o DECnet-Plus Planning Guide
Explains in detail the transition from DECnet Phase IV
to DECnet-Plus, providing configuration guidelines and
planning tasks.
o DECnet-Plus DECdns Management
o DECnet-Plus DECdts Management
o DECnet-Plus for OpenVMS Network Management
o X.25 for OpenVMS Configuration Guide
o OpenVMS License Management Utility Manual
o OpenVMS System Management Utilities Reference Manual
For additional information on the DECnet-Plus products and
services, access the Digital OpenVMS World Wide Web site.
Use the following URL:
http://www.openvms.digital.com
ix
Reader's Comments
Digital welcomes your comments on this manual or any of the
DECnet-Plus documents. Send us your comments through any of
the following channels:
Internet openvmsdoc@zko.mts.dec.com
Fax 603 881-0120, Attention: OSSG Documentation,
ZKO3-4/U08
Mail OSSG Documentation Group, ZKO3-4/U08
110 Spit Brook Rd.
Nashua, NH 03062-2698
How To Order Additional Documentation
Use the following table to order additional documentation
or information. If you need help deciding which
documentation best meets your needs, call 800-DIGITAL
(800-344-4825).
x
Conventions
The following conventions are used in this book.
___________________________________________________________
Convention_______Meaning___________________________________
special type Indicates a literal example of system
output or user input. In text, indicates
command names, keywords, node names, file
names, directories, utilities and tools.
UPPERCASE Indicates keywords that you enter. You
can type the characters in uppercase or
lowercase. You can abbreviate command
keywords to the smallest number of
characters that OpenVMS, NCP, NCL, or
the other tools accept.
Uppercase also indicates the names of
files, directories, utilities, tools,
commands, parameters, and procedures.
italic type Indicates a variable.
bold Indicates a new term defined in the text
or important information.
<Return> Indicates that you press the Return key.
Ctrl/x Indicates that you press the Control key
while you press the key noted by x.
[YES] Brackets indicate that the enclosed item
is a default value in an installation
prompt.
{ } In command format descriptions, indicates
you must enter at least one listed
_________________element.__________________________________
xi
Part I
_________________________________________________________________
DECnet-Plus for OpenVMS Installation
Part I describes the prerequisite steps necessary to
install DECnet-Plus for OpenVMS, and how to install it.
o Chapter 1 - Preparing to Install DECnet-Plus for OpenVMS
o Chapter 2 - Pre-Installation Tasks
o Chapter 3 - Installing DECnet-Plus for OpenVMS
1
_________________________________________________________________
Preparing to Install DECnet-Plus for OpenVMS
This chapter describes the tasks you must perform before
installing and configuring the DECnet-Plus for OpenVMS
distribution kit.
1.1 The POLYCENTER Software Installation Utility
The POLYCENTER Software Installation utility replaces
VMSINSTAL as the method of installing layered products for
OpenVMS systems. It allows you to install several software
products with a single command.
Full details for using the POLYCENTER Software Installation
utility to install and manage software products on your
system are provided in the OpenVMS System Management
Utilities Reference Manual. This manual also provides
information on removing products along with other
POLYCENTER Software Installation utility features.
See Appendix A for a basic overview of the POLYCENTER
Software Installation utility.
1.2 Inspecting the Distribution Kit
Before you install the DECnet-Plus for OpenVMS software,
make sure you have a complete software distribution kit. If
you have the OpenVMS condist CD-ROM distribution kit, check
the CD master index for the kit location. If you have a
magtape or TK50 kit, supply the device name when requested
by the POLYCENTER Software Installation utility.
Check that the kit contains everything listed on the bill
of materials (BOM). If anything is missing or damaged,
contact your Digital representative.
Preparing to Install DECnet-Plus for OpenVMS 1-1
Preparing to Install DECnet-Plus for OpenVMS
1.2 Inspecting the Distribution Kit
The distribution kit contains the following component kit
files:
o Base components software
- DECnet-Plus for OpenVMS base kit
o Optional software
- OSI remote file operations support kit (FTAM
software)
- OSI applications support kit (OSAK software)
- Virtual Terminal (VT) software kit
For a more detailed list, see Chapter 3.
1-2 Preparing to Install DECnet-Plus for OpenVMS
Preparing to Install DECnet-Plus for OpenVMS
1.2 Inspecting the Distribution Kit
________________________ Note ________________________
Before installing any of the software, read the
DECnet-Plus Planning Guide (included with your DECnet-
Plus for OpenVMS core documentation set). This guide
contains installation planning information, including
namespace planning instructions.
______________________________________________________
1.3 Time Required for Installation and Configuration
The time required to complete the DECnet-Plus installation
and configuration procedures depends on the following:
o Configuration option used (FAST, BASIC, or ADVANCED)
o Optional software installed
o CPU on the system
o Type of distribution media
The time required to install and configure DECnet-Plus
can vary from 30 minutes to 2 hours, depending on the
combination of choices you make from the above list.
1.4 Prerequisite Software and Licenses
Before you can install and configure the software, the
system must have the required operating system software and
license(s).
1.4.1 Software and Licenses
The prerequisites for installing DECnet-Plus for OpenVMS
software are as follows:
o OpenVMS operating system Version 7.0 or 7.1
o One of the available DECnet-Plus licenses
The specific license required on your system is determined
by the functions you want to use:
o Basic function license (DVNETEND) - provides end system
support.
Preparing to Install DECnet-Plus for OpenVMS 1-3
Preparing to Install DECnet-Plus for OpenVMS
1.4 Prerequisite Software and Licenses
o Extended function license (DVNETEXT) for Alpha systems
- provides end system support, DECdts server, cluster
alias, and OSI applications gateways.
o Extended function license (DVNETRTG) for VAX systems
- provides end system support, DECdns server, DECdts
server, cluster alias, and OSI applications gateways.
For the extended function licenses, the TELNET/VT
gateway also requires the Digital TCP/IP Services for
OpenVMS product.
o X.25 license (Alpha systems only) - provides
functionality over a wide area network link.
At least one node of an OpenVMS Cluster system requires the
extended function license to use cluster alias.
1.4.1.1 DECnet and OSI Applications over TCP/IP
If you plan to use the DECnet-Plus over TCP/IP feature,
then TCP/IP software is a prerequisite. Your end system
will be able to operate over TCP/IP if and only if the
TCP/IP product used on your system supports the PATHWORKS
Internet Protocol (PWIP) interface.
The PWIP interface is currently supported by the products
listed below. Contact the vendor for the required versions
of their product.
o Digital TCP/IP Services for OpenVMS
o TCPware
Process Software Corporation
959 Concord Street
Framingham, MA 01701
800-722-7770
info@process.com
o MultiNet for OpenVMS
Cisco Systems, Inc. (formerly TGV, Inc.)
101 Cooper Street
Santa Cruz, CA 95060
408-457-5200
sales@tgv.cisco.com
o PATHway for OpenVMS
1-4 Preparing to Install DECnet-Plus for OpenVMS
Preparing to Install DECnet-Plus for OpenVMS
1.4 Prerequisite Software and Licenses
The Attachmate Corp. (formerly The Wollongong Group,
Inc.)
1129 San Antonio Road
Palo Alto, California 94303
800-872-8649 (800-962-8649 in CA)
sales@twg.com
________________________ Note ________________________
For more information on using DECnet over TCP/IP or
the OSI applications over TCP/IP, refer to the DECnet-
Plus for OpenVMS Network Management guide.
______________________________________________________
1.4.2 Checking Licenses
To determine the OpenVMS operating system version number,
enter the following DCL command:
$ show system <Return>
To determine whether a DECnet-Plus license is registered,
enter the following DCL command:
$ show license dvnet* <Return>
If the system does not have the required license(s),
obtain the Product Authorization Key (PAK) and register
the license. For instructions on registering a license,
refer to the OpenVMS License Management Utility Manual.
1.5 System Requirements
Before you install the DECnet-Plus for OpenVMS
software, make sure that your system meets the following
requirements.
1.5.1 Disk Space
If this is the first time you are installing DECnet-Plus on
a particular system, ensure that you have enough free space
on the system disk. You need enough space to install the
DECnet-Plus Base components and any options you select.
If you already have DECnet-Plus installed, you need
considerably less free space for the installation because
the earlier installation allocated most of the space that a
subsequent installation needs.
Preparing to Install DECnet-Plus for OpenVMS 1-5
Preparing to Install DECnet-Plus for OpenVMS
1.5 System Requirements
Required Disk Space - Base Components
The total amount of disk space required to install the
software for base components is 77,000 blocks for VAX
systems and 85,000 blocks for Alpha systems.
Disk Space - Optional Software
Table 1-1 shows the amount of disk space needed to install
the optional software. Make sure you have enough free
space to install the required software and the optional
software.
Table_1-1_Disk_Space_Requirements_-_Optional_Software______
Blocks for
Component__________Alpha____________Blocks_for_VAX_________
DECdts server 1400 1800
DECdns server N/A 3000[1]
VAX P.S.I. N/A 7000
VAX WANDD N/A 5500
X.25 12144 N/A
FTAM 28000 12000
Virtual Terminal 4000 2000
OSAK 6900 6000
[1]Approximate_amount_-_actual_amount_depends_on_the_size__
of the namespace, the number of logs created, and so forth.
The amount of required disk space could double when running
tests, then return to original amount when duplicate files
are deleted.
___________________________________________________________
To find out how many free blocks exist on the system disk,
enter the following command:
$ show device sys$sysdevice <Return>
If the number of required blocks exceeds the number of free
blocks, you must clear space on the system disk.
1-6 Preparing to Install DECnet-Plus for OpenVMS
Preparing to Install DECnet-Plus for OpenVMS
1.5 System Requirements
1.5.2 Required Memory
The minimum amount of memory required is 24 MB for VAX
systems and 64 MB for Alpha systems.
To check memory on your system, enter the following
command:
$ show memory/full <Return>
1.5.3 Required System Parameters
This section provides information about the system
parameters, their values, and how to modify them.
Table 1-2 lists the minimum system parameters required for
the base software.
Table 1-2 Minimum System Parameters Required - Base
__________Software_Installation____________________________
Minimum
Value for Minimum Value
Parameter__________________Alpha_______for_VAX_____________
MIN_GBLSECTIONS 512 400
MIN_GBLPAGES 100000 60000
MIN_GBLPAGFIL 1024 4096
MIN_CLISYMTBL 750 500
MIN_KSTACKPAGES 2 N/A
MIN_VIRTUALPAGES___________N/A_________35000_______________
To check these parameters, invoke the SYSGEN utility and
enter the following command:
$ mcr sysgen
SYSGEN> show gblsections
If any of the system parameters need to be modified, follow
these steps:
1. Edit the modparams.dat file by entering:
$ edit sys$system:modparams.dat
Preparing to Install DECnet-Plus for OpenVMS 1-7
Preparing to Install DECnet-Plus for OpenVMS
1.5 System Requirements
2. Enter the values into the file in the following format:
SCSSYSTEMID=65187
SCSNODE="SUPER1"
MIN_GBLSECTIONS=512
.
.
.
MIN_GBLPAGFIL=1024
3. Exit from the editor.
4. Run AUTOGEN by entering the following command:
$ @sys$update:autogen getdata reboot
________________________ Note ________________________
Run AUTOGEN to ensure that your system is tuned with
the appropriate parameters.
______________________________________________________
1.5.3.1 SYSGEN Parameters for OpenVMS Cluster Members
When installing DECnet-Plus for OpenVMS on an OpenVMS
Cluster, make sure that all cluster members have the
suggested SYSGEN parameters set correctly. If a node in
the cluster does not have the required minimum parameters,
startup of the network will fail. If the network fails
to start for this reason, the logical NET$STARTUP_STATUS
is set to OFF-AUTOGENREQ. Set the parameters to the
recommended values before you run net$configure.
1.6 Privileges and Rights Identifiers
Digital recommends that you install and configure DECnet-
Plus from the SYSTEM account. If you are configuring from
another account, make sure the account has the following
privileges and rights identifiers in place before you
begin.
Required account privileges are as follows:
o CMKRNL
o NETMBX
o SYSPRV
1-8 Preparing to Install DECnet-Plus for OpenVMS
Preparing to Install DECnet-Plus for OpenVMS
1.6 Privileges and Rights Identifiers
o TMPMBX
o OPER
o SYSNAM
o WORLD
________________________ Note ________________________
The account cannot have the locked password (LOCKPWD)
flag set.
______________________________________________________
Required rights identifiers are as follows:
o NET$MANAGE
o NET$SECURITY
o NET$REGISTERDNSOBJECT
________________________ Note ________________________
If your account has the BYPASS privilege, then you do
not need to grant these rights identifiers.
______________________________________________________
1.7 Backing Up the System Disk
Use the OpenVMS BACKUP utility to make a copy of the system
disk.
1.8 Notifying Users
Inform users on the system that you plan to install a
product and that they must log out.
Use the reply/all command and be sure to indicate the exact
time you plan to begin running the POLYCENTER Software
Installation utility. For example:
$ set logins/interactive=0
$ reply/all "Installing software at 18:00; Please log out."
If possible, give users an estimated time when they will be
able to log in to the system.
Preparing to Install DECnet-Plus for OpenVMS 1-9
2
_________________________________________________________________
Pre-Installation Tasks
Before installing the software, complete the installation
planning checklist in this chapter. This ensures that you
have the information you need to complete the installation
and configuration in the minimum amount of time. In
addition to identifying necessary information and directing
you to sources of help, the checklist also assists you in
choosing optional software.
2.1 Information Required to Complete the Installation Planning
Checklist
Determine the following information before you begin
the installation and configuration procedure. Enter this
information on your installation planning checklist:
o System's full name (you may have a DECdns full name, a
Local namespace full name, and a fully qualified host
name for the Domain Name System [DNS/BIND])
o Node synonym
o Phase IV-compatible address to interface with Phase IV
nodes
o Phase IV prefix
o Network address
2.2 Installation Planning Checklist
Complete the checklist in Table 2-1 before continuing with
the installation process.
Pre-Installation Tasks 2-1
Pre-Installation Tasks
2.2 Installation Planning Checklist
Table_2-1_Installation_Planning_Checklist__________________
Question_____________________Yes__No___For_More_Information
Have you backed up your < > < >
system disk?
If not, then do so before
you start the installation.
___________________________________________________________
Will the system get network < > < > See Section 6.2
addresses from a DECdns
name server?
If yes, what is the
system's DECdns node
name (for example,
ACME:.BOSTON)?
___________________________________________________________
Will the system store < > < > See Section 6.2
network addresses in a
Local database?
If yes, what is the
system's Local node
name (for example,
LOCAL:.BOSTON)?
___________________________________________________________
Is TCP/IP installed on the < > < > See Section 6.2
system? Will the system
store network addresses in
the DNS/BIND database?
If yes, what is the
system's DNS/BIND name (for
example, BOSTON.ACME.COM)?
___________________________________________________________
What is the system's node See Section 6.2.4
synonym (for example,
BOSTON)?
(continued on next page)
2-2 Pre-Installation Tasks
Pre-Installation Tasks
2.2 Installation Planning Checklist
Table_2-1_(Cont.)_Installation_Planning_Checklist__________
Question_____________________Yes__No___For_More_Information
___________________________________________________________
Will the system communicate < > < > See Section 6.2.5
with Phase IV nodes? and Section 6.2.6
o Phase IV-compatible
address (for example,
2.38)
o Phase IV Prefix (the
default is 49::)
___________________________________________________________
Will the system < > < > See Section 6.2.7
autoconfigure its network
addresses?
If not, you'll need network
entity titles (for example,
47:24:02-01-0A-04:08-00-2B-93-ED-99:00).
___________________________________________________________
Do you want to install < > < > Refer to the DECnet-
DECdts server software? Plus Planning Guide.
___________________________________________________________
(continued on next page)
Pre-Installation Tasks 2-3
Pre-Installation Tasks
2.2 Installation Planning Checklist
Table_2-1_(Cont.)_Installation_Planning_Checklist__________
Question_____________________Yes__No___For_More_Information
(For VAX only.) Do you < > < > Refer to the DECnet-
want to install VAX WANDD Plus for OpenVMS
software for VAX? Applications
You must install this Installation
software if you want to and Advanced
use any of the following: Configuration guide.
- Non-LAN connections to
the network
- Routing over synchronous
connections
- X.25 software over
synchronous lines
___________________________________________________________
(For Alpha only.) Do < > < > Refer to the DECnet-
you want to install X.25 Plus for OpenVMS
software for Alpha? Applications
You must install this Installation
software if you want to and Advanced
use any of the following: Configuration guide.
- X.25 communications via
DEC X25gateway
- X.25 communications via
X.25 Multihost
- X.25 communications
on local system (X.25
Native)
- LAN X.25 (LLC Class 2)
- DECnet over X.25
___________________________________________________________
(continued on next page)
2-4 Pre-Installation Tasks
Pre-Installation Tasks
2.2 Installation Planning Checklist
Table_2-1_(Cont.)_Installation_Planning_Checklist__________
Question_____________________Yes__No___For_More_Information
Do you want to install < > < > Refer to the DECnet-
DECnet-Plus for OpenVMS Plus for OpenVMS
OSAK software? Applications
If you plan to use an OSI Installation
application such as FTAM or and Advanced
Virtual Terminal, you must Configuration guide.
install this software.
___________________________________________________________
Do you want to install < > < > Refer to the DECnet-
DECnet-Plus for OpenVMS Plus for OpenVMS
FTAM software? Applications
If you plan to copy files Installation
to and from other OSI- and Advanced
compliant systems or Configuration guide.
manage such files, you
must install this software.
___________________________________________________________
Do you want to install < > < > Refer to the DECnet-
DECnet-Plus for OpenVMS Plus for OpenVMS
Virtual Terminal (VT) Applications
software? Installation
If you plan to support and Advanced
remote logins and access Configuration guide.
to remote applications on
OSI-compliant systems, you
must_install_this_software.________________________________
Pre-Installation Tasks 2-5
3
_________________________________________________________________
Installing DECnet-Plus for OpenVMS
The DECnet-Plus for OpenVMS distribution software is
provided on compact disc (CD-ROM). The software consists
of the following components:
Components for Alpha Systems
o Base Components
- DECnet-Plus for OpenVMS base kit
- DECdts server
o Optional Components (included with the base kit but must
be installed separately)
- FTAM
- Virtual Terminal (VT)
- OSAK
o X.25 for Alpha (requires a separate license)
Components for VAX Systems
o Base Components
- DECnet-Plus for OpenVMS base kit
- VAX P.S.I.
- WANDD for VAX
- DECdns server
- DECdts server
o Optional Components (included with the base kit but must
be installed separately)
- FTAM
- VT
Installing DECnet-Plus for OpenVMS 3-1
Installing DECnet-Plus for OpenVMS
- OSAK
3-2 Installing DECnet-Plus for OpenVMS
Installing DECnet-Plus for OpenVMS
________________________ Note ________________________
The DECnet-Plus base components, FTAM, OSAK, and VT,
are all packaged as separate installation kits on
the distribution medium. They are usually located
in the same directory. The X.25 for OpenVMS Alpha
kit, however, is a separately licensed product
and as such is in a different directory on the
distribution medium. Consult the documentation with
your distribution medium for the location of the kits
you desire.
______________________________________________________
Use the POLYCENTER Software Installation utility to install
the base components and any combination of optional
components. See Appendix A for information on using the
DCL interface with the POLYCENTER Software Installation
utility.
3.1 Recommended Order for Installing Software
The following sections describe the order in which you
should install the DECnet-Plus for OpenVMS software for
either an Alpha or VAX system.
3.1.1 Installing DECnet-Plus for an OpenVMS Alpha System
If you choose to install all the software products
at the same time, install and configure the OpenVMS
operating system and layered products in the following
order, referring to the appropriate documentation. For a
quick reference, see Figure 3-1. After OpenVMS has been
installed, perform the following steps:
1. Inspect the distribution kit.
2. Verify that all prerequisite software and licenses are
installed.
Refer to the OpenVMS system documentation set.
3. Shut down all network-related applications and tell
users to log out.
4. Install DECnet-Plus for OpenVMS.
See Section 3.2.
Installing DECnet-Plus for OpenVMS 3-3
Installing DECnet-Plus for OpenVMS
3.1 Recommended Order for Installing Software
5. Set the system parameters.
6. Reboot the system.
7. Install X.25 for OpenVMS Alpha and WANDD, if necessary.
Refer to the DECnet-Plus for OpenVMS Applications
Installation and Advanced Configuration guide.
8. Configure DECnet-Plus for OpenVMS. First, see Chapter 4
to determine which configuration option to choose: FAST,
BASIC, or ADVANCED.
For a FAST configuration, see Chapter 5. For a
BASIC configuration, see Chapter 6. For an ADVANCED
configuration, refer to the DECnet-Plus for OpenVMS
Applications Installation and Advanced Configuration
guide.
9. Configure X.25 for OpenVMS Alpha.
Refer to the DECnet-Plus for OpenVMS Applications
Installation and Advanced Configuration guide.
10.Install and configure the OSI Applications (FTAM, VT,
OSAK).
Refer to the DECnet-Plus for OpenVMS Applications
Installation and Advanced Configuration guide.
3-4 Installing DECnet-Plus for OpenVMS
Installing DECnet-Plus for OpenVMS
3.1 Recommended Order for Installing Software
Figure 3-1 Installation and Configuration Flowchart (Alpha
Only)
Installing DECnet-Plus for OpenVMS 3-5
Installing DECnet-Plus for OpenVMS
3.1 Recommended Order for Installing Software
3.1.2 Installing DECnet-Plus for a VAX System
If you choose to install all the software products
at the same time, install and configure the OpenVMS
operating system and layered products in the following
order, referring to the appropriate documentation. For a
quick reference, see Figure 3-2. After OpenVMS has been
installed, perform the following:
1. Inspect the distribution kit.
2. Verify that all prerequisite software and licenses are
installed.
Refer to the OpenVMS system documentation set.
3. Shut down all network-related applications and tell
users to log out.
4. Install DECnet-Plus for OpenVMS.
See Section 3.2.
________________________ Note ________________________
If you want to install VAX P.S.I., select the option
now while installing DECnet-Plus for OpenVMS.
______________________________________________________
5. Set the system parameters.
6. Reboot the system.
7. Configure DECnet-Plus for OpenVMS. First, review
Chapter 4 to determine which configuration option to
choose: FAST, BASIC, or ADVANCED.
For a FAST configuration, see Chapter 5. For a
BASIC configuration, see Chapter 6. For an ADVANCED
configuration, refer to the DECnet-Plus for OpenVMS
Applications Installation and Advanced Configuration
guide.
8. Configure VAX P.S.I.
Refer to the DECnet-Plus for OpenVMS Applications
Installation and Advanced Configuration guide.
9. Install and configure the OSI applications (FTAM, VT,
OSAK).
3-6 Installing DECnet-Plus for OpenVMS
Installing DECnet-Plus for OpenVMS
3.1 Recommended Order for Installing Software
Refer to the DECnet-Plus for OpenVMS Applications
Installation and Advanced Configuration guide.
Installing DECnet-Plus for OpenVMS 3-7
Installing DECnet-Plus for OpenVMS
3.1 Recommended Order for Installing Software
Figure 3-2 Installation and Configuration Flowchart (VAX
Only)
3.2 Installing DECnet-Plus Using the POLYCENTER Software
Installation Utility
This section describes the steps for installing DECnet-Plus
software using the POLYCENTER Software Installation utility
(for more information on this utility, see Appendix A).
You must have SYSPRV privileges on the local or remote node
where you want to run this utility.
3.2.1 Sample DECnet-Plus for OpenVMS Alpha Installation
To start the installation, follow these steps:
1. Log in to the SYSTEM account.
2. Mount the software CD-ROM. Refer to the OpenVMS Layered
Products Compact Disc User's Guide for instructions on
mounting and removing a compact disc.
3. Enter the following command, substituting the name of
your device for the devicename parameter:
$ product install decnet_osi /source=devicename:[dnvosi071.kit]
You are then prompted for installation information as in
the following example. In this example, numbered callouts
(1, 2, 3, . . . ) guide you through the sequence of steps
that require your response. For Alpha systems, you will see
AXPVMS as product information on your screen.
The following product has been selected:
DEC AXPVMS DECNET_OSI V7.1 [Available]
1 Do you want to continue? [YES] <Return>
DEC AXPVMS DECNET_OSI V7.1: DECnet-Plus V7.1 for OpenVMS AXP
Copyright � Digital Equipment Corporation 1996. All rights reserved.
Digital Equipment Corporation
3-8 Installing DECnet-Plus for OpenVMS
Installing DECnet-Plus for OpenVMS
DECnet-Plus Using the POLYCENTER Software Installation Utility
This product requires one of two PAKS: DVNETEND or DVNETEXT.
2 Do you want the defaults for all product options? [YES] <Return>
3 Do you want to view the options? [NO] <Return>
Execution phase starting ...
The following product will be installed:
DEC AXPVMS DECNET_OSI V7.1
Portion Done: 0%...10%...20%...30%...40%...50%...80%...90%...100%
The following product has been installed:
DEC AXPVMS DECNET_OSI V7.1
1 At this point, you can stop the installation process.
If you want to continue, press Return. If you want to
stop, type NO, then press Return.
2 This question allows you to select which optional parts
of the DECnet-Plus product you want to install. If you
want to install just the base software, press Return.
If you want to select the optional software, type NO
and press Return. The procedure then displays a list of
choices for you.
3 This question allows you to review and change your
current selections. Type YES if you are satisfied with
the current selected options. Type NO if you want to
make changes.
3.2.2 Sample DECnet-Plus for OpenVMS VAX Installation
To start the installation, follow these steps:
1. Log in to the SYSTEM account.
2. Mount the software CD-ROM. Refer to the OpenVMS Layered
Products Compact Disc User's Guide for instructions on
mounting and removing a compact disc.
3. Enter the following command, substituting the name of
your device for the devicename parameter:
$ product install decnet_osi /source=devicename:[dnvosi071.kit]
Installing DECnet-Plus for OpenVMS 3-9
Installing DECnet-Plus for OpenVMS
3.2 Installing DECnet-Plus Using the POLYCENTER Software Installation Utility
The installation prompts you for information as in the
following example. In this example, numbered callouts (1,
2, 3, . . . ) guide you through the sequence of steps that
require your response. For VAX systems, you will see DEC
VAXVMS as product information on your screen.
The following product has been selected:
DEC VAXVMS DECNET_OSI V7.1 [Available]
1 Do you want to continue? [YES] <Return>
DEC VAXVMS DECNET_OSI V7.1: DECnet-Plus V7.1 for OpenVMS VAX
Copyright � Digital Equipment Corporation 1996. All rights reserved.
Digital Equipment Corporation
This product requires one of two PAKS: DVNETEND or DVNETRTG.
2 Do you want the defaults for all product options? [YES] <Return>
3 Do you want to view the options? [NO] y <Return>
DEC VAXVMS DECNET_OSI V7.1: DECnet-Plus V7.1 for OpenVMS VAX
DEC VAXVMS VMS V7.1 [Available]
VAX P.S.I. or P.S.I. Access software: NO
VAX Wide Area Device Drivers: NO
DECdns Server software: NO
DECdts Server software: NO
Are you satisfied with these options? [YES] <Return>
Execution phase starting ...
The following product will be installed:
DEC VAXVMS DECNET_OSI V7.1
Portion Done: 0%...10%...20%...30%...40%...80%...90%...100%
The following product has been installed:
DEC VAXVMS DECNET_OSI V7.1
1 At this point, you can stop the installation process.
If you want to continue, press Return. If you want to
stop, type NO, then press Return.
3-10 Installing DECnet-Plus for OpenVMS
Installing DECnet-Plus for OpenVMS
DECnet-Plus Using the POLYCENTER Software Installation Utility
2 This question allows you to select which optional parts
of the DECnet-Plus product you want to install. If you
want to install just the base software, press Return.
If you want to select the optional software, type NO
and press Return. (For example, if you want to configure
wide area devices such as WANDD, X.25, or P.S.I, answer
NO to this question. The procedure then displays a list
of choices for you.)
3 This question allows you to review and change your
current selections. Type YES if you are satisfied with
the current selected options. Type NO if you want to
make changes.
3.3 Files Installed on Your System
The DECnet-Plus installation procedure installs a number
of files on your system. To list the files, enter the
following command:
$ product show object /product=decnet_osi
Installing DECnet-Plus for OpenVMS 3-11
Part II
_________________________________________________________________
DECnet-Plus for OpenVMS BASIC Configuration
Part II describes how to configure DECnet-Plus for OpenVMS
using the FAST and BASIC configuration options.
It includes the following chapters:
o Chapter 4 - Configuration Options
o Chapter 5 - Using the FAST Configuration Option
o Chapter 6 - Using the BASIC Configuration Option
o Chapter 7 - Managing Name Services
4
_________________________________________________________________
Configuration Options
This chapter explains the three configuration options you
can use to configure your system for DECnet-Plus. These
configuration options enable you to configure the DECnet-
Plus for OpenVMS base components so that the system becomes
a DECnet-Plus end system on a network.
The procedure you use to configure your system for DECnet-
Plus is sys$manager:net$configure.com. You can use any of
the following net$configure configuration options:
o FAST configuration option (Chapter 5)
The FAST configuration allows you to quickly upgrade
a non-clustered system from DECnet Phase IV to DECnet
Phase V.
o BASIC configuration option (Chapter 6)
The BASIC configuration allows you to configure your
system for DECnet-Plus by answering a few questions and
using the default answers on others.
o ADVANCED configuration option (DECnet-Plus for OpenVMS
Applications Installation and Advanced Configuration
guide)
The ADVANCED configuration allows you to customize your
system's network configuration.
This chapter presents additional information about the
following topics:
o Selecting a configuration option
o Running net$configure
See Section 1.6 for a list of account privileges you need
to run net$configure.
Configuration Options 4-1
Configuration Options
4.1 Selecting a Configuration Option
4.1 Selecting a Configuration Option
If you installed the required software, you can configure
your system using the net$configure configuration option
for the FAST configuration, using the net$configure basic
configuration option for the BASIC configuration, or using
the net$configure advanced configuration option for the
ADVANCED configuration.
Table 4-1 provides some guidelines for making your
configuration choice.
If you choose to use either the FAST configuration option
or the BASIC configuration option, continue with this
section. If you prefer to customize your system's network
configuration with the ADVANCED configuration option, refer
to the DECnet-Plus for OpenVMS Applications Installation
and Advanced Configuration guide.
4-2 Configuration Options
Configuration Options
4.1 Selecting a Configuration Option
Table_4-1_Choosing_Your_Configuration_Option_____________________
Option..._Choose_if...___________________________________________
FAST You are upgrading from a DECnet Phase IV node and you
plan to use the existing Phase IV configuration.
The node is not in a cluster.
You are running the configuration procedure for the
first time.
_________________________________________________________________
BASIC The node is in a cluster.
You are upgrading or reconfiguring DECnet-Plus.
You need to access a DECdns server for network
addresses.
You want to run DECnet over TCP/IP (RFC 1859) and/or
OSI applications over TCP/IP (RFC 1006).
You only have one communications device, or you
have multiple devices, all of which will be used for
DECnet-Plus communications.
You want to use the default names for all devices and
routing circuits.
You want to autoconfigure your network addresses only.
You want to configure both the NSP and OSI transports
and only want to create default OSI templates. You want
to enable both DECnet over TCP/IP or OSI applications
over TCP/IP.
You do not want to enable FDDI large packet support (if
you have an FDDI-type circuit).
You want to set the routing characteristic DNA
Address Format to TRUE (this attribute controls the
interpretation of address structuring).
You want to use integrated mode routing.
_________________________________________________________________
(continued on next page)
Configuration Options 4-3
Configuration Options
4.1 Selecting a Configuration Option
Table_4-1_(Cont.)_Choosing_Your_Configuration_Option_____________
Option..._Choose_if...___________________________________________
ADVANCED Your configuration is complex.
You need to customize your network's configuration.
Your system has multiple communication devices, and you
want them to run a mix of protocols.
You want to configure a cluster with both DECnet Phase
IV and DECnet Phase V nodes.
You want the option to give specific names to all
devices and routing circuits. You also want the option
of not configuring all of your devices for DECnet-Plus.
You want the option of manually entering your network
addresses.
You want to configure either the NSP transport or
the OSI transport (or both). You want the option
to create additional OSI templates. You want the
option of enabling/disabling DECnet over TCP/IP or
OSI applications over TCP/IP.
You want the option of enabling FDDI large packet
support (if you have an FDDI-type circuit).
You want the option of setting the routing
characteristic DNA Address Format to TRUE or FALSE
(to control the interpretation of address structuring).
You want the option of using either integrated mode
routing or segregated mode routing.
You want the option to provide default accounts for
__________FAL.___________________________________________________
4.2 How to Run NET$CONFIGURE
The net$configure.com procedure configures the DECnet-Plus
for OpenVMS software. This command creates or modifies
the Network Control Language (NCL) scripts required to run
DECnet-Plus for OpenVMS on your node.
The net$configure.com procedure is an interactive procedure
that displays a series of questions. After each question,
the default response, if there is one, appears in brackets
4-4 Configuration Options
Configuration Options
4.2 How to Run NET$CONFIGURE
([ ]). At the end of each question, a colon (:) appears.
Respond in one of the following ways:
o To get help after a question, type a question mark (?).
After the help display, the same question reappears.
o To select the default response, press Return.
o To enter information, type it immediately after the
colon or question mark; then press Return.
o Type Y for YES and N for NO.
o To terminate the procedure, press Ctrl/Y.
If you execute net$configure.com without specifying BASIC
or ADVANCED, the BASIC configuration option is invoked by
default.
________________________ Note ________________________
If you are running the configuration procedure for
the first time on a system that was previously
configured for Phase IV and you do not specify
BASIC or ADVANCED, the initial default is the FAST
configuration procedure.
However, the FAST configuration procedure can only
be run once on a system, and after that the BASIC
configuration procedure automatically becomes the
default.
______________________________________________________
To invoke net$configure.com with the default BASIC option,
enter the following:
$ @sys$manager:net$configure
4.2.1 Local and Global Symbols
The net$configure.com procedure deletes all of your local
and global symbols at the beginning of the procedure in
order to free the symbol table. This happens because
net$configure.com creates and uses a large number of
symbols. If the symbols were not deleted at the beginning
of the procedure, net$configure would often run out of
symbol table space to use while configuring the system.
Configuration Options 4-5
Configuration Options
4.2 How to Run NET$CONFIGURE
4.2.2 Running the Procedure from Different Processes
Although net$configure.com can be run simultaneously
on different nodes in a cluster, it should not be run
simultaneously from different processes on the same node.
4-6 Configuration Options
5
_________________________________________________________________
Using the FAST Configuration Option
This chapter describes how to configure the DECnet-Plus for
OpenVMS base components using the FAST configuration option
so that the system becomes a DECnet-Plus for OpenVMS end
system on a network.
________________________ Note ________________________
If you have already run the FAST configuration
procedure once on your system, the configuration
procedure automatically defaults to the BASIC
configuration procedure.
______________________________________________________
5.1 Invoking the FAST Configuration Option
To invoke the net$configure.com procedure using the FAST
configuration option, enter the following command:
$ @sys$manager:net$configure <Return>
The procedure starts:
Copyright (c) Digital Equipment Corporation 1996. All rights reserved.
DECnet-Plus for OpenVMS network configuration procedure
This procedure will help you create or modify the management scripts
needed to operate DECnet on this machine. You may receive help about
most questions by answering with a question mark '?'.
%NET$CONFIGURE-I-SETUPNEW, setting up for new configuration
%NET$CONFIGURE-I-PHASEIVDATA, Phase IV DECnet database found
FAST CONFIGURATION OPTION
Using the FAST Configuration Option 5-1
Using the FAST Configuration Option
5.1 Invoking the FAST Configuration Option
You have the option of using the existing Phase IV information
to quickly configure DECnet-Plus. This provides full network access
and uses a local file to hold naming information. Very few questions
will be asked.
If you want to use the fast configuration option, answer YES to the next
question.
If you are running a DNS Server on this system, or plan to run a DNS
Server on this system, you *must* answer NO to the next question.
If you want more flexibility when configuring DECnet-Plus, also answer
NO.
Answering NO will cause some additional questions to be asked
regarding configuration.
* Do you want the fast default configuration? [YES] : <Return>
Press Return to continue with the FAST configuration
option.
The procedure informs you that the Phase IV database
conversion has completed.
%NET$CONFIGURE-I-PHASEIVCOMPL, Phase IV database conversion complete
Determining DTSS timezone rules from OpenVMS information...
%NET$CONFIGURE-I-CREDEFOSITEMPLATE, created default OSI templates
%NET$CONFIGURE-I-EVDDEFAULT, providing default Event Dispatcher configuration
%NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account CML$SERVER
Summary of Configuration
Node Information:
Node Type: ENDNODE
Directory Services Chosen: LOCAL
Primary Directory Service: LOCAL
Node Synonym: NCLGUI
Phase IV Address: 4.260
Phase IV Prefix: 49::
Autoconfiguration of Network Addresses: Enabled
Session Control Address Update Interval: 10
Routing ESHello Timer: 600
Device Information:
Device: EWA (TULIP):
Data Link name: EWA-0
Routing Circuit Name: EWA-0
5-2 Using the FAST Configuration Option
Using the FAST Configuration Option
5.1 Invoking the FAST Configuration Option
Transport Information:
NSP Transport: Configured
Maximum number of logical links: 200
Maximum Transmit and Receive Window: 20
Maximum Receive Buffers: 4000
Congestion Avoidance Disabled
Event Dispatcher Configuration:
Sinks: local_sink
Outbound Streams: local_stream
Phase IV Relay: Enabled
* Do you want to apply this configuration? [YES] : <Return>
Answer YES to apply this configuration. If you answer
NO, the procedure defaults to the BASIC configuration
procedure.
If you answer YES, the following message displays:
%NET$CONFIGURE-I-CHECKSUM, checksumming NCL management scripts
* Do you want to start the network? [YES] : <Return>
Answer YES if you want to start the network and complete
your system's network configuration.
If you want to postpone starting the network, answer NO.
When you answer NO, the procedure displays the following
message:
********************************************************************
You have decided not to start the network. NET$CONFIGURE.COM
cannot complete your system's network configuration since it needs
the network to be partially started in order to perform certain
operations. As a result, your system may be left in an inconsistent
state if you try to startup the network manually or if you decide
to reboot your system.
Once you are ready to start the network, please invoke the
NET$CONFIGURE.COM procedure, choose menu Option 2 (Change node
name/namespace name), and respond YES to starting the network so
that the configuration procedure can finish your system's network
configuration.
********************************************************************
Network Startup Incomplete
Using the FAST Configuration Option 5-3
Using the FAST Configuration Option
5.1 Invoking the FAST Configuration Option
Digital recommends that you answer YES and start the
network.
When you choose to start the network, the procedure
displays information similar to the following:
Copyright (c) Digital Equipment Corporation 1996. All rights reserved.
.
.
.
%NET$STARTUP-I-OPERSTATUS, DECnet-Plus for OpenVMS operational status is
RUNNING-MAJOR
sys$manager:net$dns_clerk_startup.ncl changed to use the new default namespace.
Your default namespace nickname is ACME.
Your default namespace NSCTS is 08-00-2B-0D-2E-89-23-5B-15-9E-F1-85-95-00.
Node 0
at 1995-05-26-14:12:24.170-04:00I0.404
%NET$CONFIGURE-I-NODERENAMED, node successfully renamed to ACME:.WABBIT.ELMER
Directory Service: DECdns
You can ignore the Error - Node name lookup failure message
during startup.
Error - Node name lookup failure
ACME:.WABBIT.ELMER
Number of nodes reported on: 0
%NET$CONFIGURE-W-NODENOTREG, node is not completely registered yet in the
DECdns directory service
Directory Service: Local name file
Error - Node name lookup failure
LOCAL:.ELMER
Number of nodes reported on: 0
%NET$CONFIGURE-W-NODENOTREG, node is not completely registered yet in the
LOCAL directory service
%NET$CONFIGURE-I-IMPORTFILECREATED, created the DECNET_REGISTER import file
Directory Service: DECdns
5-4 Using the FAST Configuration Option
Using the FAST Configuration Option
5.1 Invoking the FAST Configuration Option
Updating nodes listed in SYS$MANAGER:DECNET_REGISTER_IMPORT_FILE_ELMER.TXT
Number of nodes registered: 1
Number of nodes modified: 0
%NET$CONFIGURE-I-REGSUCCESS, node has been successfully registered in the
DECdns directory service
Directory Service: Local name file
Updating nodes listed in SYS$MANAGER:DECNET_REGISTER_IMPORT_FILE_ELMER.TXT
Number of nodes registered: 1
Number of nodes modified: 0
%NET$CONFIGURE-I-REGSUCCESS, node has been successfully registered in the
LOCAL directory service
Node 0
at 1995-05-26-14:13:25.980-04:00I0.411
%NET$CONFIGURE-I-NODERENAMED, node successfully renamed to
ACME:.WABBIT.ELMER
Node 0 Session Control Tower Maintenance ACME:.WABBIT.ELMER
at 1995-05-26-14:13:35.360-04:00I0.411
%NET$CONFIGURE-I-TOWERSUPDATED, updated address towers for node
Node 0 Session Control Backtranslation Softlink *
at 1995-05-26-14:13:43.360-04:00I0.412
Node 0 Session Control Backtranslation Softlink *
at 1995-05-26-14:13:43.370-04:00I0.412
%NET$CONFIGURE-I-BCKTRNUPDATED, updated backtranslation softlink for node
%NET$CONFIGURE-I-CONFIGCOMPLETED, DECnet-Plus for OpenVMS configuration
completed
$
You have just completed the initial configuration of
a DECnet-Plus for OpenVMS system. It should now be
operational as an end system on the network.
See Figure 3-1 and Figure 3-2 to determine your next
step. According to the flowcharts, you have just completed
configuring the base components.
Using the FAST Configuration Option 5-5
Using the FAST Configuration Option
5.2 Changing a Current DECnet-Plus System Configuration
5.2 Changing a Current DECnet-Plus System Configuration
You can use the net$configure procedure to modify the
current configuration. Depending on which menu option you
select, net$configure either modifies the configuration
automatically or produces modified NCL scripts that you can
use to modify the system's configuration.
See Chapter 4 to determine whether you want to use the
BASIC or ADVANCED configuration option to change your
configuration. Refer to the DECnet-Plus for OpenVMS
Applications Installation and Advanced Configuration for
instructions on how to run the ADVANCED configuration.
5-6 Using the FAST Configuration Option
6
_________________________________________________________________
Using the BASIC Configuration Option
This chapter describes how to configure the DECnet-Plus
for OpenVMS base components using the BASIC configuration
option so that the system becomes a DECnet-Plus for OpenVMS
end system on a network.
The BASIC configuration option allows you to configure your
system by answering a few questions and using the default
answers on others.
If you have already configured the DECnet-Plus for OpenVMS
software and you want to customize the configuration, see
Chapter 4 to determine if you want to use the BASIC or
ADVANCED option.
6.1 Invoking the BASIC Configuration Option
To invoke the net$configure.com procedure using the BASIC
configuration option, enter the following command:
$ @sys$manager:net$configure basic
The procedure starts:
Copyright (c) Digital Equipment Corporation 1993, 1996. All rights reserved.
DECnet-Plus for OpenVMS BASIC network configuration procedure
This procedure will help you create or modify the management scripts
needed to operate DECnet on this machine. You may receive help about
most questions by answering with a question mark '?'.
You have chosen the BASIC configuration option. This option enables
you to quickly configure your system by answering a few questions and
using most of the default answers. If you would rather do some specific
tailoring of your system's network configuration, you should invoke
NET$CONFIGURE.COM with the ADVANCED configuration option, ie:
@SYS$MANAGER:NET$CONFIGURE ADVANCED
* Do you want to continue? [YES] :
Using the BASIC Configuration Option 6-1
Using the BASIC Configuration Option
6.1 Invoking the BASIC Configuration Option
Press Return to continue with the BASIC configuration
option.
The procedure informs you that this is the first time you
are configuring your system to use DECnet-Plus for OpenVMS:
%NET$CONFIGURE-I-SETUPNEW, setting up for new configuration
If a Phase IV database exists on the system, the procedure
displays the following message:
%NET$CONFIGURE-I-PHASEIVDATA, Phase IV DECnet database found
You have the option of using the existing Phase IV database
to generate the Network Control Language (NCL) scripts
and configure the system. If you do not want to use the
existing Phase IV database to generate the NCL scripts
and configure the system, then net$configure configures
the system based on your answers to the configuration
questions.
* Do you want to convert Phase IV database? [YES] :
If you answer YES, the net$configure procedure uses the
system's existing Phase IV database to generate NCL scripts
and configure the system.
If you answer NO, the net$configure procedure does not
use the system's existing Phase IV database to generate
NCL scripts and proceeds to ask all the configuration
questions, starting with the directory services to use
on the system. If you need more information to answer a
question, you can type a question mark (?) at the prompts.
Review the installation planning checklist in Chapter 2
before continuing.
6.2 Directory Name Services
DECnet-Plus provides access to the node name and addressing
information stored in one or more name services. This
release of DECnet-Plus supports the following directory
name services:
o Local namespace - A discrete, nondistributed namespace
that stores name and address information locally in
database files, the Local namespace replaces the DECdns
Local Naming Option (LNO). It also has the ability to
hold 100,000 nodes, and can scale beyond that number.
6-2 Using the BASIC Configuration Option
Using the BASIC Configuration Option
6.2 Directory Name Services
The actual number of nodes that the Local namespace can
hold depends on the space available on your system.
For more detailed information on namespaces, see
Section 7.1.1.
o DECdns distributed namespace - Digital's Distributed
Name Service, DECdns is a distributed, global name
service. For more information, see Section 7.1.2.
o Domain Name System - The Domain Name System (DNS/BIND)
is supported for storage of IP addresses. For more
information, see Section 7.1.3.
If you choose to enter more than one directory name
service for your system, enter them in order of priority.
The ordering of this list is very important: the first
directory service entered in this list is considered the
primary directory service to use on the system. The primary
directory service is considered the first choice to use
when looking up naming information for the system.
Enter an ordered list of the directory services you want
to use on the system. If you enter more than one directory
service, separate each service with a comma.
* Enter the directory services to use on the system [LOCAL,DECDNS,DOMAIN] :
6.2.1 Node Full Name
The DECnet-Plus for OpenVMS configuration procedure
net$configure.com prompts you for the system's full name.
You can enter a DECdns full name, a Local namespace full
name, a fully qualified host name for the Domain Name
System (DNS/BIND), or all three. For DECdns and Local
namespace full names, you must specify a node full name
that includes a namespace nickname (this complies with
DECdns distributed namespace requirements). The full name
format is the same for distributed namespaces and Local
namespaces.
The full name uses the following form:
NamespaceNickname:.DirectoryPath.NodeObject
The following are the guidelines for selecting a full name:
o For DECdns and Local, the node full name must begin with
the namespace nickname and a colon (:). The nickname for
the Local namespace is always LOCAL: (or local:).
Using the BASIC Configuration Option 6-3
Using the BASIC Configuration Option
6.2 Directory Name Services
o For DECdns and Local, the directory path must begin with
a dot (.).
o The full name can be up to 511 characters long: the
namespace nickname can be up to 255 characters, and
the directory path and node object can be up to 255
characters.
o The full name can be any combination of letters, digits,
and certain punctuation characters from the ISO Latin-
1 character set. Some other characters are allowed as
long as they are enclosed in quotation marks. For a list
of all allowable characters, refer to the DECnet-Plus
DECdns Management guide.
o For DNS/BIND, enter a fully qualified IP host name.
The following are some examples of suitable node full
names:
AU:.chemistry$lab.Sunil$Sethi
XYZ_CORP:.sales.east_coast.BrianMacKrill
Mbi:.MIS.Europe.Monaco_headquarters.F_Riviera
local:.bryan
smilee.mass.acme.edu
________________________ Note ________________________
If you plan to use a Local namespace and you are
converting a Phase IV system to DECnet-Plus, Digital
recommends that you use the system's Phase IV node
name in the DECnet-Plus full name (for example,
LOCAL:.PASTRY).
______________________________________________________
You should plan node full names carefully and make sure
they are unique within the namespace. If your network
administrator has not assigned a unique node full name
for your system, be sure to read the DECnet-Plus Planning
Guide before you assign a node name for your system. For
more information on name services, see Chapter 7.
At the prompt, enter a node full name for each directory
service chosen. The node full name is the name of your
system's node object in the directory service. It includes
the namespace nickname and the full list of directories
6-4 Using the BASIC Configuration Option
Using the BASIC Configuration Option
6.2 Directory Name Services
leading to the node object name. Examples of node full
names include:
Local namespace - LOCAL:.TomThumb
DECdns - ACME:.wabbit.Elmer
Domain - elmer.wabbit.acme.edu
For the Local namespace, the namespace nickname LOCAL is
prepended to the full name and is terminated with a colon
(:). The namespace nickname LOCAL means that the Local
namespace is used. The node object name must begin with
a dot (.), and no element of the name (namespace name,
directory, or node object name) can be a null string.
Note that the namespace nickname LOCAL is reserved, and
indicates that the Local namespace is used on this system.
For example, if you enter "Local,DECdns,Domain" at the
previous prompt, you will be asked for a DECdns full name,
a Local full name, and a fully qualified host name for DNS
/BIND.
* Enter the full name for directory service LOCAL : LOCAL:.ELMER
* Enter the full name for directory service DECDNS : ACME:.WABBIT.ELMER
* Enter the fully qualified host name for DNS/BIND : ELMER.WABBIT.ACME.EDU
6.2.2 Specifying the Node Type
Prior to DECnet-Plus Version 7.1, DECnet-Plus systems were
end nodes. Dedicated routers on the network performed
routing functions for the end nodes as necessary. With
the Version 7.1 release, DECnet-Plus allows a system to
run integrated IS-IS, thus providing host-based routing
functionality. The default is to be an end node.
* What type of node (Endnode or Router)? [ENDNODE] :
6.2.3 Specifying Routing Information
This section only applies if your DECnet-Plus system is a
router.
* Type of routing node (L1 or L2)? [L1] :
Enter L1 if your DECnet-Plus system will provide intra-area
level 1 routing capability. Enter L2 if your DECnet-Plus
system will provide inter-area level 2 routing capability.
The default is to be a level 1 router.
Using the BASIC Configuration Option 6-5
Using the BASIC Configuration Option
6.2 Directory Name Services
6.2.4 Node Synonym
The node synonym is an alphanumeric character string
between one and six characters long. The first character
must be an alphabetic character; after the first character,
the string can contain either alphabetic or numeric
characters.
The node synonym is primarily a transition tool that allows
you to use a Phase IV-style node name for your DECnet-
Plus node. Other users can then find your node by using
this synonym rather than your full name. If you were using
DECnet Phase IV, consider using your Phase IV node name
as your synonym. The synonym is required for Phase IV
applications that can only handle Phase IV-style node
names. If your network has only DECnet-Plus or OSI (Open
Systems Interconnection) systems, you may not need a node
synonym.
The default node synonym is the first six characters of
the system's last simple name. The last simple name is
the string that follows the last period of your full
name. For example, if you specify XYZ_CORP:.sales.east_
coast.BrianMacKrill as a node full name, the default node
synonym is BrianM.
If this system had previously been running DECnet Phase IV
software, then you should use the old Phase IV node name as
the synonym. If this system is joining a DECnet network for
the first time, you can use any name for the synonym, as
long as it meets the criteria listed above, and is unique
within the network.
* What is the synonym name for this node? [ELMER] :
For more information on node synonym directories, see
Section 7.4.
6.2.5 Specifying a DECnet Phase IV-Compatible Address
If you want your system to communicate with Phase IV
nodes, you must specify a Phase IV address and a Phase
IV prefix. These will be used to construct a DECnet Phase
IV-compatible address.
6-6 Using the BASIC Configuration Option
Using the BASIC Configuration Option
6.2 Directory Name Services
A DECnet Phase IV-compatible address is a DECnet-Plus
address (NSAP - network service access point) that conforms
to the Phase IV area and node limits; that is, the area
number is from 1 to 63, and the node number is from 1 to
1023.
If there are no Phase IV systems on your network or you do
not want to communicate with Phase IV systems, you do not
need a Phase IV-compatible address. Entering a Phase IV
address of 0.0 at configuration time indicates that this
DECnet-Plus system will not have a Phase IV-compatible
address, and will not communicate with Phase IV nodes.
* Enter PhaseIV Address [15.27] :
Enter the Phase IV address you want to use, or enter 0.0 if
you do not want to communicate with Phase IV nodes.
6.2.6 Specifying a Phase IV Prefix
The net$configure basic configuration option provides 49::
as the default value for the Phase IV prefix. If you do not
enter a Phase IV-compatible address, you will not have a
Phase IV prefix.
6.2.7 Configuring Network Addresses
The net$configure basic configuration option autoconfigures
one network address for you.
6.2.8 DNA Address Format
The net$configure basic configuration sets the routing
characteristic DNA address format to TRUE.
6.3 Configuring Devices
The net$configure procedure checks for network devices on
the system that are supported by net$configure and then
configures them. If the procedure finds that you have WANDD
or X.25 installed but not configured, you will see the
following information:
You have installed wide area device support, but it has not been
configured. You may configure it now if you want.
* Do you want to configure Wide Area devices? [YES] : N
%NET$CONFIGURE-I-SCANCONFIG, scanning device configuration - please wait
Using the BASIC Configuration Option 6-7
Using the BASIC Configuration Option
6.3 Configuring Devices
6.3.1 Configuring an Alpha System
For an Alpha system, the procedure displays the following
information:
DEC X.25 software has been installed on this system. You have
the option of configuring DECnet to run over X.25.
* Do you want to configure DECnet over X.25? [NO] :
Answer YES if you want to configure DECnet over X.25.
If you answer YES, you will see a list of choices for the
type of X.25 circuit to use:
Types of X.25 circuits:
[1] - X.25 Dynamic Assigned (DA)
[2] - X.25 Static Incoming (IN)
[3] - X.25 Static Outgoing (OUT)
[4] - X.25 Permanent (PVC)
* Which type of X.25 circuit do you want to use? : 4
* Routing Circuit Name to use? [X25-PVC-0] :
* Template name? [X25-PVC-0] :
* Configure another X.25 routing circuit for DECnet? [NO] :
Enter the number for the type of circuit you want, then
enter a routing circuit name and a template name to use
for that circuit. If you do not want to configure any other
X.25 routing circuits, press Return for the default. The
configuration procedure continues with the next series of
questions (such as time zone or transports, for example).
If no devices are found on the Alpha system, the procedure
displays the following prompt:
* Should a SYSMAN IO AUTO be executed? :
If you answer YES, the net$configure procedure invokes the
SYSMAN IO AUTO command to find devices on the system. If
you answer NO, there are no devices to configure.
6-8 Using the BASIC Configuration Option
Using the BASIC Configuration Option
6.3 Configuring Devices
6.3.2 Configuring a VAX System
If you answer YES to the question, "Do you want to
configure Wide Area devices?" and you are using a VAX
system, the procedure displays the following information:
* Do you want to configure Wide Area devices? [YES] :
Answer YES if you want to configure DECnet over P.S.I.
If you answer YES, the procedure displays the following:
This is the Configuration Procedure for the
===========================================
VAX Wan Device Drivers for DECnet/OSI for VMS
=============================================
The Wide Area Network Datalinks and Drivers are a prerequisite
for DECnet/OSI. They also provide synchronous datalinks in
systems that do not use DECnet/OSI for networking.
Access to DECnet/OSI datalinks (created by NCL) is possible via
the QIO interface to the WAN pseudo-driver, WANDRIVER. Layered
products that use synchronous devices do not normally require
programming access to WANDRIVER. For further information, see
the "DECnet/OSI for VMS WANDD Programming" guide.
Do you wish to use WANDRIVER [N] ? y
Will you use DEC HDLC [Y] ?
Will you use LAPB/E (VAX P.S.I. requires LAPB/E) [Y] ?
The DSV11 (Q-bus), DIV32 (Q-bus), DSB32 (BI-bus), DSF32 (MI-bus) and
DSW devices are soft-loadable. The WANDD startup procedure will load
the microcode for these devices if required.
Do you have any soft-loadable microcode devices on this system [N] ?
Will you use the VAXft DSF32 device driver [N] ? y
The VAXft DSF32 software supports the pairing of physical
controllers to provide a fault-tolerant configuration. Such a
pairing is called a Failover Set. The DSF32 device does not
automatically create the failover sets, so you will need to pair
controllers using the Failover Set Manager software.
Using the BASIC Configuration Option 6-9
Using the BASIC Configuration Option
6.3 Configuring Devices
This management software can be invoked during system startup
from within the command procedure WANDD$STARTUP_SF.COM, which is
placed in the SYS$STARTUP directory by the kit installation
procedure. If you want to have these Failover Sets automatically
configured when the system starts up you will need to modify
WANDD$STARTUP_SF.COM to include Failover Set Manager commands
that you require.
Are you satisfied with the answers you have given [Y] ?
If you have already started up the WAN Drivers and Datalinks
(that is, if you have already successfully run
SYS$STARTUP:WANDD$STARTUP.COM since your system was last
booted), then you will need to reboot your system for your new
configuration to take effect.
%NET$CONFIGURE-I-SCANCONFIG, scanning device configuration - please wait
* Do you want to configure DECnet over X.25? [NO] : yes
Types of X.25 circuits:
[1] - X.25 Dynamic Assigned (DA)
[2] - X.25 Static Incoming (IN)
[3] - X.25 Static Outgoing (OUT)
[4] - X.25 Permanent (PVC)
* Which type of X.25 circuit do you want to use? : 1
* Routing Circuit Name to use? [X25-DA-0] :
* Template name? [X25-DA-0] :
* Filter name? [X25-DA-0] :
* Do you want to configure any reachable addresses? [NO] :
* Configure another X.25 routing circuit for DECnet? [NO] :
The procedure continues to ask for information. See
Section 6.3.1 for the types of questions you will see and
possible responses you can enter.
If no devices are found on the VAX system, the procedure
displays the following prompt:
* Should a SYSGEN AUTOCONFIGURE ALL be executed? :
If you answer YES, the net$configure procedure invokes
the SYSGEN AUTOCONFIGURE ALL command to find devices on
the system. If you answer NO, there are no devices to
configure.
6-10 Using the BASIC Configuration Option
Using the BASIC Configuration Option
6.4 Configuring Transports
6.4 Configuring Transports
Next, the NSP transport and the OSI transport are
configured.
The procedure displays the following message to indicate
that the default OSI templates have been created:
%NET$CONFIGURE-I-CREDEFOSITEMPLATE, created default OSI templates
The default OSI templates are used by the OSAK and FTAM
installation verification procedures (IVPs) for loopback
testing. You will not be able to use OSI applications
to make connections to other OSI systems unless you use
the net$configure advanced configuration option to create
additional OSI templates. You can do this at a later time.
6.5 Configuring Time Zone Differential Factors
The UTC (Coordinated Universal Time) is calculated
automatically by using the OpenVMS UTC, and the procedure
displays the following message:
Determining DTSS timezone rules from OpenVMS information...
After the initial system configuration, you can choose to
reconfigure the system's time zone rule (TZR) by selecting
Option 5 in the top-level net$configure menu in either the
BASIC or ADVANCED configuration procedure.
6.6 Configuring an Event Dispatcher
The procedure then provides the default Event Dispatcher
configuration:
%NET$CONFIGURE-I-EVDDEFAULT, providing default Event Dispatcher configuration
6.7 Configuring an Application Database
The procedure creates the DECnet-Plus default applications
to include in the application database. The procedure
creates default user accounts for the CML, MAIL, VPM,
MIRROR, and PHONE applications (no account is created for
FAL):
Using the BASIC Configuration Option 6-11
Using the BASIC Configuration Option
6.7 Configuring an Application Database
%NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account CML$SERVER
%NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account MAIL$SERVER
%NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account VPM$SERVER
%NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account MIRRO$SERVER
%NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account PHONE$SERVER
o CMIP Management Listener (CML) is the DECnet-Plus
management module that implements DNA Common Management
Information Protocol (DNA CMIP). CML provides access to
CMIP.
o MAIL allows users to send and receive messages.
o VMScluster Performance Monitor (VPM) needs an account
for your system to support the OpenVMS Monitor utility
command MONITOR CLUSTER.
o MIRROR is needed for particular forms of loopback
testing.
o PHONE allows users on the same or different OpenVMS
systems to communicate interactively.
6.8 Configuring a Cluster Alias
The following steps describe how to configure a cluster
alias.
1. If the node is a OpenVMS Cluster member or if
net$configure finds an alias NCL script on the system,
the procedure prompts you to enter the full name of a
cluster alias.
* Full name of Cluster Alias : ACME:.WABBIT.HELP
If you do not want the node to participate in a cluster
alias, press Return.
If you want the node to participate in a cluster alias,
specify the full name that uniquely identifies the
cluster alias node (for example, ACME:.WABBIT.HELP).
2. If you entered a cluster alias full name in response
to the previous prompt, the procedure displays the
following prompt:
* Cluster Alias Phase IV Address (aa.nnnn OR AA-00-04-00-xx-xx) : 12.139
6-12 Using the BASIC Configuration Option
Using the BASIC Configuration Option
6.8 Configuring a Cluster Alias
Do not use your address for the cluster alias. If you
are unsure which address to enter, consult your network
manager.
Specify either the DECnet Phase IV node address or
Ethernet physical address of the alias.
The Phase IV node address has the format area-
number.node-number (for example, 12.139).
The Ethernet physical address has the format AA-00-
04-00-xx-xx, where xx-xx is calculated from the Phase
IV node address. To determine the Ethernet physical
address, proceed as follows:
a. Convert the Phase IV node address to its decimal
equivalent as follows:
(area-number * 1024) + node-number = decimal equivalent
(For example, (12 * 1024) + 139 = 12427 decimal)
b. Convert the decimal node address to its hexadecimal
equivalent and reverse the order of the bytes to form
the hexadecimal node address. For example:
(12427 decimal = 308B hex, reversed = 8B30 hexnodeaddress)
c. Incorporate the hexadecimal node address in the
following format:
AA-00-04-00-hexnodeaddress
(For example, AA-00-04-00-8B-30)
3. If you entered a cluster alias full name and a Phase IV
address, the procedure displays the following prompt:
* Selection weight for this cluster node [0 for satellites] :
The selection weight determines the number of sequential
incoming connects passed to this alias member node in
the round-robin sequence before proceeding to the next
member node in the sequence. A value of zero means this
node is not eligible to receive incoming connections to
this alias address. Selection weight apportions incoming
alias connections according to the capacity of each
alias member. For example, nodes with greater capacity
should have larger values of selection weight, while
OpenVMS Cluster satellites should generally have a value
of zero. Specify a nonzero selection weight if this node
is connected locally to a dual-ported disk, or if it
Using the BASIC Configuration Option 6-13
Using the BASIC Configuration Option
6.8 Configuring a Cluster Alias
will be serving any multihost disks, such as RFxx or
HSC-connected disks, to other cluster members. Digital
recommends values between 0 and 10.
4. The procedure then displays:
Summary of Configuration
Node Information
Directory Services Chosen: DECDNS,LOCAL,DOMAIN
Primary Directory Service: DECDNS
DECdns Full name: ACME:.WABBIT.ELMER
Local Full name: LOCAL:.ELMER
Fully Qualified
Host name: ELMER.WABBIT.ACME.EDU
Node Synonym: ELMER
Phase IV Address: 15.27
Phase IV Prefix: 49::
Autoconfiguration of Network Addresses: Enabled
Alias Name: ACME:.WABBIT.HELP
Device Information:
Device: ESA0 (DESVA):
Data Link name: CSMACD-0
Routing Circuit Name: CSMACD-0
Transport Information:
NSP Transport: Configured
Maximum number of logical links: 200
Maximum Transmit and Receive Window: 20
Maximum Receive Buffers: 4000
OSI Transport: Configured
Maximum number of logical links: 200
Maximum Transmit and Receive Window: 20
Maximum Receive Buffers: 4000
Congestion Avoidance Disabled
Event Dispatcher Configuration:
Sinks: local_sink
Outbound Streams: local_stream
Phase IV Relay: Enabled
* Do you want to generate NCL configuration scripts? [YES] :
6-14 Using the BASIC Configuration Option
Using the BASIC Configuration Option
6.8 Configuring a Cluster Alias
Answer YES to accept the configuration you just
specified. The procedure automatically generates the
NCL scripts and then configures the system according to
the information you supplied.
%NET$CONFIGURE-I-CHECKSUM, checksumming NCL management scripts
________________________ Note ________________________
The net$configure procedure only provides checksums of
those NCL management scripts it creates or modifies.
It does not provide checksums of user-modified NCL
scripts.
______________________________________________________
5. The procedure displays the following prompt:
* Do you want to start the network? [YES] :
Answer YES if you want to start the network and complete
your system's network configuration.
If you want to postpone starting the network, answer NO.
When you answer NO, the procedure displays the following
message:
********************************************************************
You have decided not to start the network. NET$CONFIGURE.COM
cannot complete your system's network configuration since it needs
the network to be partially started in order to perform certain
operations. As a result, your system may be left in an inconsistent
state if you try to startup the network manually or if you decide
to reboot your system.
Once you are ready to start the network, please invoke the
NET$CONFIGURE.COM procedure, choose menu Option 2 (Change node
name/namespace name), and respond YES to starting the network so
that the configuration procedure can finish your system's network
configuration.
********************************************************************
Network Startup Incomplete
Digital recommends that you answer YES and start the
network.
Using the BASIC Configuration Option 6-15
Using the BASIC Configuration Option
6.8 Configuring a Cluster Alias
6. When you choose to start the network, the procedure
displays information similar to the following:
Copyright (c) Digital Equipment Corporation 1995. All rights reserved.
.
.
.
%NET$STARTUP-I-OPERSTATUS, DECnet-Plus for OpenVMS operational status is
RUNNING-MAJOR
sys$manager:net$dns_clerk_startup.ncl changed to use the new default namespace.
Your default namespace nickname is ACME.
Your default namespace NSCTS is 08-00-2B-0D-2E-89-23-5B-15-9E-F1-85-95-00.
Node 0
at 1995-05-26-14:12:24.170-04:00I0.404
%NET$CONFIGURE-I-NODERENAMED, node successfully renamed to ACME:.WABBIT.ELMER
Directory Service: DECdns
7. You can ignore the Error - Node name lookup failure
message during startup.
Error - Node name lookup failure
ACME:.WABBIT.ELMER
Number of nodes reported on: 0
%NET$CONFIGURE-W-NODENOTREG, node is not completely registered yet in the
DECdns directory service
Directory Service: Local name file
Error - Node name lookup failure
LOCAL:.ELMER
Number of nodes reported on: 0
%NET$CONFIGURE-W-NODENOTREG, node is not completely registered yet in the
LOCAL directory service
%NET$CONFIGURE-I-IMPORTFILECREATED, created the DECNET_REGISTER import file
Directory Service: DECdns
Updating nodes listed in SYS$MANAGER:DECNET_REGISTER_IMPORT_FILE_ELMER.TXT
6-16 Using the BASIC Configuration Option
Using the BASIC Configuration Option
6.8 Configuring a Cluster Alias
Number of nodes registered: 1
Number of nodes modified: 0
%NET$CONFIGURE-I-REGSUCCESS, node has been successfully registered in the
DECdns directory service
Directory Service: Local name file
Updating nodes listed in SYS$MANAGER:DECNET_REGISTER_IMPORT_FILE_ELMER.TXT
Number of nodes registered: 1
Number of nodes modified: 0
%NET$CONFIGURE-I-REGSUCCESS, node has been successfully registered in the
LOCAL directory service
Node 0
at 1995-05-26-14:13:25.980-04:00I0.411
%NET$CONFIGURE-I-NODERENAMED, node successfully renamed to
ACME:.WABBIT.ELMER
Node 0 Session Control Tower Maintenance ACME:.WABBIT.ELMER
at 1995-05-26-14:13:35.360-04:00I0.411
%NET$CONFIGURE-I-TOWERSUPDATED, updated address towers for node
Node 0 Session Control Backtranslation Softlink *
at 1995-05-26-14:13:43.360-04:00I0.412
Node 0 Session Control Backtranslation Softlink *
at 1995-05-26-14:13:43.370-04:00I0.412
%NET$CONFIGURE-I-BCKTRNUPDATED, updated backtranslation softlink for node
%NET$CONFIGURE-I-CONFIGCOMPLETED, DECnet-Plus for OpenVMS configuration
completed
$
You have just completed the initial configuration of
a DECnet-Plus for OpenVMS system. It should now be
operational as an end system on the network.
See Figure 3-1 and Figure 3-2 to determine your next
step. According to the flowcharts, you have just completed
configuring the base components.
Using the BASIC Configuration Option 6-17
Using the BASIC Configuration Option
6.9 Changing a Current DECnet-Plus System Configuration
6.9 Changing a Current DECnet-Plus System Configuration
You can use the net$configure procedure to modify the
current configuration. Depending on which menu option you
select, net$configure either modifies the configuration
automatically or produces modified NCL scripts that you can
use to modify the system's configuration.
See Chapter 4 to determine whether you want to use the
FAST, BASIC or ADVANCED configuration option to change
your configuration. Refer to the DECnet-Plus for OpenVMS
Applications Installation and Advanced Configuration for
instructions on how to run the ADVANCED configuration.
6-18 Using the BASIC Configuration Option
7
_________________________________________________________________
Managing Name Services
If this is the first time you are configuring the DECnet-
Plus for OpenVMS software on your system, the information
in this chapter further explains some of the topics that
appear as you run the configuration procedure.
7.1 Names Services Overview
While configuring DECnet-Plus, the system administrator
specifies one or more of the following directory name
services to use on the node: the Local namespace, DECdns,
or Domain Name System (for DNS/BIND). See Section 6.2 for
more information.
o Local namespace - A discrete, nondistributed namespace
that stores name and address information locally in
database files. DECnet-Plus includes a Local namespace.
o DECdns - Digital's Distributed Name Service, a
distributed, global name service.
o Domain Name System - The Domain Name System (DNS/BIND)
supported for storage of IP addresses.
For more information on name services, refer to the DECnet-
Plus Planning Guide.
7.1.1 The Local Namespace
DECnet-Plus includes a Local namespace, independent of
DECdns, that is designed to scale to at least 100,000
nodes.
The Local namespace is a discrete, nondistributed namespace
that exists on a single node and provides that node with
a local database of name and address information. The
prefix LOCAL: (or local:) is reserved to indicate that the
information for the node is stored in the Local namespace.
Managing Name Services 7-1
Managing Name Services
7.1 Names Services Overview
DECnet-Plus recognizes that when a node full name begins
with LOCAL:, information for that node is stored in a
Local namespace. The following are typical node full names
properly formatted for the Local namespace: LOCAL:.xyz.abc
and local:.maximum.
Unlike DECdns, the Local namespace does not employ
backtranslation directories for address-to-node-name
translation.
7.1.1.1 Creating a Local Namespace
If you want to create a Local namespace, enter
LOCAL:.DirectoryPath.NodeObject at the following prompt:
* Enter the full name for directory service LOCAL:
The directory path identifies the namespace subdirectory
(if any). The node object is the system's node name.
7.1.1.2 Managing the Local Namespace
The DECdns distributed namespace is not a requirement
for DECnet-Plus and the Local namespace is not dependent
on DECdns. However, the DECdns clerk software is still
required on each node. You cannot use the DECdns Control
Program (DNSCP) to manage information stored in the Local
namespace. Instead, use decnet_register to manage the node
name and address information stored in your namespace. The
decnet_register tool is described in the DECnet-Plus for
OpenVMS Network Management guide.
7.1.2 The Digital Distributed Name Service (DECdns)
DECdns is a networkwide service that makes it possible
to use network resources without knowing their physical
location. Users and applications can assign DECnet-Plus
names to resources such as nodes. The creator of a name
also supplies other relevant information, such as the
resource's network address, for DECdns to store. Users then
need to remember only the name, and DECdns acts as a lookup
service, providing the rest of the data when necessary.
7-2 Managing Name Services
Managing Name Services
7.1 Names Services Overview
7.1.2.1 Creating a New Namespace
You need to create a new DECdns namespace only if you are
configuring the first DECdns server for the network or if
you are creating an additional namespace. If you already
have a DECdns namespace, you do not need to create a new
namespace to be able to run DECnet-Plus. However, if this
is the first system in a network where no namespace exists
and you do not intend to use the Local namespace, you must
create (and populate) a DECdns namespace.
If you are unsure whether you need to create a new
namespace or configure your system as a server, see your
network manager. For information about namespace planning,
refer to the DECnet-Plus Planning Guide.
To create a new namespace while configuring a DECnet-Plus
for OpenVMS system:
o The DECdns server software must be installed on the
system.
o DECdns must be specified as one of the naming services
configured on the system.
When you create a namespace, you need a namespace nickname
and clearinghouse name. The namespace nickname is part of
the full name of every subsequent system in the network and
should be unique to your network. The namespace nickname
that you specify becomes the actual name of the namespace.
A clearinghouse is a collection of directory replicas that
contains the names and addresses of objects (for example,
servers, clerks, files).
Digital recommends that you create namespace
directories before using the configuration procedure
(net$configure.com) to create the namespace. Follow these
steps to create namespace directories:
1. Invoke decnet_register and select option 10 ("Manage the
directory service").
2. Follow directions. Be sure to specify DECdns as the
directory service to manage (the Local namespace is
the default). The decnet_register procedure invokes
sys$manager:decnet_register_decdns.com to create the
namespace directories.
Managing Name Services 7-3
Managing Name Services
7.1 Names Services Overview
3. When finished, invoke the configuration procedure to
create the new namespace.
For more information on decnet_register, refer to DECnet-
Plus for OpenVMS Network Management.
7.1.2.2 Creating a DECdns Namespace
If you select DECdns as a directory service, net$configure
prompts you for the full name you want to use:
* Enter the full name for directory service DECDNS: new_ns:.mrv042 <Return>
If this is a new namespace, net$configure prompts you for
more information once the configuration procedure completes
and you have started the network. The startup information
will be similar to the following:
%NET$STARTUP-I-OPERSTATUS, DECnet-Plus for OpenVMS operational status is RUNNING-
MAJOR
The namespace you specified was NEW_NS.
%DNS-E-NOMATNS, The specified namespace is not being served on your LAN.
please choose from the following list
[1] BB_NS
[2] DOMAIN
[3] LOCAL
[4] X500
[0] - Reject this list -
Pick a number from the list: 0 <Return>
Because you are creating a new namespace, the namespace
you specified at the prompt, "What is the full name of this
node?" does not appear in the list. To continue, enter 0
and press Return to reject the list.
If you are installing DECnet-Plus for OpenVMS for the first time
and you want to create a namespace, type Y. If you want to
attempt a WAN connection to a remote DECdns server,
type N (default) at the following prompt:
Do you want to proceed with creating a new namespace [n]: y <Return>
7-4 Managing Name Services
Managing Name Services
7.1 Names Services Overview
At this point, the configuration procedure needs to
determine whether you intend to configure your system as
a clerk on a WAN (connect to an off-LAN server) or create
a new namespace. Since you cannot create a new namespace
unless you have installed DECdns server software on the
system, the procedure first verifies that the server
software has been installed.
If you want to create a new namespace, type YES at the
prompt and press Return. The procedure continues prompting
you for information necessary to create the namespace
and the appropriate directories. The procedure displays
information about the namespace, the directories, and other
network parameters, then tells you when the configuration
is complete.
Your next input will determine the name of the clearinghouse
in your namespace new_ns. Enter the clearinghouse name as
alphanumeric and/or underscore characters.
Enter a simple name for the clearinghouse: .mrv042_new_ns_ch <Return>
Node 0
at 1995-04-06-15:49:35.420-04:00Iinf
Creating DECdns Server process ...
%RUN-S-PROC_ID, identification of created process is 00000122
Your default namespace nickname is new_ns.
Node 0
at 1995-04-06-15:49:42.100-04:00Iinf
%NET$CONFIGURE-I-FLUSHCACHE, flushing selected cache entries
Node 0
at 1995-04-06-15:49:47.180-04:00Iinf
%NET$CONFIGURE-I-NODERENAMED, node successfully renamed to new_ns:.mrv042
%NET$CONFIGURE-I-NEWNAMESPACE, a new namespace has been created
%NET$CONFIGURE-I-ADDGROUP, adding .WorldRead_Group to the new namespace
Create the initial namespace directories.
Press Ctrl/Z at any question to cancel the initialization.
* Phase IV prefix value [afi:idi:predsp, Def=47:0027:]: <Return>
* Maximum Phase IV area to use [1-63, Def=63]: 2 <Return>
Managing Name Services 7-5
Managing Name Services
7.1 Names Services Overview
The DECdns namespace groups and directories will now be created. This might
take up to 6 minutes or more, depending on the speed of the DECdns
server system and the amount of traffic on the network.
Creating the NEW_NS:.DNA_Registrar group.
Creating the NEW_NS:.DNA_BackTranslation directory.
Creating the NEW_NS:.DNA_BackTranslation.%X470027 directory.
Creating the NEW_NS:.DNA_BackTranslation.%X470027.%X0001 directory.
Creating the NEW_NS:.DNA_BackTranslation.%X470027.%X0002 directory.
Creating the NEW_NS:.DNA_NodeSynonym directory.
Creating the NEW_NS:.DTSS_GlobalTimeServers directory.
DECdns namespace initialization for DECnet use is complete.
If this is the first time you have initialized the namespace for DECnet
use, use SYS$SYSTEM:DECNET_REGISTER.EXE to:
- Create a command file to automatically register previously defined
Phase IV nodes. Execute this command file before you manually
register any other nodes using SYS$SYSTEM:DECNET_REGISTER.EXE.
- Create any directories you need for node names that should be registered
immediately, according to your namespace design. This includes the node
you are currently running on.
- Be sure to add backtranslation directories for any non PhaseIV areas/IPDs.
Failure to do so will lead to Backtranslation Failures. Once you've added
the necessary backtranslation directories, you may need to use the
ncl flush session control naming cache entry "*" command.
- Change the local node's registered name from its default name to its
final full name. The local node will be registered as a Phase IV node
with a default name when you execute the Phase IV node registration
command file above.
- Change the currently registered names of other nodes from their default
names to their final full names when appropriate (for example, when they
are upgraded to run DECnet-Plus software).
Continue to use SYS$SYSTEM:DECNET_REGISTER.EXE to:
- Create any additional directories you need for node names, as new nodes
are brought up on the network.
- Register new nodes as they are brought up on the network.
- Add members to the NEW_NS:.DNA_Registrar access control group.
Additionally, you can use the DECdns control utility to:
7-6 Managing Name Services
Managing Name Services
7.1 Names Services Overview
- Add specific access control to individual directories, objects, and
soft links.
- Create replicas of directories.
The following were created:
Group: NEW_NS:.DNA_Registrar
Directory: NEW_NS:.DNA_BackTranslation
Directory: NEW_NS:.DNA_BackTranslation.%X470027
Directories: NEW_NS:.DNA_BackTranslation.%X470027.*
Directory: NEW_NS:.DNA_NodeSynonym
Directory: NEW_NS:.DTSS_GlobalTimeServers
%NET$CONFIGURE-I-CREATEINITDIR, created initial namespace directories
Registering the node NEW_NS:.mrv042
Type is DECnet-Plus
Synonym is MRV042
%NET$CONFIGURE-I-REGSUCCESS, node has been successfully registered in the
!NEW_NS directory service
Node 0
at 1995-04-06-15:50:29.390-04:00Iinf
%NET$CONFIGURE-I-NODERENAMED, node successfully renamed to new_ns:.mrv042
. . .
. . .
. . .
. . .
. . .
%NET-I-LOADED, executive image NET$LOOP_APPLICATION.EXE loaded
%NET$STARTUP-I-OPERSTATUS, DECnet-Plus for OpenVMS operational status is RUNNING-
ALL
%NET$CONFIGURE-I-CONFIGCOMPLETED, DECnet-Plus for OpenVMS configuration completed
7.1.3 Domain Name System
Refer to your BIND server documentation for specific
installation and configuration instructions. For a list
of supported vendors, see Section 1.4.1.1. Any properly
constructed DNS/BIND node name is supported by DECnet-Plus.
Managing Name Services 7-7
Managing Name Services
7.1 Names Services Overview
7.1.4 Namespace Management
DECnet-Plus includes a new in-memory naming cache to
improve performance of name and address resolution for
all supported name services. Refer to the DECnet-Plus for
OpenVMS Network Management guide for more information.
DECnet-Plus includes several new features to ease namespace
management including decnet_register (a new namespace
management tool), several new Network Control Language
(NCL) commands, and Common Trace Facility (CTF) support for
monitoring node name and address resolution.
The decnet_register tool, an executable image located
in SYS$SYSTEM:, centralizes and simplifies namespace
management tasks by replacing functionality previously
provided by both the decnet_dns_register and decnet_
loc_register command procedures, which were located in
SYS$MANAGER:. The decnet_register tool manages information
in both the DECdns distributed name service and the Local
namespace. The decnet_register manage command assists with
setting up tasks for the DECdns name service. For example,
it creates namespace directories and access groups, and
enables autoregistration. Refer to the section on decnet_
register in the DECnet-Plus for OpenVMS Network Management
guide for more information.
7.2 Name Service Search Path
The name service search path applies systemwide and
allows DECnet-Plus to search a list of name services in
a predetermined order when looking up names or addressing
information. The search path includes naming templates
that tell DECnet-Plus how to interpret any abbreviated node
names entered by users.
The ordering of the name services is very important. The
first name service listed is the primary name service
to use on the system. The primary name service is the
first choice used when looking up names and addressing
information. The remaining name services listed are the
secondary name services used on the system.
The search path contains a list of name service keywords,
each followed by a naming template that specifies a
"defaulting rule" so users can enter shorter node names.
7-8 Managing Name Services
Managing Name Services
7.2 Name Service Search Path
7.2.1 Configuring the Search Path Information
During DECnet-Plus configuration, the system administrator
uses net$configure.com to set up one, two, or three name
services on each node.
From the information provided by the system administrator,
net$configure creates NET$SEARCHPATH_STARTUP.NCL, the
standard search path NCL startup script which contains
the name service search path information for the node.
The system administrator supplies one or two properly
formatted DECnet-Plus node full names (in the case of the
Local namespace and the DECdns distributed name service)
and one fully qualified host name for DNS/BIND (if DNS/BIND
is to be used on the node).
The first full name is specified in the proper format for
the name service to be searched first. The second and third
node names are properly formatted for the name services to
be searched second and last.
If more than one name service is to be used on the node,
the name services are searched in the order specified
by the system administrator. For example, if the system
administrator specifies Local, DECdns and Domain for the
name services to use on the system, the Local namespace is
searched before the DECdns namespace and DNS/BIND.
The following configuration example illustrates how to
upgrade to DECnet-Plus Version 7.1 and use the new name
service access features. Invoke net$configure.com and
select Option 2 ("Change node name/namespace name"). The
following prompt is displayed:
* Enter the directory services to use on the system [LOCAL,DECDNS,DOMAIN]:
At the prompt, you can choose the following name services
for the system: LOCAL, DECDNS, and DOMAIN. If you enter
more than one name service, separate each name with commas.
For example, entering DECDNS,LOCAL,DOMAIN at the prompt,
means the following:
o You want to use the name services DECdns, Local, and
DNS/BIND.
o The primary name service is DECdns.
Managing Name Services 7-9
Managing Name Services
7.2 Name Service Search Path
o The secondary name services are Local and DNS/BIND, in
that order.
________________________ Note ________________________
If your node is also a DECdns server, the primary name
service must be DECdns.
______________________________________________________
7.2.1.1 Naming Search Path in a Cluster
All members in a cluster should have identical naming
search paths configured. This will help to ensure that
nodes are recognized in the various services you have
identified.
For example, if you receive mail on one node in the
cluster, the "from" node name would be LOCAL:.NODE::SMITH.
If you attempt to reply to this node from a node in the
cluster that does not have Local configured, the system
would indicate that there is no such node.
7.2.2 Displaying the Search Path Information
The system maintains two separate search paths:
o One search path supports forward translation or naming
(node-name-to-address translation).
$ mcr ncl show session control naming search path
o Another separate search path supports backtranslation
(address-to-node-name translation).
$ mcr ncl show session control backtranslation search path
Refer to DECnet-Plus OpenVMS Network Management for more
information.
7.2.3 Modifying the Search Path Information
Digital recommends that you rerun net$configure.com to
revise the standard search path NCL script (NET$SEARCHPATH_
STARTUP.NCL) whenever it is necessary to reorder access
to the name services on the node. To modify the standard
search path startup script, run net$configure.com and use
Option 2 ("Change node name/namespace name").
7-10 Managing Name Services
Managing Name Services
7.2 Name Service Search Path
________________________ Note ________________________
Whenever you directly edit an existing NET$SEARCHPATH_
STARTUP.NCL script, or when you use the NCL set
command to change the script (rather than changing
the script by rerunning net$configure.com), your
edits are overwritten by any new NET$SEARCHPATH_
STARTUP.NCL scripts you subsequently generate by
rerunning net$configure.com.
______________________________________________________
7.2.4 Creating a Site-Specific Search Path NCL Script
Digital recommends that you allow net$configure.com (and in
some cases net$startup.com) to create and use the standard
NCL search path script (NET$SEARCHPATH_STARTUP.NCL).
However, if you need to make site-specific changes to your
search path NCL script and you do not want net$configure
to overwrite these changes, you can create a site-specific
search path NCL script by renaming the standard search
path script (NET$SEARCHPATH_STARTUP.NCL) to NET$SEARCHPATH_
LOCAL.NCL and making your changes to the new file.
For example, you might want to use the NCL set command
described in Section 7.2.6 to create site-specific naming
templates in NET$SEARCHPATH_LOCAL.NCL.
The net$configure.com and net$startup.com procedures check
for the presence of a site-specific search path script
(NET$SEARCHPATH_LOCAL.NCL) on the node. If NET$SEARCHPATH_
LOCAL.NCL is present on the node, it is invoked instead of
the standard script. A message similar to the following is
displayed:
**************************************************************
A site-specific searchpath NCL script has been found on the
system (SYS$SYSROOT:[SYSMGR]NET$SEARCHPATH_LOCAL.NCL;). The
configuration procedure will use this script to set the
searchpath instead of using the standard searchpath script
that is created by NET$CONFIGURE (NET$SEARCHPATH_STARTUP.NCL).
**************************************************************
%NET$CONFIGURE-I-SITESEARCHPATH, invoking site-specific searchpath
NCL script found on system
Managing Name Services 7-11
Managing Name Services
7.2 Name Service Search Path
The net$configure.com and net$startup.com procedures do
not modify the site-specific search path NCL script;
rather, they invoke the site-specific search path script
as it currently exists. Therefore, when using a site-
specific search path NCL script, you must modify it prior
to invoking net$configure.com whenever you change any of
the following name service information:
o The number of name services used on the node
o The order of the name services used on the node
o The specific name services used on the node
7.2.5 Using the Search Path to Ease Migration
A search path can be used to simplify migration from one
name service to another. The system administrator can
create a search path designating the currently used name
service as the primary name service (to be searched first)
and the new name service as the secondary name service
(to be searched second after the primary name service is
searched).
As the secondary name service becomes populated with node
and addressing information, the system administrator can
rerun net$configure.com and select Option 2 to reverse the
positions of the name services in the search path. This
causes the current secondary service to become primary, to
be searched first for node and addressing information.
7.2.6 Setting Up Naming Templates
In each template, the user-supplied portion of the name
(usually the node's terminating name or rightmost simple
name) is indicated with an asterisk (*). For example, if
the DECdns template is: "ABCDE:.xyz.*" and a user supplies
the name fin, then the following full name: ABCDE:.xyz.fin
is looked up in namespace ABCDE in the DECdns name service.
You should specify only one asterisk per template. Only
the first occurrence of an asterisk (*) in the template is
substituted with the user-supplied name. Any additional
asterisks are passed to the name service as part of
the full name. When you specify a template without an
asterisk, the template string is passed to the name service
unchanged.
7-12 Managing Name Services
Managing Name Services
7.2 Name Service Search Path
If the user-supplied name should be passed to the name
service as entered by the user, the template should be
specified as follows: "*".
DECnet-Plus provides an NCL set command for modifying
the naming templates associated with the naming and
backtranslation search paths. Do not use the NCL set
command to modify aspects of the search path other than
the naming templates.
The following NET$SEARCHPATH_LOCAL.NCL script creates
typical naming and backtranslation search paths. In this
script ABCDE represents the namespace nickname. Your
namespace nickname will appear in your NCL script:
SET NODE 0 SESSION CONTROL NAMING SEARCH PATH -
([DIRECTORY SERVICE = LOCAL, TEMPLATE = "*"], -
[DIRECTORY SERVICE = LOCAL, TEMPLATE = "local:*"], -
[DIRECTORY SERVICE = LOCAL, TEMPLATE = "LOCAL:.*"], -
[DIRECTORY SERVICE = DECDNS, TEMPLATE = "*"], -
[DIRECTORY SERVICE = DECDNS, TEMPLATE = "ABCDE:*"], -
[DIRECTORY SERVICE = DECDNS, TEMPLATE = "ABCDE:.xyz.*"], -
[DIRECTORY SERVICE = DECDNS_SYNONYM, TEMPLATE = "ABCDE:.DNA_NodeSynonym.*"
], -
[DIRECTORY SERVICE = DOMAIN, TEMPLATE = "*"], -
[DIRECTORY SERVICE = DOMAIN, TEMPLATE = "*.xyz.ABCDE.com"])
SET NODE 0 SESSION CONTROL BACK SEARCH PATH -
([DIRECTORY SERVICE = LOCAL, TEMPLATE = ""], -
[DIRECTORY SERVICE = DECDNS, TEMPLATE = "ABCDE:.DNA_BackTranslation"], -
[DIRECTORY SERVICE = DOMAIN, TEMPLATE = ""])
7.3 Domain Synonyms
Support for the Domain Name System (DNS/BIND) provides
for the use of node synonyms. This allows for backward
compatibility with older applications that cannot use long
domain names.
There are two ways to configure node synonyms for use with
DNS/BIND:
o By constructing an appropriate set of naming search path
templates
o By defining local aliases
Managing Name Services 7-13
Managing Name Services
7.3 Domain Synonyms
7.3.1 Search Path Naming Template Support for Domain Synonyms
You can provide synonym support for entire domains by
constructing an appropriate set of search path templates.
Note that excessively long search paths (search paths with
many entries) can increase the time it takes to look up
node addresses. See Section 7.2 for general information on
name service search paths.
Entering the following NCL command sets up a search path
for a system using DNS/BIND:
$ mcr ncl set session control naming search path = -
{ [Directory Service = Domain, Template = "*"], -
[Directory Service = Domain, Template = "*.finbar.com"], -
[Directory Service = Domain, Template = "*.abc.finbar.com"], -
[Directory Service = Domain, Template = "*.xyz.finbar.com"]}
This NCL command results in the following DNS/BIND naming
templates:
*
*.finbar.com
*.abc.finbar.com
*.xyz.finbar.com
When DECnet-Plus receives a connection from node
koi.abc.finbar.com, it determines that koi is a usable
synonym for this node, and DECnet-Plus will return the name
koi to applications that require Phase IV style node names.
Using search path naming templates for synonym support
allows the user to enter any of the following node names:
koi, koi.abc, or koi.abc.finbar.com for node koi.
7.3.2 Local Aliases
Another way to define a node synonym for a particular node
is by adding DNS/BIND alias names to the local host's
database. The following is an example using Digital TCP
/IP Services for OpenVMS:
$ ucx set host koi.abc.finbar.com/address=aa.bb.cc.dd/alias=koi
DECnet-Plus now returns the node synonym koi to
applications that require Phase IV-style node names.
7-14 Managing Name Services
Managing Name Services
7.4 Node Synonym Directories
7.4 Node Synonym Directories
The default node synonym directory is .DNA_NodeSynonym.
If you plan to use a node synonym directory other than
this default directory, you must define the logical
name DECNET_MIGRATE_DIR_SYNONYM to the synonym directory
name you want to use in sys$manager:net$logicals.com.
(If you do not have a sys$manager:net$logicals.com
procedure on your system, you can create one using
sys$manager:net$logicals.template.) This makes the
definition permanent (that is, it will not be deleted when
you reboot the system).
7.4.1 Defining an Alternate Node Synonym Directory
Use the following format to define an alternate node
synonym directory:
$ define decnet_migrate_dir_synonym "alt-directory-name"
If you use a synonym directory name that includes special
characters or three or more dots, the system might produce
an error. To avoid this, enclose the synonym directory name
in quotes. For example:
$ define/system decnet_migrate_dir_synonym ".ch.noun.synonym"
The net$configure procedure needs this logical name to be
defined at all times if you wish to use a synonym directory
other than .DNA_NodeSynonym. Be sure to add this definition
to net$logicals.com to ensure that the definition of the
synonym directory will be permanent.
7.4.2 When to Use the Logical Name
You can use the logical name described in Section 7.4.1 for
either the BASIC or the ADVANCED configuration option.
You must define this logical name before you use any of
following procedures:
net$configure.com
decnet_register.exe
decnet_migrate.exe
Managing Name Services 7-15
Managing Name Services
7.4 Node Synonym Directories
If synonym lookup fails in the namespace, the software does
one of the following:
o The startup procedure defines SYS$NODE, SYS$CLUSTER_
NODE, or both to be the first six characters of the last
simple name of the respective node full name or cluster
full name.
o The configuration procedure defines SYS$NODE to be the
node synonym name that was entered during configuration.
The system displays a message that it has redefined the
logical names.
7.5 Using a DNS Version 1 Namespace with DECdns Version 2
If you are already using a namespace created with Version
1 of the VAX Distributed Name Service (DNS) (running on
DECnet Phase IV), you can continue to use the namespace
when you upgrade your networking software to DECnet-Plus
for OpenVMS. However, because of differences in the way
that DNS Version 1 and DECdns Version 2 handle access
control, you must prepare your DNS Version 1 namespace
for use by DECnet-Plus. DNS Version 1 and DECdns Version
2 interpret principal specifications in access control
entries (ACEs) differently.
In DNS Version 1, servers recognize principals only
in the form nodename::username. In DECdns Version 2,
servers recognize principals primarily in the form
nodename.username. For DECdns Version 2 clerks and servers
to interpret and process existing DNS Version 1-style
access control entries in the namespace, you need to create
a backtranslation directory (.DNA_BackTranslation) and
a node synonym directory (.DNA_NodeSynonym) in the root
directory of the namespace. You must then populate these
directories by registering all the nodes participating in
the Version 1 namespace.
7-16 Managing Name Services
Managing Name Services
7.5 Using a DNS Version 1 Namespace with DECdns Version 2
7.5.1 Preparing a DNS Version 1 Namespace for Use by DECdns
Version 2
To prepare a namespace created with DNS Version 1 for use
by DECnet-Plus, follow these steps:
1. Install and configure DECnet-Plus for OpenVMS on any
node in your namespace that is not currently functioning
as a DNS Version 1 server. Configure the node as a
DECdns Version 2 clerk. See Chapter 3 and Chapter 5
in this book if you plan to use the BASIC configuration
option, or the DECnet-Plus for OpenVMS Applications
Installation and Advanced Configuration guide if you
plan to use the ADVANCED configuration option.
2. From any node running DNS Version 1 server software,
use the DNS Version 1 control program (DNS$CONTROL) add
access command to grant the following DNS Version 1-
style access on behalf of the SYSTEM account on the new
Version 2 clerk node that you configured in Step 1:
o Read, write, delete, test, and control access to the
root directory of the namespace
o Read, write, delete, test, and control access to the
clearinghouse that stores the master replica of the
root directory
For example, if the DECnet-Plus full name of the new
clerk is .pastry, and the master replica of the Version
1 namespace is stored in the .paris_ch clearinghouse,
enter the following two commands:
DNS> add access pastry::system directory . /rights=(r,w,d,t,c)
DNS> add access pastry::system clearinghouse .paris_ch /rights=(r,w,d,t,c)
You need to grant this access to ensure that the SYSTEM
account on the new Version 2 clerk has sufficient access
to run the decnet_register utility. The Version 2 clerk
must also have permission to create and populate a
backtranslation directory (.DNA_BackTranslation) and
node synonym directory (.DNA_NodeSynonym) in the root
directory of the namespace during the next step of this
procedure.
Managing Name Services 7-17
Managing Name Services
7.5 Using a DNS Version 1 Namespace with DECdns Version 2
________________________ Note ________________________
If the node you configured as a Version 2 clerk in
Step 1 is a new node, or is being assigned a new
DECnet Phase IV-compatible address, you should update
the DECnet node databases on all Version 1 servers in
the namespace to include the new address before you
proceed.
______________________________________________________
3. Log in to the new Version 2 clerk node under the SYSTEM
account and invoke the sys$manager:decnet_register_
decdns.com utility. Do the following:
a. Choose Option 3 on the decnet_register_decdns.com
menu to create and populate a backtranslation
directory (.DNA_BackTranslation). Choose Option 2 to
create a node synonym directory (.DNA_NodeSynonym).
b. Choose Option 2 on the decnet_register menu to
register the new Version 2 clerk node (the node
you are logged in to) and to register all other
DECnet Phase IV nodes in the namespace including all
nodes that are currently functioning as DNS Version 1
servers.
Refer to the DECnet-Plus for OpenVMS Network Management
guide for complete information on how to use the decnet_
register utility and the decnet_register_decdns.com utility
to perform these steps.
7.5.2 Using the DNS Version 1 Namespace
When you have completed this step, the DNS Version 1
namespace is ready for use by other nodes running DECdns
Version 2 on DECnet-Plus for OpenVMS software.
Perform this procedure only once to prepare a DNS Version 1
namespace for use with DECnet-Plus. After the node synonym
and backtranslation directories are populated, you can
configure new DECdns clerks, new DECdns servers (for VAX
only) into an existing namespace, or convert existing
DNS Version 1 servers to DECdns Version 2 format in the
normal manner. Refer to the DECnet-Plus DECdns Management
guide for information on how to convert a DNS Version 1
clearinghouse to DECdns Version 2 format.
7-18 Managing Name Services
Managing Name Services
7.6 Registering a Node in the Namespace
7.6 Registering a Node in the Namespace
The net$configure.com procedure creates an Export/Import
file to register your node in the appropriate namespace.
If your node is already registered, the decnet_register
Export/Import file is not created.
7.6.1 Export/Import File Format
The decnet_register Export/Import file is a text file
that has the following format where <synonym> is the node
synonym name you selected during configuration:
sys$manager:decnet_register_import_file_<synonym>.TXT
7.6.2 Problems Registering a Node
If you encounter problems registering your node in the
Local namespace or in the DECdns namespace, you will see
information similar to the following:
.
.
.
Updating nodes listed in SYS$MANAGER:DECNET_REGISTER_IMPORT_FILE_ELMER.TXT
1) local:.elmer
Error - Node registration was unsuccessful
Please correct any problems and re-register the node LOCAL:.elmer
The specified node name is already in use as a synonym
Used by node: LOCAL:.WABBIT.ELMER
Synonym: elmer
You can choose to stop processing this command, continue executing this
command until completion or until the next error, or ignore further errors
and continue to completion.
Number of nodes registered: 0
Number of nodes modified: 0
Number of update failures: 1
%NET$CONFIGURE-E-COULDNOTREG, could not automatically register node in the LOCAL
directory service
Managing Name Services 7-19
Managing Name Services
7.6 Registering a Node in the Namespace
**********************************************************************
WARNING
This node could not be registered in one or more of the directory
services you have chosen. When this procedure completes you or your
network manager will have to manually register this node in the directory
service(s) for which the error occurred. See the DECnet-Plus Installation
and Configuration guide for more details, or contact your network manager.
Once the problem has been rectified, you or your namespace manager can
use the following decnet_register command(s) to register your node in the
appropriate directory service(s):
For the LOCAL directory service:
DECNET_REGISTER IMPORT DIRECTORY LOCAL FILE -
SYS$MANAGER:DECNET_REGISTER_IMPORT_FILE_ELMER.TXT
Once the node has been successfully registered in the appropriate
directory service(s), invoke option 2 of NET$CONFIGURE.COM (Change
node name/namespace name) to complete the node's network configuration
and startup.
**********************************************************************
If net$configure.com cannot access the DECdns namespace you
have selected, it is most likely because:
o The namespace is not available at the moment.
o Your node does not have proper access to the DECdns
namespace.
o The namespace you are using is new and the directories
have not been created yet.
When this happens, you will see the following message
(this example uses ACME: as the namespace that is not
accessible):
*************************************************************************
WARNING
NET$CONFIGURE.COM cannot access the ACME: namespace, either because
the namespace is not available at the moment, your node does
not have proper access to the namespace, or because the namespace
you are using is new and the directories have not been created yet.
Therefore, the decnet_register tool cannot attempt to look up or register
your node into the ACME: namespace.
7-20 Managing Name Services
Managing Name Services
7.6 Registering a Node in the Namespace
When the problem is rectified, please use the decnet_register import file
to register your node into the ACME: namespace.
*************************************************************************
If you receive this message because the namespace you are
using is new and the namespace directories have not been
created yet, use the decnet_register manage command to
invoke decnet_register_decdns.com (located in SYS$MANAGER:)
to create the proper directories. For more details, refer
to the DECnet-Plus for OpenVMS Network Management guide.
If you see the preceding warning messages, net$configure
will display another message indicating how you or your
namespace manager can attempt node registration once the
problem is resolved. For example:
**********************************************************************
WARNING
This node could not be registered in one or more of the directory
services you have chosen. When this procedure completes you or your
network manager will have to manually register this node in the directory
service(s) for which the error occurred. See the DECnet-Plus Installation
and Configuration guide for more details, or contact your network manager.
Once the problem has been rectified, you or your namespace manager can
use the following decnet_register command(s) to register your node in the
appropriate directory service(s):
For the DECdns directory service:
DECNET_REGISTER IMPORT DIRECTORY DECDNS FILE -
DECNET_REGISTER_IMPORT_FILE_ELMER.TXT
For the LOCAL directory service:
DECNET_REGISTER IMPORT DIRECTORY LOCAL FILE -
DECNET_REGISTER_IMPORT_FILE_ELMER.TXT
Once the node has been successfully registered in the appropriate
directory service(s), invoke option 2 of NET$CONFIGURE.COM (Change
node name/namespace name) to complete the node's network configuration
and startup.
**********************************************************************
You may see the previous messages if the following exists:
o You enter LOCAL for the primary directory service and
DECDNS for the secondary directory service and,
Managing Name Services 7-21
Managing Name Services
7.6 Registering a Node in the Namespace
o Your primary Local node full name does not have the
proper access necessary to look up or register your
secondary DECdns node full name.
If this is the case, you or your namespace manager need
to perform the following steps on the node that has the
DECdns server in order for your primary Local node to
obtain this access to the DECdns namespace:
1. Make sure the .WorldRead_Group is created on the
DECdns server node. If the .WorldRead_Group has not
been created yet, use the decnet_register manage
command to invoke decnet_register_decdns.com (located
in sys$manager:) to create the .WorldRead_Group. For
more details, refer to the DECnet-Plus for OpenVMS
Network Management guide.
2. Once you or your namespace manager knows that the
.WorldRead_Group has been created, invoke the
DNS$CONTROL utility on the node with the DECdns
server and enter the following commands:
$ mcr dns$control
DNS> add group <ns>:.worldread_group member local:.*...
DNS> add clear <ns>:.<ch_name> access <ns>:.worldread_group as group for r,t
where <ns> is the DECdns namespace name to which you
want your LOCAL node to have access and <ch_name> is
the clearinghouse name of the DECdns namespace you
are using.
These commands will give your primary Local full name the
proper access it needs to look up information regarding the
secondary DECdns full name you have chosen.
________________________ Note ________________________
If you use DECDNS for the primary directory service
and LOCAL for the secondary directory service, these
steps are not necessary.
______________________________________________________
7-22 Managing Name Services
Part III
_________________________________________________________________
Additional Installation Information
Part III contains the following appendixes:
o Appendix A - Overview of the POLYCENTER Software
Installation Utility
o Appendix B - Installing DECnet-Plus for OpenVMS from an
InfoServer
o Appendix C - System Files Loaded During Installation
A
_________________________________________________________________
The POLYCENTER Software Installation Utility
The POLYCENTER Software Installation utility replaces
VMSINSTAL as the method of installing layered products
for OpenVMS such as the OSI applications for DECnet-Plus
for OpenVMS, and X.25 for OpenVMS Alpha. It allows you to
install several software products with a single command.
________________________ Note ________________________
Before installing DECnet-Plus using the POLYCENTER
Software Installation utility for the first time
on OpenVMS VAX Version 7.1, you should execute the
following DCL command:
$ product register product vms/version=v7.1/source=sys$update
This needs to be done only once in the life of the
OpenVMS system; it makes a permanent entry in the
POLYCENTER Software Installation utility database, so
it remains effective across system boots and for all
future software upgrades.
If you do not perform this operation before installing
DECnet-Plus, the installation recommends termination
due to the failure to locate the product "DEC VAXVMS
VMS Version 7.1." Answer YES to the question Do you
want to terminate? and perform the product register
command as in the above example.
______________________________________________________
Additional details for using the POLYCENTER Software
Installation utility to install, manage, and remove
software products on your system are provided in the
OpenVMS System Management Utilities Reference Manual.
The POLYCENTER Software Installation Utility A-1
The POLYCENTER Software Installation Utility
A.1 DCL Help with POLYCENTER
A.1 DCL Help with POLYCENTER
To obtain DCL Help for POLYCENTER, type the DCL command
help product, followed by the name of a POLYCENTER Software
Installation utility command (for example: help product
install).
A-2 The POLYCENTER Software Installation Utility
The POLYCENTER Software Installation Utility
A.1 DCL Help with POLYCENTER
A.1.1 DCL Command Summary
DCL Help for the PRODUCT commands listed in Table A-1
describes all the tasks you can perform from the DCL
interface.
Table A-1 DCL PRODUCT Commands and Qualifiers
___________________________________________________________
PRODUCT_Command_________________Qualifiers_________________
CONFIGURE /CONFIGURATION
Creates a product /HELP
configuration file (PCF) /LOG
for one or more products in /OUTPUT
reference format. Optionally,
uses the values in an existing
PCF to create the new PCF.
COPY /DESTINATION
Manipulates a product /FORMAT
distribution. You can use /HELP
copy to create a sequential /LOG
copy from a reference copy, /OUTPUT
a reference copy from a /OWNER_UIC
sequential copy, or to create /SOURCE
a copy without changing the
format.
EXTRACT RELEASE_NOTES /DISPLAY
Accesses the release notes for /LOG
the selected product or group /OUTPUT
of products. /SOURCE
FIND /LOG
Looks at the distribution /OUTPUT
media and reports on the /SOURCE
products it finds there.
(continued on next page)
The POLYCENTER Software Installation Utility A-3
The POLYCENTER Software Installation Utility
A.1 DCL Help with POLYCENTER
Table_A-1_(Cont.)_DCL_PRODUCT_Commands_and_Qualifiers______
PRODUCT_Command_________________Qualifiers_________________
INSTALL /CONFIGURATION
Installs one or more software /DESTINATION
products on your system. /HELP
/LOG
/OUTPUT
/PURGE
/REMARK
/SOURCE
/TEST
/WORK
RECONFIGURE /CONFIGURATION
Changes the active /HELP
configuration choices for /LOG
a product. /OUTPUT
/REMARK
/SOURCE
REGISTER PROCESSOR /BASE_SYSTEM
Adds a processor in a /BOOTSTRAP
computing facility. Used /DESTINATION
primarily within a DCL command /GLOBAL
procedure during system /HELP
startup. /LOG
/OPERATING
/OUTPUT
/REMARK
REGISTER PRODUCT /DESTINATION
Registers a product in the /HELP
product database. /LOG
/OUTPUT
/REMARK
/SOURCE
(continued on next page)
A-4 The POLYCENTER Software Installation Utility
The POLYCENTER Software Installation Utility
A.1 DCL Help with POLYCENTER
Table_A-1_(Cont.)_DCL_PRODUCT_Commands_and_Qualifiers______
PRODUCT_Command_________________Qualifiers_________________
REGISTER VOLUME /HELP
For a volume containing /LOG
installed products, records a /OUTPUT
change in volume label in the
product database.
REMOVE /HELP
Removes a software product /LOG
from your system and the /OUTPUT
product database. /REMARK
/WORK
SHOW FILE /BRIEF
Displays information about /DEVICE
files created during a /DIRECTORY
software product installation. /FULL
/PRODUCT
SHOW HISTORY /ACTION
Displays a log of actions, /BEFORE
users, and remarks that apply /BRIEF
to a particular product. /FULL
/REMARK
/SINCE
/STATE
/USER
(continued on next page)
The POLYCENTER Software Installation Utility A-5
The POLYCENTER Software Installation Utility
A.1 DCL Help with POLYCENTER
Table_A-1_(Cont.)_DCL_PRODUCT_Commands_and_Qualifiers______
PRODUCT_Command_________________Qualifiers_________________
SHOW PRODUCT /ACTION
Displays information about /BEFORE
the products installed on your /BRIEF
system. /DEVICE
/DIRECTORY
/FILE
/FULL
/LINK
/PATCHED
/SINCE
/SOFTWARE
/STATE
/STATUS
/USER
UNREGISTER PROCESSOR /HELP
Removes a processor from /LOG
a computing facility. Used /OUTPUT
primarily within a DCL command /PURGE
procedure during system /REMARK
startup.___________________________________________________
A.2 Creating and Using a Product Configuration File
Some software products require you to make a set of choices
when you install the product. For example, if you are
installing a tool that checks spelling, you might choose
which languages you want to include. When you use the
POLYCENTER Software Installation utility, you can configure
a product in one of three ways:
o By responding to questions asked during the installation
procedure
o By modifying your choices after you install a product
o By creating a product configuration file (PCF) before
you install the product
A-6 The POLYCENTER Software Installation Utility
The POLYCENTER Software Installation Utility
A.2 Creating and Using a Product Configuration File
By saving your answers in a PCF and using the file for
subsequent installations, you can reduce or eliminate the
questions asked when you install a product. You can also
create multiple PCFs for each product. This allows you
to customize software installations for unique hardware
situations or for different usage patterns within a group.
If you create a PCF as a separate operation, rather than
as part of the installation procedure, you can determine
how your choices are recorded in the PCF. You have the
following options:
o Save your answer.
You can specify that your response to an installation
question (rather than the current default value) be
stored in the PCF.
o Use your answer only once.
You can answer a question without recording your
answer in the PCF. This is useful for responding to
questions that are specific to a single system (such as
a DECnet-Plus node name) or installation (such as a time
setting).
o Defer a question so that it is asked again during a
future installation.
For example, you might want an installer to verify that
a particular response is still valid for the systems on
which each installation is being performed.
o Prevent a question from being asked again.
If you do not defer a question when you create a PCF,
the default response recorded in the PCF is used during
future installations. The installer is not prompted for
the information. This reduces the length and complexity
of the actual installation procedure.
The POLYCENTER Software Installation Utility A-7
The POLYCENTER Software Installation Utility
A.2 Creating and Using a Product Configuration File
A.2.1 Responding to Installation Questions
The following are valid responses to questions asked during
an installation:
o Enter your own value and press Return.
o Press Return to accept a default value.
o Press the defer key F17 or ~D to ask the same question
during future installations.
o Press F18 or ~W if you do not want to record the answer
as the default value in the PCF.
o Press the noexpand key F19 to accept default values for
a subset of options.
To get help on using the POLYCENTER Software Installation
utility script, at the DCL prompt type the following
command:
$ help product
A.3 Verifying Pre-installation Tasks
The POLYCENTER Software Installation utility verifies that
any or all of the following are true, depending on your
product:
o You are logged in to a privileged account.
It is good practice to install software from the system
manager's account with your default device and directory
set to SYS$UPDATE.
o Quotas, system parameters, disk space (and memory) are
adequate for installation.
The POLYCENTER Software Installation utility checks for
the quota values specified in Chapter 1. If it does not
find sufficient disk space, the installation procedure
provides the following options:
- You can restart the installation and specify another
disk to use as an alternate working device for the
temporary working directory.
A-8 The POLYCENTER Software Installation Utility
The POLYCENTER Software Installation Utility
A.3 Verifying Pre-installation Tasks
- You can terminate the installation and then create
more disk space on the system disk. The OpenVMS
VAX Upgrade and Installation Manual, and OpenVMS
Alpha Upgrade and Installation Manual describe how to
use tailoring utilities so you can delete files and
create more disk space.
If you lack sufficient free disk space for installation
or have no other disk to use as an alternate working
device, the installation procedure terminates.
o The minimum version of the OpenVMS operating system
supported by this release is installed.
When the POLYCENTER Software Installation utility detects
a problem in any of these areas, it asks if you want to
continue the installation. If you want to continue, type
YES. If you want to stop the installation, press Return.
A.4 Resolving Conflicts
The POLYCENTER Software Installation utility resolves some
conflicts automatically. For other types of conflicts, the
POLYCENTER Software Installation utility provides feedback
on the nature of the conflict, letting you decide how you
want to proceed.
For example, if the wrong version of DECnet-Plus is
installed, the Software Integrator prompts you to install
the required version.
Similarly, if the correct version of OpenVMS is installed
and you elect not to use the default values when installing
X.25, the Software Integrator warns you that you will need
to use the RECONFIGURE option if you want to change the
version of OpenVMS to be used.
A.5 Determining Installation Progress
As an installation procedure progresses, the system
displays a percentage to indicate how much of the
installation has been completed. For example:
Percent Done: 0%...10%...20%...30%...40%...50%...80%...90%...100%
The following product has been installed:
DEC AXPVMS DECNET_OSI V7.1
The POLYCENTER Software Installation Utility A-9
The POLYCENTER Software Installation Utility
A.5 Determining Installation Progress
Or, as another example:
Percent Done: 0%...10%...20%...30%...40%...50%...80%...90%...100%
The following product has been installed:
DEC VAXVMS DECNET_OSI V7.1
If you started the installation using the /LOG qualifier,
the system displays details of the installation.
A.6 Possible Installation Errors
If the installation procedure fails for any reason, an
error message appears. For example, if the installation of
X.25 fails, the following message appears:
%POLYCENTER Software Installation UtilityINSTAL-E-INSFAIL, The
... installation of X.25 for OpenVMS Alpha Version 1.0 has failed.
An error can occur during the installation if one or more
of the following conditions exist:
o The operating system version is incorrect.
o The prerequisite software version is incorrect.
o Quotas necessary for successful installation are
inadequate.
o Process quotas required by the POLYCENTER Software
Installation utility are inadequate (see Chapter 1).
o The OpenVMS Help library is currently in use.
If the installation fails, you must restart the
installation procedure.
A.7 Reporting Problems
If you encounter a problem while using DECnet-Plus for
OpenVMS or X.25 for OpenVMS Alpha, report it to Digital.
Depending on the nature of the problem and the type
of support you have, you can take one of the following
actions:
o If your software contract or warranty agreement entitles
you to telephone support, call your Digital support
representative.
A-10 The POLYCENTER Software Installation Utility
The POLYCENTER Software Installation Utility
A.7 Reporting Problems
o If the problem is related to the product's user
documentation, send comments and suggestions to the
electronic address at the beginning of this guide.
Include the section and page number of the error.
Review the Software Product Description (SPD) and Warranty
Addendum for an explanation of warranty. If you encounter a
problem during the warranty period, report the problem as
previously indicated.
The POLYCENTER Software Installation Utility A-11
B
_________________________________________________________________
Installing DECnet-Plus for OpenVMS from an InfoServer
B.1 Steps to Installing the Software from an InfoServer
The following steps show you how to access the distribution
kit via an InfoServer and install the software on your
system.
________________________ Note ________________________
The InfoServer does not use DECnet-Plus software to
install software kits over the network.
______________________________________________________
1. Verify that the network hardware is installed and
working properly.
2. Log into the system manager account on your system.
3. Set your system's SCSNODE SYSGEN parameter to a non-
blank value.
________________________ Note ________________________
The InfoServer requires that the SCSNODE parameter
be set to a non-blank value even if your system is
running in a non-clustered environment.
______________________________________________________
4. Check with the InfoServer manager to verify that the
DECnet-Plus for OpenVMS distribution kit is available.
If necessary, the InfoServer manager can refer to the
OpenVMS Layered Products Compact Disc User's Guide that
came with the compact disc distribution kit for specific
details about the disc that contains the distribution
kit.
Installing DECnet-Plus for OpenVMS from an InfoServer B-1
Installing DECnet-Plus for OpenVMS from an InfoServer
B.1 Steps to Installing the Software from an InfoServer
5. Get the distribution kit service name from the
InfoServer manager. For example, CDBIN is used in the
commands in this appendix as a kit service name.
6. Enter the following command to start the InfoServer
client software on your system:
$ @sys$startup:ess$startup disk tape
7. Assuming a service name of CDBIN, enter the following
command to bind the service containing the distribution
kit.
$ mcr ess$ladcp bind cdbin
8. Assuming a service name of CDBIN, enter the following
command to mount the kit device (optional):
$ mount/override=identification dad$cdbin
B.2 Install Commands
To install DECnet-Plus from the CDBIN service, for example,
you would enter:
$ product install decnet_osi /source=dad$cdbin:[dnvosi071.kit]
B-2 Installing DECnet-Plus for OpenVMS from an InfoServer
C
_________________________________________________________________
System Files Loaded During Installation
This appendix lists the system files that are placed on the
system or copied to the system disk during the installation
procedure.
The following table lists the files according to the
directory into which they are copied.
System Files Loaded During Installation C-1
System Files Loaded During Installation
_________________________________________________________________
Directory/Files__________________________________________________
[SYS$LDR]
LES$CHECK_LICENSE.EXE LES$LES_V30.EXE
LES$NETMAN.EXE LES$NETMANLDR.EXE
LES$PROFILE.EXE NET$ALIAS.EXE
NET$ALIAS.STB NET$DRIVER.EXE
NET$DRIVER.STB NET$LOOP_APPLICATION.EXE
NET$MOPS0.EXE NET$MOPS0.STB
NET$OSDRIVER.EXE NET$OSDRIVER.STB
NET$OSVCM.EXE NET$OSVCM.STB
NET$ROUTING_ES.EXE NET$ROUTING_ES.STB
NET$ROUTING_VCM.EXE NET$SESSION_CONTROL.EXE
NET$SESSION_CONTROL.STB NET$TPCONS.EXE
NET$TPCONS.STB NET$TRACER.EXE
NET$TRANSPORT_NSP.EXE NET$TRANSPORT_NSP.STB
NET$TRANSPORT_OSI.EXE NET$TRANSPORT_OSI.STB
SYS$NAME_SERVICES.EXE SYS$NAME_SERVICES.STB
SYS$NETWORK_SERVICES.STB NET$MESSAGE.EXE
NET$ROUTING_IS.EXE SYS$NETWORK_SERVICES.EXE
[SYS$STARTUP]
DNS$CLERK_STARTUP_V.COM DNS$CLERK_STOP_V.COM
DTSS$STARTUP.COM NET$LES_STARTUP.COM
NET$ROUTING_STARTUP.COM NET$STARTUP.COM
[SYSEXE]
ALIAS$SYMBOLS.STB CDI$TRACE.EXE
CDI_CACHE_DUMP.EXE CML.EXE
CTF$DCP.EXE CTF$SERVER.EXE
CTF$SYMBOLS.STB CTF$UI.EXE
CTI$SYMBOLS.STB DECNET_LOC_REGISTER.EXE
DECNET_REGISTER.EXE DECNET_REGISTER_LNO.EXE
DNS$ADVER_V.EXE DNS$ANALYZE_V.EXE
C-2 System Files Loaded During Installation
System Files Loaded During Installation
_________________________________________________________________
Directory/Files__________________________________________________
DNS$CONFIGURE.EXE DNS$CONTROL.EXE
DNSBROWSER.EXE DNSCP.BPT
DNSCP.MBF DSMDECDNS.EXE
DTSS$SERVICE.EXE DTSS$SET_TIMEZONE.EXE
ESIS$SYMBOLS.STB LES$ACP_V30.COM
LES$ACP_V30.EXE LES$FINDPTMAX.EXE
LES$STARTUP_V30.EXE NCL.EXE
NET$ACP.EXE NET$ACP.STB
NET$CCR.EXE NET$DEBUG.EXE
NET$EVENT_DISPATCHER.EXE NET$LES_CONTROL.DAT
NET$LOAD.EXE NET$MGMT.EXE
NET$MIRROR.EXE NET$MOP.EXE
NET$MOP.STB NET$QIO_SYMBOLS.STB
NET$SERVER.COM NET$SERVER.EXE
NET$SYMBOLS.STB NSPTP$SYMBOLS.STB
OSITP$SYMBOLS.STB OSVCM$SYMBOLS.STB
SCL$SYMBOLS.STB TPCONS$SYMBOLS.STB
CTF$CONFIG.EXE NCP.EXE
[SYSHLP.EXAMPLES.DNVOSI]
DNS_ADD_VALUE_TO_ATTRIBUTE.C
[SYSHLP.EXAMPLES.DNVPLUS]
DNS_CREATE_OBJECT.C IPC_SERVER.C
DNS_READ_ATTRIBUTE.C IPC_BACKTRANSLATE.C
IPC_BUILD.COM IPC_CLIENT.C
IPC_COMMON.C IPC_DEF.H
[SYSHLP.EXAMPLES]
CX.C NSAPS.DAT
OSIT$CMD_EXECUTOR.COM OSIT$CMD_EXECUTOR.MAR
OSIT$CMD_SOURCE.CLD OSIT$CMD_SOURCE.MAR
System Files Loaded During Installation C-3
System Files Loaded During Installation
_________________________________________________________________
Directory/Files__________________________________________________
OSIT$ECHO.FOR OSIT$RANDOM.C
OSIT$RECEIVER.PAS OSIT$RECORD_STRUCTURES.FOR
OSIT$STORAGE.FOR OSIT$TRANSMITTER.PAS
SETUP_NCL_KEYPAD.COM SUBX.C
SX.C VMS_OSI.H
XTIUTIL.C XTI_EXAMPLES.COM
[SYSHLP]
CTF$HELP.HLB DECNET_LOC_REGISTER.HLB
DECNET_MIGRATE.HLB DECNET_REGISTER_COMMANDS.HLB
DECNET_REGISTER_FORMS.HLB DNS$CPHELP.HLB
DSMDECDNS.DECW$BOOK LES$SDAHELP.HLB
NCLHELP.HLB NET$CONFIGURE_HELP.HLB
NET$MGMT_HELP.HLB NET$SDA.HLB
DECNET-PLUS-V7_1.RELEASE_NOTES
C-4 System Files Loaded During Installation
System Files Loaded During Installation
[SYSLIB]
CDI$SHR.EXE CDI$SHR.STB
CML.OLB CTF$ALIAS_ANALYZE.EXE
CTF$CSMA-CD_TRACEPOINTS.DAT CTF$CTI_ANALYZE.EXE
CTF$DECNET_TRACEPOINTS.DAT CTF$DNA_ANALYZE.EXE
CTF$DUMP_ANALYZE.EXE CTF$ESEVENT_ANALYZE.EXE
CTF$IEEE8022_ANALYZE.EXE CTF$IEEE8023_ANALYZE.EXE
CTF$KEY.INIT CTF$KEY.TEMPLATE
CTF$MOP_ANALYZE.EXE CTF$NSPTP_ANALYZE.EXE
CTF$NSP_ANALYZE.EXE CTF$NSP_TRACEPOINTS.DAT
CTF$OSITP_ANALYZE.EXE CTF$OSVCM_ANALYZE.EXE
CTF$ROUTING_ANALYZE.EXE CTF$ROUTING_TRACEPOINTS.DAT
CTF$SCL_ANALYZE.EXE CTF$TPCONS_ANALYZE.EXE
CTF$VOTS_ANALYZE.EXE DNS$RTL_V.EXE
DNSDEF_V.ADA DNSDEF_V.BAS
DNSDEF_V.FOR DNSDEF_V.H
DNSDEF_V.MAR DNSDEF_V.PAS
DNSDEF_V.PLI DNSDEF_V.R32
DNSMSG_V.ADA DNSMSG_V.BAS
DNSMSG_V.FOR DNSMSG_V.H
DNSMSG_V.MAR DNSMSG_V.PAS
DNSMSG_V.PLI DNSMSG_V.R32
DSMDECDNS.DAT DSMDECDNS.UID
DTSS$RUNDOWN.EXE DTSS$SHR.EXE
DTSS$SHRD.EXE LES$ACP_CODE_V30.EXE
LES$NETMANSHR.EXE LES$SDA.EXE
NCL$GLOBALSECTION.DAT NCLSHR.EXE
NET$CMISE.EXE NET$EVD_RELAY_FORMATTER.EXE
NET$NISCS_LAA.EXE NET$NISCS_LAA.STB
NET$PROCESS_EMAA.EXE NET$ROUTING_ACPSHR.EXE
NET$SDA.EXE NET_CMISE.H
NET_EXTERNALS.ADA NET_EXTERNALS.BAS
System Files Loaded During Installation C-5
System Files Loaded During Installation
_________________________________________________________________
Directory/Files__________________________________________________
NET_EXTERNALS.FOR NET_EXTERNALS.H
NET_EXTERNALS.L32 NET_EXTERNALS.MLB
NET_EXTERNALS.PAS NET_EXTERNALS.PLI
OSIT$LIBRARY.EXE OSIT$LIBRARY.OLB
OSIT.ADA OSIT.FOR
OSIT.H OSIT.L32
OSIT.MAR OSIT.MLB
OSIT.PAS OSIT.PEN
OSIT.PLI OSIT.R32
OSIT.SDI UTC.H
XTI$DNETSHR.EXE XTI$OSISHR.EXE
XTI$UCXSHR.DECNET-PLUS XTI.DECNET-PLUS
OSITMSG.H
[SYSMGR]
CTF$STARTUP.COM NET$AUTOGEN.COM
DECNET_DNS_REGISTER.COM DECNET_DNS_TOWERS.COM
DECNET_LOC_REGISTER.COM DECNET_REGISTER_DECDNS.COM
DNS$CLERK_CLUSTER.NCL DNS$CONFIGURE.COM
DTSS$CONFIG.COM DTSS$CONFIG_TEMPLATE.DAT
NET$CONFIGURE.COM NET$DNS_CLERK_STARTUP.NCL
NET$DTSS_CLERK_STARTUP.NCL NET$EVENT_LOCAL.TEMPLATE
NET$LOGICALS.TEMPLATE NET$SHUTDOWN.COM
[SYSMSG]
CTF$MESSAGES.EXE DNS$MSG_V.EXE
LES$ACP_MESSAGES_V30.EXE LES$NM_MESSAGES.EXE
OSIT$VOTS_MSG.EXE
[SYSTEST]
OSIT$IVP.CLD OSIT$IVP.EXE
OSIT$IVPINIT.COM OSIT$IVPRESP.COM
C-6 System Files Loaded During Installation
System Files Loaded During Installation
_________________________________________________________________
Directory/Files__________________________________________________
OSIT$IVP_SUPPORT.COM
[SYSUPD]
CTF.CLD
DECNET_MIGRATE.EXE DECNET_MIGRATE_LSE.ENV
DTSS$INSTALL_TIMEZONE_RULE.COM DTSS$TIMEZONE_RULES.DAT
NCP_EMULATOR.TXT NET$CONFIGURE_UPGRADE.COM
NET$CONVERT_DATABASE.EXE NET$PARSE_PREFIX.EXE
NET$FIXUP_IDENTIFIERS.EXE NET$PCSI_INSTALL.COM
NET$REMOVE_EMU.COM___________________NET_ISHFILTER.EXE___________
System Files Loaded During Installation C-7
_________________________________________________________________
Index
A CMIP Management Listener (CML)
_______________________________ defined, 6-12
ADVANCED configuration option, Command procedure
4-1, 7-15 decnet_migrate.exe, 7-15
Alternate node synonym decnet_register.exe, 7-15
directory net$configure.com, 4-4
defining logicals, 7-15 Configuration
format for defining, 7-15 changing basic components,
when used, 7-15 6-18
AUTOGEN utility changing fast components,
running, 1-7 5-6
choosing options, 4-2
B______________________________ cluster alias, 6-12
Backing up system disk DECdns clerk-only system
before running VMSINSTAL, joining LAN DECdns
1-9 namespace, 6-1
Base components DECdns namespace, 7-4
configuring, 7-1 flowchart, 3-5, 3-8
basic, 6-1 list of tasks involved, 3-3
BASIC configuration option, of base components, 7-1
4-1, 7-15 basic, 6-1
invoking, 6-1 of network, 4-1
basic, 6-1 to 6-18
C fast, 5-1 to 5-6
_______________________________ proper sequence of steps,
Characters 3-3
valid for full name, 6-3, requirements, 2-1
6-6 search path information, 7-9
Checklist selection weight, 6-13
installation, 2-2 Configuring
Cluster alias a cluster alias, 6-12
configuring, 6-12 application databases, 6-11
DECnet over X.25, 6-8
Index-1
Configuring (cont'd) DECnet-Plus (cont'd)
DECnet over X.25 (Alpha configuration requirements,
system), 6-8 2-1
DECnet over X.25 (VAX system) installation, 1-1
, 6-9 license requirements, 1-3
NSP and OSI Transports, 6-11 node name, 6-3
the search path, 7-9 decnet_migrate.exe, 7-15
time zone differential decnet_register
factors, 6-11 export file, 7-19
using event dispatcher, 6-11 import file, 7-19
Conventions namespace management tool,
of net$configure, 4-4 7-8
Creating decnet_register.exe, 7-15
DECdns namespace, 7-4 Default
Local namespace, 7-2 node synonym, 6-6
new namespace, 7-3 Dependency
Creating a namespace for DECdns server, 1-4
during initial configuration, for gateways, 1-4
7-3 Directory name services
DECdns, 6-2, 7-2
D______________________________ DNS/BIND, 6-2, 7-7, 7-13
DCL Local namespace, 6-2, 7-1
reply command, 1-9 node full name, 6-3
show device command, 1-6 Disk space requirements
show memory command, 1-7 base components installation,
DCL help, A-2 1-6
command summary, A-3 DECdts server installation,
DECdns clerk-only system 1-6
joining LAN DECdns namespace FTAM installation, 1-6
configuring, 6-1 installation, 1-6
DECdns namespace OSAK installation, 1-6
configuring, 7-4 software installation, 1-6
creating a new namespace, Virtual terminal installation
7-3 , 1-6
full name, 6-3 Displaying information for
valid characters, 6-3, 6-6 search path, 7-10
DECnet over X.25 Distribution kit
configuring (Alpha system), contents, 1-1
6-8 inspecting, 1-1
configuring (VAX system), Distribution media
6-9 mounting, 3-8, 3-9
DECnet-Plus DNA address format, 6-7
configuration default values, DNS version 1
4-5 namespace preparation, 7-17
Index-2
DNS version 1 (cont'd) Installation (cont'd)
using with DECdns Version 2, installed files, 3-11
7-16 list of tasks involved, 3-3
Domain synonym, 7-13 net$configure, how to run,
node, 7-13 4-4
search path naming template OpenVMS for Alpha example,
support, 7-14 3-8
OpenVMS for Alpha flowchart,
E______________________________ 3-5
Error recovery, A-10 OpenVMS for VAX example, 3-9
Export file, 7-19 OpenVMS for VAX flowchart,
decnet_register, 7-19 3-8
possible errors, A-10
F Product Configuration File,
_______________________________ A-6
FAST configuration option prompts and responses, A-8
invoking, 5-1 proper sequence of steps,
Files 3-3
installed, 3-11 recommended order, 3-3
system, C-1 reporting problems, A-10
Full name required system parameters,
node, 6-3 1-7
valid characters, 6-3, 6-6 resolving conflicts, A-9
I system files loaded during,
_______________________________ C-1
Import file, 7-19 time required for, 1-3
decnet_register, 7-19 valid responses, A-8
InfoServer verification of pre-
bind command, B-2 installation tasks, A-8
installing software from, Installation planning
B-1 checklist, 2-2
mount command, B-2 Installation procedure, 3-8 to
start command, B-2 3-11, A-8
Installation Installation questions, A-8
checklist, 2-2 Installed files, 3-11
components included, 3-1
DCL help, A-2 L______________________________
DECnet-Plus for OpenVMS LAN DECdns namespace
(Alpha), 3-3 joining, 6-1
DECnet-Plus for OpenVMS (VAX) LNO
, 3-6 replaced by Local Namespace,
determining progress, A-9 7-1
enabled keys, A-8
from InfoServer, B-1
how to run, A-1
Index-3
Local aliases, 7-14 NCL
Local namespace creating site-specific search
creating, 7-2 path script, 7-11
managing, 7-2 net$configure.com
replaces LNO, 7-1 conventions, 4-4
how to run, 4-4
M______________________________ privileges required to run,
Managing namespaces 1-8
decnet_register tool, 7-8 starting
Migration basic, 6-1
using search path, 7-12 fast, 5-1
Modifying search path Network configuration, 4-1
information, 7-10 basic, 6-1 to 6-18
mount command fast, 5-1 to 5-6
InfoServer, B-2 Node full name, 6-3
Node name
N DECnet-Plus, 6-3
_______________________________ valid characters, 6-6
Name service Node synonym
access features, 7-1 default, 6-6
primary, 7-8 defined, 6-6
search path, 7-8 defining an alternate, 7-15
secondary, 7-8 directories, 7-15
Namespace local aliases, 7-14
DECdns, 7-4 Phase IV-compatible, 6-6
directory path Node type
valid characters in, 6-3, specifying, 6-5
6-6
local, 7-2 O______________________________
management tool OpenVMS operating system
decnet_register, 7-8 checking the version number,
nickname 1-5
valid characters in, 6-3, requirements, 1-3
6-6
node object P
valid characters in, 6-3, _______________________________
6-6 PCF
preparation See Product Configuration
DNS version 1, 7-17 File, A-6
Naming template PCSI
setting up for search path, see POLYCENTER Software
7-12 Installation utility,
support for domain synonyms, A-1
7-14
Index-4
Phase IV
compatible synonym, 6-6 S______________________________
POLYCENTER Software Scripts
Installation utility creating for site-specific
starting the DCL interface, search path, 7-11
3-8, 3-9 Search path, 7-8
using, A-1 configuring, 7-9
Post-installation tasks, A-10 creating site-specific script
to A-11 , 7-11
Prerequisite displaying information, 7-10
backing up system disk, 1-9 modifying information, 7-10
disk space, 1-5 naming template support,
informing users to log out, 7-14
1-9 primary name service, 7-8
required memory, 1-7 secondary name service, 7-8
setting system parameters, setting up naming templates,
1-7 7-12
Privileges using to ease migration,
to run net$configure.com, 7-12
1-8 Selection weight
Product Configuration File configuring, 6-13
creating, A-6 Simple name, 6-6
use, A-6 Software license
PWIP interface, 1-4 checking the version number,
1-5
Q______________________________ requirements, 1-3
Quota SYSGEN utility
verifying disk space, 1-6 autoconfigure all command,
6-10
R______________________________ invoking, 1-7
Registering a node setting parameters, 1-8
resolving problems, 7-19 System
reply command, 1-9 disk space requirements, 1-5
Reporting installation verifying disk space, 1-6
problems, A-10 System files
Routing loaded during installation,
DNA address format C-1
characteristic, 6-7 System parameters
Routing information requirements, 1-7
specifying, 6-5 requirements for cluster
members, 1-8
values, 1-7
Index-5
T______________________________ V______________________________
TCP/IP Valid characters
DECnet and OSI applications for namespace nickname, 6-3,
over, 1-4 6-6
Time zone
configuring differential X______________________________
factors, 6-11 X.25
configuring DECnet over X.25
(Alpha system), 6-8
configuring DECnet over X.25
(VAX system), 6-9
Index-6