DOCSLIB.ORG

Z/OS Basics Preface

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Z/OS Basics Preface Contents Preface . iii How this course is organized . iii How each topic is organized . iv 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 S/360: A turning point in mainframe history . 4 1.3 An evolving architecture . 5 1.4 Mainframes in our midst . 6 1.5 What is a mainframe? . 7 1.6 Who uses mainframe computers?. 10 1.7 Factors contributing to mainframe use . 11 1.8 Typical mainframe workloads . 14 1.9 Roles in the mainframe world . 21 1.10 z/OS and other mainframe operating systems . 27 1.11 Summary . 29 Chapter 2. z/OS overview. 31 2.1 What is an operating system? . 32 2.2 Overview of z/OS facilities. 32 2.3 What is z/OS? . 34 2.4 Virtual storage and other mainframe concepts . 39 2.5 What is workload management? . 57 2.6 I/O and data management. 60 2.7 Supervising the execution of work in the system . 60 2.8 Defining characteristics of z/OS . 68 2.9 Licensed programs for z/OS . 69 2.10 Middleware for z/OS . 70 2.11 A brief comparison of z/OS and UNIX. 71 2.12 Summary . 73 Chapter 3. TSO/E, ISPF, and UNIX: Interactive facilities of z/OS . 75 3.1 How do we interact with z/OS? . 76 3.2 TSO overview . 76 3.3 ISPF overview . 80 3.4 z/OS UNIX interactive interfaces. 99 3.5 Summary . 105 © Copyright IBM Corp. 2005, 2006. All rights reserved. i Chapter 4. Working with data sets. 107 4.1 What is a data set? . 108 4.2 Where are data sets stored? . 109 4.3 Role of DFSMS in managing space . 109 4.4 What are access methods?. 111 4.5 How are DASD volumes used?. 111 4.6 Allocating a data set . 112 4.7 Allocating space on DASD volumes through JCL . 113 4.8 Data set record formats. 114 4.9 Types of data sets . 117 4.10 What is VSAM? . 122 4.11 How data sets are named . 124 4.12 Catalogs and VTOCs . 125 4.13 z/OS UNIX file systems . 130 4.14 Summary . 133 Chapter 5. Batch processing and JES. 135 5.1 What is batch processing? . 136 5.2 What is JES?. 136 5.3 What an initiator does . 139 5.4 Why z/OS uses symbolic file names . 139 5.5 Job and output management with JES . 141 5.6 Job flow through the system . 148 5.7 JES2 compared to JES3 . 151 5.8 Summary . 151 Chapter 6. Using JCL and SDSF . 153 6.1 What is JCL? . 154 6.2 Basic JCL statements . 154 6.3 JOB, EXEC, and DD operands . 156 6.4 Data set disposition, DISP operand . 159 6.5 Continuation and concatenation . 161 6.6 Reserved DDNAMES . 162 6.7 JCL procedures (PROCs) . 163 6.8 Using SDSF. 165 6.9 Utilities. 170 6.10 System libraries. 170 6.11 Summary . 170 ii z/OS Basics Preface This course provides students of information systems technology with the background knowledge and skills necessary to begin using the basic facilities of a mainframe computer. For optimal learning, students are assumed to have successfully completed an introductory course in computer system concepts, such as computer organization and architecture, operating systems, data management, or data communications. They should also have successfully completed courses in one or more programming languages, and be PC literate. Note that this course can also be used as a prerequisite for courses in advanced topics such as compiler algorithms, or for internships and special studies. Others who will benefit from this course include data processing professionals who have experience with non-mainframe platforms, or who are familiar with some aspects of the mainframe but want to become knowledgeable with other facilities and benefits of the mainframe environment. When moving through this course, instructors are encouraged to alternate between course, lecture, discussions, and hands-on exercises. The instructor-led discussions and hands-on exercises are an integral part of the learning experience, and can include topics not covered in this course. After reading this course, students will have received: A general introduction to mainframe concepts, usage, and architecture A comprehensive overview of z/OS, a widely used mainframe operating system An understanding of mainframe workloads and an overview of the major middleware applications in use on mainframes today The basis for subsequent course work in more advanced, specialized areas of z/OS, such as system administration or application programming How this course is organized This course is organized in four parts, as follows: Part 1. “Introduction to z/OS and the mainframe environment” provides an overview of the types of workloads commonly processed on the mainframe, such as batch jobs and online transactions. This part of the course helps students explore the © Copyright IBM Corp. 2005, 2006. All rights reserved. iii user interfaces of z/OS, a widely used mainframe operating system. Discussion topics include TSO/E and ISPF, UNIX interfaces, job control language, file structures, and job entry subsystems. Special attention is paid to the users of mainframes and to the evolving role of mainframes in today’s business world. Part 2. “Application programming on z/OS” introduces the tools and utilities for developing a simple program to run on z/OS. This part of the course guides the student through the process of application design, choosing a programming language, and using a runtime environment. Part 3. “Online workloads for z/OS” examines the major categories of interactive workloads processed by z/OS, such as transaction processing, database management, and Web-serving. This part of the course includes discussions of several popular middleware products, including DB2®, CICS®, and WebSphere® Application Server. Part 4. “System programming on z/OS” provides topics to help the student become familiar with the role of the z/OS system programmer. This part of the course includes discussions of system libraries, starting and stopping the system, security, network communications and the clustering of multiple systems. Also provided is an overview of mainframe hardware systems, including processors and I/O devices. In this course, we use simplified examples and focus mainly on basic system functions. Hands-on exercises are provided throughout the course to help students explore the mainframe style of computing. Exercises include entering work into the system, checking its status, and examining the output of submitted jobs. How each topic is organized Each chapter follows a common format: Objectives for the student Topics that teach a central theme related to mainframe computing Summary of the main ideas of the chapter A list of key terms introduced in the chapter Questions for review to help students verify their understanding of the material Topics for further discussion to encourage students to explore issues that extend beyond the chapter objectives Hands-on exercises intended to help students reinforce their understanding of the material iv.
Load more

Recommended publications
  • The Arcati Mainframe Yearbook 2020
    ArcatiArcati MainframeMainframe YearbookYearbook 20072020 Mainframe strategy The Arcati Mainframe Yearbook 2020 The independent annual guide for users of IBM mainframe systems SPONSORED BY: PUBLISHED BY: Arcati Limited 19 Ashbourne Way Thatcham Berks RG19 3SJ UK Phone: +44 (0) 7717 858284 Fax: +44 (0) 1635 881717 Web: http://www.arcati.com/ E-mail: [email protected] © Arcati Limited, 2020 1 Arcati Mainframe Yearbook 2020 Mainframe strategy Contents Welcome to the Arcati Mainframe Yearbook 2020 ............................................................ 3 10 Steps to True Mainframe DevOps: A Phased Approach to Cross-platform DevOps Success ................................................................................. 6 Mainframe Data Management .......................................................................................... 17 Join a Mainframe Development Revolution in 2020 – Embrace Open! ....................... 22 Indicators of Compromise and Why It Takes Six-Plus Months to ID a Breach ........... 27 Mainframe breaches: a beginner’s defensive strategy ................................................. 33 The 2020 Mainframe User Survey .................................................................................... 37 An analysis of the profile, plans, and priorities of mainframe users Vendor Directory ............................................................................................................... 55 Vendors, consultants, and service providers in the z/OS environment A guide to sources of information
    [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]
  • 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]
  • 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]
  • Performance Best Practices for Vmware Workstation Vmware Workstation 7.0
    Performance Best Practices for VMware Workstation VMware Workstation 7.0 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more recent editions of this document, see http://www.vmware.com/support/pubs. EN-000294-00 Performance Best Practices for VMware Workstation You can find the most up-to-date technical documentation on the VMware Web site at: http://www.vmware.com/support/ The VMware Web site also provides the latest product updates. If you have comments about this documentation, submit your feedback to: [email protected] Copyright © 2007–2009 VMware, Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws. VMware products are covered by one or more patents listed at http://www.vmware.com/go/patents. VMware is a registered trademark or trademark of VMware, Inc. in the United States and/or other jurisdictions. All other marks and names mentioned herein may be trademarks of their respective companies. VMware, Inc. 3401 Hillview Ave. Palo Alto, CA 94304 www.vmware.com 2 VMware, Inc. Contents About This Book 5 Terminology 5 Intended Audience 5 Document Feedback 5 Technical Support and Education Resources 5 Online and Telephone Support 5 Support Offerings 5 VMware Professional Services 6 1 Hardware for VMware Workstation 7 CPUs for VMware Workstation 7 Hyperthreading 7 Hardware-Assisted Virtualization 7 Hardware-Assisted CPU Virtualization (Intel VT-x and AMD AMD-V)
    [Show full text]
  • Introduction to MS-DOS
    1.Introduction to MS-DOS : MS-DOS (Microsoft Disk Operating System) was the Microsoft-marketed version of the first widely-installed operating system in personal computers. It was essentially the same operating system that (Bill Gates's) young company developed for IBM as Personal Computer - Disk Operating System in 1981. Most users of either DOS system simply referred to their system as Disk Operating System. Like PC-DOS, MS-DOS was (and still is) a non-graphical line-oriented command- driven operating system, with a relatively simple interface but not overly "friendly" user interface. Its prompt to enter a command looks like this: C:\> MS-DOS does not care about anything called an icon, wallpaper or screen saver. Rather than being considered as a Graphical User Interface (GUI) MS-DOS is what is known as a command-line interface. You type commands on what is called the command line. MS-DOS is a single-user, single-tasking computer operating system. In spite of its very small size and relative simplicity, it is one of the most successful operating systems that has been developed to date. In DOS, a file name consists of eight character followed by a 3 character file extension. The size of a file is restricted to a 4 byte file descriptor, which limits a file’s maximum size to approximately 4 billion characters. The first release of DOS could not read or write to disk drives so users could only read and write to a floppy disc. DOS was not a state of the art operating system, even for its time.
    [Show full text]
  • Chapter 1. Origins of Mac OS X
    1 Chapter 1. Origins of Mac OS X "Most ideas come from previous ideas." Alan Curtis Kay The Mac OS X operating system represents a rather successful coming together of paradigms, ideologies, and technologies that have often resisted each other in the past. A good example is the cordial relationship that exists between the command-line and graphical interfaces in Mac OS X. The system is a result of the trials and tribulations of Apple and NeXT, as well as their user and developer communities. Mac OS X exemplifies how a capable system can result from the direct or indirect efforts of corporations, academic and research communities, the Open Source and Free Software movements, and, of course, individuals. Apple has been around since 1976, and many accounts of its history have been told. If the story of Apple as a company is fascinating, so is the technical history of Apple's operating systems. In this chapter,[1] we will trace the history of Mac OS X, discussing several technologies whose confluence eventually led to the modern-day Apple operating system. [1] This book's accompanying web site (www.osxbook.com) provides a more detailed technical history of all of Apple's operating systems. 1 2 2 1 1.1. Apple's Quest for the[2] Operating System [2] Whereas the word "the" is used here to designate prominence and desirability, it is an interesting coincidence that "THE" was the name of a multiprogramming system described by Edsger W. Dijkstra in a 1968 paper. It was March 1988. The Macintosh had been around for four years.
    [Show full text]
  • IBM DB2 for Z/OS: the Database for Gaining a Competitive Advantage!
    Why You Should Read This Book Tom Ramey, Director, DB2 for z/OS IBM Silicon Valley Laboratory “This book is a ‘must read’ for Enterprise customers and contains a wealth of valuable information! “It is clear that there is a technology paradigm shift underway, and this is opening enormous opportunities for companies in all industries. Adoption of Cloud, Mobile, and Analytics promises to revolutionize the way we do business and will add value to a company’s business processes across all functions from sales, marketing, procurement, manufacturing and finance. “IT will play a significant role enabling this shift. Read this book and find out how to integrate the heart of your infrastructure, DB2 for z/OS, with new technologies in order to maximize your investment and drive new value for your customers.” Located at IBM’s Silicon Valley Laboratory, Tom is the director of IBM’s premiere relational database management system. His responsibilities include Architecture, Development, Service, and Customer Support for DB2. He leads development labs in the United States, Germany, and China. Tom works closely with IBM’s largest clients to ensure that DB2 for z/OS continues as the leading solution for modern applications, encompassing OLTP to mobile to analytics. At the same time he continues an uncompromising focus on meeting the needs of the most demanding operational environments on Earth, through DB2’s industry- leading performance, availability, scaling, and security capabilities. IBM DB2 for z/OS: The Database for Gaining a Competitive Advantage! Shantan Kethireddy Jane Man Surekha Parekh Pallavi Priyadarshini Maryela Weihrauch MC Press Online, LLC Boise, ID 83703 USA IBM DB2 for z/OS: The Database for Gaining a Competitive Advantage! Shantan Kethireddy, Jane Man, Surekha Parekh, Pallavi Priyadarshini, and Maryela Weihrauch First Edition First Printing—October 2015 © Copyright 2015 IBM.
    [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]
  • Operating Systems
    CS101 – Fundamentals of Computer and Information Sciences – LIU 1 of 2 Operating systems OS History We covered a (slightly rambling) story about the history of operating systems. Batch computing Batch systems were extraordinarily large and expensive, so that organizations could afford at most one or two. The machines had a human operator who was responsible for scheduling tasks for the machine, in order to make best use of its (very valuable) time. • Norwich council takes delivery of its first computer –@StuartSumner • Punch cards • IBM ad feat. punched cards • Keypunch machine • IBM 704 with card reader • LEGO Grace Hopper with Univac TODO: scheduling and calculating turn-around time using First-Come First-Served (FCFS) vs. Shortest Job First. (See book section 10.4, pages 350–351.) Time-sharing When mini-computers became available (just the size of a refrigerator, not a whole room), then we could have one for each workgroup or department within an orga- nization. They were powerful enough that multiple users could share the computer at the same time, by connecting multiple terminals (keyboard and monitor) to the same machine. The job of the human operator was now automated, and this was the golden ageof operating systems. Not only did they have to schedule tasks effectively, but they had to switch efficiently among serving different users, protect those users from interfer- ing with each other’s work, and so on. Some of the operating systems developed in this era were Multics, VMS, and UNIX. • PDP-11 with Ken Thompson, Dennis Ritchie • VT-101 terminal • IBM 7090 time-sharing video • Brian Kernighan on Bell Labs (Computerphile video) 2 of 2 Prof.
    [Show full text]