Basic of Mainframe

Total Page:16

File Type:pdf, Size:1020Kb

Basic of Mainframe Basic of Mainframe 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. Software upgrades are only non-disruptive when Parallel Sysplex is in place, with true workload sharing, so one system can take over another's application, while it is being refreshed. More recently, there are several IBM mainframe installations that have delivered over a decade of continuous business service as of 2007, with hardware upgrades not interrupting service. Mainframes are defined by high availability, one of the main reasons for their longevity, because they are typically used in applications where downtime would be costly or catastrophic. The term Reliability, Availability and Serviceability (RAS) is a defining characteristic of mainframe computers. Proper planning (and implementation) is required to exploit these features. In the 1960s, most mainframes had no interactive interface. They accepted sets of punch cards, paper tape, and/or magnetic tape and operated solely in batch mode to support back office functions, such as customer billing. Teletype devices were also common, at least for system operators. By the early 1970s, many mainframes acquired interactive user interfaces and operated as timesharing computers, supporting hundreds or thousands of users simultaneously along with batch processing. Users gained access through specialized terminals or, later, from personal computers equipped with terminal emulation software. Many mainframes supported graphical terminals (and terminal emulation) by the 1980s. Nowadays most mainframes have partially or entirely phased out classic terminal access for end-users in favor of Web user interfaces. Developers and operational staff typically continue to use terminals or terminal emulators. Historically, mainframes acquired their name in part because of their substantial size, and because of requirements for specialized heating, ventilation, and (air conditioning HVAC), and electrical power. Those requirements ended by the mid-1990s with CMOS mainframe designs replacing the older bipolar technology. In a major reversal, IBM now touts its newer mainframes' www.pankajkumarjha.com ability to reduce data center energy costs for power and cooling, and the reduced physical space requirements compared to server farms. Characteristics of mainframes Nearly all mainframes have the ability to run (or host) multiple operating systems, and thereby operate not as a single computer but as a number of virtual machines. In this role, a single mainframe can replace dozens or even hundreds of smaller servers. While mainframes pioneered this capability, virtualization is now available on most families of computer systems, though not to the same degree or level of sophistication. The distinction between supercomputers and mainframes is not a hard and fast one, but supercomputers generally focus on problems which are limited by calculation speed while mainframes focus on problems which are limited by input/output and reliability ("throughput computing") and on solving multiple business problems concurrently (mixed workload). The mainframe is the backbone of many industries that are the lifeblood of the global economy. More mainframe processing power is being shipped now than has ever been shipped. Businesses that require unparalleled security, availability, and reliability for their applications depend on mainframe. Mainframes were designed initially for high-volume business transactions and, for more than 40 years, have been continually enhanced to meet the challenges of business data processing. No computing platform can handle a diversity of workloads better than a mainframe. But aren't "insert-your-favorite-alternative-platform" computers cheaper/faster/easier to operate? The answer is: It all depends. A student who is composing his term paper does not have the same information needs as a bank that needs to handle millions of transactions each day, especially because the bank also needs to be able to pass security and accounting audits to verify that each account has the correct balance. Mainframes aren't for every computing task. Businesses opt for mainframes and mainframe operating systems when they have large volumes of data, large transaction volumes, large data transfer requirements, a need for an extremely reliable system, or many differing types of workloads that would operate best if they were located on the same computer. Mainframes excel in these types of environments. Mainframe Computers Mainframes are computers used mainly by large organizations for critical applications, typically bulk data processing such as census, industry and consumer statistics, ERP, and financial transaction processing. The term probably had originated from the early mainframes, as they were housed in enormous, room-sized metal boxes or frames. Later the term was used to distinguish high-end commercial www.pankajkumarjha.com machines from less powerful units. Today in practice, the term usually refers to computers compatible with the IBM System/360 line, first introduced in 1965. (IBM System z10 is the latest incarnation.) Otherwise, large systems that are not based on the System/360 are referred to as either "servers" or "supercomputers". However, "server", "supercomputer" and "mainframe" are not synonymous (see client-server). Some non-System/360-compatible systems derived from or compatible with older (pre-Web) server technology may also be considered mainframes. These include the Burroughs large systems, the UNIVAC 1100/2200 series systems, and the pre-System/360 IBM 700/7000 series. Most large-scale computer system architectures were firmly established in the 1960s and most large computers were based on architecture established during that era up until the advent of Web servers in the 1990s. There were several minicomputer operating systems and architectures that arose in the 1970s and 1980s, but minicomputers are generally not considered mainframes.Many defining characteristics of "mainframe" were established in the 1960s, but those characteristics continue to expand and evolve to the present day. Characteristics of Mainframe Computers Nearly all mainframes have the ability to run (or host) multiple operating systems, and thereby operate not as a single computer but as a number of virtual machines. In this role, a single mainframe can replace dozens or even hundreds of smaller servers. While mainframes pioneered this capability, virtualization is now available on most families of computer systems, though not to the same degree or level of sophistication. Mainframes can add or hot swap system capacity non disruptively and granularly, again to a level of sophistication not found on most servers. Modern mainframes, notably the IBM zSeries, System z9 and System z10 servers, offer three levels of virtualization: logical partitions (LPARs, via the PR/SM facility), virtual machines (via the z/VM operating system), and through its operating systems (notably z/OS with its key-protected address spaces and sophisticated goal- oriented workload scheduling, but also Linux, OpenSolaris and Java). This virtualization is so thorough, so well established, and so reliable that most IBM mainframe customers run no more than two machines one in their primary data center, and one in their backup data center²fully active, partially active, or on standby²in case there is a catastrophe affecting the first building. All test, development, training, and production workload for all applications and all databases can run on a single machine, except for extremely large demands where the capacity of one machine might be limiting. Such a two-mainframe installation can support continuous business service, avoiding both planned and unplanned outages. Mainframes are designed to handle very high volume input and output (I/O) and emphasize throughput computing. Since the mid-1960s, mainframe designs have included several subsidiary computers (called channels or peripheral processors) which manage the I/O devices, leaving the CPU free to deal only with high-speed memory. It is common in mainframe shops to deal with massive databases and files. Giga-record or tera-record files are not unusual. Compared to a www.pankajkumarjha.com typical PC, mainframes commonly have hundreds to thousands of times as much data storage online, and can access it much faster. While some other server families also offload certain I/O processing and emphasize throughput computing, they do not do so to
Recommended publications
  • 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]
  • DB2 V8 Exploitation of IBM Ziip
    Systems & Technology Group Connecting the Dots: LPARs, HiperDispatch, zIIPs and zAAPs Share in Boston,v August 2010 Glenn Anderson IBM Technical Training [email protected] © 2010 IBM Corporation What I hope to cover...... What are dispatchable units of work on z/OS Understanding Enclave SRBs How WLM manages dispatchable units of work The role of HiperDispatch What makes work eligible for zIIP and zAAP specialty engines Dispatching work to zIIP and zAAP engines z/OS Dispatchable Units There are different types of Dispatchable Units (DU's) in z/OS Preemptible Task (TCB) Non Preemptible Service Request (SRB) Preemptible Enclave Service Request (enclave SRB) Independent Dependent Workdependent z/OS Dispatching Work Enclave Services: A Dispatching Unit Standard dispatching dispatchable units (DUs) are the TCB and the SRB TCB runs at dispatching priority of address space and is pre-emptible SRB runs at supervisory priority and is non-pre-emptible Advanced dispatching units Enclave Anchor for an address space-independent transaction managed by WLM Can comprise multiple DUs (TCBs and Enclave SRBs) executing across multiple address spaces Enclave SRB Created and executed like an ordinary SRB but runs with Enclave dispatching priority and is pre-emptible Enclave Services enable a workload manager to create and control enclaves Enclave Characteristics Created by an address space (the "owner") SYS1 AS1 AS2 AS3 One address space can own many enclaves One enclave can include multiple Enclave dispatchable units (SRBs/tasks) executing concurrently in
    [Show full text]
  • IBM System Z10 Business Class - the Smart Choice for Your Business
    IBM United States Hardware Announcement 108-754, dated October 21, 2008 IBM System z10 Business Class - The smart choice for your business. z can do IT better Table of contents 4 Key prerequisites 36 Publications 4 Planned availability dates 38 Services 5 Description 38 Technical information 35 Product positioning 55 IBM Electronic Services 36 Statement of general direction 55 Terms and conditions 36 Product number 57 Pricing 36 Education support 57 Order now 58 Corrections At a glance The IBM® System z10 BC is a world-class enterprise server built on the inherent strengths of the IBM System z® platform. It is designed to deliver new technologies and virtualization that provide improvements in price/performance for key new workloads. The System z10 BC further extends System z leadership in key capabilities with the delivery of granular growth options, business-class consolidation, improved security and availability to reduce risk, and just-in-time capacity deployment helping to respond to changing business requirements. Whether you want to deploy new applications quickly, grow your business without growing IT costs, or consolidate your infrastructure for reduced complexity, look no further - z Can Do IT. The System z10 BC delivers: • The IBM z10 Enterprise Quad Core processor chip running at 3.5 GHz, designed to help improve CPU intensive workloads. • A single model E10 offering increased granularity and scalability with 130 available capacity settings. • Up to a 5-way general purpose processor and up to 5 additional Specialty Engine processors or up to a 10-way IFL or ICF server for increased levels of performance and scalability to help enable new business growth.
    [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]
  • IBM Z Open Automation Utilities Provides New Services to Help Developers Work with IBM Z/OS Data Sets Directly from the Shell, Java, Or Python
    IBM United States Software Announcement 220-087, dated February 18, 2020 IBM Z Open Automation Utilities provides new services to help developers work with IBM z/OS data sets directly from the shell, Java, or Python Table of contents 1 Overview 3 Technical information 2 Key requirements 3 Ordering information 2 Planned availability date 5 Terms and conditions 2 Program number 9 Prices 2 Publications 9 Order now At a glance IBM Z(R) Open Automation Utilities helps z/OS(R) developers to automate tasks that access z/OS resources. It enables easier calling of z/OS utilities compared with JCL by providing a natural coding experience on UNIX System Services (USS) and interfaces in modern programming languages. Overview Job Control Language (JCL) has been used for a long time for performing or automating a set of steps on the IBM(R) z/OS operating system. Though JCL has evolved with the times, it is inevitably foreign to people familiar with environments such as Linux(R), UNIX, and Microsoft Windows. On z/OS, as an alternative to using JCL, developers can write scripts to automate tasks in the USS environment. Such scripts are easier to understand and to manage, and many open source tools are also available in USS. However, there is a gap in some cases, and z/OS developers have to fall back to submitting JCL jobs, which requires z/OS specific knowledge. In addition, JCL jobs are asynchronous, which means you must submit them to batch and wait for the result; thus, they do not fit in well with the rest of the script, which is typically synchronous.
    [Show full text]
  • 9228 Brown/JCL 01.K.Qxd 5/1/02 11:39 AM Page 1
    9228 Brown/JCL 01.k.qxd 5/1/02 11:39 AM Page 1 CHAPTER 1 INTRODUCTION 1.1 THE SHOCK OF JCL Your first use of JCL (Job Control Language) will be a shock. No doubt you have used personal computers costing $500 or $1,000 that had wonderfully human-engineered software, giving you an expectation of how easy it is to use a computer. Now, as you use a computer costing several million dollars, you may feel like a waif in a Dickens story standing in the shadow of a mas- sive mainframe computer saying meekly, “Please, sir, may I run my job?” It will come as a shock that its software is not wonderfully human engi- neered. The hardware and software design of large IBM mainframe computers date back to the days when Kennedy was president. JCL is a language that may be older than you are. It was designed at a time when user-friendliness was not even a gleam in the eye of its designers. This is easily demonstrated by taking the simple task of copying a file and contrasting how it is done through JCL with how it is done on the most popular personal computer system, Windows. To copy a file with Windows, you left-click twice on the MY COMPUTER icon, left-click on the C: drive icon, left-click twice on the folder containing the file, and right-click on the file to copy. On the resulting menu, you click on COPY and then left-click twice on the folder into which you want the file copied.
    [Show full text]
  • IDUG EU 2009 Patric Becker: Leveraging Data Warehouse
    Session: A01 Leveraging Data Warehouse Performance with DB2 9 for z/OS and System z10 Patric Becker IBM Boeblingen Lab 05 October 2009 • 11:30 – 12:30 Platform: DB2 for z/OS This session looks into new feature delivered with IBM System z10 as well as the new capabilities of DB2 9 for z/OS and highlights those options which can be beneficial for Data Warehousing environments in terms of availability and performance. Not all the relevant features can be described at a very granular level, but the idea is to provide information to understand the important features to trigger further analysis to improve the availability and performance of existing Data Warehouses. IBM Deutschland Research & Development GmbH IBM D Research & Development Headquarter IBM Deutschland Research & Development GmbH Schönaicher Straße 220 D-71032 Böblingen Berlin Managing Director Erich Baier Employees 2008 Approx. 1.800 (2.200) Homepage ibm.com/de/entwicklung Very strong development portfolio Mainz Globally integrated in hardware and software Walldorf development One of the biggest IBM R&D location world wide IBM Forschung & Böblingen Acknowledged innovation team Entwicklung ~ 310 patent submissions 2008 München ~ 400 students 2008 IND GmbH ~ 80 new-hires 2007 2 IBM Research & Development Locations worldwide Böblingen Greenock ▲ Yorktown Heights Toronto Hursley ▲ Peking Rochester Krakau Boulder Dublin Moskau Beaverton Paris Fujisawa ▲ Zürich ▲ Tokio Burlington Rom Yasu Yamato Endicott San Jose Shanghai ▲ Almaden East Fishkill Santa Teresa Poughkeepsie
    [Show full text]
  • 1. Types of Computers Contents
    1. Types of Computers Contents 1 Classes of computers 1 1.1 Classes by size ............................................. 1 1.1.1 Microcomputers (personal computers) ............................ 1 1.1.2 Minicomputers (midrange computers) ............................ 1 1.1.3 Mainframe computers ..................................... 1 1.1.4 Supercomputers ........................................ 1 1.2 Classes by function .......................................... 2 1.2.1 Servers ............................................ 2 1.2.2 Workstations ......................................... 2 1.2.3 Information appliances .................................... 2 1.2.4 Embedded computers ..................................... 2 1.3 See also ................................................ 2 1.4 References .............................................. 2 1.5 External links ............................................. 2 2 List of computer size categories 3 2.1 Supercomputers ............................................ 3 2.2 Mainframe computers ........................................ 3 2.3 Minicomputers ............................................ 3 2.4 Microcomputers ........................................... 3 2.5 Mobile computers ........................................... 3 2.6 Others ................................................. 4 2.7 Distinctive marks ........................................... 4 2.8 Categories ............................................... 4 2.9 See also ................................................ 4 2.10 References
    [Show full text]
  • IBM System Z10 Capacity on Demand
    Front cover IBM System z10 Capacity on Demand Describes the concepts and structure of Capacity on Demand Explains the offerings and how they can be applied Provides step-by-step examples Marian Gasparovic Greg Chambers Ivan Dobos Per Fremstad Torsten Gutenberger Damian Ortega Lumbreras Rolf Mueller Karl-Erik Stenfors Yi Li Zhou ibm.com/redbooks International Technical Support Organization IBM System z10 Capacity on Demand January 2009 SG24-7504-01 Note: Before using this information and the product it supports, read the information in “Notices” on page vii. Second Edition (January 2009) This edition applies to the IBM System z10 servers. © Copyright International Business Machines Corporation 2008, 2009. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Notices . vii Trademarks . viii Preface . ix The team that wrote this book . ix Become a published author . xi Comments welcome. xi Chapter 1. Overview . 1 1.1 System upgrades . 2 1.2 Capacity on Demand on the System z10 . 3 1.3 Provisioning architecture. 7 1.4 z/OS Capacity Provisioning. 11 1.5 Terminology . 14 Chapter 2. Understanding the Capacity on Demand environment . 17 2.1 Capacity on Demand upgrades. 18 2.1.1 On-line Permanent Upgrade . 20 2.1.2 Capacity Backup . 20 2.1.3 Capacity for Planned Events. 26 2.1.4 On/Off Capacity on Demand. 27 2.2 Multiple activations . 35 2.2.1 Multiple active temporary offerings . 35 2.2.2 Permanent upgrade with temporary offerings active. 39 2.2.3 Subcapacity activation .
    [Show full text]
  • Unisys IBM Mainframe Security - Part 2
    ProTech Professional Technical Services, Inc. Unisys IBM Mainframe Security - Part 2 Course Summary Description This course is intended for individuals who need an initial, introductory understanding of IBM's mainframe operating system z/OS and the mainframe security software product Resource Access Control Facility (RACF). It is specifically designed to give attendees a solid foundation in z/OS and RACF without overloading them with advanced technical topics, yet it also serves as the ideal springboard for acquiring Course Outline Course further skills and knowledge. Attendees will gain a fundamental understanding of the components and functions of z/OS and RACF. Objectives After taking this course, students will be able to understand: What z/OS is and what functions it performs The software components of z/OS How to use TSO and ISPF Coding and submitting batch jobs What RACF is and what functions it performs The contents of each type of RACF profile What groups are and how they are used Protecting datasets and general resources How RACF decides whether to grant access Topics Introduction to z/OS Groups Time Sharing Option (TSO) Resource Protection Batch Job Control Language (JCL) Datasets Introduction to RACF General Resources Users RACF Administration Audience This course is designed for anyone requiring general, introductory knowledge of z/OS and RACF. Including; Entry-level security administrators Compliance staff Non-mainframe IT security administrators IT Auditors IT Security Supervisors Prerequisites There are no prerequisites for this course. Duration Two days Due to the nature of this material, this document refers to numerous hardware and software products by their trade names.
    [Show full text]
  • White Pape Product Review
    productwhite pape reviewr Micro Focus Studio Enterprise Edition Test Server Micro Focus Studio Enterprise Edition™ Test Server (Test Server) is a testing suite that supports pre-production testing of mainframe applications on commodity Windows platforms before they are deployed back to the mainframe for production use. PRODUCT REVIEW | Micro Focus Studio Enterprise Edition Test Server OVERVIEW Micro Focus Test Server is a fast, scalable testing environment that enables organizations to perform substantial pre- production testing of IBM mainframe applications on more cost effective Windows servers, while still deploying these back to the mainframe for final system test and release into production. Test Server is a multi-tasking, multi-user transactional and batch testing platform that supports IBM COBOL, IBM Assembler, IBM CICS, IBM IMS (TM and DB) and IBM JCL, IBM DB2, IBM z/OS file formats and SORT utilities on Windows. This means that substantial and complex mainframe applications can be comprehensively tested under Test Server without being constrained by the availability of mainframe resources. Test Server is supplied with the development tools required to compile or assemble mainframe programs as well as data access tools to support the creation or modification of vital test data. It can also be configured so that code and data can, where logical, continue to reside on the mainframe and be executed remotely from the Test Server platform. BENEFITS Complete testing phases faster and with high quality as test cycles are not constrained
    [Show full text]
  • Job Control Language
    JCL Job Control Language im z/OS-Umfeld praktisch anwenden von: Markus Karl Scheibe Informatik-/Betriebswirt (VWA) Nachtigalstr. 10 30173 Hannover Tel.: 0173/6181348 1 Inhaltsverzeichnis 1. Einleitung………………………………………………………………………………….9 1.1. Verarbeitungsmethoden………………………………………………………...….9 1.2. Was ist ein (MVS-)Betriebssystem………………………………………………..9 1.3. Der Katalogeintrag………………………………………………………...………10 1.4. Was ist JCL?..................................................................................................11 1.5. JCL im Vergleich zu anderen Programmiersprachen………………………….11 2. Job-Aufbau………………………………………………………………………………13 2.1. Job-Spezifikation…………………………………………………………………..13 2.2. Arbeitsabläufe……………………………………………………………………...13 2.3. Arbeitsmittel………………………………………………………………………...14 2.4. Der erste Job……………………………………………………………………….15 2.5. Umfeld der JCL…………………………………………………………………….17 2.6. Job Entry Subsystem……………………………………………………………...17 3. JCL in der Praxis………………………………………………………………………..18 3.1. Stepabfolge…………………………………………………………………………18 3.2. DSNAME……………………………………………………………………………18 3.3. DISP…………………………………………………………………………………22 3.3.1. Status………………………………………………………………………...23 3.3.1.1. NEW………………………………………………………………….23 3.3.1.2. OLD…………………………………………………………………..23 3.3.1.3. SHR…………………………………………………………………..23 3.3.1.4. MOD………………………………………………………………….23 3.3.2. Normal Termination………………………………………………………...24 3.3.2.1. DELETE……………………………………………………………..24 3.3.2.2. KEEP…………………………………………………………………24 3.3.2.3. PASS…………………………………………………………………24 3.3.2.4. CATLG……………………………………………………………….24 3.3.2.5.
    [Show full text]