DOCSLIB.ORG

Enterprise PL/I for Z/OS Messages and Codes About This Book

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Enterprise PL/I for z/OS IBM Developer for z Systems PL/I for Windows IBM Messages and Codes Version 5 Release 2 GC27-8950-01 Enterprise PL/I for z/OS IBM Developer for z Systems PL/I for Windows IBM Messages and Codes Version 5 Release 2 GC27-8950-01 Note Before using this information and the product it supports, be sure to read the general information under “Notices” on page 163. First Edition (September 2017) | This edition applies to Version 5 Release 2 of Enterprise PL/I for z/OS (5655-PL5), and Version 9.1 of IBM Developer for z Systems (formerly IBM Rational Developer for System z) PL/I for Windows, and to any subsequent releases until otherwise indicated in new editions or technical newsletters. Make sure you are using the correct edition for the level of the product. Order publications through your IBM representative or the IBM branch office serving your locality. Publications are not stocked at the address below. A form for readers' comments is provided at the back of this publication. If the form has been removed, address your comments to: IBM Corporation, Department H150/090 555 Bailey Ave. San Jose, CA, 95141-1099 United States of America When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. © Copyright IBM Corporation 1999, 2017. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents About this book ........... v Condition codes 501 through 1000 ...... 144 Compiler and preprocessor messages ...... v Condition codes 1001 through 1499 ...... 147 How to send your comments ........ vi Condition codes 1500 through 2000 ...... 149 Accessibility .............. vii Condition codes 2001 through 2500 ...... 156 Condition codes 3000 through 4000 ...... 158 Chapter 1. Compiler Informational Condition codes 4001 through 9999 ...... 159 Messages (1000-1076, 2800-2999, Notices .............. 163 3000-3100).............. 1 Trademarks .............. 164 Chapter 2. Compiler Warning Messages Bibliography............ 165 (1078-1225, 2600-2799) ........ 7 PL/I publications ............ 165 Related publications ........... 165 Chapter 3. Compiler Error Messages (1226-1499, 2400-2599) ........ 27 Chapter 4. Compiler Severe Messages (1500-2399) ............. 51 Chapter 5. MACRO, CICS, and SQL Preprocessor Messages (3000-3999) . 109 Chapter 6. Code Generation Messages (5000-5999) ............ 135 Chapter 7. Condition codes ..... 139 Condition codes 1 through 500 ....... 139 © Copyright IBM Corp. 1999, 2017 iii iv Enterprise PL/I for z/OS Messages and Codes About this book This book is for PL/I programmers and system programmers. It helps you understand compiler and preprocessor messages. Compiler and preprocessor messages This guide lists the compiler messages in numerical order. These messages are also listed in numerical order in the output following the source program and in any other listings produced by the compiler. Format of messages In your compilation output, each compiler message, with the exception of the code generation messages in the range 5000-5999, starts with IBMnnnnI X where: v IBM indicates that the message is a PL/I message. v nnnn is the number of the message. v The closing letter I indicates that no system operator action is required. v The X represents a severity code. In some catastrophic situations, such as not being able to open SYSPRINT, the compiler might not follow the last two of the preceding rules. In this guide, messages are listed numerically. Each compiler message in this section has the form IBMnnnnI X where X is the severity code. Severity codes can be any of the following: I, W, E, S, or U. These severity codes indicate the following. (Note that the return codes listed are the highest return code generated.) I An informational message (RC=0) indicates that the compiled program should run correctly. The compiler might inform you of a possible inefficiency in your code or some other condition of interest. W A warning message (RC=4) warns you that a statement might be in error (warning) even though it is syntactically valid. The compiled program should run correctly, but might produce different results than expected or be significantly inefficient. E An error message (RC=8) describes a simple error fixed by the compiler. The compiled program should run correctly, but might produce different results than expected. S A severe error message (RC=12) describes an error not fixed by the compiler. If the program is compiled and an object module is produced, it should not be used. U An unrecoverable error message (RC=16) signifies an error that forces termination of the compilation. An object module is not successfully created. Compiler messages are printed in groups according to these severity levels and to the component that produced them. © Copyright IBM Corp. 1999, 2017 v The code generation messages (those in the range 5000-5999) start with IBMnnnn where: v IBM indicates that the message is a PL/I message. v nnnn is the number of the message. Under batch, the code generation messages are written to the STDOUT DD data set, while all other messages appear in the listing which is written to the SYSPRINT DD data set. Under z/OS UNIX, the code generation messages are written to stdout, while all other messages appear in the listing and are also written to stdout. The compiler FLAG option suppresses the listing of messages in the compiler listing. You can find a description of the FLAG option in Enterprise PL/I for z/OS Programming Guide. Message inserts Many of the compiler messages contain message inserts indicating where the compiler inserts information when it prints the message. These inserts are emphasized in the messages in this section using italics. Contacting IBM for support If you contact IBM for programming support for a compiler error, it is useful to have a listing of your source program available. To make the analysis of any potential problem easier, it is best if that listing is created with the options: INSOURCE MACRO OPTIONS SOURCE. How to send your comments Your feedback is important in helping us to provide accurate, high-quality information. If you have comments about this document or any other PL/I documentation, contact us in one of these ways: v Use the Online Readers' Comment Form at www.ibm.com/software/awdtools/rcf/ or send an e-mail to [email protected] Be sure to include the name of the document, the publication number of the document, the version of PL/I, and, if applicable, the specific location (for example, page number) of the text that you are commenting on. v Fill out the Readers' Comment Form at the back of this document, and return it by mail or give it to an IBM representative. If the form has been removed, address your comments to: International Business Machines Corporation Reader Comments H150/090 555 Bailey Avenue San Jose, CA 95141-1003 USA v Fax your comments to this U.S. number: (800)426-7773. vi Enterprise PL/I for z/OS Messages and Codes When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. Accessibility Accessibility features assist users who have a disability, such as restricted mobility or limited vision, to use information technology content successfully. The accessibility features in z/OS® provide accessibility for Enterprise PL/I. Accessibility features z/OS includes the following major accessibility features: v Interfaces that are commonly used by screen readers and screen-magnifier software v Keyboard-only navigation v Ability to customize display attributes such as color, contrast, and font size z/OS uses the latest W3C Standard, WAI-ARIA 1.0 (http://www.w3.org/TR/wai- aria/), to ensure compliance to US Section 508 (http://www.access-board.gov/ guidelines-and-standards/communications-and-it/about-the-section-508-standards/ section-508-standards) and Web Content Accessibility Guidelines (WCAG) 2.0 (http://www.w3.org/TR/WCAG20/). To take advantage of accessibility features, use the latest release of your screen reader in combination with the latest web browser that is supported by this product. The Enterprise PL/I online product documentation in IBM® Knowledge Center is enabled for accessibility. The accessibility features of IBM Knowledge Center are described at http://www.ibm.com/support/knowledgecenter/en/about/ releasenotes.html. Keyboard navigation Users can access z/OS user interfaces by using TSO/E or ISPF. | Users can also access z/OS services by using IBM Developer for z Systems. For information about accessing these interfaces, see the following publications: v z/OS TSO/E Primer (http://publib.boulder.ibm.com/cgi-bin/bookmgr/BOOKS/ ikj4p120) v z/OS TSO/E User's Guide (http://publib.boulder.ibm.com/cgi-bin/bookmgr/ BOOKS/ikj4c240/APPENDIX1.3) v z/OS ISPF User's Guide Volume I (http://publib.boulder.ibm.com/cgi-bin/ bookmgr/BOOKS/ispzug70) v IBM Rational® Developer for System z® Knowledge Center (http:// www.ibm.com/support/knowledgecenter/SSQ2R2/rdz_welcome.html?lang=en) These guides describe how to use TSO/E and ISPF, including the use of keyboard shortcuts or function keys (PF keys). Each guide includes the default settings for the PF keys and explains how to modify their functions. About this book vii Interface information The Enterprise PL/I online product documentation is available in IBM Knowledge Center, which is viewable from a standard web browser. PDF files have limited accessibility support. With PDF documentation, you can use optional font enlargement, high-contrast display settings, and can navigate by keyboard alone.
Recommended publications
  • IBM Developer for Z/OS Enterprise Edition

    IBM Developer for Z/OS Enterprise Edition

    Solution Brief IBM Developer for z/OS Enterprise Edition A comprehensive, robust toolset for developing z/OS applications using DevOps software delivery practices Companies must be agile to respond to market demands. The digital transformation is a continuous process, embracing hybrid cloud and the Application Program Interface (API) economy. To capitalize on opportunities, businesses must modernize existing applications and build new cloud native applications without disrupting services. This transformation is led by software delivery teams employing DevOps practices that include continuous integration and continuous delivery to a shared pipeline. For z/OS Developers, this transformation starts with modern tools that empower them to deliver more, faster, with better quality and agility. IBM Developer for z/OS Enterprise Edition is a modern, robust solution that offers the program analysis, edit, user build, debug, and test capabilities z/OS developers need, plus easy integration with the shared pipeline. The challenge IBM z/OS application development and software delivery teams have unique challenges with applications, tools, and skills. Adoption of agile practices Application modernization “DevOps and agile • Mainframe applications • Applications require development on the platform require frequent updates access to digital services have jumped from the early adopter stage in 2016 to • Development teams must with controlled APIs becoming common among adopt DevOps practices to • The journey to cloud mainframe businesses”1 improve their
  • The Machine That Builds Itself: How the Strengths of Lisp Family

    The Machine That Builds Itself: How the Strengths of Lisp Family

    Khomtchouk et al. OPINION NOTE The Machine that Builds Itself: How the Strengths of Lisp Family Languages Facilitate Building Complex and Flexible Bioinformatic Models Bohdan B. Khomtchouk1*, Edmund Weitz2 and Claes Wahlestedt1 *Correspondence: [email protected] Abstract 1Center for Therapeutic Innovation and Department of We address the need for expanding the presence of the Lisp family of Psychiatry and Behavioral programming languages in bioinformatics and computational biology research. Sciences, University of Miami Languages of this family, like Common Lisp, Scheme, or Clojure, facilitate the Miller School of Medicine, 1120 NW 14th ST, Miami, FL, USA creation of powerful and flexible software models that are required for complex 33136 and rapidly evolving domains like biology. We will point out several important key Full list of author information is features that distinguish languages of the Lisp family from other programming available at the end of the article languages and we will explain how these features can aid researchers in becoming more productive and creating better code. We will also show how these features make these languages ideal tools for artificial intelligence and machine learning applications. We will specifically stress the advantages of domain-specific languages (DSL): languages which are specialized to a particular area and thus not only facilitate easier research problem formulation, but also aid in the establishment of standards and best programming practices as applied to the specific research field at hand. DSLs are particularly easy to build in Common Lisp, the most comprehensive Lisp dialect, which is commonly referred to as the “programmable programming language.” We are convinced that Lisp grants programmers unprecedented power to build increasingly sophisticated artificial intelligence systems that may ultimately transform machine learning and AI research in bioinformatics and computational biology.
  • INTRODUCTION to PL/1 PL/I Is a Structured Language to Develop Systems and Applications Programs (Both Business and Scientific)

    INTRODUCTION to PL/1 PL/I Is a Structured Language to Develop Systems and Applications Programs (Both Business and Scientific)

    INTRODUCTION TO PL/1 PL/I is a structured language to develop systems and applications programs (both business and scientific). Significant features : v Allows Free format v Regards a program as a continuous stream of data v Supports subprogram and functions v Uses defaults 1 Created by Sanjay Sinha Building blocks of PL/I : v Made up of a series of subprograms and called Procedure v Program is structured into a MAIN program and subprograms. v Subprograms include subroutine and functions. Every PL/I program consists of : v At least one Procedure v Blocks v Group 2 Created by Sanjay Sinha v There must be one and only one MAIN procedure to every program, the MAIN procedure statement consists of : v Label v The statement ‘PROCEDURE OPTIONS (MAIN)’ v A semicolon to mark the end of the statement. Coding a Program : 1. Comment line(s) begins with /* and ends with */. Although comments may be embedded within a PL/I statements , but it is recommended to keep the embedded comments minimum. 3 Created by Sanjay Sinha 2. The first PL/I statement in the program is the PROCEDURE statement : AVERAGE : PROC[EDURE] OPTIONS(MAIN); AVERAGE -- it is the name of the program(label) and compulsory and marks the beginning of a program. OPTIONS(MAIN) -- compulsory for main programs and if not specified , then the program is a subroutine. A PL/I program is compiled by PL/I compiler and converted into the binary , Object program file for link editing . 4 Created by Sanjay Sinha Advantages of PL/I are : 1. Better integration of sets of programs covering several applications.
  • A Block Design for Introductory Functional Programming in Haskell

    A Block Design for Introductory Functional Programming in Haskell

    A Block Design for Introductory Functional Programming in Haskell Matthew Poole School of Computing University of Portsmouth, UK [email protected] Abstract—This paper describes the visual design of blocks for the learner, and to avoid syntax and type-based errors entirely editing code in the functional language Haskell. The aim of the through blocks-based program construction. proposed blocks-based environment is to support students’ initial steps in learning functional programming. Expression blocks and There exists some recent work in representing functional slots are shaped to ensure constructed code is both syntactically types within blocks-based environments. TypeBlocks [9] in- correct and preserves conventional use of whitespace. The design cludes three basic type connector shapes (for lists, tuples aims to help students learn Haskell’s sophisticated type system and functions) which can be combined in any way and to which is often regarded as challenging for novice functional any depth. The prototype blocks editor for Bootstrap [10], programmers. Types are represented using text, color and shape, [11] represents each of the five types of a simple functional and empty slots indicate valid argument types in order to ensure language using a different color, with a neutral color (gray) that constructed code is well-typed. used for polymorphic blocks; gray blocks change color once their type has been determined during program construction. I. INTRODUCTION Some functional features have also been added to Snap! [12] Blocks-based environments such as Scratch [1] and Snap! and to a modified version of App Inventor [13]. [2] offer several advantages over traditional text-based lan- This paper is structured as follows.
  • High Performance Computing Toolkit: Installation and Usage Guide | Appendix B

    High Performance Computing Toolkit: Installation and Usage Guide | Appendix B

    IBM Parallel Environment Developer Edition High Performance Computing Toolkit Version 2 Release 1 Installation and Usage Guide SC23-7287-00 IBM Parallel Environment Developer Edition High Performance Computing Toolkit Version 2 Release 1 Installation and Usage Guide SC23-7287-00 Note Before using this information and the product it supports, read the information in “Notices” on page 255. This edition applies to version 2, release 1, modification 0 of the IBM Parallel Environment Developer Edition High Performance Computing Toolkit (HPC Toolkit) (product number 5765-PD2) and to all subsequent releases and modifications until otherwise indicated in new editions. © Copyright IBM Corporation 2008, 2014. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Figures ..............vii | Part 3. Using the IBM PE Developer | Edition graphical performance Tables ...............ix || analysis tools ...........21 About this information ........xi | Chapter 6. Using the hpctView Who should read this information .......xi Conventions and terminology used in this || application .............23 information ..............xi || Preparing an application for analysis ......24 Prerequisite and related information ......xii || Working with the application ........25 Parallel Tools Platform component .....xii || Opening the application executable ......25 How to send your comments ........xiii || Instrumenting the application ........28 || Running the instrumented application .....29 Summary of changes ........xv || Viewing performance data .........37 | Chapter 7. Using hardware Limitations and restrictions .....xvii || performance counter profiling.....41 || Preparing an application for profiling......41 Part 1. Introduction .........1 || Instrumenting the application ........41 || Running the instrumented application .....43 Chapter 1. Introduction to the IBM HPC || Viewing hardware performance counter data . 45 Toolkit ...............3 IBM PE Developer Edition components .....3 || Chapter 8.
  • Kednos PL/I for Openvms Systems User Manual

    Kednos PL/I for Openvms Systems User Manual

    ) Kednos PL/I for OpenVMS Systems User Manual Order Number: AA-H951E-TM November 2003 This manual provides an overview of the PL/I programming language. It explains programming with Kednos PL/I on OpenVMS VAX Systems and OpenVMS Alpha Systems. It also describes the operation of the Kednos PL/I compilers and the features of the operating systems that are important to the PL/I programmer. Revision/Update Information: This revised manual supersedes the PL/I User’s Manual for VAX VMS, Order Number AA-H951D-TL. Operating System and Version: For Kednos PL/I for OpenVMS VAX: OpenVMS VAX Version 5.5 or higher For Kednos PL/I for OpenVMS Alpha: OpenVMS Alpha Version 6.2 or higher Software Version: Kednos PL/I Version 3.8 for OpenVMS VAX Kednos PL/I Version 4.4 for OpenVMS Alpha Published by: Kednos Corporation, Pebble Beach, CA, www.Kednos.com First Printing, August 1980 Revised, November 1983 Updated, April 1985 Revised, April 1987 Revised, January 1992 Revised, May 1992 Revised, November 1993 Revised, April 1995 Revised, October 1995 Revised, November 2003 Kednos 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 Kednos Corporation or an anthorized sublicensor.
  • CA XCOM Data Transport for Z/OS User Guide

    CA XCOM Data Transport for Z/OS User Guide

    CA XCOM™ Data Transport® for z/OS User Guide Version 12.0.00 This Documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to as the “Documentation”) is for your informational purposes only and is subject to change or withdrawal by CA at any time. This Documentation is proprietary information of CA and may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. If you are a licensed user of the software product(s) addressed in the Documentation, you may print or otherwise make available a reasonable number of copies of the Documentation for internal use by you and your employees in connection with that software, provided that all CA copyright notices and legends are affixed to each reproduced copy. The right to print or otherwise make available copies of the Documentation is limited to the period during which the applicable license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed. TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION “AS IS” WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE.
  • Program Directory for IBM Enterprise COBOL for Z/OS

    Program Directory for IBM Enterprise COBOL for Z/OS

    IBM Program Directory for IBM Enterprise COBOL for z/OS V06.02.00 Program Number 5655-EC6 FMIDs HADB620, JADB621, JADB622, JADB62H for Use with z/OS Document Date: September 2017 GI13-4526-01 Note Before using this information and the product it supports, be sure to read the general information under 7.0, “Notices” on page 30. © Copyright International Business Machines Corporation 1991, 2017. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents 1.0 Introduction . 1 1.1 Enterprise COBOL Description ......................................... 1 1.2 Enterprise COBOL FMIDs ........................................... 4 2.0 Program Materials . 5 2.1 Basic Machine-Readable Material ....................................... 5 2.2 Optional Machine-Readable Material ..................................... 6 2.3 Program Publications . 6 2.3.1 Optional Program Publications ...................................... 7 2.4 Program Source Materials ........................................... 7 2.5 Publications Useful During Installation .................................... 7 3.0 Program Support . 8 3.1 Program Services . 8 3.2 Preventive Service Planning .......................................... 8 3.3 Statement of Support Procedures ....................................... 9 4.0 Program and Service Level Information ................................. 10 4.1 Program Level Information .......................................... 10 4.2 Service Level Information ..........................................
  • RTL-To-Gates Synthesis Using Synopsys Design Compiler

    RTL-To-Gates Synthesis Using Synopsys Design Compiler

    RTL-to-Gates Synthesis using Synopsys Design Compiler CS250 Tutorial 5 (Version 091210b) September 12, 2010 Yunsup Lee In this tutorial you will gain experience using Synopsys Design Compiler (DC) to perform hardware synthesis. A synthesis tool takes an RTL hardware description and a standard cell library as input and produces a gate-level netlist as output. The resulting gate-level netlist is a completely structural description with standard cells only at the leaves of the design. Internally, a synthesis tool performs many steps including high-level RTL optimizations, RTL to unoptimized boolean logic, technology independent optimizations, and finally technology mapping to the available standard cells. Good RTL designers will familiarize themselves with the target standard cell library so that they can develop an intuition on how their RTL will be synthesized into gates. In this tutorial you will use Synopsys Design Compiler to elaborate RTL, set optimization constraints, synthesize to gates, and prepare various area and timing reports. You will also learn how to read the various DC text reports and how to use the graphical Synopsys Design Vision tool to visualize the synthesized design. Synopsys provides a library called Design Ware which includes highly optimized RTL for arithmetic building blocks. DC can automatically determine when to use Design Ware components and it can then efficiently synthesize these components into gate-level implementations. In this tutorial you will learn more about what Design Ware components are available and how to best encourage DC to use them. The following documentation is located in the course locker (~cs250/manuals) and provides ad- ditional information about Design Compiler, Design Vision, the Design Ware libraries, and the Synopsys 90nm Standard Cell Library.
  • IDL Quick Reference

    IDL Quick Reference

    IDL Quick Reference IDL Version 6.2 July 2005 Edition Copyright © RSI All Rights Reserved 0705IDL62QR Restricted Rights Notice The IDL®, ION Script™, and ION Java™ software programs and the accompanying procedures, functions, and documentation described herein are sold under license agreement. Their use, dupli- cation, and disclosure are subject to the restrictions stated in the license agreement. RSI reserves the right to make changes to this document at any time and without notice. Limitation of Warranty RSI makes no warranties, either express or implied, as to any matter not expressly set forth in the license agreement, including without limitation the condition of the software, merchantability, or fitness for any particular purpose. RSI shall not be liable for any direct, consequential, or other damages suffered by the Licensee or any others resulting from use of the IDL or ION software packages or their documentation. Permission to Reproduce this Manual If you are a licensed user of this product, RSI grants you a limited, nontransferable license to repro- duce this particular document provided such copies are for your use only and are not sold or dis- tributed to third parties. All such copies must contain the title page and this notice page in their entirety. Acknowledgments IDL® is a registered trademark and ION™, ION Script™, ION Java™, are trademarks of ITT Industries, registered in the United States Patent and Trademark Office, for the computer program described herein. Numerical Recipes™ is a trademark of Numerical Recipes Software. Numerical Recipes routines are used by permission. GRG2™ is a trademark of Windward Technologies, Inc.
  • UEFI Shell Specification

    UEFI Shell Specification

    UEFI Shell Specification January 26, 2016 Revision 2.2 The material contained herein is not a license, either expressly or impliedly, to any intellectual property owned or controlled by any of the authors or developers of this material or to any contribution thereto. The material contained herein is provided on an "AS IS" basis and, to the maximum extent permitted by applicable law, this information is provided AS IS AND WITH ALL FAULTS, and the authors and developers of this material hereby disclaim all other warranties and conditions, either express, implied or statutory, including, but not limited to, any (if any) implied warranties, duties or conditions of merchantability, of fitness for a particular purpose, of accuracy or completeness of responses, of results, of workmanlike effort, of lack of viruses and of lack of negligence, all with regard to this material and any contribution thereto. Designers must not rely on the absence or characteristics of any features or instructions marked "reserved" or "undefined." The Unified EFI Forum, Inc. reserves any features or instructions so marked for future definition and shall have no responsibility whatsoever for conflicts or incompatibilities arising from future changes to them. ALSO, THERE IS NO WARRANTY OR CONDITION OF TITLE, QUIET ENJOYMENT, QUIET POSSESSION, CORRESPONDENCE TO DESCRIPTION OR NON-INFRINGEMENT WITH REGARD TO THE SPECIFICATION AND ANY CONTRIBUTION THERETO. IN NO EVENT WILL ANY AUTHOR OR DEVELOPER OF THIS MATERIAL OR ANY CONTRIBUTION THERETO BE LIABLE TO ANY OTHER PARTY FOR THE COST OF PROCURING SUBSTITUTE GOODS OR SERVICES, LOST PROFITS, LOSS OF USE, LOSS OF DATA, OR ANY INCIDENTAL, CONSEQUENTIAL, DIRECT, INDIRECT, OR SPECIAL DAMAGES WHETHER UNDER CONTRACT, TORT, WARRANTY, OR OTHERWISE, ARISING IN ANY WAY OUT OF THIS OR ANY OTHER AGREEMENT RELATING TO THIS DOCUMENT, WHETHER OR NOT SUCH PARTY HAD ADVANCE NOTICE OF THE POSSIBILITY OF SUCH DAMAGES.
  • E.W. Dijkstra Archive: on the Cruelty of Really Teaching Computing Science

    E.W. Dijkstra Archive: on the Cruelty of Really Teaching Computing Science

    On the cruelty of really teaching computing science Edsger W. Dijkstra. (EWD1036) http://www.cs.utexas.edu/users/EWD/ewd10xx/EWD1036.PDF The second part of this talk pursues some of the scientific and educational consequences of the assumption that computers represent a radical novelty. In order to give this assumption clear contents, we have to be much more precise as to what we mean in this context by the adjective "radical". We shall do so in the first part of this talk, in which we shall furthermore supply evidence in support of our assumption. The usual way in which we plan today for tomorrow is in yesterday’s vocabulary. We do so, because we try to get away with the concepts we are familiar with and that have acquired their meanings in our past experience. Of course, the words and the concepts don’t quite fit because our future differs from our past, but then we stretch them a little bit. Linguists are quite familiar with the phenomenon that the meanings of words evolve over time, but also know that this is a slow and gradual process. It is the most common way of trying to cope with novelty: by means of metaphors and analogies we try to link the new to the old, the novel to the familiar. Under sufficiently slow and gradual change, it works reasonably well; in the case of a sharp discontinuity, however, the method breaks down: though we may glorify it with the name "common sense", our past experience is no longer relevant, the analogies become too shallow, and the metaphors become more misleading than illuminating.