DOCSLIB.ORG

Decnet-Plus Planning Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Decnet-Plus Planning Guide DECnet-Plus Planning Guide Part Number: AA-QBTHE-TE November 1996 This manual provides an overview of the transition and planning tasks necessary to move from DECnet for OpenVMS (Phase IV) to DECnet- Plus for OpenVMS (Phase V) and DECnet/OSI for Digital UNIX. Revision/Update Information: This manual supersedes the DECnet/OSI Planning Guide. Operating Systems: OpenVMS VAX Version 7.1 OpenVMS Alpha Version 7.1 Digital UNIX Version 4.0 Software Versions: DECnet-Plus for OpenVMS Version 7.1 DECnet/OSI for Digital UNIX Version 4.0 Digital Equipment Corporation Maynard, Massachusetts 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 conducts its business in a manner that conserves the environment and protects the safety and health of its employees, customers, and the community. © Digital Equipment Corporation 1996. All rights reserved. The following are trademarks of Digital Equipment Corporation: Bookreader, DDCMP, DEC, DECdirect, DECnet, DECNIS, DECserver, DECsystem, DECwindows, Digital, DNA, InfoServer, OpenVMS, OpenVMS cluster, PATHWORKS, ULTRIX, VAX, VAX DOCUMENT, VAXcluster, VAXstation, VMS, VMScluster, and the DIGITAL logo. The following are third-party trademarks: Macintosh is a registered trademark of Apple Computer, Inc. Microsoft, MS, and MS–DOS are registered trademarks of Microsoft Corporation. MS–DOS is a registered trademark of Microsoft Corporation. Motif, OSF, OSF/1, OSF/Motif, and Open Software Foundation are registered trademarks of the Open Software Foundation, Inc. OS/2 is a registered trademark of International Business Machines Corporation. OSF/1 is a registered trademark of Open Software Foundation, Inc. OSI is a registered trademark of CA Management, Inc. SCO is a trademark of Santa Cruz Operations, Inc. TCPware is a registered trademark of Process Software Corporation. UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company Ltd. All other trademarks and registered trademarks are the property of their respective holders. Contents Preface ............................................................ ix 1 Preplanning: Understanding the Transition Process 1.1 Transition Defined . ........................................ 1–1 1.1.1 Why Make the Transition to DECnet-Plus? ..................... 1–2 1.1.2 How Long Does Transition Take? ............................ 1–3 1.1.3 What Is the Transition Environment? . ....................... 1–3 1.1.4 When Do DECnet-Plus Features Become Available? ............. 1–3 1.1.5 When Does Transition End? ................................ 1–4 1.2 Transition Features . ........................................ 1–4 1.3 Addressing ................................................ 1–5 1.3.1 Phase IV Addressing and OSI Addressing: A Comparison . ....... 1–6 1.3.2 Advantages of Using OSI Addresses That Are Also Phase IV Compatible ............................................. 1–8 1.3.3 Advantages of Using Extended Addressing ..................... 1–8 1.3.4 Advantages of Using Multihoming ........................... 1–9 1.3.5 Autoconfiguration of Addresses .............................. 1–9 1.4 Routing . ................................................ 1–9 1.4.1 Interdomain Routing ...................................... 1–10 1.4.2 Level 2 Routing Between Phase IV and Phase V Areas ............ 1–10 1.4.3 Multivendor Routers ...................................... 1–10 1.5 Name Services and Time Service Considerations .................... 1–11 1.5.1 The Local Namespace ..................................... 1–11 1.5.2 The Name Service Search Path .............................. 1–11 1.5.3 Name Service and Time Service Interdependencies ............... 1–12 1.5.4 Mapping Node Names to Addresses . ....................... 1–12 1.6 OpenVMS Cluster Systems (OpenVMS Only) ...................... 1–13 1.7 DECnet Phase IV Applications . ................................ 1–13 1.7.1 DECnet for OpenVMS Phase IV Applications (OpenVMS Only) ..... 1–13 1.7.2 DECnet–ULTRIX Phase IV Applications (Digital UNIX Only) ....... 1–14 1.8 Network Management ........................................ 1–14 1.8.1 Managing a Mixture of Phase V and Phase IV Nodes ............. 1–14 1.8.2 Network Management Protocols and Constraints . ............... 1–14 1.8.2.1 Phase IV Protocols in User Applications (OpenVMS Only) ...... 1–14 1.8.3 Managing Multivendor OSI-Compliant Systems . ............... 1–15 1.9 Noncompatibility with Pre-Phase IV Systems ...................... 1–15 1.10 Products That Do Not Migrate to DECnet Phase V . ............... 1–15 iii 2 Planning the Transition 2.1 Step 1: Document the Current Network Configuration ............... 2–3 2.2 Step 2: Determine Your Transition Strategy ....................... 2–3 2.2.1 If the Network Is Not Moving Entirely to the DECnet-Plus Environment ............................................ 2–4 2.2.2 If the Network Is Moving Entirely to the DECnet-Plus Environment ....................................................... 2–4 2.3 Step 3: Develop a New Network Configuration ..................... 2–5 2.3.1 Planning the New Network Configuration ...................... 2–5 2.3.1.1 Single Extended-Area LANs ............................. 2–6 2.3.1.2 End-System-Only LAN Configurations ...................... 2–6 2.3.1.3 Multicircuit End-System Configurations .................... 2–7 2.3.2 Including Multivendor Systems in the Network . ............... 2–10 2.3.3 Using the Inactive Network Layer Protocol .................... 2–11 2.3.4 Planning Addressing ...................................... 2–12 2.3.4.1 Do You Need a Unique IDP for Your Network? ............... 2–12 2.3.4.2 Do You Need Extended OSI Addresses? ..................... 2–12 2.3.4.3 Considerations for a Network with DECnet Phase V Areas ...... 2–13 2.3.5 Planning Routing . ........................................ 2–14 2.4 Step 4: Plan for Your Name Services and the DECdts Time Service ..... 2–15 2.4.1 Choosing DECdns and DECdts Servers ....................... 2–15 2.4.2 Creating Multiple Namespaces .............................. 2–16 2.4.3 Preparing a DNS Version 1 Namespace for Use By DECnet-Plus .... 2–17 2.5 Step 5: Choose the First End System to Migrate ................... 2–18 3 Performing Transition Tasks 3.1 Tools: Network Management, Node-Name Management, and Transition .......................................................... 3–1 3.2 Immediate Tasks ............................................ 3–2 3.2.1 IDP Planning . ........................................ 3–3 3.2.2 Using a Local Namespace: Migrating the Network ............... 3–3 3.2.3 Using a Distributed Namespace: Migrating the First End Node .... 3–4 3.2.3.1 If the Network Does Not Have a Namespace . ............... 3–4 3.2.3.2 If the Network Has a DNS Version 1 Namespace ............. 3–6 3.2.4 Using a Distributed Namespace: Migrating Subsequent End Nodes ....................................................... 3–6 3.2.4.1 Registering a New System ............................... 3–7 3.2.4.2 Registering a System You Migrated from Phase IV to DECnet-Plus . ........................................ 3–8 3.2.4.3 Registering a System You Changed from DECnet-Plus to Phase IV.................................................. 3–9 3.2.5 Migrating OpenVMS Cluster Nodes (OpenVMS Only) ............. 3–9 3.2.6 Migrating Local Area Networks ............................. 3–9 3.2.7 Configuring a DECnet-Plus End System in a Multivendor OSI Network ............................................... 3–14 3.3 Additional Tasks ............................................ 3–15 3.3.1 Converting the Phase IV Object Database with the OBJTONCL Utility (Digital UNIX Only) . ................................ 3–16 3.3.2 Converting the Phase IV Proxy File (Digital UNIX Only) . ....... 3–17 3.3.3 Converting the MOP Database (Digital UNIX Only) .............. 3–17 3.3.4 Becoming Familiar with NCL Commands, Network Management Modules, and Network Management Tasks ..................... 3–18 3.4 Optional Tasks ............................................. 3–20 iv 3.4.1 Adjusting Buffer Sizes During Transition ...................... 3–20 3.4.2 Changing the Network’s IDP and preDSP ...................... 3–21 4 Creating NSAP Addresses 4.1 IDP Values ................................................ 4–2 4.2 DSP Values ................................................ 4–3 4.3 NSAP Entry and Display Formats ............................... 4–4 4.4 Converting Phase IV Addresses to NSAPs . ....................... 4–5 4.5 Converting NSAPs to Phase IV Addresses . ....................... 4–6 4.6 Forms of the NSAP Displayed by NCL ........................... 4–7 4.7 How to Obtain a Unique IDP and PreDSP . ....................... 4–9 4.7.1 For a Private Network (AFI 49) ............................. 4–9 4.7.2 Allocation Authority for Single-Country Organizations (AFI 39) ..... 4–9 4.7.3 Allocation Authority for International Organizations (AFI 47) ...... 4–9 4.7.4 Using an X.25 Data Network Address for the IDI (AFIs 37 and 53) ......................................................
Load more

Recommended publications
  • DEC Ada Installation Guide for Openvms Alpha Systems
    DEC Ada Installation Guide for OpenVMS Alpha Systems Order Number: AA–PW1VC–TE May 1999 This guide contains instructions for installing DEC Ada Version 3.5 on OpenVMS Alpha systems. It also explains how to read the online release notes before or after installing the product. This guide applies to DEC Ada Version 3.5 and all maintenance updates throughout that version. Revision/Update Information: This is a new guide. Operating System & Version: OpenVMS Alpha Version 6.2 through 7.2 Software Version: DEC Ada Version 3.5 Compaq Computer Corporation Houston, Texas First Printing, January 1993 Revised, May 1999 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, 1999. All Rights Reserved. Compaq and the Compaq logo are registered trademarks of Compaq Computer Corporation. Bookreader, DEC, DEC Ada, DEC C, DECdocument, Debugger, DECnet, DECset, DECstation, DECthreads, DIGITAL, DIGITAL Fortran, DIGITAL FUSE, DIGITAL Ladebug, DIGITAL logo, Digital UNIX, OpenVMS, ULTRIX, VAX, VAXcluster, VAX DOCUMENT, VMScluster are trademarks of Digital Equipment Corporation.
    [Show full text]
  • Console Port
    DIGITAL NetRider Network Access Server Management Part Number: AA-PW5VE-TE June 1997 Revision/Update Information: This is a revised document. Software and Version: DECserver Network Access Software, Version 2.2 © Digital Equipment Corporation 1997. All rights reserved. Digital Equipment Corporation makes no representations that the use of its products in the manner described in this document will not infringe on existing or future patent rights, nor do the descriptions contained in this document imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from DIGITAL or an authorized sublicensor. The following are trademarks of Digital Equipment Corporation: DDCMP, DEC, DECmcc, DECnet, DECserver, DECsystem, DECwindows, DIGITAL, DNA, LAT, NetRider, OpenVMS, ThinWire, ULTRIX, VAX, VAXstation, VMS, VMScluster, VT100, VT220,VT320, VT330, and the DIGITAL logo. The following are third-party trademarks: AppleTalk and Macintosh are registered trademarks of Apple Computer, Inc. HP and Hewlett-Packard are registered trademarks of Hewlett Packard Company. IBM is a registered trademark of International Business Machines Corporation. Kerberos is a trademark of the Massachusetts Institute of Technology. Microsoft, MS-DOS, and Windows 95 are registered trademarks, and Windows NT is a trademark of Microsoft Corporation. NetBIOS is a trademark of Micro Computer Systems, Inc. Novell and NetWare are registered trademarks of Novell, Inc. OS/2 is a registered trademark of International Business Machines Corporation. OSF/1 is a registered trademark of Open Software Foundation, Inc. PostScript is a registered trademark of Adobe Systems, Inc.
    [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]
  • 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]
  • PMDF User's Guide Openvms Edition
    PMDF User’s Guide OpenVMS Edition Order Number: V-5305-66-NN-V September 2015 This document describes the OpenVMS user interfaces to Version 6.7 of the PMDF e-mail Interconnect family of products. Revision/Update Information: This manual supersedes the V6.6 PMDF User’s Guide, OpenVMS Edition Software Version: PMDF V6.7 Operating System and Version: OpenVMS VAX V6.1 or later OpenVMS Alpha V7.0 or later OpenVMS I64 V8.2 or later Copyright ©2015 Process Software, LLC. Unpublished — all rights reserved under the copyright laws of the United States No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language or computer language, in any form or by any means electronic, mechanical, magnetic, optical, chemical, or otherwise without the prior written permission of: Process Software, LLC 959 Concord Street Framingham, MA 01701-4682 USA Voice: +1 508 879 6994; FAX: +1 508 879 0042 [email protected] Process Software, LLC (‘‘Process’’) makes no representations or warranties with respect to the contents hereof and specifically disclaims any implied warranties of merchantability or fitness for any particular purpose. Furthermore, Process Software reserves the right to revise this publication and to make changes from time to time in the content hereof without obligation of Process Software to notify any person of such revision or changes. Use of PMDF, PMDF-DIRSYNC, PMDF-FAX, PMDF-LAN, PMDF-MR, PMDF-MSGSTORE, PMDF- MTA, PMDF-TLS, PMDF-X400, PMDF-X500, PMDF-XGP, and/or PMDF-XGS software and associated documentation is authorized only by a Software License Agreement.
    [Show full text]
  • DEC 7000 AXP System VAX 7000 Operations Manual
    DEC 7000 AXP System VAX 7000 Operations Manual Order Number EK–7000B–OP.002 This manual is intended for the system manager or system operator and covers the basic operations of a DEC 7000 AXP system or VAX 7000 system. digital equipment corporation maynard, massachusetts First Printing, November 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, 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 re- sponsibility is assumed for the use or reliability of software or equipment that is not supplied by Digital Equipment Corporation or its affiliated companies. Copyright © 1992 by Digital Equipment Corporation. All Rights Reserved. Printed in U.S.A. The following are trademarks of Digital Equipment Corporation: Alpha AXP DECUS VAXBI AXP DWMVA VAXELN DEC OpenVMS VMScluster DECchip ULTRIX XMI DEC LANcontroller UNIBUS The AXP logo DECnet VAX OSF/1 is a registered trademark of the Open Software Foundation, Inc. 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]
  • Oracle Rdb7™ SQL Reference Manual Volume 1
    Oracle Rdb7™ SQL Reference Manual Volume 1 Release 7.0 Part No. A42814-1 ® SQL Reference Manual, Volume 1 Release 7.0 Part No. A42814-1 Copyright © 1987, 1996, Oracle Corporation. All rights reserved. This software/documentation contains proprietary information of Oracle Corporation; it is provided under a license agreement containing restrictions on use and disclosure and is also protected by copyright law. Reverse engineering of the software is prohibited. The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. Oracle Corporation does not warrant that this document is error-free. Restricted Rights Legend Programs delivered subject to the DOD FAR Supplement are ’commercial computer software’ and use, duplication and disclosure of the Programs shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement. Otherwise, Programs delivered subject to the Federal Acquisition Regulations are ’restricted computer software’ and use, duplication and disclosure of the Programs shall be subject to the restrictions in FAR 52.227-14, Rights in Data—General, including Alternate III (June 1987). Oracle Corporation, 500 Oracle Parkway, Redwood City, CA 94065. The programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be licensee’s responsibility to take all appropriate fail-safe, back up, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and Oracle disclaims liability for any damages caused by such use of the Programs.
    [Show full text]
  • Openvms Glossary
    OpenVMS Glossary Order Number: AA-PV5UA-TK May 1993 This document contains definitions for commonly used terms in documentation of the OpenVMS operating system. Revision/Update Information: This manual supersedes the VMS Glossary, Version 5.5. Software Version: OpenVMS AXP Version 1.5 OpenVMS VAX Version 6.0 Digital Equipment Corporation Maynard, Massachusetts May 1993 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 1993. All rights reserved. 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: Alpha AXP, AXP, CI, CMI, DECdtm, DECmigrate, DECnet, DECwindows, DECwriter, Digital, DNA, Ethernet, HSC, IAS, LAT, MASSBUS, MicroVAX, MicroVAX II, MSCP, OpenVMS, Packetnet, PDP–11, RMS–11, RSX–11, RSX–11M, RSX11-S, RT–11, TMSCP, UNIBUS, VAX, VAX–11/750, VAX11/780, VAX–11 RSX, VAX 8200, VAX 8250, VAX 8300, VAX 8350, VAX 8530, VAX 8550, VAXBI, VAXcluster, VAX DOCUMENT, VAX FORTRAN, VAXft, VAX MACRO, VMS, VMScluster, VT100, the AXP logo, and the DIGITAL logo. ZK4507 This document was prepared using VAX DOCUMENT Version 2.1.
    [Show full text]
  • Building Dependable Systems: the Openvms Approach
    Building Dependable Systems: The OpenVMS Approach Order Number: AA–PV5YB–TE March 1994 This handbook describes the principles of building dependable computing systems. It also highlights the dependability features of OpenVMS software, layered products software, and related hardware components. Revision/Update Information: This manual supersedes Building Dependable Systems: The OpenVMS VAX Approach, OpenVMS VAX Version 6.0. Software Versions: OpenVMS AXP Version 6.1 OpenVMS VAX Version 6.1 Digital Equipment Corporation Maynard, Massachusetts March 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. © Digital Equipment Corporation 1994. All rights reserved. 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: ACMS, Alpha AXP, AXP, BI, Bookreader, Business Recovery Server, CDA, CDD/Repository, CI, COHESION, DATATRIEVE, DECADMIRE, DECalert, DECamds, DBMS, DECalert, DECdecision, DECdesign, DECdtm, DECforms, DECmcc, DECnet, DECquery,
    [Show full text]
  • Alpha AXP DSSI Vmscluster Installation and Troubleshooting Guide
    Alpha AXP DSSI VMScluster Installation and Troubleshooting Guide Order Number: EK–D4AXP–TS. B01 Digital Equipment Corporation Maynard, Massachusetts First Printing, May 1993 Second Printing, May 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. 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 © 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]
  • Openvms Introduction
    G O Y O S Id gm vaxvms Version Date Septemb er Revised August GSI Online Oine S Ystem Op enVMS Intro duction HG Essel M Richter W Schieb el August GSI Gesellschaft fur Schwerionenforschung mbH PostfachPlanckstrae D Darmstadt Tel List of Figures GSI Computer Network IBM VT Terminal Keyb oard Op enVMS LSE Terminal Keyb oard Op enVMS Debug Terminal Keyb oard A Alpha AXP or VAX Terminal Keyb oard Version August Version August Conventions used in this Do cument Chapter Preface GOOSY Copy Right The GOOSY software package has b een develop ed at GSI for scientic applications Any distribu tion or usage of GOOSY without p ermission of GSI is not allowed To get the p ermission please contact at GSI Mathias Richter tel or EMail MRichtergside or HansGeorg Essel tel or EMail HEsselgside Conventions used in this Do cument Fn PFn Do or Return key All key in frame b oxes refer to the sp ecial keypads on VTx compatible terminals like VT VT VT VT VT VT PECAD PERICOM terminals or DECterm windows under DECwindowsMotif on top or rightto the main keyb oard to control characters or to the delete and return keys of the main keyb oard Fn PFn KPn DoorCtrl This is the alternativeway of writing the keypad or control keys GOLD GOLD The PF key is called GOLD in most utility programs using the keypad PERICOM On the PERICOM terminal keyb oard the function keys are marked opp osite to all other terminals ie the PFn of the rightmost VTx compatible keypad are named Fn and the Fn keys on the
    [Show full text]
  • The Openvms Frequently Asked Questions (FAQ)
    The OpenVMS Frequently Asked Questions (FAQ) ABSTRACT This document contains answers to many common questions on the OpenVMS operating system, and covers OpenVMS, and OpenVMS running on Itanium, Alpha, and VAX hardware. While this document is available in multiple formats, the text-format version is far and away generally the easiest format to search. Revision/Update Information OpenVMS V8.3 Revision/Update Information: Revision Date/September 2006 FAQ Contents PREFACE i OPENVMS FREQUENTLY ASKED QUESTIONS (FAQ) iii CHAPTER 1 INTRODUCTION 1–1 1.1 WHAT CORE OPENVMS URLS DO YOU NEED TO KNOW? 1–1 1.2 WHAT ARE THE OPENVMS USENET NEWSGROUPS? 1–2 1.2.1 What is the scope of the comp.os.vms newsgroup? 1–2 1.2.2 What newsgroups carry VMS-related information? 1–2 1.2.3 What newsgroup archives are available? 1–3 1.2.4 What is the INFO-VAX mailing list? 1–3 1.2.4.1 How do I subscribe to or unsubscribe from INFO-VAX? • 1–3 1.3 WHAT IS [N]ETIQUETTE? 1–4 1.4 WHAT OPENVMS USER GROUP(S) ARE AVAILABLE? 1–5 1.5 OPENVMS SUPPORT, QUESTIONS AND COMMENTS? 1–5 1.5.1 Corporate contacts for OpenVMS Business Issues? 1–6 1.5.2 OpenVMS Ambassadors? 1–6 1.5.3 Contact for OpenVMS Marketing Issues and Questions? 1–6 1.5.4 Contact URLs for OpenVMS Technical Issues? 1–7 CHAPTER 2 GENERAL INFORMATION 2–1 2.1 WHAT IS OPENVMS? WHAT IS ITS HISTORY? 2–1 2.2 WHAT IS THE DIFFERENCE BETWEEN VMS AND OPENVMS? 2–2 iii Contents 2.3 WHAT’S IN A NAME? TERMINOLOGY AND PRODUCTS? 2–3 2.3.1 How do I port from VMS to OpenVMS? 2–4 2.4 WHICH IS BETTER, OPENVMS OR UNIX? 2–4 2.5 IS HP CONTINUING
    [Show full text]