Jürgen Ley Brandmanagement IBM Stuttgart

Jürgen Ley Brandmanagement IBM Stuttgart
IBM System z ™ mit z/OS Aktuelle News, Previews und Trends Lahnstein 06. April 2006 Jürgen Ley Brandmanagement IBM Stuttgart

Agenda Einleitung z/OS 1.8 Preview Zukünftige Ausrichtung System z
Innovation für System z Neue Rolle im Unternehmen z/OS 1.8 Preview Zukünftige Ausrichtung System z Dataserving SOA Transformation Zukünftige Direction IBM z/Architecture™

Mainframe-Plattform mit aktueller Software
Innovation durch Kollaboration Nutzen des Mainframes Information On Demand SOA / Enterprise Transformation IT Service Management DATEN ANWENDUNGEN INFRASTRUKTUR Information Flexibilität Nutzen Daten Insight Value of the Mainframe - This is the umbrella message we should weave throughout all of our messaging to remind customers why they originally invested in the mainframe, why it was a good choice then and why it is an even better choice now. It should cover how the hardware, operating system, middleware and tools all work together to drive a cost effective platform for existing applications as well as new deployment. This messaging would probably be directed at all departments within a zSeries account but would probably focus on IT Management and above that those with cross IT discipline responsibility who can see the value of all the "moving parts". zSeries Currency - This covers the value of individual middleware components and how they exploit the zSeries platform in order to deliver the promise of the three major themes. This is probably most effectively addressed to practitioners with an IT discipline, those interested in the value of DB2 for example. However, we should always tie the individual middleware value back to the overall Value of the Mainframe. SOA Enable SOA, delivering business flexibility through integration and transformation within and beyond the enterprise-core systems, applications, data and skills to be reused in end-to-end, cross-platform solutions to create new business processes and end-user applications ITSM Continually adjust the end-to-end zSeries IT service management infrastructure to deliver high-performance in a volatile business climate IOD Leverage existing information assets with database and database management tools Mainframe-Plattform mit aktueller Software

Organisatorischen Barrieren entfernen
Phase Phase 1 OnDemand Organisation IT Organisation OLTP Datenbank Serving Ausfallsicherheit Business Sicherheit Business Prozess Integration Workload Integration Hosted Client Datenanalyse Storage Bestand Anwendungen “Verteilte Systeme” Web Serving & Internet Access Business Intelligence Storage Area Networks Schnelle Anwendungsentwicklung “gerade gut genug” Linux, Windows, UNIX, zSeries Message is that we have to encourage our customers to break down political barriers. As you go through the screen show, I have a Red line, to represent two separate organizations. I added a yellow dashed line, for things like the introduction of Communication Server on zSeries Linux to reduce 3745 expense. The problem with that one is that the 3745 is probably funded out of the mainframe community, so they need to "beg for skills" out of the "open systems" community to get the benefits. But we need that first step to occur. But then I made it a green box around the entire organization as you begin to wrestle with all the possibilities of sharing across the communities. z/OS, zLinux and zVM (my zSeries label) combined with the Intel/RISC world. There is no right model, but ultimate success will come when our customers start to break down these political barriers.

Innovation durch Kollaboration Erweiterter Service des Mainframes für das Unternehmen
Vier unternehmensweite Rollen des Mainframe Systems Manager der Ausfallsicherheit für Businessprozesse Management Sicherheit Workload Management Data Serving Hub für Daten & SOA

Unternehmensweites Management Business-Ausfallsicherheit
Mainframe Architektur Silo Architektur GDPS Kapazitäts- Backup Hohe System z9 Widerstands-fähigkeit Spezielle Engines (Linux & Java) GDPS Ein Managementpunkt Business driven - Managementregeln Prioritätssteuerung Effizientes Backup Volle Redundanz & gespiegelte Fähigkeiten Anwendungs-server When slide appears: Describe current environment & issues with distributed / siloed architecture – include thoughts on costs and risks added by continuing on this route ( cost of down time, data loss, recovery time….) Multiple tiers to manage Varying systems management policies Multiple failure points Incomplete backup Little built in redundancy On First Click: Using a mainframe architecture, you recognize the traditional benefits of the environment with industry leading Availability, resiliency, & management……. Working together with our SWG partners like Tivoli, the new System z9 continues that tradition, with capacity backup, new features that further enhance the platforms resiliency and the ability, through our specialty engines to run Linux and Java workloads natively in this environment. Discuss some of the key points delivered Single management point Business driven policy management Priority control Efficient backup Fully redundant & mirrored capabilities On second Click A primary example of the resiliency provided by the System z9 is delivered through GDPS….. Describe what it can do in the native MF environment On Third Click In the future as we expand the capabilities of GDPS, you can automate UNIX and Windows tiers....etc. based on standards, open interfaces , allowing a single point of management. Datenbank Server

Unternehmensweites Management Sicherheit
Netz Edge/Web Anwendung Daten/Transaktion RACF Tivoli Vanguard Encryption Appliances Mehrere Angriffspunkte Tape Subsysteme Because of the global marketplace and the Net, every institution today has far greater contact with the world -- access to more markets and information, exposure to more threats, and a rapid fire competitive environment. In the traditional operating environment, there are many points of vulnerability for security point of view. Mehrere Sicherheitsdatenbanken Mehrere Sign on Unterschiedliche Regeln Mehrere Angriffspunkte Multi-step Verschlüsselung Verteiltes Schlüsselmanagement

Unternehmensweites Management Sicherheit
Netz Edge/Web Anwendung Daten/Transaktion RACF Tivoli Vanguard RACF Sicherheit Encryption Facility for z/OS Encryption Appliances Mehrere Angriffspunkte Tape Subsysteme Because of the global marketplace and the Net, every institution today has far greater contact with the world -- access to more markets and information, exposure to more threats, and a rapid fire competitive environment. In the traditional operating environment, there are many points of vulnerability for security point of view. Einheitliche Sicherheitsdatenbank Ein Sign on Begrenzte Sicherheitsrisiken Business driven Regeln Integrierte Verschlüsselung Unternehmensweites Schlüsselmanagement

Unternehmensweites Workload Management
Network Edge/Web Application Data/Transaction EWLM RDS Because of the global marketplace and the Net, every institution today has far greater contact with the world -- access to more markets and information, exposure to more threats, and a rapid fire competitive environment. In the traditional operating environment, there are many points of vulnerability for security point of view. Kein Überblick über end to end Workloads Ungenutzte Ressourcen Unbalancierte Ressource Nutzung Technologie getriebene SLA

Unternehmensweites Workload Management
Network Edge/Web Application Data/Transaction EWLM RDS Virtualization Engine VE Release 2 Discover Monitor Manage Because of the global marketplace and the Net, every institution today has far greater contact with the world -- access to more markets and information, exposure to more threats, and a rapid fire competitive environment. In the traditional operating environment, there are many points of vulnerability for security point of view. Monitoring Workload end to end Höchste Nutzung der Industrie Ausbalancieren der Workload bei heterogenen Plattformen Business Ziele mit SLA

Komplexität der Infrastruktur: Verdeckte Kosten
UI Data DNS Servers Web Servers Application Security & Directory Servers File/Print LAN Servers Database Business Data PCs UNIX Mainframe

Infrastructure Simplification: Optimizing I/T Operations
UI Data DNS Servers Web Servers Application Security & Directory Servers File/Print LAN Servers Database Business Data PCs UNIX Mainframe Heterogenes Mgmt und Virtualisierung BladeCenter zSeries Mainframe Enterprise Virtualisierungs Struktur Transaction Data Reference Backup SAN Storage Databank, Transaktion und Enterprise Mgmt Server p / i Series Servers Heterogener end-to-end Support Offene & Industrie Standards Geschäftsprozess getrieben Autonom Anwendungs Server WebServices Distributed Management Server Cluster N/W Storage CIM Native VMWare MSVS

Server Partitionierung und Virtualisierung
Eine wichtige Betrachtung für alle Gebiete eines Server-Designs und Bereitstellung Prozessor Design Workload Management I/O Architektur On/Off Capacity on Demand Partitioning und Virtualisierung Sicherheit Server Provisioning Software Lizensierung Systems Management © 2006 IBM Corporation

Partitioning Definition
Partitioning ist die Aufteilung eines Servers und der einzelnen Ressourcen* in mehrere, unabhängige, isolierte Systeme, die dann mit eigenem Operating System fahren. Drei Typen des Partitioning: Hardware – Allokation der Ressourcen zu Partitions in einer eins zu eins Basis mit der darunterliegenden physischen Hardware (kein Sharing unter Partitions) Logisch – Ressourcen werden gemanaged durch Hardware-Firmware und Allokation zu Partitions mit feinerer Granularität als Hardware Partitioning (Ressource Sharing zwischen Partitions) Software – Ressourcen werden gemanaged durch Software Layer, aggregiert in gemeinsam genutzten Ressource Pools und aufgeteilt auf Benutzer als virtuelle Systemressource mit Trennung der Ressourcen von aktuellen physischen Entities * Resources include: processors, memory, I/O adapters and devices, networking interfaces, co-processors © 2006 IBM Corporation

Hypervisor Technologie
“Trapping and Mapping” Methode Guest OS läuft im Usermode Hypervisor läuft im privileged Mode Privilegierte Instruktionen des Gast Operating System(s) werden durch Hpervisor ‘getrapped’ IA-32 (Intel) Komplikationen: Einige Instruktionen verhalten sich unterschiedlich im privilegiertem und User Mode Z.B. “POPF” Behandlung eines Interrupt enabled Flags ‘User mode Instructions that access privileged resources/state cannot be trapped; instruction must be changed to something that can be trapped’ Einige Guest Kernel Binary Translations können erforderlich werden Ursprünglich wurde dies von Mainframes in 1960 iger und 1970 iger (VM/370) verwendet Heute benutzt durch VMware There are 19 instructions in IA-32 that cause virtualization problems: they behave differently in user mode vs. privileged mode. The instructions are not privilege mode instructions. The hypervisor must account for these instructions. This is not a zSeries problem. The S/390 and z/Architecture are very much aware of the need to accommodate layers of virtualization. Binary translation means the hypervisor must scan the guest kernel and replace offending instructions (e.g., POPF) with something else. © 2006 IBM Corporation

Hypervisor Technologie
Hypervisor Call Method (“Paravirtualization”) Gast OS läuft im privilegierten Mode Hypervisor läuft im super-privilegiertem Mode Gast OS Kernel (z.B. AIX, i5/OS, Linux) ist modifiziert, um Hypervisor Calls für I/O, Memory Management, ‘yield rest of time slice’ usw. zu machen Memory Mapping Architektur wird benutzt zur Isolation des Gasts von anderen und zum Schutz des Hypervisors Benutzt heute POWER5 © 2006 IBM Corporation

Hypervisor Technologien
Direkter Hardware-Support Methode Gast OS läuft im privilegiertem Mode Gast OS läuft unmodifiziert, kann aber einige Hypervisor Calls absetzen zur Verbesserung der Performance oder für bestimmte Funktionen I/O (z/VM) Yield time slice (PR/SMTM und z/VM) Extensive Hardware Assists für Hypervisor (Virtual Processor Dispatching, I/O Pass-through, Memory Partitioning, usw.) Benutzt durch System z und zSeries (PR/SMTM und z/VM) Yielding time slice allows the hypervisor to dispatch another virtual processor belonging to the guest image. IBM z/Architecture™ © 2006 IBM Corporation

Der Nutzen der System z9 und zSeries Virtualisierung
Ersatz für einen oder mehrere physische Server durch einen virtuellen Server Gemeinsame Ressourcen mit hohem Nutzungsgrad Server-Ressourcen werden dynamisch zugeordnet basierend auf Demand Zusätzliche verfügbare Kapazität zur Bedienung von unvorhersehbaren Fluktuationen auch für geplante Upgrades Vorteile durch Virtualisierung… Kosten – Reduzierung der Kosten und der Management Kosten Konsolidierung – weniger Server, die mehr tun Hoher Nutzungsgrad – Fähigkeit für Handhabung hoher Workloads und mehrerer Anwendungen auf einem System Standardisierung – Standard Management Tools cross unterschiedlicher Lastumgebungen Automation – Ersetzt manuelle Prozesse für Steuerung und Kontrolle für Infrastrukturmanagement Integration – Enge Kollaboration cross im Unternehmen mit hoher Effizienz und Wirtschaftlichkeit There is nothing mystical about the solution needed to address these concerns: virtualization. Virtualizing some portion of the physical infrastructure to alleviate the management burden on internal personnel and the cost of maintaining a large number of servers. Virtual servers, located offsite and accessible via the network (VPN or frame relay), share the application workload. Resources are pooled and allocated dynamically as needed so there is never a shortage of capacity. When a surge occurs, excess capacity is directed to the application that needs it. Virtualization enables you to achieve a variety of common business objectives. You can consolidate the number of servers that comprise your infrastructure because virtual servers have the capability to work harder and smarter. They are able to handle increased workloads more efficiently. That means servers can handle multiple applications, enabling you to increase server utilization. With disparate management tools and business processes used across the enterprise, each business unit may require its own staff to handle administration. Management tools purchased and implemented on an ad hoc basis can result in a very complex work environment. Virtualization allows companies to implement a standardized toolset, restoring some order and reducing the cost and complexity of managing an IT environment. Virtualization enables standard tools and processes to be applied across heterogeneous work environments. Virtualization also facilitates the implementation of automated business processes, such as resource provisioning. Instead of the manual effort and time typically taken to handle functions like provisioning, automation enables them to be handled more simply and with fewer personnel. Finally, virtualization facilitates integration across the enterprise, enabling formerly isolated business units to work together. In a virtualized environment, individual business units can share capacity resources with less waste. With resources pooled, individual workloads can be handled by common hardware. This results in greater operating efficiencies and economies of scale.

Unternehmensweiter Hub für Daten & SOA
Client 1st Tier 2nd Tier IMS CICS DB2 Standard CP AFTER Integrated z/OS Application & Database Servicing z/OS zAAP & IFL fähig Unternehmensweiter Hub für Daten & SOA Vorher Networked Web Serving 1st Tier 2nd Tier 3rd Tier Data Power WAS zAAP zIIP Client App Server IFL Linux Integrated Application & Database Server z/OS Database Server Client App Server Client Multiple Data Copies Single Data View Vorteile der Konsolidierung der Anwendungs- und Datenservices Sicherheit Weniger Angriffpunkte Widerstandfähigkeit Weniger Fehlerpunkte Performance Vermeidung der netz Latency Betrieb Weniger Teile zu managen Umgebung Weniger Hardware Key Point of Chart** By continuing to introduce, feature and leverage leading edge technology, System z is the optimal platform for consolidating and optimizing distributed implementations into an enterprise hub that is a simplified, tightly integrated and single tier environment. As a result, customers can take advantage of 40 years of proven high performance, reliability, availability, and security for their data and “services” at an affordable cost. Co-location of the database and application server provides both operational and performance advantages over a physically separated multi-tier solution. These advantages come not only in the elimination of TCP/IP and the associated latency but also in the tight security integration, and most importantly the ability to run the transactions using native z/OS services rather than a distributed 2 phase commit protocol. The introduction of specialty engines like the IFL, zAAP and zIIP can help simplify and reduce complexity of a server infrastructure and improve operational efficiencies as the illustration on the right suggests. Integrated Facility for Linux The IFL (Integrated Facility for Linux) is a hardware processor engine specifically configured to run Linux workloads, including those managed by z/VM. IFL's enable customers to consolidate distributed workloads on IBM's most reliable platform, and provides secure, close proximity to z/OS workloads. When used with z/VM, customers have a flexible, virtual processing environment that runs multiple workloads and multiple Linux environments, allowing the mainframe to act as the hub of the enterprise, and simplifying enterprise architecture and introducing advantages of consolidation such as improved Security, Resilience, Performance, Operations and Environmental factors. What are the System z Application Assist Processor (or zAAP for short) and System z9 Integrated Information Processor (zIIP for short)? The zAAP is an attractively priced, specialty workload processor available on the z890, z990 and z9-109 that provides a specialized z/OS Java execution environment for customers who desire the powerful integration advantages and traditional Qualities of Service and core strengths of the “ z” platform. Dedicated to z/OS JAVA execution, it enables you to integrate e-business java workloads with core business applications and data, safely, securely efficiently and cost effectively. The IBM System z9 Integrated Information Processor (IBM zIIP), is a new specialty engine for the System z9 Mainframe that is designed to help customers integrate data across the enterprise and improve resource optimization and lower cost of ownership for eligible data serving workloads. z/OS manages and directs work between the general purpose processor and the zIIP. There are no changes required to applications in order to exploit the zIIP. This is enabled by DB2 for z/OS V8. There are three types of workloads that may benefit from zIIP 1. ERP or CRM Data Serving 2. Data Warehousing applications 3. Some DB2 for z/OS V8 Utilities The zAAP and zIIP provide further benefits when used to consolidate applications and data. The bring the same advantages provided by the IFL but also contribute, improvements in Utilization, Scalability, Auditability, Simplification, and Transaction Integrity. Vorteile mit IFL Vorteile mit zAAP & zIIP Nutzung Effiziente Nutzung der Ressourcen Skalierbarkeit Batch und Transaktionsverarbeitung Auditability Konsistente Identität Vereinfachung Problemerkennung/Diagnose Integrität der Transaktion Automatische Recovery/Rollback

Keine Softwaregebühren für spezielle Engines
Dieser Kunde bezahlt für weniger als 3 Engines für z/OS und CICS (obwohl er 8 Engines nutzt) Mehr Workload auf z! Gebühren basierend auf MSUs* keine Gebühren Gebühren pro Prozessor** C I S I M S D B 2 C I S D B 2 W A S J V M J V M L i n u x L i n u x L i n u x L i n u x L i n u x z/OS z/OS z/VM V5 LPAR LPAR LPAR LPAR CP0 CP1 CP2 ZP1 ZP1 LN0 LN1 LN2 Spare SAP Standard Prozessor Engines zAAPs, zIIPs IFL Engines System z9 * Basierend auf MIPs ** oder “Engine”

Preview z/OS 1.8 (Ankündigung 21.2.2006) Ausbau Mainframe Leadership
Geplante Verfügbarkeit September 2006 Heterogeneous Integration Workload Manage-ment Business Resiliency & Security Heterogeneous enterprise Virtualisierung IT Vereinfachung VERFÜGBARKEIT Granulare Optionen für Fast Replication von Daten Erhöhte Sysplex Resiliency und Recovery SICHERHEIT Fortschritt beim Management Digitaler Zertifikate, Netzverschlüsselung und RACF NETZVERARBEITUNG Erhöhte Automation im Sysplex Support für WTS Clients, SAMBA für Linux Clients OPTIMIERUNG Verbessertes I/O Prioritäts-Handling für Bandeinheiten Verbessertes WLM Management von zAAP Workloads APPLICATION INTEGRATION Support für Industrie und de facto Standards Optimierter LDAP Directory Server für Konsolidierung Vereinfachung z/OS Management Mehr Checks im Health Checker for z/OS Hilfe bei Konfiguration für IPv6 Verbesserte unternehmensweites Ressource Management Bessere Integration zwischen z/OS WLM und Enterprise Workload Manager (EWLM) * All statements regarding IBM future direction and intent are subject to change or withdrawal without notice, and represents goals and objectives only.

z/OS Support Summary z890 z900 z800 z/OS 1.1 1.2 1.3 1.4 1.5 1.6 1.7 x
G5/G6 Multiprise ® 3000 z890 z900 z800 z/OS 1.1 1.2 1.3 1.4 1.5 1.6 1.7 x xc x1 z990 End of Service Coexists with z/OS... Planned Ship Date DS8000 DS6000 3/04 10/04 3/05 3/07 1.8 9/07 9/08* 1.9* 9/05* z9-109 1.8* 9/09* 1.10* 9/06* 9/10* 1.11* 9/07* This chart summarizes much of the information about z/OS that you need to know. Server and DASD hardware support, end of service dates, coexistence, and planned availability dates are shown here for existing and planned releases through z/OS R9. Note that: The lowest supported level of z/OS is R4 R7 is the currently orderable release. z/OS 1.5 , z/OS 1.6, and z/OS 1.7 geplante Koexistenz mit z/OS 1.8 z/OS 1.7 geplante Koexistenz mit z/OS 1.8 und 1.9 xc - Compatibility support only x1 – z990 compatibility or exploitation feature required (orderable until December 2006) There is no IBM Bimodal Accommodation Offering available for z/OS 1.5 or higher releases. * All statements regarding IBM future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only. © IBM Corporation

Over 90% on supported releases of z/OS. Job well done!
Percent (%) of z9xx WW System Inventory © 2004, 2006 IBM Corporation

z/OS 1.8 Preview* Helping Meet the Future challenges of on demand business* with designs intended for: Scalability & Performance New zIIP processor, GRS ENQ limits, CF Stage 2, Parallel VARY ONLINE, z/OS UNIX file descriptors, Device Groups, 31-bit constraints, Support for up to 4 TB memory, DADSM/CVAF Rapid Index Rebuild… Improving Usability and Skills More Health Checks and framework improvements, HCM, ISPF, InfoPrint® Server, & RRS improvements, Extensions to the Network Security Configuration Assistant GUI … Improving Availability Consoles Stage 2, CFRM Stage 2, Logstream rename, test and production logstream separation, Recoverable BRLM, GDPS enhanced recovery, Fast replication, Hyperswap trigger, z/OS UNIX latch contention detection… z/OS R8 Integrating new Applications and Supporting Industry and Open Standards Unicode improvements; inittab support; Authorized Language Environment improvements, new LDAP server, z/OS XML System Services, BPXBATCH, CIM, eServerOS Monitoring, XPLINK, Networking APIs … Self-Managing Capabilities WLM, zAAP Stage 2, Sysplex Distributor, Tape I/O priority, GRS Star, JES2 balancing of WLM-managed initiators … Enhancing Security PKI extensions, Distributed Identity Support, RACF pass phrase support, Tape data set protection, 128-bit AES for IPSec, … Extending the Network Sysplex partitioning support, Dynamic DNS registration, JES3 NJE via TCP/IP, TN3270 and telnet improvements, IP filtering, IKE, IPSec, WTS, Samba, … Supporting the Heterogeneous Infrastructure WLM/EWLM Service Class Correlation, zAAP Reporting for EWLM, DFSMSrmm CIM agent… © 2006 IBM Corporation All statements regarding IBM future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only.

Scalability* Support for more real memory
New z/OS limit will be 4 TB; old limit was 128 GB Up to 512 GB supported on z9-109, up to 256 GB on z990 GRS support for more concurrent ENQs Default limits unchanged: Unauthorized ENQ default limit remains 4096; authorized default ENQ limit is 250,000; can specify higher maximums than the defaults New maximum is 2,147,483,647 (x’7FFFFFFF’) New ISGADMIN authorized interface, T GRS command, and GRSCNFxx parmlib support for setting higher maximums GRS 31-bit constraint relief Move star-mode global QCBs and QCBS control blocks above the bar Better compaction for remaining QCBs Scalability z/OS V1.8 is planned to extend system limits and continue to support application workload growth. Support is planned for up to 4 TB of real memory on a single z/OS image. This is expected to allow the use of up to 512 GB of real memory on a single z/OS image on IBM System z9 servers and up to 256 GB on z990 servers. Also planned are improved support for large-format sequential data sets, increased system-wide and intra-address space limits for Global Resource Serialization (GRS), and improved high-level language support for VSAM data sets with extended addressability. New and enhanced z/OS V1.8 function: Support is planned for up to 4 TB (4,398,046,511,104 bytes) of real memory on a single z/OS image on IBM System z9 servers and up to 256 GB on IBM zSeries z990 servers, an increase from the prior maximum of 128 GB. This is expected to enable programs that use large amounts of real memory to avoid paging and swapping overheads, and to help enable workload growth. GRS is planned to offer a new programming interface designed to allow authorized programs to set their own concurrent enqueue (ENQ) limits within their address spaces. Some subsystems, such as DB2, often need to open a large number of data sets concurrently. Others, such as CICS, can manage many different units of work within a single address space. This new support is intended to allow such programs to increase their ENQ limits beyond the system's default limit. Also, this support will be designed to allow system programmers to dynamically alter the system-wide limits. GRS design is planned to be changed to move selected GRS control blocks above the 2-GB bar. This is expected to help avoid GRS storage constraints as the storage size, processor capacity, and workloads running on large z/OS images grow. Language Environment is planned to deliver enhancements to the C run-time library functions fgetpos(), fsetpos(), and fseek(). This is intended to improve the performance of repositioning operations within multivolume data sets. Language Environment is planned to provide full z/OS XL C/C++ run-time library support for large-format sequential data sets opened using QSAM (noseek in C/C++). This support will remove the constraint of tracks per volume for sequential data sets. Language Environment is planned to provide z/OS XL C/C++ run-time library support for VSAM data sets with extended addressability. This support is planned for key-sequenced (KSDS), entry-sequenced (ESDS), and relative-record data sets (RRDS). DFSMSrmm is planned to extend support for managing removable media across the enterprise. The DFSMSrmm CIM agent will be designed to support the creation, change, and deletion of volumes and data sets. This will be in addition to the query and display capabilities provided in z/OS V1.7. The CIM agent is planned to use the OpenPegasus CIM Server. It will be able to run on z/OS and other systems supported by OpenPegasus. In addition, to improve systems support across the enterprise, DFSMSrmm support is planned to use common time and provide support for displaying and setting dates and times in any chosen time zone. Support for DASDSM/CVAF Rapid Index Rebuild in z/OS V1.8 will be designed to help speed DADSM VTOC conversions from Indexed to operating system format. * All statements regarding IBM future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only. © 2006 IBM Corporation

Scalability* CF performance enhancements Stage 2
Designed to allow more systems, structures, and connectors to be added without availability impacts Parallel VARY ONLINE processing Designed to reduce the duration of VARY commands for large numbers of devices Expected to reduce serialization contention Complements parallel VARY OFFLINE processing, available with z/OS R7 Language Environment support for sequential data sets larger than 64K tracks and for VSAM extended addressability data sets QSAM support in Language Environment for C/C++ programs (using noseek) Support for ESDS, KSDS, RRS extended format data sets with extended addressability * All statements regarding IBM future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only. © 2006 IBM Corporation

Scalability* z/OS UNIX limit on file descriptors per process increased from 128K to 512K MAXFILEPROC limit will be in BPXPRMxx and SET OMVS command Can restrict for individual users by setting FILEPROCMAX in the OMVS segment C and assembler programming interfaces support new limit Support for more than 32K device groups Device groups are consumed by tape devices (1 per device) and DASD esoteric names (1 per device range per esoteric name). You can reach this limit with fewer than the 63.75K maximum number of devices APAR OA02983 increased the limit to 64K-1 devices (x’FFFF’) at the end of 2003 The new limit will be really high (4G-1, or x’FFFFFFFF’) Note: You can check on your systems by looking at the number of entries in the Group Pointer Table using the IPCS LISTEDT command. DADSM/CVAF Rapid VTOC Index Rebuild © 2006 IBM Corporation * All statements regarding IBM future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only.

Optimization* Improved WLM IBM System z9 Application Assist Processor (zAAP) support WLM designed to manage based on both CP and zAAP delays Improved IFAHONORPRIORITY=YES processing New design intended to use CP resource only when zAAP workload goals are expected to be missed (also available with APARs OA14131 and OA13953 on z/OS R6 and R7) Sysplex Distributor enhancements Designed to favor local servers when possible Builds on integration with WLM introduced with z/OS R7 JES2 load balancing for WLM-managed initiators Designed to keep approximately the same percentage of WLM-managed initiators in each service class in use on all systems in a sysplex within the same MAS Designed to help balance sysplex batch workloads Self-optimization capabilities In z/OS V1.8, Communications Server is planned to offer additional network and workload balancing improvements by favoring local servers when possible to reduce inter-CEC network traffic. Also planned are enhanced Workload Manager (WLM) processing for zAAP workloads, improved I/O priority for tape devices, and more integration between WLM and Enterprise Workload Manager (EWLM). These functions are intended to help optimize workloads within an image and across a sysplex: A new option will be designed to allow the z/OS Sysplex Distributor to favor local system target servers where possible, while avoiding servers that are no longer active or are overloaded. If the Sysplex Distributor chooses a target on the same system as the client, this new design will be intended to optimize the connection in the following manner: Traffic for the target connection will no longer be routed to the sysplex distributor routing stack. The connections will be eligible for the "fast local sockets" optimized path. Sysplex Sockets will report these sockets as being on the same system. In z/OS V1.8, Workload Manager (WLM) improvements are planned to: Manage workloads based on zAAP delay in addition to CP delay. This will be designed to manage workloads based on both zAAP and CP utilization. Change the way the IFAHONORPRIORITY=YES parameter in IEAOPTxx parmlib members is processed. This change is intended to help limit the amount of work that is scheduled on CPs when sufficient zAAP capacity is available to run work that is eligible to run on zAAPs. This new function will be designed to enable zAAPs to obtain help from CPs when there is more zAAP eligible work than zAAP capacity. This function is also available with APARs OA14131 and OA13953 for z/OS and z/OS.e V1.6; and z/OS and z/OS.e V1.7. System Resource Manager (SRM) is planned to calculate a new static I/O priority for all address spaces and enclaves. The new I/O priority will be derived from the importance of the service class the unit of work is classified to, and will be designed to be used by IOS when no dynamic I/O priority is provided by WLM or SRM. This function will be supported for tape I/O only. Global Resource Serialization (GRS) enhancements are planned to enable GRS Star users to specify which system will be the contention notifying system (CNS). In a GRS Star environment, global contention is reported by a single image acting as the CNS. Allowing you to specify the placement of CNS work can help you better balance workload in a sysplex. All systems in a sysplex must support this function to enable its use. In addition to z/OS V1.8, this new function is planned to be included on z/OS V1.7 with APAR OA11382. EWLM support is planned to be added to z/OS WLM: WLM will be designed to accept the classification of work from EWLM. It is planned that EWLM transaction classes can be correlated to WLM service classes via classification rules in the WLM Service Definition. If such a correlation has been defined, WLM will assign the specified WLM service class to the end-to-end work in the EWLM transaction class rather than classify it. A performance administrator on the EWLM control center will then be able to see integrated information about end-to-end work within the same transaction class for reporting and management. This is expected to help improve cross-platform workload management. With z/OS V1.8, a high-performance EWLM instrumentation option via WLM Enclave Services is planned to be introduced that is designed to help reduce the instrumentation overhead significantly. The high-performance EWLM instrumentation option is suitable for applications that implement a sequential transaction processing flow without sub-transactions. WLM execution delay monitoring services are planned to be mapped to appropriate Application Response Measurement (ARM) services. This is expected to simplify the EWLM instrumentation of subsystems that are already instrumented with WLM execution delay monitoring services, such as CICS and IMS. The WLM functions are planned to be enhanced to provide a consistent management of process entitlements on both the z/OS-centric world and the heterogeneous world controlled by EWLM. Five new WLM system service classes, SYSSTC1-5, will be introduced. These are associated with fixed dispatching priorities as well as an enhanced resource group concept that allows capacity limits to be defined based on the LPAR capacity or the capacity of a single processor. Currently only CP data is reported to EWLM. With z/OS V1.8, zAAP data is planned to be included in the CPU using and delay samples as well as in the CPU service times reported to EWLM for processes using zAAPs. Support for the Object Access Method (OAM) DB2 Binary Large Object Support is planned to enable objects larger than 32 KB to be stored using DB2's large object (LOB) support and the binary large object (BLOB) data type. A new keyword is planned to be supported on the OAM1 statement of the IEFSSNxx parmlib member to indicate that DB2's LOB support should be used. Coexistence support is planned for earlier release levels to coexist in an OAMplex with z/OS V1.8. Storing in LOB storage structures is expected to improve performance when working with large objects. A 256-MB object, for example, can be stored in a single row in a LOB storage structure, but would require rows in a conventional 32-KB table. OAM Object Tape Enhancements will add automatic selection of RECYCLE-eligible tape volumes to the existing MOVEVOL with RECYCLE function, and provide support for an immediate backup copy to be created for an object at the time the object is originally stored. The z/OS UNIX System Services asynchronous socket read and write operations (the aio_read() and aio_write() callable services) are planned to be converted to use fast-path processing. In addition, performance will be improved for all fast-path syscalls that are called in SRB mode. This is expected to improve performance for applications that use asynchronous I/O or that run in SRB mode. SCLM design changes to reduce the number of ISPF service calls and cache certain data, intended to improve the performance of the SCLM Library utility (option 3.1), are planned. VARY processing will be redesigned to bring multiple devices online in parallel. This is expected to provide a significant improvement in the elapsed time required to vary a large number of devices online. JES2 will be designed to help balance workload in a multi-access spool configuration within a sysplex. This new design will be intended to use approximately the same percentage of active WLM-managed initiators in each service class on each system. Depending on the characteristics of your workloads and their arrival patterns, this can help balance batch workloads across a MAS configuration within a sysplex. © 2006 IBM Corporation * All statements regarding IBM future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only.

Optimization* I/O priority improvements
SRM designed to assign I/O priority for tape when there is no WLM recommendation Ability to specify CNS notification system for GRS Star Also planned for z/OS R7 with APAR OA11382 WLM delays mapped to ARM services Process entitlement group support Can specify new classes, SYSSTC1-SYSSTC5, with fixed dispatching priorities Can also define capacity limits for resource groups * All statements regarding IBM future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only. © 2006 IBM Corporation

Networking* VTAM and TCP/IP network sysplex partitioning support
Can define multiple logical networks (Subplex) within a sysplex Dynamic DNS registration/deregistration Network Security Configuration Assistant Introduced in z/OS R7 Extended in z/OS R8 to help with IDS and QoS configuration IPv6 support improved: For IP Filtering, IPSec, IKE Policy Agent support for IP filters, manual tunnels, dynamic tunnels WTS (Windows Terminal Server) support SMB support for Linux Samba clients REXX interface designed to allow calling FTP programmatically Sample program included JES3 support for NJE via TCP/IP (delayed availability) Networking In z/OS V1.8, significant improvements are planned for networking and communications, including the ability to specify subplexes for TCP/IP communications and improved sysplex autonomic functions, support for JES3 NJE connections via TCP/IP, improvements in networking security, and support for Windows Terminal Server (WTS). The following enhancements are planned for Sysplex environments: The ability to specify a subdivision of a sysplex into multiple "subplex" scopes from a sysplex networking function perspective will be delivered. For example, some VTAM and TCP/IP instances in a sysplex might belong to one subplex, while other VTAM or TCP/IP instances in the same sysplex might belong to other subplexes. This function can be useful in scenarios where different LPARs within the same sysplex need to be isolated into different security zones, with isolation between those zones. The sysplex autonomics function will be enhanced to deliver monitoring of critical network interfaces so that sysplex autonomics recovery can be triggered when a failure occurs at the interface. A new application is planned to allow dynamic registration and deregistration of Domain Name Server (DNS) records for z/OS hosts, host groups, servers, and server groups and their associated zones based on their current availability. This function is intended to provide an improved alternative to the dynamic registration and deregistration of DNS hostnames currently available with the z/OS BIND DNS server. Support for JES3 NJE communications using TCP/IP will be available in z/OS V1.8. This function will include support for IPv6, secure sockets (SSL/TLS), and all the NJE constructs (ENDNODE, SUBNET, Store-and-Forward) supported by the owning JES. This new support will be in addition to the SNA and BSC protocols currently supported by JES3. In order to use the NJE/TCP support, both sides of the connection will be required to support NJE/TCP. This function is expected to be available during the first half 2007. Functions to support IP filtering, IPSec, and Internet Key Exchange (IKE) for IPv6 are planned to be provided: The Policy Agent, to help configure IP filters, manual tunnels, and dynamic tunnels for IPv6 The TCP/IP profile, to allow configuration of default IP filters for IPv6 when the policy-based IP filters are not active The z/OS Communications Server IKE daemon, to negotiate dynamic tunnels for IPv6 The z/OS Network Security Configuration Assistant GUI, to help configure IPSec for IPv6 in the Policy Agent and the IKE daemon The ipsec command, to display and modify installed IP filter information, manual tunnel information, and dynamic tunnel information for IPv6 The Traffic Regulation Management daemon (TRMD), to support logging of IP Security events, such as IP filter permits and denies, for IPv6 z/OS Communications server delivers a rich set of callable APIs that can be used by network management applications. In z/OS V1.8, a number of additions and improvements will be made to this set of APIs: An API is planned for dropping multiple TCP connections or UDP endpoints. The existing Enterprise Extender network management interface will be enhanced to allow the specification of wildcard characters in the CP name on HPR connection requests. For applications using this interface to gather HPR connection data, using a wildcard value can reduce the number of NMI requests issued to obtain all of the data, and this is expected to improve application performance. The ability to manage TN3270 connections is planned to be improved with: The provision of a new API designed to allow for the retrieval of performance data for TN3270 server sessions The addition of the TCP connection ID to the TN3270 SMF records WTS support: Currently, the z/OS SMB server can handle a single user session over a single communications session from a Windows PC. The WTS will be able to act as a client to the z/OS SMB server. The WTS allows many Windows clients to connect to it. The server will, in turn, act as a client to the z/OS SMB server and send many user sessions over a single communications session. Linux Samba client support: The z/OS SMB server is also planned to support Linux Samba clients. The following changes are planned for SNA and Enterprise Extender (EE): An EE connectivity test command is planned to be provided to assist in debugging various network problems. This new test command is intended to be used to test an existing EE connection, or to assist in determining why an EE connection cannot be established. A number of miscellaneous usability, serviceability, and problem determination improvements are planned to be made to SNA, and in particular EE. FTP enhancement: z/OS V1.8 Communications Server is planned to provide a new REXX interface designed to be used to invoke the FTP client programmatically. This API support will extend the existing FTP Client API to support the REXX programming language. A sample REXX program is also planned to be delivered. Telnet enhancements: Enhancements are planned to allow you to specify that a TN3270 server should automatically clean up hung SNA Telnet sessions when a new TN3270 connection is initiated. This will be designed to help reduce the number of reconnect failures caused when Telnet still has a SNA session for the original connection. Support for the resolution of system symbols is planned for Telnet unformatted system services message (USSMSG) processing. System-specific symbols such as the system name are planned to be displayed to help you diagnose problems. The USS table assignment from the LU exit will be designed to provide more flexibility in assigning a USS table based on client criteria. AnyNet is planned to be removed from z/OS Communications Server. AnyNet has not been enhanced in many years, and has been supplanted by EE, which has superior function and performance. The ability to define parallel EE Transmission Groups (TGs) using multiple SAPs is planned to be removed in z/OS V1.8. Parallel TGs defined in such a manner provide no benefit over single EE logical links. A new TCP/IP configuration parameter is planned that allows users to designate the source IP address to be used for outbound TCP connections based on the destination IP addresses or networks. In scenarios where outbound TCP connections from z/OS need to traverse multiple distinct networks, this enhancement can help make firewall administration easier, as users can permit traffic from a single, predictable IP address to traverse the firewall. In z/OS V1.8, the Firewall Technologies component of the Integrated Security Services element is planned to be removed. Many Firewall Technologies functions have been stabilized for some time and can be replaced using comparable or better functions provided by Communications Server, notably, IPSecurity. In addition, a functionally rich downloadable tool replaces the IPSecurity and IP Filtering configuration GUI support. For more information, refer to z/OS V1R7.0 Migration. * All statements regarding IBM future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only. © 2006 IBM Corporation

Networking* Additions and improvements planned for Communications Server callable APIs: Support for dropping multiple TCP connections or UDP endpoints Enhancing the Enterprise Extender network management interface to allow CP name wildcarding for HPR connection requests TN3270 connection management is planned to be improved: New API designed to allow for the retrieval of performance data for TN3270 server sessions Add TCP connection IDs to TN3270 SMF records Planned Telnet enhancements: Ability to specify TN3270 servers should automatically clean up hung SNA Telnet sessions when a new TN3270 connection is initiated Support for the resolution of system symbols is planned for Telnet unformatted system services message (USSMSG) processing. USS table assignment from the LU exit will be designed to provide more flexibility in assigning a USS table based on client criteria. * All statements regarding IBM future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only. © 2006 IBM Corporation

Application Integration*
New z/OS XML System Services component of z/OS Expected to help satisfy requirements for high performance or unique environmental XML non-validating parsing Support for cross-memory and SRB modes Initial support for HLASM; IBM plans to add C/C++ high-level language support in a future release Also planned to be made available on z/OS R7 New CIM version, planned to include An upgrade of the CIM Server Runtime Environment to V2.5.1 of OpenPegasus from the Open Group CIM Schema upgrade to 2.9 Additional resource instrumentation Support for Embedded Objects, Events (CIM Indications), HTTP Chunking, and the capability to run CIM providers in a separate address space Command line interface planned for running CIM Client requests against the CIM Server Security, reliability, and scalability improvements also planned for CIM Server Application integration In z/OS V1.8, several important functions intended to deliver further application integration support and support for industry and de facto standards are planned: A new system component of z/OS, z/OS XML System Services Improvements in Unicode support BPXBATCH support for output data sets CIM Server and schema upgrades The ability to trace transitions in and out of XPLINK in z/OS UNIX System Services (z/OS UNIX) programs Other improvements that are all intended to add new capabilities and help extend and tune your applications New and enhanced z/OS V1.8 function is planned to include: IBM intends to deliver a new LDAP server for z/OS designed to improve performance, scalability, auditability, availability, and ease of use. Also, IBM intends to deliver stronger affinity to z/OS platform features like Parallel Sysplex. Among the planned enhancements are: A new backend for small- and medium-sized directories designed to cache all directory entries in memory for better performance and use a z/OS UNIX System Services file as its backing store. This is planned to be made available in addition to the existing DB2-based backend. This enhancement is expected to help simplify setup and operation for small- and medium-sized directories. Automatic Restart Management (ARM) and TCP/IP restart support designed to help improve availability. Parallel Sysplex support designed to enhance synchronization of LDAP servers within a sysplex and allow a sysplex group to replicate with other LDAP servers. The creation of SMF records designed to improve LDAP auditability. IBM plans to introduce a new system component of z/OS, z/OS XML System Services (z/OS XML), which will be designed to deliver an optimized set of services for parsing XML documents. It is expected to be of use to IBM, Independent Software Vendors (ISVs), and customer middleware and applications having high performance or unique environmental XML non-validating parsing requirements, such as the ability to run in cross-memory and service request block (SRB) modes. Initial support is planned to deliver an assembler language interface. This new function will be intended to satisfy a statement of direction made in Software Announcement (RFA41468), dated July 26, 2005, and will be available on z/OS V1.7. In a future release, IBM plans to add C/C++ high-level language support. Unicode support is vital to enterprises with globalization imperatives; that is, to those for which storing data from different languages in a common format is important. z/OS V1.8 is planned to offer new collation tables needed by middleware applications. Their names will be based on the Unicode Collation Algorithm (UCA), which conforms to the Unicode 4.0 standard. Using the new keywords can allow collation sequences for various locales to be used so that data stored in Unicode can be sorted using the appropriate collating sequence for each supported language. The BPXBATCH program is planned to be enhanced to allow STDOUT and STDERR DD statements to specify SYSOUT data sets and partitioned, PDSE, and sequential data sets. This can help provide more options for storing the output of programs run using BPXBATCH. This function is also available for z/OS V1.5 and higher with APAR OA11699. z/OS V1.8 is planned to include a new version of the Common Information Model (CIM). This includes the upgrade of the CIM Server Runtime Environment to V2.5.1 of OpenPegasus from the Open Group, an upgrade of the CIM Schema to 2.9, and additional resource instrumentation. Key features of the new CIM Server for z/OS are the support for Embedded Objects, Events (CIM Indications), HTTP Chunking, and the capability to run CIM providers in a separate address space. In addition, a command line interface is planned to be provided to execute CIM Client requests against the CIM Server. Improvements are planned to be implemented in the areas of security, reliability, and scalability of the CIM Server. RMF is planned to implement eServer OS monitoring Stage 2 for z/OS. Stage 2 includes: A WBEM profile based on the IETF SLP protocol will be intended to make self-discovery of the CIM-based monitoring service easier. Support for CIM indications is designed to enable exploiters using standard CIM client applications to subscribe to asynchronous events. Some additional existing RMF metrics are exposed to CIM. A new capability is planned for tracing XPLINK/non-XPLINK transitions. It will be intended to help benefit customers porting UNIX applications to z/OS. This tracing capability will be designed to be turned on or off, and to trace the transitions between upward (non-XPLINK) and downward (XPLINK) growing stacks. This is expected to help application programmers more easily diagnose the performance bottlenecks that might exist in mixed XPLINK/non-XPLINK applications. Support is planned for the /etc/inittab file that is used on other UNIX systems to start and restart daemons. This will be intended to allow you to identify system processes to be started during system initialization that should receive additional system management by z/OS UNIX System Services. The dbx debugger will be designed to support the complex and packed decimal data types used by applications that demand a higher degree of mathematical precision. ISPF Edit informational messages are planned to be made available to ISPF Edit macros. Currently, in ISPF Edit interactive mode, the message identifier, short message text, and long message text are displayed on the screen. This change will make the same information available to non-interactive macros in order to help allow them to handle more conditions. Additional locale support for the Euro currency symbol is planned to be provided for countries that have recently joined the European Union: Czech Republic, Estonia, Hungary, Latvia, Lithuania, Poland, Slovakia, and Slovenia. As it does for other locales, this support is planned to allow the Euro currency symbol to be displayed and printed as the national currency symbol in these countries. This function is also available with APAR PQ99282 for z/OS V1.4 and higher. RMF Spreadsheet macros will be extended to analyze zAAP usage. The Software Configuration and Library Manager (SCLM) component of ISPF is planned to include the following enhancements: The ability to specify a language description when using the SPROF (SCLM Edit Profile) command and the SCLMINFO service to define an SCLM language Additional information about return codes in error messages generated by the COBOL parser (FLMLPCBL) JES3 is planned to be enhanced to allow applications using the SYSOUT Application Programming Interface (SAPI) to retrieve SYSOUT data sets with READ access to the appropriate profile in the JESSPOOL class. Currently, UPDATE access is always required. © 2006 IBM Corporation * All statements regarding IBM future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only.

New LDAP server Designed to improve performance, scalability, auditability, availability, and ease of use, and planned to include: z/OS UNIX file-based backend for small- and medium-sized directories with memory caching for all directory entries, to help simplify setup and operation of small- and medium-sized directories In addition to existing support for DB2-based backstore ARM and TCP/IP restart support Parallel Sysplex support designed to enhance synchronization of LDAP servers within a sysplex and allow a sysplex group to replicate with other LDAP servers SMF records designed to improve LDAP auditability. * All statements regarding IBM future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only. © 2006 IBM Corporation

Unicode collation tables: New needed by middleware applications added Based on the Unicode Collation Algorithm (UCA), which conforms to the Unicode 4.0 standard Improvements for Language Environment’s Preinitialized Environments for Authorized Programs: Support for changing the number of system-managed environments dynamically Improved failure data collection capabilities and more recovery options inittab support in z/OS UNIX for Java recovery Provide de facto standard recovery methods XPLINK transition tracing Can help optimize application performance Additional locale Euro support for EU countries Czech Republic, Estonia, Hungary, Latvia, Lithuania, Poland, Slovakia, Slovenia * All statements regarding IBM future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only. © 2006 IBM Corporation

RMF eServer OS monitoring Stage 2 for z/OS A WBEM profile based on the IETF SLP protocol, intended to make self-discovery of the CIM-based monitoring service easier Support for CIM indications, designed to enable exploiters using standard CIM client applications to subscribe to asynchronous events Expose some additional existing RMF data to CIM BPXBATCH improvements STDIN, STDOUT support for sequential & SYSOUT data sets, PDS(E) members Also available now on z/OS R5 and up with APAR OA11699 CLIST variable pool and REXX OUTTRAP constraint relief for authorized programs Move data area above the 16MB line Larger storage area available for authorized programs * All statements regarding IBM future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only. © 2006 IBM Corporation

Ease of Use* Health Checker Framework improvements:
Support for running checks outside the Health Checker address space Support for defining checks in parmlib More health checks: GRS Communications Server RRS ASM/VSM DFSMS Network Security Configuration Assistant improvements: Support for QoS and IDS policy configuration Designed to allow you to configure IPSec, Application Transparent TLS, QoS, and IDS policy using a consistent user interface RRS displays, shutdown command Support for changing file format (extattrs) from the z/OS UNIX shell Ease of use Ease of use is a continued focus area in z/OS V1.8. Significant improvements are planned to be delivered in the Health Checker Framework and also additional checks, a number of Hardware Configuration Manager (HCM) and ISPF enhancements, and usability extensions to Infoprint Server's Web-based print management interface. These and other usability improvements are planned: The z/OS NSCA (Network Security Configuration Assistant) GUI, introduced in z/OS V1.7, is planned to be extended to include support for QoS (Quality of Service) and IDS (Intrusion Detection Services) policy configuration. This support is planned to allow an administrator to configure IPSec, Application Transparent TLS, QoS, and IDS policy using a consistent user interface. QoS and IDS are currently configured with separate GUIs. These changes are expected to simplify the QoS/IDS configuration tasks by applying the NSCA concepts to QoS and IDS. Also, the NSCA will be designed to generate the policy agent configuration file for IDS policy, as described in Security. In z/OS V1.8, significant improvements are planned for health checking. The enhanced Health Checker Framework is intended to make it easier to write checks, and to provide improved parmlib, parsing, and display support for checks. In addition, a number of new checks are planned for Communications Server, GRS, storage management (ASM and VSM), DFSMS, and Resource Recovery Services (RRS). These Hardware Configuration Manager (HCM) enhancements are planned: A new function will be designed to export and import I/O definition files (IODFs). This is expected to improve processing time and help make it easier to send IODFs to IBM for problem determination. A new function will be designed to save the layout of a controller in a physical description file (PDF) so it can be used as a model for new controllers. Another new function is planned to allow you to locate objects that contain specific values in user fields, filter via wildcards, and select multiple objects for deletion in the Edit dialog. Support for the Copy, Add like, and Repeat functions that are provided by Hardware Configuration Definition (HCD) is planned. This support is intended to enable you to define complex objects more quickly and eliminate the need to switch back to HCD to use the function. A new function will be intended to allow you to compare HCM configuration files and get HCD IODF Compare Reports via an HCM dialog, and provide an additional means to check whether the changes that have been made were those intended. The automatic generation of entries in the activity log file of an IODF is intended to enhance the usability of the activity log file. The generation of cable labels is planned to include PCHID information for channel paths. Switch port names are planned to be defaulted to the connection data for each port. These functions will be intended to reduce the need for manual changes. The ability to hide connections in the HCM diagram is planned to help allow you to tailor a cropped configuration view for documentation purposes. Hardware Configuration Manager (HCM) is planned to provide performance data integration with a Web interface of the RMF Distributed Data Server (DDS) for selected objects of the HCM diagram. The displayed RMF Monitor III online performance data will enable you to detect performance bottlenecks and provide faster problem resolution. These ISPF improvements are planned: Support for SuperC Compare and Search-For functions on the Data Set List Actions panel. Enhancements that help make it easier to search for members: A new member list primary command, FILTER, will be designed so you can filter member lists using member attributes. The command will be designed to allow you to use it repeatedly to refine the member list. A new option on the SRCHFOR command will enable you to specify that member list filtering display only those members containing a search string. The ISPF workstation connect program WSCON will be designed to auto-discover the IP address of the connected TN3270 workstation and use this address to establish a session with the Work Station Agent. This is expected to improve usability, because you will no longer need to be aware of your IP address or enter it on the Initiate Workstation Connection panel to establish a session. ISPF client/server code will be converted to use the IBM C/C++ run-time libraries, which can help reduce the number of C run-time libraries in use on your system. Also, some performance improvement is expected. ISPF will be designed to help ensure that, when a member having one or more aliases is renamed or deleted, aliases are updated to point to the new name or deleted. This will be intended to prevent the inadvertent creation of "orphaned" alias entries. Data Set List line commands support for tape data sets is planned to be enabled. DFSMSrmm supports this by enabling fast path directly into the relevant part of the DFSMSrmm dialog. Enhancements to Infoprint Server's Infoprint Central Web-based print management GUI will be designed to: Display additional printer status information, such as paper levels in bins Turn printers online and offline and reset them directly from Infoprint Central Provide the ability to stop an IP PrintWay print job without canceling it Allow selection of log messages by hour and also by day Provide an audit trail for GUI actions into job and printer logs Force error messages to open when an action is performed on the Summary table Expand the ping action to include the TRACEROUTE command RMF enhancements planned to support ease of use include: The RMF postprocessor will be designed to honor duration intervals for overview processing in the same way as for standard intervals. This support will be intended to allow you to generate meaningful postprocessor trend reports over long periods and use the spreadsheet macros to plot charts for multiple days and even weeks. RMF Monitor III is planned to display LRU status VSAM RLS activity reports, which is expected to enable you to distinguish between buffers below and above the 2-GB bar. System Display and Search Facility (SDSF) will display zAAP utilization in addition to system CP utilization on the DA screen. Recoverable Resource Services (RRS) enhancements are planned: MVS DISPLAY commands are planned to include RRS status information. This is expected to make it easier to implement automatic alerts and capture information in syslog. A new SHUTDOWN command will be designed to allow you to end RRS instead of doing a CANCEL. This is intended to help avoid unnecessary abnormal termination and provide clearer shutdown messages. * All statements regarding IBM future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only. © 2006 IBM Corporation

Ease of Use* ISPF improvements
Data Set List (OPT3.4) support for SuperC and Search-for Better member list searching Autodiscovery of IP address for ISPF workstation GUI Improved alias processing for copy, move, delete Tape data set support in DSLIST Edit informational messages available to ISPF Edit macros SDSF display of zAAP utilization RMF postprocessor & Monitor III improvements HCM enhancements Literally, too many to list! * All statements regarding IBM future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only. © 2006 IBM Corporation

Supporting the Heterogeneous Environment*
EWLM/WLM service class correlation WLM designed to accept classification when same-named service class is passed from EWLM New DFSMSrmm CIM agent support Designed to support the creation, change, and deletion of volumes and data sets Complements the query and display functions in z/OS R7 zAAP reporting for EWLM Infoprint Server improvements EWLM support is planned to be added to z/OS WLM, to accept the classification of work from EWLM, introduce a high-performance EWLM instrumentation option via WLM Enclave Services, map WLM execution delay monitoring services to appropriate Application Response Measurement (ARM) services, and provide a consistent management of process entitlements on both the z/OS-centric world and the heterogeneous world controlled by EWLM by introducing new WLM system service classes. WLM will be designed to include zAAP data in the CPU using and delay samples as well as in the CPU service times reported to EWLM for processes using zAAPs. Enhancements to Infoprint Server's Infoprint Central Web-based print management GUI will be designed to: Display additional printer status information, such as paper levels in bins Turn printers online and offline and reset them directly from Infoprint Central Provide the ability to stop an IP PrintWay print job without canceling it Allow selection of log messages by hour and also by day Provide an audit trail for GUI actions into job and printer logs Force error messages to open when an action is performed on the Summary table Expand the ping action to include the TRACEROUTE command * All statements regarding IBM future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only. © 2006 IBM Corporation

Availability* Consoles Stage 2
Support for defining up to 250 (S)MCS consoles, with up to 99 active** Master console and console switch elimination (so no EXT interrupt action) 1-byte console IDs no longer supported UCME, ENQ, ORE, CONVCON, demand selection, command transport changes GDPS Enhanced Recovery CFRM recovery time improvements (CFRM Stage 2) Logger improvements: Rename Logstream support Test and production logstreams ** Post-GA delivery expected Availability z/OS, in conjunction with IBM System z (TM) servers, continues to address requirements for high availability. z/OS V1.8 is planned to extend DFSMS fast replication to the data set level on 2105 (Enterprise Storage Server) and later storage controllers; offer improved recoverability for the z/OS UNIX System Services (z/OS UNIX) Byte Range Lock Manager when a system failure occurs in a sysplex; improve the Coupling Facility Resource Manager (CFRM); provide further improvements to Consoles processing and System Logger; and make significant improvements in GDPS HyperSwap and CF duplexing recovery. These include: In z/OS V1.8, DFSMShsm fast replication support is planned to extend the full-volume dump function to allow dumping of fast replication backup copies to tape. The dump copies can be created by command or by automatic dump. Fast replication backup versions can be recovered from DASD target volumes (as in previous releases) or from dump tapes. In z/OS V1.8, DFSMS fast replication is planned to be enhanced to support data set recovery on 2105 (Enterprise Storage Server) and later disk storage devices. This support is intended to allow recovery of an individual data set from a copy pool backup version using the FRRECOV command, whose syntax will be enhanced to allow one or more fully or partially qualified data set names to be specified. The backup version being recovered can reside on disk or tape. When the backup version is recovered from disk, the recovery can be performed using fast replication or previously available copy methods. In z/OS V1.8, the z/OS UNIX System Services (z/OS UNIX) byte range lock manager (BRLM) is planned to be enhanced. It will be designed to allow applications that use byte-range locking to stay active when a system within the sysplex fails. This is expected to improve availability for those applications. Performance improvements are planned for CFRM. These enhancements will be intended to enhance sysplex availability by significantly reducing I/O contention for CFRM couple data sets (CDS). This is expected to improve the performance of sysplex processes that use the CFRM couple data set. These processes include rebuilding Coupling Facility structures, Coupling Facility Duplexing establishment and failover, and connect/disconnect processing. When sysplex partitioning actions are taken, and when a Coupling Facility fails, Parallel Sysplex configurations are expected to recover significantly faster, improving sysplex availability. In z/OS V1.8, the single master console is eliminated, and therefore it no longer can act as a single point of failure. The functions associated with the master console, including master command authority and the ability to receive messages delivered via the INTERNAL or INSTREAM message attribute, will be able to be applied to any console, including EMCS consoles, in the configuration. In addition, the function of console switch will be removed, because you will be able to define and use many more consoles that can be used should a primary console fail. Console enhancements are intended to deliver additional improvements in message processing and thus help improve Parallel Sysplex availability. These enhancements will be designed to focus on improving availability for sysplex configurations by: Reducing the amount of console configuration data that is passed around the sysplex under serialization. This change is expected to improve overall sysplex recovery time and reduce serialization delays during system startup and planned system shutdown activities. Increasing the maximum number of MCS and SMCS consoles that can be defined in a configuration from 99 per sysplex to 99 per system in the sysplex. These console enhancements are planned to be available for Early Support Programs (ESP) in the second quarter 2007, and to be generally available in the third quarter 2007. System Logger enhancements are planned to include: Support for renaming an existing log stream. This will allow you to maintain the current data under a new name and enable new work to begin after defining a new instance of the log stream, and is expected to help reduce the impact of a damaged log stream by not requiring that the original data be deleted. Support for specifying different groups of log streams in the LOGR CDS. This function will be intended to allow you to separate logger activity for test and production log streams. This can allow them to run in the same sysplex with less interference between them. GDPS Enhanced Recovery: GDPS and Peer-to-Peer Remote Copy (PPRC) enhancements will be designed to help reduce the length and variability of failover recovery times by improving the consistency between secondary copies of data at the recovery site and duplexed structures in the Coupling Facility. New interfaces between the Cross-System Communications Facility (XCF) and GDPS will enable "break duplexing" decisions for duplexed Coupling Facility structures to be made in a way that parallels the DASD "break PPRC mirroring" decision. This enhancement is intended to preserve a usable copy of the duplexed Coupling Facility structures for recovery. It is expected to help improve GDPS recovery time, enable consistent application restart times, and reduce the need for log-based recovery. The XCF support for this function is available for z/OS V1.5 and above with the PTFs for APAR OA11719. In z/OS V1.8, support is planned for a new HyperSwap trigger source type, I/O Timeout. Currently, HyperSwap function is invoked automatically when an error indication is returned for an I/O operation because of failures such as subsystem failures, boxed devices, or I/O errors. This support is planned to be extended to act on I/O timeouts detected by the Missing Interrupt Handler (MIH). The new function will be designed to allow transactions to resume processing quickly on the secondary volumes. It will help deliver improved availability while helping reduce the need for operator intervention. HyperSwap is available with the separately-priced GDPS/PPRC and GDPS/PPRC HyperSwap Manager offerings. Improved z/OS UNIX System Services latch contention detection is planned for z/OS V1.8. The output of the DISPLAY OMVS,Waiters operator command is planned to be enhanced to include a table of waiting threads and show file system latches held. These additional display capabilities are expected to help operators better identify the tasks that are waiting and the resources they are waiting for. * All statements regarding IBM future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only. © 2006 IBM Corporation

Availability* New Hyperswap trigger based on MIH
Recoverable z/OS UNIX Byte-Range Lock Manager (BRLM) in USS Designed to improve application availability in a sysplex when an owning system becomes unavailable Additional display support for z/OS UNIX latch contention New Fast Replication functions: Fast Replication at the data set level on (ESS) and later controllers DFSMShsm support for dumping fast replication copies to tape * All statements regarding IBM future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only. © 2006 IBM Corporation

Security* PKI Extensions:
SCEP support (programmatic certificate request support for network devices) Multiple CA support (in a single image) Distributed identity support: SAF Identity Token support EIM/TAM schema convergence Pass phrase support character pass phrases Vastly larger namespace Improved tape data set security administration Can use DATASET class without activating TAPEVOL or TAPEDSN Can specify that all data sets on the same tape should have common authorization IPSEC support for 128-bit AES Security In z/OS V1.8, z/OS continues to deliver industry leadership for security. Improvements that are all intended to help deliver the kind of security-rich environment that has made z/OS an industry leader include: Support for RACF pass phrases from 14 to 100 characters in length Significant improvements to Identrus-certified support for digital certificates, including SCEP and multiple-CA support Improvements for tape data set protection using RACF or another external security manager Support for the Advanced Encryption Standard (AES) for IPSec z/OS V1.8 is planned to include: Support for defining Intrusion Detection Services (IDS) policies in a policy agent configuration file as well as an LDAP server. This solution provides an IDS policy solution that is consistent with other policy types for those installations that do not have an LDAP infrastructure in place or that prefer using configuration files instead of LDAP. RACF is planned to support the use of passwords longer than eight characters, often called pass phrases. A pass phrase is a character string that can comprise mixed-case letters, numbers, and special characters including blanks, from 14 to 100 characters in length. Pass phrases allow for an exponentially greater number of possible combinations of characters and numbers than do passwords. A user ID can have both a password and a pass phrase. The same user ID can be used both for existing applications that accept an eight-character password and those that take advantage of the pass phrase infrastructure. This support is intended to help to improve system security and usability. Public Key Infrastructure (PKI) Services improvements: Multiple certificate authority (CA) support will be designed to allow more than one instance of the PKI Services daemon to run on a z/OS system. Also, new support is intended to allow you to establish multiple certificate authorities on a single image. Both new functions are expected to help improve the scale and availability of PKI Services management and fulfillment services on z/OS. Simple Certificate Enrollment Protocol (SCEP) support is planned for PKI Services. SCEP support, which is also offered by other industry certificate authority (CA) software, can allow SCEP-enabled clients, such as Cisco routers, to request certificates by sending messages to a CA using the HTTP protocol. The addition of SCEP support will be designed to allow PKI Services to respond to SCEP messages and support both manual and automatic enrollment. DFSMS support is planned to introduce new options for securing tape data sets using System Authorization Facility (SAF). These are planned to allow you to define profiles to protect data sets on tape using the DATASET class without the need to activate the TAPEDSN option or the TAPEVOL class. This will be designed to enable you to use generic profiles for both tape and disk data sets. DFSMS is also planned to provide options you can use to specify that all data sets on a tape volume should have common authorization and that users are authorized to overwrite existing files on a tape volume. Support is planned to be provided for the Advanced Encryption Standard (AES) algorithm for IP Security with a 128-bit key length. This algorithm replaces DES as the standard encryption algorithm. Support for SAF Identity Tokens is planned to provide exploiters with increased user accountability and auditability of resources by providing end-to-end auditing that tracks identities used for initial authentication and those used on the current platform. RACF support is planned for virtual key rings. This support is intended to treat the collection of all the certificates owned by one user ID, including the SITE and CERTAUTH reserved user IDs, as an independent key ring. The use of the CERTAUTH virtual key ring will be intended to help eliminate the need to manually create multiple real key rings for SSL-enabled z/OS client applications such as FTP. * All statements regarding IBM future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only. © 2006 IBM Corporation

Statements of Direction*
Old news Beyond z/OS 1.7 (1 of 4) z/OS Communications Server will remove support for BIND DNS function in a future release. VSAM support for IMBED, REPLICATE, & KEYRANGE will be removed in a future release. DFSORT™ ISPF panels will be removed in a future release. Support for sharing zSeries File System (zFS) file systems contained in multi-file system aggregates to be shared across a sysplex will be withdrawn in the release after z/OS 1.7. z/OS 1.7 is planned to be the last release to include the Firewall Technologies component of the Integrated Security Services element. * All statements regarding IBM future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only. © 2006 IBM Corporation

Old news Beyond z/OS 1.7 (2 of 4) z/OS 1.7 is planned to be the last release in which z/OS Communications Server will support: Configuration profile block definition statements (ASSORTEDPARMS and KEEPALIVEOPTIONS) The PAGTSNMP subagent Defining EE TGs with multiple SAP addresses AnyNet® z/OS 1.7 is planned to be the last release to support 1-byte Console IDs. Support for zFS multi-file system aggregates will be withdrawn in a future release. IBM intends to provide a VSAM Java (TM) database connectivity (JDBC) Connector in the future, not in 2005 as previously stated. * All statements regarding IBM future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only. © 2006 IBM Corporation

Old news Beyond z/OS 1.7 (3 of 4) Support for the TCP/IP, z/OS UNIX, Language Environment, Parallel Sysplex, ISPF, and RMF plug-ins for msys for Setup will be withdrawn in the release following z/OS V1.7. IBM intends to deliver z/OS setup and configuration improvements in the future. DB2 V8 plug-in is not affected TCP/IP plug-in will be made available via the Web and will not require msys for Setup z/OS V1.7 is planned to be the last release to support the z/OS msys for Operations element. In the next release of IBM Communication Controller for Linux on zSeries, IBM intends to provide enhancements in network connectivity such as channel data link control (CDLC) using OSA-Express2 OSN (OSA for NCP), data-link switching (DLSw), and an open interface for X.25 (NPSI). * All statements regarding IBM future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only. © 2006 IBM Corporation

Old news Beyond z/OS 1.7 (4 of 4) IBM plans to support more than 32 processors in a single z/OS image on the IBM System z9 109 server in the future. IBM plans to announce a version of New Application License Charges (NALC) intended to help improve the price performance of z/OS in certain new workload environments by delivering subcapacity pricing, in 2H2006. * All statements regarding IBM future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only. © 2006 IBM Corporation

New news! Effective with z/OS 1.8 IBM intends to stabilize the prelinker The prelinker is designed to be used with the linkage editor Note: The Binder provides additional function, and is not stabilized z/OS R8 is planned to be the last release to support APPC communication between HCD and HCM TCP/IP communication remains supported z/OS V1.8 is planned to be the last release to include the C/C++ IBM Open Class (IOC) Dynamic Link Libraries (DLLs) You should plan to migrate to the standard C/C++ libraries See the IBM Open Class Library Transition Guide Statement of direction: IBM plans to take the following actions effective with the general availability of z/OS V1.8: IBM intends to stabilize the prelinker. The prelinker was designed to process long names and support constructed reentrancy in earlier versions of the C compiler on the MVS (TM) and OS/390 (R) operating systems. The prelinker, shipped with the z/OS C/C++ run-time library, provides output that is compatible with the linkage editor, shipped with the binder. The binder is designed to include the function of the prelinker, the linkage editor, the loader, and a number of APIs to manipulate the program object. Its functionality delivers a high level of compatibility with the prelinker and linkage editor, but provides additional functionality in some areas. For more information on the compatibility between the binder and the linker and prelinker, refer to z/OS MVS Program Management: User's Guide and Reference. Further enhancements will not be made to the prelinker utility. Enhancements will be made only to the binder, the strategic tool for program object manipulation. z/OS V1.8 is planned to be the last release that supports host communication between Hardware Configuration Manager (HCM) and Hardware Configuration Definition (HCD) elements via Advanced Program to Program Communication (APPC). Currently, for host communication either TCP/IP or APPC are supported. Starting with the z/OS release available in 2007, the host communication will be done exclusively via TCP/IP. z/OS V1.8 is planned to be the last release to include the C/C++ IBM Open Class (IOC) Dynamic Link Libraries (DLLs). Application development support for the C/C++ IOC Library was withdrawn in z/OS V1.5. The run-time support (DLLs) for applications that use the IOC Library is planned to be removed in the z/OS release available in Applications that are dependent on the IOC Library will not run starting with the z/OS release available in IBM has previously recommended that customers with application code that uses the IOC Library migrate to the Standard C++ Library. The publication IBM Open Class Library Transition Guide was published with z/OS V1.2 C/C++ as a reference for customers migrating their code from the IBM Open Class Library to the Standard C++ Library. You can get this guide by visiting * All statements regarding IBM future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only. © 2006 IBM Corporation

New news! Beyond z/OS 1.8 In a future release of z/OS Communications Server, support for the in-stack version of the TN3270 Server is planned to be discontinued. The standalone TN3270 server introduced in z/OS R6 offers significant advantages, and remains supported. In a future release, IBM plans to replace the RMF LDAP backend. Also: IBM plans to enhance the IBM Encryption Facility for z/OS (product 5655-P97) Encryption Services feature to use the OpenPGP standard, RFC 2440. This is expected to allow file exchange with others having OpenPGP-capable software running on their systems. IBM plans to take the following actions in a future release: z/OS V1R6 Communications Server and subsequent releases include a stand-alone TN3270 Server. This stand-alone TN3270 Server is expected to provide increased flexibility, improved reliability, and simplified problem diagnosis as compared to the in-stack version of the TN3270 Server. In a future release of z/OS Communications Server, support for the in-stack version of the TN3270 Server is planned to be discontinued. In preparation for that change, customers should consider implementing the stand-alone TN3270 Server. For more information, refer to IBM plans to replace the RMF LDAP backend in a future release of the operating system. The RMF LDAP interface currently allows access to RMF performance data from application programs. This functionality will be replaced with a Common Information Model (CIM) Monitoring interface that is now part of z/OS V1.7. IBM plans to enhance the IBM Encryption Facility for z/OS (5655-P97) Encryption Services feature to use the OpenPGP standard, RFC This support will be designed to allow you to exchange an encrypted, compressed, and/or digitally signed file between your internal data centers using the Encryption Services feature in conjunction with your external partners and vendors who have an installed RFC 2440-compliant client running on z/OS and other operating systems. IBM plans to give additional details on the specific OpenPGP functions at a later date. All statements regarding IBM's plans, directions, and intent are subject to change or withdrawal without notice. * All statements regarding IBM future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only. © 2006 IBM Corporation

Previewing z/OS 1.8* Summary
Planned to be available September 2006 AVAILABILITY More granular options for fast replication of data Improved sysplex resiliency and recovery SECURITY Advances in Digital Certificate management, network encryption, and RACF® NETWORKING Improved autonomics in a sysplex Support for WTS clients, SAMBA for Linux clients OPTIMIZATION Improved I/O priority handling for tape devices Improved WLM management of zAAP workloads APPLICATION INTEGRATION Support for industry and de facto standards Optimized LDAP directory to allow greater consolidation Advancing mainframe leadership Simplifying z/OS management More checks added to Health Checker for z/OS Aids to help configure for IPv6 Helping to improve enterprise-wide resource management Improved integration between z/OS WLM and Enterprise Workload Manager (EWLM) zOSSUM_105 * Statements regarding IBM's future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only

Datenservice für Unternehmen Übergang zu Information on Demand
Information on Demand ist wichtig für Geschäftsstrategie Daten bilden Kern des Business von Kunden und sollten für Wettbewerbsvorteile genutzt werden Mainframe ist über vier Dekaden führend in Daten und Transaktionsservice Dieser Vorteil wird weiter ausgebaut Ankündigung 24. Januar 2006 für IBM System z Innovative Technologie für erweiterten Datenservice Plan für zukünftige Ausrichtung und Roadmap Neue spezielle Engine Neue DB2 Funktionen Today we want to brief you on an announcement that will occur on the 24th of January 2006. This announcement is all around the reinforcing the idea of the mainframe as an enterprise data hub, and reinforcing and extending the technology and the price performance of the mainframe. IBM will be announcing a technology preview of the next version of DB2 for z/OS – called ‘DB2 vNext’. We will announce a new specialty engine that offers better resource utilization and improved price performance, whose first exploiter will be DB2 for z/OS V8. For customers that are familiar with our zAAP, than you can equate that this new engine will offer zAAP-like capabilities. We are also going to review the planned future directions and roadmap that we’ll be announcing. Hopefully you’ll see the ever tightening integration between DB2 and the mainframe, which positions us for data serving.

85% der Information ist unstrukturiert
Unternehmen begegnen wachsenden Realitäten in der Informationsverarbeitung 60%+ der CEOs: Sollten besser sein in der Einbeziehung/Nutzung der Informationen für bessere Geschäftsentscheidungen Nur 1/3 der CFOs glauben, dass Informationen einfach zu nutzen sind, gut aufbereitet, kostengünstig erschlossen und integriert sind Transaktionen Dokumente Berichte s Media Kunden Personal Partner Databases Organisationen Finanz Produkte Web Content 48 unterschiedliche Finanzsys. und 2.7 ERP Sys. im Durchschnitt ($1 Mrd Unternehmen 79% der Unternehmen: haben 2 + Repositories… 25%: haben 15 + 85% der Information ist unstrukturiert 30-50% der Designzeit ist Copy Management 17% des IT Budgets für Storage: HW+SW + Personal 30% der Zeit für Suche von relevanten Informationen Reality is we have lots of disparate financial systems driven by mergers, acquisitions, different countries, multinational, and also over time we pick up multiple ERP systems, legacy, modern and the migration between the two. Not to go through the factoids, but there is a lot of data and it’s growing rapidly, 85% is unstructured and the challenge that many it organizations fast is the management of lots of data, lots of copies manage it consistently and securely, and be able to pull more in. Reality belies the vision that we have and have had in the IT industry for the last 30 years. 37% CGR Disk Storage Wachstum ’96-’07 40% des IT Budgets können für Integration ausgegeben werden 122 Terabytes Disk Storage in 2005 Sources: IBM & Industry Studies, Customer Interviews

Der Ort für die Datenhaltung ist wichtig…
Der Ort für die Datenhaltung ist wichtig…. Vertrauen in System z, z/OS und DB2 for z/OS Integrität z/OS System Integrität - Programmierstandard System z Integritätsfeature schützt die Daten Hochverfügbarkeit Design für ‘immer verfügbar’ Philosophie im Gegensatz zu ‘schneller Reboot’ Philosopie Fähigkeit für ‘concurrent’ HW-Wartung und Upgrades und rollierende Änderungen bei DB2 for z/OS (im Parallel Sysplex) bedeuten weniger Datenbankausfälle Sicherheit Verschüsselung, Verschlüsselung, Verschlüsselung – umfassende und ausgereifte Lösung MLS – Daten in einem einzigen Server mit Datenschutz. Einhaltung der Adressregualarien mit der Möglichkeit für zentrale Regeln und Prozeduren für Vertraulichkeit, Sicherheit und Revisionsicherheit System und Datenbankmanagement DB2 for z/OS in: 25 der top 25 WW Banken* 23 der top 25 US Händler** 9 der top 10 globalen Lebens- und Krankenversicherhungen*** System z9 109 Erweiterungen: Erweiterte Book Verfügbarkeit & Treiber-Wartung Verbesserter Datenzugriff: hohe Bandbreite & FICON Kanäle Compliance & Sicherheit We’ll start with a set of specific facts to remind you of the confidence you can have in System z, z/OS and DB2 for z/OS. We’ll point back to our system integrity programming standards which have been around since the days of MVS. We continue to put these in writing and update. And we have a number of technology points to help protect data on mainframes. We’ll point to a number of specific technology features around the design for high availability on mainframes which is really designed to ‘never go down’ as opposed to ‘reboot’. We’ll point to a number of very specific things that we’ve done in db2 v8 to provide much higher application availability. We’ll point to a number of specific things that we’ve done around security both as it relates to encryption in the z9 announcement, multi level security (MLS) - which was done in collaboration with z/OS and db2 on mainframes to provide a much more granular view of data to the user and to be able to better manage and control what person sees what row of data. And we done a lot over the last few years to increase the systems and data base management capability – both in terms of self manage and resource tuning capabilities- which first came out in db2 v7 and autonomic advances that we’ve made in both the operating system and in DB2 v8. Important to note that it starts with the notion where you put data matters… and there are proof pints to support what we say. * WW Banks from The Banker.com: **US Retailers from National Retail Federation July 2005: ***Insurance Ward's 50 Benchmark Group:

Technologie-Evolution mit speziellen Engines des Mainframes
Aufbauend auf klarem Weg für innovative Technologie mit speziellen Engines, beabsichtigt IBM die Einführung des System z9 Integrated Information Processor IBM System z9 Integrated Information Processor (IBM zIIP) geplant für 2006 Zentrale gemeinsame Nutzung der Daten cross Mainframes Design zur besseren Ressource-Optimierung für ausgewählte Daten-Workloads im Unternhemen System z9 Application Assist Processor (zAAP) 2004 Internal Coupling Facility (ICF) 1997 Design für bessere Ressource Optimierung für auf z/OS Java-Technologie basierende Workload Integrated Facility for Linux (IFL) 2001 This slide covers the concept of our mainframe specialty engines and how they have evolved over time. We’ve had the Internal Coupling Facility (ICF) available to support our parallel Sysplex environment and centralized data sharing across mainframes. In the 2001, we introduced the Integrated Facility for Linux – our specialty engine for Linux. The IFL was designed to help bring Linux workloads onto the mainframe and support open standards. We’ve had a lot of success and excitement there and continue to invest in Linux, z/VM and the qualities of service the mainframe can bring to supporting a large ‘virtual’ server environment. We continued to build on the specialty engine story with the introduction of the zAAP in There has been lots of interest as customers are really starting to see the benefit of being able to run Java based workloads like WebSphere on the mainframe. By utilizing the zAAP customers are able to leverage the capabilities that the mainframe has to support mixed workloads as well as having the applications close to the data. As we’ve introduced these specialty engines, our customers have said they like the concept of specialty engines, finding them to be simple, affordable, and really helpful to their goals for the mainframe – and so they ask us to please do more. Specifically, customers have asked IBM to do more in the way in helping them with mainframe database workloads. So a real highlight of January 24 announcement will be the new System z9 Integrated Information Processor (zIIP) – it’s the next big proof point on how the mainframe is continuing to evolve to play that ongoing role as the hub - in this case specifically as the hub for data. It is the latest edition for the specialty engine family and as we move to the next slide we’ll talk about some of the details of the zIIP. Support für neue Workloads und Open Standards

Workloadarten für DB2 for z/OS die vom zIIP Nutzen ziehen können
ERP oder CRM Application Serving* Für Anwendungen mit z/OS, UNIX, Linux, Intel, oder Linux auf System z, mit Zugriff auf DB2 for z/OS V8 auf einem System z9 109, über DRDA über eine TCP/IP Verbindung gibt DB2 dem z/OS die notwendigen Informationen, um Teile dieser SQL Requests auf den zIIP zu verlagern. TCP/IP CP Neue Engine Data Warehousing Applications* Bei Requests die DB2 for z/OS V8 Star Schema Parallel Queries nutzen, können Teile dieser SQL Requests auf den zIIP verlagert werden, wenn DB2 dem z/OS die notwendige Information gibt Einige DB2 for z/OS V8 Tools und Utilities* Teile der internen DB2 Utility Funktionen, die für die Wartung der Index Maintenance Struktur (Beispiel LOAD, REORG und REBUILD INDEX) laufen typischerweise in Batch und können verlagert werden auf den zIIP. DB2 for z/OS workloads that may benefit from zIIP. * The zIIP is designed so that a program can work with z/OS to have all or a portion of it’s Service Request Block (SRB) enclave work directed to the zIIP. The above types of DB2 V8 work are those executing in SRB enclaves, portions of which can be sent to the zIIP.

Spezielle Engines z/OS LPAR WAS Application zAAP TCP/IP HiperSockets z/OS LPAR IBM System z9 spezielle Engines können auf der gleichen Maschine zusammenarbeiten links gezeigt, wo der zIIP bereitgestellt wird DRDA DB2 WAS Application Application Application nicht auf System z D R A TCP/IP Star Schema zAAP CP zIIP DRDA TCP/IP HiperSockets Linux on System z LPAR Application IFL

Struktur von DB2 auf z/OS

IBM zIIP Data Serving Workload Beispiel mit SAP Lösung
SAP NetWeaver basierende SAP Lösung kann die Vorteile des IBM zIIP nutzen Linux for zSeries AIX® Web AS Web AS DB2 Connect DB2 Connect™ HiperSockets CP Windows TCP/IP Central Services Web AS Collectors DB2 Connect New Engine z/OS Linux DB2 V8 Data Sharing Web AS CP DB2 Connect Ermöglicht Wachstum der System z9 SAP Workloads durch Ressource Optimierung

Instanzen, bei denen der zIIP nicht zum Einsatz kommt
z/OS LPAR WAS Anwendungen mit Zugriff mit lokalem Type2 JDBC Access. Aus Performancegründen ist dies das empfohlene Szenario, da der WAS Code für diese Konfiguration optimiert ist. Hier wird kein zIIP gebraucht. WAS Application DB2 zAAP QMF™ (TSO) Batch CP CP CICS® IMS™ CP CP

System z9 und DB2 for z/OS sind die ideale Data Serving Plattform
Konsolidierung der Daten reduziert: mehrere Kopien, ungleiche Daten Kosten und Komplexität von Back up und Recovery Netz-Traffic Storagemenge DB Administration und Management Risiko durch verteilte Vertraulichkeit, Sicherheit und Auditregeln Weiterentwicklung System z Technologie Parallel Sysplex Clustering mit Skalierbarkeit und Verfügbarkeit und Performance Data sharing = Eine Sicht der Daten Datakompression für TCO Zentrales Backup, Recovery, Vertraulichkeit Sicherheit und Auditregeln Die neue System z9 Engine (geplant für 2006) hat Design für: Integration der Daten cross Unternehmen Bessere Ressourceoptimierung Verringern der TCO für Data Serving Workloads Vorher Distributed Data App Daten App Daten App Server App Daten App Daten z/OS Datenbank Server App Server App Daten App Daten zIIP fähig Nachher Daten Integration, zentraler Datenservice App Daten App Daten App Server z/OS Datenbank Server App App App App Server App

Hier nur einige Partner, die System z als unternehmensweiten Datenserver unterstützen

Vision für System z mit fortgeschrittenem Data Serving System z Unternehmens-Hub für Mission Critical Data With a strong foundation for transaction processing, built on 40+ years of technology innovation, System z servers with z/OS and DB2 can provide a premiere platform for data serving, today and into the future* IBM plans to continue to invest in new solutions to address customers' strategic information on demand goals* Future direction* Extension of capabilities* Additional zIIP exploitation DB2 enhancements to help improve usability and reduce complexity and management costs. DB2 table scan acceleration via DS8000 Support of encryption capability (disk subsystem) with z/OS centralized key mgmt Handle larger volumes of data, with improved scalability Today’s Capabilities New specialty engine (zIIP) with DB2 exploitation - for mission critical ERP, CRM, and Data Warehousing workloads * Database support improves regulatory compliance and autonomics Support of encryption capability (tape subsystem) with z/OS centralized key mgmt Data protection to achieve highest levels of security certifications Industry leading data integrity and security Data sharing solution for centralized view of data Scalability and availability for enterprise class workloads Comprehensive systems and data management environment *All statements regarding IBM’s future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only.

DB2 for z/OS vNext – Addressierung der Ziele für Unternehmensdaten
Verbesserte IT Infrastruktur für die Unterstützung der Kompliance Trusted Security Kontext Rolle der Databank Audit-Fähigkeit Vereinfachung von Entwicklung und Portierung Viele SQL Erweiterungen zur Vereinfachung der Portierung Native SQL Stored Procedures Default Datenbanken und Tablespaces Automatische ‘unique’ Indexe zur Unterstützung der Definition von primary keys Reduzierung der Komplexitä und der Kosten Fast Table Replacement Partition by growth Table Anhang Volume-basierendes COPY/RECOVER Optimierung Service Center Weiterentwicklung der Umgebung & SOA Integriertes XML WebSphere integration IBM will be moving into early ship in the May time frame and we will be making this generally available in November and December timeframe. The way to think of DB2 vNext is in the following context: If you go back to V7 of DB2, it was based on system r technology that was fundamentally built and conceived of in the 1970s. If you think about relational data bases on other platforms (UDB, Oracle and the like), by and large the technology time frame of their genesis was the mid to late 1980s with a later generation of relational technology. So as a consequence, if you go back to V7 and prior, typically we would work very hard and spend most of our investment to optimize the database to the mainframe, however when it came to things like open standards and new function, quite frankly the mainframe was lagging. We started to make major changes to that in V8. With DB2 for z/OS V8 we took the once in a decade opportunity to completely redo the kernel with improvements to a lot of the physical and logical limits that customers were experiencing, and we also re-base-lined the technology to be on the same technology base that was on UDB and other competitive data bases. So it was a technology re-base-line. We then proceeded to reengineer the SQL language to make it much more open. We wanted it to be consistent with open standards and other databases. We had seen a number of customers taking advantage of the implicit advantages of easier and faster portability, since many wanted to move data and applications around between platforms. The third point in our V8 revamp, was that having redone and reengineered the base in the product, we now began the journey of taking functions that had only before run on UDB (distributed as an example) and moving them to the mainframe where we began the process of sizing opportunities to exploit zOS and the System z hardware environment to deliver unique function exploiting mainframe qualities of services. On a prior side we already mentioned that security is one of those mainframe areas we wanted to exploit – and we did that with multi-level security (MLS). We also announced with the z9-109 that we’d made modifications to the channel architecture – the MIDAW Facility – which as resulted in 50% plus I/O throughput for DB2 on mainframes when using FICON. So, fundamentally, DB2 vNext builds on v8. It is NOT a rework of the kernel but it does contain a significant amount of function that we’ve moved from distributed world to the mainframe as well as number of new and unique functions that we are putting in that will further exploit the unique capabilities of the mainframe This release if very heavy on function and has a lot of line items. The themes in general for DB2 vNext are: Enabling high volume transaction processing for next wave of web applications Extend the lead in transaction processing through availability, security and performance improvements Reduce total cost of ownership by reducing the labor intensity and skills requirements We want to work with the hardware to reposition and revitalize the mainframe for data warehousing and data mining. In terms of the specifics and there are a lot of them, lets look at a few key ones. Improved IT Infrastructure in support of compliance efforts Let’s start with support for compliance. With MLS we had significant amounts of granularity, in terms of what users saw (by row of data). We’ll dramatically extend that thinking within the notion of trust and the security context. Today the customer has the option to set a system parameter that indicates to DB2 for z/OS that all connections are to be trusted - a binary thing. What we will be doing in vNext is providing the capability for the data base administrator to set different parameters and settings around the connection type, the server type, as well as the user type. This will give much more granularity to different levels of trust within a security context. We’ll integrate this with z/OS Workload Manager in order to provide more automatic capabilities to manage different types of work from a performance perspective. And many large customers are telling us that they are concerned about the possibility of inside theft. With the July and September 2005 announcements remember that IBM announced a lot of enhancements in the z9-109 and z/OS - specifically in the area of tape security. We will do some things in terms of DB2 vNext to encrypt major parts of the DB2 system resource itself. We’ll give the customer’s security officer the ability to define roles and then limit what the data base administrator can see and access and not see and not access. For example they’ll be able to access prime shift but not third shift, weekdays not weekends – a wide variety of abilities. With this the customer is better able to manage and control what a data base administrator tech does, task-wise, day in and day out. And will have the management capability to back it up. And in addition DB2 vNext will have extensive audit capabilities in terms of improved trace and trace filtering. We can do a better job of investigating and auditing who is touching what data. Customers are telling us that they don’t want data base administrators to have full access to all the data within the company. You want to be able to give the data base administrator privileges and then, if needed, remove those privileges. And you want to be able to manage the changes according to the needs of the business using a policy base. You also want to have the capability to do audit trace as well. And all these items will be a mainframe advantage, building upon multi level security which we did on v8 with z/OS. So major changes here on the security and compliance. Simplify development and porting From a simplification development and porting perspective we are making major enhancements. There has been a long standing requirement for native SQL stored procedures so we will be delivering that with vNext. The language we’ll use is ANSI standard and it is similar to the propriety stored procedure languages of several competitive data bases, which will further facilitate migration and porting onto DB2 for z/OS. Typically this type of capability is done in a way that the statements are created and then they are converted into C such that the execution is C code. The implementation with DB2 on the mainframe, being new, will be to have it run natively into the DB2 engine which will eliminate the need to convert it to C. So on the mainframe, not only do we get the SQL function for stored procedures, but we will do it in a way that is very efficient and delivers excellent performance. We’ll provide the capability for default databases and tablespaces this also have implications on porting. We will give z/OS and DB2 vNext the ability to dynamically create indices as opposed to having applications and DBAs produce them. There are many other specific line item features has been put into DB2 vNext in order to enable further development and porting – and that is on top of the continued re-engineering of the SQL language such that we move from about 80% commonality with the open standard of our code, to up into the mid to high 90%s. We’ll never get to 100% because we will need to maintain support older legacy SQL statements to support existing applications. In summary, we’ve made major strides to make DB2 vNext not only very compatible with open standards but also we put in a number to very specific functions and facilities to enable porting in a relatively easy and high performance way. Decrease complexity and cost In terms of decreasing complexity and cost we are adding a lot of specific items. One is fast replacement of a table which you can literally think of this as cloning. It allows a customer to generate a copy of a table with the same attributes, and the same data, in the same table space, and to the application/user it will appear as a very fast replacement of data within a table. This ties with the main theme to enable the next wave of web applications. We’ve found the need for cloning tables is driven heavily by web based applications that need maximum availability to get at the data and get copies of the data for things like application testing and auditing. So cloning will be a major function addition in vNext. Partition by growth will help make growth more automatic and dynamic. Today, partition tables have required key ranges to determine the target partition for row placement. With this capacity you will no longer need key ranges. Table appends simply says that we will be able to offer increased performance for inserting data at the end of a table. And as we did with V8, we will continue to have major enhancements around indexing - specifically index compression . DB2 vNext will provide index support for compression for larger index page sizes and indexing of expressions. IBM is finding that a lot of the emerging workloads on data warehousing are dependent on this type of indexing capabilities so these functions are being specifically added in order to facilitate and improve performance in the data warehousing arena. We have had a lot of focus on autonomics with DB2, starting with smart technology in v8. In vNext, we will introduce an Optimization Service Center. It will be GUI based, as opposed to 3270 green screen, and it will integrate with the DB2 engine and fundamentally will capture meaningful information about workloads and how they are running and provide insights to the DBA and performance manger on things that they can do to specifically tune and improve performance and the availability of the configuration. Some of this will also be in the tooling. We’ll extend and enhance a lot of our DB2 tooling around the adviser notion, or expert notion, and provide experts for query formulations, rewrites, history of execution over time, query patterns, and so on. Evolve your environment and SOA The last point is on Service Oriented Architecture (SOA) where we will be making major changes to the way that we implement XML to improve usability and performance. In effect, we will do it and we are going to be sharing the common code to do this with DB2 for Linux, Windows, Unix and also parenthetically IMS. We’ll provide an extender to DB2 vNext that the customer can optionally install to provide engine integrated support for XML documents, and associated functions for dealing with large character documents and the breaking up of XML documents into relational columns for storage and query. And we’ll continue the theme of integration with WebSphere by adding a number of specific items, including optimistic locking support and automatic time stamping, the combination of which basically eliminate the need for application programming within WebSphere itself, improved performance and simpler migration of Java applications to mainframes and DB2 for z/OS on the mainframe if the customers choose. Lots of updates to vNext. We’ll be coming out with more detail over the next several months. To summarize - you can think of this announcement as a major set of function enhancements on the mainframe that move it from being backlevel, with V7, to reasonably competitive in the v8 time, to highly common and open and having a leadership role in vNext.

Nächste Schritte Kunde sollte prüfen
Qualifikation für zIIP Einbeziehung ISV Lösungen wie SAP, PeopleSoft und Siebel und andere ISV Workloads. Überprüfung der Vorraussetzungen System z9, DB2 V8 und z/OS 1.6 mit zIIP Spezielle Angebote für zSeries Information als Service (zIAS) zSeries Data Server Upgrade und Tools DB2 Version-to-Version und Tools Portion of the Play

System z Data Serving Roadmap
Today… Tomorrow… Future… System z9 mainframes & z/OS combine for Industry Leading Performance, Scalability, Security, Availability and Virtual Partitioning capabilities with a focus on TCO improvements DB2 Universal Database™ (UDB) for z/OS provides the premier high performance DBMS for high volume transaction workloads based on relational technology. Security for z/OS and DB2 is designed to provide protection and advanced encryption capabilities with focus on recognized industry certifications DB2 Content Manager for z/OS provides a foundation for managing, accessing, and integrating critical business information on demand. WebSphere Information Integration Platform for z/OS can help you readily access your pertinent information to support strategic business initiatives DB2 Business Intelligence Solutions for z/OS provides cost-effective, rapid access to your core business data for warehousing and analytics IMS & DB2 for z/OS Tools & Utilities provide integrated and intelligent management & monitoring of your IMS & DB2 applications and performance IMS Version 9 extends and enhances your Industry Leading IMS environment with increased connection & integration capabilities DB2 V8 Exploitation of a new specialty processor (zIIP – System z9 Integrated Information Processor) - types of eligible DB2 for z/OS V8 work, portions of which can be sent to the zIIP include: - Network Connected Application processing using DRDA over a TCP/IP connection - Data Warehouse Query processing that utilize star scheme parallel queries - Select index maintenance in the DB2 Utilities (LOAD, REORG, REBUILD) DB2 for z/OS Enhancements - Unmatched infrastructure for supporting customer needs for regulatory compliance and auditing - Continue to improve people resources efficiency - Integrated XML - DB2 Spatial Data Support - OmniFind Search in DB2 Security for z/OS and DB2 Enhancements -Common Criteria EAL Certifications -Support of encryption capability (tape subsystem) with z/OS centralized key mgmt z/OS Scalability & Resource Management Enhancements -Enhancements in Device Addressability -WLM Dynamic DB2 Bufferpool Management -z/OS Global Mirror (XRC) and Global Mirror (asynchronous PPRC) consistency groups WebSphere Information Integration Platform -zSeries legacy data replication DB2 and IMS Tools Focus Areas -New and enhanced tools in recovery and performance -Additional Support for SAP environments, Content Management & Business Integration IMS Enterprise Support on z/OS -XQuery Support -Integrated Connect XML Adapter support Further exploitation of zIIP Additional DB2 for z/OS Enhancements - Improve usability and reduce complexity - Java Language Integrated Query - DB2 Table Scan acceleration via DS8000 processing Ongoing Security Enhancements - Common Criteria EAL4 Certification for DB2 - Support of encryption capability (disk subsystem) with z/OS centralized key mgmt System z9 server and z/OS Futures - Continued FICON Enhancements - Continued focus on Storage capability & capacity - Heterogeneous File Sharing Support - NFS V4 Client - Continuous data protect - Dynamic storage provisioning DB2 CM for z/OS Advancements - XML API and Web Services WebSphere Information Integration Platform - Expanded integration and process automation across and between platform components DB2 and IMS Tools Focus Areas - New function in change management - Increased function to help meet compliance requirements - Continued advancements in key functional areas Additional IMS Futures - Enhancing IMS XML and Web Services Connectivity - Integrating Operations across Subsystems/Platforms - Simplifying Installation and Management *All statements regarding IBM’s future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only © 2004, 2006 IBM Corporation

Information als Service bringt Flexibilität
Trigger Trigger Prozess A Prozess B Information als Service Shared Metadata Data Warehouse Kern- Anwendungen Packaged Application Konsistene Daten Gemeinsame Nutzung und Beziehungen über Metadaten Konsistente Regeln für Daten Zentrale Kontrolle und Wartung Flexible Anpassung an Veränderungen der Informationsquellen und Formate SOA centralizes and standardizes the approach to data integration for processes Within this approach, data integration really just becomes a set of rules applied to data that can be called by EAI to make what they do better Providing: Consistent definition and packaging of data from process to process Consistent rules applied to the data Ensured data quality Centralized control and maintenance It also leverages profiling, quality and metadata relationships to ensure that the best and most complete data is used and that the processes understand where it came from When data access is more ad hoc and the same information is frequently accessed, EII can provide flexibility, reduce database load, and improve performance The integration between data integration and EAI leverages the concepts of SOA Ideally, there are multiple options (or what we call bindings) for connecting data integration services into EAI This is what is going to provide flexibility and meet the broadest range of project requirements We’ll discuss the pros and cons of each of these in a moment.

Architektur-Evolution im Unternehmen On Demand Business und technische Flexibilität
Auf Services basierende Architektur möglich auf Basis von Open Standard ist nächste wichtige Computing-Ära Vor 1980 Batch Online 1980 bis Mitte 1990 Mitte 1990 bis Anfang 2000 Heute On Demand Zukunft Systems Agenda Monolithische Architektur Client-Server Architektur Network Centric Architektur Service Oriented Architektur / Web Services Dynamische System- architektur: einheitlich (rekonfigurierbar) Mainframe eBusiness eCommerce Service Oriented Computing Web Services Architektur Virtualisiert Offen kollaborativ

Enterprise Hub für SOA: Flexibles Business erfordert flexible IT
Volle Business Sicht Prozess zur Optimierung Bank Shared Service Customer Bank 2 – “Supplier” Outsourced Case Study: Payments Processing Aufbau IT Flexibilität ´Hürden’ für Business Flexibilität Fehlende Standards für Geschäftsprozesse Begrenzte Architekturregeln Spezielle Anwendungen zum Support redundanter LOB Erfordernisse Aufbau der Infrastruktur ohne Roadmap IBM SOA Foundation Software Skills & Support

SOA auf System z9 und zSeries – Modernisierung der wertvollsten Umgebungen! Erweiterung und Anreicherung der Kernanwendungen in CICS, IMS und WebSphere Creates opportunities for new business processes with … CICS, IMS und DB2 sind bereit für SOA! Laufähig auf allen Plattformen einschliesslich z/OS and Linux on zSeries $5,000,000 Mrd ($5T) Kernanwendungen der zSeries WebSphere SOA Plattform Produke Für Wiederverwendung schnell und zeitgerecht geringes Risiko geringe Kosten .. mit Serviceintegrität Sicherheit Verfügbarkeit Wiederherstellbarkeit Für erweiterte Services.. User Interaction Prozessmanagement Information Integration Enterprise Service Bus Unlocks the value of…

Was ist Service Oriented Architecture (SOA)?
SOA Definition Was ist ein Service? Eine wiederholbare Business Task z.B. Prüfung Kundenkredit oder Eröffnung neues Konto Was ist Service Orientierung? Ein Weg zur Integration des Business als vernetzte Services die ein Ergebnis, mit sich bringen Was ist Service Oriented Architecture (SOA)? IT architekturale Methode, die die Serviceorientierung unterstützt Was bedeutet SOA für das Business? - Flexibilität für Business - Guter Kundenservice - Geringe Kosten und hohe Effizienz It is appropriate to take some time to understand and define what SOA is all about.

Was unterscheidet SOA von bisherigen Methoden der Vergangenheit?
Breit akzeptierte Webservices bringen klar definierte Interfaces. Vorher, proprietäre Standards resultierten in Vendor lock-in Standards SOA vereinigt Business und IT (66% der Projekte werden von der Businesslinie getrieben) Vorher definierte die IT allein das Design Organisatorische Commitment SOA Services definieren jetzt grobere Business Tasks Davor hat jedes wiederverwendbare Objekt feinkörnige Subprozesse definiert Level der Abstraktion SOA Services können extensiv wiederverwendet werden und ermutigen die Wiederverwendung Davor war jede Wiederverwendung innerhalb von Siloanwendungen Level of Reuse SOA Services sind lose angebunden und dynamisch vernetzt Davor musste jedes wiederverwendbare Objekt rigide und fest verbunden werden Connections What is different about SOA from earlier approaches? STANDARDS Earlier architectures were not standards-based which resulted in vendor lock-in to specific architectures. Broadly adopted Web services standards ensure well-defined interfaces. LEVEL OF ABSTRACTION Earlier architectures used the concept of objects, but those objects tended to be very fine-grained, basically sub-processes. SOA lets you define much larger-grained business functions. CONNECTIONS Earlier architectures had poor reuse capabilities. Any reuse tended to be confined to siloed business applications. SOA services can be extensively reused and encourages asset repurposing. ORGANIZATIONAL COMMITMENT In earlier architectures, IT alone defined the design of a business system. SOA unites business and IT to build solutions together.

Erweiterte Nutzung der Kernanwendungen für besseren Informationszugriff
Kunden Angestellte Lieferanten Core Applications Core Applications Core Applications Core Applications Kern Anwendungen Core Applications Linux Web User Interface Portale Linux Neue Anwendungen Verteilte und Partner Systeme Linux WAS Linux IMS Linux CICS Linux DB2 Web Services And this is how you might show it… Core applications on the right; whether they run under IMS, CICS or DB2; can connect to portals and new applications (running either on mainframe z/OS, mainframe Linux or on distributed platforms) to provide faster and better access to information. Slide 14 please Linux, z/OS, VSE, TPF z/OS und Linux Server Farmen

Mainframe Basis für unternehmensweite SOA
Applications Applications Anwendungen Processes Portals Information Processes Portals Information Prozesse Portale Information Kunden Angestellte Lieferanten Advanced Enterprise Service Bus Partner Systeme Advanced Enterprise Service Bus Advanced Enterprise Service Bus Access control Assured delivery Transaction and Workload Management Access control Assured delivery Transaction and Workload Management Zugriffskontrolle Sichere Bereitstellung Transaktions und Workload Management And this is how you might show it. Applications and systems running across and beyond the enterprise, can be connected via an Advanced Enterprise Service bus that delivers enterprise-wide SOA infrastructure services with mainframe qualities of security, availability and recoverability. Slide 16 please Entfernte (Geschäftstellen ) Abteilungs- systeme Server-Farmen

Mainframe als unternehmensweiter Datenserver
Applications Applications Anwendungen Applications Analytik Automatisiertes Backup Hierarch. Speicherung Information Integration Kunden Angestellte Lieferanten Rollback und Recovery f.Transaktion Hardware Verschlüsselung Storage Virtualisierung Real-time Entferntes Backup Event-getriebene Integration And this is how you might show it. Mainframe applications, analytics, storage, security, backup, recovery and information integration capabilities can be leveraged by users and by applications wherever they are sited. Departmental applications can work on mainframe data. Data can be replicated across server farms. Business events can be identified and reported across geographically dispersed systems. Real-time backup on a remote mainframe server can provide the highest levels of continuity and recoverability in the case of natural or man-made disaster. Slide 18 please Federation Replication Entfernte Büros Abteilungsysteme Server-Farmen

Paradigma Shift: SOA ist eine Revolution – Bereitstelllung ist evolutionär
Von zu Prozess orientiert Ausgelegt auf Veränderung Inkrementell aufgebaut und bereitgestelt Funktionsorientiert Ausgelegt auf Dauer Lange Entwicklungszyklen Application Silos Lose verbunden Mit Komponenten und Objekten zu strukturierten Anwendungen Bekannte Implementierung Orchestrierte Lösungen Lose verbunden Strukturierte Anwendungen über Services Abstrakte Implementierung SOA ist ein Paradigmenwechsel. Komponentisierung und Prozessoptimierungen sowie die Erstellung kleiner, überschaubarer und leicht zu verbindender Komponenten und Einheiten sind Hauptmerkmale von SOA. Überleitung: wie stellt sich die Service Oriented Architektur dar?

Aufbau von SOA Anwendungen aus bestehenden Funktionen
Modellierung neuer Businessprozesse aufbauend auf bestehenden Funktonen ….. …Erfassung von Programm- Units und Business Rules zum Wiederverwenden in neuen Prozessen. Modellierung WebSphere Studio Asset Analyzer WebSphere Business Modeler Wrapping von Programmen als Services, Aufbau von zusammengesetzten Anwendungen aus Kern-funktionen…. … und Zusammenstellung der Services cross multipler Plattformen Assemble WebSphere Developer for zSeries, plus Service Flow Modeler WebSphere Integration Developer Choreographie und Auslieferung neuer zusammengesetzter Anwendungen …. … Einsatz eines ausgereiften ESB zur Unterstützung von SOA WebSphere Message Broker Bereitstellung WebSphere Process Server IBM has a complementary set of WebSphere tools that make it straightforward to build and deploy new composite applications from new and existing programs. Model One of the key attributes of an SOA is the ability to reuse existing program assets – so the process starts with discovering which program assets you already have that you can reuse in new applications. WebSphere Studio Asset Analyzer helps you discover these hidden assets by determining which programs are good candidates for reuse in Web applications based on the number and type of changes required. Once you understand what business operations you already have coded and available, you can use WebSphere Business Modeller (WBM) to create end-to-end process models that represent key business processes throughout the enterprise – some of which are represented by the assets discovered by WSAA. WBM helps you to understand and transform your business through business modeling, simulation, analysis, and collaboration capabilities. You can use the models you build with WBM to direct your Assemble and Deploy activities for creating composite applications. There are other tools (not shown in the slide) that can help you to reuse your existing applications. Many enterprises use CICS to run their core business, and they have large amounts of reliable and trusted CICS code. CICS Interdependency Analyzer helps you to understand, preserve, evolve and integrate existing CICS applications with new on demand application models. In addition, Asset Transformation Workbench helps you identify the business rules coded within your core applications, and helps in restructuring large applications into more manageable segments and removing dead code. At the end of the modeling phase, you should have a clear idea of the assets that you have available, and where they can be used in the new business processes that you have modeled. The next stage is to create services and assemble them into deployable composite applications. Assemble WebSphere Developer for zSeries V6 (WDz) includes capabilities that make traditional mainframe development, Web development, and composite application development faster and more efficient. If you you use CICS, IMS or WebSphere transactional environments, WDz simplifies the development of new Web user interfaces, traditional terminal interfaces, and back-end business logic. You can wrap your CICS and IMS transactions as Web services and, because so much business is transacted using CICS applications, you can model and reuse core assets from CICS systems with Service Flow Modeller (SFM, part of WebSphere Developer for zSeries). SFM models and renders CICS transactions of all kinds (3270, comm area) into callable web services. WebSphere Integration Developer V6 (WID) is a new tool for rapid assembly of business solutions that allows you to construct all styles of processes with one programming model based on Business Process Execution Language (BPEL). It requires relatively minimal skills, with easy-to-use authoring tools, so it’s highly productive, and offers features for integrated development, testing of the models. When you’re happy with your composite application model, then you can deploy it to the WebSphere Process Server in the next stage. WID combines well with other development tools from IBM, for example, Rational Application Developer (not shown on the slide) and WebSphere Business Modeler in the Model stage of the process. Deploy WebSphere Process Server V6 (WPS) is the runtime engine that controls the execution of all the Web services created in the previous steps, and drawn together via the WID tool. It is the culmination of discovering assets and business rules, bringing them into a model of a business process, and then plugging individual executable Web service components into the model. WPS deploys the composite applications, and controls the execution of the process, choreographing the individual programs in the process into an automated flow. The runtime process is very flexible -- for example, you can replace, say, a human task (like an approval) with a business rule without changing anything else in the entire solution. This is an extremely powerful capability that fully delivers on the promise of SOA for delivering greater flexibility and responsiveness to your business. This is possible because of the ESB. Message Broker is IBM's advanced ESB, and has the ability to handle connectivity to any application, whether standards-based or not. This means that you can choreograph any of your applications through WPS, making it particularly attractive to the established customer with a large base of trusted existing applications - the typical zSeries customer. The power of the Message Broker is that it can mediate and transform messages in flight to meet the needs of the receiving applications, offloading the mediation processing to a zAAP processor, with an immediate benefit in performance and throughput. Manage WebSphere Business Monitor V6 (WBMonitor) measures the actual performance time of every process and process step. This provides you with accurate information about how the process is executed by and for its users, and the knowledge you need to design the site, up the capacity or any other changes that will benefit the majority of your users. Furthermore, because the information is dynamic, anything of interest –like a group of users having really long response times—can be investigated on the spot by clicking and drilling down on the data. The answers are immediately available and presented in graphical form as well as in columns and text. There are other tools (not shown in the slide) that can help you to reuse your existing applications. The real power of the Business Monitor is the ability to take your real time data and load it back into the Business Modeler for analysis. The ONLY way to optimize your processes is to run simulations and ‘what-if’ scenarios using your REAL business data – and that’s what Business Modeler does, completing the loop of continual improvement, re-using existing assets. Summary IBM, through the WebSphere family, provides a complete set of tools that enable you to build dynamic new flexible processes that capitalize on your existing applications, reusing them in new and profitable ways. All aspects of the development cycle, from identifying what existing assets you can use, through deploying them in new and flexible processes, to monitoring the efficiency of your new processes, are covered with easy-to-use and effective tools. The slide shows a virtuous circle, a beneficial loop of continual improvement based on reuse of existing, trusted assets. …. und Export der Daten für Analyse und Prozessverbesserungen…. Monitoring der Prozesse cross SOA und Eingriff bei Erforderniss. WebSphere Business Modeler WebSphere Business Monitor Management

System z9 und zSeries: Für SOA heute und morgen
Weiterentwicklung zSeries Infrastruktur Basisplattform für Integration. z/Architektur, Virtualisierung, Sysplex, z/OS V1.6 und V1.7, WLM/IRD, zAAP, IFL, Linux Modellierung & Erfassung Business Funktionen und Prozesse. WS Business Modeler, Service Flow Model for WDz, WS Asset Analyzer, Rational Rose/XDE, CICS Interdependency Manager Transformation, Modernisierung & Erweiterung Kernanwendungen, Prozesse und Daten. WAS, SOA & Web Services und ESB, HATS, CICS TG, DB2 Connect, IMS Connect, WS MQ Integration Anwendungen, Prozesse und Daten; neue und alte z/OS, PR/SM, zAAP, IFL / Linux, z/VM, HiperSockets WS MQ Workflow, WS MQ Message Broker WebSphere ESB, WebSphere Process Server Management Workload Performance bezogen auf Businessziele. WLM & IRD, EWLM, z/OS Security Server, IBM Director, Sysplex Distributor, VMRM Tivoli OMEGAMON, WS Application Monitor (Cyanea), WS Workload Simulator WebSphere Business Monitor Resiliency & Security Mixed Workloads Gemeinsame Nutzung von Daten Virtualisierung Workload Optimierung z/Architektur Sysplex Cluster Key Points IBM is already investing heavily in zSeries. We already have substantial capabilities in the pipeline. Many of the substantial capabilities that have already been delivered are listed here – along with several of the latest SOA-related technologies currently running on or planned for Z. The increased investment in zSeries that we’ve discussed is intended to further extend and enhance the value of the mainframe to our customers. zSeries is well-positioned to provide world-class business integration, IT infrastructure management and business flexibility – all of which are key benefits of SOA. System z9 bietet fortgeschrittene SOA Integrationsplattgform für on demand Welt!

* Indicates new products
Neue und erweiterte System z / zSeries Produkte Verstärkung der IBM SOA Basis WebSphere Integration Developer* WebSphere Developer for zSeries Enterprise COBOL und PL/I Compilers Problem Determination Tools Process: WebSphere Process Server for z/OS* WebSphere ESB for z/OS* WebSphere Message Broker for z/OS WebSphere Extended Deployment CICS Transaction Gateway People: WebSphere Portal for z/OS Information: WebSphere Information Integrator Application Infrastructure: CICS Transaction Server IMS DB2 WebSphere Application Server & XD for z/OS WebSphere Business Modeler Service Flow Modeler in WebSphere Developer for zSeries WebSphere Studio Asset Analyzer CICS Interdependency Analyzer zSeries specific points: This rich set of SOA-compliant products introduces service oriented offerings and new process management capabilities to the enterprise-class zSeries customer. Products in burgundy text currently run – or have stated plans to run – natively on System z9 and zSeries computing systems. Other products in grey text are Eclipsed-based products that run on distributed platforms/workstations with a rich graphical user interface, and they are capable of deploying composite applications that run on System z9 and zSeries. General speaker’s notes: 15 new and enhanced products! – 6 of which are new. Other Tivoli SOA products include Other Tivoli SOA Products Tivoli Composite Application Manager for Response Time Tracking * Tivoli OMEGAMON XE for WebSphere Business Integration Tivoli Monitoring * Tivoli Netview Tivoli Identity Mgr Tivoli Access Mgr for e-Business Tivoli Business Systems Manager Tivoli Service Level Advisor * Tivoli Configuration Manager Tivoli Provisioning Manager WebSphere Business Monitor Tivoli Composite Application Manager for WebSphere Tivoli Composite Application Manager for SOA * Tivoli Federated Identity Manager CICS Operations Tools * Indicates new products Produkte verfügbar zur Zeit – oder mit festen Plänen – nativ auf System z9 und zSeries. Indikator Eclipse-basierende Produkte auf vert. Plattformen/Workstations mit Bereitstellung gemeinsamer Applications auf System z9 und zSeries.

Business Innovation & Optimization Services Infrastruktur Services
SOA Referenz Architektur - Liefert technischen Unterbau für IBM SOA Foundation Info Assets Apps & Business Innovation & Optimization Services Development Services Interaction Services Process Services Information Services Partner Services Business App Services Access Services Integrated environment for design and creation of solution assets Manage and secure services, applications & resources Facilitates better decision-making with real-time business information Enables collaboration between people, processes & information Orchestrate and automate business processes Manages diverse data and content in a unified manner Connect with trading partners Build on a robust, scaleable, and secure services environment Facilitates interactions with existing information and application assets ESB Facilitates communication between services IT Service Management Infrastruktur Services Optimizes throughput, availability and performance **Main point: The SOA reference architecture is a vendor-neutral way of looking at and planning the set of services that go into building an SOA. The SOA reference architecture is a way of looking at the set of services that go into building an SOA. This architecture is not unique to IBM; these are things that you need to consider when approaching SOA regardless of what products and services are used. These capabilities can be implemented on a build-as-you-go basis allowing capabilities and project level solutions to be easily added as new requirements are addressed over time. You can see that these services organized along the same lifecycle we’ve discussed. On the left in is Development Services which is model and assemble, in the middle are the elements of the deployment run-time environment you use and on the right is management. The backbone of the reference architecture is the enterprise service bus which facilitates communication between services. The reference architecture is a great tool for laying out roadmaps for pursuing SOA. Regardless of what kind of project you’re undertaking, it makes sense to lay it out on a reference architecture to see how the various services you’re designing are going to interact with each other Additional detail: The SOA Reference Architecture outlines the key capabilities that are required for comprehensive, enterprise wide SOA solutions. These capabilities can be implemented on a build-as-you-go basis allowing capabilities and project level solutions to be easily added as new requirements are addressed over time. Tools are an essential component of any comprehensive integration architecture. The SOA Architecture includes both Development Services which are used to implement custom artifacts that leverage the infrastructure capabilities, and Business Innovation & Optimization Services which are used to monitor and manage the runtime implementations at both the IT and business process levels. At the core of the SOA Reference Architecture is the Enterprise Service Bus. This delivers all of the inter-connectivity capabilities required to leverage the services implemented across the entire architecture. Transport services, event services, and mediation services are all provided through the ESB. The SOA Reference Architecture also contains a set of services that are oriented toward the integration of people, processes, and information: Interaction Services provide the capabilities required to deliver IT functions and data to end users, meeting the end-user's specific usage preferences. Process Services provide the control services required to manage the flow and interactions of multiple services in ways that implement business processes. Information Services provide the capabilities required to federate, replicate, and transform data sources that may be implemented in a variety of ways. Many of the services in an SOA are provided through existing applications; others are provided in newly implemented components; and others are provided through external connections to third party systems. Existing enterprise applications and enterprise data are accessible from the ESB through a set of Access Services that provide the bridging capabilities between legacy applications, pre-packaged applications, enterprise data stores and the ESB. The SOA Reference Architecture also contains a set of Partner Services that provide the document, protocol, and partner management capabilities required for business processes that involve inter-actions with outside partners and suppliers. Business Application Services provide runtime services required for new application components to be included in the integrated system. Underlying all these capabilities of the SOA Reference Architecture is a set of Infrastructure Services which are used to optimize throughput, availability and performance. IT Services Management Services include capabilities that relate to scale and performance, for example edge services, clustering services, and virtualization capabilities allow efficient use of computing resources based on load patterns. The SOA Reference Architecture is a complete and comprehensive architecture that covers all the integration needs of an enterprise. Its services are well integrated and are delivered in a modular way, allowing SOA implementations to start at a small project level. As each additional project is addressed, new functions can be easily added, incrementally enhancing the scope of integration across the enterprise. Background: The IBM SOA Foundation delivers the capabilities you need to adopt SOA through a comprehensive architecture. These capabilities can be implemented on a build-as-you-go basis, and yet, because of the architecture and its service orientation, capabilities and project level solutions can be easily added as new requirements are addressed over time. The SOA Reference Architecture shows the key capabilities that are required for comprehensive, enterprise wide SOA solutions. Development Services are an essential component of any comprehensive integration architecture. The SOA Architecture includes development tools, used to implement custom artifacts that leverage the infrastructure capabilities, and business performance management tools, used to monitor and manage the runtime implementations at both the IT and business process levels. Development tools allow people to efficiently complete specific tasks and create specific output based on their skills, their expertise, and their role within the enterprise. Business Analysts who analyze business process requirements need modeling tools that allow business processes to be charted and simulated. Software Architects need tool perspectives that allow them to model data, functional flows, system interactions, etc. Integration Specialists require capabilities that allow them to configure specific inter-connections in the integration solution. Programmers need tools that allow them to develop new business logic with little concern for the underlying platform. Yet, while it is important for each person to have a specific set of tool functions based on their role in the enterprise, the tooling environment must provide a framework that promotes joint development, asset management and deep collaboration among all these people. A common repository and functions common across all the developer perspectives (e.g. version control functions, project management functions, etc) are provided in the SOA Reference Architecture through a unified development platform. The Business Innovation & Optimization Services incorporate monitoring capabilities that aggregate operational and process metrics in order to efficiently manage systems and processes. Managing these systems requires a set of capabilities that span the needs of IT operations professionals and business analysts who manage the business operations of the enterprise. These capabilities are delivered through a set of comprehensive services that collect and present both IT and process-level data, allowing business dashboards, administrative dashboards, and other IT level displays to be used to manage system resources and business processes. Through these displays and services, it is possible for LOB and IT personnel to collaborate to determine, for example, what business process paths may not be performing at maximum efficiency, the impact of system problems on specific processes, or the relationship of system performance to business process performance. This collaboration allows IT personnel and assets to be tied more directly to the business success of the enterprise than they traditionally have been. One key feature of the SOA Reference Architecture is the linkage between the Development and the Business Innovation & Optimization Services. The ability to deliver runtime data and statistics into the development environment allows analyses to be completed that drive iterative process re-engineering through a continuous business process improvement cycle. At the core of the SOA Reference Architecture is the Enterprise Service Bus. This architectural construct delivers all the inter-connectivity capabilities required to leverage and use services implemented across the entire architecture. Transport services, event services, and mediation services are all provided through the ESB. Transport services provide the fundamental connection layer; event services allow the system to respond to specific stimuli that are part of a business process; and mediation services allow loose-coupling between interacting services in the system. The ESB is a key factor in enabling the service orientation of the SOA Reference Architecture to be leveraged in implementing service oriented solutions and can be implemented today to meet the quality of service requirements of any integration solution. The SOA Reference Architecture also contains a set of services that are oriented toward the integration of people, processes, and information. These services control the flow of interactions and data among people and automated application services in ways appropriate to the realization of a business process: - Interaction Services provide the capabilities required to deliver IT functions and data to end users, meeting the end-user's specific usage preferences. - Process Services provide the control services required to manage the flow and interactions of multiple services in ways that implement business processes. - Information Services provide the capabilities required to federate, replicate, and transform data sources that may be implemented in a variety of ways. Automated application services, implementations of business logic in automated systems, are a critical part of any integration architecture or solution. Many of these services are provided through existing applications; others are provided in newly implemented components; and others are provided through external connections to third party systems. Existing enterprise applications and enterprise data are accessible from the ESB through a set of access services. These Access Services provide the bridging capabilities between legacy applications, pre-packaged applications, enterprise data stores (including relational, hierarchical and nontraditional, unstructured sources such as XML and Text), etc and the ESB. Using a consistent approach, these access services expose the data and functions of the existing enterprise applications, allowing them to be fully re-used and incorporated into functional flows that represent business processes. Existing enterprise applications and data leverage the Business Application and Data Services of their operating environments such as CICS, IMS, DB2, etc. As these applications and data implementations evolve to become more flexible participants in business processes, enhanced capabilities of their underlying operating environments, for example support of emerging standards, can be fully utilized. The SOA Reference Architecture also contains a set of Business Application Services that provide runtime services required for new application components to be included in the integrated system. These application components provide new business logic required to adapt existing business processes to meet changing competitive and customer demands of the enterprise. Design and implementation of new business logic components for integration enables them to be fully re-useable, allowing them to participate in new and updated business processes over time. The Business Application Services include functions important to the traditional programmer for building maintainable, flexible, and re-useable business logic components. In many enterprise scenarios, business processes involve inter-actions with outside partners and suppliers. Integrating the systems of the partners and suppliers with those of the enterprise improves efficiency of the overall value chain. Partner Services provide the document, protocol, and partner management services required for efficient implementation of business-to-business processes and inter-actions. Underlying all these capabilities of the SOA Reference Architecture is a set of Infrastructure Services which provide security, directory, IT system management, and virtualization functions. The security and directory services include functions involving authentication and authorizations required for implementing, for example, single sign-on capabilities across a distributed and heterogeneous system. IT Services Management Services include functions that relate to scale and performance, for example edge services and clustering services, and the virtualization capabilities allow efficient use of computing resources based on load patterns, etc. The ability to leverage grids and grid computing are also included in infrastructural services. While many of the Infrastructure and IT Service Management services perform functions tied directly to hardware or system implementations, others provide functions that interact directly with integration services provided in other elements of the architecture through the ESB. These interactions typically involve services related to security, directory, and I/T operational systems management. The SOA Reference Architecture is a complete and comprehensive architecture that covers all the integration needs of an enterprise. Its services are well integrated and are delivered in a modular way, allowing SOA implementations to start at a small project level. As each additional project is addressed, new functions can be easily added, incrementally enhancing the scope of integration across the enterprise. In addition to supporting SOA strategies and solutions, the architecture itself is designed using principles of service orientation and function isolation.

System z9 – Hohe Kapazität und Performance
Neuer Level der Skalierbarkeit Aufbau mit modularem Book Design – ein bis vier Books Fünf Modelle mit einem Maschinen Typ 1 bis 38-wege Server mit hoher Performance (vier Modelle) Bis zu 54-wege erweitertertes Modell für hohe Performance und maximaler Kapazität z9-109 Uniprocessor hat ca 35% mehr Leistung als der z990 Uniprozessor * 54-wege System hat 95% mehr Serverkapazität als z990 Zwei spare Prozessoren pro Server Mehr Memory – bis zu 512 GB pro Server Mehrere Subchannel Sets (MSS) für höhere Anzahl logischer Volumes Bis zu 60 logische Partitions (2X Erhöhung) Hohe I/O Performance Bis zu 80% mehr Bandbreite als der IBM eServer zSeries 990 (z990) Erhöhte FICON Performance mit Modified Indirect Data Address Word (MIDAW) Facility Extended format Data Sets – einschl. DB2® und VSAM Supported in z/OS® 1.6 und höher * LSPR mixed workload average. z Vs z ** This is a comparison of the z way and the z990 D32 and is based on LSPR mixed workload average. z9-109 Engines z990 z900 Kapaziät

System z Was sind die Top 5 z-Fakten: 40+ Jahre Kompatibilität
Extreme E/A Leistung Extreme Zuverlässigkeit, Verfügbarkeit & Serviceability (RAS) Beste Plattform für “mixed Workloads” Eine sehr gute Plattform für “neue Workloads” einschl. Java und Linux

System z Community Ecosystem Initiative
Ziel = skilled Mainframe Professionals im Markt in 2010… Key Programme für zukünftige Skills: Ambassadors Programme, Matching schools mit Kunden, Neue Kurse, Universitäts Hubs, Student mainframe Contest, zNextGen, Vereinfachtes z/OS Über 800% Wachstum in WW Partizipierung von Schulen durch Akademische Initiative in 2 Jahren (auf über 215 Schulen) Fall contest – 700+ Studenten absolvierten Hands on training und denken der Mainframe ist ‘cool’ Dutzende positive IT Presseartikel über wachsende Mainframe Skills für die nächste Generation Wichtige Programme für heutige Skills: Kunden Skill Web Portal, Kunden Einührungsklassen, zBLC Skills Advisory Council, Interne Skills Programme, zChampions, THINK z Ca 20 neue Anstellungen in IOTs und AG für 2005, gleicher Plan für 2006 Freie “intro to z/OS & the Mainframe” Klasse mit hoher Nachfrage Mainframe blog Erweiterung des Nutzens durch Partner Wachstum des Anwendungsportfolios ist strategisch Linux : 790 total Apps von 282 ISVs, 195 der Appls neu in 2005 Partnership & Zusammenarbeit zur Erreichung strategischer Ziele Partner wie Vanguard & Cisco Zusammenarbeit um MF als Enterprise Hub für Sicherheit zu positionieren Einflussnahme auf ISV zur Adoption der neuen SW pricing Modelle Kunden Councils & User Groups zBLC wichtig für Kunden und die Plattformweiterentwicklung SHARE/Guide wichtig für Kundenbeziehungen Kunden & User Groups Akademien Linux apps – cross industry and banking, insurance., Govt. FM, Retail, healthcare, Telco, Auto and electronics Some notable new ISV Linux apps in 05 .Acucorp V7 .Aduva .Computer Sciences Corp ( CSC) .Group 1 .Informs .Koukia .LRS, Inc. .Levanta .New Atlanta Communications, LLC .OpenPro .Pegasystems .Rocket Software .SSH .Seagull Software LegaSuite .Software AG .TOLIS Group .Wily Technology Examples of SW adoption – recently SAS Open Source IBM Tech Support & Services Collaborate to Innovate Nutzennetz Industrie

Ziel: IBM Informations-Server
Zentrale Kontrolle für Informationsservices Gemeinsame Metadaten, Logging, Sicherheit, Service-Registrierung und Konfiguration Zentral gesteuerte Informationsbestände Zuverlässiger sicherer Informationsservice Beinhaltet komplette Sicht der Information cross über unterschiedliche Landschaften Konsistente Transformation und Datenbereinigung Verbindungen und direkte Beziehung zu Geschäft Flexibilität & reduzierte Kosten Zielorientierte Informationen Unterbrechungsfreie Prozesse auch bei Änderungen der Quellen Mehrere Optionen für den Zugriff auf die Informationen Zeitgewinn Unterstützung der Wiederverwendung des Zugriffs auf verschiedene Informationsebenen Introducing the Information Server

Anhang

z/OS R7 – Antwort auf zukünftige Herausforderungen Gesamtüberblick
Skalierbarkeit 32-wege Support, XES locks, 64-bit Virtual RLS, >64K Track Support, >255 Extents per VSAM component, CICS Sockets Erweiterungen Einfache Nutzung und Skill TCP/IP Konfigurationsänderungen über neue Operator Commands, Automatic Table loading für Unicode Hohe Verfügbarkeit Dynamic Service Activation for z/OS UNIX® System Services, JES2 und Unicode Recovery, Dynamisches Capacity upgrade/downgrade, GDPS Logger Erweiterungen mit XRC+ Integration neue Anwendungen und Support für Industrie und offene Standards C/C++ hex Floating Point Support für AMODE 64, C99 Self-Managing Fähigkeiten Health Checker als neue Basis- funktion, weitere Health checks, OAM immediate recall to disk, Sysplex Distributor z/OS R7 Erweiterungen für Netzverarbeitung FTP, IPv6 Sysplex Support, Load Balancing Advisor, Enterprise Extender, Linux® Appliance Support für NCP, DVIPA Reclamation, Sysplex Distributor Erweiterungen, Support für JES2 NJE über TCP/IP – geplant 1Q06 Hohe Sicherheit IPSec und NAT, Transparent TLS, IP Filtering, Internet Key Exchange und Virtual Private Network Erweiterungen, Mixed-case Passworte This foil identifies those functions being provided in z/OS 1.7 addressing many different areas. Many of these will be described in more detail as we go though the remainder of the foils. z/OS continues to provide functionality in support of addressing the challenges of on demand. Support heterogene Infrastruktur DFSMSrmm™, Virtualization Engine™, Common Information Model, EWLM ARM Agent Integration zOS_PG_130

Zusammenfassung: SOA Referenz Architektur - IBM SOA Foundation
Info Assets Apps & Business Innovation & Optimization Services Development Services Interaction Services Process Services Information Services Partner Services Business App Services Access Services Integrated environment for design and creation of solution assets Manage and secure services, applications & resources Facilitates better decision-making with real-time business information Enables collaboration between people, processes & information Orchestrate and automate business processes Manages diverse data and content in a unified manner Connect with trading partners Build on a robust, scaleable, and secure services environment Facilitates interactions with existing information and application assets ESB Facilitates communication between services IT Service Management Infrastructure Services Optimizes throughput, availability and performance **Main point: The SOA reference architecture is a vendor-neutral way of looking at and planning the set of services that go into building an SOA. The SOA reference architecture is a way of looking at the set of services that go into building an SOA. This architecture is not unique to IBM; these are things that you need to consider when approaching SOA regardless of what products and services are used. These capabilities can be implemented on a build-as-you-go basis allowing capabilities and project level solutions to be easily added as new requirements are addressed over time. You can see that these services organized along the same lifecycle we’ve discussed. On the left in is Development Services which is model and assemble, in the middle are the elements of the deployment run-time environment you use and on the right is management. The backbone of the reference architecture is the enterprise service bus which facilitates communication between services. The reference architecture is a great tool for laying out roadmaps for pursuing SOA. Regardless of what kind of project you’re undertaking, it makes sense to lay it out on a reference architecture to see how the various services you’re designing are going to interact with each other Additional detail: The SOA Reference Architecture outlines the key capabilities that are required for comprehensive, enterprise wide SOA solutions. These capabilities can be implemented on a build-as-you-go basis allowing capabilities and project level solutions to be easily added as new requirements are addressed over time. Tools are an essential component of any comprehensive integration architecture. The SOA Architecture includes both Development Services which are used to implement custom artifacts that leverage the infrastructure capabilities, and Business Innovation & Optimization Services which are used to monitor and manage the runtime implementations at both the IT and business process levels. At the core of the SOA Reference Architecture is the Enterprise Service Bus. This delivers all of the inter-connectivity capabilities required to leverage the services implemented across the entire architecture. Transport services, event services, and mediation services are all provided through the ESB. The SOA Reference Architecture also contains a set of services that are oriented toward the integration of people, processes, and information: Interaction Services provide the capabilities required to deliver IT functions and data to end users, meeting the end-user's specific usage preferences. Process Services provide the control services required to manage the flow and interactions of multiple services in ways that implement business processes. Information Services provide the capabilities required to federate, replicate, and transform data sources that may be implemented in a variety of ways. Many of the services in an SOA are provided through existing applications; others are provided in newly implemented components; and others are provided through external connections to third party systems. Existing enterprise applications and enterprise data are accessible from the ESB through a set of Access Services that provide the bridging capabilities between legacy applications, pre-packaged applications, enterprise data stores and the ESB. The SOA Reference Architecture also contains a set of Partner Services that provide the document, protocol, and partner management capabilities required for business processes that involve inter-actions with outside partners and suppliers. Business Application Services provide runtime services required for new application components to be included in the integrated system. Underlying all these capabilities of the SOA Reference Architecture is a set of Infrastructure Services which are used to optimize throughput, availability and performance. IT Services Management Services include capabilities that relate to scale and performance, for example edge services, clustering services, and virtualization capabilities allow efficient use of computing resources based on load patterns. The SOA Reference Architecture is a complete and comprehensive architecture that covers all the integration needs of an enterprise. Its services are well integrated and are delivered in a modular way, allowing SOA implementations to start at a small project level. As each additional project is addressed, new functions can be easily added, incrementally enhancing the scope of integration across the enterprise. Background: The IBM SOA Foundation delivers the capabilities you need to adopt SOA through a comprehensive architecture. These capabilities can be implemented on a build-as-you-go basis, and yet, because of the architecture and its service orientation, capabilities and project level solutions can be easily added as new requirements are addressed over time. The SOA Reference Architecture shows the key capabilities that are required for comprehensive, enterprise wide SOA solutions. Development Services are an essential component of any comprehensive integration architecture. The SOA Architecture includes development tools, used to implement custom artifacts that leverage the infrastructure capabilities, and business performance management tools, used to monitor and manage the runtime implementations at both the IT and business process levels. Development tools allow people to efficiently complete specific tasks and create specific output based on their skills, their expertise, and their role within the enterprise. Business Analysts who analyze business process requirements need modeling tools that allow business processes to be charted and simulated. Software Architects need tool perspectives that allow them to model data, functional flows, system interactions, etc. Integration Specialists require capabilities that allow them to configure specific inter-connections in the integration solution. Programmers need tools that allow them to develop new business logic with little concern for the underlying platform. Yet, while it is important for each person to have a specific set of tool functions based on their role in the enterprise, the tooling environment must provide a framework that promotes joint development, asset management and deep collaboration among all these people. A common repository and functions common across all the developer perspectives (e.g. version control functions, project management functions, etc) are provided in the SOA Reference Architecture through a unified development platform. The Business Innovation & Optimization Services incorporate monitoring capabilities that aggregate operational and process metrics in order to efficiently manage systems and processes. Managing these systems requires a set of capabilities that span the needs of IT operations professionals and business analysts who manage the business operations of the enterprise. These capabilities are delivered through a set of comprehensive services that collect and present both IT and process-level data, allowing business dashboards, administrative dashboards, and other IT level displays to be used to manage system resources and business processes. Through these displays and services, it is possible for LOB and IT personnel to collaborate to determine, for example, what business process paths may not be performing at maximum efficiency, the impact of system problems on specific processes, or the relationship of system performance to business process performance. This collaboration allows IT personnel and assets to be tied more directly to the business success of the enterprise than they traditionally have been. One key feature of the SOA Reference Architecture is the linkage between the Development and the Business Innovation & Optimization Services. The ability to deliver runtime data and statistics into the development environment allows analyses to be completed that drive iterative process re-engineering through a continuous business process improvement cycle. At the core of the SOA Reference Architecture is the Enterprise Service Bus. This architectural construct delivers all the inter-connectivity capabilities required to leverage and use services implemented across the entire architecture. Transport services, event services, and mediation services are all provided through the ESB. Transport services provide the fundamental connection layer; event services allow the system to respond to specific stimuli that are part of a business process; and mediation services allow loose-coupling between interacting services in the system. The ESB is a key factor in enabling the service orientation of the SOA Reference Architecture to be leveraged in implementing service oriented solutions and can be implemented today to meet the quality of service requirements of any integration solution. The SOA Reference Architecture also contains a set of services that are oriented toward the integration of people, processes, and information. These services control the flow of interactions and data among people and automated application services in ways appropriate to the realization of a business process: - Interaction Services provide the capabilities required to deliver IT functions and data to end users, meeting the end-user's specific usage preferences. - Process Services provide the control services required to manage the flow and interactions of multiple services in ways that implement business processes. - Information Services provide the capabilities required to federate, replicate, and transform data sources that may be implemented in a variety of ways. Automated application services, implementations of business logic in automated systems, are a critical part of any integration architecture or solution. Many of these services are provided through existing applications; others are provided in newly implemented components; and others are provided through external connections to third party systems. Existing enterprise applications and enterprise data are accessible from the ESB through a set of access services. These Access Services provide the bridging capabilities between legacy applications, pre-packaged applications, enterprise data stores (including relational, hierarchical and nontraditional, unstructured sources such as XML and Text), etc and the ESB. Using a consistent approach, these access services expose the data and functions of the existing enterprise applications, allowing them to be fully re-used and incorporated into functional flows that represent business processes. Existing enterprise applications and data leverage the Business Application and Data Services of their operating environments such as CICS, IMS, DB2, etc. As these applications and data implementations evolve to become more flexible participants in business processes, enhanced capabilities of their underlying operating environments, for example support of emerging standards, can be fully utilized. The SOA Reference Architecture also contains a set of Business Application Services that provide runtime services required for new application components to be included in the integrated system. These application components provide new business logic required to adapt existing business processes to meet changing competitive and customer demands of the enterprise. Design and implementation of new business logic components for integration enables them to be fully re-useable, allowing them to participate in new and updated business processes over time. The Business Application Services include functions important to the traditional programmer for building maintainable, flexible, and re-useable business logic components. In many enterprise scenarios, business processes involve inter-actions with outside partners and suppliers. Integrating the systems of the partners and suppliers with those of the enterprise improves efficiency of the overall value chain. Partner Services provide the document, protocol, and partner management services required for efficient implementation of business-to-business processes and inter-actions. Underlying all these capabilities of the SOA Reference Architecture is a set of Infrastructure Services which provide security, directory, IT system management, and virtualization functions. The security and directory services include functions involving authentication and authorizations required for implementing, for example, single sign-on capabilities across a distributed and heterogeneous system. IT Services Management Services include functions that relate to scale and performance, for example edge services and clustering services, and the virtualization capabilities allow efficient use of computing resources based on load patterns, etc. The ability to leverage grids and grid computing are also included in infrastructural services. While many of the Infrastructure and IT Service Management services perform functions tied directly to hardware or system implementations, others provide functions that interact directly with integration services provided in other elements of the architecture through the ESB. These interactions typically involve services related to security, directory, and I/T operational systems management. The SOA Reference Architecture is a complete and comprehensive architecture that covers all the integration needs of an enterprise. Its services are well integrated and are delivered in a modular way, allowing SOA implementations to start at a small project level. As each additional project is addressed, new functions can be easily added, incrementally enhancing the scope of integration across the enterprise. In addition to supporting SOA strategies and solutions, the architecture itself is designed using principles of service orientation and function isolation.

Schlüsselprodukte – Modellierung und Assemble
Rational Application Developer Rational Software Architect WebSphere Integration Business Modeler Schlüsselprodukte – Modellierung und Assemble Apps & Info Assets Business Innovation & Optimization Services Development Services Interaction Services Process Services Information Services Partner Services Business App Services Access Services ESB IT Service Management Infrastructure Services A service-oriented architecture (SOA) is an approach for building distributed systems that enables flexible connectivity of applications/resources Represents every application or resource as a service with a standard interface Enables applications and resources to exchange structured information Delivers flexibility by treating business processes and infrastructure as defined components that can be mixed and matched Lets you start small (e.g., wrapper an IBM CICS® transaction) and add additional services as business needs dictate Lets you start today with existing technology Modular product portfolio built on open standards Functionally rich adopted incrementally Simple to develop, deploy and manage Integrated role based tools for development & administration …using a common install, administration, security and programming model What it the ESB? Connects and integrates an organization’s IT infrastructure across many locations, using different transport services securely, reliably, at very high volumes in a manageable manner. What it IS NOT: A new software product. However, it is currently implemented using existing IBM products (WMQ, WBIMB) IBM has provided an ESB architectural construct for a long time The emergence of this as a new and more widely accepted architectural concept is a result of the rising maturity and adoption of newer standards-based integration technologies that further support SOA. IBM strategy is to continue its leadership and commitment to an open standards service oriented approach to integration and universal connectivity.

Schlüsselprodukte – Betrieb
WebSphere Process Server WebSphere Portal Server WebSphere Product Center & WebSphere Information Integrator WebSphere Application Server WebSphere Partner Gateway WebSphere Adapters WebSphere XD WebSphere ESB & WebSphere Message Broker Schlüsselprodukte – Betrieb Apps & Info Assets Business Innovation & Optimization Services Development Services Interaction Services Process Services Information Services Partner Services Business App Services Access Services ESB IT Service Management Infrastructure Services Slide Objectives: To map IBM offerings to SOA Operating Environment. Details Walk through the animation and talk briefly about each offerings.

Kosten für Kauf verteilt über 4 Jahre
Reine TCA Betrachtung Kosten für Kauf verteilt über 4 Jahre

Plus Personal & Servicekosten
Verteilte Systeme haben höhere Service, Monitoring und Supportkosten – und kosten mehr bei Entwicklung und Implementierung Gesamtkosten über 4 Jahre

TCO Ergebnis-Chart (Beispiel)
Col’s 1-3: Year 1 Col’s 4-6 : Year 2 -4

Alle Kostenfaktoren – viele davon werden oft ignoriert
Sicherheit Authentication / Authorization User Administration Datensicherheit Server und OS Sicherheit RACF vs. andere Lösungen Bereitstellung und Support System Programmierung Aufwand konsistente OS u.SW Level Databank Aufwand Middleware SW Maintenance SW Verteilung (across firewall) Anwendung Technologie Ugrade System Releasewechsel ohne Unterbrechung Betriebskonzept Entwicklung Betriebsprozeduren Anwendbarkeit der entwicklelten Prozeduren Automation Ressource Nutzung und Performance Mixed Workload / Batch Ressource Sharing shared nothing vs. shared everything Parallel Sysplex vs. andere Konzepte Antwortzeiten Performance Management Spitzenhandling / Skalierbarkeit Integration Integrierte Funktionalität vs. implemeniterter Funktionalität (möglich mit 3rd party Tools) Balanced System Integration von / in Standards Weitere Verfügbarkeits Aspekte Geplante Ausfälle Ungeplante Ausfälle Automatisches Take Over Unter brechungsfreiees Take Over (speziell für DB) Workload Management cross physischer Grenzen Business kontinuität Verfügbarkeitsaspekte für andere Anwendungen / Projekte End User Service End User Productivität Virtualisierung Skill und Resourcen Personalausbildung Verfügbarkeit der Ressourcen Verfügbarkeit Hochverfügbarkeit Betriebsstunden Backup / Restore / Site Recovery Backup Disaster Szenario Restore Aufwand für komplette Site Recovery SAN Aufwand Infrastrukturkosten Raum Strom Netz-Infrastrukutr Speicher-Infrastruktur Zusätzlicher Aufwand für Entwicklung und Implementierung Investition in eine Plattform – Reproduction für andere Kontrolle und Abrechnung (Accounting) Analyse der Systeme Kosten Betriebsaufwand Monitoring, Operating Problem Determination Server Management Tools Integrated Server Management – Enterprise Wide

Das ‘New Face’ von z/OS Vereinfachung und Modernisierung des Mainframes für neue Generation von IT Professionals Nachwuchs mit neuem Talent: IBM Akademische Initiative erreicht Colleges und Univesitäten Kunden behalten die ‘in-house’ Mannschaft Besuchen Sie IBM Academic Initiative zSeries Web site (Siehe Link der z/OS Home Page … ibm.com/zseries/zos) Reduzierung der z/OS Komplexität; ermöglicht einfacher den Aufbau von Experten: Eliminierung, Automatisierung und vereinfachung der komplexen Augaben Modernisierung des “face” von z/OS Beibehaltung des best. “faces” für erfahrene Benutzer Entwicklung der Cross-Plattform Management Lösung der IBM

z/OS Management Portal -neues Gesicht für z/OS
Integrierte Information Interaktiver Advisor: z.B.: Installation Integration mit anderen zSeries Management Tools Breiter Scope von Management Tsks * All statements regarding IBM future direction and intent are subject to change or withdrawal without notice, and represents goals and objectives only.

z/OS Absichserklärungen (SOD)
IBM beabsichtigt: Bereitstellung einer Verschlüsselungsfunktion für z/OS zum Schutz von Daten, die gemeinsam mit Partner, Herstellern und Kunden verwendet werden Design für Weiterentwicklung des z/OS Key Management und der Hochleistungsverschlüsselung. Targeted for availability in 2005 Neues Benutzerinterface für z/OS Management geplant für neue Generation von IT Professionals Geplant für 4Q 2005 Support von mehr als 32 Prozessoren in einer logsichen Partition auf der z9-109 in der Zukunft Ankündigung einer neuen Version des New Application License Charges (NALC) mit der Absicht mit der Absicht das Preis/Leistungsverhältnis von z/OS in bestimmten New Workload Umgebungen zu verbessern, indem ein neues Subcapacity Gebührenmodell bereitgestellt wird. Ziel ist Bereitstellung in 2H2006. Einführung einer neuen Systemkomonente genannt z/OS XML System Services (z/OS XML). Diese Komponente ist designt um besondere Services für das Parsing von XML Dokumenten bereitzustellen. Geplant für zuk. Release von z/OS Verschlüsselungs- funktion Vereinfachtes z/OS Management Hohe z/OS Skalierbarkeit Verbesserte Preis/Leistung Optimierung neuer Workloads zOSSUM_280

Jürgen Ley Brandmanagement IBM Stuttgart

Ähnliche Präsentationen

Präsentation zum Thema: "Jürgen Ley Brandmanagement IBM Stuttgart"— Präsentation transkript:

Ähnliche Präsentationen

Über Projekt

Feedback

Anmelden

Anmeldung über soziales Netzwerk:

Jürgen Ley Brandmanagement IBM Stuttgart

Ähnliche Präsentationen

Präsentation zum Thema: "Jürgen Ley Brandmanagement IBM Stuttgart"— Präsentation transkript:

Ähnliche Präsentationen

Über Projekt

Feedback