DOCSLIB.ORG

Introduction to the New Mainframe: Z/OS Basics

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Introduction to the New Mainframe: Z/OS Basics Front cover Introduction to the New Mainframe z/OS Basics Basic mainframe concepts, including usage and architecture z/OS fundamentals for students and beginners Mainframe hardware and peripheral devices Mike Ebbers John Kettner Wayne O’Brien Bill Ogden ibm.com/redbooks International Technical Support Organization Introduction to the New Mainframe: z/OS Basics March 2011 SG24-6366-02 Note: Before using this information and the product it supports, read the information in “Notices” on page xi. Third Edition (March 2011) © Copyright International Business Machines Corporation 2006, 2009, 2011. 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 . xiii How this text is organized . xiv How each chapter is organized . xiv The team who wrote this book . xv Acknowledgements . xvi Now you can become a published author, too! . xix Comments welcome. xix Stay connected to IBM Redbooks . xix Summary of changes . xxi March 2011, Third Edition . xxi August 2009, Second Edition . xxi Part 1. Introduction to z/OS and the mainframe environment Chapter 1. Introduction to the new mainframe . 3 1.1 The new mainframe. 4 1.2 The System/360: A turning point in mainframe history . 4 1.3 An evolving architecture . 5 1.4 Mainframes in our midst . 8 1.5 What is a mainframe . 9 1.6 Who uses mainframe computers. 12 1.7 Factors contributing to mainframe use . 15 1.8 Typical mainframe workloads . 22 1.9 Roles in the mainframe world . 29 1.10 z/OS and other mainframe operating systems . 37 1.11 Introducing the IBM zEnterprise System . 40 1.12 Summary . 41 1.13 Questions for review . 42 1.14 Topics for further discussion . 42 Chapter 2. Mainframe hardware systems and high availability . 45 2.1 Introduction to mainframe hardware systems . 46 2.2 Early system design . 47 2.3 Current design. 50 2.4 Processing units . 59 © Copyright IBM Corp. 2006, 2009, 2011. All rights reserved. iii 2.5 Multiprocessors . 62 2.6 Disk devices . 63 2.7 Clustering . 65 2.8 Basic shared DASD. 66 2.9 What is a sysplex . 69 2.10 Intelligent Resource Director . 75 2.11 Platform Performance Management with zEnterprise. 76 2.12 Typical mainframe system growth. 77 2.13 Continuous availability of mainframes. 78 2.14 Summary . 87 2.15 Questions for review . 88 2.16 Topics for further discussion . 89 2.17 Exercises. 89 Chapter 3. z/OS overview. 91 3.1 What is an operating system . 92 3.2 What is z/OS . 92 3.3 Overview of z/OS facilities. 99 3.4 Virtual storage and other mainframe concepts . 101 3.5 What is workload management . 126 3.6 I/O and data management. 129 3.7 Supervising the execution of work in the system . 131 3.8 Cross-memory services. 143 3.9 Defining characteristics of z/OS . 144 3.10 Understanding system and product messages . 146 3.11 Predictive failure analysis . 150 3.12 z/OS and other mainframe operating systems . 151 3.13 A brief comparison of z/OS and UNIX. 152 3.14 Additional software products for z/OS . 155 3.15 Middleware for z/OS . 156 3.16 The new face of z/OS . 157 3.17 Summary . 159 3.18 Questions for review . 161 3.19 Topics for further discussion . 163 Chapter 4. TSO/E, ISPF, and UNIX: Interactive facilities of z/OS . 165 4.1 How do we interact with z/OS . 166 4.2 Time Sharing Option/Extensions overview . 166 4.3 ISPF overview . 172 4.4 z/OS UNIX interactive interfaces. 188 4.5 Summary . 194 4.6 Questions for review . 195 4.7 Exercises. 196 iv Introduction to the New Mainframe: z/OS Basics Chapter 5. Working with data sets. 203 5.1 What is a data set . 204 5.2 Where are data sets stored . 205 5.3 What are access methods. 206 5.4 How are DASD volumes used. 206 5.5 Allocating a data set . 208 5.6 How data sets are named . 208 5.7 Allocating space on DASD volumes through JCL . 210 5.8 Data set record formats. 211 5.9 Types of data sets . 214 5.10 What is Virtual Storage Access Method . ..
Load more

Recommended publications
  • Cloud Enabling CICS
    Front cover Cloud Enabling IBM CICS Discover how to quickly cloud enable a traditional IBM 3270-COBOL-VSAM application Use CICS Explorer to develop and deploy a multi-versioned application Understand the benefits of threshold policy Rufus Credle Isabel Arnold Andrew Bates Michael Baylis Pradeep Gohil Christopher Hodgins Daniel Millwood Ian J Mitchell Catherine Moxey Geoffrey Pirie Inderpal Singh Stewart Smith Matthew Webster ibm.com/redbooks International Technical Support Organization Cloud Enabling IBM CICS December 2014 SG24-8114-00 Note: Before using this information and the product it supports, read the information in “Notices” on page vii. First Edition (December 2014) This edition applies to CICS Transaction Server for z/OS version 5.1, 3270-COBOL-VSAM application. © Copyright International Business Machines Corporation 2014. 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 . vii Trademarks . viii IBM Redbooks promotions . ix Preface . xi Authors. xii Now you can become a published author, too! . .xv Comments welcome. .xv Stay connected to IBM Redbooks . xvi Part 1. Introduction . 1 Chapter 1. Cloud enabling your CICS TS applications . 3 1.1 Did you know?. 4 1.2 Business value . 4 1.3 Solution overview . 5 1.4 Cloud computing in a CICS TS context. 6 1.5 Overview of the cloud-enabling technologies in CICS TS V5 . 11 1.5.1 Platform overview . 12 1.5.2 Application overview . 13 Chapter 2. GENAPP introduction. 15 2.1 CICS TS topology . 16 2.2 Application architecture. 17 2.2.1 GENAPP in a single managed region.
    [Show full text]
  • On-Line Computing with a Hierarchy of Processors
    University of Pennsylvania ScholarlyCommons Technical Reports (CIS) Department of Computer & Information Science December 1968 On-Line Computing With a Hierarchy of Processors Richard P. Morton University of Pennsylvania Follow this and additional works at: https://repository.upenn.edu/cis_reports Recommended Citation Richard P. Morton, "On-Line Computing With a Hierarchy of Processors", . December 1968. University of Pennsylvania Department of Computer and Information Science Technical Report No. MS-CIS-69-13. This paper is posted at ScholarlyCommons. https://repository.upenn.edu/cis_reports/804 For more information, please contact [email protected]. On-Line Computing With a Hierarchy of Processors Abstract Time shared computer systems have been based upon the two techniques of multiprogramming and swapping. Multiprogramming is based on restricting each program to a portion of the total computer memory. Swapping requires considerable overhead time for loading and unloading programs. To alleviate the size restriction due to multiprogramming, segmentation is employed, resulting in fact in vastly increased swapping. A new system architecture is proposed for time shared computing that alleviates the high overhead or program size restriction. It utilizes a hierarchy of processors, where each processor is assigned tasks on the basis of four factors: interactive requirements, frequency of use, execution time, and program length. In order to study the hierarchical approach to system architecture, the Moore School Problem Solving Facility (MSPSF) was built and used. The study of the manner of operation and the reactions of the users clarified and defined the Hierarchy of Processors system architecture. The Moore School Problem Solving Facility was implemented on second generation equipment, the IBM 7040, and therefore it is not possible to adequately compare the efficiency with third generation computers operating in a swapping mode.
    [Show full text]
  • IBM Developer for Z/OS Enterprise Edition
    Solution Brief IBM Developer for z/OS Enterprise Edition A comprehensive, robust toolset for developing z/OS applications using DevOps software delivery practices Companies must be agile to respond to market demands. The digital transformation is a continuous process, embracing hybrid cloud and the Application Program Interface (API) economy. To capitalize on opportunities, businesses must modernize existing applications and build new cloud native applications without disrupting services. This transformation is led by software delivery teams employing DevOps practices that include continuous integration and continuous delivery to a shared pipeline. For z/OS Developers, this transformation starts with modern tools that empower them to deliver more, faster, with better quality and agility. IBM Developer for z/OS Enterprise Edition is a modern, robust solution that offers the program analysis, edit, user build, debug, and test capabilities z/OS developers need, plus easy integration with the shared pipeline. The challenge IBM z/OS application development and software delivery teams have unique challenges with applications, tools, and skills. Adoption of agile practices Application modernization “DevOps and agile • Mainframe applications • Applications require development on the platform require frequent updates access to digital services have jumped from the early adopter stage in 2016 to • Development teams must with controlled APIs becoming common among adopt DevOps practices to • The journey to cloud mainframe businesses”1 improve their
    [Show full text]
  • Netezza EOL: IBM IAS Is a Flawed Upgrade Path Netezza EOL: IBM IAS Is a Flawed Upgrade Path
    Author: Marc Staimer WHITE PAPER Netezza EOL: What You’re Not Being Told About IBM IAS Is a Flawed Upgrade Path Database as a Service (DBaaS) WHITE PAPER • Netezza EOL: IBM IAS Is a Flawed Upgrade Path Netezza EOL: IBM IAS Is a Flawed Upgrade Path Executive Summary It is a common technology vendor fallacy to compare their systems with their competitors by focusing on the features, functions, and specifications they have, but the other guy doesn’t. Vendors ignore the opposite while touting hardware specs that mean little. It doesn’t matter if those features, functions, and specifications provide anything meaningfully empirical to the business applications that rely on the system. It only matters if it demonstrates an advantage on paper. This is called specsmanship. It’s similar to starting an argument with proof points. The specs, features, and functions are proof points that the system can solve specific operational problems. They are the “what” that solves the problem or problems. They mean nothing by themselves. Specsmanship is defined by Wikipedia as: “inappropriate use of specifications or measurement results to establish supposed superiority of one entity over another, generally when no such superiority exists.” It’s the frequent ineffective sales process utilized by IBM. A textbook example of this is IBM’s attempt to move their Netezza users to the IBM Integrated Analytics System (IIAS). IBM is compelling their users to move away from Netezza. In the fall of 2017, IBM announced to the Enzee community (Netezza users) that they can no longer purchase or upgrade PureData System for Analytics (the most recent IBM name for its Netezza appliances), and it will end-of-life all support next year.
    [Show full text]
  • Operating Systems
    Operating Systems Interface between User & Computer Hardware Applications Programs Utilities Operating System Hardware Utilities Memory Resident File Access & Control Program Creation Memory Resident File Format Structures o Editors Access Management o Compilers Protection Schemes o Debuggers System Access & Control File Manipulation System-Wide Access o File Manipulation Resource Access o File Deletion Error Detection & Response Mechanism Program Execution Error Detection Link-Loaders Error Correction Run-Time Management Response to Unrecoverable Error I/O Device Access & Control Accounting Storage File Format Structures System Usage Collection Access Management System Performance Tuning Protection Schemes Forecasting Enhancement Requirements Billing Users for Usage Resource Manager O/S KernelKernel I/O Controller Printers, Keyboards, I/O Controller Monitors, Portions of Cameras, the O/S Etc. currently in use Computer Main System Memory Portions of Various I/O Application Devices Programs Currently in use Operating System Data Application Programs I/O Controller Storage Processor Processor Data Processor Processor Operation Allocation of Main Memory is made jointly by both the O/S and Memory Management Hardware O/S controls access to I/O devices by Application Programs O/S controls access to and use of files O/S controls access to and use of the processors, i.e., how much time can be allocated to the execution of a particular Application Program Classification of Operating Systems Interactive O/S Keyboard & Monitor Access to O/S Immediate,
    [Show full text]
  • SAP Database Administration with IBM
    André Faustmann, Michael Greulich, André Siegling, Benjamin Wegner, and Ronny Zimmerman SAP® Database Administration with IBM® DB2® Bonn Boston Contents at a Glance 1 Introduction ............................................................................ 19 2 SAP System Landscapes ......................................................... 25 3 Basics and Architecture of the IBM DB2 for LUW Database ................................................................................. 71 4 Lifecycle ................................................................................. 233 5 Administration Tools Inside and Outside the SAP System .... 327 6 Backup, Restore, and Recovery .............................................. 463 7 Monitoring DB2 SAP Systems with SAP Solution Manager .................................................................................. 575 8 SAP NetWeaver Business Warehouse and IBM DB2 for LUW .................................................................................. 647 9 Common Problems and Their Solutions for DB2 Administrators ........................................................................ 697 Contents Foreword .................................................................................... 15 Acknowledgments ....................................................................... 17 1 Introduction ................................................................. 19 1.1 Who This Book Is For .................................................... 21 1.2 Focus of This Book .......................................................
    [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]
  • Of Friday 13 June 2008 Supplement No. 1 Birthday Honours List — United Kingdom
    05-06-2008 13:04:14 [SO] Pag Table: NGSUPP PPSysB Job: 398791 Unit: PAG1 Number 58729 Saturday 14 June 2008 http://www.london-gazette.co.uk B1 [ Richard Gillingwater. (Jun. 14, 2008). C.B.E. Commander of the Order of the British Empire, 2008 Birthday Honours, No. 58729, Supp. No. 1, PDF, p. B7. London Gazette. Reproduced for educationaly purposes only. Fair Use relied upon. ] Registered as a newspaper Published by Authority Established 1665 of Friday 13 June 2008 Supplement No. 1 Birthday Honours List — United Kingdom CENTRAL CHANCERY OF Dr. Philip John Hunter, C.B.E., Chief Schools THE ORDERS OF KNIGHTHOOD Adjudicator. For services to Education. Moir Lockhead, O.B.E., Chief Executive, First Group. St. James’s Palace, London SW1 For services to Transport. 14 June 2008 Professor Andrew James McMichael, F.R.S., Professor of Molecular Medicine and Director, Weatherall The Queen has been graciously pleased, on the occasion Institute of Molecular Medicine, University of Oxford. of the Celebration of Her Majesty’s Birthday, to signify For services to Medical Science. her intention of conferring the honour of Knighthood William Moorcroft, Principal, TraVord College. For upon the undermentioned: services to local and national Further Education. William Desmond Sargent, C.B.E., Executive Chair, Better Regulation Executive, Department for Business, Enterprise and Regulatory Reform. For services to Knights Bachelor Business. Michael John Snyder. For services to Business and to the City of London Corporation. Paul Robert Stephenson, Q.P.M., Deputy Commissioner, Dr. James Iain Walker Anderson, C.B.E. For public and Metropolitan Police Service.
    [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]
  • 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]
  • Data Definition Language
    1 Structured Query Language SQL, or Structured Query Language is the most popular declarative language used to work with Relational Databases. Originally developed at IBM, it has been subsequently standard- ized by various standards bodies (ANSI, ISO), and extended by various corporations adding their own features (T-SQL, PL/SQL, etc.). There are two primary parts to SQL: The DDL and DML (& DCL). 2 DDL - Data Definition Language DDL is a standard subset of SQL that is used to define tables (database structure), and other metadata related things. The few basic commands include: CREATE DATABASE, CREATE TABLE, DROP TABLE, and ALTER TABLE. There are many other statements, but those are the ones most commonly used. 2.1 CREATE DATABASE Many database servers allow for the presence of many databases1. In order to create a database, a relatively standard command ‘CREATE DATABASE’ is used. The general format of the command is: CREATE DATABASE <database-name> ; The name can be pretty much anything; usually it shouldn’t have spaces (or those spaces have to be properly escaped). Some databases allow hyphens, and/or underscores in the name. The name is usually limited in size (some databases limit the name to 8 characters, others to 32—in other words, it depends on what database you use). 2.2 DROP DATABASE Just like there is a ‘create database’ there is also a ‘drop database’, which simply removes the database. Note that it doesn’t ask you for confirmation, and once you remove a database, it is gone forever2. DROP DATABASE <database-name> ; 2.3 CREATE TABLE Probably the most common DDL statement is ‘CREATE TABLE’.
    [Show full text]
  • Chapter 10 Introduction to Batch Files
    Instructor’s Manual Chapter 10 Lecture Notes Introduction to Batch Files Chapter 10 Introduction to Batch Files LEARNING OBJECTIVES 1. Compare and contrast batch and interactive processing. 2. Explain how batch files work. 3. Explain the purpose and function of the REM, ECHO, and PAUSE commands. 4. Explain how to stop or interrupt the batch file process. 5. Explain the function and use of replaceable parameters in batch files. 6. Explain the function of pipes, filters, and redirection in batch files. STUDENT OUTCOMES 1. Use Edit to write batch files. 2. Use COPY CON to write batch files. 3. Write and execute a simple batch file. 4. Write a batch file to load an application program. 5. Use the REM, PAUSE, and ECHO commands in batch files. 6. Terminate a batch file while it is executing. 7. Write batch files using replaceable parameters. 8. Write a batch file using pipes, filters, and redirection. CHAPTER SUMMARY 1. Batch processing means running a series of instructions without interruption. 2. Interactive processing allows the user to interface directly with the computer and update records immediately. 3. Batch files allow a user to put together a string of commands and execute them with one command. 4. Batch files must have the .BAT or .CMD file extension. 5. Windows looks first internally for a command, then for a .COM files extension, then for a .EXE file extension, and finally for a .BAT or .CMD file extension. 6. Edit is a full-screen text editor used to write batch files. 7. A word processor, if it has a means to save files in ASCII, can be used to write batch files.
    [Show full text]