Methods of configuring OSI over TCP/IP and DECnet over TCP/IP
    depend upon the operating system in use.

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.

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.