Plan for Porting and Enhancing TPF Software Tools for zTPF

Contents Where We Are Why Travel? Overview of the Trip Where We’re Going Assumptions Loading Programs and Testing Beyond zTPF

Where We Are: Seeing the Big Picture It’s easy to miss the big picture when you work with pieces of the puzzle Likewise, when you think about products and features, it’s easy to miss the big picture about TPF Software tools CMSTPF TReX SOURCE VIEW TPF/IDE TPF/GI CTFS RTF

What’s the Essence? More than a collection of parts… These products work with features you never think about.. To form a comprehensive Test Management System TPF/GI TPF/IDE TReX CTFS RTF SOURCE VIEW VM/CMS Unseen Kernel Features CMSTPF TReX SOURCE VIEW TPF/IDE TPF/GI CTFS RTF

A Comprehensive Test Management System System resource management Development environment Graphical interface for debugging Connectivity Regression testing Transaction analysis TPF/IDE TReX VM/CMS TPF/GI CTFS SOURCE VIEW RTF

The Test Management System Kernel Is More Than A Debugger Inside the VM/CMS Kernel TPF/IDE TReX APM Server (daemon) Security--User validation Worker machines On-demand resources Debugger Shared Memory Management Shared storage between workers Reduces VM paging Fast IPL or Startup Management TPF Simulator CPU Management Use CPU only when transactions are running No CPU usage during idle state VM/CMS TPF/GI CTFS SOURCE VIEW RTF

VM/CMS High-Level Flow User connects through TPF/GI APM Server starts worker machine ACF/RACF Logon is verified The system is loaded using Shared Memory During testing, CPU Manager minimizes use of CPU Provides cost savings User disconnects APM Server disposes of worker machine automatically TPF/GI APM Server Worker Machine CPU Manager Shared memory VM/CMS

Why Travel? QUESTION: Why not keep things the same? Why not stay in the “same place” and keep enhancing the Test Management System?

Why Travel? TWO ANSWERS: Customers are moving to zTPF zTPF requires major changes to the base TPF product This requires major changes to the kernel of TPF Software’s test management system TPF as an operating system is more stable Because of this, we can rebuild the kernel and potentially serve more TPF users

Overview of the Trip Starting here Finishing here VM/CMS VM/VPARS TPF/GI TPF/IDE TReX CTFS RTF SOURCE VIEW VM/CMS TPF/IDE TReX TPF/GI TPF/IDE TReX TTFS RTF SOURCE VIEW VM/VPARS VM/CMS TPF/GI CTFS SOURCE VIEW RTF

Overview of the Trip Kernel moves from VM/CMS to VM/VPARS VM/CMS TPF/GI TPF/IDE TReX CTFS RTF SOURCE VIEW TTFS VM/CMS VM/VPARS

Overview of the Trip Products remain the same or are enhanced = VM/CMS TPF/IDE TReX TPF/IDE TReX VM/CMS VM/VPARS TPF/GI CTFS zTPF/GI TTFS = SOURCE VIEW RTF SOURCE VIEW RTF

TPF/GI Sample Feature Comparison VM/CMS VM/VPARS Graphical ECB  Source View for SabreTalk, C/C++, Assembler Integrated Terminal Emulation Message Run/Capture/Log Macro/Instruction trace add Suitable for System Programmers Eclipse Plug-In Available

Other Products Feature/Product VM/CMS VM/VPARS RTF  TPF/IDE GI/TERM Connectivity to Remote Resources (CTFS) (TTFS) TREX

A New Kernel for the Same Comprehensive Test Management System Inside the VM/VPARS Kernel TPF/IDE TReX APM Server Handles connectivity and security Worker machines On-demand resources Debugger Shared Segment Management Shared storage between workers Reduces VM paging Startup Management No TPF Simulator  Real TPF CPU Management Use CPU only when transactions are running No CPU usage during idle state VM/VPARS TPF/GI TTFS SOURCE VIEW RTF

zTPF High-Level Flow User connects through zTPF/GI VM Logon is verified APM Server starts Product Worker machine Product Worker Validates accessibility Connects to zTPF/VPARS Acts as intermediary between zTPF/GI and zTPF/VPARS Responsible for file information User disconnects Product worker goes away zTPF/GI goes away Product Worker APM Server zTPF/VPARS zVM

Overall Architecture Client/Server Uses Worker Machines PC Client/Server Uses Worker Machines Work distributed across 3 platforms PC Worker (VM) zTPF TSS is TPF Software Infrastructure Services Product A Client Product B Client zVM Product A Worker Product B Worker zTPF TSS Product A Server Product B Server

Advantages of Three-Part Structure PC PC Graphical Presentation VM Worker Security/Configuration File access Customizable Exits zTPF Execution of code to be tested, viewed, etc. Product A Client Product B Client VM Product A Worker Product B Worker zTPF TSS Product A Server Product B Server

Configuration Configuration information will be supplied by a combination of configuration files user exits (REXX execs) Etc. User Product System Project

User Configuration Resources (VPARS) user is allowed to get to Products user is allowed to access Terminal information for user User-level security File information for user Where will his/her files reside (path information) User Product System Project

Product Configuration Authorization info about product, e.g. … Product not valid on Production Product valid only Read mode File information for Product-associated files This is the path information Ex. For DF/Explorer – path for the panels Ex. For TPFGI – path for SV files Etc. Other User Product System Project

System Configuration System definition – Prod/Test/Private User limits (how many allowed for this VPARS) List of valid products authorized on this VPARS File Information Where are panels How to load – default Where to get source – for SV tracing Etc. IP address of System (VPARS) Port where TSS should listen for requests User Product System Project

Project Configuration Project definitions Other project info Private/Public project File information for project Will have path for project files Etc. User Product System Project

Assumptions

TPF Assumptions Network Customer must have automation to bring zTPF to NORM state Customer must have an IP address defined for that zTPF When zTPF comes up TSS (TPF Software Infrastructure Services) will automatically be activated TSS would read the System Configuration TSS will bring up products that are defined for that zTPF Both TPF Debugger and our debugger can run at the same time zTPF in Norm State TSS TPF Debugger DFExp zTPF/GI

ü ü ü ü zVM Assumptions zVM Customer must install APM Server Customer must define Worker machines Customer needs to allocate unique Terminal Addresses for each user (user exits available – and will be called when the USER CONFIG file is being read) Customer responsible for these User Exits (REXX) ü APM Server ü Worker Machine Definitions ü Terminal Definitions ü User Exits

TPF Control Program Changes We are using the standard IBM user-exits We will ship E-type code and C-type code C-type code will plug directly into IBM exits E-type code will be our kernel and software

Loading Programs and Testing

If You Use TPF/Toolkit for Development… Programs must be moved to VPARS so they can be loaded Edit, Compile, Transfer This is customer responsibility Path for Source Customer provides source path info through the Compiler or through Worker User Exits zTPFGI will have functions to Display programs loaded by user Load a program for a specific user Fallback a program for a specific user zLinux zTPF Product Worker User Exits TPF Toolkit zTPF/GI

If You Use TPF/IDE for Development TPFIDE will Edit, Compile and Transfer AND Provide source location info zTPFGI will have functions to Display programs loaded by user Load a program for a specific user Fallback a program for a specific user zLinux or zVM zTPF Product Worker TPF/IDE zTPF/GI

Delivery Roadmap Version 1 Version 2 Version 3 Kernel running under VM/VPARS Debugger, APMServer, etc. Version 2 Faster startup or IPL Shared Segment Management Version 3 CPU management Private VPARS for each user 1 2 3

Beyond zTPF: Other Exciting New Platforms for TPF Software products…

TPF/GI iPhone Edition Featuring our patented new ECB to MP3 converter

TPF/IDE Tivo Interface Fix Single Source issues while watching “American Idol”

Regression Test Facility Now Bundled With Guitar Hero II See! It’s True! Now with RTF!

Questions & Feedback We want to know your questions and issues so we can address them Any special requirements we didn’t cover?