The System z World

7/21/2019 The System z World

1/41

IBM India Software Labs

2008 IBM Corporation

The System z world

K.ShreekanthLab ArchitectIBM Software Labs


2/41

IBM India Systems and Technology Lab

2007 IBM Corporation2 The System z world

Agenda

History & Evolution of System z (Mainframes) System z facts

Why System z

Unique ITIes of System z

Specialty Engines

Roles in Mainframe World


3/41



History & Evolution of System z (Mainframes)


4/41



Mark I - Automatic Sequence Controlled Calculator, 1944

First ever fully-automaticcalculator

Developed in collaborationwith Harvard University

51 feet x 8 feet. 5 tonnes

Built using gears, counters,switches, adding machines

One addition in 1/3 of asecond

One multiplication in 6seconds

Loop was created byphysically looping thePunched Paper tapes


5/41



IBM 701 (1953)

Used Electrostatic storage(vacuum tubes)

Could store 2048 words (4bytes each)

18 bit instructions (sign1,opcode5, address12)

2 registers (Accumulator andMultiplier/Quotient)

It executed 17,000

instructions per second


6/41



IBM 7090 (1959)

Fully transistorized mainframe

36 bit words, 36 bitinstructions, address spacesize of 32K.

229,000 calculations persecond

US Air force used it to runtheir Ballistic Missile EarlyWarning System

NASA used it for simulatingthe moon flight


7/41



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

IBMs $5 Billion Gamble

19 combinations of power, speed andmemory

Dedicated I/O Processors, ParallelI/O channels

8 bitbytes, Byte addressablestorage

16 GRs and 4 FPRs, each 32 bit.

EBCDIC was introduced

Microcode (Firmware)

In 1969, Apollo 11s moon landingwas supported by many S/360s andIMS


8/41



S/370 & OS/370 (1970s)

Multiprocessor (two)system

Backward compatible

24 bits (16 MB)address space

Virtual Memory

31 bit addressingfrom S/370 XA (1983)

Dataspaces &Hiperspaces fromESA/370


9/41



Mainframes are not Dead!

I predict that the last mainframe will be unplugged on March 15, 1996Stewart Alsop, former InfoWorld columnist (now at Fortune Magazine), March, 1991

Annual growth in MIPS of over 30%since 1992

More than $20B in mainframe revenuesince 1996 (when the last one was tohave been unplugged)

But there have been many changes inthe mainframe since 1991!

Today the mainframe runs Unix andLinux workload in co-operation with z/OSand VM.


10/41



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

24 & 31 bit addressing

2 GB address spaces

Bipolar to CMOS migration

LPARs, Parallel Sysplex


11/41



System z & z/OS (2000s)

24, 31 bit & 64 bit

Up to 54 CPUs, 60LPARs, 32 systemsin a Sysplex.

64 bit registers.

GPRs, FPRs, FPCR,ARs and CRs.

512 GB main memory(4 TB soon)

16 Exabyte address

spaces Virtualization,

WLM/IRDIs that a Fridge?? No, System z.


12/41



Evolution of System z

1964 1970 1980 1990 2000 2004

S/360 S/370 S/370XA 31 bits ESA/390 z/Architecture 64 bits

MVT, PCP

MFTMVS - VTAM

VM

MVS/XAMVS/ESA

OS/390z/OS

DB2z/VM

LinuxCICS

HW

SW

USS -

TCP/IP

WebSphere

CMOS

Parallel Sysplex


13/41



System z Facts

100% of the 10 world largest banks run their coreapplications on System z

100% of Fortune 100 run mission critical applicationson a System z

95% of Fortune 1000 companies use IMS on Systemz

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


14/41



Typical mainframe workloads


15/41



Typical batch use

Disk Storagedatabases

Tape Storage

Sequentialdata sets

Partnersand clientsexchange

information

Reports

Backups

Dataupdate

Reports

Statistics,summaries,exceptions

ResidenceMainoffice

Branch offices

Account balancesbills, etc

Processingreports

Mainframe

Processing batch jobs

44

55

Reports

22

1010

11

88

66

33

CREDIT CARD

1234 5678 90121234 5678 9012V AL ID F RO M G OO D TH RU

X X /X X /X X X X/ X X/ XX

PAUL FISCHER

X X /X X /X X X X /X X /X X

PAUL FISCHER

77

99

SystemOperator

ProductionControl


16/41



Typical online use

Diskstorage

controller

Storesdatabase

files

queriesand

updates

Accountactivities

Officeautomation

systems

Mainframe

Accessesdatabase

Requests

ATMs

Branchoffices

Business analysts Inventory control

Branch officeautomationsystems

Network

(e.g. TCP/IP or SNA)

55

66

33

22

44

11

Central office


17/41



Myths About Mainframes

5.

Mainframes are

inflexible & unable

to change quickly

4.

Inability to

find talent as those

with mainframe

skills retire

3.

ISV enthusiasm

for mainframeapplications is

dwindling

2.

There is nothing

new in the worldof mainframes

1.

Mainframes are

expensive to buy

and operate

5 Myths


18/41



Why System z?

EXTREMELY reliable (MTBF of 50+ Years)

Because of the ITIES (sounds like Cities without the C)

RAS (RELIABILITY, AVAILABILITY, SERVICEABILITY),

RECOVERABILITY

INTEGRITYSystem Integrity and Data Integrity

SCALABILITYboth Vertical and Horizontal Scalability

MANAGEABILITY

QOSQualities of Service

Designed and built in over 40 years.

Cant Beat its RAS!

S


19/41



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)

IBM I di S t d T h l L b


20/41



Service Level Agreement

A Service Level Agreement (SLA) is an agreementbetween a service provider and a recipient, generallythe 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 lessthan one second.

90% of daily reports are completed by 6 A.M.



21/41



System z enables Service Level Agreements

Recurring reporting, uses leftover cycles

OLAP analysis for buying patterns

Points of Sale and Pharmacy Transactionsget fast track as a matter of policy

High PriorityTransactions

Medium PriorityAnalysis

Low PriorityBatch

Result(Enterprise Averages)

zStack > 85%

UNIX ~ 10-20%

WINTEL ~ 5%

Policy Driven Real-Time Prioritization



22/41



System z is optimized for many types of processing

There's m ore to per formance than jus t processing pow er

Data intensive workloads like large databases, transaction processing, objectoriented code, and virtualization and context switching potentially run betteron System z servers

CPU Time Memory Time I/O Time

CPU Busy

CPUTime Memory Time I/O Time

CPU Busy

zSeries

Others



23/41



System z - Hardware scalability

System I/O Bandwidth

CPUs

GBsITRs for

1-way

System z9 109*

zSeries 990zSeries 900

Generation 6

Generation 5

172.8GB/sec

96 GB/sec

24 GB/sec

256 GB 64 GB 288.15 450 ~ 600

16-way

32-way

54-way

512 GB

Balanced System

CPU, nWay,

Memory,

I/O B andwidth*

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

ITR = Internal Throughput Rate

ITR =Unit of Work

Processor busy timeITR =

Unit of Work

Processor busy time

Unit of Work

Processor busy time



24/41



Capacity On Demand (CoD)

Different CoD options:

Capacity Upgrade on Demand (CUoD)

Customer Initiated Upgrade (CIU)

On/Off Capacity on Demand

CoD encompasses the var ious capabi l it ies for you o

dynam ically act ivate one or more resou rces in you r

server as your b usiness peaks dictate.



25/41



Security

System Z servers achieveCommon Criteria SecurityCertification - Evaluation

Assurance Level 5.

U. S. Government had rated themainframe EAL5.

ATTENTION: Only the IBMmainframe partitions haveattained an EAL5 rating.

IBM System Z partitioning achieves highest certification



26/41



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.

AuthorizedProgram Facility(AFP)

Limits the use of sensitive SVCs to authorizedprograms.

Ensures that all modules fetched by authorizedprograms only come from authorized libraries.

Storage

Protection Keys

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

by programs in supervisor state. Keys 8-15 areuser keys.

AuthorizedProgram

Any program that runs, in supervisor state, withAPF authorization, with a storage key in 0-7.



27/41



Example: Financial Services Company

$300B assets, 2500+ branches, 15Mcustomers

Retail banking, loans, mortgages, wealthmanagement, credit cards

CRM Systembranches, financialadvisors, call centers, internet

Number of users20,000+

Financial Impact of Downtime Per Hour

Industry segment Cost

Energy $2,818K

Telecommunications $2,066K

Manufacturing $1,611K

Financial $1,495K

InformationTechnology

$1,345K

Insurance $1,202K

Retail $1,107K

Pharmaceuticals $1,082K

Banking $997K

Consumer Products $786K

Chemicals $704K

Transportation $669K

How Important is High Availability?Fractional Improvements Make a Difference

Unix/

Oracle

zSeries/

DB2

Availability % 99.825% 99.975%

Annual outage 15h 20m 2h 11mCost ofDowntime

$45.2M $3.6M



28/41



Cost of outages..



29/41



Inhibitors to availabilityNumber of 9sor the Myth of the nines

Class of 9s Outage Example

99.999 % 5 min / year ContinousAvailability

z/OS ParallelSysplex

99.99 % 53 min / year Fault Tolerant S/390 ParallelSysplex

99,9 % 8.8 hrs / year HighAvailability

Single IBMSystem z CPC

99 % 88 hrs / year GeneralPurpose

High availableUNIX Cluster

90 % 876 hrs (36.5days) / year

Campus LAN



30/41



z900 z990 z9 EC

Microcode Driver Updates 6 Hr Scheduled outage 6 Hr Scheduled outage Concurrent*

Book Replacement** Not Applicable Scheduled Outage Concurrent

Memory Replacement Scheduled Outage Scheduled Outage Concurrent(Book Offline)

ECC on Memory Control

Circuitry (EX: SMI) Unscheduled Outage Unscheduled Outage TransparentMemory Bus Adapter(MBA) Replacement

Scheduled Outage. Loseconnectivity to I/O

Domain

Scheduled Outage. Loseconnectivity to I/O

Domain

Concurrent.Connectivity to I/ODomain remains

STI Failure As for MBA As for MBA As for MBA

Oscillator Failure Unscheduled Outage Unscheduled Outage Transparent

Processor Upgrades Concurrent Concurrent Concurrent

Physical MemoryUpgrades Scheduled Outage Scheduled Outage

Concurrent(Book Offline)

I/O Upgrades Concurrent Concurrent Concurrent

Spare PUs 1 System 2 / Book 2 / System*In select circumstances **Customer pre-planning required, may require acquisition of additional hardware resources

Evolution of RAS for IBM System z high endSystems



31/41



System zAvailability & Disaster Recovery

Addresses Planned/Unplanned

Hardware and Software OutagesFlexible, Nondisruptive Growth

Capacity beyond largest CEC

Scales better than SMPs

Dynamic Workload/ResourceManagement

Built In Redundancy

Capacity Upgrade onDemand

Capacity Backup

Hot Pluggable I/O

Addresses Site

Failure/MaintenanceSync/Async Data Mirroring

Eliminates Tape/Disk SPOF

No/Some Data Loss

Application Independent



32/41



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.



33/41



Breaking the Myths..

5.

Mainframes are

inflexible & unableto change quickly

4.

Inability to

find talent as thosewith mainframe

skills retire

3.

ISV enthusiasm

for mainframeapplications is

dwindling

2.

There is nothing

new in the worldof mainframes

1.

Mainframes are

expensive to buy

and operate

5 Myths



34/41



Myth 1Mainframes are expensive to buy and operate



35/41

y gy


Myth 2There is nothing new in the world of mainframes

IBM System z Workload Evolution

Core Business

Enterprise Applications

e-business Solutions

Enterprise Applications

Core Business

e-business Solutions

Business Continuity & Recovery

Linux

Perception of

ComplexityandInflexibility

Inabilityto FindTalent

ISVEnthusiasm

Lackof Innovation

Price-to-Performance

Ratio

PrimaryInhibitors/

Concerns

2



36/41

y gy


Myth 3ISV enthusiasm for mainframe applications is dwindling

Front Office BackOffice

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

Priority System z Selected Business Solutions

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

Core Insurance

BANKING

ACI Carreker IntraNet ARGO China Systems Bottomline S1

SWIFT SAS Mantas Algorithmics SAP PeopleSoft

Risk &Compliance

FIN MKTSINSURANCE

Perception ofComplexityand

Inflexibility

Inabilityto Find

TalentISVEnthusiasm

Lackof Innovation


Ratio

PrimaryInhibitors/Concerns

3



37/41

y gy


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

Resources with mainframeskills are aging

Mainframe resources areexpensive

Mainframe skills are not beingtaught to university students

Middleware-related skills, which are less dependent upon platform, aremost important for the banking industry

Integration and process management requirements within banking result in agreater need for Java/C++ skills over COBOL

Automation and intelligent agents decrease the resources needed to supportmainframe systems

Counterpoints

Competitor Messages

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'ssalary wouldn't be under $100,000, but would be $200,000 to $250,000. Theproblem isn't quite as bad as it seems. There are thousands of new Cobolprogrammers in India, China, and the Philippines. - Ian Archball, Micro Focus1

Salaries for mainframe-based skills are only slightly higher than AIX/Unix-basedskills1% 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 over200 colleges and universities

IBM is teaming with service providers like TCS

Perception of



ISVEnthusiasm

Lackof Innovation


Ratio

PrimaryInhibitors/

Concerns

4

1Source: Mainframe Programmers Wanted, InformationWeek, September 20052Source: Enterprise Systems (www.esj.com), 2005 Salary Survey, August 2005



38/41

y gy


Myth 5Mainframes are inflexible and unable to change quickly

Mainframes are in-flexible andunable to respond quickly tochange

Mainframes provide flexibility through partitioning and workloadmanagement

The mainframe is designed to maximize its capabilities in a multi-workloadenvironment because a major part of the system is dedicated to managing mixedworkloads as opposed to pure processor performance

CounterpointsCompetitor Messages

Mainframes also enjoy the same flexibility benefits of distributed serverenvironments UNIX APIs, J2EE, grid standards and Linux can now be run on mainframes

Perception of



ISVEnthusiasm

Lackof Innovation


Ratio

PrimaryInhibitors/

Concerns

5

Adding permanent processor capacity and storage to a mainframe canoccur 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 torun new workloads alongside existing applications



39/41


Roles in the mainframe world

Operator

Production Control Analyst

System AdministratorSystem Programmer

End User

ApplicationDeveloper

RolesRoles



40/41


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 111 z/Architecture Principles of Operation (POP)

Introduction to the New Mainframe: z/OS Basics
http://www.redbooks.ibm.com/http://www.ibm.com/ibm/historyhttp://www.ibm.com/ibm/history/exhibits/index.htmlhttp://www.ibm.com/ibm/history/exhibits/index.htmlhttp://www.ibm.com/ibm/historyhttp://www.redbooks.ibm.com/


41/41



Questions?

The System z World

Documents