HP DECnet-Plus for OpenVMS allows you to run DNA and OSI
applications over an IP network backbone. Applications
include those supplied by HP, third-party applications, and
user-written applications.
RFC 1006 and RFC 1859 (formerly known as RFC 1006 Extension)
are standards of the Internet community. RFC 1006 defines
how to implement ISO 8073 Class 0 on top of TCP. Hosts that
implement RFC 1006 are expected to listen on TCP port 102.
RFC 1859 defines how to implement ISO 8073 Transport Class 2
Non-use of Explicit Flow Control on top of TCP. Hosts that
implement RFC 1859 are expected to listen on TCP port 399.
The DECnet over TCP/IP feature (RFC 1859) allows traditional
DECnet applications (such as MAIL, CTERM, and FAL) to accept
IP names and addresses. The OSI applications over TCP/IP
feature (RFC 1006) allows OSI applications (such as FTAM and
VT) to accept IP names and addresses.
1 – Configuring
Methods of configuring OSI over TCP/IP and DECnet over TCP/IP
depend upon the operating system in use.
1.1 – Tru64 UNIX
Running OSI applications over TCP/IP (RFC1006) is automatically
enabled when you install and configure DECnet. To enable DECnet
over TCP/IP (RFC1859), you can either run "decnetsetup advanced"
and answer "yes" to the question "Do you want to configure DECnet
over TCP/IP?" or you can run dxdecnetsetup, select the advanced
format, and select the "Configure DECnet over TCP/IP" option.
1.2 – OpenVMS
If you want to use OSI applications over TCP/IP and/or DECnet
over TCP/IP, invoke NET$CONFIGURE with the ADVANCED option,
and select Option 4 ("Configure Transports") to configure (or
reconfigure) the OSI transport. You can then create a new
OSI transport NCL script (or replace the old script). You
must also include Domain in your Session Control naming search
path by selecting Option 2 to rename your node. This is
described in Section 2 of the Applications Installation and
Advanced Configuration Manual.
For the changes to take effect, either disable the OSI
transport entity (if it exists) and invoke the new OSI
transport NCL script, or reboot the system.
NCL> disable osi transport
NCL> do sys$manager:net$osi_transport_startup.ncl
Also, ensure that TCP/IP is started on the node and that the
PWIP driver is loaded.
When configuring RFC 1006, RFC 1859, or both, each element in
the OSI transport entity's set of RFC 1006 listener ports
attribute corresponds to a TCP listener port. By default,
NET$CONFIGURE sets the OSI transport RFC 1006 listener ports
attribute to { 102, 399 }. Port 102 is required for RFC 1006,
and port 399 is required for RFC 1859.
2 – Additional Template Creation (OpenVMS)
To create RFC 1006 or RFC 1859 templates in addition to the
default templates, use Option 4 under the NET$CONFIGURE
ADVANCED option. When the procedure asks if you want to
create additional OSI templates, answer yes. Then select
RFC 1006 as the network service.
The RFC 1006 port number attribute of the OSI transport
template subentity must contain a TCP port number that is
one of the chosen RFC 1006 or RFC 1859 listener ports. The
default value for the RFC 1006 port number attribute is 102.
If you create an OSI transport template subentity to use
with DECnet over TCP/IP (RFC 1859), then set the RFC 1006
port number attribute of that template to 399.
3 – Disabling (OpenVMS)
DECnet-Plus only attempts to locate TCP/IP if the RFC 1006
listener ports attribute set of the OSI Transport entity is
not empty.
To disable OSI over TCP/IP (RFC 1006) and/or DECnet over
TCP/IP (RFC 1859), you can discontinue listening on the
appropriate port(s). Port 102 applies to RFC 1006, and
Port 399 applies to RFC 1859.
For example, this will disable both RFC 1006 and RFC 1859:
NCL> disable osi transport
NCL> remove osi transport rfc1006 listener ports {102,399}
NCL> enable osi transport