Você está na página 1de 41

IBM India Software Labs

The System z world

K.Shreekanth
Lab Architect
IBM Software Labs

2008 IBM Corporation

IBM India Systems and Technology Lab

Agenda
History & Evolution of System z (Mainframes)
System z facts
Why System z
Unique ITIes of System z
Specialty Engines

Roles in Mainframe World

The System z world

2007 IBM Corporation

IBM India Software Labs

History & Evolution of System z (Mainframes)

2008 IBM Corporation

IBM India Systems and Technology Lab

Mark I - Automatic Sequence Controlled Calculator, 1944


First ever fully-automatic
calculator
Developed in collaboration
with Harvard University

51 feet x 8 feet. 5 tonnes


Built using gears, counters,
switches, adding machines
One addition in 1/3 of a
second
One multiplication in 6
seconds
Loop was created by
physically looping the
Punched Paper tapes
4

The System z world

2007 IBM Corporation

IBM India Systems and Technology Lab

IBM 701 (1953)


Used Electrostatic storage
(vacuum tubes)
Could store 2048 words (4
bytes each)
18 bit instructions (sign 1,
opcode 5, address 12)
2 registers (Accumulator and
Multiplier/Quotient)
It executed 17,000
instructions per second

The System z world

2007 IBM Corporation

IBM India Systems and Technology Lab

IBM 7090 (1959)


Fully transistorized mainframe
36 bit words, 36 bit
instructions, address space
size of 32K.
229,000 calculations per
second
US Air force used it to run
their Ballistic Missile Early
Warning System
NASA used it for simulating
the moon flight

The System z world

2007 IBM Corporation

IBM India Systems and Technology Lab

S/360 (Big Iron) & OS/360 (1960s)


IBMs $5 Billion Gamble
19 combinations of power, speed and
memory
Dedicated I/O Processors, Parallel
I/O channels

8 bit bytes, Byte addressable


storage
16 GRs and 4 FPRs, each 32 bit.
EBCDIC was introduced
Microcode (Firmware)

In 1969, Apollo 11s moon landing


was supported by many S/360s and
IMS

The System z world

2007 IBM Corporation

IBM India Systems and Technology Lab

S/370 & OS/370 (1970s)


Multiprocessor (two)
system
Backward compatible
24 bits (16 MB)
address space
Virtual Memory
31 bit addressing
from S/370 XA (1983)
Dataspaces &
Hiperspaces from
ESA/370

The System z world

2007 IBM Corporation

IBM India Systems and Technology Lab

Mainframes are not Dead!


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!

Today the mainframe runs Unix and


Linux workload in co-operation with z/OS
and VM.

The System z world

2007 IBM Corporation

IBM India Systems and Technology Lab

S/390 & OS/390, ESA/390 & MVS/ESA (1990s)


24 & 31 bit addressing
2 GB address spaces
Bipolar to CMOS migration
LPARs, Parallel Sysplex

10

The System z world

2007 IBM Corporation

IBM India Systems and Technology Lab

System z & z/OS (2000s)


24, 31 bit & 64 bit
Up to 54 CPUs, 60
LPARs, 32 systems
in a Sysplex.

64 bit registers.
GPRs, FPRs, FPCR,
ARs and CRs.
512 GB main memory
(4 TB soon)
16 Exabyte address
spaces
Virtualization,
WLM/IRD

Is that a Fridge?? No, System z.


11

The System z world

2007 IBM Corporation

IBM India Systems and Technology Lab

Evolution of System z

HW

S/360

1964

1970

MVT, PCP
MFT

CMOS

S/370XA 31 bits

S/370

MVS - VTAM

ESA/390

1980

1990

MVS/XA

MVS/ESA
OS/390

Parallel Sysplex

z/Architecture 64 bits

2000

USS -

2004

z/OS

TCP/IP

SW
Linux
CICS

VM

DB2

WebSphere
z/VM

12

The System z world

2007 IBM Corporation

IBM India Systems and Technology Lab

System z Facts
100% of the 10 world largest banks run their core
applications on System z
100% of Fortune 100 run mission critical applications
on a System z
95% of Fortune 1000 companies use IMS on System
z

60% of all data in the world reside on System z


Application compatibility from 1964 till date
No security incident, virus or worm for 42 years

13

The System z world

2007 IBM Corporation

IBM India Systems and Technology Lab

Typical mainframe workloads

14

The System z world

2007 IBM Corporation

IBM India Systems and Technology Lab

Typical batch use


Residence
CREDIT CARD

1234 5678 9012


VALID FROM

Branch offices

Main
office

Account balances
bills, etc

GOOD THRU

XX/XX/XX
XX/XX/XX
PAUL FISCHER
FISCHER
PAUL

5
Processing
reports 7

Reports
Statistics,

4 summaries,
exceptions

Partners
and clients
exchange
information

Mainframe
Processing batch jobs
Reports

2
1

Reports

Backup
s 3
Data
update

Tape Storage
10

Sequential
data sets

Disk Storage
Production
Control

15

The System z world

System
Operator

databases

2007 IBM Corporation

IBM India Systems and Technology Lab

Typical online use


ATMs
Account
activities

Network
(e.g. TCP/IP or SNA)

4
Requests

Branch
offices

Branch office
automation
systems

Mainframe

Accesses
database

3
Office
automation
systems

queries
and
updates

Central office
Business analysts

Inventory control
Disk
storage
controller
Stores
database
files

16

The System z world

2007 IBM Corporation

IBM India Systems and Technology Lab

Myths About Mainframes


1.
Mainframes are
expensive to buy
and operate
5.
Mainframes are
inflexible & unable
to change quickly

2.
There is nothing
new in the world
of mainframes

5 Myths

4.
Inability to
find talent as those
with mainframe
skills retire

17

The System z world

3.
ISV enthusiasm
for mainframe
applications is
dwindling

2007 IBM Corporation

IBM India Systems and Technology Lab

Why System z?
EXTREMELY reliable (MTBF of 50+ Years)
Because of the ITIES (sounds like Cities without the C)
RAS (RELIABILITY, AVAILABILITY, SERVICEABILITY),
RECOVERABILITY

INTEGRITY System Integrity and Data Integrity


SCALABILITY both Vertical and Horizontal Scalability
MANAGEABILITY
QOS Qualities of Service
Designed and built in over 40 years.

Cant Beat its RAS!

18

The System z world

2007 IBM Corporation

IBM India Systems and Technology Lab

Why System z?
Capacity & performance
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
Mixed workloads on mainframe, single applications on distributed
100% CPU utilization on mainframes is normal, but fatal on distributed systems

Personnel costs
Per-user support costs less on mainframe than other platforms
Security
Scalability

Up to 32 54-way systems with Parallel Sysplex


Availability (5 Nines)

19

The System z world

2007 IBM Corporation

IBM India Systems and Technology Lab

Service Level Agreement


A Service Level Agreement (SLA) is an agreement
between a service provider and a recipient, generally
the server owner and a business unit.

SLAs are the baseline for capacity, availability and


performance measurements and ratings.
Example:
95% of ATM transactions are completed in less
than one second.
90% of daily reports are completed by 6 A.M.

20

The System z world

2007 IBM Corporation

IBM India Systems and Technology Lab

System z enables Service Level Agreements


Policy Driven Real-Time Prioritization
Points of Sale and Pharmacy Transactions
get fast track as a matter of policy

High Priority
Transactions

OLAP analysis for buying patterns

Medium Priority
Analysis

Recurring reporting, uses leftover cycles

Low Priority
Batch

Result (Enterprise Averages)


zStack > 85%
UNIX ~ 10-20%
WINTEL ~ 5%
21

The System z world

2007 IBM Corporation

IBM India Systems and Technology Lab

System z is optimized for many types of processing


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 virtualization and context switching potentially run better
on System z servers

22

The System z world

2007 IBM Corporation

IBM India Systems and Technology Lab

System z - Hardware scalability


System I/O Bandwidth
172.8
GB/sec

Balanced System
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

54-way

CP
Us

*z9-109 exploits a subset of its designed I/O capability


ITR = Internal Throughput Rate

ITR =
23

System z9 109*
zSeries 990
zSeries 900
Generation 6
Generation 5

Unit of Work
Processor busy time
The System z world

2007 IBM Corporation

IBM India Systems and Technology Lab

Capacity On Demand (CoD)


CoD encompasses the various capabilities for you o
dynamically activate one or more resources in your
server as your business peaks dictate.

Different CoD options:


Capacity Upgrade on Demand (CUoD)
Customer Initiated Upgrade (CIU)
On/Off Capacity on Demand

24

The System z world

2007 IBM Corporation

IBM India Systems and Technology Lab

Security
IBM System Z partitioning achieves highest certification
System Z servers achieve
Common Criteria Security
Certification - Evaluation
Assurance Level 5.

ATTENTION: Only the IBM


mainframe partitions have
attained an EAL5 rating.

U. S. Government had rated the


mainframe EAL5.

25

The System z world

2007 IBM Corporation

IBM India Systems and Technology Lab

z/OS System Security Mechanisms


Supervisor Call
Routine (SVC)

Code to perform system level functions.

Problem State

Most modules run in this state.

Supervisor State

Only operating system modules run in this state.

Authorized
Program Facility
(AFP)

Limits the use of sensitive SVCs to authorized


programs.

Storage
Protection Keys

Keys 0-7 are system keys and can only be obtained


by programs in supervisor state. Keys 8-15 are
user keys.

Authorized
Program

Any program that runs, in supervisor state, with


APF authorization, with a storage key in 0-7.

26

The System z world

Ensures that all modules fetched by authorized


programs only come from authorized libraries.

2007 IBM Corporation

IBM India Systems and Technology Lab

How Important is High Availability?


Fractional Improvements Make a Difference
Example: Financial Services Company
$300B assets, 2500+ branches, 15M
customers

Industry segment

Cost

Energy

$2,818K

Telecommunications

$2,066K

CRM System branches, financial


advisors, call centers, internet

Manufacturing

$1,611K

Number of users 20,000+

Financial

$1,495K
$1,345K

Retail banking, loans, mortgages, wealth


management, credit cards

27

Financial Impact of Downtime Per Hour

Unix/

zSeries/

Information
Technology

Oracle

DB2

Insurance

$1,202K

Availability %

99.825%

99.975%

Retail

$1,107K

Annual outage

15h 20m

2h 11m

Pharmaceuticals

$1,082K

Cost of
Downtime

$45.2M

$3.6M

The System z world

Banking

$997K

Consumer Products

$786K

Chemicals

$704K

Transportation

$669K
2007 IBM Corporation

IBM India Systems and Technology Lab

Cost of outages..

28

The System z world

2007 IBM Corporation

IBM India Systems and Technology Lab

Inhibitors to availability

Number of 9s or the Myth of the nines


Class of 9s

Outage

99.999 % 5 min / year


99.99 % 53 min / year
99,9 % 8.8 hrs / year

99 % 88 hrs / year
90 % 876 hrs (36.5
days) / year

29

The System z world

Example
Continous
Availability

z/OS Parallel
Sysplex

Fault Tolerant

S/390 Parallel
Sysplex

High
Availability

Single IBM
System z CPC

General
Purpose

High available
UNIX Cluster
Campus LAN

2007 IBM Corporation

IBM India Systems and Technology Lab

Evolution of RAS for IBM System z high end


Systems
z900
Microcode Driver Updates

6 Hr Scheduled outage 6 Hr Scheduled outage

Book Replacement**

Not Applicable

Scheduled Outage

Memory Replacement

Scheduled Outage

Scheduled Outage

Unscheduled Outage

Unscheduled Outage

ECC on Memory Control


Circuitry (EX: SMI)
Memory Bus Adapter
(MBA) Replacement
STI Failure

z9 EC
Concurrent*
Concurrent
Concurrent
(Book Offline)
Transparent

Scheduled Outage. Lose Scheduled Outage. Lose


Concurrent.
connectivity to I/O
connectivity to I/O
Connectivity to I/O
Domain
Domain
Domain remains
As for MBA
As for MBA
As for MBA

Oscillator Failure

Unscheduled Outage

Unscheduled Outage

Transparent

Processor Upgrades
Physical Memory
Upgrades

Concurrent

Concurrent

Concurrent

Scheduled Outage

Scheduled Outage

I/O Upgrades

Concurrent

Concurrent

Concurrent
(Book Offline)
Concurrent

Spare PUs

1 System

2 / Book

2 / System

*In select circumstances


30

z990

The System z world

**Customer pre-planning required, may require acquisition of additional hardware resources

2007 IBM Corporation

IBM India Systems and Technology Lab

System z Availability & Disaster Recovery

Built In Redundancy
Capacity Upgrade on
Demand
Capacity Backup
Hot Pluggable I/O

31

The System z world

Addresses Planned/Unplanned
Hardware and Software Outages

Addresses Site
Failure/Maintenance

Flexible, Nondisruptive Growth


Capacity beyond largest CEC
Scales better than SMPs

Sync/Async Data Mirroring


Eliminates Tape/Disk SPOF
No/Some Data Loss

Dynamic Workload/Resource
Management

Application Independent

2007 IBM Corporation

IBM India Systems and Technology Lab

Specialty Engines - zAAPs, zIIPs, IFLs and ICF


z Application Assist Processor (zAAP)
For Java work loads
z Integrated Information Processor (zIIP)
For DB workloads (Long running, parallel queries, ODBC,
JDBC)
Integrated Facility for Linux (IFL)
For zLinux
Internal Coupling Facility
For coupling the PLEXes.

32

The System z world

2007 IBM Corporation

IBM India Systems and Technology Lab

Breaking the Myths..


1.
Mainframes are
expensive to buy
and operate
5.
Mainframes are
inflexible & unable
to change quickly

2.
There is nothing
new in the world
of mainframes

5 Myths

4.
Inability to
find talent as those
with mainframe
skills retire

33

The System z world

3.
ISV enthusiasm
for mainframe
applications is
dwindling

2007 IBM Corporation

IBM India Systems and Technology Lab

Myth 1 Mainframes are expensive to buy and operate

34

The System z world

2007 IBM Corporation

IBM India Systems and Technology Lab

Myth 2 There is nothing new in the world of mainframes

Price-to-Performance
Ratio

Perception of
Complexity and
Inflexibility

Lack of Innovation

Primary Inhibitors/
Concerns

Inability to Find
Talent

ISV Enthusiasm

IBM System z Workload Evolution

Core Business
Enterprise Applications
e-business Solutions

Core Business
Enterprise Applications
e-business Solutions
Business Continuity & Recovery
Linux
35

The System z world

2007 IBM Corporation

IBM India Systems and Technology Lab

Myth 3 ISV enthusiasm for mainframe applications is dwindling


Price-to-Performance
Ratio

Perception of
Complexity and
Inflexibility

Lack of Innovation

Primary Inhibitors/
Concerns

Inability to Find
Talent

Priority System z Selected Business Solutions

BANKING

ISV Enthusiasm

INSURANCE
FIN MKTS

Front Office
Back Office

36

TCS/FNS
Fidelity
Temenos
FiServ
SAP
SAS
Epiphany
Unica
QCi
Kana
MicroStrategy

Business Objects
Ascentia
Evoke
DWL
MarketSoft
Chordiant
Reveleus
Acxiom
Experian
PeopleSoft
Siebel Analytics

The System z world

Risk &
Compliance

ACI
Carreker
IntraNet
ARGO
China Systems
Bottomline
S1
SWIFT
SAS
Mantas
Algorithmics
SAP
PeopleSoft

Core Insurance

DWL
Siebel
Epiphany
Chordiant
Callidus
CSC
PureEdge
PeopleSoft
Doc Sciences
MapInfo
Pega

SAS
SAP
Adhesion
Finaplex
netDecide
Syncsoft
Tenemos
MicroStrategy
Cognos
Hyperion
Adobe
Cognos
Brio

2007 IBM Corporation

IBM India Systems and Technology Lab

Myth 4 Inability to find talent as those with mainframe skills retire|

Price-to-Performance
Ratio

Perception of
Complexity and
Inflexibility

Lack of Innovation

Primary Inhibitors/
Concerns

Inability to Find
Talent

ISV Enthusiasm

Counterpoints
Competitor Messages
Resources with mainframe
skills are aging
Mainframe resources are
expensive
Mainframe skills are not being
taught to university students

Middleware-related skills, which are less dependent upon platform, are


most important for the banking industry
Integration and process management requirements within banking result in a
greater need for Java/C++ skills over COBOL
Automation and intelligent agents decrease the resources needed to support
mainframe systems

Salaries for mainframe skills are on-par with non-mainframe skills


If the demand for mainframe skills including COBOL was significantly greater
than for non-mainframe skills, the average salary would be significantly greater
"If this were actually a killer issue, you'd find the average Cobol programmer's
salary wouldn't be under $100,000, but would be $200,000 to $250,000. The
problem isn't quite as bad as it seems. There are thousands of new Cobol
programmers in India, China, and the Philippines. - Ian Archball, Micro Focus1
Salaries for mainframe-based skills are only slightly higher than AIX/Unix-based
skills 1% more for IT staff and 4% more for all IT positions2

IBM is supporting the teaching of these skills


IBM has set a goal of training 20,000 workers for 2010; this is supported by over
200 colleges and universities
IBM is teaming with service providers like TCS
1Source:
2Source:

37

Mainframe Programmers Wanted, InformationWeek, September 2005


Enterprise Systems (www.esj.com), 2005 Salary Survey, August 2005

The System z world

2007 IBM Corporation

IBM India Systems and Technology Lab

Myth 5 Mainframes are inflexible and unable to change quickly

Price-to-Performance
Ratio

Perception of
Complexity and
Inflexibility

Lack of Innovation

Primary Inhibitors/
Concerns

Inability to Find
Talent

Competitor Messages

ISV Enthusiasm

Counterpoints
Mainframes provide flexibility through partitioning and workload
management

Mainframes are in-flexible and


unable to respond quickly to
change

The mainframe is designed to maximize its capabilities in a multi-workload


environment because a major part of the system is dedicated to managing mixed
workloads as opposed to pure processor performance

Mainframes also enjoy the same flexibility benefits of distributed server


environments
UNIX APIs, J2EE, grid standards and Linux can now be run on mainframes

Adding permanent processor capacity and storage to a mainframe can


occur quickly and on demand without interruptions
This can typically be done without increasing staff levels
On demand options are available to help with utilization spikes
A distributed server based infrastructure requires adding servers in order to
scale or handle spikes in utilization
Distributed server infrastructures also require a linear increase in support staff to
manage the new servers

IBM has provided a robust, flexible SOA environment on the mainframe


IBM has added the capability that allows existing business logic contained within
core systems to be exposed as Web services as part of a SOA allowing banks to
run new workloads alongside existing applications

38

The System z world

2007 IBM Corporation

IBM India Systems and Technology Lab

Roles in the mainframe world


Roles
Application
Developer

Production Control Analyst

Operator
End User

System Programmer

39

The System z world

System Administrator

2007 IBM Corporation

IBM India Systems and Technology Lab

References
www.redbooks.ibm.com
www.ibm.com/ibm/history
www.ibm.com/ibm/history/exhibits/index.html
ABCs of z/OS System Programming Volumes 1 11
z/Architecture Principles of Operation (POP)

Introduction to the New Mainframe: z/OS Basics

40

The System z world

2007 IBM Corporation

IBM India Software Labs

Questions?

2008 IBM Corporation

Você também pode gostar