![[Digital logo]](../../IMAGES/DIGITAL-LOGO.GIF){kind=logo}
![[HR]](../../IMAGES/REDBAR.GIF)
This manual describes changes to the software; installation, upgrade, and compatibility information; new and existing software problems and restrictions; and software and documentation corrections.
Revision/Update Information: This is a new manual.
Operating Systems:
OpenVMS Alpha Version 7.1
OpenVMS VAX Version 7.1
Software Versions: DECnet-Plus for OpenVMS Version 7.1
Digital Equipment Corporation Maynard, Massachusetts
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: ACMS, DECdtm, DEC WANrouter, DDCMP, DEC, DECnet, DECNIS, DECserver, DECsystem, DECwindows, DNA, OpenVMS, ULTRIX, VAX, 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.
OSI is a registered trademark of CA Management, 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 through X/Open Company Ltd.
All other trademarks and registered trademarks are the property of
their respective holders.
This manual is intended for all DECnet-Plus for OpenVMS (formerly DECnet/OSI) software users. Read this manual before you install, upgrade, or use Version 7.1 of DECnet-Plus for OpenVMS.
This manual contains the following chapters and applicable release notes:
This manual contains release notes introduced in the current release and notes from previous DECnet versions that still apply to the new release.
For a list of additional documents available that support this version of the DECnet-Plus for OpenVMS software, see the DECnet-Plus for OpenVMS Introduction and User's Guide.
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 |
|
OSSG Documentation Group, ZKO3-4/U08
110 Spit Brook Rd. Nashua, NH 03062-2698 |
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).
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. |
This chapter outlines the new features of the DECnet-Plus for OpenVMS software and provides notes about general restrictions, upgrades, and functionality.
The following notes introduce new features that are available in Version 7.1 of DECnet-Plus for OpenVMS software.
DECnet-Plus for OpenVMS software now supports host-based routing using the routing vector protocol (default), including support for:
Host-based routing is especially useful for those configurations where you need to route from a LAN to a WAN and want to use an existing system to do the routing rather than investing in a dedicated router. Host-based routing is not intended for use in network configurations that have high-throughput requirements.
The DECnet-Plus host-based routing functionality cannot communicate with OSI-only routers and is not intended to replace dedicated routers. The host-based routing functionality does not support Null Internet (the inactive subset of CLNS) or link state routing.
For information about configuring your network to enable DECnet-Plus host-based routing, see Section 2.1 of this document.
DECnet-Plus for OpenVMS now supports a fast configuration option within net$configure that allows a system or network manager to quickly configure a node after upgrading from Phase IV to Phase V (DECnet-Plus).
For information about how to configure your network using the FAST configuration option, see Section 2.2 of this document.
Starting with Version 7.1, in most cases net$configure.com no longer asks you to select a time zone for your DECnet-Plus system. The net$configure procedure now automatically sets the DECdts time zone based on the OpenVMS operating system logical name SYS$LOCALTIME. If SYS$LOCALTIME does not have a value, the net$configure.com procedure prompts you for input to configure DECdts time zones, as in previous versions.
When you use net$configure.com to reconfigure DECnet-Plus, Option 5 on the main menu still provides you with the ability to configure the DECdts time zone settings manually if, for customization purposes, you desire more control over the settings.
The following notes discuss information relevant to DECnet-Plus system upgrades.
If you are upgrading to DECnet-Plus from DECnet Phase IV and have the DEC X.25 Client for OpenVMS Alpha Systems product installed, be aware that there are two X.25 products for OpenVMS Alpha systems:
If you upgrade to DECnet-Plus and want to retain access to X.25, remove the DEC X.25 Client product and install the X.25 product for OpenVMS Alpha systems, which provides both client and native X.25 functionality.
For details about installing and configuring the DEC X.25 product, refer to the DECnet-Plus for OpenVMS Applications Installation and Advanced Configuration and the DEC X.25 Installation and Configuration manuals.
If your system is running the VAX Message Router X.400 Gateway Version 2.3 (MRX) and you upgrade to DECnet/OSI Version 5.7A or later or DECnet-Plus Version 7.1, you need to either reconfigure the message transfer agent (MTA) dictionary used by MRX or use a psi$l3cs.exe image that does not perform X.121 mapping.
With the introduction of X.121 mapping in DECnet-Plus, the incoming DTE (data terminal equipment) address seen by MRX is an NSAP preceded by a digit count. For inbound call verification to work correctly, you must add a new /NETWORK_ADDRESS to each MTA record that contains a DTE address in its existing /NETWORK_ADDRESS. The new /NETWORK_ADDRESS must specify the NSAP as the DTE address.
The existing /NETWORK_ADDRESS is still used for outgoing calls; therefore, do not modify or delete the existing /NETWORK_ADDRESS.
The DTE address must be exactly 14 digits long. If it is less than 14 digits, you must pad it as follows:
If the DTE address is padded with 1s or begins with a 0 (zero), it is preceded by 1052. If the DTE address is padded with 0s or begins with any digit except 0, it is preceded by 1036. Therefore, a DTE address of 0123456789 appears as 105211110123456789 and a DTE address of 1234567890 appears as 103600001234567890.
For example, for an MTA with the MTA_NAME MTA_1 that currently has two /NETWORK_ADDRESS qualifiers of .ENG.X25_QNET%0123456789 and .ENG.X25_QNET%1234567890, you must enter the following commands:
$ run sys$system:mrxman MRXMAN> select mta/mta_name=mta_1 MRXMAN> modify mta/netno=new/network=.eng.x25_qnet%105211110123456789 MRXMAN> modify mta/netno=new/network=.eng.x25_qnet%103600001234567890 MRXMAN> add modified MRXMAN> exit
To use an image that does not perform X.121 mapping, enter the following command:
$ rename sys$common:[sys$ldr]psi$l3cs-nmd.exe - _$ sys$common:[sys$ldr]psi$l3cs.exe
Contact your Digital support representative for help with troubleshooting any problems.
DECnet-Plus Version 7.1 for OpenVMS requires Version 7.0 or Version 7.1 of the OpenVMS operating system.
For IP addresses, session control returns the full name if the synonym is not available regardless of the Session Control Application Node Synonym setting. If neither the full name nor synonym is available, the IP$aa.bb.cc.dd format is returned.
This chapter provides DECnet-Plus for OpenVMS information applicable to installation and configuration.
To enable DECnet-Plus host-based routing, invoke the interactive net$configure.com procedure using either the BASIC or ADVANCED configuration option. The configuration procedure prompts you to choose whether you want the system to be an end node or a router running level 1 or 2, as follows:
* What type of node (Endnode or Router)? [ENDNODE] : Router * Type of routing node (L1 or L2)? [L1] :
To invoke host-based routing, the OpenVMS operating system loads the routing image net$routing_is.exe. If you switch from end node to router, you must reboot the system for the change to take effect.
For complete configuration information, see the DECnet-Plus for OpenVMS Installation and Basic Configuration and DECnet-Plus for OpenVMS Applications Installation and Advanced Configuration manuals.
The net$configure.com procedure now includes a fast configuration option that allows a system or network manager to configure DECnet-Plus (Phase V) quickly when upgrading a node from DECnet Phase IV. The FAST configuration option is a one-time procedure that you start by invoking net$configure.com without specifying the BASIC or ADVANCED parameter.
Note
The FAST configuration option is not supported on a node that is running in an OpenVMS Cluster or where the DECnet-Plus system is also a DECdns server.
The FAST configuration procedure asks very few questions, and you can quickly and easily configure a DECnet-Plus system with full network connectivity.
In the FAST configuration mode, the DECnet-Plus system configures itself by determining the Phase IV and OpenVMS operating system parameters. A local database holds naming information. You can reconfigure the system at a later time to include additional functionality.
Once the FAST configuration option is running, you may decide you do not want to use the FAST option. Net$configure allows you to revert to the standard set of configuration questions if you answer NO to the following question. The system then tells you it is reverting to the standard set of configuration questions.
* Do you want the default configuration? [YES] : NO Reverting to standard set of configuration questions
If you invoke net$configure.com in BASIC or ADVANCED mode, the procedure works as it did prior to Version 7.1 of DECnet-Plus where the FAST configuration option is not a choice.
The following example shows the interactive procedure for the FAST configuration option:
$ @net$configure
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
*** Not supported on cluster nodes.
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] :
%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: BEAVIS
Phase IV Address: 24.89
Phase IV Prefix: 49::
Autoconfiguration of Network Addresses: Enabled
Session Control Address Update Interval: 10
Routing ESHello Timer: 600
Device Information:
Device: ERA (DE422):
Data Link name: ERA-0
Routing Circuit Name: ERA-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 apply this configuration? [YES] :
%NET$CONFIGURE-I-CHECKSUM, checksumming NCL management scripts
* Do you want to start the network? [YES]:
This chapter outlines problems and restrictions that are applicable to network management and includes information about configuration, routing, transitioning to DECnet-Plus, the NSP (Network Services Protocol) transport, and the OSI transport.
With this release of DECnet-Plus, the startup procedure displays a minimum amount of Network Control Language (NCL) information.
If you want to view the complete NCL output for troubleshooting purposes, you can define the following logical name in sys$manager:net$logicals.com:
$ define/system/nolog net$startup_quiet_ncl false
If the net$logicals.com file does not exist on your system, you can create one by renaming the file from the sys$manager:net$logicals.template.
If you want to communicate with Phase IV nodes and your node has an FDDI controller that uses large packets, you must edit the sys$management:net$routing_startup.ncl script to set the Enable-Phase IV-Addressing attribute to true on one FDDI routing circuit.
The RECEIVE BUFFERS attribute of the HDLC LINK entity is not implemented in DECnet-Plus. If you attempt to set the attribute according to the following example, NCL displays the subsequent informational messages:
NCL> set node 0 hdlc link hdlc-0 receive buffers 8 Node 0 HDLC Link HDLC-0 at 1994-04-28-09:51:10.780-04:00I0.113 Command failed due to: set list error Characteristics no such attribute ID: Receive Buffers = 8
HDLC (High-level Data Link Control) allocates the number of receive buffers that it requires; you cannot specify this setting.
If you are using DECnet-Plus, you cannot use DECdtm services on OpenVMS VAX Version 6.0.
Although DECdtm supports DECnet-Plus full names, Rdb and ACMS do not. Rdb and ACMS work only with node synonyms.
The following notes discuss information about transitioning your network from DECnet Phase IV to DECnet-Plus.
Some connection errors might be reported for nodes with DECnet-Plus addresses that are not Phase-IV compatible as well. These errors occur because the network management interface on the OpenVMS operating system does not recognize connections to nodes by the explicit use of a DECnet-Plus address that is not Phase-IV compatible.
If a DECnet-Plus node also has a Phase-IV compatible address, information is collected for it using that address.
DECnet-Plus for OpenVMS supports only those IDPs (initial domain parts) that specify the use of binary syntax DSPs (domain-specific parts). IDPs that specify decimal syntax DSPs are not supported.
The following notes discuss information about OSI transport.
The following list outlines OSI transport problems and their workarounds.
To create X.25 Access filters with the X.25 Native Mode software (formerly VAX P.S.I.) configuration procedure, use the Declaring a Network Process section, as follows:
Do you want X.25 or X.29 programs to specify filter names in $QIO(IO$_ACPCONTROL) calls?
Do you want IO$_ACPCONTROL calls issued by your programs to name any dynamic filters?
Do you want IO$_ACPCONTROL calls issued by your programs to name any static filters?
This chapter contains information applicable to the programming environment.
This version of OSAK includes a programming interface that is backwards compatible with the Version 2.0 programming interface. As a result of more rigorous conformance testing, some additional problems have been uncovered in the Version 2.0 interface.
As a result, applications built against OSAK Version 2.0 might encounter problems when using the Version 2.0 backwards-compatible interface in OSAK Version 3.0 if the applications contain previously untrapped application problems.
You can use 64-bit virtual addresses only with $QIO operations on the NET: devices; you cannot use 64-bit virtual addresses with $QIO operations on the OS: devices.
For transparent task-to-task communication, the $ASSIGN system service accepts only 32-bit addresses and 32-bit descriptors for the DEVNAM parameter when it describes a network connect block (NCB). You can use non-transparent task-to-task operations when you want 64-bit descriptor addresses and 64-bit descriptors to specify an NCB.
For IP addresses, session control returns the full name if the synonym is not available regardless of the Session Control Application Node Synonym setting. If neither the full name nor synonym is available, the IP$aa.bb.cc.dd format is returned.
If the system is configured to use IP addresses, you should prepare the application to receive a node name or address string longer than six characters in length even if Session Control Application Node Synonym= TRUE is specified for the application.
With DECnet-Plus, your application must wait for the completion of the $QIO system service call used to accept the connection before attempting to use the connection.
This chapter provides information applicable to the common directory interface (CDI).
In DECnet/OSI Version 6.2 or later or DECnet-Plus Version 7.1, you can use a logical name table (CDI$SYSTEM_TABLE) to define node synonyms. You should use the following commands to create and examine logical names in a CDI_SYSTEM_TABLE. For example, you can define a system named bks.pub.dec.com as bks according to the following command examples.
DECNET_RELNOTES.HTML OSSG Documentation 5-DEC-1996 09:18:20.94
Copyright © Digital Equipment Corporation 1996. All Rights Reserved.