z/TPF Migration

KLM environment and status

Errol Smit – PM z/TPF project

2z/TPF Migration

Agenda

• KLM environment

• z/TPF Project Introduction & Scope

• z/TPF Project Planning & Status

• z/TPF Project Tools

• Q & A

3z/TPF Migration

Current TPF Hardware components

• CPU’s- Production: IBM z9 Enterprise Class (type 506) - 2053 Mips.- Development: IBM z9 Enterprise Class (type 402) – 388 Mips

• Database2 X IBM DS8100 (Production), 1 X IBM DS8100 (Development/Test)

• TapeVTS: IBM TS7700

• TPF operator consoles running on “TPF Operations Server”

• Barr Printer (software) used for console logging test systems

1.94 m

1.50 m

4z/TPF Migration

TPF4.1 usage at KLM:

• Current release is TPF4.1 (PUT 19++ ) at KLM since 1996

• Total approximately 21500 application sources

• Assembler application programs: appr. 67 %

• C/C++ language application programs: appr. 33 %

• TPF connectivity:- Terminals and Printers: appr. 10K+ RES related - Message Switching - Host-to-Host Links: Altéa, AF, NW, WSP e-ticketing, etc.- Misc. non-TPF based KLM applications, e.g. Webfarm

5z/TPF Migration

What functionality?

• TPF at KLM hosts primary applications:- Corda (reservations, fares, ticketing, inventory)- Codeco (check-in, load & balance)- Cargoal (Cargo booking system)- Firda (Flight information)

• TPF at KLM is part of more than 50 service chains among which:- EBT, WebPearl, Bagmanager, Acars, Lido, CISS-Firda, SSCI, ICI, VLC

• For KLM via TPF 66M msgs are processed daily with peaks of 1310 msg/sec. During 2007 the number of msgs increased by 23% despite Altéa.

• An availability of 99,974% over 2007, incl. 25 planned & 6 unplanned downtimes

Moved to Amadeus Altéa RES in 2007

6z/TPF Migration

z/TPF Rationale

• Support of 64-bit z/Architecture IBM mainframes

• Support of new features like encryption, etc.

• The complete Amadeus Altéa Suite (RES/INV/DC) cannot be implemented before 2012 replacing TPF based Corda & Codeco

• Cargoal will be replaced by AF/KL CARGO Ph-II (2013/2014 ?)

• Firda replacement by a non-TPF solution has not been decided

• Workload based licensing instead of mainframe model-based makes z/TPF cheaper to run for KLM

7z/TPF Migration

Overview costs TPF Systems

Overview costs TPF Systems (only)

17%

10%

53%

10%3% 7% Manpower intern

Manpower extern

License costs

Depreciation

Maintenance hardware

Miscellaneous

8z/TPF Migration

z/TPF project scope:

• z/TPF EE 1.1 PUT4+

• KLM TPF Systems and Communications modifications

• Single Source updates TPF applications

• Based upon z/VM V5.3 the introduction of z/Linux Red Hat V5.0 environment for z/TPF purposes

• Migrate Idefix software management system (based upon z/OS V1.8 and USS/HFS) to z/Linux based z/Idefix, including related tools (compilers, loader, etc.)

• Migration of ODF (Online Dump Facility) to z/ODF

9z/TPF Migration

z/TPF Impact on HW infra

• CPU- 10% increase in CPU production capacity required for z/TPF ???- 2 X IFL required for z/VM & z/Linux

• Memory- ± three (3) times the memory requirements of TPF4.1 ???- Extra memory required for z/VM & z/Linux (IFL’s: 8 GB)

• Database- Small impact on TPF DB.- Extra disk space (SAN) for z/VM (2*80 GB) & z/Linux (2*100 GB)

• Tape: No impact

10z/TPF Migration

- z/TPF EE 1.1 PUT4+- TPF GCC- HLASM for zLinux- SST

- z/VM 5.3- Performance toolkit- Dirmaint- RACF- VMBackup- VMTape

- z/Linux RHEL5.0- DB2 Connect- TSM client- Tivoli Enterprise Console Agent- Control-M client??

z/TPF Impact on SW

11z/TPF Migration

z/TPF Project Budget

• Total Manpower estimate: 2532 Working Days- Applications: 481 WD- Systems & Comms: 1457 WD- Training: 171 WD- Project Management: 192 WD- Unforeseen (10%): 231 WD

• Lead time: appr. 20 months incl. 2 months after-care period

• Hardware and software investments:- IFL’s, z/VM, z/Linux, GCC support

12z/TPF Migration

z/TPF Project Milestones

• 17 Sept. 2007: formal start of project

• 30 Jan. 2008: finish Global Designs & Single Source updates

• Mid-feb. 2008: z/Idefix environment ready for project usage

• 1 April 2008: vanilla z/TPF test system up and running- 2 June 2008 incl. basic KLM mods

• 19 Sept. 2008: start integration tests- 13 Oct. 2008 incl. all KLM mods (systems, comms & appl.)

• 1 Jan. 2009: start user acceptance tests

• 21 March 2009: target cut-over date

13z/TPF Migration

z/Idefix Development Tool

• Application development tool for z/TPF integrated in IBM’s TPF Toolkit 3.0 or stand-alone usage

• Windows XP based graphical user-interface (stand-alone)

• z/Linux based server application

• Defect/Feature control (Grips)

• Repository management

• Version management and promotion control

• Compiling and linking

• z/TPF load management (via GDS)

14z/TPF Migration

z/TPF DevelopmentEnvironment

15z/TPF Migration

z/TPF Test Strategy & Tools:

• Requires a freeze period (TBD: 1Q 2009 ?)

• Dedicated z/TPF test system GTI8

• LSAS: Live Size Acceptance System

• Regression / verification tests with a selection of important TPF interfaces / applications (Altéa, Webfarm, etc.)

• TPF Toolkit only partly used (mainly Debugger); z/Idefix tools used

• Stress test tool (Capture & Playback)

• z/ODF (Online Dump Facility)

16z/TPF Migration

z/Online Dump Facility

• To improve the ONLINE problem solving activities in TPF, KLM has implemented an tool called OnLine Dump Facility (OLDF).

• Rel 5.21 will be adapted for z/TPF -> z/ODF (available mid-June)

• Provides the following BASIC capabilities:- Creation of an online displayable MINI-DUMP or SNAPSHOT-DUMP.- Creation of online displayable ERROR-REPORTS and DUMP SUMMARIES.- Registration of occurrences of 'NODUPL' situations in the ERROR-REPORT.- RTA/RTT tape information.- System UP/DOWN information.

• PLUS: Breakpoint facility (part of maintenance release end 2008)

17z/TPF Migration

z/ODF Data Displays

• Error message, PSW, Subsystem

• ECB pages, data fields and macro trace

• (Detached) Data blocks (unformatted and formatted)

• General-, Floating point- and Control registers

• Around registers (80 bytes per addressed area)

• SW00SR and application Stack

• Last C stack frame

• DECB index frames and blocks

18z/TPF Migration

Contacts

• Overall z/TPF project: errol.smit@klm.com

• Single Source migration: michael.bahlen@klm.com

• z/Idefix: john-van.beers@klm.com

• z/ODF: harry.verschure@klm.com

19z/TPF Migration

Summary & Conclusion

• Intended z/TPF cut-over date: 21 March 2009

• Very ambitious schedule, but currently still on target

• If and when realized: after a relatively late start KLM will be one of the first z/TPF airline systems in production !

• We are very interested in exchanging z/TPF migration experiences !

• QUESTIONS ?