Trailing-Edge
-
PDP-10 Archives
-
BB-F492Z-DD_1986
-
10,7/703mon/decnet.bwr
There are 17 other files named decnet.bwr in the archive. Click here to see a list.
BEWARE FILE FOR DECNET-10 VERSION 4.0 DISTRIBUTION
Revision: 1
Date: 17 January 1986
COPYRIGHT (c) DIGITAL EQUIPMENT CORPORATION 1986. 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 DISTRIBUTION Page 2
1.0 DECNET MONITOR CODE IN SECTION 2
For KL10s, the monitor code to support DECnet has been moved into
monitor section 2. The load order of monitor modules is very
important. DECnet modules must be loaded immediately following the
COMMON modules (COMMON, COMDEV, COMNET, and COMMOD). CPNSER (if an
SMP system) must be loaded immediately following the DECnet modules.
LINK Version 6 must be used to link this monitor; EDDT Version 44 (or
later) must be loaded with this monitor.
Failure to load the monitor modules in the correct order may cause
incorrect functioning of DECnet and may result in a COMWLO stopcode
(wrong load order) during system startup.
2.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.
3.0 MCB FRONT ENDS
DECnet-10 Version 4.0 requires the MCB software distributed with this
release. To make use of the MCB, the system must be generated as a
DECnet routing node (NETGEN dialog of MONGEN). 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.
4.0 NML COMPATABILITY
The NML distributed with TOPS-10 Version7.03 will not function
correctly under 7.02. The 7.03 NML will automatically run
SYS:NML702.EXE if run under a 7.02 monitor. Due to differences in
NCPTAB between 7.02 and 7.03 we have rebuilt the 7.02 PSI version of
NML using the 7.03 NCPTAB. This NML is being distributed as
NML702.EXE and should be installed on the system.
BEWARE FILE FOR DECNET-10 VERSION 4.0 DISTRIBUTION Page 3
5.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.
6.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.
7.0 SET HOST COMPATABILITY
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 protocol) may be used to circumvent these problems.
BEWARE FILE FOR DECNET-10 VERSION 4.0 DISTRIBUTION Page 4
8.0 REQUIRED PCOS
BEWARE FILE FOR DECNET-10 VERSION 4.0 DISTRIBUTION Page 5
9.0 SUPPLEMENTAL PATCHES
9.1 DECnet Multi-Area Ethernet Support
DECnet-10 Version 4.0 has problems communicating with nodes on the
same Ethernet which are part of a different DECnet area. The
following changes to ROUTER address this problem.
These changes have received only limited testing and should only be
installed by sites which have configured multiple DECnet areas on the
same Ethernet.
File 1) BLKK:ROUTER.MAC[7,7032] created: 0735 16-Jan-86
File 2) DSKC:ROUTER.MAC[10,6026,703A] created: 1124 10-Feb-86
1)28 RTRFD2: JE RMIAP,(MB),RTRFD3 ; If from our NSP then visit count is zero
1) LOAD T1,RMFST,(MB) ;GET THE FIRST BYTE OF MESSAGE
**** ;At RTRFD2
2)28 RTRFD2: JE RMICP,(MB),RTRFD3 ; If from our NSP then visit count is zero
2) LOAD T1,RMFST,(MB) ;GET THE FIRST BYTE OF MESSAGE
**************
1)36 LOAD T2,MBDST,(MB) ; Yes, get the destination address
1) MOVE T3,T2 ; In case we need it later
1) TXZ T2,RN%ARE ; Clear the area number field
1) ADD T2,RTRNRV ; Add reach vector offset
1) TMNN RMTRY,(MB) ; "Try hard" flag set?
1) IFSKP.
1) SETZRO RNCCH,(T2) ; Yes, clear the in-cache flag
1) ENDIF.
**** ;At RTR2R4+5L
2)36 LOAD T3,MBDST,(MB) ; Yes, get the destination address
2) TMNN RMTRY,(MB) ; "Try hard" flag set?
2) IFSKP.
2) LOAD T2,RN%ARE,+T3 ; Yes, get area number of node
2) CAME T2,RTRHOM ; Our area?
2) IFSKP.
2) MOVE T2,T3 ; Get node address
2) TXZ T2,RN%ARE ; Clear the area number field
2) ADD T2,RTRNRV ; Add reach vector offset
2) SETZRO RNCCH,(T2) ; Clear the in-cache flag
2) ENDIF.
2) ENDIF.
**************
1)36 LOAD T4,RCDSL,(RC) ; No, get address of designated router
1) TMNN RNCCH,(T2) ; Is cache flag set?
1) JUMPN T4,RTR2R5 ; Not in cache, use DSR if we have one
1) CAME T3,RTRNAD ; Is this destined for us?
**** ;At RTR2R4+20L
2)36 LOAD T4,RCDSL,(RC) ; Get address of designated router
2) LOAD T2,RN%ARE,+T3 ; Get area number of node
2) CAME T2,RTRHOM ; Our area?
2) JRST RTR2R3 ; No, node not in cache, continue
2) MOVE T2,T3 ; Get node address
2) TXZ T2,RN%ARE ; Clear the area number field
2) ADD T2,RTRNRV ; Add reach vector offset
BEWARE FILE FOR DECNET-10 VERSION 4.0 DISTRIBUTION Page 6
2) TMNN RNCCH,(T2) ; Is cache flag set?
2) RTR2R3: JUMPN T4,RTR2R5 ; Not in cache, use DSR if we have one
2) CAME T3,RTRNAD ; Is this destined for us?
**************
1)76 CALLRET FREMSG ; Not in our area, dump the message
1) RTRIN4: STOR AJ,RMIAP,(MB) ; and store it for the forwarding routine
**** ;At RTIINC+13L
2)76 SETZ AJ, ;Not in our area, no adjacency block
2) RTRIN4: STOR AJ,RMIAP,(MB) ; and store it for the forwarding routine
**************
[End of DECNET.BWR]