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 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? . 1-20 1.8.3 Who are the application designers and programmers? . 1-21 1.8.4 Who is the system operator? . 1-21 1.8.5 Who is the production control analyst? . 1-22 1.8.6 What role do vendors play? . 1-22 1.9 z/OS and other mainframe operating systems . 1-23 1.9.1 z/VM . 1-24 1.9.2 VSE . 1-24 1.9.3 Linux for zSeries . 1-24 1.9.4 z/TPF. 1-25 1.10 Summary . 1-26 1.11 Topics for further discussion . 1-27 Chapter 2. z/OS overview. 2-1 2.1 What is an operating system? . 2-2 © Copyright IBM Corp. 2005. All rights reserved. iii 2.2 What is z/OS? . 2-2 2.2.1 Hardware resources used by z/OS . 2-3 2.2.2 Modules and macros. 2-4 2.2.3 Program status word . 2-5 2.2.4 Multiprogramming and multiprocessing . 2-5 2.2.5 Control blocks . 2-6 2.2.6 Physical storage used by z/OS . 2-6 2.3 Virtual storage and other mainframe concepts . 2-7 2.3.1 What is virtual storage?. 2-7 2.3.2 What is an address space?. 2-8 2.4 Virtual storage overview . 2-9 2.4.1 What is paging? . 2-9 2.4.2 What is a virtual storage address? . 2-10 2.4.3 What is dynamic address translation? . 2-11 2.4.4 How does virtual storage work? . 2-12 2.4.5 Frames, pages, and slots . 2-13 2.4.6 Page stealing . 2-14 2.4.7 Swapping . 2-14 2.4.8 A brief history of virtual storage and 64-bit addressability. 2-15 2.4.9 What’s in an address space? . 2-19 2.4.10 z/OS system address spaces . 2-20 2.5 How peripheral storage is managed in z/OS. 2-21 2.6 Summary of z/OS facilities . 2-22 2.7 Defining characteristics of z/OS . 2-23 2.8 Program products for z/OS . 2-24 2.9 Middleware for z/OS . 2-25 2.10 Interfaces for z/OS application programmers . 2-26 2.11 A brief comparison of z/OS and UNIX. 2-26 2.12 Summary . 2-29 2.13 Questions for review . 2-30 2.14 Topics for further discussion . 2-31 Chapter 3. TSO/E, ISPF, and UNIX: Interactive facilities of z/OS . 3-1 3.1 How do we interact with z/OS? . 3-2 3.2 TSO overview . 3-2 3.2.1 Using TSO commands in native mode . 3-3 3.2.2 Using CLISTs and REXX under TSO . 3-6 3.3 ISPF overview . 3-6 3.3.1 Keyboard mapping used in this course . 3-12 3.3.2 Using PF1-HELP and the ISPF tutorial . 3-13 3.3.3 Navigating through ISPF menus . 3-14 3.3.4 Using the ISPF editor . 3-17 3.3.5 Using the online help. 3-18 iv z/OS Basics 3.3.6 Customizing your ISPF settings . 3-20 3.3.7 Adding a GUI to ISPF . 3-23 3.4 z/OS UNIX interactive interfaces. 3-24 3.4.1 ISHELL command (ish) . 3-26 3.4.2 ISHELL - user files and directories . 3-26 3.4.3 OMVS command shell session . 3-27 3.4.4 Direct login to the shell . 3-28 3.5 Summary . 3-30 3.6 Questions for review . 3-31 3.7 Exercises. 3-32 3.7.1 Logging on to z/OS and entering TSO commands . 3-32 3.7.2 Navigating through the ISPF menu options . 3-32 3.7.3 Using the ISPF editor . 3-33 3.7.4 Using SDSF . 3-34 3.7.5 Opening the z/OS UNIX shell and entering commands . 3-35 3.7.6 Using the OEDIT and OBROWSE commands . ..
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]
  • 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]
  • 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]
  • Implementing REXX Support in SDSF
    Front cover Implementing REXX Support in SDSF Harness the power of SDSF with the versatility of REXX Write powerful REXX code to manage your environment Access SDSF outside of your mainframe Lydia Parziale Ludvik Drobnic Dario Facchinetti Richard Levey Amy Miu ibm.com/redbooks International Technical Support Organization Implementing REXX Support in SDSF June 2007 SG24-7419-00 Note: Before using this information and the product it supports, read the information in “Notices” on page xi. First Edition (June 2007) This edition applies to z/OS Release 1 Version 9 with APAR PK43448 Note: This book is based on a pre-GA version of a product and might not apply when the product becomes generally available. We recommend that you consult the product documentation or follow-on versions of this book for more current information. © Copyright International Business Machines Corporation 2007. 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 Figures . ix Notices . xi Trademarks . xii Preface . xiii The team that wrote this book . xiv Become a published author . xv Comments welcome. xvi Introduction and overview. 1 The REXX with SDSF interface . 2 Telling SDSF to execute commands . 4 Panel display commands . 5 New capabilities of REXX with SDSF in z/OS V1.9 . 11 SDSF programming practices . 13 Host environment verses interactive environment . 13 Recommendations . 14 Tune the command processing. 16 Areas to consider . 16 Debugging tools . 17 VERBOSE parameter . 17 SDSF trace . 17 Running REXX executables . 21 TSO/E address spaces . 21 Batch non TSO/E address spaces .
    [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]
  • High Level Assembler for Z/OS & Z/VM & Z/VSE: Programmer's Guide
    High Level Assembler for z/OS & z/VM & z/VSE Programmer's Guide Version 1 Release 6 SC26-4941-06 Note Before using this information and the product it supports, be sure to read the general information under “Notices” on page 397. This edition applies to IBM High Level Assembler for z/OS & z/VM & z/VSE, Release 6, Program Number 5696-234 and to any subsequent releases until otherwise indicated in new editions. Make sure that you are using the correct edition for the level of the product. Order publications through your IBM representative or the IBM branch office serving your locality. IBM welcomes your comments. For information on how to send comments, see “How to send your comments to IBM” on page xix. © Copyright IBM Corporation 1992, 2013. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Figures ...............ix *PROCESS statement options .......37 Default options ............37 Tables ...............xi Invoking the assembler dynamically .....37 Coding rules .............37 Assembler options ............38 About this document ........xiii ADATA...............39 Who should use this document .......xiii ALIGN ...............39 Programming interface information ......xiii ASA (z/OS and CMS) ..........40 Organization of this document........xiii BATCH...............40 High Level Assembler documents .......xv CODEPAGE .............41 Documents .............xv COMPAT ..............42 Collection kits ............xvi DBCS ...............43 Related publications ...........xvi DECK ...............43 Syntax notation .............xvi DISK (CMS) .............44 DXREF ...............44 How to send your comments to IBM xix ERASE (CMS) ............45 If you have a technical problem .......xix ESD................45 EXIT................46 Summary of changes ........xxi FLAG ...............48 FOLD ...............51 Chapter 1.
    [Show full text]
  • The FORTRAN Automatic Coding System J
    The FORTRAN Automatic Coding System J. W. BACKUS?, R. J. BEEBERt, S. BEST$, R. GOLDBERG?, L. M. HAIBTt, H. L. HERRICK?, R. A. NELSON?, D. SAYRE?, P. B. SHERIDAN?, H.STERNt, I. ZILLERt, R. A. HUGHES§, AN^.. .R. NUTT~~ system is now copplete. It has two components: the HE FORTRAN project was begun in the sum- FORTRAN language, in which programs are written, mer of 1954. Its purpose was to reduce by a large and the translator or executive routine for the 704 factor the task of preparing scientific problems for which effects the translation of FORTRAN language IBM's next large computer, the 704. If it were possible programs into 704 programs. Descriptions of the FOR- for the 704 to code problems for itself and produce as TRAN language and the translator form the principal good programs as human coders (but without the sections of this paper. errors), it was clear that large benefits could be achieved. The experience of the FORTRAN group in using the For it was known that about two-thirds of the cost of system has confirmed the original expectations con- cerning reduction of the task of problem preparation solving most scientific and engineering problems on 1 large computers was that of problem preparation. and the efficiency of output programs. A brief case Furthermore, more than 90 per cent of the elapsed time history of one job done with a system seldom gives a for a problem was usually devoted to planning, writing, good measure of its usefulness, particularly when the and debugging the program.
    [Show full text]
  • Chapter Three Introduction to Computer Troubleshooting
    Chapter Three Introduction to Computer Troubleshooting Welcome to the Machine Introduction to Computer Troubleshooting What are the three steps in the computer troubleshooting process? What do you do if the three steps does not solve your problem? DON’T PANIC!” When things go wrong remain calm, as most computer problems are a simple fix. Even if it is the rare serious problem, usually your data is still there waiting for you. The computer troubleshooting process at its most basic is gathering information about what is going on, drawing conclusions about the information gathered, and acting on those conclusions to solve the problem. If that does not solve the problem, then we return to the gathering information stage and go through the steps again. You might think of it as a loop which we exit when the problem is solved. At the top of the paragraph, I said that most computer problems are a simple fix and I would like you to keep that in mind as we go through this chapter. Important Words in this Chapter Cables Memory Simple-to-Complex Connectors Monitor Surge Protector CPU Motherboard System HD (Hard Drive) NIC (Network Card) Troubleshooting Input Devices Power Supply Video Card Main Troubleshooting Principle What is the principle on which we base all efficient and effective troubleshooting? All efficient and effective troubleshooting is based on the principle of proceeding from the simple-to-the- complex. Why is this true? Starting with complex items first, can cause you to draw the wrong conclusions. The complex parts of a computer depend on the simpler things.
    [Show full text]
  • NBS FORTRAN Test Programs 3^1 No "I Volume 1- Documentation for Versions 1 and 3 V.I
    j I i Vt NBS SPECIAL PUBLICATION 399 J Volume 1 U.S. DEPARTMENT OF COMMERCE / National Bureau of Standards] National Bureau of Standards Library, £-01 Admin. BIdg. ncT 1 1981 13102^1 NBS FORTRAN Test Prog Volume 1-Documentation for Versions 1 and 3 NATIONAL BUREAU OF STANDARDS The National Bureau of Standards^ was established by an act of Congress March 3, 1901. The Bureau's overall goal is to strengthen and advance the Nation's science and technology and facilitate their effective application for public benefit. To this end, the Bureau conducts research and provides: (1) a basis for the Nation's physical measurement system, (2) scientific and technological services for industry and government, (3) a technical basis for equity in trade, and (4) technical services to promote public safety. The Bureau consists of the Institute for Basic Standards, the Institute for Materials Research, the Institute for Applied Technology, the Institute for Computer Sciences and Technology, and the Office for Information Programs. THE INSTITUTE FOR BASIC STANDARI>S provides the central basis within the United States of a complete and consistent system of physical measurement; coordinates that system with measurement systems of other nations; and furnishes essential services leading to accurate and uniform physical measurements throughout the Nation's scientific community, industry, and commerce. The Institute consists of a Center for Radiation Research, an Office of Meas- urement Services and the following divisions: Applied Mathematics — Electricity — Mechanics
    [Show 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 .
    [Show full text]
  • 2 9215FQ14 FREQUENTLY ASKED QUESTIONS Category Pages Facilities & Buildings 3-10 General Reference 11-20 Human Resources
    2 FREQUENTLY ASKED QUESTIONS Category Pages Facilities & Buildings 3-10 General Reference 11-20 Human Resources 21-22 Legal 23-25 Marketing 26 Personal Names (Individuals) 27 Predecessor Companies 28-29 Products & Services 30-89 Public Relations 90 Research 91-97 April 10, 2007 9215FQ14 3 Facilities & Buildings Q. When did IBM first open its offices in my town? A. While it is not possible for us to provide such information for each and every office facility throughout the world, the following listing provides the date IBM offices were established in more than 300 U.S. and international locations: Adelaide, Australia 1914 Akron, Ohio 1917 Albany, New York 1919 Albuquerque, New Mexico 1940 Alexandria, Egypt 1934 Algiers, Algeria 1932 Altoona, Pennsylvania 1915 Amsterdam, Netherlands 1914 Anchorage, Alaska 1947 Ankara, Turkey 1935 Asheville, North Carolina 1946 Asuncion, Paraguay 1941 Athens, Greece 1935 Atlanta, Georgia 1914 Aurora, Illinois 1946 Austin, Texas 1937 Baghdad, Iraq 1947 Baltimore, Maryland 1915 Bangor, Maine 1946 Barcelona, Spain 1923 Barranquilla, Colombia 1946 Baton Rouge, Louisiana 1938 Beaumont, Texas 1946 Belgrade, Yugoslavia 1926 Belo Horizonte, Brazil 1934 Bergen, Norway 1946 Berlin, Germany 1914 (prior to) Bethlehem, Pennsylvania 1938 Beyrouth, Lebanon 1947 Bilbao, Spain 1946 Birmingham, Alabama 1919 Birmingham, England 1930 Bogota, Colombia 1931 Boise, Idaho 1948 Bordeaux, France 1932 Boston, Massachusetts 1914 Brantford, Ontario 1947 Bremen, Germany 1938 9215FQ14 4 Bridgeport, Connecticut 1919 Brisbane, Australia
    [Show full text]