0% found this document useful (0 votes)
80 views55 pages

SWG Competitive Project Office: To IBM's System Z Platform

MainFrame Books: JCL -- Download VSAM -- Download COBOL -- Download DB2 -- Download CICS -- Download Mainframe Refresher Book -- Download Here Mainframe Refresher Book Part2 -- Download Here

Uploaded by

Vinod Kumar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
80 views55 pages

SWG Competitive Project Office: To IBM's System Z Platform

MainFrame Books: JCL -- Download VSAM -- Download COBOL -- Download DB2 -- Download CICS -- Download Mainframe Refresher Book -- Download Here Mainframe Refresher Book Part2 -- Download Here

Uploaded by

Vinod Kumar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 55

SWG Competitive Project Office

Introduction
to
IBM’s System z Platform
Introduction
Learning Objectives- What you should Know
 Introducing the Mainframe Environment
 What makes mainframes important for business
 What are some of the main qualities of the mainframe
 Who uses mainframes
 Why enterprises throughout the world rely on the mainframe
as the foundation of large-scale computing
 The IBM System z family
− The names of the current mainframes
 The operating systems supported on System z
 The types of workloads that are commonly associated with
the mainframe.
 Roles and responsibilities of the skilled staff of a mainframe IT
organization.
 Some Terminology to get you started

zCPO zClass Introducing the Mainframe Environment VN 2


If I had just a few things to say about the MF…
 Focus on RAS – Reliability, Availability, Serviceability
 MTBF design point of at least 50 years
 Hardware and software built to stay alive
 Security is essential and comprehensive – lots of $$$ flow through the mainframe: close to impossible to
crack (unless there is a rouge system programmer) (Financial companies are the prevalent customers)
 Shared everything – enables resiliency and scalability
 Scales up and out – Better than most others
 Hardware and software scaling
 Capacity on Demand Capability
 Concurrent Maintenance
 Integrated platform – Software architects working with hardware architects to develop platform
 Includes clustering technologies including ‘special’ H/W & S/W
 I/O bandwidth without parallel
 H/W and S/W built to run at 100% CPU utilization
 Manages Mixed Workloads
 Evolutionary workload management
 Highly evolved virtualization
 Enables efficient resource utilization
 Provides cost and facility reductions via consolidation
 It’s a Green Machine 
 Growth on the mainframe is less expensive than growth on distributed

zCPO zClass Introducing the Mainframe Environment VN 3


HARDWARE ACTING ON ITS OWN

 Reliability:
 Base Design Point 40+ years MTBF for critical failure
 Availability - Self Healing:
 Dynamic PU Sparing (CP, IFL, ICF, SAP)
 Processor Availability Facility (PAF)
 Dynamic Memory Chip Sparing
 Extra I/O Port Sparing
 Instruction retry
 Error Correction Circuitry ( ECC ) for memory
 Concurrent Upgrade (this is upgrading capability)
− Availability - Concurrent Upgrade
− Processors ( CPs, ICFs, IFLs )
− Memory within card boundary
− IO adapters
− Network Adapters
− Crypto Adapters
− Coupling Cards / Links Did I mention Phone Home?
 Turns down the clock if it is getting hot..
 Redundancy
− Two cooling units
− Two thinkpads (for fixes and control)
 Some hardware functions are coded in millicode
− Easier and cheaper to fix than circuits on a board…

zCPO zClass Introducing the Mainframe Environment VN 4


zSeries Hardware Availability
 First Error Data Capture  Memory
Capture errors at run-time ECC Chip kill memory

 Processor Memory chip sparing

Dual execution with compare Hardware memory scrubbing

Enhanced application preservation Concurrent memory add

Transparent CP/ICF/IFL/SAP Partition memory restart


sparing Storage protect keys
Dynamic CPU de-allocation ECC Data buses
Concurrent upgrade  Cache
Capacity backup Cache coherency
 I/O Channels L1 line delete / sparing
Concurrent install/replace ECC L2 line/directory delete/sparing
ESCON port sparing.  Other
Capacity on Demand ESCON-16 Secondary support element
ports. Redundant hot plug power & cooling
Partial I/O restart

zCPO zClass Introducing the Mainframe Environment VN 5


What could cause these things to happen?
 Your airplane might not land safely (air traffic control)
 Your ATM would not give you $$ (banks all over the world)
 There would not be any websites for the Olympics
 You would not find what you wanted on at the super store. (product distribution)
 Your email would not arrive. (manufacturing and design processes)
 You could not buy something online (transaction processing)
 You could not trade stock (database updates)
 Trains could not run everywhere (virtual Linux servers)
 You would not get your paycheck (payroll processing)
 Hospitals could not find get patient records (Patient Management()
 You could not get your prescription filled (legally of course)
 Your FedEx /UPS package would not ship? (shipping and tracking of shipments)
 The Shuttle would not take off.
 The CIA would be in a panic.
 No one would know how fast serves are at Wimbledon!
 The internet would not work. Just ask Al Gore 
zCPO zClass Introducing the Mainframe Environment VN 6
7th April 1964, Poughkeepsie NY
 A new generation of electronic computing equipment was
introduced today by International Business Machines Corporation.
IBM Board Chairman Thomas J. Watson Jr. called the event the most
important product announcement in the company's history.

 The new equipment is known as the IBM System/360.

 "System/360 represents a sharp departure from concepts of the past


in designing and building computers. It is the product of an
international effort in IBM's laboratories and plants and is the first
time IBM has redesigned the basic internal architecture of its
computers in a decade. The result will be more computer
productivity at lower cost than ever before. This is the beginning of
a new generation - - not only of computers - - but of their application
in business, science and government."

zCPO zClass Introducing the Mainframe Environment VN 7


Over Four Decades of Value – now entering Fifth


40 +

Batch
IMS
CICS

Lots of Patents VM and Virtual Storage UPC

S/390 Sysplex CMOS G5/G6

z900/z990 z800/z890
System z9

zCPO zClass Introducing the Mainframe Environment VN 10


It all started with the IBM 701
 Circa 1951:

 And proceeded through the 700, 1400, S/360 & 370, 303x, 308x,
4300, S/390 Parallel Server, to today’s eServer zSeries z10

zCPO zClass Introducing the Mainframe Environment VN 11


Mainframes…44 years of growth

 The 3033, circa 1977 – yes, it filled a  The z10 2008


room – >30,000 MIPS
– 4.7 MIPS
– Up to 1.5 TB Central storage
– 4, 6 or 8 MB central storage – Theoretical Bandwidth Around
– 12 channels (up to 3MB/sec transfer 288 Gbps channels
rate) (total bandwidth = 36MB/sec)

 And customers can run most of the same apps on the z10 as they
could in 1977 on the 3033!

zCPO zClass Introducing the Mainframe Environment VN 12


Notable quotable…
 “I predict that the last mainframe will be unplugged on March
15, 1996”
 Stewart Alsop, former InfoWorld columnist (now at Fortune
Magazine), March, 1991
 Annual growth in MIPS of over 30%
since 1992
 More than $20B in mainframe revenue
since 1996 (when the last one was to
have been unplugged…)
 But there have been many changes in
the mainframe since 1991!
 Prior to the mid-90’s, mainframes were
the IBM “cash cow”. Revenues are still
healthy and margins high, but things
have changed…

zCPO zClass Introducing the Mainframe Environment VN 13


IBM Mainframe Architecture

S/360 S/370 S/370-XA ESA/370 S/390 z Architecture

4/9/1964 6/1970 1981 1988 9/1990 10/2000

24 Bit 24 Bit 24/31 Bit Exp Storage 24/31 Bit 24/31/64 Bit
1-2 Processors 1-2 CPUs 1-4 CPUs 1-6 CPUs 1-12 CPUs 1-32 CPUs
General Purpose 64 MB Storage TCM PR/SM EMIF Hypersockets
Channels Memory Chips Channel Subsystem Vector Processor Parallel Sysplex
Multi-tasking Virtual Storage Crypto Processor ESCON
MCM
FICON
CMOS

20XX 125, 135, 145, 308x 3090 9672 G1-G6 z900 & z800
Model 20-195 168, etc. z990 & z890
3031-3033 System z9-109
31xx

zCPO zClass Introducing the Mainframe Environment VN 14


Shifting Trends Favor the Mainframe Again
 Continuous availability is even more important in the web
world
 Security and compliance are top of mind
 Server sprawl has driven up the cost of labor
 TCO pressure is driving customers to consolidate
workloads on virtualized platforms
 Network economics favor consolidation once again
 Cost of power is increasing
 Growing use of Linux
 IBM has delivered dramatic mainframe price reductions
 Improved Capacity on Demand Provisioning

Make the mainframe part of your winning proposal!


zCPO zClass Introducing the Mainframe Environment VN 15
The Value of Mainframe Computing
 Mainframe core business systems can be easily extended
 Mainframes have a much lower environmental impact
 Consolidation is a proven way to save money and simplify
operations
 Modern mainframe tools enable speed to value, flexibility,
deployment, productivity and reduced cost
 The mainframe delivers superior qualities of continuous
operations, rapid scale up, and security
 Modern mainframes leverage the latest hardware and
software technology for maximum business value

zCPO zClass Introducing the Mainframe Environment VN 16


Meet the IBM Mainframe
 Advanced innovation
Meeting customer needs for 40+ years

 A long standing commitment to protecting our customers


investment in applications
Created the concept of upward compatibility
Unparalleled record of delivering on this commitment

 In a single environment supports multiple, diverse


 workloads concurrently

− Online transaction processing


− Batch
− UNIX workloads
− Linux workloads
− Web serving
− CRM
− ERP
 490 of the Fortune 500 rely on IBM mainframes
Financial institutions
Municipal, state, and federal governments
Retailers
Manufacturing

IBM z10
zCPO zClass Introducing the Mainframe Environment VN 17
Why mainframes?
 Capacity & performance
 Cost per MIPS is meaningless
− MIPS cost on distributed much cheaper
− Commercial workloads are data-intensive, not processor-intensive
− Distributed systems are “data poor”
− Much processing is done outboard from the actual “CPU” (e.g. RISC in I/O
subsystem)
 Superior multitasking & Multiprocessing
 Mixed workloads on mainframe, single workloads on distributed
 100% CPU utilization on mainframes is normal, but fatal on distributed systems

 Personnel costs
 No “end-user maintenance” on mainframes
 Mainframes take more support personnel, but costs have declined considerably

 Data integrity & security is built in


 Scalability
 Parallel Sysplex
 Availability (“5 Nines”)
zCPO zClass Introducing the Mainframe Environment VN 19
Mainframe facts
 Who uses mainframes?
 Most Fortune 1000 companies use a mainframe
environment
 60% of all data available on the Internet is stored on
mainframe computers
 Why mainframes?
 Large-scale transaction processing
− Thousands of transactions per second
 Support thousands of users and application programs
 Simultaneously accessing /sharing resources
 Terabytes of information in databases
 Large-bandwidth communications

 There are more CICS transactions processed daily than Web


pages served

zCPO zClass Introducing the Mainframe Environment VN 20


How are Mainframes Different from Distributed
 Mainframes run at 100% CPU utilization by design
 Distributed systems usually run 60% at the most
 Mainframes run multiple workloads at the same time
 Distributed has single node applications
 Mainframes have specific hardware to enable clustering
 Distributed clustering is usually done through software enablement
 Mainframes have goal oriented workload management optimized through hardware and
software
 Distributed workload management is not as well evolved
 Mainframes have high I/O bandwidth to support batch and transactions loads
 Distributed cannot match the bandwidth without incurring power, space, cooling issues
 Mainframes have significant technology to maintain continuous availability using both
hardware and software error correction and retries
 Distributed system do not have the aggregated recovery capability like the mainframe
 Mainframes have been in use for 10 years or more at accounts
 Distributed systems traditionally have a ‘floor life’ of 3 – 5 years before upgrades.
 Mainframe software is architected with the hardware in mind, and the hardware is
architected with the software in mind
 Distributed software is generally commodity based and is not usually optimized in
conjunction with hardware architects
 Incremental upgrades on the mainframe are usually at a lower cost than like deployments
on distributed platforms.
 Distributed platforms are not as extensible as the mainframe. Extensibility is built into the
mainframe
zCPO zClass Introducing the Mainframe Environment VN 21
Is Distributed that Bad? - NO
 Different architectures are optimized in different ways
 Intel/Windows optimized for low hardware-acquisition costs
 Unix/RISC optimized for compute performance
 zSeries optimized for maximum throughput
− The z10 Changes this with the 4.4 GHz and quad cores
 zSeries processors have very efficient memory structure with very rapid
access to shared cache
 Permits efficient context switching and virtualization
 Other differences
 I/O handling is a zSeries strength
 Processors dedicated to I/O
− Also contributes to RAS

zCPO zClass Introducing the Mainframe Environment VN 22


Optimizing Workloads on a Mainframe is more
effective
Same workload
Mixed Workloads on UNIX
4 UNIX Instances, 4 separate SMPs or Partitions
Web Serving
Mixed Workloads on zSeries
100

Processor Utilization
80
Web Serving

Processor Utilization Percentage


Business Intelligence & Data Mining
Percentage

01:00 03:00 05:00 07:00 09:00 11:00 13:00 15:00 17:00 19:00 21:00 23:00
60

40 Business Intelligence
& Data Mining
20
Batch Batch
SAP
0
00: 00

01: 00

02: 00

03: 00

04: 00

05: 00

06: 00

07: 00

08: 00

09: 00

10: 00

11: 00

12: 00

13: 00

14: 00

15: 00

16: 00

17: 00

18: 00

19: 00

20: 00

21: 00

22: 00

23: 00

24: 00
00: 00 02: 00 04 :0 0 06 :0 0 08 :00 10 :0 0 12 :00 14: 00 16 :00 18: 00 2 0: 00 2 2: 00 2 4: 00

SAP

z/OS WLM balances resources for you


Based on business goals
No other platform comes close
 IBM Mainframes: Up to 100% Utilization  UNIX processors: typically under 25% utilization
– Highly virtualized and shared resources – More of them and more SW license
– “hands off”, business priority driven intelligent – Static scripted workload management
workload management – Higher admin and environmental cost
– Fewer servers, less power, cooling & admin – Intel worse, typically <10% utilization
– Optimized use of SW assets
Baldor Electric, Arkansas
‘Baldor migrated to a z990 in January, and consolidated Unix-based servers onto a single IBM z990, or "T-Rex," with 24
separate, secure partitions on Linux and z/OS. According to (Baldor Electric IS director Mark) Shackleford, this has
allowed Baldor to increase application performance by 40% and cut IT expenditures from 1.7% of total sales to 1.2%. He
expects to get that figure under 1% by the end of 2005.
From “Tech Target August 2005
zCPO zClass Introducing the Mainframe Environment VN 23
What determines system capacity?
There's more to performance than just processing power

 Single system capacity is determined by:


 Processor speed
 Memory hierarchy
 I/O structure

CPU Busy I/O Busy

CPU Time Memory Time I/O Time

Processor, memory, and I/O times vary greatly by


application, and by machine type
zCPO zClass Introducing the Mainframe Environment VN 24
Relative single-system capacity
There's more to performance than just processing power

CPU Busy

CPU Time Memory Time I/O Time zSeries

CPU Busy

CPU
Time Memory Time I/O Time Others

Data intensive workloads like large databases, transaction processing, object


oriented code and context switching potentially run better on zSeries servers.

zCPO zClass Introducing the Mainframe Environment VN 25


Relative single-system capacity
There's more to performance than just processing power
Workloads that do not require "balanced" computing, and rely solely on
processor power will most likely perform better on other architectures

CPU Busy

CPU Time Memory Time I/O Time


zSeries

CPU Busy

CPU Time Memory Time I/O Time Others

Processor intensive workloads like SPECint, Deep Computing, Graphic Rendering


perform poorly on zSeries servers.

zCPO zClass Introducing the Mainframe Environment VN 26


Why the z ?
http://www.ibm.com/systems/z/
 It
used to be OS/390 for the software and S/390 for the
hardware.
 Now it is z/OS and zSeries for the S/W and H/W.
 The z (make sure it is lower case) stand for zero down time.
− The hardware has a targeted MTBF of ~50 years.
− This re-branding took place in October 2000. IBM called its S/W and
H/W offerings eServers.
 IBM re-branded all it’s systems; there is the iSeries, pSeries and
xSeries too.
 iSeries was the AS/400 - A mid range system with a proprietary
operating system
 pSeries was the RS6000 – A RISC system with IBM’s AIX
operating system
 xSeries was the Netfinity system – An X86 based system for
Windows and Linux zCPO zClass Introducing the Mainframe Environment VN 27
A BIG DEAL IS WHEN MONEY IS INVOLVED

 CUSTOMERS CANNOT TOLERATE DOWN TIME!!

 IT COSTS >>>>>>

zCPO zClass Introducing the Mainframe Environment VN 28


Why we need Mainframes (this data is not
from mainframes)

Date Duration Cause


February 7 90 minutes Hardware failure (system board)
FEBRUARY 13 2 hours Hardware failure (system board)
16 2 hours Hardware failure (memory)
22 2.5 hours Hardware failure (SCSI card)
23 1 hour System crash
24 30 minutes System crash
26 2 hours Software problems
27 30 minutes Software problems
March 3 1 hour Hardware failure (system board)
29 2 hours Memory & I/O problems
April 25 1 hour System crash
30 90 minutes I/O subsystem problems
May 3 5 hours Hardware failure (system board)
7 1 hour Software problems
zCPO zClass Introducing the Mainframe Environment VN 29
Why we need Mainframes
(this data is not from mainframes)
Unplanned Outages are Bad for Business
Date Duration Cause
February 7 90 minutes Hardware failure (system board)
FEBRUARY 13 2 hours Hardware failure (system board)
16 2 hours Hardware failure (memory)
22 2.5 hours Hardware failure (SCSI card)
23 1 hour System crash
24 30 minutes System crash
26 2 hours Software problems
27 30 minutes Software problems
March 3 1 hour Hardware failure (system board)
29 2 hours Memory & I/O problems
April 25 1 hour System crash
30 90 minutes I/O subsystem problems
May 3 5 hours Hardware failure (system board)
7 1 hour Software problems
zCPO zClass Introducing the Mainframe Environment VN 30
And Outages cost BIG BUCKS

Representative examples of cost of one hour Web outage*

Web Activity Revenue Loss


Brokerage $43.8 million
Automotive sales $20.4 million
Airline reservations $8.3 million
Catalog retail $5.6 million
Grocery retail $0.445 million
*Lost revenues based on customer lifetime value (CLV).
Outage during peak hours.
Source: International Technology Group

zCPO zClass Introducing the Mainframe Environment VN 31


What would happen If all the mainframes
suddenly stopped?
 Your airplane might not land safely (air traffic control)
 Your ATM would not give you $$ (banks all over the world)
 There would not be any websites for the Olympics
 You would not find what you wanted on at the super store. (product distribution)
 Your email would not arrive. (manufacturing and design processes)
 You could not buy something online (transaction processing)
 You could not trade stock (database updates)
 Trains could not run everywhere (virtual Linux servers)
 You would not get your paycheck (payroll processing)
 Hospitals could not find get patient records (Patient Management()
 You could not get your prescription filled (legally of course)
 Your FedEx /UPS package would not ship? (shipping and tracking of shipments)
 The Shuttle would not take off.
 The CIA would be in a panic.
 No one would know how fast serves are at Wimbledon!
 The internet would not work. Just ask Al Gore 

zCPO zClass Introducing the Mainframe Environment VN 32


Ain't Your Grandpa's Mainframe
 It's A SERVER
 HEY, it’s an SMP
 It’s a CLUSTER
 It’s 64 bit architecture (16 Exabytes worth)
 Up to 64 Processors in a server
 Up to 60 images in a server
 Hot plugging
 CPU Sparing
 Isolates Memory Errors
 Capacity On Demand (CoD)
 Customer Initiated Upgrade (CUI)
 Capacity BackUp (CBU)
 Service Download off the Internet
 GOT FIBER
 GOT JAVA (Really Good Java)
 LINUX RUNS on the Hardware
 HAS “imbedded” Branded UNIX System
 GOT WEBSERVING
 HAS TCP/IP
 Supports UNICODE, ASCII and EBCDIC
 TALK about SECURITY
LDAP, PKI, Kerberos, Digital Certificates,
CRYPTO CoProcessors, Key Vaults, MAC Digests, ..and it’s Green
TRIPLE DES, VPN
zCPO zClass Introducing the Mainframe Environment VN 33
IBM “Big Green” Messages / System z
 Energy efficiency is a global issue with significant impact today — and will
have an even greater impact in the future
 IBM Project Big Green is defining leadership in data center energy
efficiency
 Real solutions are available today
 We are deploying these capabilities with our clients and within IBM
 How to get started

 System z Green message:


 System z is a key technology for energy efficiency
Energy Efficient design + architecture
Highest Utilization rates
World’s best virtualization

zCPO zClass Introducing the Mainframe Environment VN 34


Distributed Power Costs Have Become a
Major Issue
 According to the Wall Street Journal, distributed server farms can
generate as much as 3,800 watts per square foot (up from 250 in 1992)

 By comparison, a System z9 consumes 107-312 watts per square


foot – one tenth or less the amount
 Turning on an IFL processor consumes 75 additional watts
 Cooling cost is roughly an additional 60% of the power cost

 More than half of all serious outages are now caused by power
problems*
 Room temperatures averaging 92ºF lead to erratic machine
behavior

 Aside from cost, some data centers can’t obtain additional power from
their providers

*Source: recent AFCOM survey of 200


zCPO zClass Introducing the Mainframe Environment VN 35
IBM System z: Balanced System Design
System I/O Bandwidth

Balanced System
172.8 GB/sec CPU, nWay, Memory,
I/O Bandwidth*

96 GB/sec

24 GB/sec

GBs 512 GB 256 GB


64 GB 288.15 450 ~ 600
ITRs for 1-way

16-way

32-way

System z9 EC*
zSeries 990
54-way zSeries 900
Generation 6
CPUs
*z9 EC exploits a subset of its designed I/O capability Generation 5

zCPO zClass Introducing the Mainframe Environment VN 36


IBM System z: System Design Comparison
System I/O Bandwidth
Balanced System
288 GB/sec*
CPU, nWay, Memory,
I/O Bandwidth*

172.8 GB/sec*

96 GB/sec

ITR for
Memory 24 GB/sec 1-way
1.5 TB** 512 GB 256 GB 64 GB 300 450 ~600 ~920

16-way

32-way z10 EC

z9 EC
54-way
zSeries 990
*Servers exploit a subset of its designed I/O capability
64-way zSeries 900
** Up to 1 TB per LPAR Processors

zCPO zClass Introducing the Mainframe Environment VN 37


IBM System z10 EC Quick Reference

zCPO zClass Introducing the Mainframe Environment VN 38


IBM System z10 EC Naming Summary

Brand Name: IBM


Product Class: IBM mainframe
Family Name: IBM System z
Family Short Name: System z*
Product Line Name: IBM System z10
Product Line Short Name: System z10*
Model Names (Short Names): IBM System z10 Enterprise Class
(z10 EC or System z10 EC)**
z10 EC Configs: E12, E26, E40, E56, E64

* Please note, “IBM” can be dropped only after first usage of full family or product line name.
** When using short name, NEVER use EC without z10 preceding it. Short names may NOT
appear on nameplate of hardware and can only be used after first usage of full formal names
within content and collateral.

zCPO zClass Introducing the Mainframe Environment VN 39


IBM z10 EC Continues the CMOS Mainframe
Heritage
4000

3500
4.4
GHz
3000 1.7
GHz
2500
MHz

1.2
2000 GHz
770
MHz
1500
550
300 420
MHz
MHz
1000 MHz

500

0
1997 1998 1999 2000 2003 2005 2008
G4 G5 G6 z900 z990 z9 EC z10 EC
 G4 - 1st full-custom CMOS S/390®  z900 - Full 64-bit z/Architecture®  z10 EC – Architectural
 G5 - IEEE-standard BFP; branch target prediction  z990 - Superscalar CISC pipeline extensions
 G6 – Copper Technology (Cu BEOL)  z9 EC - System level scaling

zCPO zClass Introducing the Mainframe Environment VN 40


Does GHz matter?
 GHz does matter
 It is the "rising tide that lifts all boats"
 It is especially important for CPU-intensive applications
 GHz is not the only dimension that matters
 System z focus is on balanced system design across many factors
− Frequency, pipeline efficiency, energy efficiency, cache / memory design, I/O design
 System performance is not linear with frequency
 Need to use LSPR + System z capacity planning tools for real client / workload sizing
 System z has been on consistent path while others have oscillated between extremes
 Growing frequency steadily, with occasional jumps/step functions (G4 in 1997, z10 in
2008)
 z10 leverages technology to get the most out of high-frequency design
 Low-latency pipeline
 Dense packaging (MCM) allows MRU cooling which yields more power-efficient
operation
 Virtualization technology (etc.) allows consistent performance at high utilization,
which makes CPU power-efficiency a much smaller part of the system/data-center
power consumption picture

zCPO zClass Introducing the Mainframe Environment VN 41


2008+ What do businesses need from their
Infrastructure?

IT is critical to the business,


it needs to be there . . . Always
Resiliency is a must

Opening IT to sophisticated
users attracts sophisticated Security is a must
danger . . . viruses, hackers, theft
Maximizing return on investment by Intelligent
maximizing utilization of virtualization
IT resources is a must
With complex infrastructures, need to be Advanced systems
able to control and management is a
manage resources must
As IT becomes more of a commodity, Advanced
people become the largest part automation
of IT budgets is a must
Having high capacity is needed to support
the biggest applications or hundreds of Scalability is a must
smaller applications
As clients strive to integrate the Linux, Java™,
infrastructure, open standards WebSphere®
become the key to success are a must
One final thought It needs to be
affordable!
zCPO zClass Introducing the Mainframe Environment VN 42
Mainframes in our midst
 Mainframes:
 Are prevalent, yet hidden from public eye
 Not often publicized – stable, reliable, dependable.
 Contrast with other forms of computing, such as PCs.
 Present opportunities for college graduates in a variety of
technical fields.

zCPO zClass Introducing the Mainframe Environment VN 44


What is a mainframe?
 A mainframe is a computing system that businesses
use to host the commercial databases, transaction
servers, and applications that require a greater
degree of security and availability than is commonly
found on smaller-scale machines.
 The power of a mainframe provides computing speed
and capacity, enabling it to perform high volumes of
processing.
 The mainframe can process a mixed workload of jobs
from different time zones and of different types.

zCPO zClass Introducing the Mainframe Environment VN 45


Mainframe facts
 Who uses mainframes?
 Most Fortune 1000 companies use a mainframe
environment
 60% of all data available on the Internet is stored on
mainframe computers
 Why mainframes?
 Large-scale transaction processing
− Thousands of transactions per second
 Support thousands of users and application programs
 Simultaneously accessing resources
 Terabytes of information in databases
 Large-bandwidth communications
 There are more CICS transactions processed daily than Web
pages served

zCPO zClass Introducing the Mainframe Environment VN 46


System z9 BC and EC Comparison
IBM System z9 BC (2096) IBM System z9 EC (2094)

 Server with 8 PUs  Server with up to 64 PUs


 2 models – Up to 4-way  5 models – Up to 54-way
 High levels of Granularity  Granular Offerings for up
 73 Capacity Indicators to 8 CPs

 Memory – up to 64 GB  Memory – up to 512 GB

 I/O  I/O
 Two LCSSs  Four LCSSs
 Up to 420 ESCON channels  Up to 1024 ESCON channels
 Up to 112 FICON channels  Up to 336 FICON channels
 Enhanced FICON Express2  Enhanced FICON Express2
4 Gbps and 4
 HiperSockets – up to 16  HiperSockets – up to 16

 Up to 30 logical partitions  Up to 60 logical partitions

zCPO zClass Introducing the Mainframe Environment VN 47


Z890 MAINFRAME

MODEL 2086

Z800 (MODEL 2066) zCPO zClass Introducing the Mainframe Environment VN 48


z890 – Single Hardware Model (announced 7th
of April, 2004)
 Machine Type
 2086
 Model A04 with a Single Book
 One MCM per Model with:
5 Processing Units (PUs)
 4 PUs available for characterization as Central
Processors (CPs), Integrated Facility for Linux (IFLs),
Internal Coupling Facility (ICFs), and zAAPs
 1 standard SAP
 No standard spares
 Memory - System Level:
 Up to 32 GB
 Single card (8, 16 or 32 GB)
 System minimum of 8 GB
 8 GB increments (8, 16, 24, 32 GB)
 One concurrent memory upgrade path (24 to 32 GB)
 I/O:
8 Self-Timed Interfaces (STIs) @ 2.0 GB/s each
 Up to 512 CHPIDs and up to 420 Channels in I/O
Cage (dependent on Channel types)
 Max 2 Logical Channel SubSystems (LCSSs)
zCPO zClass Introducing the Mainframe Environment VN 49
Minimum Operating System Support Levels for
z890

zCPO zClass Introducing the Mainframe Environment VN 50


z89x upgrade to z990 / System z9

zCPO zClass Introducing the Mainframe Environment VN 51


Typical mainframe workloads

zCPO zClass Introducing the Mainframe Environment VN 52


Typical batch use

Residence Branch offices


CREDIT CARD Main
Account balances office
1234 5678 9012
VALID FROM
XX/XX/XX
XX/XX/XX
PAUL FISCHER
GOOD THRU

XX/XX/XX
FISCHER
bills, etc
PAUL

5
6 Reports
Processing
reports 7
Statistics,
4 summaries,
exceptions

8 Mainframe
Partners Processing batch jobs
and clients
exchange Reports
information 2

1 Reports

Backup 3
s

Data
update Tape Storage
10 Sequential
9 data sets

Disk Storage
Production System databases
Control Operator

zCPO zClass Introducing the Mainframe Environment VN 53


Typical online use

ATMs

Account
activities
SNA or TCP/IP 4
1 network
Requests

Branch office
Branch automation
offices systems
2 Mainframe
3 Accesses
database
Office
automation 5
systems

queries 6
and
updates
Central office

Business analysts Inventory control

Disk
storage
controller
Stores
database
files

zCPO zClass Introducing the Mainframe Environment VN 54


Roles in the mainframe world

Roles

Application Production Control Analyst


Developer

Operator
End User

System Programmer System Administrator

zCPO zClass Introducing the Mainframe Environment VN 55


Jobs are US
 System Programmer
 Security Administrator
 Performance analyst
 Network Administrator
 DBA (DataBase Administrators)
 CICS, DB2, IMS, …
 Application Developers
 Java, COBOL, C++, Assembler Language, REXX, FORTRAN…
 I/O Specialist
 Workload Scheduler
 Change Control
 Liaisons for Clients

zCPO zClass Introducing the Mainframe Environment VN 56


Operating Systems on the Mainframe
 z/OS
 The flagship zSeries/z9 operating system

 Ultra-high reliability – over 50% of the OS is dedicated to error recovery!

 z/VM
 Run any zSeries/z9 operating system as a “guest” – similar to VMWare, but
on a large scale!
 Sometimes used for application development
 Linux for zSeries & z10
 A native Unix operating system for zSeries & z10

 zLinux is already trademarked, so we can’t call it that…

 z/VSE
 Small- to mid-size 390 customers
 Most often used on very small 390 hardware

 z/TPF
 Primarily for very high transaction rate, specialized applications (airline
zCPO zClass Introducing the Mainframe Environment VN 57
scheduling)
Mainframe Operating System Heritage
 OS/360 -> OS/VS -> MVS/SP -> MVS/XA -> MVS/ESA -> OS/390 -> z/OS
z/OS is IBM’s premier zSeries operating system, is a highly secure, scalable, high-performance
enterprise operating system on which to build and deploy traditional and Java-enabled
applications, providing a comprehensive and diverse application execution environment.

 DOS/360 -> DOS/VS -> VSE/SP -> VSE/ESA -> z/VSE


VSE enables proven, robust, and cost-effective solutions. VSE provides sturdy batch and
industrial strength on-line transaction processing (CICS) capabilities. VSE can fit comfortably into
a legacy of thrifty, dependable VSE solutions.

 ACP -> TPF-> z/TPF


 TPF is the platform driving the business-critical systems for many of IBM's largest
and most sophisticated users of online transaction processing - airlines, railroads,
hotels, financial services, government, credit card and banking industries.

 CP/67 -> VM/370 -> VM/SP -> VM/XA -> VM/ESA -> z/VM
z/VM provides a highly flexible test and production environment for enterprises
deploying the latest e-business solutions. z/VM helps enterprises meet their growing
demands for multi-user server solutions with support for a broad range of operating
systems.

zCPO zClass Introducing the Mainframe Environment VN 58


 The New Mainframe

 Thank you
for being a
zScholar

zCPO zClass Introducing the Mainframe Environment VN 59

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy