Vaxserver 3100/Microvax 3100 System Conversion Guide Order Number EK-V3100-CG-001

Total Page:16

File Type:pdf, Size:1020Kb

Vaxserver 3100/Microvax 3100 System Conversion Guide Order Number EK-V3100-CG-001 VAXserver 3100/MicroVAX 3100 System Conversion Guide Order Number EK-V3100-CG-001 Digital Equipment Corporation First Edition, May 1990 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. Copyright © Digital Equipment Corporation 1990 All Rights Reserved. Printed in U.S.A. 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. The following are trademarks of Digital Equipment Corporation: DEC DIBOL UNIBUS DEC/CMS EduSystem VAX DEC/MMS IAS VAXcluster DECnet MASSBUS VMS DECsystem–10 PDP VT DECSYSTEM–20 PDT DECUS RSTS DECwriter RSX This document was prepared and published by Educational Services Development and Publishing, Digital Equipment Corporation. Contents About This Manual v 1 Converting the VAXserver 3100, Model 10 System 1.1 Preparing the System for Conversion . 1–1 1.2 Converting the System . 1–1 2 Converting the VAXserver 3100, Model 20 System 2.1 Preparing the System for Conversion . 2–1 2.2 Converting the System . 2–1 A Module Return Procedure and Forms A.1 Return Procedure . A–1 A.2 Digital Forms . A–2 A.3 CAS District Offices . A–11 Figures 1–1 System Cover Removal . 1–2 1–2 SCSI Port Connector Removal . 1–3 1–3 DC Power Harness Plug . 1–3 1–4 System Module Cable . 1–4 1–5 Drive Mounting Shelf Removal . 1–5 1–6 DSH32-B Module Removal . 1–6 1–7 Memory Expansion Module Removal . 1–7 1–8 System Module Removal . 1–8 1–9 Ethernet ID ROM Location . 1–9 1–10 PTT and PCL Label Location . 1–10 iii iv Contents 2–1 System Cover Removal . 2–2 2–2 SCSI Bus Cable and DC Power Harness Plug . 2–3 2–3 Upper Drive Mounting Shelf Removal . 2–4 2–4 SCSI Port Connector Removal . 2–5 2–5 System and DSH32-B Module Cable . 2–5 2–6 Lower Drive Mounting Shelf Removal . 2–6 2–7 DSH32-B Module Removal . 2–7 2–8 Memory Expansion Module Removal . 2–8 2–9 System Module Removal . 2–9 2–10 Location of Ethernet ID ROM . 2–10 2–11 PTT and PCL Label Location . 2–11 About This Manual This conversion guide describes how to install the conversion kit on either the VAXserver 3100 model 10 or model 20 system. Conversion Kit Contents The following table lists the contents and part numbers of the conversion kit 310XR-AC, and 310XR-AE. Part Number 310XR Contents AC AE QL-001AP-BM VMS 1-5 User’s License 1 - QL-D04AP-AA DECnet-VAX End Node License 1 - QL-VEYAP-BC ULTRIX-32 2 User Upgrade - 1 QL-VEYAP-BE ULTRIX-32 8 User Upgrade - 1 QL-716AP-AA DECnet-ULTRIX-32 License - 1 54-18856-01 Time Share CPU Module 1 1 EK-V3100-CG-001 System Conversion Guide 1 1 36-31684-01 Label, PTT, Model 10 1 1 36-31381-01 Label, PTT, Model 20 1 1 36-15946-01 Product Conversion Label 1 1 36-26123-xx Return Labels 1 1 74-37642-07 Medallion, MicroVAX 3100 1 1 9907976-09 CPU Box 1 1 9907952-01 External Box 1 1 9907092-04 Anti-static bag 1 1 The Return Labels are for conversion kits being installed in the U.S. only v vi About This Manual Customer Responsibilities The customer should not install this conversion kit unless they are a qualified self-maintenance customer. Only qualified maintenance personnel should perform the installation procedure. Call the Digital Customer Services office to schedule a system conversion. It is the customer’s responsibility to perform a software backup before the Digital Customer Services representative arrives at the site. When a conversion is complete, return the old system module to Digital for credit. Appendix A contains forms that need to be completed by the Customer Services representative and signed by the representative as well as by the customer. Digital Customer Services Responsibilities To save time, the Digital Customer Services representative should contact the customer and make arrangements to have the customer’s software backed up before arrival on site. Software installation, conversion and testing are not described in the hardware conversion procedure, but such tasks are part of the overall system conversion. The customer should contact a Digital sales representative to transfer an existing software product services contract to the MicroVAX/VAXserver Systems group. After the representative installs the conversion kit, they are to complete the following forms and then remove them from this document by tearing them along the perforated line. The following forms are in Appendix A. • Customer Services Worksheet • Installation Receipt–Customer Copy • Installation Receipt–Customer Services Copy • Return Material Worksheet The Digital Customer Services representative should give the customer the signed Installation Receipt - Customer Copy. They should include the signed Customer Services Copy with the system module that is being returned to Digital to ensure that the customer receives credit. A self-adhesive mailing label is contained within this kit. Peel off the label and attach it to the package containing the system module to be returned. About This Manual vii Convention The following convention was used in this document. Convention Meaning NOTE Provides general information. CAUTION Provides information to prevent damage to equipment or software. Read carefully. Related Document MicroVAX 3100 and VAXserver 3100 Maintenance Guide, part number EK-A0372-MG. 1 Converting the VAXserver 3100, Model 10 System This chapter describes how to convert the VAXserver 3100, model 10 system to a MicroVAX 3100, model 10 timesharing system. 1.1 Preparing the System for Conversion To prepare the system for conversion: Unpacking the Contents When unpacking the contents from the conversion kit, keep the packing material so that you may use it when packaging and returning the old module to Digital for proper credit (if applicable). 1.2 Converting the System To convert the system, perform the procedures in the following sections: Shut Down the System 1. Shut down the operating system software and halt the system. 2. Turn off the power to the system box and any expansion boxes. Open the System Box CAUTION Make sure you are wearing an antistatic wrist strap connected to a grounded antistatic workstation or an antistatic mat before you handle the system field replaceable units (FRUs). 1. Disconnect all cables and loopbacks that are connected to the system unit and place any expansion boxes off to the side and away from the system unit. 1–1 1–2 Converting the VAXserver 3100, Model 10 System 2. Loosen the two screws on the rear bezel of the system box (Figure 1–1). Cover Screw Locations MLO-003278 MA-0458-90.DG Figure 1–1 System Cover Removal 3. Slide the top cover forward and up off the system box. Remove the Drive Mounting Shelf 1. Remove the SCSI "B" external port connector from the rear panel by removing the two mounting screws on the rear of the system unit (Figure 1–2). Converting the VAXserver 3100, Model 10 System 1–3 ASYNC SYNC EXTERNAL 2 SCREWS PORT PORT SCSI PORT ON/OFF SWITCH THICKWIRE THINWIRE TERMINAL MODEM PORT PORT LINES PORT MA-0453-90.DG Figure 1–2 SCSI Port Connector Removal 2. Disconnect the dc power harness plug from J1 on the H7821 power supply (Figure 1–3). J1 Unused Distribution SCSI-B Board Power SCSI-A DSH32-B Supply System Module To FDI Board for RX23 Option Additional Power Connector for RX23 RZ2X TZ30, RX23 Unused or RZ2X Drive Drive Mounting Shelf MLO-003373 MA-0465-90.DG Figure 1–3 DC Power Harness Plug 1–4 Converting the VAXserver 3100, Model 10 System 3. Disconnect the system module cable from the distribution module (Figure 1–4). 4. Disconnect the DSH32-B module cable (if applicable) from the distribution module (Figure 1–4). SCSI-B Cable DSH32-B Communications Module Cable Captive Screws SCSI-A Cable System Module Cable MLO-003286 MA-0467-90.DG Figure 1–4 System Module Cable 5. On the drive mounting shelf, loosen the four captive screws on the top, and the three panhead screws located on the right-hand side of the shelf (Figure 1–5). Converting the VAXserver 3100, Model 10 System 1–5 Captive Screws (2) Captive Screws (2) Panhead Screws (3 Loosened) MLO-003279 MA-0456-90.DG Figure 1–5 Drive Mounting Shelf Removal 6. Slide the drive mounting shelf forward, then lift the shelf from the system unit and gently set it aside.
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]
  • Software Product Description
    Software Product Description PRODUCT NAME: Uniplex™ Business Software for ULTRIX SPD 32.83.01 on RISC, Version 7.00c DESCRIPTION • On-screen print effects Uniplex Business Software is a product of Uniplex Lim- • Paragraph and page numbering ited and distributed under Digital Equipment Corpora- • Decimal tab and column align tion’s Terms and Conditions. • Headers, footers, footnotes and endnotes Uniplex Business Software is a suite of UNIX™-based • Line and box drawing, sketch mode office applications designed to handle routine office ac- tivities. Uniplex II Plus, the base program for all Uniplex • Auto backup and auto save Business Software, provides word processing, spread- • Document boilerplate merge sheet, database and business graphics. In addition to Uniplex II Plus, several optional applications can be • Flexible search and replace added to expand overall office functionality. • Automatic index and table of contents generation Uniplex Advanced Office System (AOS) adds electronic • Spelling dictionary and thesaurus mail, time manager, personal organizer, card index and report writer. Uniplex Advanced Graphics System • Flexible printer formatting on Digital printers (AGS) provides charting, graphing and freehand draw Spreadsheet capabilities. Uniplex Additional Dictionary Pack (ADP) provides support for multiple dictionaries which enables The Uniplex spreadsheet provides the user with a users to spellcheck documents in various languages. choice of using either the Uniplex interface or an in- dustry standard interface (ISSI) similar to that used by Uniplex Business Software uses consistent commands, other leading spreadsheet products. Data can imported menus and softkeys throughout all applications. Users from Lotus® 1-2-3, DIF or ASCII files into a matrix as may "hot-key" between several applications or between large as 1024 rows x 256 columns.
    [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]
  • Technical Description of the DEC 7000 and DEC 10000 AXP Family 1
    Technical Description of the DEC 7000 and DEC 10000 AXP Family 1 Abstract The DEC 7000 and DEC 10000 products are mid-range and mainframe Alpha AXP system offerings from Digital Equipment Corporation. These machines were designed to meet the needs of large commercial and scientific applications and therefore are high-performance, expandable systems that can be easily upgraded. The DEC 7000 and 10000 systems utilize the DECchip 21064 microprocessor operating at speeds up to 200 MHz. The high-speed chips, large caches, multiprocessor system architecture, high-performance backplane interconnect, and large memory capacity combine to create mainframe-class performance with a cost and size previously attributed to mid-range systems. The design of the DEC 7000 and 10000 systems provides a high-end platform and system environment for multiple generations of Alpha AXP chips. This platform, combined with a multiprocessor architecture, yields a multidimensional upgrade capability that will allow the system to meet users' needs for several years. System upgrade can take place by adding processors, replacing existing processors with next-generation processors, or both. This upgrade capability ensures stability to the system in terms of the physical and fiscal aspects of the end user's computing environment. The DEC 7000 and DEC 10000 systems are the logical follow-on products of the highly successful VAX 6000 family.[1] The new systems are capable of supporting either VAX processors or Alpha AXP processors. The capability to upgrade from a VAX processor to an Alpha AXP processor without changes to the system is essential for minimal disruption of large commercial applications.
    [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]
  • 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]
  • Decstation/Decsystem 5000 Model 200 Series Maintenance Guide
    EK-PM38C-MG-002 DECstation/DECsystem 5000 Model 200 Series Maintenance Guide digital equipment corporation maynard, massachusetts First printing, January 1992 Second printing, April 1993 © Digital Equipment Corporation 1993. USA This equipment 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. 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. The following are trademarks of Digital Equipment Corporation: DEC PDP VAXBI DECnet ThinWire VAXcluster DECstation TURBOchannel VAXstation DECsystem ULTRIX VMS DECUS ULTRIX-32 VT MicroVAX UNIBUS MicroVMS VAX dt Contents About This Guide .......................................... xix Part I Hardware 1 System Overview System Hardware Configurations . .................... 1–2 System Unit ......................................... 1–4 Controls and Indicators ............................ 1–6 External System Unit Connectors ................... 1–8 Internal Base System Module Connectors . ........... 1–10 Hardware Options and Peripherals . .................... 1–12 CPU Module Description ........................... 1–13 System Boot ROM ................................. 1–13 Memory Modules .................................
    [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]
  • 1 Booting the Decstation/Decsystem 5000 Model 200 Series Processor
    EK-FSFCO-WS ULTRIX/ULTRIX Worksystem Software Boot Commands for DECstation/DECsystem 5000 Model 200 Series Processors Dear Digital Customer, Because of changes in the ®rmware of the DECstation/DECsystem 5000 Model 200 series processors to enhance support for the TURBOchannel, the boot commands have changed. As a result, the boot commands for the DECstation/DECsystem 5000 Model 200 series processors that are listed in the Basic Installation Guide, Guide to System Shutdown and Startup, Guide to Diskless Management Services, and that are displayed on the console during an installation are no longer correct. After your new ®rmware is installed, even if you are not reinstalling the ULTRIX operating system, you must reset the environmental variables for the boot and haltaction commands immediately. Until the software and documentation can be revised, please refer to this document when booting your DECstation/DECsystem 5000 Model 200 series processor. 1 Booting the DECstation/DECsystem 5000 Model 200 Series Processor The following sections explain the procedures for: d Determining the Slot and Unit Numbers of Your Boot Device d Setting the Console Environmental Variables d Booting from a System Disk d Booting from a TK50 Tape d Booting from a CDROM Disc Kit d Booting from the Network d Booting during the Installation 1.1 Determining the Slot and Device Numbers of Your Boot Device If you are not reinstalling the ULTRIX operating system after your new ®rmware has been installed, you will need to determine both the slot number of the controller attached to your boot device and the device number of your boot device in order to change the boot variable.
    [Show 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.
    [Show full text]