MainframeArchitecture@Daimler Extern V1 - IBM · PDF fileMainframe Architecture WilfriedReimann March 2014 Mainframe Outdated Technology? 1886 Benz Patent Motor Car 2014 New Mercedes

MainframeArchitecture

Wilfried Reimann

Head of IT-Enterprise Architecture & [email protected]

Mainframe Architecture Wilfried Reimann March 2014

Mainframe

Outdated Technology?

1886

Benz Patent Motor Car

2014

New Mercedes

After 128 years

1964

IBM System/3602014

IBM zEC 12

After 100 years

2


Mainframe

Agenda

3

1 Daimler

2 IT Facts&Figures

3 Mainframe Datacenter

4 Evolution of Mainframe@Daimler

5 Mainframe Architecture

6 Challenges and Strength of Mainframe

7 Analyst View

8 Mainframe Direction

9Summary and Outlook


Mainframe

Daimler consists of five divisions

11 Company overview

Note: 2013: Revenue Group € 117.982 Bn; Employees: 274,616, Sales organization 52,455, Corporate/Others 6,698

4


Mainframe

Agenda

5

1 Daimler

2 IT Facts&Figures





7 Analyst View




Mainframe

The IT Organization of the Daimler EnterpriseAll IT functions consolidated

ITM

Mercedes Benz

Cars

ITM

Commercial Vehicles

Trucks, Buses & Vans

ITM Daimler

Financial Services

ITM F&C,

Procurement,

Compliance & BI

ITM HR &

COM Systems

Global Information Security

ITM Cross Functions & Chief Technology Officer

ITM SAP & Rollout Shared Service

IT Infrastructure & Operations

6


Mainframe

15

196

1

EMEA &

Germany

NAFTA

APAC

LATAM

Germany

Mexiko,

Monterrey

Indien,

Bangalore

Japan,

Toyama

Südafrika,

East London

Brasilien,

Sao Bernardo

Spanien,

Vitoria

USA,

Portland

IT is the nervous system of DaimlerEvery Day – Any time – Anywhere – 24x7x365

6 continents – >500 sites cross linked – 275,087 employees – 8,421 locations*

*45 concern branches, 62 production locations, 8,314 distribution locations

7


Mainframe

8

Daimler - IT Infrastructure

• Supporting one of the largest auto

companies. Vehicles, production in

6 continents and over 100 plants.

• 275,000 employees using the IT

infrastructure with 190,000 PCs and

other technical devices.

• 4 regional data center areas –

NAFTA, EMEA, Asia/Pac and Latin

America

• Distributed Systems in nearly 100

datacenter locations with Servers

on Windows, Solaris, AIX, HP and

Linux

• 6 mainframe (zOS) datacenters with

high availability

EMEA

APAC

NAFTA

Latin

America


Mainframe

Agenda

9

1 Daimler

2 IT Facts&Figures





7 Analyst View




Mainframe

Mainframe World Datacenter

10

DTNA

(Frightliner)MB-USA

EMEA (Dailmer)

MB-

Brazil

Japan (Former

Mitsubishi)DFS (former

Chrysler)

•Data Center operated by Daimler

•400 application instances

•Increasing use of zLinux generates

substantial savings

NAFTA

•Data Center operated by T-Systems

•2400 application instances, major mission critical

•8 major subsystems with cloud-like governance

EMEA & RoW

•Data Center operated by IBM

•87 application instances

Japan

• For 40 years the mainframe is the work horse for major mission critical applications in engineering,

sales, production, procurement and financial services and is still requested for new applications

• No common global architecture for mainframe across regional mainframe sites

• Data Center operated by

T-Systems Brazil

• 15 application instances

Brazil


Mainframe

Agenda

11

1 Daimler

2 IT Facts&Figures





7 Analyst View




Mainframe

12

Evolution - High Level Mainframe Architecture

New WorkloadBatch Online TransactionProcessing

1970 1990 2000

Multi-Platform Integration“System of Systems”

2010

Ap

p-1

Ap

p-2

Ap

p-3

Ap

p-4

Ap

p-5

System/370

MVS

Ap

p-1

Ap

p-2

Ap

p-3

370/XA

MVS/XA

IDMS

Ap

p-1

Ap

p-2

Ap

p-3

S/390

OS/390

CICS/DB2

Ap

p-1

Ap

p-2

Ap

p-3

Ap

p-4

Ap

p-5

z196

IDMS

CICS

DB2

Java

SOA

WebSphere

DB2

...A

pp

-1

Ap

p-2

Ap

p-3

Ap

p-4

Ap

p-5

System z

z/OS

IDMS

CICS

DB2

SOAWebSpher

DB2...

zLinux z/OS zLinux

x86

zEnterprise

P7

Linux AIX

Op

timiz

ers

Ap

p-6

Ap

p-7

Ap

p-8

Ap

p-9

Ap

p-x

1980


Mainframe

Evolution - Mainframe Architecture EMEA• Applications can run local (plant/sales)

and global (many locations)

• Application development is done central and local in every production and sales organization.

• System-Software (zOS, RACF..) is centrally tested and deployed (SDM Software Deployment Method) to all locations (production and sales)

• Application development environment (CASD Computer Aided Software development) is centrally provided for all tools based on ISPF/CLIST/REXX

• Traditional applications (1970-2000) are build with Cobol/4GL code generators (MPS) and reusable run time components (Basis)

• Batch Jobs are dynamical generated from AJM (Automatic Job Management)

• New Applications have used native JAVA code in combination with Cobol, because Daimlers distributed JAVA-Platforms didn't support zOS

High CPU/Memory usage needs hardware

New Workload

Run-Time

Development

CICS/DB2

Basis/AJM App-4

App-5

App-6

Batch

App-1

App-2

App-3

App-4

App-5

• DB2• Object Oriented• TCP/HTTP• JAVA• WebSphere• WebServices• SOA

IDMS DC

Basis/AJM

App-1

App-2

App-3

Shared Data Architecture

1970 1990 2000

P l a n t s

Sales CountriesReusable

Components

1980

CASD/MPSTSO

13


Mainframe

Agenda

14

1 Daimler

2 IT Facts&Figures





7 Analyst View




Mainframe

Mainframe Architecture 1980–95 : many are still in place

Cobol Systems for IDMS und DB2 are developed with: • Source-Code generators, which generate compliable code for COBOL IDMS/DC/DB and CICS/DB2• Applications are developed as a set of functions with a common reusable structure, which are implemented by

generated code and reusable Basis-Run-Time• Most (70%+) of the execution code is based on reusable components (Application-Control, DB-Control, Security, UI,

Language, Printing, Scrollable Maps etc.)• 1000 Applications (200 MioLoC) are implemented in this architecture, more than 70% exists today

Cobol-Programmer

edits Business-Logik

MPS-Generator

Generated

Cobol-Program

MPS-Macros

Basis-SystemRun-Time 100 Modules

Reusable Modules &

Components

Application-1 (e.g. GO with 4000 functions)

Function-1

Function-2

Function-N

Application-2 (e.g. ZEM with 200 functions)

Function-1

Function-2

Function-N

Deployment to

Production

Production Environment IDMSDC/DB or CICS/DB2

Basis

DB

Database App-1 Database App-2

Development-Environment

15


Mainframe

16

JAVA Enterprise Platforms since 2001 (UNIX, LINUX, Windows) –

more than 200 applications

• Built on a firm foundation of standards such as J2EE, XML and Web Services

• New products and technologies could be added or changed with minimal impact to the applications.

• Closes the gap between application development and operations.

• Ongoing series of product releases subject to constant evolution.

• IT-Customers gain access to the leading edge technology built into the platform

• DC’s (Technology) SOA-Foundation

PAI based Development & Operations

App-1

PAI-Platforms

J2EE, XML, Web Services

Microsoft

HPOpen Source

• WebSphere Application Server

• WebSphere Portal

• WebSphere Broker

• WebSphere Process Server

• WebSphere MQ Workflow

• DB2 Universal Database

• Rational Development Tools

• AIX

App-2 App-3 App-4 App-5


Mainframe

Architecture Change of Mainframe-Application (VEGA)

17

19982 tier Architecture

20012,5 tier Architecture

2005:3 tier Architecture

2013:

Multi tier

Architecture

Client/Server Architecture

Server: OS390/CICS/COBOL/DB2

Only IBM could guarantee non

functional requirements

Frontend:

• Smalltalk Client (MPC)

• Dealer frontend 3270 (Daimler-

Network, because PC/Smalltalk

to instable)

Communication:

• Communication over „Service

Request Manager“ (ECI –

Extended CICS Interface)

Client/Server Architecture

Server: zOS/CICS/COBOL/DB2

UNIX/Java

Frontend:

• MPC frontend (Smalltalk)

• Dealer frontend (JAVA Browser)

Communication:




• RPC TCP/IP

3-Tier Architecture

Server:

• zOS/CICS/COBOL/DB2

• UNIX/Java, PAI-J2EE, UDB

Frontend:

• MPC frontend (PAI-JAVA, rich

client)


Communication:




• RPC TCP/IP

Multi-Tier Architecture

Server:

• zOS/CICS/COBOL/DB2

• UNIX/PAI-J2EE/UDB

WebServices, XML Platform

Frontend:

• MPC frontend (PAI-JAVA, rich

client)


Communication:

• RPC, SOAP, XML


Mainframe

Mercedes Cars Global Ordering System – Pure zOS based with COBOL and JAVA

18

GO Application Core

(COBOL/CICS)

Zugangsschicht

(GO Dispatcher)

GO Application Core Java

WebServer

ISPD GCC DB

Externe

Systeme

JEE Webbridge

RACF

(Auth.)

Basis

GO-Client

(Java)

WebServiceWebService

Consumer

(z.B: POS, CESAR)

http(s)

https

Advantage

• High scalability

• High security

• Best performance

• High Availability

• Best reliability

• Very secure environment

Challenge

• Price for Operations

• Modernization of COBOL

• Skills 2020+

• Innovation (JAVA, BigData)


Mainframe

Agenda

19

1 Daimler

2 IT Facts&Figures





7 Analyst View




Mainframe

Mainframe Strength

•IMS, IDMS, etc. only on MF

•CICS, Cobol, etc. only advised on MFLegacy technologies

•Goals in some cases only possible on zOS

•High transaction rates (esp. write operations)DB2 Performance

•extensive self-checking and self-recovery capabilities

•software has ability to make quick updatesReliability

•High application and data availability out of the box

•Advanced modular Disaster Recovery capabilitiesAvailability

•Advanced failure detection (predictive Maintenance)

•Replacement of HW/SW with minimal operational impactServiceability

•Horizontal and vertical for non-disruptive growth (HW+SW)

•Workload management across all applications Scalability

•Continuing compatibility

•Strong governance across all applications enforced and accepted

Software License Management

•Highest isolation level in industry for logical partitions

•No viruses known yetSecurity

20


Mainframe

Mainframe weakness – Innovation Adoption

Adoption Daimler EMEA

Adoption Daimler NAFTA

Technology Availability

21


Mainframe

Agenda

22

1 Daimler

2 IT Facts&Figures





7 Analyst View




Mainframe

Mainframe Renaissance – Analyst View

• MIPS grew by 300% from 3.5m in 2000 to 14m

in 2008 when the z10 was introduced

• Worldwide installed base of 15,000 sites

• 80% of worlds electronic transactions in Banks,

Insurance Companies and Governments are run

on mainframes

Analyst 2011:

� „Linux MIPS [...] now represents

approximately 20% of the installed MIPS.”

� “Expect Linux to remain a cornerstone of

IBM's mainframe value proposition,

� “Recommendation: Consolidate distributed

servers to mainframe IFLs when the ratios

are greater than 20-to-1 and the software is

priced on a per-processor basis.”

Analyst 2014:

• 73 of the 75 largest banks use System z − But Amazon, Google, Facebook, Salesforce do not

− More mainframe MIPS installed than at any point in

history

− But increasingly concentrated in fewer orgs

• It’s increasingly a scale out world − Yet Linux on z continues to grow

23


Mainframe

Daimlers conclusion out of analyst workshops

Market • We believe companies over 20,000 MIPS remain on the mainframe

• The market moves away from workloads under 5000 MIPS

Positioning • the mainframe platform is [required for its] reliability, availability and

serviceability

• Large mainframe shops [..] remain on this platform because the costs

and risks of moving are more than they are able to justify.

Strategy

Recommendation

• If you stay, invest in your skills. Do not totally rely on market and/or

provider.

• Mainframe governance needs to be done at enterprise level. Define

mainframe position in Enterprise !

Technical

Recommendation

• Get rid of pre-relational databases (e.g. IDMS, IMS) depending on

Enterprise Architecture definition.

• Define which existing systems can be moved to Java, and do it.

24


Mainframe

Agenda

25

1 Daimler

2 IT Facts&Figures





7 Analyst View




Mainframe

Mainframe Direction 2014:

Bring Mainframe Back into Fair Competition of Platforms

Innovation happens on

mainframe at

competetive pricing

Charge model supports

mainframe strategy

and innovation

Position mainframe to

provide direction for

strategic initiatives

Goals Core Aspects

� Fulfill business requirements (e.g. from business intelligence, Mobile

Computing Strategy)

� Leverage synergies from global collaboration (i.e. EMEA/NAFTA)

� Use innovations on the mainframe, which are available today (SOA

backbone, Web application server, zLinux, etc.)

� Available budget spendings support overall goals

� Mainframe will be attractive for modern applications and increasing

workload (prevent cost explosion)

� Decisions about application landscape planning and platform

selection consider overall costs

� Strategic projects have a reliable positioning for mid-term and long-

term planning

� Unaligned individual opinions will be stream-lined by strategic

direction

� Decisions about application landscape planning are done across

technology silos

26


Mainframe

Agenda

27

1 Daimler

2 IT Facts&Figures





7 Analyst View


9 Summary and Outlook


Mainframe

28

Mainframe– Summary and Outlook

•Since more than 40 years the mainframe is the work horse for

core business applications in engineering, sales,

production/logistics, procurement and financial services and is

still requested for new application development.

•Mainframe technology is still a unique solution for “extreme

transaction processing (XTP)” enabling the implementation of

large-scale, business-critical, transactional applications with high

availability and Zero-Down-Time requirements

•Skills for the existing mainframe applications and future XTP-Like

application will be critical for the mainframe future

•Current mainframe (at Daimler) has limited usage of new

technologies this will be improved step by step

•Mainframe consolidation will go on

•Common global architecture for mainframe will be addressed

in future

•Application development on JAVA will grow in future and will

be the standard beside COBOL


Mainframe

29

Thank You

Documents

MainframeArchitecture@Daimler Extern V1 - IBM · PDF fileMainframe Architecture WilfriedReimann March 2014 Mainframe Outdated Technology? 1886 Benz Patent Motor Car 2014 New Mercedes