Trailing-Edge
-
PDP-10 Archives
-
BB-X116A-BB_1984
-
decnet.bwr
There are 17 other files named decnet.bwr in the archive. Click here to see a list.
DECnet-10 BEWARE FILE
(1) ------------------------------
A node name must be unique in both ANF and DECnet networks. If you have names
which conflict between the ANF and DECnet networks, you MUST change one or the
other. If there are conflicting names, various cusps will do the wrong thing in
attempting to access these nodes, since there is no way to indicate which
network you mean - The cusp will assume that the names mean the same node, and
arbitrarily pick a network to use.
(2) ------------------------------
The DN20/MCB does not support DMC11 to DMR11 links.
(3) ------------------------------
When both DMC and DMR devices are configured on a DN20/MCB, the CSR addresses of
the DMC devices must numerically precede the CSR addresses of the DMR devices
on the unibus. If this is not the case, your actual network configuration will
be different than your intended configuration.
(4) ------------------------------
The responses to the NCP commands to OPR are not synchronous. This means that a
person, or in particular, a batch file, can give many commands and exit OPR
before the responses come back. Many of the control files have WAIT commands to
OPR to attempt to give time for the response to appear, but these waits may be
insufficient. If you are not getting responses to the NCP commands in the batch
control file NIPTST.CTL, increase the WAIT times, or use the batch control file
as an example and type the commands in manually.
(5) ------------------------------
MCO 10791. A format type 2 connect is of the form [PPN]STRING, where the PPN is
limited by the DECnet architecture to 32 bits. If your site has any PPNs where
either the programmer or project number is greater than 177777, these users
will be unable to use format type 2 connects. We currently do not supply any
programs which use this form of connect, but we probably will in the future
(next release).
(6) ------------------------------
Certain interfaces to the NSP. UUO, particularly in the area of the connect
block, accept zero as a legitimate address pointer (pointing into AC 0). This
only occurs on functions which cause the monitor to return fields to the user
and not on functions for which the monitor reads user data. Users should both
be aware of this unique aspect and also not depend on its existence in future
releases of DECnet-10. Under the current implementation, it is recommended that
the user supply legitimate addresses for all arguments which can be returned by
the monitor.
(7) ------------------------------
If costs on an MCB's line are set via NCP SET command, and the line is inactive
at the time, the DN20/MCB's routing data base gets destroyed, and it will
corrupt your network with bad routing messages. If you need to have costs set,
build them into the image with NETGEN, and do not attempt to change them while
the DN20/MCB is running.
(8) ------------------------------
Account verification (ACTDAE) is required to run DECnet. Specifically, NML and
FAL verify access control by executing QUEUE.s to request that ACTDAE validate
passwords and accounts. If ACTDAE is not running, these cusps will reject all
access control as invalid.
(9) ------------------------------
The command to OPR in the NCP subset "CANCEL QUEUE REQUEST" may cause NML to
crash if given to a queue request that was generated implicitly rather than
explicitly. An example of these queue requests are the ones generated by the
data link watcher after a SET CIRCUIT DTE-0-3 SERVICE ENABLED has been given.
(10) -----------------------------
The unsupported tool DNSNUP (on the customer supported tape) is a program which
locks in core and inserts breakpoints into the monitor to trace messages. Due
to these aspects, the tool is dangerous and stands a chance of crashing your
monitor. This tool should only be run under controlled conditions, where
crashes will not have drastic consequences.
(11) -----------------------------
Several of the DECnet tools (DNTATL, DCNSPY, DCN, NSPTST) search a universal by
the name of NSCAN and require a rel file by the name of NSLIB. To compile and
load these tools, copy NSCAN.UNV=SWIL.UNV and NSLIB.REL=SWIL.REL.
(12) -----------------------------
The LOOP CIRCUIT functionality does not exist in DECnet-10. The DN20/MCB does
support them, but the TOPS-10 system itself (KL or KS) cannot handle either
direction of LOOP CIRCUIT commands across the DTE (in the KL) or KDP (in the
KS).
(13) -----------------------------
The architecture of this DECnet-10 release has been verified with the
following:
DECnet-VAX V3.0
DECnet-RSX V4.0
DECnet-20 V3.0
DECnet-RT V2.0
(14) -----------------------------
Under certain normal circumstances a mcb dmc/dmr circuit may set itself to
state off. This may happen for many reasons. The most common is a DDCMP start
received while the circuit thought it was running. The circuit should shut
itself off and then turn back on again. Instead the circuit stays in the off
state. To correct the problem periodically inspect the circuit states with NCP
and turn circuits found in the off state to on. This should be fixed in
autopatch tape 8.
(15) -----------------------------
The DECNET-E (RSTS) NFT will not communicate with the TOPS-10 NFT. To correct
this problem, apply the following PCO. This wil also correct some problems
with accessing files from VMS systems.
*********************
*PCO #:10-NFT -001*
*********************
[Program Data] System: NFT
Component:NFT
[Validity] 1(5)
[Date Entered] 15-MAR-84
[Programmer] RDH
[Routines] FAL
[Key Words] DIRECTORY RSTS RSX VAX
[Source Before Edit] %1 (000005)
[Source After Edit] %1A (000006)
[Miscellaneous] DOC changes: N
SER/SPR Number:10-000000
Archived: NO
OTHER PRODUCT:
AUTOPATCH TAPE #
************************************************************************
Digital Equipment Corporation 15-MAR-84 Page 2
PCO Log Report
[PCO Write-up]
**********
[SYMPTOM]
1) RSX/VAX/etc. systems attempting a non-wildcarded directory of
a TOPS-10 area fail - either no file is listed (RSX's interpretation)
or a DAP protocol error is flagged (VAX's interpretation).
2) RSTS doesn't work.
**********
[DIAGNOSIS]
1) Name messages not being sent.
2) RSTS doesn't like my default FOP field attributes.
**********
[CURE]
1) Typo in DIRECTORY support (in FAL), "PUSHJ P,FANTY3" should
instead be a "PUSHJ P,FANTY5".
2) Rather than sending a default FOP field, "echo" back to the
remote accessing node whatever FOP is in effect (i.e., whatever FOP
the remote sent to FAL - if no FOP field was sent then a blank FOP
will be returned to the remote).
Digital Equipment Corporation 15-MAR-84 Page 3
PCO Log Report
[FILCOM]
File 1) BLKX:NFT.MAC[7,2,NFT] created: 0929 12-Jan-84
File 2) DSKB:NFT.MAC[226,4563] created: 1023 15-Mar-84
1)13 MINVER==0 ;MAINTENANCE LEVEL
1) CSTVER==0 ;CUSTOMER VERSION
1) EDTVER==5 ;EDIT LEVEL
1) LOC .JBVER
****
2)13 MINVER==1 ;MAINTENANCE LEVEL
2) CSTVER==0 ;CUSTOMER VERSION
2) EDTVER==6 ;EDIT LEVEL
2) LOC .JBVER
**************
1)14 SUBTTL Definitions
****
2)13 ;NFT %1(5) released with 7.02, Spring '84.
2) ;6 RDH 8-Mar-84
2) ; Fix FAL to keep RSTS happy; fix typo in FAL for RSTS/RSX
/VAX
2) ; non-wildcarded directory.
2)14 SUBTTL Definitions
**************
Digital Equipment Corporation 15-MAR-84 Page 4
PCO Log Report
[FILCOM]
File 1) BLKX:FAL.MAC[7,2,NFT] created: 2243 05-Jan-84
File 2) DSKB:FAL.MAC[226,4563] created: 2313 08-Mar-84
1)3 SUBTTL External linkages
****
2)2 ;6 RDH 18-Mar-84
2) ; Fix typo that broke RSX/RSTS/VAX non-wildcarded director
y; Do not
2) ; generate a FOP field (at FFAD28), just "echo" back whate
ver the
2) ; remote has sent (keeps RSTS happy, probably the right th
ing to do
2) ; anyway).
2)3 SUBTTL External linkages
**************
1)54 PUSHJ P,FANTY3 ;FORCE SENDING OF NAME MESSAGES
FOR "DIRECTORY"
1) STOPCD <FANTY failed in FDIR20>
****
2)54 PUSHJ P,FANTY5 ;[6] FORCE NAME MESSAGES FOR "DI
RECTORY"
2) STOPCD <FANTY failed in FDIR20>
**************
1)67 FFAD28: MOVDII T3,FOP,<TEF> ;ASSUME TRUNCATE TO EOF ON CLOSE
1) TXNE P4,IM.CTG ;CONTIGUOUS ALLOCATION WANTED?
1) TFO T3,CTG ;FLAG CONTIGUOUS ALLOCATION REQU
IRED
1) TFNE T3,CTG ;CONTIGUOUS ALLOCATION REQUIRED?
1) TFZ T3,CBT ;YES, THEN NO "BEST TRY OK"
1) MOVE T1,.IOFSB(CO) ;ADDRESS OF FILE SPEC BLOCK
1) MOVE T1,.FXMOD(T1) ;FILE MODS
1) TXNN T1,FX.SUP ;/ERSUPERSEDE?
1) TFO T3,SUP ;NO, OK TO SUPERSEDE
1) MOVDM T3,FOP ;SET MAIN ATTR FILE ACCESS OPTIO
NS FIELD
1) TMO P1,FOP ;AND FLAG IT IN THE MENU TOO
1) FFAD30: MOVE T1,.IODCH(CO) ;GET THE SLAVE FILE/DEVICE CHARA
CTERISTICS
****
2)67 FFAD28: TMO P1,FOP ;[6] "ECHO" WHATEVER FOP THE REM
OTE SENT TO US
2) FFAD30: MOVE T1,.IODCH(CO) ;GET THE SLAVE FILE/DEVICE CHARA
CTERISTICS
**************
[END OF PCO 10-NFT -001]