DTJ Number 3 September 1987 - Digital Technical Journals

More documents

Recommendations

Info

New Productsthat challenge forced us to address many areas,from command formats to the structure of thewritten documentation.The DECnet-ULTRIX project met all itsgoals for functionality, performance, and schedule.The completed product was deliveredto Digital's Software Distribution Center only16 months after the project's inception. TheDECnet-ULTRIX software will be followed byother releases, thus adding functions and followingthe migration of the DNA strategy to Phase V.Since the ULTRIX system supports TCPjiP, theaddition of DECnet has provided a natural basefor a DECnet-to-TCP jiP gateway. While notbeing the primary focus for this product, theessential fu nctions required for a gateway arenow present. This fact is significant becauseTCP/IP represents a de facto standard for communicationsprotocols in the UNIX community.The DECnet-ULTRIX product is thus able toprovide a level of integration for the UNIX productsof other vendors into Digital's computingenvironment. Future standards in all areas of OSIwill provide a better degree of integration for theDECnet system and the UNIX community. Untilthey are widely implemented, however, DECnetcapabilities on the ULTRIX system provide avaluable bridge between the two environments.References1. J. Forecast, J. Jackson, J. Schriesheim, "CommunicationsExecutive Implements ComputerNetworks," Computer Design (November1980):'71-75.I2 .. N. La Pelle, M. Segar, arid M. Sylor, "The Evolutionof Network Management Products,"Digital Technical journal (September1986, this issue) : i 17128.3. M. Sylor, "The NMCCjDECnet MonitorDesign,'' Digital Technical journal (September1986, this issue): 129-1 41.AcknowledgmentsThe authors wish to acknowledge the help of themembers of the DECnet-ULTRIX developmentteam, who maintained a high degree of energyand enthusiasm throughout the project. Thesemembers were Kim Buxton, Ed Ferris, KarenGillin, and Bill Spencer. Thanks are also due toSteve Seufert, Faye Allen, Marie Rowntree, TerriBuckley, Pat Nelson, and those individuals in theULTRIX Engineering Group who worked with usthroughout the project.Digital Technical JournalNo. 3 September 1986107
Peter 0. MierswaIDavid J. MittonMartha L. Sp enceThe DECnet-DOS Sy stemThe DECnet-DOS system is an implementation of the Digital NetworkArchitecture standard fo r both Digital's Rainbow personal computersand those of IBM Corporation. This system provides all the services associatedwith a DECnet implementation. These include a choice of communicationtechnologies, adaptive path routing over complex topologies,and network monitoring and management. DECnet-DOS also supp ortstask-to-task programming, remote file transfer and access, remote terminalservices, and network mail services. Those tasks are all performed ona family of low-speed, small-memory processors.Over the past few years the low cost and availabilityof appl ications for personal computers(PC) have been enticing an increasing number ofbusinesses to acquire them. At first, each PC userworked with his own computing resources in astand-alone manner. Eventually, however, theseusers found they wanted to share programs, data,and messages with each other. They also wantedto take advantage of the databases, processingpower, and larger applications on the large computersystems in their companies.Within Digital Equipment Corporation, thereis an engineering group responsible for theimplementation of DECnet software on Digital'ssmall systems. This group believed that a DECnetimplementation for personal computers couldeasily satisfy these users' desire for data and programsharing. In 1984, this grop initiated a projectto implement the Digital Network Architecture(DNA) on personal computers that used the·MS-DOS operating system.The implementation of DECnet software, amature, layered communications architecture,on the personal computers of both Digital andIBM Corporation presented a number of interestingproblems. The team had to work with asynchronousand Ethernet communications controllersand a number of different, relatively slowprocessors, all built by other companies. Theyhad to work within the confines of the MS-DOSsystem, a small operating system with few systemservices capable of supporting multiple communicationtasks in the background. Moreover, theresulting product had to be compatible withthousands of application programs already writ-ten by hundreds of different companies. Andbecause of the volatile nature of the PC business,this product had to provide a wide range of basicnetwork services and layered applications. Sinceproducts for PCs were being rapidly introduced,our goal was to design, implement, and test thisproduct in a fairly short time period.It was clear to the project team that the onlyway to meet the time-to-market goal was to followone strategy. First, the project had to adherestrictly to the DNA architecture, thus eliminatingany temptation to implement new and uniqueprotocols not supported by other existing implementations.Second, the project had to borrowsoftware freely from other products that hadbeen or were being developed.This paper presents a unique model for therapid development of a specific product by utilizingwork done on many other projects. Thecombination of original software and borrowedcode, all within the framework of DNA, allowedus to introduce the DECnet-DOS system in a relativelyshort time period. The overall problemswe encountered and how we solved them arefirst presented within the context of generalissues. Then each layer of the architecture isused as a springboard from which to discuss particularproblems encountered in that layer.General Development IssuesCoding Style and StandardsThe time-to-market goal dictated that both codingand debugging had to be done as quickly aspossible. We immediately agreed upon using a108Digital Tecbnical]ournalNo. 3 September 1986
Page 1 and 2:
Netwo;king ProductsDigital Technica
Page 3 and 4:
Editor's IntroductionRichard W. Bea
Page 5 and 6:
BiographiesRaj Jain Raj Jain gradua
Page 7:
BiographiesDavid R. Oran Dave Oran
Page 10 and 11:
increase the sizes of networks, we
Page 12:
New Productsmust be able to coexist
Page 15 and 16:
A Digital Network Architecture Over
Page 17 and 18:
Page 19 and 20:
Page 21 and 22:
---A Digital Network Architecture O
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
Performance Analysis and Modeling o
Page 29 and 30:
---Performance Analysis and Modelin
Page 31 and 32:
Performance Analysis and Modeling o
Page 33 and 34:
---Performance Analysis and Modelin
Page 35 and 36:
--Performance Analysis and Modeling
Page 37 and 38:
The DECnet/SNA Gateway Product• H
Page 39 and 40:
The DECnetjSNA Gateway ProductFrom
Page 41 and 42:
The DECnetjSNA Gateway Productcommu
Page 43 and 44:
The DECnetjSNA Gateway ProductUSER
Page 45 and 46:
The DECnetjSNA Gateway ProductThe u
Page 47 and 48:
The DECnetjSNA Gateway ProductDECne
Page 49 and 50:
The DECnetjSNA Gateway Productopera
Page 51 and 52:
The DECnetjSNA Gateway ProductSegme
Page 53 and 54:
The DECnetjSNA Gateway Product• O
Page 55 and 56:
WiUiam R. HaweMark F. KempfAlanJ. K
Page 57 and 58: The Extended Local Area Network Arc
Page 75 and 76: Terminal Servers on Ethernet Local
Page 89 and 90: Paul R. Beckjames A. KryckaThe DECn
Page 91 and 92: The DEC net- VA X Product - An Inte
Page 93 and 94: The DECnet- VA X Product - An Integ
Page 95 and 96: The DECnet- VAX Product - An Integr
Page 97 and 98: The DEC net- VA X Product - An Inte
Page 99 and 100: The DECnet- VAX Product - An Integr
Page 101 and 102: john Forecastjames L. jacksonjeffre
Page 103 and 104: The DECnet,ULTRIX SoftwareComponent
Page 105 and 106: The DECnet- ULTRIX Softwarehave pro
Page 107: The DECnet- ULTRIX Softwaresystems.
Page 111 and 112: The DECnet-DOS Systemthat CCB, whic
Page 113 and 114: The DECnet-DOS Systemdata link laye
Page 115 and 116: Tbe DECnet-DOS SystemNDU and the vi
Page 117 and 118: Th e DECnet-DOS Systemconsole can a
Page 119 and 120: The Evolution of Network Management
Page 131 and 132: The NMCCjDECnet Monitor Design5. Op
Page 133 and 134: Th e NMCCjDECnet Monitor DesignFigu
Page 135 and 136: The NMCCjDECnet Monitor DesignKERNE
Page 137 and 138: The NMCCjDECnet Monitor Designinto
Page 139 and 140: The NMCCj/JECnet Monitor DesignThe
Page 141 and 142: The NMCCjDECnet Monitor Designcan s
Page 143 and 144: Editorial StaffEditor - Richard W.
show all

DTJ Number 3 September 1987 - Digital Technical Journals

Create successful ePaper yourself

Delete template?

Save as template?