DOCSLIB.ORG

VSE to OS/390 Migration Workbook

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
VSE to OS/390 Migration Workbook IBML VSE to OS/390 Migration Workbook Cliff Bays ** Dave Greenough ** John Hutchinson Dan Janda ** Kevin Jones ** Gilbert Saint-flour International Technical Support Organization http://www.redbooks.ibm.com This book was printed at 240 dpi (dots per inch). The final production redbook with the RED cover will be printed at 1200 dpi and will provide superior graphics resolution. Please see “How to Get ITSO Redbooks” at the back of this book for ordering instructions. SG24-2043-00 IBML International Technical Support Organization SG24-2043-00 VSE to OS/390 Migration Workbook October 1998 Take Note! Before using this information and the product it supports, be sure to read the general information in Appendix D, “Special Notices” on page 553. First Edition (October 1998) This edition applies to Version 2 Release 3 of IBM Virtual Storage Extended/Enterprise Systems Architecture (VSE/ESA), Program Number 5690-VSE, and to all subsequent releases and modifications until otherwise indicated in new editions. It also applies to Version 2 Release 4 of OS/390 (5647-A01) and to all subsequent releases and modifications until otherwise indicated in new editions. Comments may be addressed to: IBM Corporation, International Technical Support Organization Dept. HYJ Mail Station P099 522 South Road Poughkeepsie, New York 12601-5400 When you send information to IBM, you grant IBM a non-exclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. Copyright International Business Machines Corporation 1998. All rights reserved. Note to U.S. Government Users — Documentation related to restricted rights — Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp. Contents Figures . xvii Tables . xix Preface . xxi The Team That Wrote This Redbook ........................ xxi Redbook Builders and Key Contributors .................... xxi Authors and Significant Contributors ...................... xxii Comments Welcome . xxii Part 1. Planning the Migration - An Introduction ......................... 1 Chapter 1. Why Customers Migrate ......................... 3 1.1 A Synopsis of This Book ............................. 3 1.2 Traditional Reasons for Migrating ........................ 4 1.2.1 Business Consolidation . 4 1.2.2 Mergers/Acquisitions . 5 1.2.3 Capacity Constraints . 5 1.2.4 Image . 9 1.3 Functional Reasons for Migrating to OS/390 .................. 10 1.3.1 Applications Availability . 10 1.3.2 Systems Management . 10 1.3.3 Connectivity . 11 1.3.4 Systems Availability . 11 1.3.5 Staff Availability . 12 Chapter 2. Sizing the Effort .............................. 13 2.1 Introduction to Sizing ............................... 13 2.1.1 Defining the Migration Project Objectives ................. 13 2.1.2 Areas of VSE and OS/390 Differences ................... 14 2.1.3 Comparison of Basic VSE Functions & Components to OS/390 .... 16 2.2 OS/390 Components/Products/Subsystems . 18 2.2.1 The OS/390 Operating Environment .................... 19 2.2.2 Subsystem Level Comparison/Affinity ................... 24 2.3 What Changes Between VSE and OS/390? ................... 24 2.3.1 Philosophical Changes . 24 2.4 Who is Affected by This Migration? ....................... 26 2.4.1 Job Roles and Normal Activities ...................... 26 2.5 Approaches to Migration ............................. 27 2.5.1 Disclaimer . 27 2.5.2 OS/390 Conversion and Production Implementation Strategies .... 27 2.5.3 VM/ESA Guest Support in Your VSE to OS/390 Migration ....... 29 2.5.4 Staffing Strategies . 29 2.5.5 Conversion Tools . 30 2.6 Educational Requirements . 31 2.6.1 Introduction . 31 2.7 Scope of Work and Challenges .......................... 32 2.7.1 Application Inventory . 32 2.7.2 Program Conversion . 33 2.7.3 JCL Conversion . 33 2.7.4 File Migration . 35 Copyright IBM Corp. 1998 iii 2.7.5 Project Management . 37 2.7.6 Automated Operations . 37 2.8 Cost Considerations . 38 2.9 OS/390 Documentation Resources ....................... 39 2.9.1 Introduction References . 39 2.9.2 Key Documents and Other References .................. 40 2.9.3 Web URL . 40 Chapter 3. Developing the Plan ............................ 41 3.1 Overview . 41 3.1.1 References . 41 3.1.2 Recommendations . 41 3.2 Plan Components . 45 3.2.1 Approach . 45 3.2.2 Team . 45 3.2.3 Tasks . 47 3.2.4 Milestone Events . 48 3.2.5 Education . 49 3.3 Progressive versus Mass Conversion ...................... 49 3.3.1 Approach Differences . 49 3.3.2 Historical Perspective . 50 3.3.3 Shared Application Files and Databases ................. 50 3.3.4 Shared Application Code .......................... 50 3.3.5 Operations Support Staffing ......................... 50 3.3.6 Automated Operations Tools ........................ 50 3.3.7 Standardized Conversion Deliverables and Automation ........ 51 3.3.8 Risk Management . 51 3.3.9 Complexity of Implementation ....................... 51 3.4 Plan Examples . 53 3.4.1 Project Schedule . 54 3.4.2 Project Plan Example ............................. 56 Part 2. Converting the VSE Operating System to the OS/390 Operating System .. 67 Chapter 4. Job Control Language (JCL) Differences and Considerations ... 69 4.1 The Philosophy of JCL in System/390 ...................... 69 4.1.1 VSE/ESA′s Job Control Language Philosophy .............. 70 4.1.2 OS/390′s Job Control Philosophy ...................... 70 4.2 High Level Similarities ............................... 72 4.2.1 JCL Statement and Job Layout ....................... 72 4.2.2 Spooling . 73 4.3 JCL Differences Between VSE and MVS .................... 73 4.3.1 Job Input . 73 4.3.2 JCL Expansion . 76 4.3.3 Operator Flexibility and Intervention .................... 76 4.3.4 Allocation of Resources ........................... 78 4.3.5 Hidden JCL . 78 4.3.6 Device Address Specifications ....................... 80 4.3.7 Catalogs . 81 4.3.8 Partition Dependent Codes in JCL ..................... 81 4.3.9 Communication Region - DATE and UPSI ................. 81 4.3.10 VSE Job Control Statements ........................ 82 4.3.11 MVS Job Control Statements ....................... 84 4.3.12 Comparison of VSE and MVS JCL - A Summary ............ 86 iv VSE to OS/390 Migration Workbook 4.3.13 Summary of MVS JCL Statements .................... 88 4.4 JECL . 89 4.4.2 Comparison of POWER and JES2 JECL - A Summary ......... 89 4.4.3 Summary of JES2 JECL - A Table ..................... 90 4.5 VSE and MVS JCL Comparison Example .................... 91 4.5.1 Sample VSE JCL ................................ 92 4.5.2 Sample MVS JCL ............................... 93 4.5.3 Sample VSE plus Carry-Over ........................ 94 Chapter 5. Disk and Tape Storage Considerations ................ 97 5.1 Access Method Similarities and Differences .................. 97 5.1.1 Access Methods . 97 5.1.2 Operating System Implementations .................... 98 5.1.3 Miscellaneous Functions . 99 5.2 Data Set Naming Considerations ........................ 99 5.2.1 VSE Considerations . 99 5.2.2 OS/390 Considerations . 99 5.3 Storage and Space Management ....................... 100 5.3.1 VSE Considerations . 100 5.3.2 OS/390 Considerations . 100 5.3.3 System Managed Storage ......................... 100 5.3.4 Implementing DFSMS . 102 5.4 Tape Similarities and Differences ....................... 103 5.4.1 Volume Interchangeability . 103 5.4.2 Standard Labels . 103 5.4.3 No Labels . 105 5.4.4 Nonstandard Labels . 106 5.4.5 Bypass Label Processing Facility in OS/390 .............. 106 5.5 DASD Similarities and Differences ...................... 108 5.5.1 Volume Interchangeability . 108 5.5.2 DASD (VTOC) Processing ......................... 108 5.5.3 Indexed VTOC Considerations (OS/390) ................. 109 5.6 VSAM Differences . 110 5.6.1 Introduction . 110 5.6.2 OS/390 Catalogs . 110 5.6.3 OS/390 Catalog Management ....................... 114 5.6.4 OS/390 - VSE/VSAM Catalog Compatibility ............... 117 5.6.5 VSAM Functional Differences ....................... 119 5.6.6 Data Sharing and Integrity ......................... 125 5.6.7 Programming Languages and VSAM Support ............. 131 5.6.8 VSAM Error and Reason Code Compatibility .............. 131 5.6.9 DFSORT and VSAM Considerations ................... 131 Chapter 6. CICS . 133 6.1 Introduction . 133 6.1.1 Overview CICS Transaction Server ................... 133 6.1.2 Essential Supplemental Reading and Migration Support Material . 134 6.1.3 General Compatibility Comments .................... 135 6.1.4 Virtual Storage Considerations for MVS ................. 135 6.1.5 CICS General System Considerations .................. 136 6.1.6 CICS Macro Resource Definition Table Changes ........... 140 6.1.7 CSD and RDO Considerations ...................... 143 6.1.8 CICS System Data Sets Requirements ................. 145 6.1.9 CICS System Program Interface and Exits ............... 147 6.1.10 CICS Transaction Security ........................ 149 Contents v 6.1.11 CICS UPSI . 149 6.1.12 Application Programming . 150 6.1.13 CICS/VSE and TS Coexistence Considerations ............ 153 6.1.14 Testing and Problem Determination Considerations ......... 153 6.1.15 Vendor Applications . 154 6.2 CICS with DL/I ................................... 154 Chapter 7. ICCF and TSO .............................. 155 7.1 Preparing to Use the System .......................... 155 7.1.1 User Profiles . 155 7.1.2 LOGON Procedures . 157 7.1.3 Message Facilities . 157 7.1.4 Security . 157 7.1.5 Summary ................................... 158 7.2 Using the System ................................. 158 7.2.1 Accessing the System ........................... 159 7.2.2 Entering and Manipulating Data ..................... 159 7.3 Executing Programs at a Terminal ...................... 161 7.4 Submitting Jobs for Batch.
Load more

Recommended publications
  • 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]
  • Facility/370: Introduction
    File No. S370-20 Order No. GC20-1800=9 IDl\n \/:u+ •• ".1 I\n"n"': ..... ft IDIVI V IIlUQI .Via"'lllIlv Facility/370: Systems Introduction Release 6 PLC 4 This publication introduces VM/370, and is intended for anyone who is interested in VM/370. However, the reader should have a basic understanding of I BM data processing. VM/370 (Virtual Machine Facility/370) is a system control program (SCP) that tailors the resources and capabilities of a single System/370 computer to provide concurrent users their one unique (virtual) machine. VM/370 consists of a Control Program (CP), which manages the real computer, a Conversational Monitor System (CMS), which is a general-purpose conversational time-sharing system that executes in a virtual machine, a Remote Spooling Communications Subsystem (RSCS), which spools files to and from geographically remote locations, and a Interactive Problem Control System (I PCS), which provides problem analysis and management faci I ities. The first section of the publication is an introduction; it describes what VM/370 can do. The second, third, fourth, and fifth sections describe the Control Program, Conversational Monitor System, Remote Spooling Communications Subsystem, and Interactive Problem Control System respectively. The appendixes include information about VM/370 publication-to-audience relationship and VM/370-related publications for CMS users. , This publication is a prerequisite for the VM/370 system library. --...- --- ---.-- ------- ------ --..- --------- -~-y- Page of GC20-1800-9 As Updated Aug 1, 1979 by TNL GN25-0U89 ~b Edition (Karch 1919) This edition (GC20-1800-~ together with Technical Newsletter GN25-0489. dated August 1, 1919, applies to Release 6 PLC 4 (Program Level Change) of IBM Virtual Machine Facility/310 and to all subsequent releases until otherwise indicated in new editions or Technical Newsletters.
    [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]
  • Z/OS ♦ Z Machines Hardware ♦ Numbers and Numeric Terms ♦ the Road to Z/OS ♦ Z/OS.E ♦ Z/OS Futures ♦ Language Environment ♦ Current Compilers ♦ UNIX System Services
    Mainframes The Future of Mainframes Is Now ♦ z/Architecture ♦ z/OS ♦ z Machines Hardware ♦ Numbers and Numeric Terms ♦ The Road to z/OS ♦ z/OS.e ♦ z/OS Futures ♦ Language Environment ♦ Current Compilers ♦ UNIX System Services by Steve Comstock The Trainer’s Friend, Inc. http://www.trainersfriend.com 800-993-8716 [email protected] Copyright © 2002 by Steven H. Comstock 1 Mainframes z/Architecture z/Architecture ❐ The IBM 64-bit mainframe has been named "z/Architecture" to contrast it to earlier mainframe hardware architectures ♦ S/360 ♦ S/370 ♦ 370-XA ♦ ESA/370 ♦ ESA/390 ❐ Although there is a clear continuity, z/Architecture also brings significant changes... ♦ 64-bit General Purpose Registers - so 64-bit integers and 64-bit addresses ♦ 64-bit Control Registers ♦ 128-bit PSW ♦ Tri-modal addressing (24-bit, 31-bit, 64-bit) ♦ Over 140 new instructions, including instructions to work with ASCII and UNICODE strings Copyright © 2002 by Steven H. Comstock 2 z/Architecture z/OS ❐ Although several operating systems can run on z/Architecture machines, z/OS is the premier, target OS ❐ z/OS is the successor to OS/390 ♦ The last release of OS/390 was V2R10, available 9/2000 ♦ The first release of z/OS was V1R1, available 3/2001 ❐ z/OS can also run on G5/G6 and MP3000 series machines ♦ But only in 31-bit or 24-bit mode ❐ Note these terms: ♦ The Line - the 16MiB address limit of MVS ♦ The Bar - the 2GiB limit of OS/390 ❐ For some perspective, realize that 16EiB is... ♦ 8 billion times 2GiB ♦ 1 trillion times 16MiB ❐ The current release of z/OS is V1R4; V1R5 is scheduled for 1Q2004 Copyright © 2002 by Steven H.
    [Show full text]
  • Managing a VSE Console Under VM from a Remote Location
    BY DAN ASKEW Managing a VSE Console Under VM From a Remote Location hen working remotely, it is sometimes necessary to make changes to the system or talk an W operator through a problem. Using the techniques presented here, you can manage a VSE console under VM. you ever tried to talk an operator through a VSEPROD. You can display the virtual machine name by HAVE problem from a remote site and thought to issuing the following commands. yourself, “If I could only see the console”? As this article will This command redisplays the last 20 lines from partition BG: examine, there are several ways you can do this if you are VSECMD VSEPROD RED 20L,BG running VSE under VM. The first method I will examine allows you to communicate with the VSE con- This command displays the last line from sole in a crude line mode. The other two the console: methods allow you to actually “steal” the VSECMD VSEPROD RED existing console away from the operator. Have you ever tried to This command displays the last 20 METHOD #1 talk an operator through occurrences of EOJ: VSECMD VSEPROD RED 20l,’EOJ’ The first method I tried used a problem from a remote IBM’s VMCF modules supplied by The syntax of these commands is VSE. ICCF Library 59 contains a site and thought to as follows: member named SKVMVSE. The yourself, “If I could only VSECMD (VSE machine name) comments at the beginning of the RED (number of lines (default is member provide you with the installa- see the console”? 1)), (redisplay command) tion instructions.
    [Show full text]
  • IBM Z/VSE 6.2 Brings Storage, Processing, Security, Recovery, and Data Transfer Enhancements
    IBM United States Software Announcement 221-201, dated May 4, 2021 IBM z/VSE 6.2 brings storage, processing, security, recovery, and data transfer enhancements Table of contents 1 Overview 5 Technical information 2 Key requirements 7 Ordering information 2 Planned availability date 7 Terms and conditions 2 Description 8 Order now 5 Program number Overview IBM(R) z/VSE(R) is an operating system for the IBM Z(R) platform used for traditional batch and online transaction processing applications. The following hardware support is available with z/VSE 6.2: • Exploitation of the latest IBM System Storage technology: – z/VSE 6.2 supports IBM System Storage TS7700 R5.1. • Exploitation of latest IBM z15TM Model T01 and T02 technology: – z/VSE 6.2 provides native support for System Recovery Boost (APAR DY47832). This enables z/VSE to temporarily boost general-purpose central processors (CPs) running at sub-capacity to full capacity in a logical partition (LPAR) during system IPL and shutdown. – z/VSE 6.2 supports the configurable IBM Crypto Express7S (APAR DY47834), which enables data encryption and Secure Sockets Layer (SSL) acceleration. Elliptic Curve Cryptography (ECC) with a Crypto Express7S can result in accelerated data-in-flight encryption. The following support is already available with z/VSE 6.2: • z/VSE supports the IBM Fibre Connection (FICON(R)) Express16S+ and FICON Express16SA, as well as the OSA-Express6S/7S family. • z/VSE supports IBM Fibre Channel Endpoint Security, which provides server authentication and data encryption to protect the integrity and confidentiality of data. z/VSE support for Transport Layer Security (TLS) 1.3: • TLS 1.3 support (APAR DY30239) is based on VSE Crypto Services/OpenSSL 1.1.1d update (APAR DY47825, in March 2020).
    [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]
  • Installing the Simple Connection Line Driver Under Z/OS, Z/VSE, MSP, Or Z/VM Installing the Simple Connection Line Driver Under Z/OS, Z/VSE, MSP, Or Z/VM
    Installing the Simple Connection Line Driver Under z/OS, z/VSE, MSP, or z/VM Installing the Simple Connection Line Driver Under z/OS, z/VSE, MSP, or z/VM Installing the Simple Connection Line Driver Under z/OS, z/VSE, MSP, or z/VM This section describes the installation steps for installing Simple Connection Line Driver on a z/OS host systems. Note: The Simple Connection Line Driver is not supported on MSP or VM/GCS systems. Installation Overview Installation Steps Installation Overview To gain an understanding of the entire installation process, Software AG recommends that you read all of the installation steps before you perform the individual steps: Step Description 1 Verify the connectivity between cooperating nodes. This step is necessary only to support the TCP/IP line driver. It is not necessary for the Simple Connection Line Driver. 2 Unload the Entire Net-Work mainline and Entire Net-Work TCP/IP line driver libraries. 3 Outline your Entire Net-Work configuration and obtain all of the data necessary to configure the Entire Net-Work startup parameters. 4 Alter the Entire Net-Work Startup Job 5 Add the TCPX-specific DRIVER and LINK statements. 6 Configure client information. This step is necessary only to support the Simple Connection Line Driver. It is not necessary for the TCP/IP line driver. 7 Ensure that ADARUN has been linked with attribute AMODE(31). This step is necessary only to support the TCP/IP line driver. It is not necessary for the Simple Connection Line Driver. 8 Start Entire Net-Work and perform installation verifications.
    [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]
  • MTS on Wikipedia Snapshot Taken 9 January 2011
    MTS on Wikipedia Snapshot taken 9 January 2011 PDF generated using the open source mwlib toolkit. See http://code.pediapress.com/ for more information. PDF generated at: Sun, 09 Jan 2011 13:08:01 UTC Contents Articles Michigan Terminal System 1 MTS system architecture 17 IBM System/360 Model 67 40 MAD programming language 46 UBC PLUS 55 Micro DBMS 57 Bruce Arden 58 Bernard Galler 59 TSS/360 60 References Article Sources and Contributors 64 Image Sources, Licenses and Contributors 65 Article Licenses License 66 Michigan Terminal System 1 Michigan Terminal System The MTS welcome screen as seen through a 3270 terminal emulator. Company / developer University of Michigan and 7 other universities in the U.S., Canada, and the UK Programmed in various languages, mostly 360/370 Assembler Working state Historic Initial release 1967 Latest stable release 6.0 / 1988 (final) Available language(s) English Available programming Assembler, FORTRAN, PL/I, PLUS, ALGOL W, Pascal, C, LISP, SNOBOL4, COBOL, PL360, languages(s) MAD/I, GOM (Good Old Mad), APL, and many more Supported platforms IBM S/360-67, IBM S/370 and successors History of IBM mainframe operating systems On early mainframe computers: • GM OS & GM-NAA I/O 1955 • BESYS 1957 • UMES 1958 • SOS 1959 • IBSYS 1960 • CTSS 1961 On S/360 and successors: • BOS/360 1965 • TOS/360 1965 • TSS/360 1967 • MTS 1967 • ORVYL 1967 • MUSIC 1972 • MUSIC/SP 1985 • DOS/360 and successors 1966 • DOS/VS 1972 • DOS/VSE 1980s • VSE/SP late 1980s • VSE/ESA 1991 • z/VSE 2005 Michigan Terminal System 2 • OS/360 and successors
    [Show full text]
  • Introduction-To-Mainframes.Pdf
    Mainframe The term ‘MainFrame’ brings to mind a giant room of electronic parts that is a computer, referring to the original CPU cabinet in a computer of the mid-1960’s. Today, Mainframe refers to a class of ultra-reliable large and medium-scale servers designed for carrier-class and enterprise-class systems operations. Mainframes are costly, due to the support of symmetric multiprocessing (SMP) and dozens of central processors existing within in a single system. Mainframes are highly scalable. Through the addition of clusters, high-speed caches and volumes of memory, they connect to terabyte holding data subsystems. Mainframe computer Mainframe is a very large and expensive computer capable of supporting hundreds, or even thousands, of users simultaneously. In the hierarchy that starts with a simple microprocessor at the bottom and moves to supercomputers at the top, mainframes are just below supercomputers. In some ways, mainframes are more powerful than supercomputers because they support more simultaneous programs. But supercomputers can execute a single program faster than a mainframe. The distinction between small mainframes and minicomputers is vague, depending really on how the manufacturer wants to market its machines. Modern mainframe computers have abilities not so much defined by their single task computational speed (usually defined as MIPS — Millions of Instructions Per Second) as by their redundant internal engineering and resulting high reliability and security, extensive input-output facilities, strict backward compatibility with older software, and high utilization rates to support massive throughput. These machines often run for years without interruption, with repairs and hardware upgrades taking place during normal operation.
    [Show full text]
  • Systems Introduction to OS/VS2 Release 2 First Edition (March, 1973)
    GC28-0661-1 File No. S370-34 Systems Introduction to OS/VS2 Release 2 First Edition (March, 1973) This edition is a reprint of GC28-0661{) incorporating some editorial changes. It does not obsolete GC28-0661-O. This edition applies to Release 2 of OS/VS2 and to all subsequent releases until otherwise indicated in new editions or Technical Newsletters. Changes are continually made to the information herein; before using this publication in connection with the operation of IBM systems, consult the latest IBM System/360 and System/370 Bibliography, Order No. GA22-6822, and the current SRL Newsletter. Order No. GN20-0360, for the editions that are applicable and current. Requests for copies of IBM publications should be made to your IBM representative or to the IBM branch office serving your locality. A form for readers' comments is provided at the back of this pUblication. If the form has been removed, comments may be addressed to IBM Corporation, Publications Development, iJepartment 058, Building 706-2, PO Box 390, Poughkeepsie, N.Y. 12602. Comments and suggestions become the property of IBM. © Copyright International Business Machines Corporation 1973 Preface This publication contains introductory information Design Concepts -- shows sequence of operation and about OS/VS2 Release 2, a system control other highlights of system design. program (SCP) that features virtual storage, System Requirements -- lists the basic hardware multiprogramming, multiprocessing, time sharing, requirements. and job entry subsystems. It is assumed that readers have a basic knowledge of programming Compatibility -- points out the major differences systems such as OS/MVT or OS/VS2 Release 1.
    [Show full text]