PATHWORKS: PC Integration Software

Total Page:16

File Type:pdf, Size:1020Kb

PATHWORKS: PC Integration Software PATHWORKS: PC Integration Software Digital Technical] ournal Digital Equipment Corporation Volume 4 Number 1 Winter 1992 Editorial Jane C. Blake, Editor Kathleen M. Stetson, Associate Editor Helen L. Patterson, Associate Editor Circulation Catherine M. Phillips, Administrator Sherry L. Gonzalez Production Mildred R. Rosenzweig, Production Editor Margaret L. Burdine, Typographer Peter R. Woodbury, Illustrator Advisory Board Samuel H. Fuller, Chairman Robert M. Glorioso Richard]. Hollingsworth John W McCredie Alan G. Nemeth Mahendra R. Patel F. Grant Saviers Victor A. Vyssotsky Gayn B. Winters The Digital Technicaljournal is published quarterly by Digital Equipment Corporation, 146 Main Street ML01-3/B68, Maynard, Massachusetts 01754-2571. Subscriptions to thejournal are $40.00 for four issues and must be prepaid in U.S. funds. University and college professors and Ph.D. students in the electrical engineering and computer science fields receive complimentary subscriptions upon request. Orders, inquiries, and address changes should be sent to the Digital Technicaljournal at the published-by address. Inquiries can also be sent electronically to DTJ®CRL.DEC.COM. Single copies and back issues are available for $16.00 each from Digital Press of Digital Equipment Corporation, 1 Burlington Woods Drive, Burlington, MA 01830-4597 Digital employees may send subscription orders on the ENET to ROVAX::JOURNAL or by interoffice mail to mailstop ML01-3/B68. Orders should include badge number, site location code, and address. All employees must advise of changes of address. Comments on the content of any paper are welcomed and may be sent to the editor at the published-by or network address. Copyright© 1992 Digital Equipment Corporation. Copying without fee is permitted provided that such copies are made for use in educational institutions by faculty members and are not distributed for commercial advantage. Abstracting with credit of Digital Equipment Corporation's authorship is permitted. All rights reserved. The information in the journal is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in the journal. !SSN 0898-901X Documentation Number EY-J825E-DP The following are trademarks of Digital Equipment Corporation: ALL·lN-1, DEC, DEC EtherWorks, DECnet, DECperformance, DECquery, DECwindows, Digital, the Digital logo, DNA, eXcursion, LAT, PATHWORKS, ULTR!X, VAX, VAX C, VAX Performance Advisor, VAX 4000, VAX 6000, VAXcluster, VAXstation, and VAX. 3Com is a registered trademark of 3Com Corporation. Apple, AppleShare, AppleTalk, LocaiTalk, and Macintosh are registered trademarks and QuickStart is a trademark of Apple Computer, Inc. CodeView, Microsoft, MS, and MS-DOS are registered trademarks and Windows is a trademark of Microsoft Corporation. CRAY is a registered trademark of Cray Research, lnc. i386, i486, and Intel are trademarks of Intel Corporation. IBM, Micro Channel, and OS/2 are registered trademarks of International Business Machines Corporation. Motif is a registered trademark of Open Software Foundation, Inc. Motorola and 68000 are registered trademarks of Motorola, Inc. CoverDesign NetWare and Novell are registered trademarks of Novell, Inc. The red and blue threads woven together in our cover design Network General and Sniffer are registered trademarks of represent the many PC clients and server systems that are inte­ Network General Corporation. grated in a network environment by the outstanding "thread" NFS and Sun are registered trademarks of Sun Microsystems, Inc. of PATHWORKS software. PATHWORKS software for the integration UNIX is a registered trademark of UNIX System Laboratories, Inc. of PCs over fANs and WANs is the featured topic in this issue. X/Open is a trademark of X/Open Company Limited. The cover was designed by Kathryn Cimis of the Corporate Book production was done by Digital's Database Publishing Group Design Group. in Northboro, MA. I Contents 6 Foreword Joseph A. Carchidi PATHWORKS: PC Integration Software 8 An Overview of the PAIHWORKSProduct Family Alan Abrahams and David A. Low 15 PAIHWORKS for VMS File Server Edward W Bresnahan and Siu Yin Cheng 24 The Development of an OptimizedPAIHWORKS Transport Interface Philip). Wells 31 Design of the PAIHWORKS for ULTRIXFile Server Anthony). Rizzolo, Elizabeth A. Brewer, and Martha A. Chandler 40 DECnet Transport Architecture Mitchell P Lichtenberg and jeffrey R. Curless 47 Microsoft WindowsNetwork Virtual DeviceDrivers in PATHWORKS for DOS Andrew W Nourse 56 eXcursion for Windows: Integrating Two Windowing Systems Dennis G. Giokas and Andrew T. Leskowitz 68 Capacity Modeling of PAIHWORKS Client-Server Workloads Christopher E. Methot I Editor:JsIntroduction server system on a LAN. However, as Anthony Rizzolo, Beth Brewer, and Martha Chandler explain in their paper, a multiple process model was cho­ sen rather than the single process used in the VMS file server. The authors give their reasons for this different approach as part of a general discussion of the server design and implementation. The network is key to the exchange of data in the PATHWORKS environment, and as is the case for the server software, multivendor systems must be addressed to ensure smooth integration. Mitch Lichtenberg and Jeff Curless describe how Digital Jane C. Blake has extended Microsoft's LA.i\f Manager across a LAN Editor or a WAN by using the DECnet transport protocol as the transport layer. In addition, they present the The integration of personal computers in a net­ reasoning behind the design of the transport com­ work environment is the subject of this issue of the ponent for DOS and OS/2 products, and review Digital Te chnical jo urnal. The software products steps taken to reduce memory usage and improve that bring about this integration are known collec­ performance. tively as PATHWORKS and are derived from Digital's Further details on the integration of DECnet and Personal Computing Systems Architecture. The LAN environments are provided in the paper on two engineering challenge for developers was to inte­ network virtual device drivers for the Microsoft grate a variety of client (PC) and server systems­ Windows environment. As Andy Nourse explains, DOS, Windows, OS/2, Macintosh, VMS, and ULTIUX­ these drivers manage DECnet and NetBIOS opera­ and to ensure that the intricacies of the meshing tions and enable the Windows operating system of these systems remained transparent to PC users. to support peripheral devices, memory resources, In the opening paper, Alan Abrahams and David and software applications. Andy first gives readers Low provide background for the papers that follow background on the Windows operating modes, and by describing the technical aspects of the various then describes the development of the two virtual hardware and software platforms, physical net­ device drivers. works, and protocols that had to be addressed by A significant new application in the PATHW ORKS PATHWORKS developers. They also present an over­ family, called excursion, brings together the capabil­ view of the PATHWORKS components which allow ities of X Windows, DECnet, and the Microsoft envi­ PC users to access network resources. ronment, resulting in the display of both Windows Among the capabilities PATH\VORKS enables, PC and X Windows on the same screen. Dennis Giokas access to files on server systems is one of the most and Andy Leskowitz present the integration philos­ important for users. Two file servers, one for VMS ophy behind the display server and the implemen­ and another for ULTRIX, were developed for this tation of the server architecture. They also relate purpose. A paper on the development of the first of how designers approached the mapping of the win­ these, written by Eel Bresnahan and Siu Yin Cheng, dows in the X and Windows environments. contains an architectural overview of the VMS file The issue concludes with a paper by Chris server. The authors also detail the mapping done to Methot on capacity modeling of PATHWORKS bridge the differences between DOS, OS/2, and VMS client-server workloads. Chris describes a queuing operating systems. In a related paper, Phil Wells analytical model used to understand resource con­ describes performance improvements made in ver­ sumption on the server and the special modeling sion 4.0 of the file server which were achieved by process required in the client-server environment. optimizing the transport interface and the data The paper works through a specific example of the buffering algorithm. He discusses the analysis of model's identification of bottlenecks in the system. server performance for various interface models, The editors thank Star Dargin and Carne! Hoover the implementation of the algorithm in the VlVlS for their help in preparing this issue. server, and test results. Like the VMS file server, the PATHWORKS software for ULTRJX systems integrates PC clients with a 2 Biographies I Alan Abrahams Alan Abrahams is a consultant engineer in the Personal Com­ puting Systems Group Technical Office. He develops management and security strategies for integrating PCs into enterprise-wide networks. Alan joined Digital in 1982 and designed and implemented the PRO/Communications package. Since 1985, he has been the architect responsible for integrating Microsoft's LAN Manager into Digital's PCSA and helped design Digital's NetBIOS emulation and remote boot of MS-DOS systems. Alan received B.S degrees in computational and statistical science and in mathematics from the University of Liverpool. Edward W. Bresnahan Senior software engineer Edward Bresnahan has been developing the PATHWORKS for VMS software since joining Digital's PCSG Server Engineering Group in 1988. He is currently responsible for the design and devel­ opment of a high-performance data cache to be used in future PATHWORKS server products. Prior to this, he was a co-op student at General Electric Company and at Charles Stark Draper Laboratory. Ed holds a B.S.C.S. (1988, hon­ ors) from Northeastern University and is pursuing an M.S.C.S. part-time. ElizabethA.
Recommended publications
  • 1.Operating Systems Overview
    OPERATING SYSTEMS OVERVIEW Contents O.S.Functions The Evolution of O.S. Characteristics of O.S. Basic hardware elements 1 Contents O.S.Components System calls O.S.Structure USER 1 USER 2 USER 3 USER n compiler text interpreter database editor system operating system computer hardware 2 Programming system components compilers loader linker comand interpreter (shell) … O.S. purposes to make a computer more convenient and easier to use to allow more efficient operations of the whole computer system 3 To simplify the program development The O.S. masks the details of the hardware from the programmer and provides the programmer with a convenient interface for using system resources (system calls) To simplify the program development Definition of an extended (virtual) machine 4 VIRTUAL MACHINE ES: DISK CONTROLLER commands: read, write, head motion, ecc… parameters: sector address, number of sectors for each track, ecc… state and error conditions 5 Hardware resource allocation Access to system resources must be controlled and conflicts for resource contention resolved Hardware resource allocation Any user should be provided with required resources, by following suitable policies 6 The details for the management of hardware resources must be hidden to users System calls provide the interface between the application programs and the O.S. 7 THE EVOLUTION OF O.S. Serial processing No O.S. Control by console Scheduling Setup time 8 Simple batch systems Monitor Resident in main memory Control of the program execution “batch” solution
    [Show full text]
  • 14 * (Asterisk), 169 \ (Backslash) in Smb.Conf File, 85
    ,sambaIX.fm.28352 Page 385 Friday, November 19, 1999 3:40 PM Index <> (angled brackets), 14 archive files, 137 * (asterisk), 169 authentication, 19, 164–171 \ (backslash) in smb.conf file, 85 mechanisms for, 35 \\ (backslashes, two) in directories, 5 NT domain, 170 : (colon), 6 share-level option for, 192 \ (continuation character), 85 auto services option, 124 . (dot), 128, 134 automounter, support for, 35 # (hash mark), 85 awk script, 176 % (percent sign), 86 . (period), 128 B ? (question mark), 135 backup browsers ; (semicolon), 85 local master browser, 22 / (slash character), 129, 134–135 per local master browser, 23 / (slash) in shares, 116 maximum number per workgroup, 22 _ (underscore) 116 backup domain controllers (BDCs), 20 * wildcard, 177 backups, with smbtar program, 245–248 backwards compatibility elections and, 23 for filenames, 143 A Windows domains and, 20 access-control options (shares), 160–162 base directory, 40 accessing Samba server, 61 .BAT scripts, 192 accounts, 51–53 BDCs (backup domain controllers), 20 active connections, option for, 244 binary vs. source files, 32 addresses, networking option for, 106 bind interfaces only option, 106 addtosmbpass executable, 176 bindings, 71 admin users option, 161 Bindings tab, 60 AFS files, support for, 35 blocking locks option, 152 aliases b-node, 13 multiple, 29 boolean type, 90 for NetBIOS names, 107 bottlenecks, 320–328 alid users option, 161 reducing, 321–326 announce as option, 123 types of, 320 announce version option, 123 broadcast addresses, troubleshooting, 289 API
    [Show full text]
  • Compaq TCP/IP Services for Openvms Concepts and Planning
    Compaq TCP/IP Services for OpenVMS Concepts and Planning Part Number: AA-Q06TF-TE April 2002 Software Version: Compaq TCP/IP Services for OpenVMS Version 5.3 Operating Systems: OpenVMS Alpha Version 7.2–2, 7.3 OpenVMS VAX Version 7.2, 7.3 This manual describes concepts and planning taskstoprepareyoutousetheCompaqTCP/IP Services for OpenVMS product. Compaq Computer Corporation Houston, Texas © 2002 Compaq Information Technologies Group, L.P. COMPAQ, the Compaq logo, Alpha, OpenVMS, Tru64, VAX, VMS, and the Compaq logo are trademarks of Compaq Information Technologies Group, L.P., in the U.S. and/or other countries. Microsoft, MS-DOS, Visual C++, Windows, and Windows NT are trademarks of Microsoft Corporation in the U.S. and/or other countries. Intel, Intel Inside, and Pentium are trademarks of Intel Corporation in the U.S. and/or other countries Motif, OSF/1, and UNIX are trademarks of The Open Group in the U.S. and/or other countries. Java and all Java-based marks are trademarks or registered trademarks of Sun Microsystems, Inc., in the U.S. and other countries. All other product names mentioned herein may be trademarks of their respective companies. Confidential computer software. Valid license from Compaq required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. Compaq shall not be liable for technical or editorial errors or omissions contained herein. The information is provided “as is” without warranty of any kind and is subject to change without notice.
    [Show full text]
  • Design of the PATHWORKS for ULTRIX File Server by Anthony J
    Design of the PATHWORKS for ULTRIX File Server By Anthony J. Rizzolo, Elizabeth A. Brewer, and Martha A. Chandler 1 Abstract The PATHWORKS for ULTRIX product integrates personal computers with the ULTRIX operating system on a local area network. The software supports both the TCP/IP protocol and the DECnet transport stacks. The design and implementation of the PATHWORKS for ULTRIX file server is based on a client-server model. The server provides file, print, mail, and time services to client PCs on the network. Network file service management is accessed through a PC-style menu interface. The file server's performance was optimized to allow parallelism to occur when the client is generating data at the same time the server is writing the data to disk. 2 Introduction The PATHWORKS for ULTRIX file server connects industry-standard personal computers running Microsoft's server message block (SMB) protocol to Digital computers running the ULTRIX operating system. The server provides a network operating system for PC integration among users of the ULTRIX, DOS, and OS/2 operating systems. The PATHWORKS for ULTRIX server provides file, print, mail, and time services to client PCs on the network. The software is layered on VAX systems and on reduced instruction set computer (RISC) hardware. It supports both the transmission control protocol/internet protocol (TCP/IP) and the DECnet transport stacks. The base product also provides centralized server-based management accessed through a PC-style menu interface. In addition, the PATHWORKS for ULTRIX server implements a network basic I/O system (NetBIOS) naming service that allows clients on the network to obtain the DECnet node address of the server in the DECnet environment or the TCP/IP address of the server in the TCP/IP environment.
    [Show full text]
  • PATHWORKS for DOS Microsoft Windows Support Guide
    PATHWORKS for DOS ' Microsoft Windows Support Guide PATHWORKS for DOS Microsoft Windows Support Guide Order Number: AA-MF87D-TH August 1991 Revision/Update Information: This document supersedes Microsoft Windows Support Guide, order number AA-MF87C-TH. Software Version: PATHWORKS for DOS Version 4.1 Digital Equipment Corporation Maynard, Massachusetts First Published, October 1988 Revised, April 1989, July 1990, October 1990, January 1991, August 1991 The infonnation in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license. No responsibility is assumed for the use or reliability of software on equipment that is not supplied by Digital Equipment Corporation or its affiliated companies. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(l)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013. © Digital Equipment Corporation 1988, 1989, 1990, 1991. All Rights Reserved. Printed in U.S.A. The postpaid Reader's Comments fonn at the end of this document requests your critical evaluation to assist in preparing future documentation. The following are trademarks of Digital Equipment Corporation: ALL-IN-I, DDCMP, DDIF, DEC, DECconnect, DEClaser, DE Cmate , DECnet, DECnet-DOS, DECpc, DECrouter, DECSA, DE C server, DECstation, DECwindows, DECwrite, DELNI, DEMPR, DEPCA, DESTA, Digital, DNA, EtherWORKS, LA50, LA75 Companion, LAT, LN03, LN03 PLUS, LN03 ScriptPrinter, METROWAVE, MicroVAX, PATHWORKS, PrintServer, ReGIS, RMS-ll, RSX, RSX-ll, RT, RT-ll, RX33, ThinWire, TK, ULTRIX, VAX, VAX Notes, VAXcluster, VAXmate, VAXmail, VAXserver, VAXshare, VMS, VT, WPS, WPS.PLUS, and the DIGITAL logo.
    [Show full text]
  • Migrating to SAS 6.08 for Windows: the Merck CANDA Experience Frank S
    Migrating to SAS 6.08 for Windows: The Merck CANDA Experience Frank S. Palmieri, Merck Research Laboratories Rob Rosen, Merck Research Laboratories Wanda Bidlack, Merck Research Laboratories Introduction ineluding a graphical user interface, database querying, In every industry there are computer applications that are graphing. statistical "analysis, document review features, critical for success. In the pharmaceutical industry, one file management utilities, and on-line help. In addition to such "critical success application" is known as a the migration, one of our objectives was to combine our Computer Assisted New Drug Application (CANDA). This existing CANDA features with those represented in is a tool designed to aid federal regulatory agencies in another CANDA system. The best features o~ both reviewing the effects of a drug before it is released to the systems remained and were placed on a common open market. As with any key system, performance and computing platform. We joined a statistical based CANDA, ease of use are important design considerations. Merck developed with SAS 6.07 on a RISC-based UHrix system, has created several CANDAs in the past six years, the and a medical based PC system that used Microsoft tools most recent o~ which involved migrating our latest CANDA for the document handling. Our goal was to create a from an Ultrix platform to a PC running Microsoft (MS) system with three primary features: a user friendly front­ Windows. end, a document review facility that depicts a visual duplicate o~ hard copy documents, and capabilities for Our new application is a large system based on MS Word querying data, creating graphics, and running statistical and the SAS 6.08 for Windows (Base, SCL, SAS/AF, analyses in a timely manner.
    [Show full text]
  • The UNIX Time- Sharing System
    1. Introduction There have been three versions of UNIX. The earliest version (circa 1969–70) ran on the Digital Equipment Cor- poration PDP-7 and -9 computers. The second version ran on the unprotected PDP-11/20 computer. This paper describes only the PDP-11/40 and /45 [l] system since it is The UNIX Time- more modern and many of the differences between it and older UNIX systems result from redesign of features found Sharing System to be deficient or lacking. Since PDP-11 UNIX became operational in February Dennis M. Ritchie and Ken Thompson 1971, about 40 installations have been put into service; they Bell Laboratories are generally smaller than the system described here. Most of them are engaged in applications such as the preparation and formatting of patent applications and other textual material, the collection and processing of trouble data from various switching machines within the Bell System, and recording and checking telephone service orders. Our own installation is used mainly for research in operating sys- tems, languages, computer networks, and other topics in computer science, and also for document preparation. UNIX is a general-purpose, multi-user, interactive Perhaps the most important achievement of UNIX is to operating system for the Digital Equipment Corpora- demonstrate that a powerful operating system for interac- tion PDP-11/40 and 11/45 computers. It offers a number tive use need not be expensive either in equipment or in of features seldom found even in larger operating sys- human effort: UNIX can run on hardware costing as little as tems, including: (1) a hierarchical file system incorpo- $40,000, and less than two man years were spent on the rating demountable volumes; (2) compatible file, device, main system software.
    [Show full text]
  • Tops-10 Monitor Calls Manual, Vol. 1
    TOPS-10 Monitor Calls Manual Volume 1 AA-097 4G-TB October 1988 This manual describes the functions that the monitor performs to service monitor calls from assembly language programs. The TOPS-10 Monitor Calls Manual Is divided Into two volumes: Volume 1 covers the facilities and functions of the monitor; Volume 2 describes the- monitor calls, calling sequences, symbols, and GETTAB tables. This manual supe-rsedes the previous manual of the same name, SOC order number AA-0974F-TB. Operating System: . TOPS-10 Version 7.04 Software: GALAXY Version 5.1 digital equipment corporation maynard, massachusetts First Printing, November 1975 Revised, May 1977 Revised, January 1978 Revised, August 1980 Revised, February 1984 Revised, April 1986 Revised, October 1988 The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license. No responsibility is assumed for the use or reliability of software on equipment that is not supplied by Digital Equipment Corporation or its affiliated companies. Copyright © 1975, 1984, 1988 Digital Equipment Corporation All Rights Reserved. Printed in U.S.A. The Reader's Comments form on the last page of this document requests the user's critical evaluation to assist in preparing future documentation. The following are trademarks of Digital Equipment Corporation: CI DECtape LA50 SITGO-10 DDCMP DECUS LN01 TOPS-10 DEC DECwriter LN03 TOPS-20 DECmail DELNI MASSBUS TOPS-20AN DECnet DELUA PDP UNIBUS DECnet-VAX HSC PDP-11/24 UETP DECserver HSC-50 PrintServer VAX DECserver 100 KA10 PrintServer 40 VAXNMS DECserver 200 KI Q-bus VT50 DECsystem-10 KL10 AeGIS DECSYSTEM-20 KS10 RSX ~BmBDmDTM CONTENTS PREFACE CHAPTER 1 INTRODUCTION TO MONITOR CALLS 1.1 MONITOR CALL SYMBOLS .
    [Show full text]
  • Software Product Description
    Software Product Description PRODUCT NAME: PATHWORKS for VMS, Version 4.0 SPD 30.50.07 (Formerly VMS Services for pes) DESCRIPTION • PATHWORKS for DOS (TCP/IP) - Software required for a personal computer running the DOS Operat­ PATHWORKS for VMS is based on the Personal Com­ ing System to access services of a PATHWORKS puting Systems Architecture (PCSA), which is an ex­ for VMS or PATHWORKS for ULTRIX server via tension of Digital Equipment Corporation's systems and the TCP/IP network transport. (Described in SPD networking architecture that merges the VAX, RISC and 33.45.xx.) personal computer environments. The PATHWORKS product family, developed under the PC SA architecture, • DECnetlPCSA Client: VAXmate - Required software provides a framework for integrating personal comput­ for VAXmates to use the facilities provided by PATH­ ers into an organization's total information system so WORKS for VMS. (Described in SPD 55.10.xx.) that different types of users can share information and PATH WORKS for VMS software allows VAX, MicroVAX, network services across the entire organization. VAXstation and VAXserver computers to act as applica­ The PATHWORKS family of software products includes: tion, data and resource servers to groups of personal computers. By using these server systems, personal • PATHWORKS for VMS - Software that allows a VMS­ computers can share applications, data and resources. based VAX system to act as a file, print, mail and Information can be accessed from local and remote sys­ disk server to DOS and OS/2® personal computers. tems and that information can be applied in DOS or (Described in this document.) OS/2 applications.
    [Show full text]
  • The UNIX Time-Sharing System
    1. Introduction ACM Symposium on Operating Systems Principles There have been three versions of UNIX. The earliest Yorktown Heights, N.Y.: October, 1963 version (circa 1969-70) ran on the Digital Equipment Corporation PDP-7 and -9 computers. The second ver. sion ran on the unprotected PDP.~~'20 computer. hi^ paper describes only the PDP-ll 40 and .'45 [I] system System The UNIX Time- since it is more modern and many of the diferences The UNMO Time-Sharing between it and older UNlx systems result from redesign Dennis M. Ritchie and Ken Thompson Sharing System of features found to be deficient or lacking. Since PDP-l l UNIX became operational in February July, 1974 Dennis M. Ritchie and Ken Thompson 1971, about 40 installations have been put into service; Volume 17, Number 7 Bell Laboratories they are generally smaller than the system described here. Most of them are engaged in applications such as pp. 365-375 the preparation and formatting of patent applications and other textual material, the collection and processing of trouble data from vartous switching machines within the Bell System, and recording and checking telephone service orders. Our own installation is used mainly machines, most notably the PDP-I1 family. for research in operating systems, languages, com- UNIPhas become one of the most widely puter networks, and other topics in computer scienc', known and imitated operating systems of all The genius of Ritchie and Thompson is in UNIX is a general-purpose, multi-user, interactive and also for document preparation. time. Ken Thompson, in working on a pro- their selection of a subset of the most pow- operating system for the Digital Equipment Corporation Perhaps the most important achievement of L.NIX PDP-II/~Oand 11/45 computers.
    [Show full text]
  • Compaq PATHWORKS for Openvms Server Installation and Configuration Guide
    Compaq PATHWORKS for OpenVMS Server Installation and Configuration Guide Order Number: AA–R6G1C–TE October 2001 This guide explains how to install and configure the PATHWORKS for OpenVMS (Advanced Server) software, including the standalone License Server and external authentication software, and the Upgrade utility. Revision/Update Information: This guide supersedes the Compaq PATHWORKS for OpenVMS (Advanced Server) Server Installation and Configuration Guide, Version 6.0B. Operating System: OpenVMS Alpha Version 6.2, 7.2-1, 7.2-2, 7.3 OpenVMS VAX Version 6.2, 7.2, 7.3 Software Version: PATHWORKS V6.1 for OpenVMS (Advanced Server) Compaq Computer Corporation Houston, Texas © 2001 Compaq Computer Corporation COMPAQ, the Compaq logo, OpenVMS, Tru64, DECnet, VAX, VMS, and the DIGITAL logo are trademarks of Compaq Information Technologies Group, L.P. Microsoft, MS-DOS, Windows, and Windows NT are trademarks of Microsoft Corporation. Intel is a trademark of Intel Corporation. UNIX is a trademark of The Open Group. All other product names mentioned herein may be trademarks of their respective companies. Confidential computer software. Valid license from Compaq required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. Compaq shall not be liable for technical or editorial errors or omissions contained herein. The information in this document is provided "as is" without warranty of any kind and is subject to change without notice. The warranties for Compaq products are set forth in the express limited warranty statements accompanying such products.
    [Show full text]
  • PATHWORKS Openvms Alphaserver 4X00 DIGITAL Hitest Notes
    PATHWORKS OpenVMS AlphaServer 4x00 DIGITAL HiTest Notes EK-HPWVA-HN. B01 March 1997 Revision/Update Information: This is a revised manual Version 1.1. Operating System and Version: OpenVMS V6.2-1H3 Digital Equipment Corporation Maynard, Massachusetts First printing December 1996 Revised March 1997 Digital Equipment Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. Possession, use, or copying of the software described in this publication is authorized only pursuant to a valid written license from DIGITAL or an authorized sublicensor. © Digital Equipment Corporation 1996, 1997. All rights reserved. The following are trademarks of Digital Equipment Corporation: AlphaServer, DEClaser, DECnet, DIGITAL, EtherWorks, OpenVMS, PATHWORKS, StorageWorks, VAX, and the DIGITAL logo. The following are third-party trademarks: Microsoft, MS-DOS, Windows 95, and Windows NT are registered trademarks and Windows is a trademark of Microsoft Corporation. UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company Ltd. Oracle is a registered trademark of Oracle Corporation. Table of Contents 1 Introduction....................................................................................1–1 DIGITAL HiTest Suite and Its Advantages...................................................................
    [Show full text]