Enter your search terms Submit search form
	Web pdp-10.trailing-edge.com

                 BEWARE FILE FOR DECNET-10 VERSION 4.0

                         (TOPS-10 Version 7.04)





                              Revision:  3

                            Date:  May 1989




















COPYRIGHT (c) DIGITAL EQUIPMENT  CORPORATION  1986,  1989.   ALL  RIGHTS
RESERVED.


THIS SOFTWARE IS FURNISHED UNDER A LICENSE AND MAY BE  USED  AND  COPIED
ONLY IN ACCORDANCE WITH THE TERMS OF SUCH LICENSE AND WITH THE INCLUSION
OF THE ABOVE COPYRIGHT  NOTICE.   THIS  SOFTWARE  OR  ANY  OTHER  COPIES
THEREOF  MAY  NOT  BE  PROVIDED OR OTHERWISE MADE AVAILABLE TO ANY OTHER
PERSON.   NO  TITLE  TO  AND  OWNERSHIP  OF  THE  SOFTWARE   IS   HEREBY
TRANSFERRED.

THE INFORMATION IN THIS SOFTWARE IS SUBJECT TO CHANGE WITHOUT NOTICE AND
SHOULD   NOT   BE   CONSTRUED  AS  A  COMMITMENT  BY  DIGITAL  EQUIPMENT
CORPORATION.

DIGITAL ASSUMES NO RESPONSIBILITY FOR THE  USE  OR  RELIABILITY  OF  ITS
SOFTWARE ON EQUIPMENT WHICH IS NOT SUPPLIED BY DIGITAL.

BEWARE FILE FOR DECNET-10 VERSION 4.0                             Page 2


1.0  KS10 SUPPORT

The KS10 is fully supported as a Phase IV ROUTING node.   Since  endnode
support is only available on Ethernet circuits, attempts to run the KS10
as a NONROUTING node will fail.



2.0  MCB FRONT ENDS

To make use of the MCB, the system must be generated as a DECnet routing
node  (MONGEN  dialog).   In  addition, the NCP.CMD file taken by OPR at
system startup must be edited to include the following line:  "SET  NODE
xxx SERVICE NODE VERSION 0" for each MCB.

Failure to use the latest MCB software or to edit NCP.CMD to include the
"SET NODE xxx SERVICE NODE VERSION 0" command will prevent the front end
from functioning.



3.0  MULTI-AREA SUPPORT

With the introduction of multiple DECnet  areas,  there  are  now  cases
where  the DNET. UUO and the monitor level NETWORK and NODE commands are
unable to  return  accurate  DECnet  information.   Since  most  of  the
information  they return is obtained from the system's routing database,
which only exists  for  the  system's  local  area,  no  information  is
available for nodes in other DECnet areas.

For nodes in other areas,  node  reachability  can  only  be  accurately
determined by attempting a network connection.



4.0  ETHERNET ENDNODE SUPPORT

With the introduction of Ethernet endnode support, there are  now  cases
where  the DNET. UUO and the monitor level NETWORK and NODE commands are
unable to  return  accurate  DECnet  information.   Since  most  of  the
information  they return is obtained from the system's routing database,
which doesn't exist in an Ethernet endnode, no information is  available
for nodes other than the host system.

In all cases, node reachability can only  be  accurately  determined  by
attempting a network connection.



5.0  SET HOST COMPATIBILITY

DECnet-10 version 4.0 supports  a  subset  of  the  CTERM  protocol  for
establishing  virtual  terminal  connections  to  other  DECnet Phase IV
systems.  This subset may not be completely transparent to the  terminal
user.   In  many cases SET HOST node/OLD (which uses the unsupported NRT

BEWARE FILE FOR DECNET-10 VERSION 4.0                             Page 3


protocol) may be used to circumvent these problems.



6.0  AUTOPATCH EDITS

The version of MCB being delivered on this tape is the same version that
was  shipped  with  TOPS-10  Version  7.03.   Some  edits to MCB will be
delivered on Autopatch Tape 23  (and  on  subsequent  Autopatch  tapes).
Please  install  these  edits  to  ensure  your  product  remains at the
supported edit level.  Autopatch Tape 23 will not contain any edits  for
NML.   The  version  being  delivered  on  this tape is at the currently
supported edit level.


[End of DECNET.BWR]