DOCSLIB.ORG

VAX 6000 Platform Technical User's Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
VAX 6000 Platform Technical User's Guide VAX 6000 Platform Technical User’s Guide Order Number: EK–600EA–TM-001 This manual serves as a reference for field-level repair or programming for systems based on the VAX 6000 platform. The manual describes the platform architecture, the XMI system bus, the DWMBB XMI-to-VAXBI adapter, and the power and cooling systems found in the H9657-CA/CB/CU cabinet. Digital Equipment Corporation First Printing, May 1991 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. Copyright ©1991 by Digital Equipment Corporation All Rights Reserved. Printed in U.S.A. The postpaid 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: DEMNA PDP VAXcluster DEC ULTRIX VAXELN DEC LANcontroller UNIBUS VMS DECnet VAX XMI DECUS VAXBI This document was prepared using VAX DOCUMENT, Version 1.2 Contents PREFACE xiii CHAPTER 1 THE VAX 6000 PLATFORM OVERVIEW 1–1 1.1 SPECIFICATIONS 1–2 1.2 SYSTEM FRONT VIEW 1–4 1.3 SYSTEM REAR VIEW 1–5 1.4 CONFIGURATIONS 1–6 1.5 XMI BACKPLANE AND CARD CAGE 1–7 1.6 CONSOLE LOAD DEVICE 1–9 1.7 DWMBB I/O ADAPTER 1–10 1.8 I/O CONNECTIONS 1–11 1.9 POWER SYSTEM 1–12 1.10 COOLING SYSTEM 1–14 1.11 OPTIONS 1–15 CHAPTER 2 THE XMI 2–1 2.1 XMI OVERVIEW 2–2 2.1.1 XMI System Block Diagram Description 2–2 iii Contents 2.1.2 XMI Corner 2–4 2.1.3 XMI Data Transactions 2–6 2.1.4 XMI Terms 2–7 2.1.5 Wraparound Reads 2–9 2.1.5.1 Octaword Wraparound Read • 2–9 2.1.5.2 Hexword Wraparound Read • 2–9 2.1.6 XMI Interrupt Transactions 2–10 2.1.7 Arbitration 2–11 2.1.8 Bus Integrity 2–11 2.2 XMI ADDRESSING 2–12 2.2.1 XMI Memory Space 2–13 2.2.2 XMI I/O Space 2–14 2.2.2.1 XMI Private Space • 2–14 2.2.2.2 XMI Nodespace • 2–15 2.2.2.3 I/O Address Space • 2–16 2.2.2.4 VAXBI Adapter I/O Address Space • 2–16 2.2.2.5 How to Find a Register in VAXBI Address Space • 2–17 2.3 ARBITRATION CYCLES 2–20 2.4 XMI CYCLES 2–22 2.4.1 Function Codes 2–22 2.4.2 Command Cycles 2–23 2.4.2.1 Command Field • 2–24 2.4.2.2 Mask Field • 2–25 2.4.2.3 Length Field • 2–26 2.4.2.4 Address Field • 2–26 2.4.2.5 Interrupt Priority Level Field • 2–27 2.4.2.6 Node Specifier Field • 2–28 2.4.3 Write Data Cycles 2–29 2.4.4 Good Read Data (GRD) and Corrected Read Data (CRD) Response Cycles 2–29 2.4.5 Locked Response Cycle (LOC) 2–30 2.4.6 Read Error Response Cycle (RER) 2–30 2.4.7 The Null Cycle 2–30 2.5 XMI TRANSACTIONS 2–31 2.5.1 Memory Block State 2–33 2.5.2 Read Transaction 2–34 2.5.3 Interlock Read Transaction 2–35 2.5.4 Ownership Read Transaction 2–37 2.5.5 Write Mask Transaction 2–38 iv Contents 2.5.6 Unlock Write Mask Transaction 2–40 2.5.7 Disown Write Mask Transactions 2–41 2.5.8 Tag Bad Data Transactions 2–42 2.5.9 Interrupt and Identify Transactions 2–43 2.5.10 Implied Vector Interrupt Transactions 2–45 2.5.11 Transaction Examples 2–46 2.5.11.1 Single Quadword Reads • 2–46 2.5.11.2 Multiple Quadword Reads • 2–48 2.5.11.3 Longword and Quadword Writes • 2–50 2.5.11.4 Multiple Quadword Writes • 2–51 2.6 CACHE COHERENCY 2–52 2.7 XMI INITIALIZATION 2–53 2.7.1 Causes of an Initialization 2–54 2.7.2 Power-Up 2–54 2.7.3 System Reset 2–55 2.7.4 Node Reset 2–55 2.8 XMI REGISTERS 2–56 DEVICE REGISTER (XDEV) 2–57 BUS ERROR REGISTER (XBER) 2–58 FAILING ADDRESS REGISTER (XFADR) 2–66 XMI GENERAL PURPOSE REGISTER (XGPR) 2–68 NODE-SPECIFIC CONTROL AND STATUS REGISTER (NSCSR) 2–69 XMI CONTROL REGISTER (XCR) 2–70 FAILING ADDRESS EXTENSION REGISTER (XFAER) 2–72 BUS ERROR EXTENSION REGISTER (XBEER) 2–74 2.9 XMI ERRORS 2–76 2.9.1 Error Conditions 2–76 2.9.1.1 Parity Error • 2–76 2.9.1.2 Inconsistent Parity Error • 2–76 2.9.1.3 Transaction Timeout • 2–77 2.9.1.4 Sequence Error • 2–77 2.9.2 Error Handling 2–78 2.9.3 Error Recovery 2–79 2.9.4 Error Reporting 2–79 v Contents CHAPTER 3 DWMBB ADAPTER 3–1 3.1 DWMBB OVERVIEW 3–2 3.2 ADDRESS TRANSLATION 3–4 3.2.1 DWMBA Compatibility Mode 3–8 3.2.1.1 DWMBA Compatibility Mode DMA Write Transaction • 3–9 3.2.1.2 DWMBA Compatibility Mode DMA Read Transaction • 3–9 3.2.2 40-Bit VAX Address Translation 3–10 3.2.3 40-Bit Address Translation (4-Kbyte Page Size) 3–11 3.2.4 40-Bit Address Translation (8-Kbyte Page Size) 3–13 3.2.5 DMA Write Transactions—Extended Address Modes 3–15 3.2.6 DMA Read Transactions—Extended Address Modes 3–15 3.3 I/O TRANSACTIONS 3–16 3.3.1 I/O References to DWMBB/A Module Registers 3–16 3.3.2 I/O References to the PMRs 3–17 3.3.3 I/O References to DWMBB/B Module Registers or to VAXBI Registers 3–17 3.4 INTERRUPTS 3–18 3.4.1 DWMBB-Detected Error Interrupt Vectors 3–21 3.4.2 VAXBI Node Vector 3–21 3.4.3 Interprocessor Interrupts 3–23 3.4.4 Interrupt Transactions 3–23 3.4.4.1 DWMBB Adapter-Generated Interrupts • 3–23 3.4.4.2 VAXBI-Generated Interrupts • 3–23 3.4.4.3 BIIC-Generated VAXBI Interrupts • 3–23 3.4.4.4 Interprocessor-Generated VAXBI Interrupts • 3–24 3.4.4.5 Passive Release of VAXBI Interrupts • 3–24 3.4.5 IDENT Transactions 3–24 3.4.6 Return Vector Disable Option 3–24 3.4.7 IVINTR Transactions 3–25 3.5 VAXBI WRAPPED READ TRANSACTIONS 3–26 3.6 LOCKOUT MODES 3–28 3.6.1 No Assertion and No Response to XMI Lockout Mode 3–29 3.6.2 Respond to XMI Lockout Mode 3–29 3.6.3 Assert XMI Lockout Mode 3–29 vi Contents 3.6.4 Full XMI Lockout Mode 3–30 3.6.5 Programmable Lockout Limit 3–31 3.6.6 Lockout Deassertion Timer 3–32 3.7 COMMANDER ARBITRATION USING RESPONDER REQUEST 3–33 3.8 PROGRAMMABLE TIMEOUTS 3–34 3.9 PROGRAMMABLE VAXBI I/O WINDOW SPACE 3–36 3.10 ECC PROTECTION ON THE PMR DATA PATH 3–37 3.10.1 ECC Errors Detected During I/O PMR Read Accesses 3–38 3.10.2 ECC Errors Detected During PMR Accesses for DMA Address Translation 3–38 3.11 DWMBB ADAPTER REGISTERS 3–39 DEVICE REGISTER (XDEV) 3–43 BUS ERROR REGISTER (XBER) 3–45 FAILING ADDRESS REGISTER (XFADR) 3–53 RESPONDER ERROR ADDRESS REGISTER (AREAR) 3–54 ERROR SUMMARY REGISTER (AESR) 3–56 INTERRUPT MASK REGISTER (AIMR) 3–64 IMPLIED VECTOR INTERRUPT DESTINATION/DIAGNOSTIC REGISTER (AIVINTR) 3–72 DIAGNOSTIC 1 REGISTER (ADG1) 3–74 UTILITY REGISTER (AUTLR) 3–81 CONTROL AND STATUS REGISTER (ACSR) 3–86 RETURN VECTOR REGISTER (ARVR) 3–91 FAILING ADDRESS EXTENSION REGISTER (XFAER) 3–92 VAXBI ERROR ADDRESS REGISTER (ABEAR) 3–94 PAGE MAP REGISTERS (PMRS) 3–96 CONTROL AND STATUS REGISTER (BCSR) 3–98 ERROR SUMMARY REGISTER (BESR) 3–100 INTERRUPT DESTINATION REGISTER (BIDR) 3–105 TIMEOUT ADDRESS REGISTER (BTIM) 3–106 VECTOR OFFSET REGISTER (BVOR) 3–107 VECTOR REGISTER (BVR) 3–108 DIAGNOSTIC CONTROL REGISTER 1 (BDCR1) 3–109 RESERVED REGISTER (BRSVD) 3–111 DEVICE REGISTER (DTYPE) 3–112 3.12 ERROR HANDLING 3–113 3.12.1 Error Interrupts 3–114 3.12.2 Error Command and Address Logging 3–114 vii Contents 3.12.3 Multiple Errors 3–115 3.12.4 Address Translation Mode Errors 3–115 3.12.4.1 Invalid VAXBI Address • 3–116 3.12.4.2 Invalid PFN • 3–116 3.12.4.3 ECC Errors on PMR Data During DMA Address Translation • 3–117 3.12.4.3.1 Uncorrectable ECC Errors • 3–117 3.12.4.3.2 Correctable ECC Errors • 3–117 3.12.4.4 ECC Errors on PMR Data During I/O Reads to PMR • 3–118 3.12.4.4.1 Uncorrectable ECC Errors • 3–118 3.12.4.4.2 Correctable ECC Errors • 3–118 3.12.5 IBUS Parity Errors 3–119 3.12.5.1 DMA Write C/A or INTR C/A IBUS Parity Error • 3–119 3.12.5.2 DMA Write Data IBUS Parity Error • 3–119 3.12.5.3 DMA Read C/A IBUS Parity Error • 3–120 3.12.5.4 I/O Read Data or IDENT Vector IBUS Parity Error • 3–120 3.12.5.5 DMA Read Data IBUS Parity Error • 3–120 3.12.5.6 I/O Write C/A IBUS Parity Error • 3–121 3.12.5.7 I/O Write Data IBUS Parity Error • 3–121 3.12.5.8 I/O Read C/A IBUS Parity Error • 3–121 3.12.5.9 IDENT IBUS Parity Error • 3–122 3.12.5.10 Undecodable I/O C/A with no IBUS Parity Error Detected • 3–122 3.12.5.11 Undecodable DMA C/A with no IBUS Parity Error Detected • 3–123 3.12.5.12 Undecodable DMA C/A with an IBUS Parity Error Detected • 3–123 3.12.6 XMI Errors 3–124 3.12.6.1 DMA Write C/A XMI Error • 3–125 3.12.6.2 DMA Read C/A XMI Error • 3–125 3.12.6.3 DMA Write Data XMI Error • 3–125 3.12.6.4 DMA Read Data XMI Error • 3–125 3.12.6.5 Parity Errors on the XMI • 3–126 3.12.6.6 I/O Read Data and IDENT Vector Errors on the XMI • 3–126 3.12.6.7 I/O Write Data Error on the XMI • 3–126 3.12.6.8 LOC Response on DMA Read Data • 3–126 3.12.7 VAXBI Errors 3–127 3.12.8 Miscellaneous Errors 3–128 3.12.8.1 Impending Power Fail • 3–128 3.12.8.2 Internal Errors • 3–128 3.12.8.3 PMR Initialization Inhibit Error • 3–128 3.12.8.4 DMA Read Data Parity Error during DWMBB/A Module Loopback • 3–129 3.12.8.5 Cable OK Error • 3–129 3.13 DWMBB INITIALIZATION 3–130 3.13.1 DWMBB/A Module Initialization Sequence 3–131 3.13.2 DWMBB/A Module Gate Array Control Reset 3–131 viii Contents 3.13.3 DWMBB/B Module Initialization Sequence 3–132 3.14 DIAGNOSTIC FEATURES 3–133 3.14.1 Internal Loopback Modes 3–134 3.14.1.1 DWMBB/A Module Loopback • 3–134 3.14.1.2 BIIC Loopback • 3–135 3.14.1.3 DMA Loopback • 3–136 3.14.2 DWMBB/A Module Gate Array Transaction Register Files Testing 3–137 3.14.2.1 Executing DMA Writes and Reads in Loopback Mode • 3–141 3.14.2.2 Transaction Register File in Loopback
Load more

Recommended publications
  • VAX 4000 V96-2.3—10 Feb 1997
    TM VAX 4000 V96-2.3—10 Feb 1997 DIGITAL Systems and Options Catalog Product Description VAX 4000 systems provide commercial systems performance, high availability, and a compact footprint. They support a wide range of applications and options, including FDDI networks and Q-bus peripherals. System enclosure supports internal storage and Q-bus expansion through a B400X expansion cabinet. VAX 4000 systems come in three packages: Desktop Model 106A, Desktop/Deskside Model 108, and Pedestal/Deskside Model 505A/705A DSSI and Ethernet adapter chips—each driven by a 10-MIP on-chip RISC processor—are tightly integrated on the CPU module with direct access to memory. Digital's DSSI to SCSI HSD10 storage solutions replace DSSI RF36 disk technology in all VAX 4000 systems. Digital’s HSD10 DSSI-to-SCSI controller. mounted internally in system cabinet, supports standard RZxx SCSI storage on VAX 4000 systems while still supporting DSSI clustering. External StorageWorks HSD10 controllers are supported. VAX 4000 Model 106A offers performance of 10-ns NVAX chip. Systems achieve 215 transactions per second (TPS). With internal support for the HSD10, DSSI-to-SCSI controller, VAX 4000 customers can take advantage of low-cost, more flexible and open StorageWorks solutions. VAX 4000 Model 108 offers identical performance, is compatible with Model 106A, but is housed in a new Desktop/Deskside minitower enclosure. In addition, these systems offer enchancements in the memory and storage capacity, supporting up to 512 MB of standard SIMM memory and six storage devices in the system enclosure. VAX 4000 Model 505A and 705A offer 12 ns and 9 ns performance, respectively in a Q-bus Pedestal package.
    [Show full text]
  • Digital Technical Journal, Number 7, August 1988: CVAX
    Digital Technical Tournal Digital Equipment Corporation Managing Editor Richard W Beam Edltor Jane C. Dlak Pcoductloa St& Production Editor - Helen 1 Partenon Designer - Charlotte Bell Typographers -Jonathan M. Bohy Macgaret Burdine lllusultor - Deborah Kc~lcy Advisoiy Board Samuel H. Fuller, Chairman Robert M. Glorioso John W. McCredle Mahendra R. Patel F. Grant Saviers William D. Srrcckr Victor A. Vyssutsky The Digital Technical Journal is published by Digital Equipment Corporatloa, 77 Reed Road, Hudson, Magsachu~etts0 1749. Changes of address should be sent to Digital Equipment Corporation. attention: List Maintenance. I0 Forbes Road, Northboro, MA 01532 Please indude the address label wlth changes marked. Comments on the content of any paper arc welcomed. Write to the editor at Mall Stop HL02.3/K11 at the published~bpaddress. Comments can ahbe sent on the BNET to RDVAX: :BIAKEor on the ARPANET to B~%RDVAX.DE~DE~. Copyright @ 1988 Digital Equipment Corporation. Copying without fee is permitted provided that such copies are made for use in educational lnstltutions by faculty members and are nor distributed for commercial advantage. Abstncting with credit of Digital Equipment Corporation's authorship is permltted. Requests for other copies for a Pee may br made to Digiul Press of Digital Equipment Corporation. A11 rights reserved. The information in this journal is subject to change without notice and should not bc construed as a com- mltment by Digital Equipment Corporation. Digital Equipment Corpmtion assumes no responslbllity for any errors that may appcss in this document ISSN 0898.901X Documentatlcm Number EY-6742H-DP The following are wademarks of Digital Gquipmcnt Corporation: ALL.IN-I.
    [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]
  • VAX 6000 Series Installation Guide
    VAX 6000 Series Installation Guide Order Number EK–600EB–IN.002 This guide is intended for use by Digital customer service engineers and self-maintenance customers installing a VAX 6000 series system. digital equipment corporation maynard, massachusetts First Printing, October 1990 Revised, November 1991 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. Copyright ©1990, 1991 by Digital Equipment Corporation. All Rights Reserved. Printed in U.S.A. The following are trademarks of Digital Equipment Corporation: DEC PDP VAXcluster DEC LANcontroller ULTRIX VAXELN DECnet UNIBUS VMS DECUS VAX XMI DWMVA VAXBI 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]
  • VAX 6000 Platform Technical User's Guide
    VAX 6000 Platform Technical User’s Guide Order Number: EK–600EA–TM-001 This manual serves as a reference for field-level repair or programming for systems based on the VAX 6000 platform. The manual describes the platform architecture, the XMI system bus, the DWMBB XMI-to-VAXBI adapter, and the power and cooling systems found in the H9657-CA/CB/CU cabinet. Digital Equipment Corporation First Printing, May 1991 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. Copyright ©1991 by Digital Equipment Corporation All Rights Reserved. Printed in U.S.A. The postpaid 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: DEMNA PDP VAXcluster DEC ULTRIX VAXELN DEC LANcontroller UNIBUS VMS DECnet VAX XMI DECUS VAXBI dt This document was prepared using VAX DOCUMENT, Version 1.2 Contents PREFACE xiii CHAPTER 1 THE VAX 6000 PLATFORM OVERVIEW 1–1 1.1 SPECIFICATIONS 1–2 1.2 SYSTEM FRONT VIEW 1–4
    [Show full text]
  • Digital Technical Journal, Number 7, August 1988: CVAX-Based Systems
    CVAX-based Systems Digital Technical Journal Digital Equipment Corporation umhcr 7 August I9R8 Managing Editor Richard W Beane Editor jane C. Blake Production Staff Produnion Editor- Helen L. Paucrson Designer- Charlo!!<: Bell Typographers- Jonathan !\·f. Uohy Margart:t Burdine lllustrawr- Dt:borah Keeley Advisory Board Samuel H. Fuller, Chairman Robert M. Glorioso John W McCredie Mahendra R. Patel F. Grant Saviers William D. Strecker Victor A. Vyssotsky The Digital Tecbnical jnumal is published by Digital Equipmt:nt Corporation. 77 Reed Road. Hudson. Massachuscus 01749. Changes of address should be sent to Digital E quipment Corporation. aut:ntion: List Maintenance. I 0 Forbes Road. Northboro. MA 015j2. Please includt: the address label with changes marked. Comments on the content of any paper are wclcomt:d. Write to the editor at Mail Stop 1-lLOl-.�/Kil at the published-by address. Comments can also be sent on the ENET to RDV�'X::OIAKE or on the ARPANET to BLA.K.E'X,RDVAX. DEC�)l)ECWRL. Copyright © 1988 Digital Equ ipment Corporation. Copying without fee is permiued providt:d that such copies are made for use in t:duc:uional institmions by faculty members and arc not distributed for commercial advamage. Abstracting with credit of Digital Equipment Corporation's authorship is pcrmiued. Requests for other copies for a fee may be made 10 Digital Press of Digital Equipmem Corporation. All rights reserved. The information in this journal is subject to change without notice and should not be construed as a com­ miunem by Digital E quipment Corporation. Digital Equipment Corporation assumt:s no responsibility for any errors that may appear in this document.
    [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]
  • Openvms I/O User's Reference Manual
    OpenVMS I/O User’s Reference Manual Order Number: AA–PV6SD–TK April 2001 This manual contains the information necessary to interface directly with the I/O device drivers supplied as part of the Compaq OpenVMS operating system. Several examples of programming techniques are included. This document does not contain information on I/O operations using the OpenVMS Record Management Services. Revision/Update Information: This manual supersedes the OpenVMS I/O User’s Reference Manual, OpenVMS Alpha Version 7.2, OpenVMS VAX Version 7.2 Software Version: OpenVMS Alpha Version 7.3 OpenVMS VAX Version 7.3 Compaq Computer Corporation Houston, Texas © 2001 Compaq Computer Corporation Compaq, VAX, VMS, and the Compaq logo Registered in U.S. Patent and Trademark Office. OpenVMS and Tru64 are trademarks of Compaq Information Technologies Group, L.P in the United States and other countries. Microsoft, MS-DOS, Visual C++, Windows, and Windows NT are trademarks of Microsoft Corporation in the United States and other countries. Intel, Intel Inside, and Pentium are trademarks of Intel Corporation in the United States and other countries. Motif, OSF/1, and UNIX are trademarks of The Open Group in the United States 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.
    [Show full text]
  • Database Integration
    I DATABASE INTEGRATION ALPHA SERVERS & WORKSTATIONS Digital ALPHA 21164 CPU Technical Journal Editorial The Digital TechnicalJournal is a refereed Cyrix is a trademark of Cyrix Corporation. Jane C. Blake, Managing Editor journal published quarterly by Digital dBASE is a trademark and Paradox is Helen L. Patterson, Editor Equipment Corporation, 30 Porter Road a registered trademark of Borland Kathleen M. Stetson, Editor LJ02/D10, Littleton, Massachusetts 01460. International, Inc. Subscriptionsto the Journal are $40.00 Circulation (non-U.S. $60) for four issues and $75.00 EDA/SQL is a trademark of Information Catherine M. Phillips, Administrator (non-U.S. $115) for eight issues and must Builders, Inc. Dorothea B. Cassady, Secretary be prepaid in U.S. funds. University and Encina is a registered trademark of Transarc college professors and Ph.D. students in Corporation. Production the electrical engineering and computer Excel and Microsoft are registered pde- Terri Autieri, Production Editor science fields receive complimentary sub- marks and Windows and Windows NT are Anne S. Katzeff, Typographer scriptions upon request. Orders, inquiries, trademarks of Microsoft Corporation. Joanne Murphy, Typographer and address changes should be sent to the Peter R Woodbury, Illustrator Digital TechnicalJournal at the published- Hewlett-Packard and HP-UX are registered by address. Inquiries can also be sent elec- trademarks of Hewlett-Packard Company. Advisory Board tronically to [email protected]. Single copies INGRES is a registered trademark of Ingres Samuel H. Fuller, Chairman and back issues are available for $16.00 each Corporation. Richard W. Beane by calling DECdirect at 1-800-DIGITAL Donald Z. Harbert (1-800-344-4825).
    [Show full text]
  • Software Product Description
    Software Product Description PRODUCT NAME: DECnet-VAX, Version 5.4 SPD 25.03.28 DESCRIPTION DECnet implementation may not be able to access all DECnet-VAX functions. DECnet-VAX allows a suitably configured VMS sys­ tem to participate as a routing or end node in DEC­ The functions available to users on mixed networks net computer networks. With proper network planning, can be determined by a comparison of the SPDs for DECnet-VAX, Version 5.4 networks can contain up to the appropriate DECnet products. 1023 nodes per network area and up to 63 areas per network. DECnet-VAX interfaces are standard compo­ Routing nents of VMS for use on a local standalone system. A Full Function DECnet-VAX License PAK must be DECnet-VAX end node and full function products are li­ registered on a node in order for that node to oper­ censed separately for VMS. The DECnet-VAX License ate as a routing node. For a node to operate as an Product Authorization Key (PAK), when registered on end node, either the Full Function or the End Node a VMS system, enables communication between dif­ DECnet-VAX License PAK must be registered on that ferent networked systems that use the same protocols. node. Full Function DECnet-VAX software allows a node to be set up as either a routing node or as an DECnet-VAX is a Phase IV network product and is end node. warranted only for use with Phase III and Phase IV products supported by Digital Equipment Corporation. A DECnet-VAX node must function as a routing node whenever multiple circuits are used by that node.
    [Show full text]
  • VAX 6000 Model 500 Mini-Reference
    VAX 6000 Model 500 Mini-Reference Order Number EK–650EA–HR–001 This manual supplies easy-to-access key information on VAX 6000 Model 500 systems. digital equipment corporation maynard, massachusetts First Printing, October 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, 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. Copyright ©1990 by Digital Equipment Corporation. All Rights Reserved. Printed in U.S.A. The following are trademarks of Digital Equipment Corporation: DEMNA PDP VAXcluster DEC ULTRIX VAXELN DEC LANcontroller UNIBUS VMS DECnet VAX XMI DECUS VAXBI 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. Contents Preface xi Chapter 1 Console Operation Chapter 2 Self-Test Chapter 3 Address Space 3.1 How to Find a Register in XMI Address Space .
    [Show full text]
  • A Conceptual Design for the Triumf Kaon Factory Control System
    TRIUMF A CONCEPTUAL DESIGN FOR THE TRIUMF KAON FACTORY CONTROL SYSTEM W.K. Dawson, R.W. Dobinson,* D.P. Gurd and Ch. Serre* TRIUMF Technology Division *on leave of absence from CERN CANADA'S NATIONAL MESON FACILITY OPERATED AS A JOINT VENTURE BY: UNIVERSITY OF ALBERTA SIMON FRASER UNIVERSITY UNIVERSITY OF VICTORIA UNIVERSITY OF BRITISH COLUMBIA UNDER A CONTRIBUTION FROM THE NATIONAL RESEARCH COUNCIL OF CANADA TRI-87-1 TRI-87-1 A CONCEPTUAL DESIGN FOR THE TRIUMF KAON FACTORY CONTROL SYSTEM W.K. Dawson, R.W. Dobinson,* D.P. Gurd and Ch. Serre* TRIUMF Technology Division *on leave of absence from CERN Postal address: TRIUMF 4004 Wesbrook Mall Vancouver, B.C. Canada V6T 2A3 December 1987 All trademarks found in this report are acknowledged as such. ii TABLE OF CONTENTS 1.0 Introduction 1-1 1.1 Why Was a Design Study Undertaken? 1-1 1.2 How Was the Work Carried Out? 1-1 1.3 Report Layout 1-2 1.4 Acknowledgements 1-3 2.0 Requirements 2-1 2.1 The Accelerators - 2-1 2.2 Timing and Synchronization 2-1 2.3 Multiple Rings, Physical Size and Complexity 2-4 2.4 High Intensity 2-5 2.5 Safety Systems 2-6 2.6 Users of the Control System 2-7 2.7 General Needs - Motherhood and Apple Pie 2-9 3.0 Review of Current Technologies and Trends in Other Laboratories . 3-1 3.1 The Importance and Role of Protocols and Standards 3-1 3.1.1 Review 3-1 3.1.2 Trends in Other Laboratories 3-2 3.2 Software 3-3 3.2.1 Review 3-3 3.2.2 Trends in Other Laboratories .
    [Show full text]