DECnet-20 Beware File February 1980 VERSION 2 AA-J693A-TM COPYRIGHT (C) 1979,1980 BY DIGITAL EQUIPMENT CORPORATION, MAYNARD, MASS. 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. DECnet-20 V2 Beware File Page 2 1.0 GENERAL INFORMATION Be sure to strictly follow the installation procedures in the DECnet-20 Programmer's Guide and Operations Manual. Installing DECnet-20 V2 is more complex than installing DECnet-20 V1. 1.1 Installation of 32K Word DN20s DECnet-20 V2 for DN20s with only 32K words of memory requires special generation procedures, which are documented in the appendix. DN20 systems with 32K have no additional maintainability features other than what was available in DECnet-20 V1. Thus, NCP (Network Control Program) commands such as "SHOW {COUNTS|STATUS} KNOWN LINES" and "SET STATE LINE line-id", which were unavailable for DECnet-20 V1, will not work for 32K configurations in DECnet-20 V2. 2.0 BEWARE ITEMS 2.1 Acceptance Procedures When running the DECnet acceptance tests, AUTO-DUMP and AUTO-LOAD for the DN20 front end must be disabled. Failure to do so will prevent operation of the loopback tests. Any "node OFFLINE" operator messages that appear during the loopback test should be ignored. There is an error in the DECnet-20 manual in the section describing the line loopback tests for the DECsystem-2020. In step 21, section 10.3.3, the order of two commands should be reversed: NCP>SET LOCAL LOOPBACK DISABLED KDP_0_0 NCP>SET STATE LINE KDP_0_0 OFF 2.2 DN20 System Cannot be Loaded if Generated Incorrectly The hardware configuration options specified for the DN20 system image during network generation must be installed on the DN20 hardware for the system image to be successfully loaded. If hardware is specified that does not exist, the DN20 node will crash a few seconds after it is loaded. It is important to know exactly what line interfaces are installed on the DN20 and generate the DN20 software for no more than this. If you plan to get more line interfaces in the near future, you cannot DECnet-20 V2 Beware File Page 3 generate them in ahead of time. Failure to adhere to this restriction will prevent successful installation of DECnet-20. 2.3 DN20 Crashes When Node Initialization is to Itself If the DN20 attempts to node initialize over a line that is in loopback, it will crash. The crash could be caused by installing a loopback connector or by placing a modem in loopback on a line that is in the ON state. See the suggestions section of the DOC file for the proper method of performing line loopback. 2.4 Patch Required to DECnet-20 for 2020 NETCON issues a warning message at startup and fails to correctly perform a number of the SHOW STATUS commands on a 2020 with only one physical KMC/DUP line. To correct this problem the following patch should be made. This patch is for a system with only DUP_0_0 installed. This patch must not be installed on a system with two DUP lines. In NSPSRV at NDGLI+7 replace NDGLI+7/ MOVEI T3,2 with NDGLI+7/ MOVEI T3,1 2.5 KMC/DUP Problem There is a known problem with the KMC/DUP hardware. The symptoms are that the KMC/DUP line becomes 'hung' and investigation of the EIA interface reveals that the DN20 has Request-to-Send up continuously. The problem is likely to happen whenever the modem on the KMC/DUP line is powered on/off or is disconnected with the line in the ON state. To prevent this problem from happening, turn the line off with the SET STATE LINE line-id OFF command prior to disconnecting or powering off a modem on any line. The line can then be turned on again when the modem is reconnected. The simplest way to recover from this problem, should it occur, is to reload the DN20. DECnet-20 V2 Beware File Page 4 2.6 DN200 Jobs Submitted on Cardreader not Queued Punched cards read at a DN200 remote station may never appear in the batch queue. The cardreader driver, CDRIVE, which is a part of GALAXY, fails to place the card stream into the batch input queue. A one instruction change to the Network Unit Record Device (NURD) module will correct the problem. A new copy of NURD.MAC, which contains the change, has been placed on the RJE-20 distribution tape. To incorporate the new module into your GALAXY system the following procedures should be followed: 1. Restore the contents of the RJE-20 Distribution Tape. 2. Copy the file NURD.MAC from PS: to PS:, or the directory to which you restored the GALAXY source files in Step 20 of Appendix G of the TOPS-20 Software Installation Guide, AA-4195G-TM. 3. Follow the instructions of Appendix G to rebuild and install the LPTSPL and CDRIVE components of the GALAXY system. APPENDIX A NETWORK GENERATION OF DECnet-20 V2 FOR 32K DN20 A.1 OVERVIEW A 32K DN20 has marginal memory capacity for running DECnet-20 V2. To maintain most DECnet-20 V1 functionality, the 72-hour testing (TEST72) capability on a production system has been dropped. Consequently, users having a 32K DN20 will need to generate two DN20 systems, one for use during the acceptance procedures, and another for use during production. The acceptance procedure involving UETP (executing in the TOPS20 system) and TEST72 (executing in the DN20) can be run only by loading a DN20 that has TEST72 configured and does not have the Topology Notification capability. Likewise, a production DN20 system must have the Topology Notification capability and must not have TEST72 configured. A.2 CONFIGURATION CONSTRAINTS There are constraints on configuration options for a 32K DN20. The configuration options are selected by commands to the NETGEN program. The only supported 32K DN20 parameter values are: o HARDWARE - Either 1 DUP11 (not a KMC-DUP combination) or 1 DMC11. [Note: this does NOT mean that you cannot run a DN20 that has KMC-DUP hardware installed, just that the KMC must not be configured.] o SOFTWARE - 20 CCBs, 12 RDBs, and 8 SDBs; all other parameters must be defaulted. The only exceptions to this are identification parameters such as password, node-name, and node-number. NETWORK GENERATION OF DECnet-20 V2 FOR 32K DN20 Page A-2 A.3 EXAMPLES OF NETGEN TYPE-INS During the generation procedure, it is advised that you create a separate directory for each configuration to eliminate any confusion. Examples of various configuration sessions are offered below. A.3.1 Acceptance Procedure Configuration @RUN NETGEN TOPS-20 Network Configurator for DN2x or DN200, Version: V2.2-39 NETGEN>EXCLUDE (from Configuration) KDP (number) 0 NETGEN>INCLUDE (in Configuration) DUP11 (number) 0 NETGEN>CCBS 20 NETGEN>RDBS 12 NETGEN>SDBS 8 NETGEN>EXCLUDE (from Configuration) TASK (type) Topology-Notification NETGEN>SAVE ACC32K NETGEN>FINISH NETGEN>EXIT @ A.3.2 Production Configuration @RUN NETGEN TOPS-20 Network Configurator for DN2x or DN200, Version: V2.2-39 NETGEN>EXCLUDE (from Configuration) KDP (number) 0 NETGEN>INCLUDE (in Configuration) DUP11 (number) 0 NETGEN>CCBS 20 NETGEN>RDBS 12 NETGEN>SDBS 8 NETGEN>EXCLUDE (from Configuration) TASK (type) 72-Hour-Test NETGEN>SAVE PRO32K NETGEN>FINISH NETGEN>EXIT @