DOCSLIB.ORG

IBM System Z Strengths and Values

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
IBM System Z Strengths and Values Front cover IBM System z Strengths and Values Technical presentation of System z hardware and z/OS Enterprise-wide roles for the System z platform Cost of computing considerations Philippe Comte Andrea Corona James Guilianelli Douglas Lin Werner Meiner Michel Plouin Marita Prassolo Kristine Seigworth Eran Yona Linfeng Yu ibm.com/redbooks International Technical Support Organization IBM System z Strengths and Values May 2008 SG24-7333-01 Note: Before using this information and the product it supports, read the information in “Notices” on page ix. First Edition (May 2008) This edition applies to the IBM System z platform and IBM z/OS V1.8. © Copyright International Business Machines Corporation 2008. 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 . ix Trademarks . x Preface . xiii The team that wrote this redbook. xiii Become a published author . xv Comments welcome. xv Summary of changes . xvii May 2008, First Edition. xvii Chapter 1. A business view . 1 1.1 Business drivers . 2 1.2 Impact on IT . 3 1.3 The System z platform . 7 1.3.1 Using System Z technology to reduce complexity . 7 1.3.2 Business integration and resiliency. 8 1.3.3 Managing the System z platform to meet business goals. 11 1.3.4 Security . 12 1.4 Summary . 13 Chapter 2. System z architecture and hardware platform . 15 2.1 History . 16 2.2 System z architecture . 17 2.2.1 Multiprogramming and multiprocessing . 18 2.2.2 The virtualization concept . 19 2.2.3 PR/SM and logical partitions . 19 2.3 System z hardware architecture . 21 2.3.1 The processing unit. 21 2.3.2 Memory . 23 2.3.3 The channel subsystem . 26 2.3.4 Control units and I/O devices . 28 2.3.5 Time-of-Day clock . 28 2.3.6 CP Assist for Cryptographic Function . 28 2.3.7 HiperSockets. 28 2.3.8 Hardware Management Console (HMC). 29 2.3.9 Intelligent Resource Director (IRD) . 29 2.4 System z frames and cages . 31 2.4.1 System z book. 33 © Copyright IBM Corp. 2008. All rights reserved. iii 2.5 The System z hardware models . 34 Chapter 3. System z software . 35 3.1 Operating systems . 36 3.1.1 z/OS . 36 3.1.2 z/VM . 37 3.1.3 Linux on System z. 38 3.1.4 Other supported operating systems . 38 3.2 z/OS software design . 38 3.2.1 Address space . 39 3.3 z/OS components . 41 3.3.1 Memory managers . 41 3.3.2 Workload Manager (WLM) . 41 3.3.3 Resource Recovery Services (RRS). 46 3.3.4 System Management Facility (SMF) . 46 3.3.5 Systems Managed Storage. 46 3.3.6 Global resource serialization (GRS) . 48 3.4 Tools . 50 3.4.1 Resource Measurement Facility (RMF) . 50 3.4.2 IBM OMEGAMON z/OS Management Console . 52 3.4.3 SMP/E . 53 3.4.4 Programming languages . 54 3.4.5 Software development tools . 56 3.5 Middleware . 57 3.5.1 Business layer. 58 3.5.2 Data layer . 63 Chapter 4. Security . 65 4.1 z/OS Security Server. 66 4.1.1 User identification and authentication . 67 4.1.2 System Authorization Facility . 70 4.1.3 Access control. 72 4.1.4 Multilevel security . 72 4.1.5 Auditing and logging . 74 4.1.6 Networking and communications security. 75 4.2 z/OS Integrated Security Services . 78 4.2.1 Integrated IPSec/VPN support . 78 4.2.2 LDAP directory server . 78 4.2.3 Network authentication service (Kerberos) . 79 4.2.4 Enterprise Identity Mapping (EIM). 80 4.3 z/OS cryptographic services . 81 4.3.1 ICSF . 81 4.3.2 OCSF . 82 iv IBM System z Strengths and Values 4.3.3 System SSL . 82 4.3.4 z/OS PKI services . 83 4.4 System z hardware cryptographic functions . 83 4.4.1 Cryptographic synchronous functions . 83 4.4.2 Cryptographic asynchronous functions . 84 4.4.3 Reasons for using hardware cryptography . 86 4.5 IBM Encryption Facility for z/OS . 88 4.5.1 IBM Encryption Facility for z/OS, Services feature . 89 4.5.2 Encryption Facility Client. 90 4.5.3 DFSMSdss Encryption feature . 91 4.6 IBM System Storage TS1120 . ..
Load more

Recommended publications
  • IDMS Conversion
    IDMS Conversion The Modern Systems IDMS conversion includes the generation of a new relational database to replace the functionality, set relationships, indexes, and data structures that are currently part of the IDMS network database. The new target database can reside on or off the mainframe, and can use any of the standard relational database management systems (RDBMS): Microsoft SQL Server, Oracle or IBM DB2. Database Functionality DB-Shuttle™ provides The Modern Systems solution provides a complete replacement for all IDMS automated technology database functionality: that protects legacy assets, reduces • IDMS record layouts maintenance costs, • Group-level elements, Occurs and Redefines clauses within IDMS record provides agility and definitions flexibility, and enables • Set definitions (record-to-record relationships) Service-Oriented • System-owned indexes Architecture (SOA) • Bill-of-material structures within business-critical • Multi-member sets, multi-set relationships between two record types applications. • Duplicate CALC designations • Sorted sets, Chained sets and NEXT sets Relational Results The resulting database is fully relational. Primary keys, foreign keys and index definitions are automatically created. All constraints are generated into the resulting DDL. Table spaces, indexes, table names and column names are all generated according to your naming standards. Delivered Components As part of the delivery process, Modern Systems generates and delivers the following component types for installation in the new relational
    [Show full text]
  • 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
    [Show full text]
  • Miami-Dade County
    MIAMI-DADE COUNTY Cognos Business Analytics and IDMS Integration at Miami-Dade County Abstract of the Program Miami-Dade County led the way as the first company in the world to successfully extract information from a CA IDMS network database using IBM Cognos Business Analytics. Miami- Dade County stores the majority of their critical data, such as Criminal Justice, Payroll, Traffic and Building information in CA IDMS mainframe databases and traditionally extracts this data using Computer Associates CA IDMS tools (CA ADS ADS/O and IDMS/Cobol/IDMS). Through the collaboration of CA Computer Associates, IBM, and Miami-Dade County, a driver was created for IBM Cognos to access this data directly by using Business Analytics tools without the need for exporting the data into a contemporary distributed environment. The problem or need for the program IDMS (Integrated Database Management System) is primarily a network (CODASYL) database management system for mainframes. Only CA tools could access IDMS data. IDMS mainframe technology did not have the capability to be accessed directly by contemporary business analytics software solutions. This limitation required data extraction, file transfer protocols, and script loading processes to expose IDMS, IMS, and DB2 mainframe data to contemporary technologies, including business analytics tools like IBM Cognos Analytics. Multiple data warehouses and operational data stores are loaded from the primary data sources originating from the IDMS mainframe platform and other relational data sources. More than 50 production IDMS databases are actively supported and used county-wide at Miami- Dade County. Access to data by the distributed world such as making the data available on an Oracle or MSSQL database requires adding multiple intermediate steps, using multiple technologies, and multiple points of failure to migrate data and make it available to analytic technologies.
    [Show full text]
  • IBM Service Management Suite for Z/OS with Service Management Unite
    Front cover IBM Service Management Suite for z/OS with Service Management Unite Lorin Ullmann Carol Davis Michael Gouveia Arthur McDonald Wolfgang Schaeberle Solution Guide Changes are happening in record time, forcing IT managers to develop strategies to anticipate and address these looming IT challenges. These service-driven demands are confronting IT management and making them choose how to best prepare for the future. They must be proactive and agile, which requires getting the most out of their team’s skills and experience to manage this increasingly complex environment. IBM® Service Management Suite for z/OS® (Figure 1) offers a single point of control for systems management functions, such as visibility, control, and automation. It spans hardware and software enterprise resources in an IBM z/OS systems environment and beyond. Stakeholder • IT Operations Dashboards • Development/SME • Line of Business W IT Analytics O Assets Business Results R • Workload Optimization K • Business Agility L • Innovation O A D Performance Automation Systems of S Management Scheduling Engagement Systems of Record Figure 1 Service Management Suite for z/OS overview and strategy for IBM z Systems® Did you know? Service Management Suite for z/OS provides operators a transparent view of the IBM z Systems compute landscape, including central electronic complex (CECs), LPARs, and Sysplexes with key performance indicators for improved problem isolation, analysis, and diagnosis. This IBM Redbooks® Solution Guide describes Service Management Suite for z/OS and its new user interface IBM Service Management Unite and includes high-level architectures (for each solution) with their key components. The guide also explains the integration of Service Management Unite with Service Management Suite for z/OS components and integration with other IBM products and third-party solutions to create a comprehensive solution.
    [Show full text]
  • 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.
    [Show full text]
  • 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).
    [Show full text]
  • IBM Monitoring OMEGAMON Best Practices & Performance Guidelines V1
    IBM Monitoring OMEGAMON Best Practices & Performance Guidelines V1 January 2020 Rocky McMahan – Rocket Matt Hunter – IBM IBM Monitoring – OMEGAMON Best Practices & IBM z Systems Performance Guidelines V4 Table of Contents 1. Objectives ........................................................................................................................................................................................... 5 1.1 Document Updates and Revisions ............................................................................................................................................... 5 2. Requirements ..................................................................................................................................................................................... 5 3. IBM OMEGAMON shared documentation ................................................................................................................................... 5 4. Maintenance Documentation ........................................................................................................................................................... 5 5. PARMGEN Configuration for OMEGAMON/TMS Products on z/OS ...................................................................................... 6 5.1 How to run OMEGAMON’s V550/V540 and still use OMEGAVIEW and OMII CUA’s at V530 levels. .................................. 6 6. Components and architecture .........................................................................................................................................................
    [Show full text]
  • IBM Z Server Time Protocol Guide
    Front cover Draft Document for Review August 3, 2020 1:37 pm SG24-8480-00 IBM Z Server Time Protocol Guide Octavian Lascu Franco Pinto Gatto Gobehi Hans-Peter Eckam Jeremy Koch Martin Söllig Sebastian Zimmermann Steve Guendert Redbooks Draft Document for Review August 3, 2020 7:26 pm 8480edno.fm IBM Redbooks IBM Z Server Time Protocol Guide August 2020 SG24-8480-00 8480edno.fm Draft Document for Review August 3, 2020 7:26 pm Note: Before using this information and the product it supports, read the information in “Notices” on page vii. First Edition (August 2020) This edition applies to IBM Server Time Protocol for IBM Z and covers IBM z15, IBM z14, and IBM z13 server generations. This document was created or updated on August 3, 2020. © Copyright International Business Machines Corporation 2020. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Draft Document for Review August 3, 2020 8:32 pm 8480TOC.fm Contents Notices . vii Trademarks . viii Preface . ix Authors. ix Comments welcome. .x Stay connected to IBM Redbooks . xi Chapter 1. Introduction to Server Time Protocol . 1 1.1 Introduction to time synchronization . 2 1.1.1 Insertion of leap seconds . 2 1.1.2 Time-of-Day (TOD) Clock . 3 1.1.3 Industry requirements . 4 1.1.4 Time synchronization in a Parallel Sysplex. 6 1.2 Overview of Server Time Protocol (STP) . 7 1.3 STP concepts and terminology . 9 1.3.1 STP facility . 9 1.3.2 TOD clock synchronization .
    [Show full text]
  • Mainframe Hardware Course: Mainframe’S Processors
    Mainframe hardware course: Mainframe’s processors z/OS Basic Skills: The mainframe’s processors Mainframe’s processors This hardware course introduces you to one model of IBM® mainframe computer, the IBM System z9™, to help you learn about the hardware parts that constitute the mainframe’s processor by comparing processing parts and functions to personal computers or notebooks. Time to complete: 10 - 15 minutes ¾The central processor complex ¾The multichip module ¾Memory cards ¾Input/output connections ¾The mainframe’s processing capacity © Copyright IBM Corp. 2006. All rights reserved. The central processor complex z/OS Basic Skills: The mainframe’s processors Mainframe’s processors > The central processor complex Mainframes have one or two metal frames that contain specialized cages, as well as other physical elements. This diagram shows the interior front view of an IBM System z9 Enterprise Class (z9 EC) model that has two frames. The z9 EC is slightly larger than a household refrigerator. The central processor complex, or CPC, resides in its own cage inside the mainframe, and consists of one to four book packages. Just like its personal-computer counterpart, the motherboard or system board, each book package consists of processors, memory, timers, and I/O connections. These collections of hardware parts are called “book packages” because you can slide them in or out of the CPC cage almost as easily as you can slide a book on or off a bookshelf. © Copyright IBM Corp. 2006. All rights reserved. z/OS Basic Skills: The mainframe’s processors Mainframe’s processors > The book package In the System z9, as well as earlier IBM mainframe models, the book package consists of three distinct areas, one each for: • The z9 EC's processors, which are inside one multichip module • Memory cards • Connections to input/output devices All of the book packages plug into a backplane in the z9 EC's frame.
    [Show full text]
  • CASE STUDY GE CAPITAL ASSESSING, CONVERTING, & REPLATFORMING a MASSIVE BUSINESS CRITICAL APPLICATION with ASTONISHING RESULTS Introduction
    CASE STUDY GE CAPITAL ASSESSING, CONVERTING, & REPLATFORMING A MASSIVE BUSINESS CRITICAL APPLICATION WITH ASTONISHING RESULTS Introduction GE Capital is the financial services unit of the American conglomerate General Electric, it provides commercial lending and leasing, as well as a range of financial services for consumers. Most of GE Capital’s commercial loans are to small and midsized companies, spread across multiple industries and geographies, and secured by tangible assets. GE Capital’s consumer lending activities are also diversified by product and geography and include operations in 55 countries. Project Summary GE Capital was looking to move their PMS suite of $ 2014 Net Income: $7.0 billion applications from ADS/O and COBOL/IDMS running 2014 Assets: $499 billion on a mainframe, to COBOL running with Oracle on Unix without changing the user interface in the Operations in 40+ Countries process. PMS was built by GE Capital in 1987 500,000+ Commercial Customers and began its life as a 20,000 account schedule system without any interfaces. 35,000+ Employees As with most homegrown systems, it was built out of necessity and to serve the business as it existed at the time. Over the decades, this small system grew in size and complexity to become the central nervous system of both GE Capital’s direct and indirect business units comprised of four highly customized implementations. With over 5 million account schedules, 382 interfaces, 1,700 concurrent users, and 3.5 million transactions per day running against 71 million lines of code, the PMS system had come a long way from its humble roots.
    [Show full text]
  • IBM System Z9 109 Technical Introduction
    Front cover IBM System z9 109 Technical Introduction Hardware description Software support Key functions Bill Ogden Jose Fadel Bill White ibm.com/redbooks International Technical Support Organization IBM System z9 109 Technical Introduction July 2005 SG24-6669-00 Note: Before using this information and the product it supports, read the information in “Notices” on page vii. First Edition (July 2005) This edition applies to the initial announcement of the IBM System z9 109. © 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 Notices . vii Trademarks . viii Preface . ix The authors . ix Become a published author . ix Comments welcome. .x Chapter 1. Introduction. 1 1.1 Evolution . 2 1.2 z9-109 server highlights . 3 1.3 zSeries comparisons. 4 1.4 z9-109 server models and processor units . 6 1.5 Upgrades. 6 1.6 Considerations . 7 Chapter 2. Hardware overview . 9 2.1 System frames . 10 2.2 Books . 10 2.3 MCM . 12 2.4 Processor units . 13 2.4.1 PU characterizations. 14 2.5 Memory . 14 2.6 I/O interfaces. 15 2.7 I/O cages and features . 16 2.7.1 Physical I/O connections. 18 2.7.2 Coupling connections . 20 2.7.3 Cryptographic functions . 20 2.8 Time functions. 21 2.8.1 Sysplex Timer . 21 2.8.2 Server Time Protocol (STP) . 22 2.9 Hardware Storage Area . 22 2.10 System control . 22 2.11 HMC and SE .
    [Show full text]
  • DATABASE SYSTEMS: a BRIEF TIMELINE Event Consequence Pre-1960S 1945 Magnetic Tapes Developed (The First Medium Replaced Punch Cards and Paper Tape
    DATABASE SYSTEMS: A BRIEF TIMELINE Event Consequence Pre-1960s 1945 Magnetic tapes developed (the first medium Replaced punch cards and paper tape. to allow searching). 1957 First commercial computer installed. 1959 McGee proposed the notion of generalized access to electronically stored data. 1959 IBM introduced the Ramac system. Read data in a non-sequential manner, and access to files became feasible. The '60s 1961 The first generalized DBMS-GE'S Integrated Formed the basis for Network Data Model Data Store (IDS)-designed by Bachman; developed by Conference on Data Systems wide distribution by 1964. Bachman Languages Database Task Group (CODASYL popularized data structure diagrams. DBTG). 1965- · Generalized file management systems Provided two-level conceptual/user view 1970 developed by numerous vendors. organization of data. · Information Management System (IMS) developed by IBM. Formed the basis for Hierarchical Data Model. · IMS DB/DC (database/data communication) System was the first Supported network views on top of the large-scale DB/DC system. hierarchies. · SABRE, developed by IBM and American Airlines. Allowed multiple-user access to data involving a communication network. The '70s Database technology experienced rapid Commercial systems followed CODASYL growth. DBTG Proposal, but none fully implemented it. IDMS system by B. F. Goodrich, Honeywell's IDS II, UNIVACs DMS 1100, Burroughs's DMS-II, CDCs DMS-170, Phillips's PHOLAS, and Digital's DBMS-11. Several integrated DB/DC systems: Cincom’s TOTAL plus ENVIRON/l. DBMS developed as an academic discipline and a research area. 1970 The relational model is developed by Ted Laid foundation for database theory. Codd, an IBM research fellow.
    [Show full text]