Seminar Zum Mainframe Summit
Total Page:16
File Type:pdf, Size:1020Kb
Load more
Recommended publications
-
Oracle Database Gateway for Adabas User's Guide, 11G Release 2 (11.2) E12074-01
Oracle® Database Gateway for Adabas User’s Guide 11g Release 2 (11.2) E12074-01 July 2009 Oracle Database Gateway for Adabas User's Guide, 11g Release 2 (11.2) E12074-01 Copyright © 2008, 2009, Oracle and/or its affiliates. All rights reserved. Primary Author: Jeanne Wiegelmann Contributing Author: Maitreyee Chaliha, Sami Zeitoun, Oussama Mkaabal Contributor: Vira Goorah, Peter Wong This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). -
The Operating System Handbook Or, Fake Your Way Through Minis and Mainframes
The Operating System Handbook or, Fake Your Way Through Minis and Mainframes by Bob DuCharme MVS Table of Contents Chapter 22 MVS: An Introduction.................................................................................... 22.1 Batch Jobs..................................................................................................................1 22.2 Interacting with MVS................................................................................................3 22.2.1 TSO.........................................................................................................................3 22.2.2 ISPF........................................................................................................................3 22.2.3 CICS........................................................................................................................4 22.2.4 Other MVS Components.........................................................................................4 22.3 History........................................................................................................................5 Chapter 23 Getting Started with MVS............................................................................... 23.1 Starting Up.................................................................................................................6 23.1.1 VTAM.....................................................................................................................6 23.1.2 Logging On.............................................................................................................6 -
Paper Mainframe
Club des Responsables d’Infrastructures et de Production IT Infrastructure and Operations IT INFRAsTRucTuRE & Operations MANAgEMENT Best Practices PAPER MAINFRAME IBM zSeries Mainframe Cost Control te i Authors Laurent Buscaylet, Frédéric Didier Bernard Dietisheim, Bruno Koch, Fabrice Vallet sponsored by september 2012 Wh PAgE 2 table of contents INTRODucTION 5 1. “z” POsITIONINg AND Strategy wIThIN A Company 6 1.1 Role of the Mainframe in the eyes of cRIP’s Members 6 1.2 The Position of system z vs. Distributed systems (windows, uNIX, Linux) 6 1.3 system z - Banking/Finance/Insurance vs. general Industry sectors 7 1.4 Evolution strategies for system z 9 2. z Platform OVERVIEw 11 2.1 Technical terms of reference 11 2.1.1 Servers 11 2.1.2 SAN & Networks 12 2.1.3 Storage 13 2.1.4 Backups 15 2.1.5 technical Architecture & Organization 16 2.1.6 Business Continuity 19 2.2 Mainframe software vendors (IsV’s) analysis & positioning 20 2.2.1 the Main Suppliers (ISV’s) 22 2.2.2 the Secondary Suppliers (ISV’s) 22 2.3 survey Results 3. z PLATFORM cOsT cONTROL 28 3.1 controling software cost 28 3.1.1 IBM Contractual Arrangements 28 3.1.2 ISV negotiation strategies: holistic/generic or piecemeal/ad-hoc 31 3.1.3 ISV contractual arrangements: licensing modes & billing 35 3.1.4 MLC: Controlling the billing level 38 3.1.4.1 The IBM billing method 38 3.1.4.2 The problem of smoothing (consolidating) peak loads 41 3.1.4.3 The methods and controls for controlling the software invoice 42 3.1.4.4 Survey feedback and recommendations 43 3.1.4.5 Other Cost Saving Options 48 3.2 Infrastructure cost Reduction 50 3.2.1 Grouping and Sharing Infrastructure 50 3.2.2 Use of specialty engines: zIIP, zAAP, IFL 54 3.3 controlling operational costs 55 3.3.1 Optimization, performance & technical/application component quality 55 3.3.2 Capacity Management, tools & methods 58 4. -
IBM System Z Functional Matrix
IBM System z July 2013 IBM System z Functional Matrix IBM System z This functional matrix consists of a list of features and functions that are supported on IBM System z® servers (this includes the IBM zEnterprise ® EC12 (zEC12), IBM zEnterprise BC12 (zBC12), IBM zEnterprise 196 (z196), IBM zEnterprise 114 (z114), IBM System z10 ® Enterprise Class (z10 ™ EC), IBM System z10 Business Class ™ (z10 BC), IBM System z9 ® Enterprise Class (z9 ® EC), and IBM System z9 Business Class (z9 BC). It is divided into nine functional areas; – Application Programming Interfaces, – Cryptographic features, – I/O, – Business On Demand, – Parallel Sysplex ®, – Performance, – Processor Resource Systems Manager (PR/SM ™) – Reliability, Availability, Serviceability (RAS) – IBM zEnterprise BladeCenter ® Extension (zBX) There is also a legend at the end of the matrix to identify the symbols that are being used. Note: This matrix is not intended to include services, RPQs or specific quantities or measurements related performance, memory size, bandwidth, etc. The intention of this matrix is to provide a comparison of the standard and optional features for the various System z servers. For further details on the features and functions listed in the tables, refer to the system specific reference guide documentation. This document is available from the Library area of Resource Link ™ at: www.ibm.com/servers/resourcelink Key: S = standard O = optional - = not supported zEnterprise System z10 System z9 ™ Application Programming Interface (API) ™ zEC12 zBC12 z196 z114 -
Big Blue in the Bottomless Pit: the Early Years of IBM Chile
Big Blue in the Bottomless Pit: The Early Years of IBM Chile Eden Medina Indiana University In examining the history of IBM in Chile, this article asks how IBM came to dominate Chile’s computer market and, to address this question, emphasizes the importance of studying both IBM corporate strategy and Chilean national history. The article also examines how IBM reproduced its corporate culture in Latin America and used it to accommodate the region’s political and economic changes. Thomas J. Watson Jr. was skeptical when he The history of IBM has been documented first heard his father’s plan to create an from a number of perspectives. Former em- international subsidiary. ‘‘We had endless ployees, management experts, journalists, and opportunityandlittleriskintheUS,’’he historians of business, technology, and com- wrote, ‘‘while it was hard to imagine us getting puting have all made important contributions anywhere abroad. Latin America, for example to our understanding of IBM’s past.3 Some seemed like a bottomless pit.’’1 However, the works have explored company operations senior Watson had a different sense of the outside the US in detail.4 However, most of potential for profit within the world market these studies do not address company activi- and believed that one day IBM’s sales abroad ties in regions of the developing world, such as would surpass its growing domestic business. Latin America.5 Chile, a slender South Amer- In 1949, he created the IBM World Trade ican country bordered by the Pacific Ocean on Corporation to coordinate the company’s one side and the Andean cordillera on the activities outside the US and appointed his other, offers a rich site for studying IBM younger son, Arthur K. -
The Advent of Recursion in Programming, 1950S-1960S
The Advent of Recursion in Programming, 1950s-1960s Edgar G. Daylight?? Institute of Logic, Language, and Computation, University of Amsterdam, The Netherlands [email protected] Abstract. The term `recursive' has had different meanings during the past two centuries among various communities of scholars. Its historical epistemology has already been described by Soare (1996) with respect to the mathematicians, logicians, and recursive-function theorists. The computer practitioners, on the other hand, are discussed in this paper by focusing on the definition and implementation of the ALGOL60 program- ming language. Recursion entered ALGOL60 in two novel ways: (i) syn- tactically with what we now call BNF notation, and (ii) dynamically by means of the recursive procedure. As is shown, both (i) and (ii) were in- troduced by linguistically-inclined programmers who were not versed in logic and who, rather unconventionally, abstracted away from the down- to-earth practicalities of their computing machines. By the end of the 1960s, some computer practitioners had become aware of the theoreti- cal insignificance of the recursive procedure in terms of computability, though without relying on recursive-function theory. The presented re- sults help us to better understand the technological ancestry of modern- day computer science, in the hope that contemporary researchers can more easily build upon its past. Keywords: recursion, recursive procedure, computability, syntax, BNF, ALGOL, logic, recursive-function theory 1 Introduction In his paper, Computability and Recursion [41], Soare explained the origin of computability, the origin of recursion, and how both concepts were brought to- gether in the 1930s by G¨odel, Church, Kleene, Turing, and others. -
IBM Global Services: a Brief History
IBM Global Services: A Brief History IBM Corporate Archives May 2002 2405SH01 2 OVERVIEW Background In 1991 IBM was a $64.8 billion company, of which less than $6 billion was derived from non-maintenance services. Ten short years later, the business of information technology (IT) services alone generated more than 40 percent of IBM’s $86 billion in sales and had become the single largest source of revenue in IBM’s portfolio. How did that happen? It was partly the result of old-fashioned hard work and serious commitment: growing customer by customer; building disciplined management and financial systems; and investing to hire and train experts in everything from IT consulting to systems architecture and Web services. IBM used its financial strength to fund the expensive push into outsourcing, and the company placed informed bets on the future in areas such as IT utility services (“e-business on demand”) and hosted storage. But most important, the success of IBM Global Services came from something very simple: a clear understanding of customers’ needs. IBM saw that technology and business were converging to create something new and challenging for every kind of enterprise. And IBM had the deep experience in both areas to help its customers bring them together most effectively. The following pages offer a brief look at the history and growth of the organization that is today IBM’s top revenue generator. Definitions What are “services?” In the IT world, that broad term has encompassed dozens of offerings and meanings, including consulting, custom programming, systems integration (designing, building and installing complex information systems), systems operations (in which a vendor runs part or all of a company’s information systems), business innovation services (such as supply chain management), strategic outsourcing, application management services, integrated technology services (such as business recovery), networking services, learning services, security services, storage services and wireless services. -
IBM System Z9 Enterprise Class
The server built to help optimize your resources throughout the enterprise IBM System z9 Enterprise Class A “classic” might just be the best Today’s market finds that business needs are changing, and having a com petitive advantage isn’t always about having more or being bigger, but more about being smarter and responding faster to change and to your clients. Often, being reactive to change has led to infrastructures with mixed technolo gies, spread across an enterprise, that are complex and difficult to control and costly to manage. Integration of appli cations and data is limited and difficult. Using internal information to make insightful decisions for the company Highlights can be difficult because knowing you are using the “best” data—that which is ■ Strengthening the role of the ■ Continued improvement in most current and complete—may not mainframe as the data hub of IBM FICON® performance and be possible. the enterprise throughput In many situations, investments have ■ New versatile capacity settings ■ On demand innovative tech been made in disparate technologies designed to optimize capacity nologies to help meet ever- that may fall short of meeting their and cost changing business demands goals. Merging information from one branch to another may not be possible ■ IBM System z9™ Integrated and so company direction is set with Information Processor (IBM zIIP) is designed to improve resource optimization and lower the cost of eligible work only a portion of the data at hand, and help achieve advanced I/O function and But data management can be a big in a global economy that can really hurt. -
Ist Das Z/OS (Objekt-) Relationale Datenbank-Produkt
Betriebssysteme it-Akademie Bayern z/OS und OS/390 Lehrgang 2009 Prof. Dr.-Ing. Wilhelm G. Spruth Teil 9b z/OS Subsysteme bs 0901 ww6 © copyright W. G. Spruth, 10-2000 wgs 03-95 Server Zugriff Unterschied zwischen Einzelplatzrechner und Client/Server Betriebssystemen. NT und Unix werden für beides eingesetzt. OS/390 ist ein reinrassiges Server Betriebssystem. Andere Beispiele für Server Betriebssysteme: Tandem Pathway, DEC Vax. Ein Server Zugriff benötigt spezielle Client Software. Möglichkeiten für selbstgeschriebene Klient-Anwendungen: Sockets, RPC, Corba, DCOM, RMI Zeilenorientierte Klienten: Unix Server Telnet Client OS/390 Server 3270 Client Vax Server VT 100 Client Klienten mit graphischer Oberfläche: NT Server Citrix Client WWW Server Browser Client SAP R/3 Server SAPGUI Client OS/390 Server Servlet, Java Server Page Client Client Server NT OS/390 LAN oder Internet Jedi 3270 Client Telnet, TN3270 es 0537 ww6 wgs 07-00 Typical online use Typical online use 1. A customer uses an ATM, which presents a user- friendly interface for various functions: Withdrawal, query account balance, deposit, transfer, or cash advance from a credit card account. 2. Elsewhere in the same private network, a bank employee in a branch office performs operations such as consulting, fund applications, and money ordering. 3. At the bank’s central office, business analysts tune transactions for improved performance. Other staff use specialized online systems for office automation to perform customer relationship management, budget planning, and stock control. 4. All requests directed to the mainframe computer for processing. 5. Programs running on the mainframe computer perform updates and inquires to the database management system (for example, DB2). -
Lynn Conway Professor of Electrical Engineering and Computer Science, Emerita University of Michigan, Ann Arbor, MI 48109-2110 [email protected]
IBM-ACS: Reminiscences and Lessons Learned From a 1960’s Supercomputer Project * Lynn Conway Professor of Electrical Engineering and Computer Science, Emerita University of Michigan, Ann Arbor, MI 48109-2110 [email protected] Abstract. This paper contains reminiscences of my work as a young engineer at IBM- Advanced Computing Systems. I met my colleague Brian Randell during a particularly exciting time there – a time that shaped our later careers in very interesting ways. This paper reflects on those long-ago experiences and the many lessons learned back then. I’m hoping that other ACS veterans will share their memories with us too, and that together we can build ever-clearer images of those heady days. Keywords: IBM, Advanced Computing Systems, supercomputer, computer architecture, system design, project dynamics, design process design, multi-level simulation, superscalar, instruction level parallelism, multiple out-of-order dynamic instruction scheduling, Xerox Palo Alto Research Center, VLSI design. 1 Introduction I was hired by IBM Research right out of graduate school, and soon joined what would become the IBM Advanced Computing Systems project just as it was forming in 1965. In these reflections, I’d like to share glimpses of that amazing project from my perspective as a young impressionable engineer at the time. It was a golden era in computer research, a time when fundamental breakthroughs were being made across a wide front. The well-distilled and highly codified results of that and subsequent work, as contained in today’s modern textbooks, give no clue as to how they came to be. Lost in those texts is all the excitement, the challenge, the confusion, the camaraderie, the chaos and the fun – the feeling of what it was really like to be there – at that frontier, at that time. -
Installation for Z/OS
Natural Installation for z/OS Version 8.2.3 für Großrechner November 2012 Dieses Dokument gilt für Natural ab Version 8.2.3 für Großrechner. Hierin enthaltene Beschreibungen unterliegen Änderungen und Ergänzungen, die in nachfolgenden Release Notes oder Neuausgaben bekanntgegeben werden. Copyright © 1979-2012 Software AG, Darmstadt, Deutschland und/oder Software AG USA, Inc., Reston, VA, Vereinigte Staaten von Amerika, und/oder ihre Lizenzgeber.. Nähere Informationen zu den Patenten und Marken der Software AG und ihrer Tochtergesellschaften befinden sich unter http://documentation.softwareag.com/legal/. Die Nutzung dieser Software unterliegt den Lizenzbedingungen der Software AG. Diese Bedingungen sind Bestandteil der Produkt- dokumentation und befinden sich unter http://documentation.softwareag.com/legal/ und/oder im Wurzelverzeichnis des lizensierten Produkts. Diese Software kann Teile von Drittanbieterprodukten enthalten. Die Hinweise zu den Urheberrechten und Lizenzbedingungen der Drittanbieter entnehmen Sie bitte den "License Texts, Copyright Notices and Disclaimers of Third Party Products". Dieses Dokument ist Bestandteil der Produktdokumentation und befindet sich unter http://documentation.softwareag.com/legal/ und/oder im Wurzelverzeichnis des lizensierten Produkts. Dokument-ID: NATMF-INSTALL-ZOS-823-20121108 Table of Contents Preface ............................................................................................................................... ix I Installation Process and Major Natural Features on z/OS .............................................. -
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