Openvms User's Manual

Total Page:16

File Type:pdf, Size:1020Kb

Openvms User's Manual OpenVMS User’s Manual Order Number: AA–PV5JF–TK June 2002 This manual describes how to use the Compaq OpenVMS operating system. The information contained in this manual is intended for all OpenVMS users and is applicable to all computers running the OpenVMS operating system. Revision/Update Information: This manual supersedes the OpenVMS User’s Manual, Version 7.3. Software Version: OpenVMS Alpha Version 7.3–1 OpenVMS VAX Version 7.3 Compaq Computer Corporation Houston, Texas © 2002 Compaq Computer Corporation Compaq, the Compaq logo, AlphaServer, OpenVMS, POLYCENTER, Tru64, VAX, VMS, and the DIGITAL logo are trademarks of Compaq Information Technologies Group, L.P. in the U.S. and/or other countries. UNIX and X/Open are trademarks of The Open Group in the U.S. and/or other countries. All other product names mentioned herein may be trademarks of their respective companies. Confidential computer software. Valid license from Compaq required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. Compaq shall not be liable for technical or editorial errors or omissions contained herein. The information in this document is provided "as is" without warranty of any kind and is subject to change without notice. The warranties for Compaq products are set forth in the express limited warranty statements accompanying such products. Nothing herein should be construed as constituting an additional warranty. ZK6489 The Compaq OpenVMS documentation set is available on CD-ROM. Contents Preface ............................................................ xix 1 Getting Started with the OpenVMS Operating System 1.1 Logging In . ................................................ 1–1 1.1.1 Successful Logins . ........................................ 1–2 1.1.2 Login Errors ............................................. 1–3 1.2 Logging In From a PC ........................................ 1–3 1.3 Choosing Passwords for Your Account ............................ 1–3 1.3.1 Obtaining Your Initial Password ............................. 1–4 1.3.2 Changing Your Initial Password ............................. 1–4 1.3.3 Restrictions on Passwords . ................................ 1–4 1.3.4 Types of Passwords ....................................... 1–5 1.3.5 Entering a System Password ................................ 1–5 1.3.6 Entering a Secondary Password .............................. 1–6 1.3.7 Password Requirements for Different Types of Accounts ........... 1–6 1.4 Reading Informational Messages ................................ 1–7 1.4.1 Suppressing Messages ..................................... 1–8 1.4.2 Successful Login Messages . ................................ 1–8 1.5 Types of Logins and Login Classes ............................... 1–8 1.5.1 Interactive Logins ........................................ 1–8 1.5.2 Noninteractive Logins ..................................... 1–9 1.6 Login Failures .............................................. 1–9 1.6.1 Terminals That Require System Passwords ..................... 1–10 1.6.2 Login Class Restrictions .................................... 1–10 1.6.3 Shift Restrictions . ........................................ 1–10 1.6.4 Batch Jobs During Shift Restrictions . ....................... 1–10 1.6.5 Failures During Dialup Logins .............................. 1–11 1.6.6 Break-In Evasion Procedures ................................ 1–11 1.7 Changing Passwords . ........................................ 1–11 1.7.1 Selecting Your Own Password ............................... 1–12 1.7.2 Using Generated Passwords . ................................ 1–12 1.7.3 Generated Passwords: Disadvantages . ....................... 1–13 1.7.4 Changing a Secondary Password ............................. 1–13 1.7.5 Changing Passwords at Login ............................... 1–14 1.8 Password and Account Expiration Times . ....................... 1–14 1.8.1 Expired Passwords ........................................ 1–14 1.8.2 Using Secondary Passwords . ................................ 1–14 1.8.3 Failure to Change Passwords ................................ 1–15 1.8.4 Expired Accounts . ........................................ 1–15 1.9 Guidelines for Protecting Your Password . ....................... 1–15 1.10 Recognizing System Responses . ................................ 1–16 1.10.1 Default Actions . ........................................ 1–16 1.10.2 Informational System Messages .............................. 1–16 iii 1.10.3 System Error Messages .................................... 1–17 1.10.4 Checking Your Current Process . ............................ 1–17 1.11 Getting Help About the System ................................. 1–18 1.11.1 Using Online Help ........................................ 1–18 1.11.2 Getting Help on Specific Commands .......................... 1–19 1.11.3 Getting Help on System Messages ............................ 1–19 1.12 Logging Out of the System . .................................... 1–20 1.12.1 Obtaining Accounting Information ............................ 1–20 1.12.2 Ending a Remote Session ................................... 1–20 1.12.3 Lost Network Connections .................................. 1–20 1.13 Logging Out Without Compromising System Security ................ 1–21 1.14 Networks .................................................. 1–21 1.14.1 Network Nodes .......................................... 1–21 1.14.2 Executing Programs over Networks ........................... 1–22 2 Using DCL to Interact with the System 2.1 Entering Commands ......................................... 2–2 2.1.1 Usage Modes ............................................ 2–2 2.1.2 Types of DCL Commands ................................... 2–3 2.2 The DCL Command Line . .................................... 2–3 2.2.1 Syntax ................................................. 2–4 2.2.2 Canceling Commands . .................................... 2–5 2.2.3 Using Defaults ........................................... 2–5 2.2.4 Entering Multiple Line Commands ........................... 2–5 2.3 Rules for Entering DCL Commands . ............................ 2–6 2.4 Entering Parameters ......................................... 2–7 2.5 Entering Qualifiers .......................................... 2–7 2.5.1 Command Qualifiers . .................................... 2–8 2.5.2 Positional Qualifiers . .................................... 2–8 2.5.3 Parameter Qualifiers . .................................... 2–8 2.5.4 Conflicting Qualifiers . .................................... 2–9 2.5.5 Values Accepted by Qualifiers . ............................ 2–9 2.6 Entering Dates and Times as Values . ............................ 2–9 2.6.1 Absolute Time Format . .................................... 2–10 2.6.2 Delta Time Format ........................................ 2–10 2.6.3 Combination Time Format .................................. 2–11 2.7 Recalling Commands ......................................... 2–12 2.7.1 Pressing Ctrl/B .......................................... 2–12 2.7.2 Using Arrow Keys ........................................ 2–12 2.7.3 Using the RECALL Command . ............................ 2–13 2.8 Editing the DCL Command Line ................................ 2–14 2.8.1 SET TERMINAL Command ................................. 2–14 2.8.2 Deleting Parts of the Command Line .......................... 2–15 2.9 Defining Terminal Keys . .................................... 2–15 2.10 Key Sequences . ............................................ 2–15 iv 3 Storing Information with Files 3.1 Understanding File Names and File Specifications . ............... 3–2 3.1.1 Providing a Complete File Specification . ....................... 3–2 3.1.2 Rules for File Specifications . ................................ 3–3 3.1.3 Default File Types Used by DCL Commands .................... 3–4 3.1.4 Default File Types for Language Source Programs ............... 3–4 3.1.5 File Versions ............................................ 3–5 3.1.6 Network Node Names ..................................... 3–6 3.1.7 Specifying DECnet-Plus Node Full Names ...................... 3–6 3.1.8 Specifying TCP/IP Names and Addresses ...................... 3–7 3.1.9 Accessing Files on Remote Nodes Using DECnet . ............... 3–7 3.1.10 Accessing Files on Remote Nodes Using TCP/IP . ............... 3–8 3.1.11 Using Network File Specifications ............................ 3–8 3.1.11.1 Conventional File Specification ........................... 3–8 3.1.11.2 Foreign File Specification ................................ 3–8 3.1.11.3 Task Specification Strings ............................... 3–8 3.1.12 Access Control String Format ............................... 3–9 3.2 Using Wildcards with File Names ............................... 3–9 3.2.1 Asterisk ( * ) Wildcard Character ............................. 3–9 3.2.2 Percent Sign ( % ) Wildcard Character . ....................... 3–10 3.3 Other File Names . ........................................ 3–10 3.3.1 Null File Names and File Types .............................. 3–11 3.3.1.1 File References with Null File Types ....................... 3–11 3.3.2 Alternate File Names for Magnetic Tapes ...................... 3–11 3.4 Creating and Modifying Files . ................................ 3–12 3.4.1 Creating Files . ........................................ 3–12 3.4.2
Recommended publications
  • A Case Against the GOT' O William a . Wulf, Carnegie-Mellon Universit Y
    A Case Against the GOT' O William A . Wulf, Carnegie-Mellon Universit y ABSTRAC T suggestion to ban the goto appears to have been a part of the computing folklore for several years , It has been proposed, by E . W . Dijkstra and others , to this author's knowledge the suggestion wa s that the goto statement in programming language i s first made in print by Professor E . W . Dijkstra i n a principal culprit in programs which are diffi- a letter to the editor of the _Communications o f cult to understand, modify, and debug . More cor- the ACM in 1968 (1) . rectly, the argument is that it is possible t o In this paper we shall examine the rational e use the goto to synthesize program structures wit h for the elimination of the Soto in programin g these undesirable properties . Not all uses of th e languages, and some of the theoretical and practi- goto are to be considered harmful ; however, it i s cal implications of its (total) elimination . further argued that the "good" uses of the got o fall into one of a small number of specific case s RATIONAL E which may be handled by specific language con- structs . This paper summarizes the arguments i n At one level, the rationale for eliminatin g favor of eliminating the goto statement and som e the poto has already been given in the introduc- of the theoretical and practical implications o f tion . Namely, it is possible to use the goto in a the proposal . manner which obscures the logical structure of a program to a point where it becomes virtually im- KEY WORDS AND PHRASES : programming, programmin g possible to understand (1,3,4), It is not claimed languages, goto-less programming, structured pro- that every use of the goto obscures the logica l grammin g structure of a program ; it is only claimed that i t CR CATEGORIES : 4 .2, 4 .22, 5 .2 4 is possible to use the Soto to fabricate a "rat' s nest" of control flow which has the undesirabl e INTRODUCTION properties mentioned above .
    [Show full text]
  • The Linux Kernel Module Programming Guide
    The Linux Kernel Module Programming Guide Peter Jay Salzman Michael Burian Ori Pomerantz Copyright © 2001 Peter Jay Salzman 2007−05−18 ver 2.6.4 The Linux Kernel Module Programming Guide is a free book; you may reproduce and/or modify it under the terms of the Open Software License, version 1.1. You can obtain a copy of this license at http://opensource.org/licenses/osl.php. This book is distributed in the hope it will be useful, but without any warranty, without even the implied warranty of merchantability or fitness for a particular purpose. The author encourages wide distribution of this book for personal or commercial use, provided the above copyright notice remains intact and the method adheres to the provisions of the Open Software License. In summary, you may copy and distribute this book free of charge or for a profit. No explicit permission is required from the author for reproduction of this book in any medium, physical or electronic. Derivative works and translations of this document must be placed under the Open Software License, and the original copyright notice must remain intact. If you have contributed new material to this book, you must make the material and source code available for your revisions. Please make revisions and updates available directly to the document maintainer, Peter Jay Salzman <[email protected]>. This will allow for the merging of updates and provide consistent revisions to the Linux community. If you publish or distribute this book commercially, donations, royalties, and/or printed copies are greatly appreciated by the author and the Linux Documentation Project (LDP).
    [Show full text]
  • Openvms Record Management Services Reference Manual
    OpenVMS Record Management Services Reference Manual Order Number: AA-PV6RD-TK April 2001 This reference manual contains general information intended for use in any OpenVMS programming language, as well as specific information on writing programs that use OpenVMS Record Management Services (OpenVMS RMS). Revision/Update Information: This manual supersedes the OpenVMS Record Management Services Reference Manual, OpenVMS Alpha Version 7.2 and 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, AlphaServer, VAX, VMS, the Compaq logo Registered in U.S. Patent and Trademark Office. Alpha, PATHWORKS, DECnet, DEC, and OpenVMS are trademarks of Compaq Information Technologies Group, L.P. in the United States and other countries. UNIX and X/Open are trademarks of The Open Group in the United States and other countries. All other product names mentioned herein may be the trademarks of their respective companies. Confidential computer software. Valid license from Compaq required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. Compaq shall not be liable for technical or editorial errors or omissions contained herein. The information in this document is provided "as is" without warranty of any kind and is subject to change without notice. The warranties for Compaq products are set forth in the express limited warranty statements accompanying such products. Nothing herein should be construed as constituting an additional warranty.
    [Show full text]
  • Writing Your First Linux Kernel Module
    Writing your first Linux kernel module Praktikum Kernel Programming University of Hamburg Scientific Computing Winter semester 2014/2015 Outline ● Before you start ● Hello world module ● Compile, load and unload ● User space VS. kernel space programing ● Summary Before you start ● Define your module’s goal ● Define your module behaviour ● Know your hardware specifications ○ If you are building a device driver you should have the manual ● Documentation ○ /usr/src/linux/Documentation ○ make { htmldocs | psdocs | pdfdocks | rtfdocks } ○ /usr/src/linux/Documentation/DocBook Role of the device driver ● Software layer between application and device “black boxes” ○ Offer abstraction ■ Make hardware available to users ○ Hide complexity ■ User does not need to know their implementation ● Provide mechanism not policy ○ Mechanism ■ Providing the flexibility and the ability the device supports ○ Policy ■ Controlling how these capabilities are being used Role of the device driver ● Policy-free characteristics ○ Synchronous and asynchronous operations ○ Exploit the full capabilities of the hardware ○ Often a client library is provided as well ■ Provides capabilities that do not need to be implemented inside the module Outline ● Before you start ● Hello world module ● Compile, load and unload ● User space VS. kernel space programing ● Summary Hello world module /* header files */ #include <linux/module.h> #include <linux/init.h> /* the initialization function */ /* the shutdown function */ static int __init hello_init(void) { static void __exit hello_exit(void)
    [Show full text]
  • The Backspace
    spumante e rosato* (choose 2) per la tavola glera NV lunetta prosecco, veneto straw, baked apple, peach 11 43 farm greens :: giardiniera, red onion, pecorino romano lambrusco NV medici ermete, emilia romagna black currant, violet, graphite 10 39 lamb & pork meatballs :: stewed tomato, bread crumb, asiago, mint NV l’onesta, emilia romagna fresh strawberry, violet, orange zest 11 43 baked ricotta :: lemon, poached tomato, olive oil * lambrusco whipped lardo bruschetta :: herbs, citrus segment * aglianico 2015 feudi di san gregorio ‘ros‘aura’, irpinia, campania fresh strawberry, rose petal 12 47 shishito peppers :: melon, basil roasted corn :: ricotta, pesto bianco bombino bianco 2016 poderi dal nespoli “pagadebit”, romagna gooseberry, apple, hawthorn blossom 11 43 antipasti (choose 3) pinot grigio 2015 ronchi di pietro, friuli hazelnut, white peach, limestone 48 sweet potato :: cippolini onion, mushroom, rosemary friulano 2014 villa chiopris, friuli grave straw, white flowers, almond 10 39 braised greens :: golden raisins, pecan, red pepper falanghina 2014 terredora, campagna lemon, quince, pear 13 51 :: tomato, basil, balsamic house-made mozzarella chardonnay 2014 tenute del cabreo ‘la pietra’, chianti classico peach preserves, salted popcorn, vanilla 85 roasted beets :: celery, lemon zest, pepperoncini moscato 2015 oddera cascina di fiori, asti tangerine, peach, sage 12 47 the backspace marinated olives :: lemon, rosemary, oregano green beans :: pancetta, garlic, lemon family-style menu rosso $20 per guest pizze (choose 2) pergola rosso
    [Show full text]
  • Video Terminal User 'Guide
    VIDEO TERMINAL USER 'GUIDE EK-VT101-UG-002 VIDEO TERMINAL USER GUIDE digital equipment corporation. maynard, massachusetts 1st Edition, March 1981 2nd Edition, April 1981 Copyright 0 1981 by Digital Equipment Corporation All Rights Reserved The Federal Communications Commission of the United States Government has published regulations which govern the allowable limits of emanation of radio frequency energy of computing devices and associated peripherals. These regulations are concerned with interference to radio communication, such as radio and TV. The regulations require equipment for end use in the United States to be labeled and to be accompanied by the notice appearing below. To minimize the potential for interference, Digital supplied interconnecting cables should be used. NOTICE Th i s equipment gene ra tes and uses rad io frequency ene rgy. I t has been type tested and found to comply with the limits for a Class B computing device in accordance with the specifications in Subpart J of Part 15 of FCC Rules, which are designed to provide reasonable protection against radio and television interference in a residential installation. However, there is no guarantee that interference will not occur in q particular installation. If this equipment does cause interference to radio or television reception, the user is encouraged to try to correct the interference. Printed in U.S.A. The following are trademarks of Digital Equipment Corporation, Maynard, Massachusetts. DEC DECnet lAS DECUS DECsystem-10 MASSBUS DIGITAL DECSYS'rEM-20 PDT Digital Logo DECwriter RSTS PDP DIBOL RSX UNIBUS EduSystem VMS VAX OMNIBUS VT OS/8 CONTENTS CHAPTER 1 OPERATING INFORMATION General .
    [Show full text]
  • Oracle Database Installation Guide 10G Release 2 (10.2)
    Oracle®[1] Database Installation Guide 11g Release 2 (11.2) for HP OpenVMS Itanium E56668-01 June 2015 Oracle Database Installation Guide, 11g Release 2 (11.2) for HP OpenVMS Itanium E56668-01 Copyright © 2008, 2015, Oracle and/or its affiliates. All rights reserved. Primary Author: Nisha Sridhar Contributors: Dave Hayter, Gary Huffman, Marc Noel, Chris Schuetz, David Miller, Kevin Duffy, Steve Holck, Grant Hayden, Gary Tate This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs.
    [Show full text]
  • Storageworks RAID Array 200 Online Mgt Utility for Openvms AXP User's
    StorageWorks RAID Array 200 Online Management Utility for OpenVMS AXP User's Guide AA–Q6WVB–TE Digital Equipment Corporation Maynard, Massachusetts Second Printing, April 1995 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 might 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 1995 by Digital Equipment Corporation. All rights reserved. Printed in the U.S.A. The following are trademarks of Digital Equipment Corporation: AXP, OpenVMS, StorageWorks, SWXCR, and the Digital logo. The following are third-party trademarks: Microsoft and MS-DOS are registered trademarks and Windows is a trademark of Microsoft Corporation. Intel, Intel486, and i486 are trademarks of Intel Corporation. All other trademarks and registered trademarks are the property of their respective holders. Contents Revision Record...................................................................................................................ix About This Guide ...............................................................................................................xi 1 Installing the RAID Array
    [Show full text]
  • Software Product Description and Quickspecs
    VSI OpenVMS Alpha Version 8.4-2L2 Operating System DO-DVASPQ-01A Software Product Description and QuickSpecs PRODUCT NAME: VSI OpenVMS Alpha Version 8.4-2L2 DO-DVASPQ-01A This SPD and QuickSpecs describes the VSI OpenVMS Alpha Performance Release Operating System software, Version 8.4-2L2 (hereafter referred to as VSI OpenVMS Alpha V8.4-2L2). DESCRIPTION OpenVMS is a general purpose, multiuser operating system that runs in both production and development environments. VSI OpenVMS Alpha Version 8.4-2L2 is the latest release of the OpenVMS Alpha computing environment by VMS Software, Inc (VSI). VSI OpenVMS Alpha V8.4-2L2 is compiled to take advantage of architectural features such as byte and word memory reference instructions, and floating-point improvements, which are available only in HPE AlphaServer EV6 or later processors. This optimized release improves performance by taking advantage of faster hardware-based instructions that were previously emulated in software. NOTE: VSI OpenVMS Alpha V8.4-2L2 does not work on, and is not supported on, HPE AlphaServer pre-EV6 systems. OpenVMS Alpha supports HPE’s AlphaServer series computers. OpenVMS software supports industry standards, facilitating application portability and interoperability. OpenVMS provides symmetric multiprocessing (SMP) support for multiprocessing systems. The OpenVMS operating system can be tuned to perform well in a wide variety of environments. This includes combinations of compute-intensive, I/O-intensive, client/server, real-time, and other environments. Actual system performance depends on the type of computer, available physical memory, and the number and type of active disk and tape drives. The OpenVMS operating system has well-integrated networking, distributed computing, client/server, windowing, multi-processing, and authentication capabilities.
    [Show full text]
  • Openvms: an Introduction
    The Operating System Handbook or, Fake Your Way Through Minis and Mainframes by Bob DuCharme VMS Table of Contents Chapter 7 OpenVMS: An Introduction.............................................................................. 7.1 History..........................................................................................................................2 7.1.1 Today........................................................................................................................3 7.1.1.1 Popular VMS Software..........................................................................................4 7.1.2 VMS, DCL................................................................................................................4 Chapter 8 Getting Started with OpenVMS........................................................................ 8.1 Starting Up...................................................................................................................7 8.1.1 Finishing Your VMS Session...................................................................................7 8.1.1.1 Reconnecting..........................................................................................................7 8.1.2 Entering Commands..................................................................................................8 8.1.2.1 Retrieving Previous Commands............................................................................9 8.1.2.2 Aborting Screen Output.........................................................................................9
    [Show full text]
  • PDP-11 C Guide to PDP-11 C
    PDP-11 C Guide to PDP-11 C Available tables: ● Contents (316 entries) ● Examples (29 entries) ● Figures (7 entries) ● Tables (24 entries) ● Index (887 entries) Contents (316 entries) CONTENTS ● Title Page ● Copyright Page ● Preface ● 1 Developing PDP-11 C Programs ● 1.1 DCL Commands for Program Development ● 1.2 Creating a PDP-11 C Program ● 1.2.1 Using EDT ● 1.2.2 Using VAXTPU ● 1.2.3 Using KED ● 1.3 Compiling a PDP-11 C Program ● 1.3.1 The Compile Command http://www.sysworks.com.au/disk$vaxdocsep953/decw$book/d33vaa11.decw$book (1 of 15)1/25/06 3:39 PM PDP-11 C Guide to PDP-11 C ● 1.3.1.1 Compiling a Program on RSX Systems ● 1.3.1.2 Compiling a Program on RSTS/E Systems ● 1.3.1.3 Compiling a Program on RT-11 Systems ● 1.3.1.4 Compiling a Program on VMS Systems ● 1.3.2 Prompt Mode ● 1.3.3 Indirect Command Files ● 1.3.4 The PDP-11 C Command Qualifiers ● 1.3.5 Compiler Error Messages ● 1.3.6 Compiler Listings ● 1.4 Copying Files Among Target Environments ● 1.4.1 File Transfer (FIT) Program ● 1.4.2 File Transfer Utility (FLX) ● 1.4.3 VMS EXCHANGE Utility ● 1.5 Linking a PDP-11 C Program ● 1.5.1 Linking a Program on RSX Systems ● 1.5.2 Linking a Program on RSTS/E Systems ● 1.5.2.1 Invoking the RSX Task Builder on RSTS/E ● 1.5.2.2 Invoking the RT-11 Linker on RSTS/E ● 1.5.3 Linking a Program on RT-11 Systems ● 1.5.4 Linking a Program on VMS Systems ● 1.5.5 Task Builder Command-Line Elements ● 1.5.5.1 Creating CMD and ODL Files for Task Building http://www.sysworks.com.au/disk$vaxdocsep953/decw$book/d33vaa11.decw$book (2 of 15)1/25/06 3:39
    [Show full text]
  • Section 11: Tennis Operations
    Section 11: Tennis Operations Sport Insert: LL-2483 The Sport Insert drawing is located at the end of this section. The Team Name insert and Block Diagram drawings are located in Appendix A. Reference Drawings: Insert, Tennis ............................................................................Drawing A-131274 Insert, Team Name ...................................................................Drawing A-125290 Block Diagrams, A/S5000/3000, Outdoor Sports .....................Drawing A-124690 Refer to the information in Section 2 to start up the console and use the sport insert. Read Section 2 carefully to fully understand the following operation instructions. If an insert is lost or damaged, a copy of the insert drawing located at the end of this section can be used until a replacement can be ordered. Use the labels provided in Appendix B to attach the correct code number label to the sport insert in the appropriate location. Write the code number in the space provided below. Write the correct code number here. If you do not know the code number to enter for your scoreboard, refer to Appendix B in this manual. If you do not know the model number of your scoreboard, refer to the Installation and Maintenance manual provided with the scoreboard. 11.1 Tennis Keys Serve LCD Display Action TOP SERVE <SERVE> turns the serve indicators on or off for the ON respective player. Tennis 11-1 Matches Won +1 LCD Display Action Matches won +1 Press <MATCHES WON +1> to increment the matches won for the current team. Top nn Nn = current matches won Games Won LCD Display Action GAMES WON +1 Press <GAMES WON +1> to increment the number of games won in the current set for the respective player.
    [Show full text]