DOCSLIB.ORG

Introduction to the New Mainframe: Z/OS Basics Access

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Introduction to the New Mainframe: Z/OS Basics Access Glossary of terms and abbreviations This glossary defines technical terms and abbreviations used in the z/OS® Basic Skills Information Center. If you do not find the term you are looking for, refer to the IBM® Glossary of Computing Terms, available from: http://www.ibm.com/ibm/terminology. The following cross-references are used in this glossary: Contrast with: This refers to a term that has an opposed or substantively different meaning. See: This refers the reader to (a) a related term, (b) a term that is the expanded form of an abbreviation or acronym, or (c) a synonym or more preferred term. Synonym for: This indicates that the term has the same meaning as a preferred term, which is defined in its proper place in the glossary. Synonymous with: This is a reference from a defined term to all other terms that have the same meaning. Obsolete term for: This indicates that the term should not be used and refers the reader to the preferred term. This glossary includes terms and definitions from American National Standard Dictionary for Information Systems, ANSI X3.172-1990, copyright 1990 by the American National Standards Institute (ANSI). Copies may be purchased from the American National Standards Institute, 11 West 42nd Street, New York, New York 10036. Definitions are identified by an asterisk (*) that appears between the term and the beginning of the definition; a single definition taken from ANSI is identified by an asterisk after the item number for that definition. © Copyright IBM Corp. 2006. All rights reserved. 1 2 Introduction to the New Mainframe: z/OS Basics access. The ability to read, update, or otherwise use a resource. Access to protected resources is usually controlled by system software. A access authority. An authority that relates to abend. abnormal end. a request for a type of access to protected resources. In RACF®, the access authorities abend dump. A kind of dump produced when are NONE, READ, UPDATE, ALTER, and a program ends abnormally. EXECUTE. abnormal end. End of a task, a job, or a access control. In computer security, subsystem because of an error condition that ensuring that the resources of a computer cannot be resolved by recovery facilities while system can be accessed only by authorized the task is performed. See abnormal users in authorized ways. termination. access list. A list within a profile of all abnormal termination. (1) The end of authorized users and their access authorities. processing prior to scheduled termination. (2) A system failure or operator action that causes access method. A technique for moving data a job to end unsuccessfully. Synonymous with between main storage and I/O devices. abend, abnormal end. ACID properties. The properties of a ABR. area border node. transaction: atomicity, consistency, isolation, and durability. In CICS®, the ACID properties ACB. access control block. apply to a unit of work (UoW). accept. In SMP/E, to install SYSMODs in the ACK. acknowledgment field. distribution libraries. This is done with the ACCEPT command. Address Resolution Protocol (ARP). In the Internet suite of protocols, the protocol that ACCEPT command. The SMP/E command dynamically maps an IP address to an used to install SYSMODs in the distribution address used by a supporting metropolitan or libraries. local area network such as Ethernet or token-ring. accepted SYSMOD. A SYSMOD that has been successfully installed by the SMP/E address. The unique code assigned to each ACCEPT command. Accepted SYSMODs do device, workstation or system connected to a not have the ERROR flag set and are found as network. SYSMOD entries in the distribution zone. © Copyright IBM Corp. 2006. All rights reserved. 3 address space. A range of contiguous virtual Advanced Peer-to-Peer Networking® storage addresses that the system creates for (APPN). An extension to SNA featuring: (a) the user, batch job, or system task. In z/OS, an greater distributed network control that avoids address space can range up to 16 exabytes of critical hierarchical dependencies, thereby contiguous virtual storage addresses that the isolating the effects of single points of failure; system creates for the user. An address space (b) dynamic exchange of network topology contains user data and programs, as well as information to foster ease of connection, system data and programs, some of which are reconfiguration, and adaptive route selection; common to all address spaces. See virtual (c) dynamic definition of network resources; address space, data space. and (d) automated resource registration and directory lookup. APPN extends the LU 6.2 addressing mode (AMODE). A program peer orientation for end-user services to attribute that refers to the address length that network control and supports multiple LU is expected to be in effect when the program is types, including LU 2, LU 3, and LU 6.2. entered. In z/OS, addresses can be 24, 31, or 64 bits in length. Advanced Program-to-Program Communication (APPC). An implementation adjacent link station (ALS). In SNA, a link of the SNA LU 6.2 protocol that allows station directly connected to a given node by a interconnected systems to communicate and link connection over which network traffic can share the processing of programs. be carried. AID. attention identifier. adjacent node. (1) In SNA, a node connected to another node by at least one path that AIW. APPN Implementation Workshop. connects no other node. (2) In OSI, a node that is attached to the same subnetwork as the alert. To cause the user's terminal to give local node. An adjacent node can be either a some audible or visual indication that an error destination node or a relay node. or some other event has occurred. adjacent subarea. A subarea connected by alias. An alternate label; for example, a label one or more links to another subarea with no and one or more aliases may be used to refer intervening subareas. See subarea. to the same data element or point in a computer program. ADJSSCP. adjacent SSCP table. allocate. To assign a resource for use in administrator. A person responsible for performing a specific task. administrative tasks such as access authorization and content management. ALLOCATE command. In z/OS, the TSO/E Administrators can also grant levels of command that serves as the connection authority to users. between a file's logical name (the ddname) and the file's physical name (the data set name). alphanumeric character. A letter or a number. 4 Introduction to the New Mainframe: z/OS Basics American Standard Code for Information application. A program or set of programs Interchange (ASCII). A standard code used that performs a task; some examples are for information exchange among data payroll, inventory management, and word processing systems, data communication processing applications. systems, and associated equipment. ASCII uses a coded character set consisting of 7-bit application layer. In the Open Systems coded characters. See Extended Binary Interconnection (OSI) reference model, the Coded Decimal Interchange Code (EBCDIC). layer that provides means for application processes residing in open systems to AMODE. addressing mode. exchange information and that contains the application-oriented protocols by which these anonymous user. A portal user who has not processes communicate. logged in to the portal with a valid user ID and password. application program. A collection of software components used to perform specific types of ANR. automatic network routing. work on a computer, such as a program that does inventory control or payroll. ANSI. American National Standards Institute. application programming interface (API). A AOR. application-owning region. software interface that enables applications to communicate with each other. An API is the APAR. authorized program analysis report. set of programming language constructs or APAR fix. A temporary correction of a defect statements that can be coded in an application in an IBM system control program or licensed program to obtain the specific functions and program that affects a specific user. An APAR services provided by an underlying operating fix is usually replaced later by a permanent system or service program. correction called a PTF. APAR fixes are application-instance DVIPA. A dynamic VIPA identified to SMP/E by the ++APAR statement. activated by an application that explicitly APF. authorized program facility. issues a bind() function call to the IP address. APF-authorized. A type of system application-owning region (AOR). In a authorization using the authorized program CICSPlex® configuration, a CICS region facility (APF) that allows an installation to devoted to running applications. identify system or user programs that can use apply. In SMP/E, to install SYSMODs in the sensitive system functions. To maintain target libraries. This is done with the APPLY system security and integrity, a program must command. be authorized by the APF before it can access restricted functions, such as supervisor calls APPLY command. The SMP/E command (SVC) or SVC paths. used to install SYSMODs in the target libraries. API. application programming interface. APPN. Advanced Peer-to-Peer Network. APPC. advanced program-to-program communications. 5 APPN end node. A node that provides a ARM. automatic restart management. broad range of end-user services and supports sessions between its local control ARP. Address Resolution Protocol. point (CP) and the CP in an adjacent network node. It uses these sessions to dynamically ARPANET. A network established by the register its resources with the adjacent CP (its United States Department of Defense network node server), to send and receive Advanced Research Projects Agency (now the directory search requests, and to obtain Defense Advanced Research Projects management services. An APPN end node Agency). can also attach to other end nodes. See ASCII. American Standard Code for Advanced Peer-to-Peer Networking. Information Interchange.
Load more

Recommended publications
  • MVS Planning: Workload Management
    z/OS Version 2 Release 3 MVS Planning: Workload Management IBM SC34-2662-30 Note Before using this information and the product it supports, read the information in “Notices” on page 235. This edition applies to Version 2 Release 3 of z/OS (5650-ZOS) and to all subsequent releases and modifications until otherwise indicated in new editions. Last updated: 2019-06-24 © Copyright International Business Machines Corporation 1994, 2019. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Figures................................................................................................................. xi Tables..................................................................................................................xv About this information....................................................................................... xvii Who should use this information..............................................................................................................xvii Where to find more information............................................................................................................... xvii Other referenced documents.................................................................................................................. xviii Information updates on the web...............................................................................................................xix How to send your comments to IBM.....................................................................xxi
    [Show full text]
  • Z/OS ISPF Services Guide COMMAND NAME
    z/OS 2.4 ISPF Services Guide IBM SC19-3626-40 Note Before using this information and the product it supports, read the information in “Notices” on page 399. This edition applies to Version 2 Release 4 of z/OS (5650-ZOS) and to all subsequent releases and modifications until otherwise indicated in new editions. Last updated: 2021-06-22 © Copyright International Business Machines Corporation 1980, 2021. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Figures................................................................................................................ xv Tables................................................................................................................xvii Preface...............................................................................................................xix Who should use this document?............................................................................................................... xix What is in this document?......................................................................................................................... xix How to read the syntax diagrams..............................................................................................................xix z/OS information...............................................................................................xxiii How to send your comments to IBM...................................................................
    [Show full text]
  • OS/390 Introduction to ISPF
    z/OS Basic Skills Information Center: ISPF Course Module Module 1: Main Features of ISPF © Copyright IBM Corp., 2005. All rights reserved. z/OS Basic Skills Information Center: ISPF Course Module Introduction This module, Main Features of ISPF, introduces you to the z/OS Interactive System Productivity Facility, or ISPF, with special emphasis on the Program Development Facility, or PDF. Time to complete: 10 – 15 minutes © Copyright IBM Corp., 2005. All rights reserved. Page 2 of 15 z/OS Basic Skills Information Center: ISPF Course Module Main Features of ISPF - Objectives Upon completion of this module, you should be able to: • Describe the purpose of ISPF and its relationship to TSO • List the four major components of ISPF • Explain the function of each of the four components © Copyright IBM Corp., 2005. All rights reserved. Page 3 of 15 z/OS Basic Skills Information Center: ISPF Course Module Main Features of ISPF – Purpose of ISPF The Interactive System Productivity Facility, or ISPF, is a development tool set for the z/OS operating system. It has been used since 1975 to increase the productivity of the development of mainframe applications, because it provides an extensive set of programmer oriented facilities. © Copyright IBM Corp., 2005. All rights reserved. Page 4 of 15 z/OS Basic Skills Information Center: ISPF Course Module Main Features of ISPF – The Time Sharing Option/Extended (TSO/E) The Time Sharing Option/Extended, or TSO/E, is a base element of IBM's mainframe z/OS operating system. TSO/E allows you to communicate interactively with the MVS operating system by typing commands (one line at a time) on a computer terminal.
    [Show full text]
  • Task Scheduling Balancing User Experience and Resource Utilization on Cloud
    Rochester Institute of Technology RIT Scholar Works Theses 7-2019 Task Scheduling Balancing User Experience and Resource Utilization on Cloud Sultan Mira [email protected] Follow this and additional works at: https://scholarworks.rit.edu/theses Recommended Citation Mira, Sultan, "Task Scheduling Balancing User Experience and Resource Utilization on Cloud" (2019). Thesis. Rochester Institute of Technology. Accessed from This Thesis is brought to you for free and open access by RIT Scholar Works. It has been accepted for inclusion in Theses by an authorized administrator of RIT Scholar Works. For more information, please contact [email protected]. Task Scheduling Balancing User Experience and Resource Utilization on Cloud by Sultan Mira A Thesis Submitted in Partial Fulfillment of the Requirements for the Degree of Master of Science in Software Engineering Supervised by Dr. Yi Wang Department of Software Engineering B. Thomas Golisano College of Computing and Information Sciences Rochester Institute of Technology Rochester, New York July 2019 ii The thesis “Task Scheduling Balancing User Experience and Resource Utilization on Cloud” by Sultan Mira has been examined and approved by the following Examination Committee: Dr. Yi Wang Assistant Professor Thesis Committee Chair Dr. Pradeep Murukannaiah Assistant Professor Dr. Christian Newman Assistant Professor iii Dedication I dedicate this work to my family, loved ones, and everyone who has helped me get to where I am. iv Abstract Task Scheduling Balancing User Experience and Resource Utilization on Cloud Sultan Mira Supervising Professor: Dr. Yi Wang Cloud computing has been gaining undeniable popularity over the last few years. Among many techniques enabling cloud computing, task scheduling plays a critical role in both efficient resource utilization for cloud service providers and providing an excellent user ex- perience to the clients.
    [Show full text]
  • IBM System/360 Operating System Sequential Access Methods Program Logic Manual
    Y28-6604-1 Program Logic IBM System/360 Operating System Sequential Access Methods Program Number 3S0S-DM-50B This publication describes the internal logic of the routines of the queued sequen­ tial access method, the basic sequential access method, and the basic partitioned access method of IBM System/360 Operating System. Program Logic Manuals are intended for use by IBM customer engineers involved in program maintenance, and by system pro­ grammers involved in altering the program design. Program logic information is not necessary for program operation and use; therefore, distribution of this manual is limited to persons with program maintenance or modification responsibilities. Restricted Distribution PREFACE This publication describes the sequen­ • Buffer pool management routines that tial access method facilities in IBM Oper­ furnish buffer space in main storage. ating System/360. It describes routines in five categories: PREREQUISITE PUBLICATIONS • Queued sequential access method rou­ tines that cause storage and retrieval Knowledge of the information in the of data records arranged in sequential following publications is required for an order .• understanding of this publication: • Basic sequential access method routines IBM system/360 Operating System: Data that cause storage and retrieval of Management, Form C28-6537 data blocks arranged in sequential order. IB,M Systerol360 Operating System: Intro­ duction to Control Program Logic. Pro­ • Basic partitioned access method rou­ gram Logic Manual, Form Y28-6605 tines that cause storage and retrieval of data blocks in a member of a parti­ tioned data set, and construct entries and search for entries in the directory RECOMMENDED READING of a partitioned data set. The publication IBM System/360 Operating • Executors that operate with System: Control Program SerVices, Form input/output supp~rt routines.
    [Show full text]
  • Resource Access Control Facility (RACF) General User's Guide
    ----- --- SC28-1341-3 - -. Resource Access Control Facility -------_.----- - - --- (RACF) General User's Guide I Production of this Book This book was prepared and formatted using the BookMaster® document markup language. Fourth Edition (December, 1988) This is a major revision of, and obsoletes, SC28-1341- 3and Technical Newsletter SN28-l2l8. See the Summary of Changes following the Edition Notice for a summary of the changes made to this manual. Technical changes or additions to the text and illustrations are indicated by a vertical line to the left of the change. This edition applies to Version 1 Releases 8.1 and 8.2 of the program product RACF (Resource Access Control Facility) Program Number 5740-XXH, and to all subsequent versions until otherwise indicated in new editions or Technical Newsletters. Changes are made periodically to the information herein; before using this publication in connection with the operation of IBM systems, consult the latest IBM Systemj370 Bibliography, GC20-0001, for the editions that are applicable and current. References in this publication to IBM products or services do not imply that IBM· intends to make these available in all countries in which IBM operates. Any reference to an IBM product in this publication is not intended to state or imply that only IBM's product may be used. Any functionally equivalent product may be used instead. This statement does not expressly or implicitly waive any intellectual property right IBM may hold in any product mentioned herein. Publications are not stocked at the address given below. Requests for IBM publications should be made to your IBM representative or to the IBM branch office serving your locality.
    [Show full text]
  • PKZIP MVS User's Guide
    PKZIP for MVS MVS/ESA, OS/390, & z/OS User’s Guide PKMU-V5R5000 PKWARE, Inc. PKWARE, Inc. 9009 Springboro Pike Miamisburg, Ohio 45342 Sales: 937-847-2374 Support: 937-847-2687 Fax: 937-847-2375 Web Site: http://www.pkzip.com Sales - E-Mail: [email protected] Support - http://www.pkzip.com/support 5.5 Edition (2003) PKZIP for MVS™, PKZIP for OS/400™, PKZIP for VSE™, PKZIP for UNIX™, and PKZIP for Windows™ are just a few of the many members in the PKZIP® family. PKWARE, Inc. would like to thank all the individuals and companies -- including our customers, resellers, distributors, and technology partners -- who have helped make PKZIP® the industry standard for Trusted ZIP solutions. PKZIP® enables our customers to efficiently and securely transmit and store information across systems of all sizes, ranging from desktops to mainframes. This edition applies to the following PKWARE of Ohio, Inc. licensed program: PKZIP for MVS™ (Version 5, Release 5, 2003) PKZIP(R) is a registered trademark of PKWARE(R) Inc. Other product names mentioned in this manual may be a trademark or registered trademarks of their respective companies and are hereby acknowledged. Any reference to licensed programs or other material, belonging to any company, is not intended to state or imply that such programs or material are available or may be used. The copyright in this work is owned by PKWARE of Ohio, Inc., and the document is issued in confidence for the purpose only for which it is supplied. It must not be reproduced in whole or in part or used for tendering purposes except under an agreement or with the consent in writing of PKWARE of Ohio, Inc., and then only on condition that this notice is included in any such reproduction.
    [Show full text]
  • Opencobol Manual for Opencobol 2.0
    OpenCOBOL Manual for OpenCOBOL 2.0 Keisuke Nishida / Roger While Edition 2.0 Updated for OpenCOBOL 2.0 26 January 2012 OpenCOBOL is an open-source COBOL compiler, which translates COBOL programs to C code and compiles it using GCC or other C compiler system. This manual corresponds to OpenCOBOL 2.0. Copyright c 2002,2003,2004,2005,2006 Keisuke Nishida Copyright c 2007-2012 Roger While Permission is granted to make and distribute verbatim copies of this manual provided the copy- right notice and this permission notice are preserved on all copies. Permission is granted to copy and distribute modified versions of this manual under the condi- tions for verbatim copying, provided that the entire resulting derived work is distributed under the terms of a permission notice identical to this one. Permission is granted to copy and distribute translations of this manual into another language, under the above conditions for modified versions, except that this permission notice maybe stated in a translation approved by the Free Software Foundation. i Table of Contents 1 Getting Started :::::::::::::::::::::::::::::::::::::::::::::::: 1 1.1 Hello World!::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 1 2 Compile :::::::::::::::::::::::::::::::::::::::::::::::::::::::: 2 2.1 Compiler Options ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 2 2.1.1 Help Options ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 2 2.1.2 Built Target ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
    [Show full text]
  • CA MII Data Sharing for Z/OS CA MII Programming Guide
    CA MII Data Sharing for z/OS CA MII Programming Guide Release 12.0 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.
    [Show full text]
  • Syncsort for Z/VSE Programmer's Guide Release
    All rights reserved. This document contains proprietary and confidential material, and is only for use by licensees of the SyncSort for z/VSE proprietary software system. PROVEN performance SyncSort for z/ VSE Programmer's Guide Release 3. 7 SI-0328-G SyncSort is a registered trademark of Syncsort Incorporated 070809 © Syncsort Incorporated, 2009 All rights reserved. This document contains proprietary and confidential material, and is only for use by licensees of the SyncSort proprietary software system. This publication may not be reproduced in whole or in part, in any form, except with written permission from Syncsort Incorporated. SyncSort is a trademark of Syncsort Incorporated. All other company and product names used herein may be the trademarks of their respective companies. Table of Contents Summary of Changes . v Performance Improvements . v Data Utility Features. v Operating System . vi Messages. vi Chapter 1. Introduction . 1.1 An Introduction to SyncSort for z/VSE. 1.1 SyncSort’s Basic Functions . 1.1 SyncSort’s Data Utility and SortWriter Features . 1.2 Join Processing Sequence . 1.5 Sample SortWriter Report. 1.6 SyncSort’s Operational Features. 1.7 Structure of the Programmer’s Guide. 1.7 Related Reading. 1.9 Chapter 2. SyncSort Control Statements . 2.1 Control Statement Summary Chart . 2.3 Data Utility Processing Sequence. 2.17 Maximum Record Length Allowed . 2.23 Control Statement Examples . 2.25 Rules for Control Statements . 2.25 ALTSEQ Control Statement . 2.30 ANALYZE Control Statement. 2.32 DUPKEYS Control Statement . 2.33 Table of Contents i END Control Statement. 2.38 INCLUDE/OMIT Control Statement .
    [Show full text]
  • Introduction to the New Mainframe: Z/OS Basics
    Front cover Introduction to the New Mainframe: z/OS Basics An introduction to mainframe computing on the IBM zSeries platform z/OS concepts and facilities for students and beginners zSeries hardware and peripheral devices Mike Ebbers Wayne O’Brien Bill Ogden ibm.com/ International Technical Support Organization z/OS Basics March 2005 SG24-6366-00 Note: Before using this information and the product it supports, read the information in “Notices” on page -1. First Edition (March 2005) © Copyright International Business Machines Corporation 2005. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Preface . xvii How this text is organized . xvii How each chapter is organized . xviii Acknowledgements . xix Comments welcome. xxi Part 1. Introduction to z/OS and the mainframe environment Chapter 1. Introduction to the new mainframe . 1-1 1.1 The new mainframe. 1-2 1.2 Evolving architecture . 1-2 1.3 Mainframes in our midst . 1-4 1.4 What is a mainframe? . 1-5 1.5 Who uses mainframe computers?. 1-7 1.6 Factors contributing to mainframe use . 1-8 1.6.1 Reliability, availability, and serviceability. 1-9 1.6.2 Security . 1-10 1.6.3 Scalability . 1-10 1.6.4 Continuing compatibility . 1-11 1.7 Typical mainframe workloads . 1-11 1.7.1 Batch processing. 1-12 1.7.2 Online transactional processing . 1-15 1.8 Roles in the mainframe world . 1-17 1.8.1 Who is the system programmer? . 1-19 1.8.2 Who is the system administrator? .
    [Show full text]
  • Static Typing Where Possible, Dynamic Typing When Needed: the End of the Cold War Between Programming Languages
    Intended for submission to the Revival of Dynamic Languages Static Typing Where Possible, Dynamic Typing When Needed: The End of the Cold War Between Programming Languages Erik Meijer and Peter Drayton Microsoft Corporation Abstract Advocates of dynamically typed languages argue that static typing is too rigid, and that the softness of dynamically lan- This paper argues that we should seek the golden middle way guages makes them ideally suited for prototyping systems with between dynamically and statically typed languages. changing or unknown requirements, or that interact with other systems that change unpredictably (data and application in- tegration). Of course, dynamically typed languages are indis- 1 Introduction pensable for dealing with truly dynamic program behavior such as method interception, dynamic loading, mobile code, runtime <NOTE to="reader"> Please note that this paper is still very reflection, etc. much work in progress and as such the presentation is unpol- In the mother of all papers on scripting [16], John Ousterhout ished and possibly incoherent. Obviously many citations to argues that statically typed systems programming languages related and relevant work are missing. We did however do our make code less reusable, more verbose, not more safe, and less best to make it provocative. </NOTE> expressive than dynamically typed scripting languages. This Advocates of static typing argue that the advantages of static argument is parroted literally by many proponents of dynami- typing include earlier detection of programming mistakes (e.g. cally typed scripting languages. We argue that this is a fallacy preventing adding an integer to a boolean), better documenta- and falls into the same category as arguing that the essence of tion in the form of type signatures (e.g.
    [Show full text]