DOCSLIB.ORG

Openvms Record Management Services Reference Manual

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read 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. ZK4523 The Compaq OpenVMS documentation set is available on CD-ROM. This document was prepared using DECdocument, Version 3.3-1b. Contents Preface ............................................................ xv Part I OpenVMS RMS—General Information 1 Introduction to RMS 1.1 RMS Functions ............................................. 1–1 1.2 Passing Arguments to RMS .................................... 1–3 1.2.1 Record Management Services and Control Blocks . ............... 1–3 1.2.2 Control Blocks for File Services .............................. 1–4 1.2.3 Control Blocks for Record Services ............................ 1–5 1.2.4 Dual Purpose of Control Blocks .............................. 1–5 2 RMS Program Interface 2.1 RMS Run-Time Environment . ................................ 2–1 2.2 Conventions for Naming Fields . ................................ 2–2 2.3 RMS Calling Sequence ........................................ 2–4 2.4 Service Completion . ........................................ 2–5 2.4.1 Illformed Calls to RMS .................................... 2–5 2.4.2 Setting Synchronous or Asynchronous Option ................... 2–5 2.4.3 Synchronous Completion . ................................ 2–6 2.4.4 Asynchronous Completion . ................................ 2–6 2.4.5 Status Code Testing ....................................... 2–7 2.4.6 Types of Errors . ........................................ 2–8 2.5 Allowable Program Execution Modes ............................. 2–9 2.6 Access-Mode Protected Memory . ................................ 2–9 2.7 Reserved Event Flags ........................................ 2–9 2.8 DEC Multinational Character Set ............................... 2–10 3 Implementing RMS from C Programs 3.1 Creating, Accessing, and Deaccessing a File ....................... 3–1 3.1.1 Example of Copying Records from One File to Another File . ....... 3–2 3.2 Program to Illustrate Record Operations . ....................... 3–5 3.3 Program to Show Index Root Levels ............................. 3–8 3.4 Program to Illustrate Using NAML Blocks for Extended File Specifications (Alpha Only) .................................... 3–9 3.5 Program to Illustrate Using the RAB64 Structure ................... 3–12 iii Part II RMS Control Blocks 4 File Access Block (FAB) 4.1 Summary of Fields ........................................... 4–1 4.2 FAB$B_ACMODES Field . .................................... 4–3 4.3 FAB$L_ALQ Field ........................................... 4–3 4.4 FAB$B_BID Field ........................................... 4–3 4.5 FAB$B_BKS Field ........................................... 4–3 4.6 FAB$B_BLN Field ........................................... 4–4 4.7 FAB$W_BLS Field ........................................... 4–5 4.8 FAB$V_CHAN_MODE Subfield ................................. 4–5 4.8.1 Override Value........................................... 4–5 4.8.2 Channel Access Mode Function . ............................ 4–6 4.9 FAB$L_CTX Field ........................................... 4–6 4.10 FAB$W_DEQ Field .......................................... 4–6 4.11 FAB$L_DEV Field ........................................... 4–7 4.12 FAB$L_DNA Field ........................................... 4–9 4.13 FAB$B_DNS Field ........................................... 4–9 4.14 FAB$B_FAC Field ........................................... 4–9 4.15 FAB$L_FNA Field ........................................... 4–11 4.16 FAB$B_FNS Field ........................................... 4–12 4.17 FAB$L_FOP Field ........................................... 4–12 4.18 FAB$B_FSZ Field ........................................... 4–18 4.19 FAB$W_GBC Field .......................................... 4–18 4.20 FAB$W_IFI Field ............................................ 4–20 4.21 FAB$B_JOURNAL Field . .................................... 4–20 4.22 FAB$V_LNM_MODE Subfield .................................. 4–21 4.23 FAB$L_MRN Field ........................................... 4–21 4.24 FAB$W_MRS Field .......................................... 4–22 4.25 FAB$L_NAM Field .......................................... 4–23 4.26 FAB$B_ORG Field ........................................... 4–24 4.27 FAB$B_RAT Field ........................................... 4–24 4.28 FAB$B_RFM Field ........................................... 4–26 4.29 FAB$B_RTV Field ........................................... 4–27 4.30 FAB$L_SDC Field ........................................... 4–27 4.31 FAB$B_SHR Field ........................................... 4–28 4.32 FAB$L_STS Field ............................................ 4–30 4.33 FAB$L_STV Field ........................................... 4–30 4.34 FAB$L_XAB Field ........................................... 4–30 5 Name Block (NAM) 5.1 Summary of Fields ........................................... 5–1 5.2 File Specification Component Descriptors ......................... 5–3 5.3 NAM$B_BID Field ........................................... 5–4 5.4 NAM$B_BLN Field .......................................... 5–4 5.5 NAM$B_DEV and NAM$L_DEV Fields ........................... 5–4 5.6 NAM$W_DID Field .......................................... 5–4 5.7 NAM$B_DIR and NAM$L_DIR Fields ............................ 5–4 5.8 NAM$T_DVI Field ........................................... 5–5 5.9 NAM$L_ESA Field ........................................... 5–5 5.10 NAM$B_ESL Field ........................................... 5–5 5.11 NAM$B_ESS Field ........................................... 5–5 iv 5.12 NAM$W_FID Field . ........................................ 5–5 5.13 NAM$W_FIRST_WILD_DIR Field ............................... 5–5 5.14 NAM$L_FNB Field . ........................................ 5–6 5.15 NAM$W_LONG_DIR_LEVELS Field ............................. 5–7 5.16 NAM$B_NAME and NAM$L_NAME Fields ....................... 5–7 5.17 NAM$B_NMC .............................................. 5–8 5.18 NAM$B_NODE and NAM$L_NODE Fields . ....................... 5–8 5.19 NAM$B_NOP Field . ........................................ 5–8 5.20 NAM$L_RLF Field . ........................................ 5–9 5.21 NAM$L_RSA Field . ........................................ 5–10 5.22 NAM$B_RSL Field . ........................................ 5–10 5.23 NAM$B_RSS Field . ........................................ 5–10 5.24 NAM$B_TYPE and NAM$L_TYPE Fields . ....................... 5–10 5.25 NAM$B_VER and NAM$L_VER Fields ........................... 5–10 5.26 NAM$L_WCC Field . ........................................ 5–11 6 Long Name Block (NAML) 6.1 Using the NAM and NAML Block ............................... 6–1 6.2 Summary of Fields . ........................................ 6–2 6.3 Validating the NAML Block .................................... 6–5 6.4 NAML$B_BID Field . ........................................ 6–5 6.5 NAML$B_BLN Field . ........................................ 6–5 6.6 NAML$L_FILESYS_NAME Field ............................... 6–5 6.7 NAML$L_FILESYS_NAME_ALLOC Field . ....................... 6–5 6.8 NAML$L_FILESYS_NAME_SIZE Field ........................... 6–6 6.9 NAML$L_INPUT_FLAGS Field . ................................ 6–6 6.10 NAML$L_LONG_DEFNAME and NAML$L_LONG_DEFNAME_SIZE Fields ..................................................... 6–6 6.11 NAML$L_LONG_DEV and NAML$L_LONG_DEV_SIZE Fields . ....... 6–6 6.12 NAML$L_LONG_DIR and NAML$L_LONG_DIR_SIZE Fields . ....... 6–7 6.13 NAML$L_LONG_EXPAND Field ................................ 6–7 6.14 NAML$L_LONG_EXPAND_ALLOC Field . ....................... 6–7 6.15 NAML$L_LONG_EXPAND_SIZE Field ........................... 6–7 6.16 NAML$L_LONG_FILENAME and NAML$L_LONG_FILENAME_SIZE Fields ..................................................... 6–7 6.17 NAML$L_LONG_NAME
Load more

Recommended publications
  • A Microkernel API for Fine-Grained Decomposition
    A Microkernel API for Fine-Grained Decomposition Sebastian Reichelt Jan Stoess Frank Bellosa System Architecture Group, University of Karlsruhe, Germany freichelt,stoess,[email protected] ABSTRACT from the microkernel APIs in existence. The need, for in- Microkernel-based operating systems typically require spe- stance, to explicitly pass messages between servers, or the cial attention to issues that otherwise arise only in dis- need to set up threads and address spaces in every server for tributed systems. The resulting extra code degrades per- parallelism or protection require OS developers to adopt the formance and increases development effort, severely limiting mindset of a distributed-system programmer rather than to decomposition granularity. take advantage of their knowledge on traditional OS design. We present a new microkernel design that enables OS devel- Distributed-system paradigms, though well-understood and opers to decompose systems into very fine-grained servers. suited for physically (and, thus, coarsely) partitioned sys- We avoid the typical obstacles by defining servers as light- tems, present obstacles to the fine-grained decomposition weight, passive objects. We replace complex IPC mecha- required to exploit the benefits of microkernels: First, a nisms by a simple function-call approach, and our passive, lot of development effort must be spent into matching the module-like server model obviates the need to create threads OS structure to the architecture of the selected microkernel, in every server. Server code is compiled into small self- which also hinders porting existing code from monolithic sys- contained files, which can be loaded into the same address tems. Second, the more servers exist | a desired property space (for speed) or different address spaces (for safety).
    [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]
  • 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]
  • Introduction to Unix
    Introduction to Unix Rob Funk <[email protected]> University Technology Services Workstation Support http://wks.uts.ohio-state.edu/ University Technology Services Course Objectives • basic background in Unix structure • knowledge of getting started • directory navigation and control • file maintenance and display commands • shells • Unix features • text processing University Technology Services Course Objectives Useful commands • working with files • system resources • printing • vi editor University Technology Services In the Introduction to UNIX document 3 • shell programming • Unix command summary tables • short Unix bibliography (also see web site) We will not, however, be covering these topics in the lecture. Numbers on slides indicate page number in book. University Technology Services History of Unix 7–8 1960s multics project (MIT, GE, AT&T) 1970s AT&T Bell Labs 1970s/80s UC Berkeley 1980s DOS imitated many Unix ideas Commercial Unix fragmentation GNU Project 1990s Linux now Unix is widespread and available from many sources, both free and commercial University Technology Services Unix Systems 7–8 SunOS/Solaris Sun Microsystems Digital Unix (Tru64) Digital/Compaq HP-UX Hewlett Packard Irix SGI UNICOS Cray NetBSD, FreeBSD UC Berkeley / the Net Linux Linus Torvalds / the Net University Technology Services Unix Philosophy • Multiuser / Multitasking • Toolbox approach • Flexibility / Freedom • Conciseness • Everything is a file • File system has places, processes have life • Designed by programmers for programmers University Technology Services
    [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]
  • Openvms Security
    OpenVMS Security Presented by Paul Williams PARSEC Group 999 18th Street, Suite 1725 Denver, CO 80202 www.parsec.com | 888-4-PARSEC To Download this Presentation, please visit: http://www.parsec.com/public/openvmssecurity.pdf To E-mail Paul [email protected] www.parsec.com | 888-4-PARSEC Outline • OpenVMS Security Design • Physical Security • Object Security • UIC/ACL Security • User Access • Break-in Detection • Network and Internet Considerations • Encrypted Network Communication • Kerberos • Secure Socket Layer (SSL) Goals • Discuss the important points and consideration of OpenVMS Security • Concentrate on the mechanics and mechanisms of OpenVMS features. • Show how OpenVMS is one of the most secure operating systems on the market. OpenVMS Security Design • Security was designed into OpenVMS since V1.0 • Many different levels of security in OpenVMS Physical Security Object Security User Management Network Security • Has never had a virus Physical Security • System • System Console • Storage devices and media System Disk Data and Database Volumes Backups • Network devices and media Physical Security: System • Increase system reliability through restricted access Prevent intentional tampering and outage Prevent outage due to accidents • Prevent Front Panel Access Halts Reset/initializations Power switch/source Power on action settings (VAX) switch Physical Security: Console • Can be a big security hole for OpenVMS Anyone with physical access to the console can break into OpenVMS buy getting into the SYSBOOT utility. Then OpenVMS can be broken into: Buy redirecting startup Buy changing system parameters Physical Security: Getting to SYSBOOT on the Integrity Console Example • On the Integrity shutdown to the EFI Boot Manager and select the EFI Shell and create a alias.
    [Show full text]
  • Chapter 1. Origins of Mac OS X
    1 Chapter 1. Origins of Mac OS X "Most ideas come from previous ideas." Alan Curtis Kay The Mac OS X operating system represents a rather successful coming together of paradigms, ideologies, and technologies that have often resisted each other in the past. A good example is the cordial relationship that exists between the command-line and graphical interfaces in Mac OS X. The system is a result of the trials and tribulations of Apple and NeXT, as well as their user and developer communities. Mac OS X exemplifies how a capable system can result from the direct or indirect efforts of corporations, academic and research communities, the Open Source and Free Software movements, and, of course, individuals. Apple has been around since 1976, and many accounts of its history have been told. If the story of Apple as a company is fascinating, so is the technical history of Apple's operating systems. In this chapter,[1] we will trace the history of Mac OS X, discussing several technologies whose confluence eventually led to the modern-day Apple operating system. [1] This book's accompanying web site (www.osxbook.com) provides a more detailed technical history of all of Apple's operating systems. 1 2 2 1 1.1. Apple's Quest for the[2] Operating System [2] Whereas the word "the" is used here to designate prominence and desirability, it is an interesting coincidence that "THE" was the name of a multiprogramming system described by Edsger W. Dijkstra in a 1968 paper. It was March 1988. The Macintosh had been around for four years.
    [Show full text]
  • Operating System Support for Parallel Processes
    Operating System Support for Parallel Processes Barret Rhoden Electrical Engineering and Computer Sciences University of California at Berkeley Technical Report No. UCB/EECS-2014-223 http://www.eecs.berkeley.edu/Pubs/TechRpts/2014/EECS-2014-223.html December 18, 2014 Copyright © 2014, by the author(s). All rights reserved. Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. To copy otherwise, to republish, to post on servers or to redistribute to lists, requires prior specific permission. Operating System Support for Parallel Processes by Barret Joseph Rhoden A dissertation submitted in partial satisfaction of the requirements for the degree of Doctor of Philosophy in Computer Science in the Graduate Division of the University of California, Berkeley Committee in charge: Professor Eric Brewer, Chair Professor Krste Asanovi´c Professor David Culler Professor John Chuang Fall 2014 Operating System Support for Parallel Processes Copyright 2014 by Barret Joseph Rhoden 1 Abstract Operating System Support for Parallel Processes by Barret Joseph Rhoden Doctor of Philosophy in Computer Science University of California, Berkeley Professor Eric Brewer, Chair High-performance, parallel programs want uninterrupted access to physical resources. This characterization is true not only for traditional scientific computing, but also for high- priority data center applications that run on parallel processors. These applications require high, predictable performance and low latency, and they are important enough to warrant engineering effort at all levels of the software stack.
    [Show full text]
  • HP C Run-Time Library Reference Manual for Openvms Systems
    HP C Run-Time Library Reference Manual for OpenVMS Systems Order Number: BA554-90014 June 2010 This manual describes the functions and macros in the HP C Run-Time Library for OpenVMS systems. Revision/Update Information: This manual supersedes the HP C Run-Time Library Reference Manual for OpenVMS Systems, Version 8.3 Software Version: OpenVMS Version 8.4 for Integrity servers OpenVMS Alpha Version 8.4 Hewlett-Packard Company Palo Alto, California © Copyright 2010 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP 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. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. UNIX is a registered trademark of The Open Group. X/Open is a registered trademark of X/Open Company Ltd. in the UK and other countries. Intel and Itanium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. Microsoft and Windows are US registered trademarks of Microsoft Corporation. Printed in the US ZK5763 The HP OpenVMS documentation set is available on CD-ROM. This document was prepared using DECdocument, Version 3.3-1b.
    [Show full text]
  • HP Openvms Utility Routines Manual
    HP OpenVMS Utility Routines Manual Order Number: BA554-90019 June 2010 This manual describes the OpenVMS utility routines, a set of routines that provide a programming interface to various OpenVMS utilities. Revision/Update Information: This manual supersedes the HP OpenVMS Utility Routines Manual, OpenVMS Alpha Version 8.3. Software Version: OpenVMS Version 8.4 for Integrity servers OpenVMS Alpha Version 8.4 Hewlett-Packard Company Palo Alto, California © Copyright 2010 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP 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. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Intel and Itanium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. ZK4493 The HP OpenVMS documentation set is available on CD. This document was prepared using DECdocument, Version 3.3-1B. Contents Preface ............................................................ xvii 1 Introduction to Utility Routines 2 Access Control List (ACL) Editor Routine 2.1 Introduction to the ACL Editor Routine ........................... ACL–1 2.2 Using the ACL Editor Routine: An Example ....................... ACL–1 2.3 ACL Editor Routine . ........................................ ACL–2 ACLEDIT$EDIT ...........................................
    [Show full text]
  • The Evolution of the Unix Time-Sharing System*
    The Evolution of the Unix Time-sharing System* Dennis M. Ritchie Bell Laboratories, Murray Hill, NJ, 07974 ABSTRACT This paper presents a brief history of the early development of the Unix operating system. It concentrates on the evolution of the file system, the process-control mechanism, and the idea of pipelined commands. Some attention is paid to social conditions during the development of the system. NOTE: *This paper was first presented at the Language Design and Programming Methodology conference at Sydney, Australia, September 1979. The conference proceedings were published as Lecture Notes in Computer Science #79: Language Design and Programming Methodology, Springer-Verlag, 1980. This rendition is based on a reprinted version appearing in AT&T Bell Laboratories Technical Journal 63 No. 6 Part 2, October 1984, pp. 1577-93. Introduction During the past few years, the Unix operating system has come into wide use, so wide that its very name has become a trademark of Bell Laboratories. Its important characteristics have become known to many people. It has suffered much rewriting and tinkering since the first publication describing it in 1974 [1], but few fundamental changes. However, Unix was born in 1969 not 1974, and the account of its development makes a little-known and perhaps instructive story. This paper presents a technical and social history of the evolution of the system. Origins For computer science at Bell Laboratories, the period 1968-1969 was somewhat unsettled. The main reason for this was the slow, though clearly inevitable, withdrawal of the Labs from the Multics project. To the Labs computing community as a whole, the problem was the increasing obviousness of the failure of Multics to deliver promptly any sort of usable system, let alone the panacea envisioned earlier.
    [Show full text]
  • The 6 Key Benefits of Being an Api-Centric Organization
    THE 6 KEY BENEFITS OF BEING AN API-CENTRIC ORGANIZATION © 2019 Radical I/O Technology Inc. FOREWORD Digital transformation is about more than adopting the latest technologies. It is about maximizing value by using technology to improve efficiency and productivity, drive engagement and growth, and ultimately make the lives of customers, partners and staff better. APIs play an integral role as the connectors between the systems, data, and people that enable digital transformation initiatives. This guide, the first in our series exploring API best practices, therefore focuses on what APIs are, how they work, and outlines six benefits they offer for achieving organizational goals. Radical I/O is a people-first technology consultancy and lab in Vancouver, BC that specializes in data-driven enterprise software development with highly performant API architecture at its core. We understand that the needs of private and public organizations are continually evolving, and we enjoy working collaboratively with our clients and partners to create forward-thinking technology solutions. IAN SIM Chief Technology Officer Radical I/O Technology [email protected] © 2019 Radical I/O Technology Inc. THE 6 KEY BENEFITS OF BEING AN API-CENTRIC ORGANIZATION 3 CONTENTS There’s an API for that ..........................................................................1 What is an API? ..................................................................................... 2 Types of APIs ...........................................................................................4
    [Show full text]