DOCSLIB.ORG

Cobol 1 Cobol

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Cobol 1 Cobol COBOL 1 COBOL COBOL Paradigm procedural, object-oriented Appeared in 1959 Designed by Grace Hopper, William Selden, Gertrude Tierney, Howard Bromberg, Howard Discount, Vernon Reeves, Jean E. Sammet Stable release COBOL 2002 (2002) Typing discipline strong, static Major OpenCOBOL, Micro Focus International implementations Dialects HP3000 COBOL/II, COBOL/2, IBM OS/VS COBOL, IBM COBOL/II, IBM COBOL SAA, IBM Enterprise COBOL, IBM COBOL/400, IBM ILE COBOL, Unix COBOL X/Open, Micro Focus COBOL, Microsoft COBOL, Ryan McFarland RM/COBOL, Ryan McFarland RM/COBOL-85, DOSVS COBOL, UNIVAC COBOL, Realia COBOL, Fujitsu COBOL, ICL COBOL, ACUCOBOL-GT, COBOL-IT, DEC COBOL-10, DEC VAX COBOL, Wang VS COBOL, Visual COBOL, Tandem (NonStop) COBOL85, Tandem (NonStop) SCOBOL (a COBOL74 variant for creating screens on text-based terminals) Influenced by FLOW-MATIC, COMTRAN, FACT Influenced PL/I, CobolScript, ABAP COBOL at Wikibooks COBOL (pronounced /ˈkoʊbɒl/) is one of the oldest programming languages. Its name is an acronym for COmmon Business-Oriented Language, defining its primary domain in business, finance, and administrative systems for companies and governments. The COBOL 2002 standard includes support for object-oriented programming and other modern language features.[1] History and specification The COBOL specification was created by a committee of researchers from private industry, universities, and government during the second half of 1959. The specifications were to a great extent inspired by the FLOW-MATIC language invented by Grace Hopper - commonly referred to as "the mother of the COBOL language." The IBM COMTRAN language invented by Bob Bemer was also drawn upon, but the FACT language specification from Honeywell was not distributed to committee members until late in the process and had relatively little impact. FLOW-MATIC's status as the only language of the bunch to have actually been implemented made it particularly attractive to the committee.[2] The scene was set on April 8, 1959 at a meeting of computer manufacturers, users, and university people at the University of Pennsylvania Computing Center. The United States Department of Defense subsequently agreed to sponsor and oversee the next activities. A meeting chaired by Charles A. Phillips was held at the Pentagon on May 28 and 29 of 1959 (exactly one year after the Zürich ALGOL 58 meeting); there it was decided to set up three committees: short, intermediate and long range (the last one was never actually formed). It was the Short Range Committee, chaired by Joseph Wegstein of the US National Bureau of Standards, that during the following months created a description of the first version of COBOL.[3] The committee was formed to recommend a short range approach to a common business language. The committee was made up of members representing six computer COBOL 2 manufacturers and three government agencies. The six computer manufacturers were Burroughs Corporation, IBM, Minneapolis-Honeywell (Honeywell Labs), RCA, Sperry Rand, and Sylvania Electric Products. The three government agencies were the US Air Force, the David Taylor Model Basin, and the National Bureau of Standards (now National Institute of Standards and Technology). The intermediate-range committee was formed but never became operational. In the end a sub-committee of the Short Range Committee developed the specifications of the COBOL language. This sub-committee was made up of six individuals: • William Selden and Gertrude Tierney of IBM • Howard Bromberg and Howard Discount of RCA • Vernon Reeves and Jean E. Sammet of Sylvania Electric Products[4] The decision to use the name "COBOL" was made at a meeting of the committee held on 18 September 1959. The subcommittee completed the specifications for COBOL in December 1959. The first compilers for COBOL were subsequently implemented during the year 1960 and on 6 and 7 December essentially the same COBOL program was run on two different makes of computers, an RCA computer and a Remington-Rand Univac computer, demonstrating that compatibility could be achieved. ANS COBOL 1968 After 1959 COBOL underwent several modifications and improvements. In an attempt to overcome the problem of incompatibility between different versions of COBOL, the American National Standards Institute (ANSI) developed a standard form of the language in 1968. This version was known as American National Standard (ANS) COBOL. COBOL 1974 In 1974, ANSI published a revised version of (ANS) COBOL, containing a number of features that were not in the 1968 version. COBOL 1985 In 1985, ANSI published still another revised version that had new features not in the 1974 standard, most notably structured language constructs ("scope terminators"), including END-IF, END-PERFORM, END-READ, etc. COBOL 2002 and object-oriented COBOL The language continues to evolve today. In the early 1990s it was decided to add object-orientation in the next full revision of COBOL. The initial estimate was to have this revision completed by 1997 and an ISO CD (Committee Draft) was available by 1997. Some implementers (including Micro Focus, Fujitsu, Veryant, and IBM) introduced object-oriented syntax based on the 1997 or other drafts of the full revision. The final approved ISO Standard (adopted as an ANSI standard by INCITS) was approved and made available in 2002. Like the C++ and Java programming languages, object-oriented COBOL compilers are available even as the language moves toward standardization. Fujitsu and Micro Focus currently support object-oriented COBOL compilers targeting the .NET framework.[5] The 2002 (4th revision) of COBOL included many other features beyond object-orientation. These included (but are not limited to): • National Language support (including but not limited to Unicode support) • Locale-based processing • User-defined functions • CALL (and function) prototypes (for compile-time parameter checking) • Pointers and syntax for getting and freeing storage • Calling conventions to and from non-COBOL languages such as C COBOL 3 • Support for execution within framework environments such as Microsoft's .NET and Java (including COBOL instantiated as Enterprise JavaBeans) • Bit and Boolean support • “True” binary support (up until this enhancement, binary items were truncated based on the (base-10) specification within the Data Division) • Floating-point support • Standard (or portable) arithmetic results • XML generation and parsing History of COBOL standards The specifications approved by the full Short Range Committee were approved by the Executive Committee on January 3, 1960, and sent to the government printing office, which edited and printed these specifications as Cobol 60. The American National Standards Institute (ANSI) produced several revisions of the COBOL standard, including: • COBOL-68 • COBOL-74 • COBOL-85 • Intrinsic Functions Amendment - 1989 • Corrections Amendment - 1991 After the Amendments to the 1985 ANSI Standard (which were adopted by ISO), primary development and ownership was taken over by ISO. The following editions and TRs (Technical Reports) have been issued by ISO (and adopted as ANSI) Standards: • COBOL 2002 • Finalizer Technical Report - 2003 • Native XML syntax Technical Report - 2006 • Object Oriented Collection Class Libraries - pending final approval... From 2002, the ISO standard is also available to the public coded as ISO/IEC 1989. Work is progressing on the next full revision of the COBOL Standard. It is expected to be approved and available in the early 2010s. For information on this revision, to see the latest draft of this revision, or to see what other works is happening with the COBOL Standard, see the COBOL Standards Website [6]. Legacy COBOL programs are in use globally in governmental and military agencies and in commercial enterprises, and are running on operating systems such as IBM's z/OS, the POSIX families (Unix/Linux etc.), and Microsoft's Windows as well as ICL's VME operating system and Unisys' OS 2200. In 1997, the Gartner Group reported that 80% of the world's business ran on COBOL with over 200 billion lines of code in existence and with an estimated 5 billion lines of new code annually.[7] Near the end of the twentieth century the year 2000 problem was the focus of significant COBOL programming effort, sometimes by the same programmers who had designed the systems decades before. The particular level of effort required for COBOL code has been attributed both to the large amount of business-oriented COBOL, as COBOL is by design a business language and business applications use dates heavily, and to constructs of the COBOL language such as the PICTURE clause, which can be used to define fixed-length numeric fields, including two-digit fields for years. COBOL 4 References [1] Oliveira, Rui (2006). The Power of Cobol. City: BookSurge Publishing. ISBN 0620346523. [2] Sammet, Jean (1978). " The Early History of COBOL (http:/ / portal. acm. org/ citation. cfm?id=1198367)". ACM SIGPLAN Notices (Association for Computing Machinery, Inc.) 13 (8): 121–161. [3] Garfunkel, Jerome (1987). The Cobol 85 Example Book. New York: Wiley. ISBN 0471804614. [4] Wexelblat, Richard (1981). History of Programming Languages. Boston: Academic Press. ISBN 0127450408. [5] NetCOBOL for .NET supports COBOL migration and software development in the .NET environment (http:/ / www. adtools. com/ products/ windows/ netcobol. html) [6] http:/ / www. cobolstandards. com [7] "What Professionals think of the Future of COBOL?" (http:/ / www. cobolportal. com/ developer/ future. asp?bhcp=1).
Load more

Recommended publications
  • ISO/IEC JTC 1/SC 22/WG4 N 0163 Information Technology
    ISO/IEC JTC 1/SC 22/WG4 N 0163 Date: 2002-05-21 Reference number of document: WDTR 19755 Version 1.1 Committee identification: ISO/IEC JTC 1/SC 22 /WG 4 Secretariat: ANSI Information Technology — Programming languages, their environments and system software interfaces — Object finalization for programming language COBOL Warning This document is an ISO/IEC proposed draft Technical Report. It is not an ISO/IEC International Technical Report. It is distributed for review and comment. It is subject to change without notice and shall not be referred to as an International Technical Report or International Standard. Recipients of this document are invited to submit, with their comments, notification of any relevant patent rights of which they are aware and to provide supporting documentation. Document type: Technical report Document subtype: n/a Document stage: (20) Preparation Document language: E ISO/WDTR 19755 Copyright notice This ISO/IEC document is a working draft and is copyright-protected by ISO/IEC. Requests for permission to reproduce this document for the purpose of selling it should be addressed as shown below or to ISO’s member body in the country of the requester: Copyright manager ISO Central Secretariat 1 rue de Varembé 1211 Geneva 20 Switzerland tel: +41 22 749 0111 fax: +41 22 734 0179 email: [email protected] Reproduction for sales purposes may be subject to royalty payments or a licensing agreement. Violators may be prosecuted. ii © ISO/IEC 2002 – All rights reserved ISO/IEC WDTR 19755 Acknowledgement notice COBOL originated in 1959 as a common business oriented language developed by the Conference on Data Systems Languages (CODASYL).
    [Show full text]
  • SAP Backup Using Tivoli Storage Manager
    Front cover SAP Backup using Tivoli Storage Manager Covers and compares data management techniques for SAP Presents a sample implementation of DB2 and Oracle databases Explains LAN-free and FlashCopy techniques Budi Darmawan Miroslav Dvorak Dhruv Harnal Gerson Makino Markus Molnar Rennad Murugan Marcos Silva ibm.com/redbooks International Technical Support Organization SAP Backup using Tivoli Storage Manager June 2009 SG24-7686-00 Note: Before using this information and the product it supports, read the information in “Notices” on page xi. First Edition (June 2009) This edition applies to Version 5, Release 5, Modification 0 of Tivoli Storage Manager and its related components: Tivoli Storage Manager Server, 5608-ISM Tivoli Storage Manager for Enterprise Resource Planning, 5608-APR Tivoli Storage Manager for Databases, 5608-APD Tivoli Stroage Manager for Advanced Copy Services, 5608-ACS Tivoli Storage Manager for SAN, 5608-SAN © Copyright International Business Machines Corporation 2009. 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 Notices . xi Trademarks . xii Preface . xv The team that wrote this book . xv Become a published author . xvii Comments welcome. xviii Part 1. Concepts . 1 Chapter 1. SAP data management. 3 1.1 SAP . 4 1.2 Data management. 4 1.3 Book structure . 5 Chapter 2. SAP overview . 7 2.1 SAP product history. 8 2.2 SAP solutions and products . 11 2.2.1 Enterprise solutions. 11 2.2.2 Business solutions . 13 2.2.3 SAP solutions for small businesses and mid-size companies . 13 2.3 SAP NetWeaver overview .
    [Show full text]
  • Stable/Build) • --Port PORT - Set the PORT Number (Default: 8000)
    Pyodide Release 0.18.1 unknown Sep 16, 2021 CONTENTS 1 Using Pyodide 3 1.1 Getting started..............................................3 1.2 Downloading and deploying Pyodide..................................6 1.3 Using Pyodide..............................................7 1.4 Loading packages............................................ 12 1.5 Type translations............................................. 14 1.6 Pyodide Python compatibility...................................... 25 1.7 API Reference.............................................. 26 1.8 Frequently Asked Questions....................................... 50 2 Development 55 2.1 Building from sources.......................................... 55 2.2 Creating a Pyodide package....................................... 57 2.3 How to Contribute............................................ 64 2.4 Testing and benchmarking........................................ 74 2.5 Interactive Debugging.......................................... 76 3 Project 79 3.1 About Pyodide.............................................. 79 3.2 Roadmap................................................. 80 3.3 Code of Conduct............................................. 82 3.4 Governance and Decision-making.................................... 83 3.5 Change Log............................................... 85 3.6 Related Projects............................................. 95 4 Indices and tables 97 Python Module Index 99 Index 101 i ii Pyodide, Release 0.18.1 Python with the scientific stack, compiled to WebAssembly.
    [Show full text]
  • PHP Programming Cookbook I
    PHP Programming Cookbook i PHP Programming Cookbook PHP Programming Cookbook ii Contents 1 PHP Tutorial for Beginners 1 1.1 Introduction......................................................1 1.1.1 Where is PHP used?.............................................1 1.1.2 Why PHP?..................................................2 1.2 XAMPP Setup....................................................3 1.3 PHP Language Basics.................................................5 1.3.1 Escaping to PHP...............................................5 1.3.2 Commenting PHP..............................................5 1.3.3 Hello World..................................................6 1.3.4 Variables in PHP...............................................6 1.3.5 Conditional Statements in PHP........................................7 1.3.6 Loops in PHP.................................................8 1.4 PHP Arrays...................................................... 10 1.5 PHP Functions.................................................... 12 1.6 Connecting to a Database............................................... 14 1.6.1 Connecting to MySQL Databases...................................... 14 1.6.2 Connecting to MySQLi Databases (Procedurial).............................. 14 1.6.3 Connecting to MySQLi databases (Object-Oriented)............................ 15 1.6.4 Connecting to PDO Databases........................................ 15 1.7 PHP Form Handling................................................. 15 1.8 PHP Include & Require Statements.........................................
    [Show full text]
  • IBM Db2 for Linux, UNIX, and Windows Database: IBM Db2 for Linux, UNIX, and Windows
    Installation Guide | PUBLIC Software Provisioning Manager 1.0 SP 32 Document Version: 3.5 – 2021-06-21 Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.0 to 7.03 on UNIX: IBM Db2 for Linux, UNIX, and Windows Database: IBM Db2 for Linux, UNIX, and Windows company. All rights reserved. All rights company. Operating System: UNIX and Linux affiliate THE BEST RUN 2021 SAP SE or an SAP SE or an SAP SAP 2021 © Content 1 About this Document........................................................12 1.1 SAP Products Based on SAP NetWeaver 7.0 to 7.0 EHP3 Supported for Installation Using Software Provisioning Manager 1.0 .......................................................13 1.2 Naming Conventions..........................................................14 1.3 New Features...............................................................15 1.4 Constraints................................................................20 1.5 Before You Start.............................................................20 1.6 SAP Notes for the Installation....................................................21 2 Installation Options Covered by this Guide........................................23 2.1 Central System..............................................................23 2.2 Distributed System...........................................................24 2.3 High-Availability System.......................................................25 2.4 ASCS Instance with Integrated SAP Web Dispatcher ...................................26
    [Show full text]
  • SAP Overview
    SAP Overview What is SAP? SAP (Systems, Applications, Products in Data Processing), is headquartered in Walldorf, Germany. They provide business software designed to help companies execute and optimize business and IT strategies. SAP defines business software as comprising enterprise resource planning (ERP) and related applications such as supply chain management (SCM), customer relationship management (CRM), product life‐cycle management, and supplier relationship management (SRM).1 SAP currently has: • More than 51,000 employees in over 50 countries developing, marketing, and selling applications and services • 82,000 customers of all sizes across 25 industries and in over 120 countries • Listings on the Frankfurt and New York stock exchanges SAP operates in three geographic regions: EMEA (representing Europe, Middle East, and Africa), Americas, and Asia Pacific Japan (APJ, representing Japan, Australia, and parts of Asia). 2 History of SAP In 1972, SAP was founded by 5 former IBM employees in Mannheim, Germany with the vision to “to develop standard application software for real‐time business processing.” After the first year, they created the first financial accounting software application, which came to be known as the "R/1 system." "R" stands for real‐time data processing. By the end of the 1970s, R/1 evolved into SAP R/2. The programming language ABAP (Advanced Business Application Programming) was also a derivative of R/2, originally serving as the report language for the system.3 In the 1980s, SAP R/2 was updated to handle different languages and currencies‐‐subsequently, this lead to SAP’s international expansion into Austria, Denmark, Sweden, Italy, and the United States.
    [Show full text]
  • Object-Oriented Programming Basics with Java
    Object-Oriented Programming Object-Oriented Programming Basics With Java In his keynote address to the 11th World Computer Congress in 1989, renowned computer scientist Donald Knuth said that one of the most important lessons he had learned from his years of experience is that software is hard to write! Computer scientists have struggled for decades to design new languages and techniques for writing software. Unfortunately, experience has shown that writing large systems is virtually impossible. Small programs seem to be no problem, but scaling to large systems with large programming teams can result in $100M projects that never work and are thrown out. The only solution seems to lie in writing small software units that communicate via well-defined interfaces and protocols like computer chips. The units must be small enough that one developer can understand them entirely and, perhaps most importantly, the units must be protected from interference by other units so that programmers can code the units in isolation. The object-oriented paradigm fits these guidelines as designers represent complete concepts or real world entities as objects with approved interfaces for use by other objects. Like the outer membrane of a biological cell, the interface hides the internal implementation of the object, thus, isolating the code from interference by other objects. For many tasks, object-oriented programming has proven to be a very successful paradigm. Interestingly, the first object-oriented language (called Simula, which had even more features than C++) was designed in the 1960's, but object-oriented programming has only come into fashion in the 1990's.
    [Show full text]
  • Visual Smalltalk Enterprise ™ ™
    Visual Smalltalk Enterprise ™ ™ Language Reference P46-0201-00 Copyright © 1999–2000 Cincom Systems, Inc. All rights reserved. Copyright © 1999–2000 Seagull Systems, Inc. All rights reserved. This product contains copyrighted third-party software. Part Number: P46-0201-00 Software Release 3.2 This document is subject to change without notice. RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013. Trademark acknowledgments: CINCOM, CINCOM SYSTEMS, and the Cincom logo are registered trademarks of Cincom Systems, Inc. Visual Smalltalk is a trademark of Cincom Systems, Inc., its subsidiaries, or successors and are registered in the United States and other countries. Microsoft Windows is a registered trademark of Microsoft, Inc. Win32 is a trademark of Microsoft, Inc. OS/2 is a registered trademark of IBM Corporation. Other product names mentioned herein are used for identification purposes only, and may be trademarks of their respective companies. The following copyright notices apply to software that accompanies this documentation: Visual Smalltalk is furnished under a license and may not be used, copied, disclosed, and/or distributed except in accordance with the terms of said license. No class names, hierarchies, or protocols may be copied for implementation in other systems. This manual set and online system documentation copyright © 1999–2000 by Cincom Systems, Inc. All rights reserved. No part of it may be copied, photocopied, reproduced, translated, or reduced to any electronic medium or machine-readable form without prior written consent from Cincom.
    [Show full text]
  • 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.
    [Show full text]
  • Oral History of Captain Grace Hopper
    Oral History of Captain Grace Hopper Interviewed by: Angeline Pantages Recorded: December, 1980 Naval Data Automation Command, Maryland CHM Reference number: X5142.2009 © 1980 Computer History Museum Table of Contents BACKGROUND HISTORY ...........................................................................................................3 1943-1949: MARK I, II, AND III COMPUTERS AT HARVARD....................................................6 1949-1964: ECKERT AND MAUCHLY, UNIVAC, AND THE ONE-PASS COMPILER ................7 The Need for User-Friendly Languages ..................................................................................10 DEMANDS FOR THE FUTURE..................................................................................................12 Application Processors, Database Machines, Distributed Processing ....................................12 Demand for Programmers and System Analysts ....................................................................14 The Value and Cost of Information..........................................................................................14 The Navy’s Dilemma: Micros and Software Creation..............................................................15 The Murray Siblings: Brilliant Communicators.........................................................................18 Common Sense and Distributed Computing ...........................................................................19 BACK TO 1943-1949: HOWARD AIKEN....................................................................................21
    [Show full text]
  • Unisys Clearpath MCP & OS 2200 Mainframes to the Google Cloud Platform
    WHITE PAPER Unisys ClearPath MCP & OS 2200 Mainframes to the Google Cloud Platform Reference Architecture Guide Astadia Mainframe-to-Cloud Modernization Series Abstract In businesses today, across all market segments, cloud computing has become the focus of current and future In this document, we will explore: technology needs for the enterprise. The cloud offers compelling • Why modernize a Unisys mainframe economics, the latest technologies and platforms, and the agility • The challenges associated with Unisys to adapt your information systems quickly and efficiently. mainframe modernization However, many large organizations are burdened by much older, previous generation platforms, typically in the form of a Unisys • An overview of the Unisys mainframe mainframe computing environment. • The Unisys mainframe to Google Cloud Platform Reference Architecture Although old and very expensive to maintain, the Unisys • An overview of Google Cloud Platform services mainframe platform continues to run many of the most important information systems of an organization. The purpose • A look at the Astadia Success Methodology of this reference architecture is to assist business and IT This document is part of the Astadia Mainframe professionals as they prepare plans and project teams to start to Cloud Modernization Series that leverages the process of moving Unisys mainframe-based application Astadia’s 25+ years of mainframe platform portfolios to the Google Cloud Platform (GCP). We will also modernization expertise. share various techniques and methodologies that may be used in forming a complete and effective Legacy Modernization plan. © 2020 Astadia. Inc. - All rights reserved. 75 State Street, Suite 100 Boston, MA 02109 All other copyrights and trademarks the property of their respective owners.
    [Show full text]
  • The Future of Business Using Enterprise Server
    Market Review Market Review Paper by Bloor Author David Norfolk Publish date June 2021 The Future of Business …using Enterprise Server 3.0 Services A company has to stay“ in business while modernising its systems and any modernisation must have a clearly documented business case and properly managed risk. What this means is that migrating a working system to a new platform may not be a good use of resources, especially as alternative modernisation options (such as the provision of cloud APIs or Application Programming Interfaces) are available. ” Executive summary he Future of Business will Well, the nub of the business issue we be largely built on the past, spotlight here is that migration to Cloud T for existing companies. is often recommended simplistically as Modernisation of what you have already, a platform for future business, almost as presumably “fit for current purpose” (or you a fashion option, with implied promises wouldn’t be in business) avoids waste and of ultimate agility, elastic capabilities mitigates certain classes of risk (although, without limits and low cost; but the if not done properly, it can add new risks). actuality is often different – and never Modernisation, of course, implies fit for quite being able to complete a migration evolution and change – once modernised, off Enterprise Server 3.0, because the you will be making further changes to business realities won’t let you, is accommodate new business. probably the most expensive scenario Modernisation of what For big enterprises, the world still runs of all. Cloud provides a wide choice of you have already,“ on very large, very resilient, servers – often platforms, some with innovative and presumably “fit for current referred to as “mainframes”, although attractive characteristics, but three truths Bloor prefers the term Enterprise Server remain important: purpose” (or you wouldn’t be in business) avoids 3.0.
    [Show full text]