DOCSLIB.ORG

Microvax 3800 Vaxserver 3800 Operation Order Number EK-16SAA-OM-001

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Microvax 3800 Vaxserver 3800 Operation Order Number EK-16SAA-OM-001 MicroVAX 3800 VAXserver 3800 Operation Order Number EK-16SAA-OM-001 digital equipment corporation maynard, massachusetts March 1989 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, if any, 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 or equipment that is not supplied by Digital Equipment Corporation or its affiliated companies. © Digital Equipment Corporation 1989. 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: COMPACTape DIBOL RSX DDCMP DSSI RT DEC MASSBUS ThinWire DECmate MicroVAX ULTRIX DECnet PDP UNIBUS DEC server P/OS VAX DECUS Professional VAXcluster DECwriter Q-bus VAXELN DELNI Rainbow VAXlab DELQA ReGIS VMS DEQNA RQDX VT DESTA RSTS Work Processor mOlalla'" ~934 FCC NOTICE: The equipment described in this manual generates, uses, and may emit radio frequency energy. The equipment has been type tested and found to comply with the limits for a Class A computing device pursuant to Subpart J of Part 15 of FCC Rules, which are designed to provide reasonable protection against such radio frequency interference when operated in a commercial environment. Operation of this equipment in a residential area may cause interference, in which case the user at his own expense may be required to take measures to correct the interference. This document was prepared using VAX DOCUMENT, Version 1.1. Contents Preface ix Chapter 1 System Overview 1.1 Front View and Physical Description .................. 1-1 1.1.1 The BA213 Enclosure ............................ 1-9 1.1.1.1 Mass Storage Shelf ........................... 1-11 1.1.1.2 Card Cage .................................. 1-13 1.1.1.3 Power Supplies .............................. 1-16 1.1.1.4 Fans ....................................... 1-18 1.2 Functional Description of Base System ................ 1-18 1.2.1 Base System Components ........................ 1-19 1.2.1.1 Central Processing Unit (CPU) .................. 1-19 1.2.1.2 Console Serial Line Unit (SLU) .................. 1-19 1.2.1.3 Main Memory ................................. 1-19 1.2.1.4 Network Controller. .. 1-19 1.2.1.5 Mass Storage Devices and Controllers . .. 1-20 1.2.2 Optional Components. .. 1-20 1.2.2.1 Mass Storage Subsystems. .. .. 1-21 1.2.2.2 Communications Controllers. .. 1-21 1.2.2.3 Real-Time Controllers. .. 1-23 1.2.2.4 Printer Interfaces. .. 1-23 1.2.2.5 Other Available Options. .. 1-23 1.3 Dual-Host Capability (VMS Systems Only) . .. 1-23 iii Chapter 2 Operating the System 2.1 Before You Operate the System ...................... 2-1 2.2 Switch Settings .................................. 2-1 2.2.1 Normal Operation .............................. 2-1 2.2.2 Special Operation ............................... 2-2 2.3 'furning On the System ............................ 2-4 2.4 Booting the System ............................... 2-5 2.4.1 Autobooting the System .......................... 2-5 2.4.2 Booting the System from Console Mode .............. 2-8 2.5 Using the System ................................. 2-8 2.6 'furning Off the System ............................ 2-9 2.7 Halting the System ............................... 2-9 2.8 Restarting the System ............................. , 2-10 Chapter 3 Operating System Options 3.1 Mass Storage Options .............................. 3-1 3.1.1 RF71 Integrated Storage Elements. .. 3-2 3.1.2 TK70 Tape Drive ............................... , 3-6 3.1.2.1 Design of the Drive ........................... 3-7 3.1.2.2 Labeling a Tape Cartridge ...................... 3-8 3.1.2.3 Write-Protecting a Tape Cartridge· ................ 3-9 3.1.2.4 Tape Cartridge Handling and Storage Guidelines .... 3-11 3.1.2.5 Inserting a Tape Cartridge ...................... 3-11 3.1.2.6 Removing a Tape Cartridge ..................... 3-14 3.1.2.7 Summary of TK70 Tape Drive Controls and Indicator Lights ...................................... 3-16 3.1.3 RV20 Optical Disk Subsystem ..................... 3-17 3.1.4 RRD40/50 Digital Disk Subsystem .................. 3-17 3.1.5 TVS05 Tape Drive .............................. 3-17 3.1.6 TU81-Plus Tape Drive ........................... 3-17 3.2 Communications Controller Options ................... 3-17 3.2.1 Asynchronous Serial Controllers .................... 3-17 3.2.1.1 Without Modem Support ........................ 3-18 3.2.1.2 With Modem Support ........................... 3-19 3.2.2 Synchronous Controllers .......................... 3-20 iv 3.2.3 Network Controllers. .. 3-20 3.3 Real-Time Options . .. 3-21 3.4 Printer Options ......................... .. 3-22 3.5 Adding Options ................................... 3-22 Appendix A Related Documentation Appendix B Reprogramming the KFQSA Storage Adapter B.1 Reprogramming the KFQSA for Dual-Host Systems. .. B-1 B.2 Changing the ISE Allocation Class .................... B-10 B.3 Reprogramming the KFQSA When Adding an R215F Expander . .. B-11 Glossary Index Examples B-1 Entering Console Mode Display . .. B-3 B-2 SHOW DEVICE Display ............................ B-4 B-3 SHOW QBUS Display . .. B-4 B-4 Configure Display ................................. B-5 B-5 Programming the First KFQSA Display ................ B--'-7 B-6 Programming the Second KFQSA Display. .. B-9 B-7 Display for Changing Allocation Class and Unit Number ... B-ll B-8 Entering Console Mode Display ....................... B-14 B-9 SHOW DEVICE Display ........... .. B-15 B-10 SHOW QBUS Display . .. B-15 B-ll Configure Display ................................. B-16 B-12 Programming the KFQSA Display ..................... B-18 v Figures 1-1 MicroVAXlVAXserver 3800 System. 1-2 1-2 Key Positions. 1-3 1-3 Sliding Window Closed. 1-4 1-4 Window Partially Open. 1-5 1-5 Window Fully Open. 1-6 1-6 Removing the Front Panel. 1-7 1-7 Attaching the Front Panel. 1-8 1-8 Front View of the BA213 Enclosure. .. 1-10 1-9 Mass Storage Shelf . .. 1-11 1-10 Card Cage ..................... .. 1-13 1-11 CPU Cover Panel. .. 1-15 1-12 Power Supply. .. 1-17 1-13 System Air Circulation. .. 1-18 1-14 KFQSA-Based Dual-Host Configuration. .. 1-25 2-1 Language Selection Menu. .. 2-3 2-2 Sample Error Summary ............................ , 2-5 2-3 Successful Power-On and Automatic Boot . .. 2-6 2-4 Successful Power-On to List of Bootable Devices . .. 2-6 2-5 Successful Power-On to Console Mode . .. 2-8 3-1 Operator Control Panel. .. 3-3 3-2 Inserting and Removing RF71 Unit J.D. Plugs ........... , 3-5 3-3 TK70 Tape Drive . .. 3-7 3-4 Labeling a Tape Cartridge. .. 3-8 3-5 Tape Cartridge Write-Protect Switch. .. 3-10 3-6 Inserting a Tape Cartridge. .. 3-13 3-7 Removing a Tape Cartridge. .. 3-15 B-1 Dual-Host Configuration Nodes and Addresses (Example). .. B-2 B-2 Expanded System Nodes and Addresses (Example) ........ B-13 vi Tables 2-1 Normal Power-On Indications 2-4 2-2 Device Names ................................... 2-7 3-1 RF71 Controls and Indicators ....................... 3-4 3-2 TK70 Tape Drive Controls. .. 3-16 3-3 TK70 Tape Drive Indicator Lights. .. 3-16 vii Preface This manual describes how to use MicroVAX 3800 and VAXserver 3800 systems. The hardware and software for each of these systems differs slightly, according to the function of the system. The MicroVAX 3800 is a multiuser system that uses the VMS, ULTRIX or VAXELN operating systems, and functions as an end- or full-function node on an Ethernet network. VAXserver systems are single-user systems that use either VMS or ULTRIX operating systems. VAXserver systems that use VMS are DECnet full-function network nodes; systems that use ULTRIX are DECnet end-function nodes. The manual is structured as follows: • Chapter 1 provides an overview of the systems. • Chapter 2 describes how to use each system. • Chapter 3 describes how to use options installed in the systems. • Appendix A lists related documentation. • Appendix B provides instruction on reprogramming the KFQSA module. • A glossary explains key terms. NOTE: VAXserver 3800 systems are designed to offer maximum performance for applications that do not require timesharing. Some ofthe devices referred to in this manual are designed for multiuser systems and may not be suitable for VAXserver systems. Contact your DIGITAL representative if you have any questions about whether use of a specific device is appropriate for your VAXserver system. ix Conventions The following conventions are used in this manual: Convention Meaning A symbol denoting a tenninal key used in text and examples in this book. For example, IBreakl indicates that you press the Break key on your tenninal keypad. IRetuml indicates that you press the Return key on your tenninal keypad. A symbol indicating that you hold down the Ctrl key while you press the Ckey. Bold Bold type is used to indicate user input. For example: »>BOOT MUAO This line shows that the user must type BOOT MUAO at the "»>" prompt. NOTE Provides general infonnation about the current topic. CAUTION Provides infonnation to prevent damage to equipment or software. WARNING Provides infonnation to prevent personal injury. x Chapter 1 System Overview MicroVAX 3800 and VAXserver 3800 systems house all system components in a BA213 enclosure. The enclosure is generally pedestal-mounted and houses the following; • Central processing unit (CPU) module • Memory modules • Communications controllers • Tape drive controller • RF71 Integrated Storage Elements • TK70 tape drive • Power supplies Up to three RF71 Integrated Storage Elements (lSEs) can be mounted inside the BA213 enclosure. This chapter describes the MicroVAX 3800 and VAXserver 3800 system components and their functions.
Load more

Recommended publications
  • CHARON-VAX/XM (Plus) for Windows Is a Third Generation VAX Charon Version 3.2 System Virtualization
    Software Product Description CHVX-021-PD-WI / CHVX-221-PD-WI CHARONTM-VAX/XM (Plus) for Windows CHARON-VAX/XM (Plus) for Windows is a third generation VAX Charon Version 3.2 system virtualization. By emulating a variety of VAX CPUs with different features, CHARON-VAX/XM can Software Concepts International replace a wide range of VAX server 402 Amherst Street hardware with modern Windows servers Suite 300 running CHARON-VAX/XM as a Windows application. Nashua, NH 03063 USA CHARON-VAX/XM provides an exact model of the emulated CPU, on which Tel: 603.879.9022 VAX/VMS, layered software and user applications execute unmodified. No conversion of binary Fax: 603.879.9023 VAX code is required. The Plus option for the CHARON-VAX/XM emulator provides a 3 to 5 www.sciinc.com times improvement of VAX CPU emulation by means of Advanced CPU Emulation mode (ACE). [email protected] The compatibility of the emulator with VAX hardware is tested with the original VAX hardware design tools and diagnostics. Functionality Features CHARON-VAX/XM (Plus) is Provides VAX CPU emulations for: VAXserver 4000-106, MicroVAX 3100-96, MicroVAX designed to prolong the use of the VAX/VMS operating system, layered 3600/3900, VAXserver 3600/3900, MicroVAX II. Only one of these CPUs can execute at a products and user applications. The given time. hardware components emulated by Does not require VAX application code conversion nor application sources. VMS, layered CHARON-VAX/XM (Plus) are software and applications can be directly installed on CHARON-VAX/XM (Plus) and do not designed to operate like their require any modifications.
    [Show full text]
  • Validated Processor List
    NISTIR 4557 Programming Languages and Database Language SQL VALIDATED PROCESSOR UST Including GOSIP Conformance Testing Registers Judy B. Kailey Editor U.S. DEPARTMENT OF COMMERCE National Institute of Standards and Technology National Computer Systems Laboratory Software Standards Validation Group Gaithersburg, MD 20899 April 1991 (Supersedes January 1991 Issue) U.S. DEPARTMENT OF COMMERCE Robert A. Mosbacher, Secretary NATIONAL INSTITUTE OF STANDARDS AND TECHNOLOGY John W. Lyons, Director NIST > NISTIR 4557 Programming Languages and Database Language SQL VALIDATED PROCESSOR LIST Including GOSIP Conformance Testing Registers Judy B. Kailey Editor U.S. DEPARTMENT OF COMMERCE National Institute of Standards and Technology National Computer Systems Laboratory Software Standards Validation Group Gaithersburg, MD 20899 April 1991 (Supersedes January 1991 Issue) U.S. DEPARTMENT OF COMMERCE Robert A. Mosbacher, Secretary NATIONAL INSTITUTE OF STANDARDS AND TECHNOLOGY John W. Lyons, Director lib t TABLE OF CONTENTS 1. INTRODUCTION 1 1.1 Purpose 1 1.2 Document Organization 1 1.2.1 Language Processors 1 1.2.2 Contributors to the VPL 2 1.2.3 Other FIPS Conformance Testing Products 2 1.2.4 GOSIP Registers 2 1.3 FIPS Programming and Database Language Standards 3 1.4 Validation of Processors 3 1.4.1 Validation Requirements 3 1.4.2 Placement in the List 4 1.4.3 Removal from the List 4 1.4.4 Validation Procedures 4 1.5 Certificate of Validation 4 1.6 Registered Report 4 1.7 Processor Validation Suites 5 2. COBOL PROCESSORS 7 3. FORTRAN PROCESSORS 13 4. Ada PROCESSORS 21 5. Pascal PROCESSORS 35 6. SQL PROCESSORS 37 APPENDIX A CONTRIBUTORS TO THE LIST A-1 APPENDIX B OTHER FIPS CONFORMANCE TESTING B-1 APPENDIX C REGISTER OF GOSIP ABSTRACT TEST SUITES C-1 APPENDIX D REGISTER OF GOSIP MEANS OF TESTING D-1 APPENDIX E REGISTER OF GOSIP CONFORMANCE TESTING LABORATORIES E-1 .
    [Show full text]
  • Alpha and VAX Comparison Based on Industry-Standard Benchmark
    Alpha and VAX Comparison based on Industry-standard Benchmark Results Digital Equipment Corporation December 1994 EC-N3909-10 Version 3.0 December 1994 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. Digital conducts its business in a manner that conserves the environment and protects the safety and health of its employees, customers, and the community. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1 )(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227 7013. Copyright© 1994 Digital Equipment Corporation All rights reserved. Printed in U.S.A. The following are trademarks of Digital Equipment Corporation: AlphaServer, AlphaStation, AlphaGeneration, DEC, OpenVMS, VMS, ULTRIX, and the DIGITAL logo. The following are third-party trademarks: MIPS is a trademark of MIPS Computer Systems, Inc. TPC-A is a trademark of the Transaction Processing Performance Council. INFORMIX is a registered trademark of lnformix Software, Inc. OSF/1 is a registered trademark of the Open Software Foundation, Inc. ORACLE is a registered trademark of Oracle Corporation. SPEC, SPECfp92, and SPECratio are trademarks of Standard Performance Evaluation Corporation. MIPS is a trademark of MIPS Computer Systems, Inc. All other trademarks and registered
    [Show full text]
  • Intro VAX-VMS.Pdf
    Introduction to VAX/VMS Bill Degnan Vintage Computer Festival 13 Digital VAX Computers • Digital Introduced VAX family of computers in 1977 • Height of “VAX generation” 1977 through 1987 • VMS Default Operating System designed for all VAX machines VAX is … • DEC’s Line of 32-bit computers • VAX = Virtual Address eXtension • VAX can use memory storage that does not exist as true physical memory • VAX designed to support multiprogramming (a.k.a. multitasking) users running programs simultaneously The VAX Product Line • 11/700 • 8000 Series • MicroVAX VAX 11/700 • Descended from PDP-11 • Share MASSBUS and UNIBUS • 11/780 was the first VAX processor (1978) • 1 Million Instructions per Second VAX 8000 • VAX BUS Interconnect (VAXBI) but will also support UNIBUS • High Performance • Large VAX Systems MicroVAX • Digital Q-22 Bus • Smaller Systems / Less Expensive • Designed for Office Environment VAXstation • Computer Workstation VAX CPU • Intended as single user • Optional GUI graphic display terminal / mouse • Older VAXStations support VT100 / Tektronix 4014 only, newer VAXStations support newer terminals and displays VAX Compatibility • Processing speed is only major difference between VAX computers • Program produced on one VAX will run on another VAX • A VAXcluster is two or more VAX computers networked together, up to 16 DECNet / Digital Network Architecture What is VMS? • VMS (Virtual Memory System) OS • Multiprocessing • Scheduling term used for sharing CPU time among users and processes. • Operates continuously • Handles the virtual memory / programs broken down into “pages” VMS Continued • Each time one uses VAX/VMS the system treats the use as a “process” • VMS checks user account requesting access to a program image or files/directory to see if the required privileges exist to access required memory, processes, CPU, and I/O • Groups with quotas, limits and privileges DEC Terminals • Terminal Printer (for era, 300-1200 baud • Serial Terminal (for era, 4800-19200) • Graphic Terminal (Color, Hi-res, GUI.
    [Show full text]
  • SOFTWARE PRODUCT DESCRIPTION Charon-VAX/XM and /XM PLUS for Linux
    SOFTWARE PRODUCT DESCRIPTION Charon-VAX/XM and /XM PLUS for Linux Product version 4.9 Document version 1 DESCRIPTION Stromasys Charon-VAX/XM and Charon-VAX/XM PLUS are members of the Charon-VAX cross-platform hardware virtualization product family. They are designed to replace MicroVAX II; VAXserver, VAXstation, and MicroVAX models 3600 and 3900; VAX 3100-96; VAX 4000-106; and VAXstation 4000-90 systems by their virtual equivalents running on an x86-64 compatible standard LICENSE PROTECTION computer system. Charon-VAX creates a virtual replica of the original A valid license should be permanently available to Charon in the form DEC VAX hardware, allowing the VAX/VMS operating system and all of a local or network attached USB HASP license dongle, or a software running in that environment to continue to work as before in Software License. The license contains customer specific parameters their existing, binary form. No or only minimal configuration changes and allows remote electronic updates. USB dongles enable a rapid to the original software (operating system, layered products, and switch-over to another host system as the Charon executable itself applications), operational procedures, and management are required. can be installed on multiple systems for disaster recovery purposes. Flexible licensing options allow combining multiple instances of NETWORK different Charon products on a single host system. Charon-VAX virtualizes the Ethernet controllers present in the original VAX hardware. Any protocol supported on these controllers DISTRIBUTION (DECnet, TCP/IP, LAT) will work on the virtualized network link. Charon Release notes, User manuals and Software Product Descriptions are available for download from the Stromasys Product STORAGE Documentation and Knowledge Base web pages.
    [Show full text]
  • DSSI Vmscluster Installation and Troubleshooting Guide
    DSSI VMScluster Installation and Troubleshooting Guide Order Number: EK–410AB–MG. D01 Digital Equipment Corporation Maynard, Massachusetts First Printing, October 1994 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 makes no representation that the use of its products in the manner described in the 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 sofware described in this publication is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. Copyright © Digital Equipment Corporation, 1994. All Rights reserved. The Reader’s Comments form at the end of this document requests your critical evaluation to assist in preparing future documentation. The following are trademarks of Digital Equipment Corporation: Alpha AXP, AXP, DEC, DECnet, Digital, MicroVAX, OpenVMS, VAX, VAX DOCUMENT, VAXcluster, VMScluster, the AXP logo, and the DIGITAL logo. OSF/1 is a registered trademark of Open Software Foundation, Inc. All other trademarks and registered trademarks are the property of their respective holders. FCC NOTICE: The equipment described in this manual generates, uses, and may emit radio frequency energy. The equipment has been type tested and found to comply with the limits for a Class A computing device pursuant to Subpart J of Part 15 of FCC Rules, which are designed to provide reasonable protection against such radio frequency interference when operated in a commercial environment.
    [Show full text]
  • Vaxserver/VAX 4000-Series System Conversion Guide
    VAXserver/VAX 4000-series System Conversion Guide Order Number: EK-VM430-CG. C01 October 1992 This is a revised manual. October 1992 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. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013. © Digital Equipment Corporation 1992. All Rights Reserved. U.S.A. The postpaid Reader’s Comments forms at the end of this document request your critical evaluation to assist in preparing future documentation. The following are trademarks of Digital Equipment Corporation: DECnet, MicroVAX, VAX, VAXcluster, VAXserver, VMS, and the DIGITAL logo. This document was prepared using VAX DOCUMENT, Version 2.0. Contents Preface . vii 1 VAXserver/MicroVAX 3300/3400 Conversion 1.1 Summary of Conversion . 1–1 1.2 Unpacking the Kit . 1–2 1.3 Before Installing the Kit . 1–3 1.4 Installing the Kit . 1–3 2 VAXserver/MicroVAX 3500/3800 Conversion 2.1 Summary of Conversion . 2–1 2.2 Unpacking the Kit .
    [Show full text]
  • VAX VMS at 20
    1977–1997... and beyond Nothing Stops It! Of all the winning attributes of the OpenVMS operating system, perhaps its key success factor is its evolutionary spirit. Some would say OpenVMS was revolutionary. But I would prefer to call it evolutionary because its transition has been peaceful and constructive. Over a 20-year period, OpenVMS has experienced evolution in five arenas. First, it evolved from a system running on some 20 printed circuit boards to a single chip. Second, it evolved from being proprietary to open. Third, it evolved from running on CISC-based VAX to RISC-based Alpha systems. Fourth, VMS evolved from being primarily a technical oper- ating system, to a commercial operat- ing system, to a high availability mission-critical commercial operating system. And fifth, VMS evolved from time-sharing to a workstation environment, to a client/server computing style environment. The hardware has experienced a similar evolution. Just as the 16-bit PDP systems laid the groundwork for the VAX platform, VAX laid the groundwork for Alpha—the industry’s leading 64-bit systems. While the platforms have grown and changed, the success continues. Today, OpenVMS is the most flexible and adaptable operating system on the planet. What start- ed out as the concept of ‘Starlet’ in 1975 is moving into ‘Galaxy’ for the 21st century. And like the universe, there is no end in sight. —Jesse Lipcon Vice President of UNIX and OpenVMS Systems Business Unit TABLE OF CONTENTS CHAPTER I Changing the Face of Computing 4 CHAPTER II Setting the Stage 6 CHAPTER
    [Show full text]
  • Microvax 3100 Model 85/95 Troubleshooting and Diagnostic Information
    MicroVAX 3100 Model 85/95 Troubleshooting and Diagnostic Information Order Number: EK–A0719–TM. B01 June 1994 This manual describes the troubleshooting procedures and diagnostic commands that you can use to solve basic problems with the MicroVAX 3100 Model 85 and Model 95 systems. Revision Information: This manual supersedes EK–A0719–TM. A01 Digital Equipment Corporation Maynard, Massachusetts June 1994 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. FCC NOTICE: This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Any changes or modifications made to this equipment may void the user’s authority to operate this equipment. Operation of this equipment in a residential area may cause interference in which case the user at his own expense will be required to take whatever measures may be required to correct the interference.
    [Show full text]
  • Software Product Description
    Software Product Description PRODUCT NAME: DECnet-ULTRIX, Version 4.0 for RISC and VAX SPD 26.83.08 ULTRIX Network Software (End-node Only) DESCRIPTION functions. The DECnet products and functions avail­ able to users on mixed networks can be determined by DECnet-ULTRIX, Version 4.0 is a Phase IV end­ comparison of the SPDs for the appropriate products. node implementation of Digital Network Architecture (DNA) for the ULTRIX Operating System and ULTRIX Note that incoming connections from all Phase III sys­ Worksystem Software (UWS) for VAX and RISC sys­ tems to DECnet-ULTRIX systems are supported. SUI>­ tems. port for outgoing connections Is limited to the following Phase I II systems: DECnet-VAX and DECnet-RT. In The DECnet-ULTRIX software enables communication addition, DECnet-ULTRIX only supports the connec­ among different networked Digital systems that use the tion of Phase IV routers/routing nodes on the point-to­ DNA Phase IIIIIV· protocols. At the same time, users point lines. and user programs can communicate with non-Digital systems that use the Internet (TCP/IP-based) proto­ Phase IV End Node cols. DECnet-ULTRIX offers the following capabilities: task-to-task communications, network virtual terminal, DECnet-ULTRIX is a Phase IV end-node only imple­ remote file transfer, mail, coexistence with the Internet mentation of DNA and as such, can communicate di­ protocols (TCPIIP-based), and network-wide resource rectly with any other Phase IV node on the Ethernet sharing and management as defined by the DNA pro­ or with any other Phase III/IV· node in the network via tocols.
    [Show full text]
  • Microvax 3100 Models 88/98 User Information
    MicroVAX 3100 Models 88/98 User Information Part Number: EK-MV489-UI. A01 November 1996 This book introduces the MicroVAX 3100 Model 88 and Model 98 systems. Use the information in this book to configure, start, use, update, and troubleshoot your system. You will also find general system information, such as console commands and system care in this book. Revision/Update Information: This is a new manual. Digital Equipment Corporation Maynard, Massachusetts First Printing, November 1996 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. All rights reserved. The following are trademarks of Digital Equipment Corporation: MicroVAX, OpenVMS, ThinWire, VAX, and the DIGITAL logo. The following are third-party trademarks: SIMM is a trademark of Molex Corporation. All other trademarks and registered trademarks are the property of their respective holders. [S3266] Information - Class A FCC NOTICE -- CLASS A DEVICE Warning! This is a Class A product. In a domestic environment this product may cause radio interference in which case the user may be required to take adequate measures. Achtung! Dieses ist ein Gerät der Funkstörgrenzwertklasse A. In Wohnbereichen können bei Betrieb dieses Gerätes Rundfunkstörungen auftreten, in welchen Fällen der Benutzer für entsprechende Gegenmaßnahmen verantwortlich ist.
    [Show full text]
  • The Design of the VAX 4000 Model 100 and Microvax 3100 Model 90 Desktop Systems by Jonathan C. Crowell and David W. Maruska
    The Design of the VAX 4000 Model 100 and MicroVAX 3100 Model 90 Desktop Systems By Jonathan C. Crowell and David W. Maruska 1 Abstract The MicroVAX 3100 Model 90 and VAX 4000 Model 100 systems were designed to meet the growing demand for low-cost, high-performance desktop servers and timesharing systems. Both systems are based on the NVAX CPU chip and a set of VLSI support chips, which provide outstanding CPU and I/O performance. Housed in like desktop enclosures, the two systems provide 24 times the CPU performance of the original VAX-11/780 computer. With over 2.5 gigabytes of disk storage and 128 megabytes of main memory, the complete base system fits in less than one cubic foot of space. The system design was highly leveraged from existing designs to help meet an aggressive schedule. 2 Introduction The demand for low-cost, high-performance desktop servers and timesharing systems is increasing rapidly. The MicroVAX 3100 Model 90 and VAX 4000 Model 100 systems were designed to meet this demand. Both systems are based on the NVAX CPU chip and a set of very large-scale integration (VLSI) support chips, which provide outstanding CPU and I/O performance.[1] Each member of the MicroVAX 3100 family of systems constitutes a low- cost, general-purpose, multiuser VAX system in an enclosure that fits on the desktop. This enclosure supports all the required components of a typical system, including the main memory, synchronous and asynchronous communication lines, thick-wire and ThinWire Ethernet, and up to five small computer system interface (SCSI)-based storage devices.
    [Show full text]