A z/OS System Programmer’s Guide to Migrating to a New IBM System z9 EC or z9 BC Server

A z/OS System Programmer’s Guide to Migrating to a New IBM System z9 EC or z9 BC Server

February, 2007 © 2007 IBM Corporation Page 1 of 82

© 2007 IBM Corporation IBM Systems


Greg [email protected] - z/OS Installation and Deployment ArchitectIBM Systems

2 February 2007© 2007 IBM Corporation IBM Systems

TrademarksThe following are trademarks of the International Business Machines Corporation in the United States and/or other countries.

The following are trademarks or registered trademarks of other companies.

* Registered trademarks of IBM Corporation

* All other products may be trademarks or registered trademarks of their respective companies.

Java and all Java-related trademarks and logos are trademarks of Sun Microsystems, Inc., in the United States and other countriesLinux is a registered trademark of Linus Torvalds in the United States, other countries, or both.UNIX is a registered trademark of The Open Group in the United States and other countries.Microsoft, Windows and Windows NT are registered trademarks of Microsoft Corporation.

Notes: Performance is in Internal Throughput Rate (ITR) ratio based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput that any user will experience will vary depending upon considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve throughput improvements equivalent to the performance ratios stated here. IBM hardware products are manufactured from new parts, or new and serviceable used parts. Regardless, our warranty terms apply.All customer examples cited or described in this presentation are presented as illustrations of the manner in which some customers have used IBM products and the results they may have achieved. Actual environmental costs and performance characteristics will vary depending on individual customer configurations and conditions.This publication was produced in the United States. IBM may not offer the products, services or features discussed in this document in other countries, and the information may be subject to change without notice. Consult your local IBM business contact for information on the product or services available in your area.All statements regarding IBM's future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only.Information about non-IBM products is obtained from the manufacturers of those products or their published announcements. IBM has not tested those products and cannot confirm the performance, compatibility, or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.Prices subject to change without notice. Contact your IBM representative or Business Partner for the most current pricing in your geography.

AnyNet*APPN*CICS*DB2*DFSMSdfpDFSMSdssDFSMShsmDFSMSrmmDFSORTe-business logo*Enterprise Storage Server*ESCON*FICON*GDPS*

Geographically Dispersed Parallel SysplexHiperSocketsHyperSwapIBM*IBM eServerIBM e(logo)server* IBM logo*IMSLanguage Environment*MQSeries*Multiprise*MVSNetView*OMEGAMON*

On Demand Business logoOS/390*Parallel Sysplex*PR/SMProcessor Resource/Systems ManagerRACF*RedbookResource LinkRMFS/360S/370S/390*Sysplex Timer*SystemPac*

System z9Tivoli*TotalStorage*Virtualization EngineVM/ESA*VSE/ESAVTAM*WebSphere*xSeries*z/Architecturez/OS*z/VM*z/VSEzSeries*




Agenda

IBM System z9 Overview z9 EC and z9 BC Support by z/OS ReleasesMigration Considerations► “Inherited” Considerations► Multisystem/Sysplex Considerations► Other Migration Considerations

Migration Paths► General Recommendations and Considerations► Recommended Paths for Supported z/OS Releases

SummaryBackup► Cryptographic Support► OSA-Express2

A z/OS System Programmer's Guide to Migrating to a New IBM System z9 EC or z9 BC Server The latest generation of IBM System z servers, the IBM System z9 Enterprise Class (z9 EC, formerly the IBM System z9 109 (z9-109)) and the IBM System z9 Business Class (z9 BC), are designed to provide an advanced combination of reliability, availability, security, scalability, and virtualization features. The good news is all supported z/OS releases can run on a z9 EC or z9 BC server (all supported z/OS.e releases can run on a z9 BC server). Similarly, all supported z/OS and z/OS.e releases can participate in a sysplex that has a CF or operating system image on a z9 server. The even better news is that most customers are well positioned to use the new server. Come hear about how to upgrade to a IBM System z9 server! This informative session will describe the software required to run on a new server (including cryptographic software), compatibility code required on other systems that share resources with systems running on the new server, and migration actions associated with the new software. This session will be of interest to systems programmers and their managers who will upgrade to a z9 server.




IBM System z9

Overview




IBM eServer zSeries 890 z890 (2086)IBM eServer zSeries 990

z990 (2084)

Announced 5/03 – first zSeries Superscalar Server with up to 48 PUs4 models – Up to 32-waySpecialty Engines

► CP, IFL, ICF, zAAPOn Demand Capabilities

► CUoD, CIU, CBU, On/Off CoDMemory – up to 256 GBChannels

► Four LCSSs ► Up to 1024 ESCON® channels► Up to 240 FICON Express2 channels► Token-Ring, GbE, 1000BASE-T

Ethernet► Coupling Links

Crypto Express2Parallel Sysplex clusteringHiperSockets™ – up to 16Up to 30 logical partitionsOperating Systems

► z/OS, z/VM®, VSE/ESA™, z/VSE™, TPF, z/TPF, Linux® on zSeries

Announced 4/04 – zSeries Superscalar Server with 5 PUs1 model – Up to 4-way

► 28 capacity settingsSpecialty Engines

► CP, IFL, ICF, zAAPOn Demand Capabilities

► CUoD, CIU, CBU, On/Off CoDMemory – up to 32 GBChannel

► Two LCSSs► Up to 420 ESCON channels► Up to 80 FICON Express2 channels► Networking Adapters (OSA)► Coupling Links

Crypto Express2Parallel Sysplex clusteringHiperSockets – up to 16Up to 30 logical partitionsOperating Systems

► z/OS, z/OS.e, z/VM, VSE/ESA, z/VSE, TPF, z/TPF, Linux on zSeries

IBM System z9 (z9 EC) (2094)

Announced 7/05 - Superscalar Server with up to 64 PUs5 models – Up to 54-wayGranular Offerings for up to 8 CPsSpecialty Engines

►CP, IFL, ICF, zAAP, zIIPOn Demand Capabilities


► Four LCSSs► Multiple Subchannel Sets► MIDAW facility► 63.75 subchannels► Up to 1024 ESCON channels► Up to 336 FICON channels► Enhanced FICON Express2 and 4► 10 GbE, GbE, 1000BASE-T► Coupling Links

Configurable Crypto Express2Parallel Sysplex clusteringHiperSockets – up to 16Up to 60 logical partitionsEnhanced AvailabilityOperating Systems

► z/OS, z/VM, VSE/ESA, z/VSE, TPF, z/TPF, Linux on System z9

IBM System z9 (z9 BC) (2096)

Announced 4/06 - Superscalar Server with 8 PUs 2 models – Up to 4-wayHigh levels of Granularity available

► 73 Capacity IndicatorsSpecialty Engines

► CP, IFL, ICF, zAAP, zIIPOn Demand Capabilities


► Two LCSSs► Multiple Subchannel Sets► MIDAW facility► 63.75 subchannels► Up to 420 ESCON channels► Up to 112 FICON channels► Enhanced FICON Express2 4 Gbps► 10 GbE, GbE, 1000BASE-T► Coupling Links

Configurable Crypto Express2Parallel Sysplex clusteringHiperSockets – up to 16Up to 30 logical partitionsEnhanced AvailabilityOperating Systems

► z/OS, z/OS.ez/VM, VSE/ESA, z/VSE, TPF, z/TPF, Linux on System z9

IBM System z family

IBM System z Family IBM eServer zSeries 990 – The IBM eServer zSeries 990 (z990) supports enterprise on demand business. Its innovative design allows it to scale up physically (up to three times the capacity of the z900 Model 216) and virtually—helping you to simplify your infrastructure and integrate multiple workloads.

The System z Application Assist Processor (zAAP), an optional feature, provides a specialized and highly integrated z/OS Java execution environment. On/Off Capacity on Demand is designed to provide greater flexibility in managing the constantly changing workload demands of today's environment.

There are 4 models, 1 to 32 processors, zAAP, Integrated Facility for Linux (IFL), Internal Coupling Facility (ICF), and optional SAP specialty engines are available. Cryptographic accelerators and coprocessors are supported, providing DES, SHA-1, SSL, and TKE security. FICON, ESCON, FCP, 1 & 10 Gb, 1000BASE-T & Fast Ethernet, Token Ring, and Hipersockets are supported.

IBM eServer zSeries 890 – The IBM eServer zSeries 890 (z890) includes zSeries functionality at a lower entry capacity level than previously available on IBM z/Architecture hardware, as well as new granular growth options.

There is 1 model, 1 to 4 processors, with 28 capacity settings. zAAP, IFL, ICF and optional SAP specialty engines are available. Cryptographic accelerators and coprocessors are supported, providing DES, SHA-1, SSL, and TKE security. FICON, ESCON, FCP, 1 & 10 Gb, 1000BASE-T & Fast Ethernet, Token Ring, and Hipersockets are supported.

IBM System z9 Enterprise Class (formerly z9-109) - The System z9 EC provides a strong combination of past mainframe characteristics, plus new functions designed around scalability - including flexible granularity solutions, virtualization, availability, such as the new Server Time Protocol (STP) feature, and security. And the z9 EC continues to extend and support the use of dedicated processors for specialized workloads, including the zAAP, IFL, ICF and System z9 Integrated Information Processor (zIIP).



There are 5 models, 1 to 54 processors, zAAP, IFL, ICF and zIIP specialty engines are available. Configurable Crypto Express2 (secure coprocessor and for SSL acceleration) are supported, providing DES, AES, SHA-256, PRNG, and TKE Smant Card Reader Support. ESCON, FICON Express 4, OSA Express2 and Hipersockets are supported.

IBM System z9 Business Class - The IBM System z9 Business Class (z9 BC) is the latest member of the System z9 family. The z9 BC provides an advanced combination of reliability, availability - including the new Server Time Protocol (STP) feature, security, scalability, and virtualization. The z9 BC is designed specifically as a midrange mainframe and delivers extensive growth options and excellent price / performance for those customers requiring a lower-capacity entry point and more granular growth options than offered with the System z9 Enterprise Class.

There are 2 models, 1 to 7 processors, zAAP, IFL, ICF, and zIIP specialty engines are available. Configurable Crypto Express2 (secure coprocessor and for SSL acceleration) are supported, providing DES, AES, SHA-256, PRNG, and TKE Smant Card Reader Support. ESCON, FICON Express 4, FCP, 1 & 10Gb 1000BASE-T & Fast Ethernet and Hipersockets are supported.

IBM eServer zSeries 900 - Specifically designed for the massive transactional and data demands of on demand business, the self-managing capabilities and balanced system design of the IBM eServer zSeries 900 (z900) enables optimal use of system resources in dynamic environments.

IBM eServer zSeries 800 - Optimized for integration and designed to handle the transaction processing demands of on demand business, the IBM eServer zSeries 800 (z800) incorporates advanced self-management capabilities and, with a dedicated Linux server, provides outstanding flexibility for deploying Linux solutions.

The attractive price/performance of z800 servers extends the advantages of zSeries technology to customers whose capacity requirements are less than those served by the z900.




Five hardware models

Faster Uni Processor

Up to 54 customer PUs

Up to 512 GB memory

Up to 60 LPARs

CBU for IFL, ICF, and zAAP

Enhanced Driver maintenance

Enhanced Book availability

Dynamic oscillator switchover

MIDAW facility

63.75K Subchannels for Set-0

Increased Number of FICON Express2 Features

Multiple Subchannel Sets per LCSS

IPv6 Support for HiperSockets

N_Port ID Virtualization

Server Time Protocol (STP)available 1/31/2007

Separate PU pool management

OSA-Express2 1000BASE-T

54 additional hardware Instructions

Redundant I/O interconnect

Up to 16 2.7 GB STIs per book

z9 EC GA Functions and Features

FICON and OSA Enhancements

Wild Branch PD Assist

Hot pluggable/ maintainableMBA/STI fanout cards

Configurable Crypto Express2

Enhanced CPACF with AES, PRNG and SHA-256

OSA-Express2 OSN (OSA for NCP)

Note: Please refer to the latest PSP bucket for latest PTFs for new functions/features

z9 EC Overview For over four decades, the IBM mainframe has been a leader in data and transaction serving. The IBM System z9 109 (z9-109) (announced July 2005), provided a strong combination of mainframe characteristics, plus new functions designed around scalability, availability, security, and virtualization. With the announcement in May of 2006, the z9-109 became known as the IBM System z9 Enterprise Class (z9 EC).

With a modular book design, the z9 EC Model S54 is designed to provide up to 95% more total system capacity than the z990 Model D32, and has up to double the available memory. The Modified Indirect Data Address Word (MIDAW) facility is designed to improve FICON performance. The number of FICON Express2 open exchanges (concurrent I/O operations) that may be active simultaneously has been increased from 32 to 64 per channel.

The z9 is focused on providing higher availability and reducing planned and unplanned outages -- which, when properly configured, may be accomplished with improved nondisruptive replace, repair, and upgrade functions for memory, books, and I/O as well as extending nondisruptive capability to download Licensed Internal Code updates.

Integrated clear key encryption security-rich features on the z9 include support for Advanced Encryption Standard, Secure Hash Algorithm-256, and integrated Pseudo Random Number Generation. Performing these functions in hardware is designed to contribute to improved performance.

Innovations on the z9 can help to ensure you have a security-rich platform, can help maximize your resources and their utilization, and can help provide you the ability to integrate applications and data across the infrastructure. The z9 is designed to be a flagship component of your heterogeneous environment.

The z9 continues the evolution of the mainframe, building upon the structure introduced on z990 in support of z/Architecture, reliability, availability, scalability, and clustering. The z9 expands upon a key attribute of the platform - availability - to help ensure you have a resilient infrastructure designed to satisfy the requirements



of On Demand Business. With the increased performance and total system capacity possible for the z9, you have an opportunity to continue to consolidate diverse applications on a single platform.

The z9 EC is designed to provide: • Five New Hardware Models - offering 1 to 54 configurable PUs. The first four models (S08, S18, S28

and S38) have 12 PUs per book. The enhanced capacity Model S54, our largest mainframe server, offers 16 PUs in each of its four books.

• Faster Uni processor - a 35% increase in capacity performance over the z990 Model 2084-301, and the overall server capacity will be 95% more on the S54 than the z990 Model 2084-332.

• Up to 54 CPs - The Model S54 is an enhanced capacity model. You can customize the machine to be a 1 to 54-way. On the standard models, the first book has 10 configurable PUs, with 12 PUs each in books 2, 3 and 4. The S54 has 12 configurable PUs in the first per book, and 14 configurable ones in each remaining book. Like the S38, the S54 can be ordered with a minimum of 16 GB of memory up to a maximum of 512 GB.

• Up to 512 GB Memory - Memory has been doubled from what was offered on the z990 processor - for a server maximum capacity up to 512 GB with a maximum of 128 GB per book.

• CBU for IFL, ICF and zAAP - The z9 will be able to activate most PU types as part of CBU upgrades: IFLs, zAAPs, ICFs and CPs (zIIPs added with GA2). This is in contrast to the z890 and z990 servers that were, and continue to be, only able to activate CPs as CBU upgrades.

• Separate PU Pool Management - New on the z9, all zAAP, zIIP, ICF and IFL processors will be managed as individual separate and distinct processor types/pools by PR/SM. On the z990 all the specialty engines were contained in just one ‘specialty pool’.

• Redundant I/O Interconnect - Redundant I/O interconnect will help maintain critical connections to devices during enhanced book availability as it provides connectivity to the server I/O resources using a second path from a different book.

• Enhanced Driver Maintenance - One of the greatest contributors to downtime during planned outages is Licensed Internal Code (LIC) updates performed in support of new features and functions. When properly configured, the z9 is designed to support activating select new LIC level concurrently. Concurrent activation is only supported at specific sync points.

• Enhanced Book Availability - The z9 is designed to allow a single book, in a multibook server, to be concurrently removed from the server and reinstalled during an upgrade or repair action.

• Dynamic Oscillator Switchover - The z9 has two oscillator cards, a primary and a backup. In the event of a failure of the primary oscillator card, the backup is designed to detect the failure, switch over, and provide the clock signal to the server transparently. Previously, in the event of a failure of the active oscillator, a server outage would occur, the subsequent Power On Reset would select the backup, and the server would resume operation. Dynamic oscillator switchover is exclusive to the z9.

• Server Time Protocol – (available since January 31, 2007) Is a new time synchronization feature, Server Time Protocol (STP), which is designed to provide the capability for multiple System z9 and zSeries servers to maintain time synchronization with each other. STP is planned to be the follow-on to the Sysplex Timer (9037-002). The Sysplex Timer and STP are designed to allow events occurring in different System z9, zSeries, and S/390 servers to be properly sequenced in time. Note: IBM intends to withdraw the Sysplex Timer Model 2 (9037-002) from marketing in 2006. For more information, refer to Hardware Announcement 105-241, dated July 26, 2005, (IBM System z9 109). STP is designed to: • Allow clock synchronization for z9 EC, z9 BC, z990, and z890 servers and CFs without requiring the

Sysplex Timer • Support a multisite timing network of up to 100 km (62 miles) over fiber optic cabling, thus allowing a

Parallel Sysplex to span these distances



• Potentially reduce the Cross-Site connectivity required for a multisite Parallel Sysplex • Coexist with an ETR network • Allow use of dial-out time services to set the time to an international time standard (such as

Coordinated Universal Time (UTC)) and adjust to UTC on a periodic basis • Allow setting of local time parameters, such as time zone and daylight savings time • Allow automatic updates of daylight savings time STP is available as a feature on z9, z990, and z890, and be supported by z/OS (and z/OS.e) V1.7 (PTFs are required to enable STP support).

• Faster 2.7GB STI and more of them - The z9 has 4 more STI (self timed interconnect) connections per book as well as a faster bandwidth. (12 STIs x 2.0 Gigabytes per STI x 4 books = 96 versus 16 STIs x 2.7 GB per STI x 4 books = 172.8 ... 172.8/96 = 80%)

• MIDAW Facility - The Modified Indirect Data Address Word (MIDAW) facility is a new and separate facility, offering an alternative for a channel program to be constructed. The new design can help to improve performance for native FICON applications that use extended format datasets (including DB2 and VSAM) by helping to improve channel utilization, reduce channel overhead, and improve I/O response times. The MIDAW facility is supported on z/OS 1.6 and above.

• Multiple Subchannel Sets (MSS) per LCSS – MSS provides a second set of subchannels for defining Parallel Access Volume (PAV) aliases. This new function can help provide relief from the 64K device limit by allowing PAV aliases to be defined without making device numbe3rs unavailable for defining additional devices. For some of our largest customers this is designed to provide an I/O constraint benefit.

• 63.75K Subchannels for Set-0 - addresses a maximum of 64K-1 subchannels in subchannel set 0 (zero). Previously 1024 (1K) of these subchannels were reserved for system use. IBM is making 768 of these subchannels available for customer use. This change increases the storage attachment capability of the System z9 - for example the IBM TotalStorage DS8000 Series can be defined to attach 63.75K unit addresses - so with 63.75K in the host there is symmetry between the server and the storage subsystem.

• Up to 336 FICON Express2 Channels - Providing the capability to populate the 28 I/O slots in one I/O cage allows the z9 to have a maximum of 336 FICON channels installed.

• N_Port Virtualization N_Port ID Virtualization (NPIV) allows a single Fibre Channel Protocol (FCP) port on Linux on System z9 to appear as multiple, distinct ports providing separate port identification and security zoning within the fabric for each operating system image as if each operating system image had its own unique physical port. NPIV is similar to the Multiple Image Facility (MIF) available on ESCON and FICON channels.

• IPv6 Support for HiperSockets - HiperSockets now supports Internet Protocol Version 6 (IPv6) designed by the Internet Engineering Task Force (IETF) to replace Internet Protocol Version 4 (IPv4) to help satisfy the demand for additional IP addresses. IPv6 provides more unique IP addresses by expanding the IP address space from 32 bits to 128 bits. IPv6 requires z/OS 1.6 and z/VM 5.2.

• OSA-Express2 1000BASE-T - With the additional memory available on OSA-Express2, the 1000BASE-T Ethernet feature will be able to: Support large send (offloading TCP segmentation processing from host TCP/IP stack to OSA-Express2), 640 TCP/IP stacks for improved virtualization by hosting of more images on System z9 and potentially reducing the number of required OSA features, and support of concurrent LIC update to minimize network traffic disruption.

• OSA-Express2 OSN (OSA for NCP) - The OSA-Express2 OSN (OSA for NCP) is designed to provide support for the IBM Communication Controller for Linux (CCL) on System z V1.2.1. OSA for NCP will help to eliminate dependencies on hardware such as the 3745/6. It helps to collapse SNA within the server while exploiting and leveraging IP.



• Enhanced CPACF with AES, PRNG and SHA-256 – CP Assist or Cryptographic Functions (CPACF) has been enhanced to include support of the Advanced Encryption Standard (AES) for 128-bit keys, Secure Hash Algorithm-256 (SHA-256), and Pseudo Random Number Generation (PRNG). PRNG is a standard function supported on the Crypto Express2 feature. CPACF, supporting clear key encryption, is standard on every CP and IFL; however a no charge enablement feature #3863 is required.

• Configurable Crypto Express2 – The Crypto Express2 feature has two PCI-X adapters, and each can be defined as either a coprocessor or as an accelerator. The Crypto Express2 feature with both PCI-X adapters defined as accelerators is designed to perform up to 6000 SSL handshakes per second. That is a 3X performance improvement compared to the z990 when using either a PCI Cryptographic Accelerator (PCICA) feature, with two PCI accelerators per feature, or the current Crypto Express2 feature, with two PCI coprocessors per feature.




z9 EC – New functions/features enhancementsMicrocode level 63J plus MCLs

New Specialty Engine – IBM zIIP

OSA Layer 2/3 Enhancements

New FICON Express4

Improved FICON Error Recovery

Crypto Enhancements

CBU for zIIP

24 New subcapacity settings

CBU Enhancements

On/Off CoDEnhancements

PU Conversions for zAAPs and zIIPs

Availability in EU after implementation

of RoHS


z9 EC (GA2) Enhancements The new microcode level for the z9 EC provides the introduction of new capacity settings with subcapacity central processors, the hardware availability of the new IBM System z9 Integrated Information Processor (IBM zIIP), and continues to help improve FICON performance and throughput.

With the demands customers face from mergers and acquisitions, consolidation of servers, on demand processing and support for legacy systems, the z9 EC’s solid foundation makes it an ideal server to help meet changing business priorities. Realizing the requirement for more granular capacity settings within the z9 EC, now offers you central processors with a larger variety of capacity choices that can help meet your business requirements. These processors will continue to have the ability to support all z9 EC features and functions.

The mainframe has evolved our use of specialty engines over time starting with the Internal Coupling Facility (ICF). The latest specialty engine, announced in January of 2006, is the zIIP. The IBM zIIP is the latest customer-inspired specialty engine for the IBM System z9 family. The zIIP, when combined with an enabling Web deliverable for z/OS V1.6 and V1.7 and enabling PTFs for DB2 UDB for z/OS V8, is designed to help improve resource utilization and lower the cost of eligible workloads, enhancing the role of the z9 EC as the data hub of the enterprise.

The z9 EC now includes FICON Express4 for potential improved I/O capacity and performance with the next generation of FICON/FCP. This new feature may offer increased channel aggregation and shorter backup windows to help reduce the cost of storage operations and infrastructure. IBM has a broad range of disk, tape, and SAN products that are ready to support FICON Express4. With these enhanced capabilities, the z9 EC is intended to help increase the flexibility to configure a server to meet current needs, provide a powerful and advanced data serving environment, and help drive down risks and business costs. The z9 EC is designed to optimize your resources without sacrificing features or functions, both within the server and within the enterprise.



Additionally, the z9 EC includes support for Remote Key Loading for ATMs and point of sale devices, and implementation of ISO 16609 CBC Mode TDES MAC.

Remote Key Loading refers to the process of loading Data Encryption Standard (DES) keys to Automated Teller Machines (ATMs) and Point of Sale (POS) devices from a central administrative site without the need for personnel to visit each machine to manually load DES keys. These enhancements provide two important new features: the ability to load initial keys to an ATM or a POS device from a remote location, and enhanced capabilities for exchanging keys with non-CCA cryptographic systems.

Remote Loading of Initial ATM Keys: Typically, a new ATM has none of the financial institutions keys installed. Remote Key Loading refers to the process of loading Data Encryption Standard (DES) keys to Automated Teller Machines (ATMs) from a central administrative site without the need for personnel to visit each machine to manually load DES keys. This has been done by manually loading each of the two clear text key parts individually and separately into ATMs. Manual entry of keys is one of the most error-prone and labor-intensive activities that occur during an installation, making it expensive for the banks and financial institutions.

Remote Key Loading Benefits: • Provides a mechanism to load initial ATM keys without the need to send technical staff to ATMs.

• Reduces downtime due to key entry errors. • Reduces service call and key management costs. • Improves the ability to manage ATM conversions and upgrades.

Integrated Cryptographic Service Facility (ICSF), together with Crypto Express2, support the basic mechanisms in Remote Key Loading. The implementation offers a secure bridge between the highly secure Common Cryptographic Architecture (CCA) environment and the various formats and encryption schemes offered by the ATM vendors. The following are new ICSF services are offered for Remote Key loading:

• Trusted Block Create (CSNDTBC) - This callable service is used to create a trusted block containing a public key and some processing rules. The rules define the ways and formats in which keys are generated and exported.

• Remote Key Export (CSNDRKX) - This callable service uses the trusted block to generate or export DES keys for local use and for distribution to an ATM or other remote device.

Refer to Application Programmers Guide, SA22-7522, for additional details.

Improved Key Exchange With Non-CCA Cryptographic Systems: IBM Common Cryptographic Architecture (CCA) employs Control Vectors to control usage of cryptographic keys. Non-CCA systems use other mechanisms, or may use keys that have no associated control information. This enhancement provides the ability to exchange keys between CCA systems, and systems that do not use Control Vectors. Additionally, it allows the CCA system owner to define permitted types of key import and export which can help to prevent uncontrolled key exchange that can open the system to an increased threat of attack.

ISO 16609 CBC Mode T-DES Enhancement: ISO 16609 CBC Mode T-DES MAC supports the requirements for Message Authentication, using symmetric techniques. ICSF will use the following callable services to access the ISO 16609 CBC Mode T-DES MAC enhancement in the Cryptographic coprocessor:

• MAC Generate (CSNBMGN) • MAC Verify (CSNVMVR) • Digital Signature Verify (CSNDDSV)

ISO 16609 CBC mode T-DES MAC is accessible through ICSF function calls made in the Cryptographic Adapter Segment 3 Common Cryptographic Architecture (CCA) code.




Two hardware models with high levels of granularity available – 73 CIs

Faster Uni Processor

Up to 7 customer PUs

Up to 64 GB memory

Up to 30 LPARs

CBU for IFL, ICF, zAAP and zIIP

Dynamic oscillator switchover

MIDAW facility

63.75K Subchannels for Set-0

Increased Number of FICON Express2 and 4 Features

Multiple Subchannel Sets per LCSS

Crypto Enhancements

IPv6 Support for HiperSockets

N_Port ID VirtualizationPU Conversions for zAAPs and zIIPs

OSA-Express2 1000BASE-T

FICON and OSA Enhancements

54 additional hardware Instructions

Redundant I/O interconnect

Configurable Crypto Express2

Hot pluggable/ maintainableMBA/STI fanout cards

Up to 16 2.7 GB STIs per system

z9 BC Functions and Features

CBU and On/Off CoD Enhancements

Separate PU pool management

Availability in EU after implementation of RoHSEnhanced Driver Maintenance


Server Time Protocol (STP)available 1/31/2007

z9 BC Overview The IBM System z9 Business Class (z9 BC) continues the generation of IBM z9 servers introduced with the IBM System z9 EC (z9 EC) that are designed to help optimize your On Demand Business. This new generation of IBM mainframes provides an advanced combination of reliability, availability, security, scalability, and virtualization features, together with the ability to reallocate processing power. The z9 BC is designed to match changing business priorities on demand.

The z9 BC is designed specifically as a midrange mainframe and offers extensive growth options and excellent price/performance for those customers requiring a lower-capacity entry point and more granular growth options than offered with the z9 EC.

The IBM z9 BC is designed to help enable your businesses to be resilient in the unpredictable on demand world. With two models and a wide range of capacity settings, the newest member of the IBM System z9 family delivers significantly improved granularity and enriched functions over its predecessor, the IBM eServer zSeries z890. The Model S07 can provide up to twice the memory, and more specialty engines as compared with the z890. Also introduced is the new System z9 Integrated Information Processor (zIIP).

The z9 BC offers four new FICON Express4 features that support auto-negotiated speeds of 1, 2, and 4 Gbps. One of the FICON Express4 features is a 2-port card that provides attractive entry pricing to FICON technology adoption and is offered exclusively on the z9 BC.

All FICON Express4 and FICON Express2 features support the Modified Indirect Data Address Word (MIDAW) facility. MIDAW is a new system architecture with software exploitation that is designed to help improve channel utilization and throughput, and potentially reduce I/O response times. The number of FICON Express4 and FICON Express2 concurrent I/O operations that may be active simultaneously has been increased from 32 to 64 per channel as compared to the z890.

IBM has a broad range of disk, tape, and SAN products that are ready to support FICON Express4. IBM TotalStorage DS8000 series and IBM TotalStorage DS6000 series disk systems, part of IBM's System



Storage portfolio, support the MIDAW facility to help enable the potential throughput and response time benefits that the MIDAW facility can bring.

New integrated clear key encryption security features on the z9 BC include support for Advanced Encryption Standard, Secure Hash Algorithm-256, and integrated Pseudo Random Number Generation. Performing these functions in hardware can contribute to improved performance.

Application of the z9 BC advanced virtualization technologies creates a solid foundation for flexible integration of business and information management.

New innovations on the z9 BC can help to ensure you have a security-rich platform, can help maximize your resources and their utilization, and can help provide you the ability to integrate applications and data across the infrastructure. The z9 BC is designed to be a flagship component of your data serving environment.




Server Time Protocol (STP)Provides capability for multiple servers to maintain time synchronization with each other and form a Coordinated Timing Network (CTN) synchronization with each other and form a Coordinated Timing Network (CTN)► CTN: a collection of servers that are time synchronized to a time value called Coordinated Server

Time (CST)Server-wide facility implemented in IBM System z9 EC, z9 BC, IBM eServer zSeries 990 and 890 (z990, z890) Licensed Internal Code (LIC)► Single view of “time” to PR/SM► PR/SM can virtualize this view of time to the individual partitions (LPARs) ► STP not available on z900, z800 or 9672 Gx servers

Message-based time synchronization protocol► Similar to Network Time Protocol (NTP) industry standard

● NOT standard NTP

Does not require dedicated Timer links► Timekeeping information transmitted over Coupling Links

● ISC-3 links (Peer mode), ICB-3 and ICB-4 links► Allows Parallel Sysplex distances to extend beyond the current 40 km limit

● Limits set by coupling protocol and linksAllows concurrent migration from an ETR network with proper planningAllows coexistence with ETR network

Server Time Protocol (STP) The Server Time Protocol feature is designed to provide the capability for multiple servers and Coupling Facilities to maintain time synchronization with each other, without requiring a Sysplex Timer. The servers and Coupling Facilities that are capable of supporting Server Time Protocol are:

• IBM System z9 Enterprise Class (z9 EC) • IBM System z9 Business Class (z9 BC) • IBM eServer zSeries 990 • IBM eServer zSeries 890

Server Time Protocol is a server-wide facility that is implemented in the Licensed Internal Code (LIC) of z9 EC, z9 BC, z990, z890, and CFs and presents a single view of time to Processor Resource/Systems Manager (PR/SM). STP uses a message-based protocol in which timekeeping information is passed over externally defined Coupling Links - InterSystem Channel-3 (ISC-3) links configured in peer mode, Integrated Cluster Bus-3 (ICB-3) links, and Integrated Cluster Bus-4 (ICB-4) links. These can be the same links that already are being used in a Parallel Sysplex for Coupling Facility (CF) message communication.

By using the same links to exchange timekeeping information and Coupling Facility messages in a Parallel Sysplex, STP can scale with distance. Servers exchanging messages over short distance links such as ICB-3 and ICB-4 are designed to meet more stringent synchronization requirements than servers exchanging messages over long distance links such as ISC-3 (distances up to 100 km), where the synchronization requirements are less stringent. This is an enhancement over the current Sysplex Timer implementation, which does not scale with distance.

The STP design has introduced a new concept called Coordinated Timing Network (CTN). A Coordinated Timing Network (CTN) is a collection of servers and Coupling Facilities that are time synchronized to a time value called Coordinated Server Time.

STP supports the following functions:



• Initialize the time manually or by dialing out to a time service, so that Coordinated Server Time can be set to within 100 milliseconds of an international time standard such as Coordinated Universal Time (UTC).

• Schedule periodic dial-outs to a time service so that Coordinated Server Time may be gradually steered to an international time standard.

• Initialize Time Zone offset, Daylight Saving Time (DST) offset, Leap seconds offset. • Schedule changes to offsets listed above. STP can automatically schedule Daylight Saving Time, based

on the selected Time Zone, a capability that did not exist on the Sysplex Timer. • Adjust Coordinated Server Time by up to +/- 60 seconds. This improves upon the Sysplex Timer's

capability of adjusting time by up to +/- 4.999 seconds.

STP Enhancements The Server Timer Protocol feature is designed to simplify hardware configurations by:

• Allowing clock synchronization for z9 EC, z9 BC, z990, and z890 servers and Coupling Facilities without requiring the Sysplex Timer and dedicated timer links. This helps reduce the need for separate hardware that needs to be ordered and maintained.

• Supporting a multisite timing network of up to 100 km (62 miles) over fiber optic cabling, thus allowing a sysplex to span these distances. This overcomes the limitations of the Sysplex Timer to Sysplex Timer links being supported only up to 40 km. STP is designed to eliminate the need for a third site to locate the second Sysplex Timer for installations where the multisite sysplex spans a distance greater than 40 km but less than 100 km (the current limit for Sysplex Timer to server connection).

• Potentially reducing the cross-site connectivity required for a multisite Parallel Sysplex. Dedicated links are no longer required to transport timing information since STP and Coupling Facility messages may be transmitted over the same links.

Additional value from Server Time Protocol may be obtained by: • Eliminating infrastructure requirements (space, power, etc) needed to support Sysplex Timers • Eliminating Sysplex Timer maintenance costs • Eliminating fiber optic infrastructure requirements for:

o Patch/trunk cables o Dense Wavelength Division Multiplexer (DWDM) ports o Dark fiber between sites for External Time Reference (ETR) and Control Link Oscillator (CLO)

links (links between Sysplex Timers) Concurrent Migration and Coexistence STP introduces the concept of a Coordinated Timing Network (CTN), to meet two key goals of System z customers:

• Concurrent migration from an existing External Time Reference (ETR) network to a timing network using STP.

• Capability of servers that cannot support STP to be synchronized in the same network as servers that support STP (z9 EC, z9 BC, z990, z890)

A CTN can be configured in two ways: • Mixed CTN (ETR and STP) which requires a Sysplex Timer. The Sysplex Timer provides the

timekeeping information in a Mixed CTN. A Mixed CTN allows you to meet the above requirements of concurrent migration and coexistence. The coexistence allows for a sysplex configuration where members of the sysplex may reside on a z800 or z900 server.

• STP-only CTN which does not require a Sysplex Timer.




z9 Support by z/OS Release

z9 capabilities differ depending on z/OS and z/OS.e release► Support provided on z/OS V1.4 w/z990 Compatibility Support

feature (and higher) or z/OS.e w/z990 Coexistence Support► NO SUPPORT provided for z/OS or z/OS.e V1.4 Base

Software requirements differ depending on z/OS release and functions exploited► Support provided via a combination of features (V1.4 only), web

deliverables, and PTFs► Required PTFs documented in hardware and software PSP

Buckets depending on what server and z/OS release you are coming from

z9 EC and z9 BC Support by z/OS (and z/OS.e) Release The software support for the z9 servers, similar to the zSeries z990 and z890, differs by z/OS release level, is provided by a combination of FMIDs and PTFs. All of the required software for migrating from a z990 or z890 to a System z9 server is delivered by PTFs. The specific PTFs that need to be installed will depend on the z/OS release. In addition, exploitation of certain functions, specifically some cryptographic functions and the new System z9 Integrated Information Processor (zIIP) support, requires the installation of FMIDs. These FMIDs are downloadable Web Deliverables. These Web deliverables are unpriced and can be downloaded at: http://www.ibm.com/eserver/zseries/zos/downloads.

The following z/OS and z/OS.e releases are supported on the z9: • z/OS V1.4 with the z/OS V1.4 z990 Compatibility Support Feature (no longer orderable), or z/OS V1.4 with

the z/OS V1.4 z990 Exploitation Support Feature (orderable until December 11, 2006, unpriced, optional feature)

• z/OS.e V1.4 with the z/OS.e V1R4 z990 Coexistence feature (no longer orderable), or z/OS.e V1.4 with the z/OS.e V1R4 z990 Coexistence Update feature (orderable until December 11, 2006, unpriced, optional feature)

• z/OS or z/OS.e V1.5 or higher Notes: 1. z/OS.e cannot run on a z9 EC, but does run on a z9 BC server. 2. The functional capabilities increase with z/OS releases. That is, z/OS V1.6 has more capabilities than

z/OS V1.4, and z/OS V1.8 exploits more functions than z/OS 1.6. For a list of z/OS and z/OS.e releases and the functions that are supported for those releases, review the tables on charts 84 and 85 on page 73.

3. The IBM Bimodal Accommodation Migration Offering (web download) is available for z/OS 1.4 (applicable to the z9 EC and z9 BC). This offering is not available for z/OS 1.5 & later, nor z/OS.e V1.4.




z9 Support by z/OS (and z/OS.e) Release

z/OS V1.8

z/OS V1.7 plus PTFs

z/OS V1.6 plus PTFs

z/OS V1.5 plus PTFs

z/OS V1.4 with z990 Exploitation Support feature + PTFs

z/OS V1.4 with z990 Compatibility Support feature + PTFs

Note: z/OS.e V1.4 with the z/OS.e z990 Coexistence feature (or z990 Coexistence Update feature) and later z/OS.e releases are supported on z9 BC servers (not z9 EC servers)

Allocation

HCD

EREP

RMF

IOCP

HLASM

SRM

SMF

IOS

DFSMS Comm Server

BCP

z9 Support by z/OS (and z/OS.e) Release These are the supported levels which can run on a z9 EC or z9 BC server. It does not imply all z9 functions are available in all supported releases. The next several charts will identify what functions each release supports.

The IBM Bimodal Accommodation Migration Offering (web download) is ONLY available for z/OS 1.4 and the z/OS V1.4 features, applicable to the z9 EC and z9 BC, therefore z/OS V1.5 and higher can only run in z/Architecture (64-bit) mode on a z9 EC, z9 BC, z990, z890, z900, and z800. This offering is not available for z/OS.e.




Software NOT Supported on z9Base z/OS or z/OS.e V1.4► does not have the z990 Compatibility or Exploitation

Support feature installed● All ServerPac z/OS orders built after Feb. 24, 2003

automatically included the z990 Exploitation Support feature– the z/OS V1.4 z990 Exploitation Support feature is orderable

through December 16, 2006 via CBPDO● All ServerPac z/OS.e orders built after Feb. 24, 2003

automatically included the z990 Coexistence Update feature– the z/OS.e V1.4 z990 Coexistence Update feature is orderable

through December 16, 2006 via CBPDO All ServerPac z/OS.eorders

z/OS V1.1, V1.2, V1.3 and z/OS.e V1.3

Any OS/390 releaseNote: Service support is withdrawn for all OS/390 releases and z/OS releases V1.1, V1.2, V1.3 and z/OS.e V1.3.

Service

supp

ort fo

r z/O

S V1.4

and V

1.5

is pla

nned

to be

with

drawn M

arch 2

007


Determining Your Level of z/OS V1.4 or z/OS.e V1.4Check if the following FMIDs are installed (or SUP’d)► HCD HCS7708► HCM HCM1510► ICKDSF EDU1H01► ICSF HCR7708

If so, you have the FMIDs for z990 support installed► If not, then you have just z/OS V1.4 or z/OS.e base code installed

Now check if BCP FMID JBB7717 is installed► If so, you have either

● z/OS V1.4 with the z/OS V1.4 z990 Exploitation feature ● z/OS.e V1.4 with the z/OS.e V1.4 z990 Coexistence Update feature

► If not, you have● z/OS V1.4 with the z/OS V1.4 z990 Compatibility feature ● z/OS.e V1.4 with the z/OS.e V1.4 z990 Coexistence feature

NOTE: The z/OS V1.4 and z/OS.e V1.4 features are no longer orderable, but the code is downloadable from the z/OS Download page ► http://www.ibm.com/servers/eserver/zseries/zos/downloads/

Determining Your Level of z/OS V1.4 or z/OS.e V1.4 You may remember that all z/OS V1.4 and z/OS.e V1.4 orders placed after February 24, 2003 were required to order the appropriate z990 (and z890) exploitation feature. Therefore, it is very likely that you have the z990 support installed. The procedure to determine what level of z/OS (or z/OS.e) that you have installed is fairly straightforward. The ‘key’ is verifying the presence of a very few FMIDs.



First, check the z/OS target zone for the following FMIDs: HCS7708 (HCD), HCM1510 (HCM), EDU1H01 (ICKDSF), and HCR7708 (ICSF). If they are installed (or SUP’d), then you have at least z990 (or z890) compatibility code installed. If they are not installed, you are running base z/OS (or z/OS.e) and will need to order the z/OS V1.4 z990 Exploitation Support feature (if you are licensed for z/OS) or the z/OS.e V1.4 Coexistence Update feature (if you are licensed for z/OS.e).

Next, check in that same z/OS target zone if you have the BCP FMID JBB7717 installed, this will determine whether or not you have the z990 (and z890) exploitation code installed.

• If you are licensed for z/OS and have the FMID installed, then you have the z/OS V1.4 z990 Exploitation feature installed.

• If you are licensed for z/OS and do NOT have the FMID installed, then you have the z/OS V1.4 z990 Compatibility feature installed.

• If you are licensed for z/OS.e and have the FMID installed, then you have the z/OS V1.4 z990 Coexistence Update feature installed.

• If you are licensed for z/OS.e and do NOT have the FMID installed, then you have the z/OS V1.4 z990 Coexistence feature installed.

To understand the differences between compatibility and exploitation, see chart 67 on page 64. You will need to verify that PTFs identified in the PSP bucket are also installed, and will need an ICSF web deliverable if you need to do secure key processing. See the following pages for more detail on how to determine what is needed and verify what has been installed.

Reminder: For z/OS V1.4 and V1.5 customers it is time to move ahead! End of service for these releases is planned for March 31, 2007. We encourage you to move to z/OS V1.7 or z/OS V1.8 now! If you're on z/OS V1.4, z/OS V1.7 is the last release you can migrate to in a single step. If you're on z/OS V1.5, z/OS V1.8 is the last release you can migrate to in a single step.




z9: APARs Provide Compatibility Supportz9 Compatibility Support for all z/OS supported environments

OA14563z/OS.e support (for z9 BC only)

OA10586, OA12728DFSMS

OA12242, OA12416SRM

OA13133, OA13333HCD – Miscellaneous Fixes

OA09157(*), OA11946ICSF (Crypto toleration)

PK02660, PK18170, PK25298, PK23005

HLASM support for new hardware instructions

OA11007, OA15169OSA/SF - OSA-Express2 CHPID type OSN; displaying layer 2 MAC addresses and VLANs registered on the OSA

OA10346, OA14024RMF for Enhanced PR/SM Diagnose 204 OutputOA11665, OA14974IOCP

OA07875(*), OA13601HCD Processor Support Module (PIT)

IO00735, IR53369EREP Support for new z9

OA11730, OA14941SMF recognizes new processor SU values, based on LSPR information for Measured Usage Reporting Program - IFAURP/IFAUMCCT

OA08197(*)BCP Support for IODF Size Reduction

(*) Integrated into z/OS V1.7 FMIDs

See 20

94DEVIC

Eor

2096

DEVICE

PSP

Bucke

t for la

test s

ervice

requ

ired


z/OS (and z/OS.e) Supported Software Environment for the z9

z/OS V1.8

z/OS V1.7 plus PTFs

z/OS V1.6 plus PTFs

z/OS V1.5 plus PTFs



Note: The z/OS Bimodal Migration Accommodation is ONLY supported on z/OS V1.4 (with or without the z990 features). Therefore, when used z/OS V1.4 can run in 31-bit mode on a z9 server. z/OS V1.5

and higher releases, and all z/OS.e releases, MUST run in 64-bit (z/Architecture) mode.

Allocation

HCD

EREP

RMF

IOCP

HLASM

SRM

SMF

IOS

DFSMS Comm Server

BCP




z/OS V1.4 with the z/OS V1.4 z990 Compatibility Support (z9 EC or z9 BC) z/OS.e V1.4 with the z/OS.e z990 Coexistence feature (z9 BC only)

Provides same functionality as that on the z990► Single Logical Channel Subsystem► Up to 15 LPARsNote: Assumes all FMIDs from compatibility feature and PTF service from the

z990 PSP are installedPlus

► 63.75K Subchannel Support ► Separate LPAR management of Processor Units (PUs)► OSA-Express2 Gigabit Ethernet SX and LX for CHPID OSD ► OSA-Express2 10 Gigabit Ethernet LR for CHPID OSD► OSA-Express2 1000BASE-T Ethernet for CHPID types OSC, OSD, and OSE► FICON Express2 CHPID FC ► FICON Express4 supporting 1, 2, or 4 Gbps with 2-port or 4-port card ► CP Assist for Cryptographic Functions (CPACF) ► Crypto Express2, compatibility support when Crypto Express2 adapter is

configured as a coprocessor ● Requires a z990 Cryptographic Support Web deliverable


In baseN/AFICON Express4 supporting 1, 2, or 4 Gbps with 2-port or 4-port card

RMF APAROA07347RMF Compatibility if Crypto Express2 (CEX2C) cards are installed

ICSF APARsOA09157OA11946

Crypto Express2 configured as a coprocessor

ICSF Web DeliverableN/ACP Assist for Cryptographic Functions (CPACF)

In baseN/AFICON Express2 CHPID FC

In baseN/AOSA-Express2 1000BASE-T Ethernet CHPID OSC, OSE, and OSD

In baseN/AOSA-Express2 10 Gigabit Ethernet CHPID OSDIn baseN/AOSA-Express2 Gigabit Ethernet CHPID OSD

In baseN/ASeparate LPAR management of Processor Units (PUs)

See chart 15All Compatibility PTFs from chart 15

HCD APAROA0787563.75K Subchannel Support

CommentsAPARFunction

z/OS V1.4 Compatibility Requirements

z/OS V1.4 with the z/OS V1.4 z990 Compatibility Support (z9 EC or z9 BC) z/OS.e V1.4 with the z/OS.e z990 Coexistence feature (z9 BC only)

z/OS V1.4 with the z/OS V1.4 z990 Compatibility Support Feature (z9 EC or z9 BC) z/OS.e V1.4 with the z/OS.e z990 Coexistence feature (z9 BC only) 63.75K Subchannel Support: The z9 makes additional subchannels available. Previous servers reserved 1024 subchannels, making it possible to define a maximum of 64,512 devices. The z9 EC and z9 BC make an additional 768 subchannels available, making it possible to define up to 65,280 devices for each z/OS (or z/OS.e) LPAR.



Separate PU management - new flexibility for managing Processor Units (PUs): PUs defined as Internal Coupling Facility (ICF) processors, Integrated Facility for Linux (IFL) processors, or System z9 Application Assist Processors (zAAPs), or System z9 Integrated Information Processor (zIIPs) are now managed separately. In the past, ICF processors, IFL processors, and zAAPs were grouped together for allocation within and across the LPARs.

The separate management of PU types enhances and simplifies capacity planning and management of the configured LPARs and their associated processor resources.

OSA-Express2 Ethernet on the z9 - choose any combination: The Open Systems Adapter-Express2 (OSA-Express2) features provide you with functions and scalability to help satisfy the demands of your global business. With data rates of 10 or 100 Megabits per second (Mbps), 1 Gigabit per second (Gbps), and 10 Gbps, you can select the features that best suit your current and future application requirements:

• OSA-Express2 Gigabit Ethernet LX (long wavelength) (#3364) • OSA-Express2 Gigabit Ethernet SX (short wavelength) (#3365) • OSA-Express2 1000BASE-T Ethernet (#3366) • OSA-Express2 10 Gigabit Ethernet LR (long reach) (#3368)

With multiple Ethernet options, you have the flexibility to deploy where applicable: • 1000BASE-T Ethernet and a copper cabling infrastructure • Gigabit Ethernet and a multimode or single mode fiber optic cabling infrastructure • 10 Gigabit Ethernet LR and a single mode fiber optic cabling infrastructure

You have LAN connectivity solutions that can help to satisfy your departmental, data center, enterprise, LAN backbone, building-to-building, and business continuity requirements.

The OSA-Express2 Ethernet features support the following CHPID types:

CHPID Type OSA-Express2 features Purpose/Traffic OSC 1000BASE-T OSA-Integrated Console Controller (OSA-ICC)

TN3270E, non-SNA DFT to IPL CECs and LPARs, Operating system console operations

1000BASE-T QDIO GbE TCP/IP traffic when Layer 3

OSD

10 GbE Protocol-independent when Layer 2

OSE 1000BASE-T Non-QDIO, SNA/APPN/HPR and/or TCP/IP

1000BASE-T OSA-Express2 OSN (OSA for NCP) OSN GbE OSA-Express2 OSN (OSA for NCP)

In addition to the above list of functions identified by CHPID type, over time the family of Open Systems Adapters has added additional connectivity and functions. Here are some of the capabilities and functions currently supported:

• Layer 2 for protocol-independent packet forwarding • Spanned channels for sharing of OSA features among Logical Channel Subsystems (LCSSs) • 48 connections to the LAN, up to 24 features per server • Open Systems Adapter/Support Facility (OSA/SF) Java (1) GUI • VLANs (802.1q) • Simple Network Management Protocol (SNMP) Get, GetNext, dot3StatsTable, performance data, trap,

set



• IPv4 and IPv6 • Checksum offload for IPv4 packets (z/OS V1.5 and higher)

The following functions are exclusive to the OSA-Express2 features: • OSA-Express2 OSN (OSA for NCP)(1000BASE-T, GbE) (new) • 640 TCP/IP stacks per port, for hosting more images on the z9. • Large send for IPv4 packets - the host sends 64 KB blocks to OSA for packet processing returning CPU

cycles for application use. • Concurrent LIC update capability - when properly configured, this capability is designed to avoid a

configuration off/on, minimizing the disruption of network traffic during an update (applicable to CHPID types OSD and OSN).

Refer to the publication OSA-Express Customer's Guide and Reference (SA22-7935).

Up to 336 FICON Express2 channels supported on a z9 EC or z9 BC: The FICON Express2 features, with 4 channels per feature, support a link date rate of 1 or 2 Gbps autonegotiated and you can now install up to 336 channels (84 features) on the z9 EC or z9 BC. Up to 240 FICON channels is supported on z990.

The FICON Express2 features support: • Native FICON and FICON Channel-to-Channel (CTC) traffic (CHPID type FC) supporting connectivity to

servers, disks, tapes, and printers in the z/OS, z/VM, z/VSE, VSE/ESA, z/TPF, TPF, and Linux on System z9 environments

• Fibre Channel Protocol traffic (CHPID type FCP) supporting connectivity to disks, tapes, and printers through Fibre Channel switches and directors in the z/VM, z/VSE (ESS disks only), and Linux on System z9 environments

The FICON Express2 LX (#3319) and SX (#3320) features are offered in four channel increments, and all channels on a single feature are of the same type, either LX or SX. You may also carry forward to the z9 your current FICON Express2 features as well as your current FICON Express features (#2319, #2320).

FICON Express4 — 1, 2, or 4 Gbps: A new generation of FICON features, FICON Express4, are now being offered. FICON Express4 continues the tradition of offering more capabilities with each new generation. FICON Express4:

• Is designed to deliver increased performance compared to the FICON Express2 features on z890 • Offers two unrepeated distance options (4 kilometer and 10 kilometer) when using single mode fiber

optic cabling • Supports a 4 Gbps link data rate with autonegotiation to 1 or 2 Gbps for synergy with existing switches,

directors, and storage devices • Offers an entry-level 4 kilometer (km) LX feature supporting two channels per feature for data

centers with limited requirements for single mode fiber optic cabling connectivity The FICON Express4 features have two modes of operation designed for connectivity to servers, switches, directors, disks, tapes, and printers:

1. Native FICON and FICON Channel-to-Channel (CTC) traffic (CHPID type FC) in the z/OS and z/OS.e, z/VM, z/VSE, VSE/ESA, z/TPF, TPF, and Linux on System z9 environments.

2. Fibre Channel Protocol traffic (CHPID type FCP) in the z/VM, z/VSE, and Linux on System z9 environments.

The FICON Express4 features are exclusive to System z9 EC and z9 BC.

CP Assist for Cryptographic Function (CPACF) enablement - CPACF for cryptographic support is standard on every Processor Unit (PU) that is defined as a Central Processor (CP) or an Integrated Facility for Linux (IFL).



CPACF offers clear key data encryption and decryption with support of Advanced Encryption Standard (AES), Data Encryption Standard (DES), Triple Data Encryption Standard (TDES), Pseudo Random Number Generation (PRNG), Secure Hash Algorithm-1 (SHA-1), and SHA-256.

CPACF functions, except SHA-1 and SHA-256, are shipped disabled with every PU. Feature #3863 is a no charge enablement feature. For new servers, shipped from the factory, #3863 CPACF enablement is loaded prior to shipment. For other than new shipments, Licensed Internal Code is shipped by an enablement diskette. The function is enabled using the Support Element (SE).

Crypto Express2 - The Crypto Express2 feature has been designed to satisfy high-end server security requirements. Crypto Express2 executes the functions that were previously offered by the PCICA (#0862) and PCIXCC features, performing hardware acceleration for Secure Sockets Layer (SSL) transactions and clear key RSA acceleration. The Crypto Express2 feature is configurable. The Crypto Express2 feature, with two PCI-X adapters, can be defined for secure key transactions or Secure Sockets Layer (SSL) acceleration.

The Crypto Express2 feature designed to conform to the Federal Information Processing Standard (FIPS) 140-2 Level 4 Certification, and supports User Defined Extension (UDX) services to implement cryptographic functions and algorithms.

Note: The crypto cards used on previous generation machines (PCICA, PCIXCC on z990 and PCICC on z900) cannot be carried forward on an upgrade to a z9 EC or z9 BC.

If you plan to configure a Crypto Express2 as a coprocessor on the System z9 server for secure key processing, then you must be at FMID HCR770A or later. The z990 Cryptographic Support web deliverable (FMID HCR770A) is no longer downloadable, but will provide the support if already installed. Its replacement, the z990 and z890 Enhancements to Cryptographic Support web deliverable (FMID HCR770B) is available for download. In addition, you must install the PTFs listed in the hardware PSP bucket (either 2094DEVICE or 2096DEVICE), as well as the service identified in the program directory that comes with the Web deliverable and the service which is recommended in the appropriate ICSF PSP bucket.

ICSF users running on z990 servers with ICSF FMIDs HCR770A or HCR770B who are planning to use the new Crypto Express2 Coprocessor (CEX2C), require ICSF toleration APAR OA09157. ICSF will ABEND with ABEND18F reason code 10F without this APAR applied.

ICSF users running on z990 servers with ICSF FMIDs HCR770A or HCR770B who are planning to use the new Crypto Express2 Coprocessor configured as an Accelerator (CEX2A),require ICSF toleration APAR OA11956. ICSF will ABEND with ABEND18F reason code 10F without this APAR applied.

ICSF users running on a z9 EC or z9 BC server with ICSF FMIDs HCR770A or HCR770B who are planning to configure a Crypto Express2 as an Accelerator (CEX2A), will require ICSF toleration APAR OA11946. ICSF will erroneously display CEX2As on the ICSF Coprocessor Management panel.





z/OS V1.8

z/OS V1.7 plus PTFs

z/OS V1.6 plus PTFs

z/OS V1.5 plus PTFs



Allocation

HCD

EREP

RMF

IOCP

HLASM

SRM

SMF

IOS

DFSMS Comm Server

BCP

Note: The z/OS Bimodal Migration Accommodation is ONLY supported on z/OS V1.4 (with or without the z990 features). Therefore, when used z/OS V1.4 can run in 31-bit mode on a z9 server. z/OS V1.5

and higher releases, and all z/OS.e releases, MUST run in 64-bit (z/Architecture) mode.


Provides same functionality as that on the z990► Multiple Logical Channel SubsystemsNote: Assumes all FMIDs from exploitation support feature and PTF service from the z990 PSP

are installedPlus

► 63.75K Subchannel Support ► Separate LPAR management of Processor Units (PUs)► OSA-Express2 Gigabit Ethernet SX and LX for CHPID OSD► OSA-Express2 10 Gigabit Ethernet LR for CHPID OSD► OSA-Express2 1000BASE-T Ethernet for CHPID types OSC, OSD, and OSE► FICON Express2 CHPID FC ► FICON Express4 supporting 1, 2, or 4 Gbps with 2-port or 4-port card ► CP Assist for Cryptographic Functions (CPACF)► Crypto Express2, compatibility support when Crypto Express2 adapter is configured as a

coprocessor ● Requires a z990 Cryptographic Support Web deliverable

►► Up to 60 Logical Partitions (15 LPARs per Up to 60 Logical Partitions (15 LPARs per LCSSLCSS))●● Up to 30 Logical Partitions (15 Up to 30 Logical Partitions (15 LPARsLPARs per per LCSSLCSS) on a z9 BC) on a z9 BC

►► Channel Data Link Control (CDLC) Protocol SupportChannel Data Link Control (CDLC) Protocol Support►► Request Node Identification Data (RNID) for Request Node Identification Data (RNID) for FICONFICON►► OSAOSA--Express2Express2 OSNOSN -- Open Systems Adapter for Open Systems Adapter for NCPNCP (Gigabit and (Gigabit and 1000BASE1000BASE--TT))►► FICONFICON Error RecoveryError Recovery

z/OS V1.4 with the z/OS V1.4 z990 Exploitation Support (z9 EC or z9 BC) z/OS.e V1.4 with the z/OS.e z990 Coexistence Update feature (z9 BC only)




z/OS V1.4 with the z/OS V1.4 z990 Exploitation Support (z9 EC or z9 BC) z/OS.e V1.4 with the z/OS.e z990 Coexistence Update feature (z9 BC only)

BCP IOSHCD

OA11238OA07875

OSAOSA--Express2Express2 OSNOSN -- Open Systems Adapter for Open Systems Adapter for NCPNCP(Gigabit and (Gigabit and 1000BASE1000BASE--TT))

BCPOA13644FICONFICON Error RecoveryError Recovery

See chart 18All PTFs listed for z/OS with the z/OS V1.4 z990 Compatibility Support Feature from chart 15

BCP IOSHCD

OA11238OA07875

Channel Data Link Control (CDLC) Protocol SupportChannel Data Link Control (CDLC) Protocol Support

IOS APAROA10906Request Node Identification Data (RNID) for FICONRequest Node Identification Data (RNID) for FICON

In BaseN/AUp to 60 Logical PartitionsUp to 60 Logical Partitions



z/OS V1.4 Exploitation Requirements

z/OS V1.4 with the z/OS V1.4 z990 Exploitation Support Feature (z9 EC or z9 BC) z/OS.e V1.4 with the z/OS.e z990 Coexistence Update feature (z9 BC only) Request Node Identification Data (RNID) - designed to assist with the isolation of FICON cabling-detected errors: In a fiber optic environment, with extended distances, resolution of fiber optic cabling problems can be a challenge. To help facilitate resolution, the operating system can now request the RNID data for each device or control unit attached to native FICON channels and display the RNID data using an operator command. In z/OS, the output of the DISPLAY MATRIX operator command (D M=DEV) includes RNIDs to help make it easier to diagnose these problems by making additional information, such as a device's serial number, available.

RNID is exclusive to the z9, and is supported by the FICON Express2 and FICON Express features (CHPID type FC), and by z/OS.

Up to 60 Logical Partitions: IBM is once again doubling the number of Logical Partitions (LPARs). You now have the ability to define up to 60 LPARs, 15 LPARs per Logical Channel Subsystem, which may provide you even more flexibility to allocate hardware resources. With Processor Resource/Systems Manager (PR/SM) and Multiple Image Facility (MIF) you can share ESCON and FICON channels, ISC-3s, and OSA ports across LPARs. Support for up to 30 LPARs became available October 2003.

Support of up to 60 LPARs is exclusive to the z9 EC server and is supported by z/OS, z/VM, z/VSE (TM), TPF, z/TPF, and Linux on System z9.

OSA-Express2 OSN - Open Systems Adapter for NCP: The OSA-Express2 Gigabit Ethernet and 1000BASE-T Ethernet features (#3364, #3365, #3366) now have the capability to provide channel connectivity from System z9 operating systems to IBM Communication Controller for Linux on zSeries (CCL) with the introduction of the Open Systems Adapter for the Network Control Program (OSA for NCP) supporting the Channel Data Link Control (CDLC) protocol, providing an alternative to a SNA network.



OSA-Express2 OSN can help to eliminate the requirement to have any form of external medium (and all related hardware) for communications between the host operating system and the CCL image. Traffic between the two images (operating system and CCL) is no longer required to flow on an external Local Area Network (LAN) or ESCON channel; traffic can flow LPAR-to-LPAR. OSA-Express2 OSN provides an efficient method of communication, and is designed to create a secure and seamless integration of the host operating system and CCL.

If you continue to require SNA solutions that require NCP functions, you can now consider CCL as a migration strategy to replace your IBM Communications Controllers (374x). The CDLC connectivity option enables TPF environments to now exploit CCL.

The OSA-Express2 Gigabit Ethernet and 1000BASE-T Ethernet features provide connectivity with a new CHPID type OSN (Open Systems Adapter for NCP). Each host operating system that currently supports CDLC is expected to be able to utilize CDLC to CCL without changes to the operating system. OSA-Express2 OSN supports both SNA PU Type 5 and PU Type 2.1 channel connectivity.

Utilizing existing SNA support (multiple transmission groups), OSA-Express2 OSN support permits multiple connections between the same CCL image and the same host operating system (such as z/OS or TPF) image. The operating systems must reside within the same physical server (CPC) as the CCL image.

OSA-Express2 OSN: • Is designed to appear to the operating systems as an ESCON channel connected to a 374x device type

which exploits existing CDLC protocols • Allows system administrators of the various operating systems to configure, manage, and operate their

CCL NCPs as if they were running in an ESCON-attached 374x Communications Controller • Enables NCP channel-related functions such as loading and dumping of the NCP • Does not require external hardware (cables or switches) • Allows multiple CCL images to communicate with multiple operating system images, supporting up to 180

connections (374x subchannels) per CHPID type OSN • Can span Logical Channel Subsystems

The CCL image connects to OSA-Express2 OSN using extensions to the QDIO architecture. Linux support is in the QETH module.

OSA-Express2 OSN support is exclusive to the z9, to the OSA-Express2 Gigabit Ethernet SX, Gigabit Ethernet LX, and 1000BASE-T Ethernet features (#3364, #3365, #3366), and requires the port to be configured as CHPID type OSN, which can be configured on a port-by-port basis. OSA-Express2 OSN is exclusively for internal communication, LPAR-to-LPAR. Concurrent LIC update is supported. OSA-Express2 OSN is supported by z/OS, z/VM, z/VSE, TPF, and Linux on System z9. Refer to the Software requirements section. Refer to the Statement of General Direction section for information on IBM Communication Controller for Linux on zSeries support of OSA-Express2 OSN.

Improved FICON error recovery: System z9 and z/OS and z/OS.e V1.7 I/O recovery processing improvements are designed to allow for the system to detect switch/director fabric problems that may cause FICON links to fail and recover multiple times in a short period of time.

This enhancement is designed to allow the system to detect these conditions and keep an affected path offline until an operator action is taken. This is expected to help limit the performance impacts of switch/director fabric problems. The improved FICON error recovery function is available on z/OS V1.4 with the z/OS V1.4 z990 Exploitation Support feature (or z/OS.e V1.4 with the z/OS.e V1.4 z990 Coexistence Update feature) with PTFs.





z/OS V1.8

z/OS V1.7 plus PTFs

z/OS V1.6 plus PTFs

z/OS V1.5 plus PTFs



Note: z/OS V1.5 (and higher) require 64-bit architecture to IPL (31-bit not allowed) when on a z9 server

Allocation

HCD

EREP

RMF

IOCP

HLASM

SRM

SMF

IOS

DFSMS Comm Server

BCP


z/OS V1.5 (z9 EC or z9 BC) or z/OS.e V1.5 (z9 BC only)Provides same functionality as that on the z990

► Multiple Logical Channel Subsystems► Broadcast for IPv4 PacketsNote: Assumes PTF service from the z990 PSP are installed

Plus► 63.75K Subchannel Support ► Separate LPAR management of Processor Units (PUs)► OSA-Express2 Gigabit Ethernet SX and LX for CHPID OSD and OSN► OSA-Express2 10 Gigabit Ethernet LR for CHPID OSD

● Includes Checksum offload► OSA-Express2 1000BASE-T Ethernet for CHPID types OSC, OSD, OSE, and OSN► FICON Express2 CHPID FC ► FICON Express4 supporting 1, 2, or 4 Gbps with 2-port or 4-port card ► CP Assist for Cryptographic Functions (CPACF)► Crypto Express2, compatibility support when Crypto Express2 adapter is configured as a

coprocessor ● Requires a z990 Cryptographic Support Web deliverable

► Up to 60 Logical Partitions (15 LPARs per LCSS)● Up to 30 Logical Partitions (15 LPARs per LCSS) on a z9 BC

► Channel Data Link Control (CDLC) Protocol Support► Request Node Identification Data (RNID) for FICON►► FICONFICON Error RecoveryError Recovery




See chart 22All PTFs listed for z/OS with the z/OS V1.4 z990 Exploitation Support Feature from chart 18

See chart 18All PTFs listed for z/OS with the z/OS V1.4 z990 Compatibility Support Feature from chart 15



z/OS and z/OS.e V1.5 Requirements

z/OS V1.5 (z9 EC or z9 BC) or z/OS.e V1.5 (z9 BC only)



z/OS V1.8

z/OS V1.7 plus PTFs

z/OS V1.6 plus PTFs

z/OS V1.5 plus PTFs



Allocation

HCD

EREP

RMF

IOCP

HLASM

SRM

SMF

IOS

DFSMS Comm Server

BCP

Note: z/OS V1.6 (and higher) require 64-bit architecture to IPL (31-bit not allowed)




Provides same functionality as that on the z990► Multiple Logical Channel Subsystems► zSeries Application Assist Processors (zAAPs)► Up to 32 CPs for a single LPARNote: Assumes all PTF service from the z990 PSP are installed

Plus► Up to 60 Logical Partitions (15 LPARs per LCSS)

● Up to 30 Logical Partitions (15 LPARs per LCSS) on a z9 BC► Channel Data Link Control (CDLC) Protocol Support► Request Node Identification Data (RNID) for FICON► 63.75K Subchannel Support ► Separate LPAR management of Processor Units (PUs)► OSA-Express2 Gigabit Ethernet SX and LX for CHPID OSD and OSN► OSA-Express2 10 Gigabit Ethernet LR for CHPID OSD (Includes Checksum offload)► OSA-Express2 1000BASE-T Ethernet for CHPID types OSC, OSD, OSE, and OSN►► FICONFICON Error RecoveryError Recovery► FICON Express2 CHPID FC ► FICON Express4 supporting 1, 2, or 4 Gbps with 2-port or 4-port card ► CP Assist for Cryptographic Functions (CPACF)►► MIDAW (Modified Indirect Addressing Words) SupportMIDAW (Modified Indirect Addressing Words) Support►► EnhancementsEnhancements to CPACF (AES, PRNG, SHAto CPACF (AES, PRNG, SHA--256)256)►► Crypto Express2 as a coprocessor or acceleratorCrypto Express2 as a coprocessor or accelerator►► TCP Segmentation OffTCP Segmentation Off--load feature (also called load feature (also called OSAOSA--Express2Express2 Large Send)Large Send)►► IBM System z9 Integrated Information Processor (IBM IBM System z9 Integrated Information Processor (IBM zIIPzIIP) Support) Support



zIIP Web DeliverableBCP, WLM, RMF,

SDSF, DB2, Omegamon XE (z/OS),

Omegamon II (MVS), Omegamon Base,

Omegamon XE for DB2

FMID(JBB77S9)APARs in Functional

ZIIP PSP Bucket

IBM System z9 Integrated Information Processor (IBM zIIP) Support

BCPOA12208GA2 Support

TCP/IPSNA

PK02490, PK21685OA11148

TCP Segmentation Off-load feature (also called OSALarge Send)

See charts 18 and 22All PTFs listed for previous z/OS levels (V1.4 & V1.5)

HCDBCP, DFSMS

OA06830 +APARs in Functional MIDAW PSP Bucket

MIDAW Support

ICSF Web DeliverableN/ACrypto Express2 configured as a acceleratorICSF Web DeliverableN/AEnhancements to CPACF (AES, PRNG, SHA-256)

See chart 15All Compatibility PTFs from chart 12CommentsAPARFunction

z/OS and z/OS.e V1.6 Requirements


z/OS V1.6 (z9 EC or z9 BC) or z/OS.e V1.6 (z9 BC Only) MIDAW (Modified Indirect Data Address Word) support: Indirect Addressing (IDA) provides virtual storage access for channel programs. The z9 implements a new function for channel programming, modified indirect addressing words (MIDAWs). MIDAWs can be used to move data over FICON and ESCON channels. For FICON channels, this support can provide substantially better response time while increasing overall



channel bandwidth. The use of the MIDAW facility, by applications that currently use data chaining, may result in improved FICON performance by reducing channel, director, and control unit overhead. Applications that use the following may benefit: DB2, VSAM, Partitioned Data Set Extended (PDSE), Hierarchical File System (HFS), z/OS File System (zFS), and other datasets exploiting striping and compression. Specifically, MIDAWs exploitation by z/OS is expected to improve performance for some DB2 table scan, DB2 sequential prefetch, BSAM, and extended-format data set operations by reducing system overhead for I/O requests on the z9 EC or z9 BC server, with no application changes.

The MIDAW facility is exclusive to the z9, and is supported by ESCON (CHPID type CNC), and by the FICON features (CHPID types FCV and FC).

Cryptographic support: Integrated Cryptographic Service Facility (ICSF) supports the cryptographic functional updates provided by the z9, including support for clear key AES and SHA-256 cryptographic algorithms. These functions are designed to allow customers to exploit new high-capacity hardware and a more robust development environment, in order to help grow existing applications and deploy new applications.

Enhancements to CP Assist for Cryptographic Function (CPACF): CPACF, supporting clear key encryption, is activated using a no-charge enablement feature (#3863) and offers the following on every Processor Unit (PU) identified as a Central Processor (CP) or Integrated Facility for Linux (IFL):

• Data Encryption Standard (DES) • Triple Data Encryption Standard (TDES) • Secure Hash Algorithm (SHA-1)

CPACF has been enhanced to include support of the following on CPs and IFLs: • Advanced Encryption Standard (AES) for 128-bit keys • Pseudo Random Number Generation (PRNG) • SHA-256

PRNG is a standard function supported on the Crypto Express2 feature.

CPACF performance is designed to scale with PU performance improvements. SHA-1 and SHA-256 are shipped enabled on all servers and do not require the enablement feature.

Support for CPACF is also available using the Integrated Cryptographic Service Facility (ICSF). ICSF is a component of z/OS, and is designed to transparently use the available cryptographic functions, whether CPACF or Crypto Express2, to balance the workload and help address the bandwidth requirements of your applications.

Configurable Crypto Express2: The Crypto Express2 feature has two PCI-X adapters. Each of the PCI-X adapters can be defined as either a Coprocessor or an Accelerator.

• Crypto Express2 Coprocessor - for secure key encrypted transactions (default) o Designed to support security-rich cryptographic functions, use of secure encrypted key values,

and User Defined Extensions (UDX) o Designed for Federal Information Processing Standard (FIPS) 140-2 Level 4 certification

• Crypto Express2 Accelerator (the acceleration mode for SSL/TLS operations and digital certificate operations which were previously done in the PCICA card allows customers to migrate from PCICA to the X Crypto Express2) - for Secure Sockets Layer (SSL/TLS) acceleration

o Designed to support clear key RSA operations o Offloads compute-intensive RSA public-key and private-key cryptographic operations employed

in the SSL protocol

When a System z9 with four CPs and both PCI-X adapters on a Crypto Express2 feature are configured as accelerators, the Crypto Express2 feature is designed to perform up to 6000 SSL handshakes per second. This



represents, approximately, a 3X performance improvement compared to z990 when using either a PCI Cryptographic Accelerator (PCICA) feature, with two PCI accelerators per feature, or the current Crypto Express2 feature, with two PCI-X adapters per feature. The SSL performance was achieved using z/OS V1.7 with Cryptographic Support for z/OS V1.6/V1.7 Web deliverable, and ICSF FMID HCR7730.

Since the performance enhancements are implemented in Licensed Internal Code, current Crypto Express2 features carried forward from z990 to System z9 may take advantage of increased SSL performance and the new configuration capability.

These measurements are examples of the maximum handshakes per second achieved in a laboratory environment with no other processing occurring and do not represent actual field measurements. Details are available upon request.

For z/OS V1.6, z/OS.e V1.6, z/OS V1.7 or z/OS.e V1.7: If you want to exploit either of the following: o Enhancements to CP Assist for Cryptographic Functions (CPACF) on the System z9 server. The

enhancements are support for the Advanced Encryption Standard (AES) for 128-bit keys, Secure Hash Algorithm-256(SHA-256), and Pseudo Random Number Generation PRNG.

o Crypto Express2 exploitation when a Crypto Express2 PCI-X adapter is configured as an accelerator or a coprocessor on the System z9 server

then you must download and install the Cryptographic Support for z/OS V1R6/R7 Web deliverable (which was FMID HCR7730, or the follow-on Enhancements to Cryptographic Support for z/OS and z/OS.e V1R6/R7 Web deliverable, which is FMID HCR7731), as well as the service identified in the program directory that comes with the Web deliverable and the service which is recommended in the appropriate ICSF PSP bucket. Please note that these Web deliverables also provides support for callers running in 64-bit addressing mode.

For z/OS V1.6, z/OS.e V1.6, z/OS V1.7 or z/OS.e V1.7: If you will exploit Remote Key Loading for ATMs and Point of Sale devices (POSs), or will implement ISO 16609 CBC Mode TDES MAC, then you must download and install the Enhancements to Cryptographic Support for z/OS and z/OS.e V1R6/R7 Web deliverable, which is FMID HCR7731, as well as the service identified in the program directory that comes with the Web deliverable and the service which is recommended in the appropriate ICSF PSP bucket. Note that for z/OS and z/OS.e V1.8, which are planned to be available September 2006, the web deliverable is not needed.

System z9 Integrated Information Processor (zIIP): The System z9 Integrated Information Processor (zIIP) is the latest specialty engine for the IBM System z9 mainframe. The zIIP is designed to help improve resource optimization and lower the cost of portions of eligible workloads, enhancing the role of the System z9 mainframe as the data hub of the enterprise. The System z9 Integrated Information Processor (zIIP) will join the ranks of the eServer zSeries Application Assist Processor (zAAP), and Integrated Facility for Linux (IFL). All specialty engines run full speed. The zIIP's execution environment will accept eligible work from z/OS (minimum level is z/OS and z/OS.e V1.6), which will manage and direct the work between the general purpose processor and the zIIP. DB2 for z/OS V8 will exploit the zIIP capability for portions of eligible workloads. The zIIP will be available on the System z9 mainframe, and its introduction can help increase the value that customers may derive from the System z9 mainframe over previous generations of the IBM mainframe. If you are running z/OS (or z/OS.e) V1.6 or V1.7 and want to use a new IBM System z9 Integrated Information Processor Support (zIIPs), then you must download and install the IBM System z9 Integrated Information Processor Support for z/OS and z/OS.e V1R6/R7 Web deliverable, which is FMID JBB77S9 for



1.6 and JBB772S for 1.7, as well as the service identified in the program directory that comes with the Web deliverable (including the service which is recommended in the appropriate ZOSV1Rn BCPZIIP PSP bucket). IBM DB2 UDB for z/OS V8 with PTFs, is also required for exploitation. Note that for z/OS and z/OS.e V1.8, which are planned to be available September 2006, the web deliverable and PTFs from the BCPZIIP PSP bucket are not needed. (zIIP PTFs will be included in the BCP subset for z/OS V1R8).

There are updates to Omegamon products for zIIP support targeted for general availability. Refer to the zIIP PSP bucket for APAR information. 1. OMEGAMON XE on z/OS 2. OMEGAMON II for MVS v550 * 3. OMEGAMON Base v550 (component of the above products) 4. OMEGAMON XE for DB2 Performance Expert on z/OS v310 5. OMEGAMON XE for DB2 Performance Monitor on z/OS v310 * OMEGAMON II for MVS is a component product of OMEGAMON XE on z/OS, but also a product in its own right. It also contains within it the product called OMEGAMON for MVS (which customers often refer to as "OMEGAMON Classic").

You must also contact your vendors regarding zIIP support. The FMID for the web downloads changes the z/OS release to 1.7.1 for z/OS 1.7 and z/OS 1.6.1 for z/OS 1.6. Check with your ISVs to ensure this will not be a problem.

It is possible to estimate the potential amount of DRDA work which can be redirected to a zIIP prior to installing the required hardware and software. IBM has developed tools which can process RMF and DB2 data to provide this information. In order to do this analysis, please have your IBM account team make a request to IBM Techline for a zIIP estimation analysis. IBM Techline will provide a data collection guide as well as an optional DB2 data reduction tool. The data collection guide asks several questions to allow IBM to do the proper evaluation. Return the completed data collection guide as well as FTP the required RMF data and optional DB2 data created by the DB2 data reduction program to IBM. The data will be analyzed and a report sent to your IBM account team.

Once the proper level of software is installed on the customer machine, RMF and DB2PM will provide additional information which will show the potential for redirecting work to a zIIP. By using the new PROJECTCPU option in SYS1.PARMLIB member IEAOPTxx, this analysis can be done prior to installation of the actual zIIP hardware.

Special note on TCP Segmentation Off-load feature (also called OSA Large Send): The TCP Segmentation Off-load feature is enabled by default if all of the requirements documented in PK02490 are met. Due to the potential for OSAs that are using this feature to experience unrecoverable INOPs (requiring intervention by configuring the affected CHPIDs off-line), it is currently recommended that Segmentation Off-load be disabled. To disable Segmentation Offload, it is recommended that the following maintenance be applied and then code NOSEGMENTATIONOFFLoad on the GLOBALCONFIG statement in the TCPIP PROFILE. Once all of the microcode issues for Segmentation Offload are resolved, a Washington Systems Center Flash will be released advising what the minimum recommended code level will be. Flash 1232599 on the z/OS Communications Server Support web page will also be updated at that time. Go to URL http://www.ibm.com/software/network/commserver/zos/support/ to subscribe to this (and other) updates. APAR/PTF updates were added to 2094DEVICE and 2096DEVICE PSP buckets in the R8, R7 and R6 sections to disable Segmentation Off-load (OSA Large Send.)





z/OS V1.8

z/OS V1.7 plus PTFs

z/OS V1.6 plus PTFs

z/OS V1.5 plus PTFs



Allocation

HCD

EREP

RMF

IOCP

HLASM

SRM

SMF

IOS

DFSMS Comm Server

BCP

Note: z/OS V1.6 (and higher) require 64-bit architecture to IPL (31-bit not allowed)


All functions listed for z/OS V1.4, V1.5 and V1.6Plus

►► Multiple Multiple subchannelsubchannel sets supportsets support►► Wild branch diagnosis improvementWild branch diagnosis improvement►► FICON link incident reportingFICON link incident reporting►► HiperSocketsHiperSockets support of IPv6support of IPv6►► VLAN management enhancements VLAN management enhancements ►► XLC C/C++ Enable ARCH(7)/TUNE(7) compiler optionsXLC C/C++ Enable ARCH(7)/TUNE(7) compiler options►► IBM System z9 Integrated Information Processor (IBM IBM System z9 Integrated Information Processor (IBM zIIPzIIP) Support) Support►► Server Time Protocol (Server Time Protocol (STPSTP))





BCP, HCD, HCM, System Automation for

z/OS

OA13344See Functional STP

PSP Bucket

Server Time Protocol

zIIP Web DeliverableBCP, WLM, RMF,

SDSF, DB2, Omegamon XE (z/OS),

Omegamon II (MVS), Omegamon Base,

Omegamon XE for DB2

FMID(JBB772S)APARs in Functional

ZIIP PSP Bucket


HCDOA11709, OA12570Additional HCD Support and Model S54 Support

In baseN/AFICON link incident reporting

In baseN/AWild branch diagnosis improvement

TCP/IPPK05337VLAN Management enhancementsC/C++PK05323XLC C/C++ Enable ARCH(7)/TUNE(7) compiler options

EREPBCP (IOS)

DFSMS

IR53369OA11862, OA13311

OA13077

Multiple Subchannel Sets

See charts 18, 22 and 28

All PTFs listed for previous z/OS levels (V1.5 and V1.6)See chart 15All Compatibility PTFs from chart 12

CommentsAPARFunctionz/OS and z/OS.e V1.7 Requirements


z/OS V1.7 (z9 EC or z9 BC) or z/OS.e (z9 BC Only) Multiple Subchannel Sets: Multiple Subchannel Sets (MSS) is designed to provide an increased number of subchannels. Two subchannel sets are now available per LCSS and are designed to enable a total of 63.75K subchannels in set-0 and the addition of 64K-1 subchannels in set-1.

With the multiple subchannel set facility, one or two sets of subchannels may be configured to each LCSS where subchannel set 0 (zero) may have from 1 to 63.75K subchannels defined, and subchannel set 1 (one) may have from 1 to (64K-1) subchannels defined. z/OS will allow Parallel Access Volume Alias (PAV-alias) devices in the subchannel set 1 (one). MSS is designed to provide greater I/O device configuration capabilities for large enterprises.

z/OS V1.7 supports the use of a second subchannel set for defining Parallel Access Volumes (PAV) aliases on the z9 EC and z9 BC servers, which provides an additional 64K subchannels. Moving PAV alias definitions to a second subchannel set can allow more devices to be defined. This new function provides relief from the 64K device limit by allowing PAV aliases to be defined without making device numbers unavailable for defining additional devices. EREP support is also provided to include the subchannel number for PAV alias devices.

MSS is exclusive to the z9 EC and z9 BC servers, and is supported by ESCON (CHPID type CNC), by all of the FICON features supported on the z9 (CHPID type FC), by z/OS, z/OS.e, and Linux on System z9.

Wild branch diagnosis improvement: A new hardware function stores the address of the last successful branch instruction on the z9. z/OS (and z/OS.e) V1.7 is designed to include this information in dumps, which can make it easier to find a program that branches to an unexpected location. This can help decrease problem determination time, improve the quality of failure diagnosis, and enhance the probability of first failure fault isolation.



RMF support for more than 16 processors - Report adaptation: RMF support for more than 16 processors in a z/OS image was made available in z/OS V1.6. In z/OS (and z/OS.e) V1.7, improved support is provided for CPU activity and system address space analysis.

FICON link incident reporting is designed to allow an operating system image (without operator intervention) to register for link incident reports improving the ability to capture data for link error analysis. z/OS will display this information on consoles and will also save it in the system log and in LOGREC.

FICON link incident reporting is exclusive to the z9, and is supported by the FICON Express2 and FICON Express features (CHPID type FC), and by z/OS (and z/OS.e).

VLAN management enhancement - support of GVRP for ease of use and simplified management: The OSA-Express2 features now support VLAN prioritization (a component of the IEEE 802.1 standard) to extend support of VLANs to help simplify networking administration and management of VLANs. You may no longer be required to manually enter VLAN IDs at the switch.

Generic Attribute Registration Protocol (GARP) Virtual Local Area Network (VLAN) Registration Protocol, also referred to as GARP VLAN Registration Protocol (GVRP), is an application defined in the IEEE 802.1 standard that allows for the control of IEEE 802.1Q VLANs.

OSA communicates with GVRP-capable (IEEE 802.1Q) switches, registering its VLANs and dynamically updating its table as the VLANs change. VLANs are designed to ease the administration of logical groups of users - they can communicate as if they were on the same LAN. Traffic can be organized by traffic patterns (such as TELNET, FTP, banking transactions) rather than by physical location.

Support of GVRP is exclusive to the z9, is applicable to all of the OSA-Express2 features when in QDIO mode (CHPID type OSD), and is supported by z/OS, z/OS.e, and z/VM. Refer to Software requirements section.

HiperSockets supports IP version 6: Internet Protocol Version 6 (IPv6) support is now being offered for HiperSockets (CHPID type IQD). IPv6 is the protocol designed by the Internet Engineering Task Force (IETF) to replace Internet Protocol Version 4 (IPv4) to help satisfy the demand for additional IP addresses.

IPv6 was introduced to expand the IP address space from 32 bits to 128 bits to enable a greater number of unique IP addresses in support of the proliferation of devices now connecting to the Internet, such as cell phones and PDAs.

This enhancement allows IPv6 communications between LPARs for z/OS TCP/IP stacks and Linux for zSeries TCP/IP stacks. It also expands IPv6 connectivity options between TCP/IP stacks in a sysplex when DYNAMICXCF is configured.

The support of IPv6 on HiperSockets (CHPID type IQD) is exclusive to the z9, and is supported by z/OS, z/OS.e, and z/VM.

C/C++ ARCH(7) and TUNE(7) options: The ARCHITECTURE C/C++ compiler option selects the minimum level of machine architecture on which your program will run. Note that certain features provided by the compiler require a minimum architecture level. ARCH(7) exploits instructions available on the z9 EC and z9 BC servers. The TUNE compiler option allows you to optimize your application for a specific machine architecture within the constraints imposed by the ARCHITECTURE option. The TUNE level must not be lower than the setting in the ARCHITECTURE option. For more information on the ARCHITECTURE and TUNE compiler options refer to the z/OS XL C/C++ User’s Guide.





z/OS V1.8

z/OS V1.7 plus PTFs

z/OS V1.6 plus PTFs

z/OS V1.5 plus PTFs



Note: z/OS V1.6 and higher require 64-bit architecture to IPL (31-bit not allowed)

Allocation

HCD

EREP

RMF

IOCP

HLASM

SRM

SMF

IOS

DFSMS Comm Server

BCP


All functions listed for z/OS V1.4, V1.5, V1.6 and V1.7Plus

►► Support for up to 512 GB of real storage on a single z/OS image Support for up to 512 GB of real storage on a single z/OS image (z9 EC only)(z9 EC only)●● up to 256 GB on IBM up to 256 GB on IBM zSerieszSeries z990 serversz990 servers●● an increase from the prior maximum of 128 GB an increase from the prior maximum of 128 GB

●● Note: 1 GB equals 1 073 741 824 bytesNote: 1 GB equals 1 073 741 824 bytes►► IBM System z9 Integrated Information Processor (IBM IBM System z9 Integrated Information Processor (IBM zIIPzIIP) )

SupportSupport●● Included in z/OS BaseIncluded in z/OS Base●● Recommended PTFs in PSP BucketRecommended PTFs in PSP Bucket





TCP/IPPK02490, PK21685PK26905

OSA Large Send Support

BCP, HCD, HCM, System Automation for

z/OS

OA13344See Functional PSP

Bucket

Server Time Protocol

In BaseBCP, DB2,

Omegamon XE (z/OS), Omegamon II (MVS),

Omegamon Base, Omegamon XE for DB2

N/AAPARs in

Functional ZIIPPSP Bucket


In BaseN/ASupport for up to 512 GB of real storage on a single z/OS image

See charts 18, 22, 28, and 31

All PTFs listed for previous z/OS levels (V1.5, V1.6, and V1.7)



z/OS V1.8 Requirements


z/OS V1.8 (z9 EC or z9 BC) or z/OS.e (z9 BC Only) Support for up to 512 GB of Real Storage on a Single z/OS Image 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 (4,398,046,511,104 bytes) of real memory on a single z/OS image. In z/OS V1.8 it is planned 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, 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.

Preview of OSA Enhancements Preview – when available, OSA Layer 3 VMAC, is planned to be exclusive to z9 EC and z9 BC, will be applicable to the OSA-Express2 features and to the OSA-Express features (Gigabit Ethernet LX and SX, #1364, #1365, #2364, #2365 and 1000BASE-T Ethernet #1366) when configured as CHPID type OSD (QDIO). OSA Layer 3 VMAC is required to exploit the support in z/OS and z/OS.e V1.8. Preview – when available, an enhancement to the QDIO architecture (OSA-Express Network Traffic Analyzer) will be designed to allow trace records to be sent to z/OS. This enhancement is planned to be exclusive to z9 EC and z9 BC, will be applicable to the OSA-Express2 features when configured as CHPID type OSD (QDIO). OSA-Express Network Traffic Analyzer is required to exploit the support in z/OS and z/OS.e V1.8. Preview – When offered on z9 EC and z9 BC, QDIO Diagnostic Synchronization is planned to be applicable to the OSA-Express2 features when configured as CHPID type OSD (QDIO). The z9 EC and z9 BC QDIO Diagnostic Synchronization support is required to exploit the support in z/OS and z/OS.e V1.8.




PSP BucketsThere are 3 types of subsets that you need to know about:1. The hardware buckets

For z9 EC: Upgrade = 2094DEVICE, Subset = 2094/ZOSFor z9 BC: Upgrade = 2096DEVICE, Subset = 2096/ZOS

► The hardware buckets identify: ● Required service for device support or exploiting specific hardware

functions. ● Additional recommended service

2. The software bucketsSubset "BCPZIIP" (Upgrades: ZOSV1R6 & ZOSV1R7)

Contains all “recommended service” for zIIP FMIDs (JBB77S9 for 1.6 , and JBB772S for 1.7)

Subset “ICSFnnnn" (Upgrades: ZOSV1R6 & ZOSV1R7)Contains all “recommended service” for the ICSF FMID HCRnnnn

► The software buckets identify: ● Recommended service to be installed when you install the software● Additional information on installation, documentation, or about the

product 3. The functional buckets

► Identifies the list of Service Recommendations needed to plan for or exploit specific functions (e.g., zAAP or zIIP processors, MIDAW, or STP)


You are instructed to:IBM zIIP Support for z/OS and z/OS.e V1R6/R7 Web Deliverable

z9 EC or z9 BC - zIIP Recommended Service

Used to identify all PTFs zIIP related, even other product exploitation

•Install service from the functional ZIIP PSP bucket

Identifies recommended service (BAU) not necessarily zIIP related

•Install service from the software BCPZIIP PSP bucket

SMP/E RECEIVE ORDERShopzSeries…

Required because service is not included in a web deliverable (BAU)

•Place a service order to obtain PTFs for Web Deliverable

Preventive Service Planning (PSP) Bucket Information It is imperative all the appropriate Preventive Service Planning (PSP) buckets are obtained. In addition to the hardware PSP buckets , the software PSP buckets must also be obtained. IBM recommends using the “Enhanced PSP Tool” to acquire service; or ServiceLink.



If you are skipping generations of processor hardware during your migration to the System z9 processor, then you should go to the PSP Buckets for those generations to ensure that you have all the software requirements installed prior to IPLing z/OS or z/OS.e on the System z9. For example, if you are migrating from a 31-bit-only processor (e.g., 9672 Rx6) to a System z9 BC, then refer to the z900/z800 PSP Bucket (either 2064DEVICE or 2066DEVICE) for the minimum z/OS and z/OS.e requirements to operate in a 64-bit environment, then refer to the z990/z890 PSP Bucket (either 2084DEVICE or 2086DEVICE) for required software support at that level and finally refer to the z9 BC PSP Bucket (2096DEVICE) for the unique z9 BC requirements.

Note: If you are migrating from an old driver level on a z900, z800, z990, or z890 server to System z9, then you may want to refer to the PSP Bucket for that server to ensure that you have the highest level software support required for that level server.

The hardware buckets (2094DEVICE and 2096DEVICE) are structured to separate the minimum support required from support needed to exploit specific functions. To simplify finding the appropriate PSP Buckets, and then identifying which PTFs listed in the PSP bucket need to be installed on your system, you can use the Technical Help Database for Mainframe Preventive Service Planning Buckets (http://www14.software.ibm.com/webapp/set2/psp/srchBroker) and the Enhanced PSP Tool . The web site provides a search capability, as well as pull down lists for types of PSP Buckets. The types currently supported include Processors, z/OS, and Functions. So you can simply select the processor you are preparing for and click ‘Go’. zAAPs and zIIPs are defined as Functions, so identifying PTFs needed to use (exploit) those functions, is just as easy. Just scroll down to the ‘Find the bucket by Type, Category, and Release’ heading, select 'Function' for the Type field, select either ‘ZAAP’ or 'ZIIP' for the Category field, and click Go.

Using the Enhanced PSP Tool will simplify the identification of required service for your specific environment. The tool output presents ‘extract files’. ‘Extract’ files are simply structured lists that identify every PTF from the PSP bucket, for every applicable z/OS release. This output can then be processed by the Enhanced PSP Tool (ePSPt) compare program (also downloadable from that same web site). The compare program will compare the structured list (‘extract’ file) to an SMP/E target zone, and identify any uninstalled service (filtering out service for releases that you don’t have installed). It even will identify if any service has to be RECEIVEd. You can then use SMP/E’s RECEIVE ORDER function (or your favorite service acquisition tool) to obtain the missing service. If desired, you can concatenate several extract files as input to the compare program. For example, you could concatenate the extract files for z990, z9 EC, ICSF, and zIIP; and then compare them to you z/OS V1.6 system to identify ALL PTFs needed for your upgrade in one fell swoop.

PSP Bucket Reference Table

Upgrade Subset Description 2094DEVICE 2094/ZOS

2094Z/VM 2094VSE/ESA

z9 Enterprise Class

2096DEVICE 2096/ZOS 2096Z/VM 2096VSE/ESA

z9 Business Class


z990


z890

ZOSV1R8 BCP ICSF7731

(includes zIIP) ICSF



ZOSV1R7 ICSF7730 ICSF7731 BCPZIIP

ICSF ICSF Enhanced zIIP

ZOSV1R6 ICSF770A ICSF770B ICSF7731 BCPZIIP

ICSF - Secure ICSF – enhanced function ICSF Enhanced BCPZIIP

ZOSV1R5 ICSF770A ICSF - Secure

ICSF770B ICSF – enhanced function

ZOSV1R4 HCD7708 Hardware Configuration Definition (HCD)

HCM1510 Hardware Configuration Manager (HCM)

OSAI400 Open Systems Adapter-Express (OSA/SF)

ICSF7708 Integrated Cryptographic Services ICSF

SSL Cryptographic Services System SSL

BCP7717 BCP77K7

BCP – exploitation BCP Japanese

MSYSOP msys for Operations

ICSF770A ICSF - Secure

ICSF770B ICSF – enhanced function

ZOSGEN General Information

ICKDSF017 EDU1N01 ICKDSF R17 Base

FDU1H07 SMF

FDU1H08 SMF English

FDU1H09 Japanese

CMS0H14 ICKDSF VM V1R17

FDS1H03 ICKDSF Standalone

FDS1HCD ICKDSF Standalone CD-ROM

VDS21NM ICKDSF VSE

Functional PSP Bucket Reference Table

Subset Description MIDAW MIDAW (Modified Indirect Data Address Word) support STP Server Time Protocol (STP) support ZAAP System z Application Assist Processor (zAAP) support ZIIP System z9 Integrated Information Processor (zIIP) support DST2007 Daylight Saving Time Change for 2007 support HYPERPAV IBM System Storage DS8000 series (D/T 2107) HyperPAV support




MigrationConsiderations


z9 EC and z9 BC Migration ConsiderationsCustomer migration (including activation) actions vary depending on z/OS release and existing hardwareIBM System z9 “inherits” migration considerations for z/Architecture and z990/z890► z/Architecture (64-bit)► LPAR ID > x’F’, CHPID Mapping Tool, Sysplex coexistencez/OS and z/OS.e “inherits” migration considerations for z/OS releases► V1.7 HCD Relatively few new migration actions introduced by z9 EC or z9 BC► Lack of connectivity to G5/G6 in parallel sysplex configurations► May see an increase of HSA ● Depends whether the configuration is changed from the current environment

► Shouldn’t exploit new C/C++ compiler options until positive compiled code will run on a z9 server

► Review message automation if z/OS V1.7 and using multiple subchannel sets► If multiple LPARs share the same OSA adaptor in QDIO mode, ensure the

PORTNAME on VTAM's TRLE must match the device name in the DEVICE statement in the TCPIP profile

► zIIP Related ‘Release’ Changes




z990 “Inherited” Migration Considerations

Migration Actions To Be Documented in ► z/OS and z/OS.e Planning for Installation► z/OS Migration

Update CFRM Policies► If Coupling Facility image resides on z990, then LPAR ID (from HMC Image Profile) is

used in CFRM policy► In order to use an LPAR ID > 15 (X'F'), z990 Compatibility (or Exploitation) code is

required on all systems in the sysplex► Use SETXCF START,POLICY,TYPE=CFRM command to make the updated policy active

Update Automation for new and changed messages► Several messages and command output updated for 2 digit LPAR IDs

Notify those affected by changed command outputUpdate PARMLIB Members

► IPCS Support - new ICSF member, CSFIPCSP► With Exploitation, IEASYSxx - the CMB= parameter is now ignored

● May affect user and vendor programs● IEAOPTxx ECMB=NO NOT supported in z/OS V1.7 and higher

► With Exploitation, IEASYSxx - you may need to increase (by 1) the value of MAXCAD.► With Exploitation, SMFPRMxx - the description of the serial number in the SID

parameter changed when running on a z990.Perform Miscellaneous Migration actions

► Rebuild Standalone Dump► OSA/SF new GUI requires Java 1.1.2 help files and Java 1.4 run-time library loaded on

the workstation

z990 “Inherited” Migration Consideration Migration to z9 EC (or z9 BC) has as its basis, the migration to z990 and z890, which in turn had as its basis a migration to z900 and z800. If you are migrating to a z9 from a z990 or z890 (and have performed the migration actions associated with z990 or z890), then you have fewer migration actions than those that are coming from servers older than z990 or z890 and have not yet performed the migration actions associated with z990 or z890.

It is important to note that you can migrate directly to z9 EC or z9 BC without going through to intermediate servers, but you still do need to ensure that any migration considerations are satisfied for those servers that you "skipped".

Detailed information on ALL the “inherited” migration considerations is documented in z/OS Migration. These “inherited” migration considerations include:

• Use of z/OS features, web deliverables, as well as PTFs to provide z990 (or z890) (and coexistence support). The combination of deliverables vary by release.

• Migrating to z/Architecture (64-bit) mode • Greater than x’F’ LPAR IDs and change in CPU ID. This affects

IBM and ISV products, e.g., requirement for ICKDSF R17 CFRM Policies (if Coupling Facility is on a LPAR whose ID is greater than x’F’ messages (now include 2 digit LPAR IDs) command output

• PARMLIB changes Use of ECMB (and IEAOPTxx option to revert back to CMB for z/OS V1.6 and lower releases)

Possible need to increase MAXCAD keyword in IEASYSxx




z/OS V1.7: HCD

For z/OS releases which have HCD FMID HCS7708 installed, they can:► Define a 2094 without subchannel set support► The 2094 definition is restricted to subchannel set 0 (zero)► Requires APAR OA07875

Base z/OS V1R4 systems► without the z990 Compatibility feature and z990 Exploitation Support

feature● Cannot read from or dynamically activate a V5 IODF from that z/OS

V1R4 system● To read from or dynamically activate a V5 IODF from a base z/OS

V1R4 system requires either: – V1R4 z990 Exploitation feature and PTFs for APARs OA07875– STEPLIB to z/OS V1.7 HCD libraries

● Can IPL if BCP Allocation APAR OA08197 is installed

HCD

z/OS V1.7 HCD Migration Consideration A new IODF level, called V5, is introduced in z/OS V1.7. This new IODF level reduces the size of the IODF and improves the processing performance of large configurations.

To read from, IPL with, and dynamically activate an IODF at the V5 level, the PTFs for coexistence APARs OA07875 and OA08197 are required on back-level systems. If you attempt to IPL with a V5 IODF from a back-level z/OS system that does not have the PTF for APAR OA08197 installed, a wait state occurs. The coexistence PTF for APAR OA07875 allows you to view and dynamically activate the V5 IODF, but does not allow you to update the V5 IODF from back-level systems. Once the IODF has been upgraded to V5, the z/OS V1.7 HCD libraries must be used to process updates to it. (A STEPLIB or JOBLIB from a back-level system to the z/OS V1.7 HCD libraries, or to a copy of the libraries, is acceptable.)

Note: APAR OA07875 is available for z/OS V1.4 systems that have the z/OS V1R4 z990 Compatibility Support feature installed (that is, HCD FMID HCS7708). z/OS V1.4 HCD without the z990 Compatibility Support feature (that is, HCD FMID HCS6091) does not have an applicable coexistence PTF. (Tip: HCD FMID HCS7708 shows up as "z/OS V1.4 HCD" on its primary panel and is described as "z/OS V1.4 HCD" in the documentation. HCD FMID HCS6091 shows up as "OS/390 Release 9 HCD" on its primary panel.)

If you are running z/OS V1.4 without the z990 Compatibility Support feature, an additional coexistence and fallback requirement applies: you cannot read or dynamically activate a V5 IODF from the z/OS V1.4 system. If you want to read or dynamically activate a V5 IODF from the z/OS V1.4 system, install the z/OS V1.4 z990 Compatibility Support feature (or its replacement, the z/OS V1.4 z990 Exploitation Support feature,) and install the PTF for APAR OA07875.

Other methods to satisfy this coexistence requirement are: • Do not share the IODF. Use EXPORT/IMPORT or COPY to create a second IODF. • Delay making IODF updates from the z/OS V1R7 system until all systems are at the level of the z/OS

V1.4 z990 Compatibility Support feature (FMID HCS7708) or later.




“New” System z9 Migration Considerations

Acquisition and installation of requisite service, web deliverables, and features.► Differs depending on z/OS release/service level and existing server

Ensure software and hardware vendors support z9 EC or z9 BC► If planning to use zIIPs, verify that vendors can support the z/OS Web Deliverable

If you add devices, subchannels, or LPARs, you will require larger HSA. ► Run HSA Estimator tool available from IBM Resource Link

Required actions to enable (or disable) function► HCD or HMC definitions/activation

z/VM Guest Considerations► Some functions unavailable when running as a guest

Review message automation if z/OS V1.7 and using multiple subchannel sets► A number of messages were changed to provide a subchannel set identifier

● For example, IOS159I – to identify subchannel set 1, a new message IOS1159I was created

If multiple LPARs share the same OSA adaptor in QDIO mode,► Ensure the PORTNAME on VTAM's TRLE must match the device name in the DEVICE

statement in the TCPIP profile and ► Ensure that they all are the same (including case) in every instances of TCPIP/VTAM

that share the same OSA adaptorClient (ICSF) CKDS first initialized on a z990/890 or later, will not be usable on a z900/800 or earlier server without migrating the records to a CCF-initialized CKDS

New


zIIP Related ‘Release’ ChangesFMID JBB77S9 provides the support in z/OS 1.6 for zIIP. It changes the following fields from their values at the levels provided by FMID HBB7709(the base FMID for z/OS 1.6):► CVTPRODN from SP7.0.6 to SP7.1.6► ECVTPMOD from 00 to 01 ► ECVTPSEQ from x'01010600' to x'01010601' ► support for zIIP also introduces the CVTZIIP bit in CVTOSLV4 (CVTZIIP EQU X'02' zIIP

routine is present)FMID JBB772S provides the support in z/OS 1.7 for zIIP. It changes the following fields from their values at the levels provided by FMID HBB7720(the base FMID for z/OS 1.7):► CVTPRODN from SP7.0.7 to SP7.1.7► ECVTPMOD from 00 to 01 ► ECVTPSEQ from x'01010700' to x'01010701' ► support for zIIP also introduces the CVTZIIP bit in CVTOSLV4 (CVTZIIP EQU X'02' zIIP

routine is present)After zIIP support is installed the value returned from the REXXMVSVAR("SYSOPSYS") function will be:► "z/OS 01.06.01 JBB77S9" on z/OS 1.6. ► "z/OS 01.07.01 JBB772S" on z/OS 1.7




Supported

z9 Multisystem/Sysplex Considerations

Only service-supported releases can coexist in the same sysplex►The following releases will NOT be supported in a

sysplex with a z/OS or CF image running on a z9 server● OS/390 2.10● z/OS V1.1● z/OS V1.2● z/OS V1.3● z/OS.e V1.3




Multisystem/Sysplex Migration Considerations

“Inherited (z990)” Migration Considerations► Same as z990 GA 1

● LPAR ID > x’F’ requires compatibility support● More than 15 LPARs defined requires CFCC code● ICKDSF 17 is required to be installed on non-z890 and non-

z990 systems sharing DASD with a z890 or z990– Even z/VM systems– Can be installed as part of Compatibility (or

Exploitation Support) or as Program Product (5655-257)

● HCD compatibility code (FMID) is required to be installed on non-z990 systems in the same JES plex (If HCD batch jobs routed to that system)

“New” System z9 Migration Considerations► CF Links and lack of connectivity to G5/G6► ICB-2 and ISC-3 Compatibility Mode Links no longer supported► CF Structure size (if changing CF LEVELs)

New

“Inherited” (z990) Multisystem/Sysplex Migration Considerations The same restrictions that are present on your z/OS release level on z990 or z890 are present on the z9 EC or z9 BC. For instance, support for LPAR ID of greater than 15 (x'F') requires at least the z/OS V1.4 z990 Exploitation support. The z990 coexistence and migration requirements, including restrictions, are documented in z/OS Migration.

New Migration Considerations The following changes introduced with z9 servers could affect your environment: • Token ring: The z990 and z890 are the last System z servers to offer token ring adapter features on the

hardware management consoles (HMCs), Support Elements (SEs), and Trusted Key Entry (TKE) workstations. Thus: – Token ring is not available as a feature on the z9 HMC. Current HMCs with token ring may be carried forward to a z9 during an upgrade from a z990 or z900. – Token ring is not available as a feature on the z9 Support Element (SE) or Trusted Key Entry (TKE) workstation. Token ring is not offered as a feature on the z9 EC or z9 BC and cannot be carried forward to a z9 during an upgrade from a z990 or z900. – The OSA-Express Token Ring feature is not supported on the z9. Token ring is not offered as a feature on the z9 EC or z9 BC and cannot be carried forward to a z9 during an upgrade from a z990 or z900.

• HMC: The z990 and z890 are the last System z servers on which the hardware management console (HMC) is open. Starting with the z9 EC, the HMC is for the exclusive use of the HMC application. Customer applications cannot reside on the HMC. The ESCON Directory and Sysplex Timer applications cannot reside on the HMC. TCP/IP is the only supported communication protocol. The HMC supports z9 ECs and z9 BCs. It can also be used to support z990, z890, z900, z800, G5, G6, and Multiprise 3000 servers. They must be upgraded to a new AROM level.

• ICB-2s and ISC-3s in compatibility mode: The z990 and z890 are the last System z servers to support Integrated Cluster Bus-2 (ICB-2) and InterSystem Channel-3 (ISC-3) compatibility mode links. The z9 EC or z9 BC does not support them. If you have ICB-2 or ISC-3 compatibility mode links defined, convert them to a supported link technology.




CF Links and lack of connectivity to G5/G6If you have a CF image on a z9 EC or z9 BC,

► You cannot connect that CF image to any G5/G6 z/OS senders (or for duplexing, to a G5/G6 CF).

► Having a z9 CF, therefore, introduces coexistence issues if there are any G5/G6 servers participating in that sysplex.

► You need to start thinking about removing any existing G5/G6 images in the sysplex

If you have a CF image on a G5/G6,► You cannot connect that CF to any z9 z/OS senders (or for duplexing, to a

CF on a z9 EC or z9 BC). ► Having a G5/G6 CF, therefore, introduces coexistence issues if there are

any z9 servers participating in that sysplex.► You need to start thinking about migrating off of the G5/G6 CFs to newer

technologyIf you have z/OS images running on a G5/G6 server AND a z9 server,

► They can coexist in the same sysplex as long as their CFs are not on G5/G6 or z9 servers (e.g., on a z900/z800/z990/z890), ● These "intermediate" CFs can connect to both the old (G5/G6) and the

new (z9) technology servers, so they can provide a "bridge" that allows them to peacefully coexist in a sysplex as described above.

IC, ICB, and ISC-3 on the z9 EC and z9 BC: The z9 EC and z9 BC supports Internal Coupling channels (ICs), Integrated Cluster Bus-3 (ICB-3), ICB-4, and InterSystem Channel-3 (ISC-3) (peer mode) links for passing information back and forth in a Parallel Sysplex environment.

• ICs are used for internal communication between Coupling Facilities defined in LPARs and z/OS images on the same server. Up to a maximum of 32 can be defined per server.

• ICBs are used for server-to-server communication over short distances, using 10 meter (33 feet) copper cables, of which 3 meters (10 feet) is used for internal routing and strain relief.

o Integrated Cluster Bus-3 (ICB-3) (#0993) supports a link data rate of 1 gigabyte per second and is used to connect z9s to z900s and z800s up to a maximum of 16 links.

o ICB-4 (#3993) supports a link data rate of 2 gigabytes per second and is used to connect z9s to z9s, z990s, and z890s up to a maximum of 16 links.

• InterSystem Channel-3s (ISC-3s) (#0217, #0218, #0219) supports a link data rate of 2 gigabits per second and is used for server-to-server communication at distances up to 10 km (6.2 miles) using 9 micron single mode fiber optic cables. ISC-3s are supported exclusively in peer mode (CHPID type CFP).

The maximum number of external Coupling links combined (ICs, ICB-3s, ICB-4s, and active ISC-3 links) cannot exceed 64 per server.

ICB-2 links no longer supported: ICB-2 links were used to support Parallel Sysplex connectivity between 9672 G5 and G6 servers and z990, z900, and z800 servers. ICB-2 links are no longer supported.

ISC-3 links in compatibility mode no longer supported: Attachment of ISC-3 links on the z9 EC and z9 BC to HiPerLinks (ISC-2) on G5 and G6 servers is not supported. ISC-3 compatibility mode is not supported on the z9 EC or z9 BC (CHPID types CFS and CFR).



44 February 2007© 2007 IBM Corporation IBM Systems23

© 2003 IBM CorporationNeed to start thinking about removing any existing G5/G6 CF or z/OS images from the sysplex!

z/OS1.4

z/OS1.4 Exploit

z/OS1.4 Compat

ICFLPAR id <=

F

z/OS1.4

Exploit

z/OS1.7

z/OS1.4

Compat

LCSS0 LCSS1

z9 EC or z9 BCG5, G6z/OS1.5

z/OS1.5

z/OS1.6

z9CF

Connecting a z9 CF image to any G5/G6 z/OS senders is NOT supported

z/OS1.4

z/OS1.4 Exploit

z/OS1.4 Compat

G5, G6z/OS1.5

ICF

ICFLPAR id <=

F

z/OS1.4

Exploit

z/OS1.7

z/OS1.4

Compat

LCSS0 LCSS1

z9 EC or z9 BCz/OS1.5

z/OS1.6

Connecting a G5/G6 CF image for duplexing to a z9 CF is NOT supported

Parallel Sysplex coexistence with a z9 CF

9674CF


© 2003 IBM Corporation

Need to start thinking about removing any existing G5/G6 CFs in the sysplex

z/OS1.4

z/OS1.4 Exploit

z/OS1.4 Compat ICF

LPAR

z/OS1.4

Exploit

z/OS1.7

z/OS1.4

Compat

LCSS0 LCSS1

z9 EC or z9 BCG5, G6z/OS1.5

z/OS1.5

z/OS1.6

Connecting a G5/G6 CF image to any z9 z/OS senders is NOT supported

Parallel Sysplex coexistence with a G5/G6 CF

z/OS1.4

z/OS1.4 Exploit

z/OS1.4 Compat

G5, G6z/OS1.5

ICFICF

LPAR id <= F

z/OS1.4

Exploit

z/OS1.7

z/OS1.4

Compat

LCSS0 LCSS1


z/OS1.6

Connecting a G5/G6 CF image for duplexing to a z9 CF is NOT supported

9674CF

z9CF




© 2003 IBM Corporation

z/OS1.4

z/OS1.4 Exploit

z/OS1.4 Compat

G5, G6z/OS1.5

z/OS1.4

Exploit

z/OS1.7

z/OS1.4

Compat

LCSS0 LCSS1


z/OS1.6

G5/G6 z/OS senders CAN be in the same sysplex with z9 senders if they connect with CFs on z900, z800, z890 or z990 servers!

z/OS1.7

z900,z800,z990,z890

ICFLPAR

CF

z900/z800

–These "intermediate" CFs can connect to both the old (G5/G6) and the new (z9) technology machines–They can provide a "bridge" allowing them to coexist in a sysplex

Parallel Sysplex coexistence with a G5/G6 and z9 Senders


Parallel Sysplex coexistence with a G5/G6 and z9 Senders

If a customer upgraded from a G5/G6 to z900 (or z990), but didn’t upgrade their link technology (i.e., still use ICB-2 links):

► They will have to upgrade their links if they upgrade to a z9 server. ● While ICB-2 were supported on prior servers, they are NOT

supported on z9● Customers with ICB-2 links need to start thinking about

upgrading their link technology► Similar exposure with ISC-3 Compatibility mode links




Coupling Facility Control Code (CFCC)

Structure size (and CF storage) increase when moving from► CF Level 11 to CF Level 14 (or 12/13)► CF Level 12 or CF Level 13 to CF Level 14

CFCC level 14 does not change on a z9 EC or z9 BC

Recommendations have not changed for z9 for CP designations► Still Workload volume dependent► Recommendation still to use dedicated CPs for production

CF/ICFs

CF structure sizes Generally, when you change Coupling Facility Control Code (CFCC) levels, the Coupling Facility structure sizes may change. z9 EC and z9 BC servers are delivered with CFCC Level 14. If as part of your z9 migration, you will change CFCC levels (either by placing a CF on the z9 EC or z9 BC, or moving the CF to a z990 or z890 at a higher CFCC level, then you may have larger structure sizes than you did previously. If your CFCC levels are identical, then there are no expected changes in structure sizes when moving from a previous server to a z9.




z/OS XL C/C++ Migration ConsiderationAs of z/OS V1.7, the z/OS C/C++ compiler has been renamed to z/OS XL C/C++. C/C++ ARCH(7) and TUNE(7) options: ► The ARCHITECTURE C/C++ compiler option selects the minimum level of

machine architecture on which your program will run. ► Note that certain features provided by the compiler require a minimum

architecture level. ARCH(7) exploits instructions available on z9. ► The TUNE compiler option allows you to optimize your application for a

specific machine architecture within the constraints imposed by the ARCHITECTURE option.

► The TUNE level must not be lower than the setting in the ARCHITECTURE option.

► For more information on the ARCHITECTURE and TUNE compiler options refer to the z/OS XL C/C++ User’s Guide.

Exploitation Restriction:► Once you exploit the C/C++ ARCH(7) or TUNE(7) option, those programs may

only run on z9 servers, or an operation exception will result. ► This is a consideration for programs that may run on different level servers

during development, test, production, and during fallback or disaster recovery.




Migration Paths


General Recommendations and Considerations

z9 based on existing zSeries technology► z/Architecture (z900/z800)► Multiple Logical Channel Subsystems (z990/z890)

z9 capabilities differ depending on z/OS release► Support provided on z/OS and z/OS.e V1.4 with z990 compatibility support

(and higher)► NO SUPPORT provided for z/OSor z/OS.e V1.4 Base ► z/OS.e ONLY supported on z9 BC (z800 or z890)

Don’t migrate software releases and hardware at the same time

Keep members of the sysplex at the same software level other than during brief migration periods.

Review z9 restrictions and migration considerations prior to creating upgrade plan




Typical z/OS V1.4 Migration Paths(from G5, G6 or MP3000)

G5/G6MP3000

z/OS V1.431-bit

G5/G6MP3000

z/OS V1.431-bit

w/z990 Exploitation

z990 and z890 Enhancements to

Cryptographic Support web deliverable

z/OS V1.4 w/z990 Exploitation64-bit

z9Service from PSP Buckets

Notes:1. z/OS V1.4 z990 Compatibility Support and

Exploitation features are no longer orderable, but the code is downloadable from the z/OS download page

2. The z990 Cryptographic Support web deliverable is no longer downloadable

6 month fallback capabilitywith the Bimodal Migration Accommodation

z9

z/OS V1.4 w/z990 Exploitation31-bit

Service

supp

ort fo

r z/O

S V1.4

is

plann

ed to

be w

ithdra

wn Marc

h 200

7

If your current server is a G5, G6, or Multiprise 3000 and you are running z/OS V1.4 without the z990 Compatibility Support feature installed If you have z/OS V1.4 installed but you don’t have the z/OS V1.4 z990 Compatibility Support feature installed, you must upgrade your z/OS V1.4 system to include the z990 support because you do not meet the minimum requirement for the z9. You must also perform a migration to z/Architecture. Your migration steps are:

1. Upgrade your z/OS V1.4 system with the following: • Either of the z990 support features: the z/OS V1R4 z990 Compatibility Support feature or the

z/OS V1R4 z990 Exploitation Support feature. The compatibility support has been replaced by the exploitation support, but still can be used if you have it. Neither feature are still orderable, but you can still acquire the exploitation support code by downloading it from the z/OS Download page.

• The PTFs in the following PSP buckets: o The z9 EC PSP bucket: upgrade 2094DEVICE, subset 2094/ZOS, or the z9 BC PSP bucket:

upgrade 2096DEVICE, subset 2096/ZOS o The z990 PSP bucket: upgrade 2084DEVICE, subset 2084/ZOS o The z900 PSP bucket: upgrade 2064DEVICE, subset 2064/ZOS o The software PSP bucket identified in the program directory that comes with your deliverable.

2. If you require Crypto Express2 compatibility support when a Crypto Express2 PCI-X adapter is configured as a coprocessor on the z9, install the z990 Cryptographic Support Web deliverable (which has FMID HCR770A and is no longer downloadable) or its replacement, the z990 and z890 Enhancements to Cryptographic Support Web deliverable (which has FMID HCR770B). In addition, install the PTFs listed in the hardware PSP bucket (either 2094DEVICE or 2096DEVICE), as well as the PTFs identified in the program directory that comes with the Web deliverable and the PTFs that are recommended in the appropriate ICSF PSP bucket.

3. Install the z/OS V1R2/3/4 Bimodal Migration Accommodation to allow your system to stay in ESA/390 mode (for up to six months) while you complete your hardware migration.



4. Upgrade your hardware to a z9. Specify ARCHLVL 1 in your LOADxx parmlib member to allow your system to remain in ESA/390 mode until your hardware migration is complete, and you are ready to do your z/Architecture migration. When using the z/OS V1R2/3/4 Bimodal Migration Accommodation, you can run in ESA/390 mode for six months for each z/OS license starting from the registration of a z/OS license to a z/Architecture-capable server.

5. Migrate to z/Architecture mode by first specifying ARCHLVL 2 in your LOADxx parmlib member, and then by following the z/Architecture migration instructions in z/OS Migration. When your migration to z/Architecture is complete, remove your ARCHLVL specification and allow ARCHLVL to default to 2.

If your current server is a G5, G6, or Multiprise 3000 and you are running z/OS V1.4 with either the z990 Compatibility Support feature or z990 Exploitation feature installed Your z/OS level is acceptable for a migration to z9, however, you must include a migration to z/Architecture as part of your migration to z9 EC or z9 BC. Your migration steps for this scenario are:

1. Ensure that you have installed the required service from the following PSP Buckets: • The z9 EC PSP bucket: upgrade 2094DEVICE, subset 2094/ZOS, or the z9 BC PSP bucket: upgrade

2096DEVICE, subset 2096/ZOS • The z990 PSP bucket: upgrade 2084DEVICE, subset 2084/ZOS • The z900 PSP bucket: upgrade 2064DEVICE, subset 2064/ZOS • The software PSP bucket identified in the program directory that comes with your deliverable.


3. Install the z/OS V1R2/3/4 Bimodal Migration Accommodation to allow your system to stay in ESA/390 mode (for up to six months) while you complete your hardware migration.

4. Upgrade your hardware to a z9. Specify ARCHLVL 1 in your LOADxx parmlib member to allow your system to remain in ESA/390 mode until your hardware migration is complete, and you are ready to do your z/Architecture migration. When using the z/OS V1R2/3/4 Bimodal Migration Accommodation, you can run in ESA/390 mode for six months for each z/OS license starting from the registration of a z/OS license to a z/Architecture-capable server.

5. Migrate to z/Architecture mode by first specifying ARCHLVL 2 in your LOADxx parmlib member, and then by following the z/Architecture migration instructions in z/OS Migration. When your migration to z/Architecture is complete, remove your ARCHLVL specification and allow ARCHLVL to default to 2.

Reminder: For z/OS V1.4 customers it is time to move ahead! End of service for these releases is planned for March 31, 2007. We encourage you to move to z/OS V1.7! If you're on z/OS V1.4, z/OS V1.7 is the last release you can migrate to in a single step.




Typical z/OS or z/OS.e V1.4 Migration Paths(from z800, z900, z890 or z990)



z/OS or z/OS.e V1.4 w/z990 Exploitation64-bit


Notes:1. z/OS V1.4 z990 Compatibility Support and Exploitation features are no longer orderable,

but the code is downloadable from the z/OS download page

2. z/OS.e V1.4 z990 Coexistence support feature is no longer orderable

3. z/OS.e with either the z990 Coexistence or z990 Coexistence Update feature is NOT supported on the z9 EC (it is only supported on z9 BC, z800 and z890 servers)

4. The z990 Cryptographic Support web deliverable is no longer downloadable

z800z900

z/OS or z/OS.eV1.4

64-bit

z/OS or z/OS.e V1.4

64-bitw/z990

Exploitation

z890z990

Service

supp

ort fo

r z/O

S V1.4

is

plann

ed to

be w

ithdra

wn Marc

h 200

7

If your current server is a z800 or z900 and you are running z/OS V1.4 without the z990 Compatibility Support feature (or running z/OS.e V1.4 without the z990 Coexistence support feature) installed If you have z/OS V1.4 installed but you don’t have the z/OS V1.4 z990 Compatibility Support feature installed, or you have z/OS.e V1.4 but you don’t have the z/OS.e V1.4 z990 Coexistence feature installed (and you are migrating to a z9 BC server), you must upgrade your z/OS (or z/OS.e) V1.4 system to include the z990 support because you do not meet the minimum requirement for the z9. You do not need to perform a z/Architecture migration; it is assumed that you completed your migration to z/Architecture after you migrated to the z900 or z800. Your migration steps are:

1. Upgrade your system with the following: • For z/OS, install either of the z990 support features: the z/OS V1R4 z990 Compatibility Support

feature or the z/OS V1R4 z990 Exploitation Support feature. The compatibility support has been replaced by the exploitation support, but still can be used if you have it. Neither feature are still orderable, but you can still acquire the exploitation support code by downloading it from the z/OS Download page.

• For z/OS.e (for a z9 BC server), install either of the z990 support features: the z/OS.e V1.4 z990 Coexistence feature or the z/OS.e V1.4 z990 Coexistence Update feature. The former is no longer orderable and has been replaced by the latter, but it can be used if you have it. The coexistence support has been replaced by the coexistence update support, but still can be used if you have it. Neither feature are still orderable, but you can still acquire the exploitation support code by downloading it from the z/OS Download page.

• The PTFs in the following PSP buckets: o The z9 EC PSP bucket: upgrade 2094DEVICE, subset 2094/ZOS, or the z9 BC PSP bucket:

upgrade 2096DEVICE, subset 2096/ZOS o The z990 PSP bucket: upgrade 2084DEVICE, subset 2084/ZOS o The software PSP bucket identified in the program directory that comes with your deliverable.




3. Upgrade your hardware to a z9.

If your current server is a z800 or z900 and you are running z/OS V1.4 with the z990 Compatibility Support feature (or running z/OS.e V1.4 with the z990 Coexistence support feature) Your operating system level is acceptable for a migration to z9, you do not need to perform a z/Architecture migration, as it is assumed that your migration to z/Architecture was completed after you migrated to z800, z900, z890, or z990. Your migration steps for this scenario are:


2096DEVICE, subset 2096/ZOS • The z990 PSP bucket: upgrade 2084DEVICE, subset 2084/ZOS • The software PSP bucket identified in the program directory that comes with your deliverable.


3. Upgrade your hardware to a z9. Note: z/OS.e is NOT supported on the z9 EC (it is only supported on z9 BC, z800 and z890 servers).

Reminder: For z/OS V1.4 customers it is time to move ahead! End of service for these releases is planned for March 31, 2007. We encourage you to move to z/OS V1.7 now! If you're on z/OS V1.4, z/OS V1.7 is the last release you can migrate to in a single step.




Typical z/OS or z/OS.e V1.5 Migration Paths

z/OS or z/OS.e V1.5

64-bit

zSeries

G5/G6MP3000

z/OS V1.531-bit



Notes:1. The z990 Cryptographic Support web deliverable is no longer

downloadable2. z/OS.e is NOT supported on the z9 EC (it is only supported on z9

BC, z800 and z890 servers)3. When migrating from a G5, G6 or MP3000, you will also change

architecture modes (from ESA/390 31-bit to z/Architecture 64-bit)


z/OS or z/OS.eV1.5

64-bit

Service

supp

ort fo

r z/O

S V1.5

is

plann

ed to

be w

ithdra

wn Marc

h 200

7

If your current server is a G5, G6, or Multiprise 3000 and you are running z/OS V1.5 Your z/OS level is acceptable for a migration to z9, however, you must include a migration to z/Architecture as part of your migration to z9 EC or z9 BC without the Bimodal Migration Accommodation. The Bimodal Migration Accommodation is not available on z/OS V1.5. Therefore, you must perform a hardware first migration, which will include a migration to z/Architecture as part of the migration to z9. Your migration steps for this scenario are:


2096DEVICE, subset 2096/ZOS • The z990 PSP bucket: upgrade 2084DEVICE, subset 2084/ZOS • The z900 PSP bucket: upgrade 2064DEVICE, subset 2064/ZOS • The software PSP bucket identified in the program directory that comes with your deliverable.


3. Upgrade your hardware to a z9 and migrate to z/Architecture mode concurrently. Follow the z/Architecture migration instructions in z/OS Migration.

If your current server is a z800, z900, z990, or z890 and you are running z/OS or z/OS.e V1.5 Your operating system level is acceptable for a migration to z9, you do not need to perform a z/Architecture migration, since V1.5 must run in z/Architecture mode on z800, z900, z890, or z990 servers. Your migration steps for this scenario are:




2096DEVICE, subset 2096/ZOS • The z990 PSP bucket: upgrade 2084DEVICE, subset 2084/ZOS (if not already on a z990 or z890) • The software PSP bucket identified in the program directory that comes with your deliverable.


3. Upgrade your hardware to a z9. Note: z/OS.e is NOT supported on the z9 EC (it is only supported on z9 BC, z800 and z890 servers).

Reminder: For z/OS V1.4 and V1.5 customers it is time to move ahead! End of service for these releases is planned for March 31, 2007. We encourage you to move to z/OS V1.7 or z/OS V1.8 now! If you're on z/OS V1.5, z/OS V1.8 is the last release you can migrate to in a single step.




z/OS or z/OS.eV1.6

64-bit

z9

Typical z/OS and z/OS.e V1.6 Migration Paths

z/OS or z/OS.e V1.6

64-bit

zSeries

Notes:1. If you require Crypto Express2 compatibility support when a Crypto Express2 PCI-X adapter is

configured as a coprocessor on the z9, you must have minimally the PTFs listed in the PSP bucket installed.

2. If you require enhancements to CP Assist for Cryptographic Function (CPACF) (which are AES, PRNG, SHA-256), or if you require Crypto Express2 exploitation when a Crypto Express2 PCI-X adapter is configured as an accelerator or a coprocessor on the z9, you must minimally have installed the Cryptographic Support for z/OS V1R6/R7 Web deliverable.

3. If you require support for support for Remote Key Loading for ATMs and point of sale devices, and implementation of ISO 16609 CBC Mode TDES MAC you must install the Enhancements to Cryptographic Support for z/OS V1R6/7 and z/OS.e V1R6/7 Web Deliverable

4. The ICSF 64-bit Virtual Support for Z/OS V1.6 and z/OS.e V1.6 web deliverable is no longer downloadable

5. z/OS.e is NOT supported on the z9 EC (it is only supported on z9 BC, z800 and z890 servers)

Cryptographic Support for z/OS V1.6/V1.7 web

deliverable

Service from PSP Buckets

PSP Bucket identifies minimal list of PTFs and SW needed to exploit functions.

Enhancements to Cryptographic Support for z/OS V1R6/R7 and z/OS.e V1R6/R7 Web Deliverable

IBM zIIP Support for z/OS and z/OS.eV1R6/R7 Web Deliverable

•Points to ICSF and zIIPweb deliverable•Points to ZIIP Functional PSP Bucket




2. If you require Crypto Express2 compatibility support when a Crypto Express2 PCI-X adapter is configured as a coprocessor on the z9, install the PTFs listed in the PSP buckets. PTFs are also available if the z990 and z890 Enhancements to Cryptographic Support Web deliverable on z/OS V1R6, or the ICSF 64-bit Virtual Support for z/OS V1R6 and z/OS.e V1R6 Web deliverable, is installed.

3. If you want to exploit either of the following cryptographic functions, you must install a Web deliverable and PTFs: Enhancements to CP Assist for Cryptographic Functions (CPACF) on the z9. (The enhancements are

support for the Advanced Encryption Standard (AES) for 128-bit keys, Secure Hash Algorithm-256 (SHA-256), and Pseudo Random Number Generation (PRNG).)

Crypto Express2 exploitation when a Crypto Express2 PCI-X adapter is configured as an accelerator or a coprocessor on the z9. The Web deliverable is Cryptographic Support for z/OS V1R6/R7 (which has FMID HCR7730) or its follow-on, Enhancements to Cryptographic Support for z/OS and z/OS.e V1R6/R7 (which has FMID HCR7731). The PTFs are those identified in the program directory that comes with the Web deliverable as well as the PTFs that are recommended in the appropriate ICSF PSP bucket. Note that these Web deliverables also provide support for callers running in 64-bit addressing mode.



4. If you plan to exploit Remote Key Loading for ATMs and point of sale (POS) devices, or will implement ISO 16609 CBC Mode TDES MAC, download and install the Enhancements to Cryptographic Support for z/OS and z/OS.e V1R6/R7 Web deliverable (which has FMID HCR7731), as well as the PTFs identified in the program directory that comes with the Web deliverable and the PTFs that are recommended in the appropriate ICSF PSP bucket.

5. If you plan to use IBM System z9 Integrated Information Processor (zIIP) support, download and install the IBM zIIP Support for z/OS and z/OS.e V1R6/R7 Web deliverable (which is FMID JBB77S9 for z/OS V1R6), as well as these PTFs: The PTFs identified in the program directory that comes with the Web deliverable The PTFs identified in the appropriate ZOSV1R6 BCPZIIP PSP bucket The PTFs identified in the ZIIP functional PSP bucket

Note: DB2 Universal Database for z/OS V8 (5625-DB2) with PTFs is also required for exploitation. The DB2 PTFs are included in the functional PSP bucket (and the hardware PSP Bucket)

6. Upgrade your hardware to a z9. If you are migrating from a z900 or z800 server, see “Migrate to a z990 or z890 server” in z/OS Migration for z990 and z890 migration considerations that you must also satisfy.

Note: z/OS.e is NOT supported on the z9 EC (it is only supported on z9 BC, z800 and z890 servers).




z/OS or z/OS.eV1.7

64-bit

z9

Typical z/OS or z/OS.e V1.7 Migration Paths

z/OS or z/OS.e V1.7

64-bit

zSeries

Cryptographic Support for z/OS V1.6/V1.7 web

deliverable

Service from PSP Buckets

Notes:1. If you require Crypto Express2 compatibility support when a Crypto Express2 PCI-X adapter is

configured as a coprocessor on the z9, you must have minimally the PTFs listed in the PSP bucket installed.

2. If you require enhancements to CP Assist for Cryptographic Function (CPACF) (which are AES, PRNG, SHA-256), or if you require Crypto Express2 exploitation when a Crypto Express2 PCI-X adapter is configured as an accelerator or a coprocessor on the z9, you must minimally have installed the Cryptographic Support for z/OS V1R6/R7 Web deliverable.

3. If you require support for support for Remote Key Loading for ATMs and point of sale devices, and implementation of ISO 16609 CBC Mode TDES MAC you must install the Enhancements to Cryptographic Support for z/OS V1R6/7 and z/OS.e V1R6/7 Web Deliverable

4. z/OS.e is NOT supported on the z9 EC (it is only supported on z9 BC, z800 and z890 servers)

PSP Bucket identifies minimal list of PTFs and SW needed to exploit functions.

•Points to ZIIP Functional PSP Bucket

Enhancements to Cryptographic Support for z/OS V1R6/R7 and z/OS.e V1R6/R7 Web Deliverable

IBM zIIP Support for z/OS and z/OS.eV1R6/R7 Web Deliverable

•Points to ICSF and zIIPweb deliverable




2. If you want to exploit either of the following cryptographic functions, you must install a Web deliverable and PTFs: Enhancements to CP Assist for Cryptographic Functions (CPACF) on the z9. (The enhancements are

support for the Advanced Encryption Standard (AES) for 128-bit keys, Secure Hash Algorithm-256 (SHA-256), and Pseudo Random Number Generation (PRNG).)

Crypto Express2 exploitation when a Crypto Express2 PCI-X adapter is configured as an accelerator or a coprocessor on the z9. The Web deliverable is Cryptographic Support for z/OS V1R6/R7 (which has FMID HCR7730) or its follow-on, Enhancements to Cryptographic Support for z/OS and z/OS.e V1R6/R7 (which has FMID HCR7731). The PTFs are those identified in the program directory that comes with the Web deliverable as well as the PTFs that are recommended in the appropriate ICSF PSP bucket. Note that these Web deliverables also provide support for callers running in 64-bit addressing mode.

3. If you plan to exploit Remote Key Loading for ATMs and point of sale (POS) devices, or will implement ISO 16609 CBC Mode TDES MAC, download and install the Enhancements to Cryptographic Support for z/OS and z/OS.e V1R6/R7 Web deliverable (which has FMID HCR7731), as well as the PTFs identified in the program directory that comes with the Web deliverable and the PTFs that are recommended in the appropriate ICSF PSP bucket.



4. If you plan to use IBM System z9 Integrated Information Processor (zIIP) support, download and install the IBM zIIP Support for z/OS and z/OS.e V1R6/R7 Web deliverable (which is FMID JBB77S9 for z/OS V1R6), as well as these PTFs: The PTFs identified in the program directory that comes with the Web deliverable The PTFs identified in the appropriate ZOSV1R6 BCPZIIP PSP bucket The PTFs identified in the ZIIP functional PSP bucket

Note: DB2 Universal Database for z/OS V8 (5625-DB2) with PTFs is also required for exploitation. The DB2 PTFs are included in the functional PSP bucket (and the hardware PSP Bucket)

5. Upgrade your hardware to a z9. If you are migrating from a z900 or z800 server, see “Migrate to a z990 or z890 server” in z/OS Migration for z990 and z890 migration considerations that you must also satisfy.

Note: z/OS.e is NOT supported on the z9 EC (it is only supported on z9 BC, z800 and z890 servers).




Summary




Summary: Support for z9 by Releasez/OS V1.4 with z990 Compatibility support feature (z/OS.e V1.4 with z990 Coexistence)

► 63.75 Subchannels► OSA-Express2 (Gigabit, 10 Gigabit, 1000BASE-T) Ethernet► Separate LPAR management of Processor Units (PUs)► FICON Express2► FICON Express4 supporting 1, 2, or 4 Gbps with 2-port or 4-port card ► CPACF or Crypto Express 2 (when configured as a coprocessor)

z/OS V1.4 with z990 Exploitation support feature (z/OS.e V1.4 w/z990 Coexistence Update feature) or z/OS or z/OS.e V1.5

► 60 Logical Partitions (30 LPARs of z9 BC)► Request Node Identification (RNID) for FICON► Channel Data Link Control (CDLC) Support ► OSA-Express2 CHPID Type OSN► FICON Error Recovery

z/OS or z/OS.e V1.6► z990 Support (zAAP, Single System Image – up to 32 engines)► Modified-Indirect-Addressing Word (MIDAW facility)► CPACF Enhancements (AES, SHA-256, and PRNG)► Crypto Express2 (when configured as a coprocessor or an accelerator)► OSA-Express2 Large Send Support► IBM System z9 Integrated Information Processor (IBM zIIP) Support

z/OS or z/OS.e V1.7 ► Multiple subchannel sets► Wild branch diagnosis improvement► FICON Incident Reporting ► HiperSockets support of IPv6► VLAN Management enhancements► XLC C/C++ Enable ARCH(7)/TUNE(7) compiler options ► Server Time Protocol (STP)

z/OS or z/OS.e V1.8► Support for up to 512 GB of real storage on a single z/OS image (z9 EC only)

z/OS.e

ONLY supporte

d on z9 BC


Summary: Migration ActionsActions you can take before you order a z9 EC or z9 BC► Review the sysplex configuration in which the z9 will participate

● Move any existing G6 or G6 z/OS images or coupling facilities to newer technology

► Review your current link technology► Review ‘inherited’ z990/z890 coexistence requirements► Install the necessary z/OS service and web deliverables► Run CFSIZER (if you are moving your coupling facilities)► Estimate the amount of HSA needed► Review message automation if z/OS V1.7 and using multiple subchannel sets► Verify PORTNAME on VTAM's TRLE match the device name in the DEVICE

statement in the TCPIP profile (If multiple LPARs share the same OSAadaptor in QDIO mode)

► Review zIIP Related ‘Release’ Changes► Create a z9 migration plan

Actions you can take after you order a z9 EC or z9 BC► Use HCD and the CHPID Mapping tool to define the processor




Time for……….


Backup




Key References for IBM System z9 EC or z9 BC

IBM System z9 Web site: www.ibm.com/systems/z/

IBM System z9 Data Sheet (US English): www.ibm.com/systems/z/hardware

IBM System z9 FAQ: www.ibm.com/systems/z/faq

Resource Link™: www.ibm.com/servers/resourcelink►zSeries Web site for no-additional-charge hardware support►Access to the zSeries library and other information required for

migration

IBM Redbooks: www.redbooks.ibm.com(Search Redbook™ Keyword = z9 EC or z9 BC)

IBM System z9 Integrated Information Processor (IBM zIIP) Web site:http://www.ibm.com/systems/z/feature012406/


Redbook™

► Server Time Protocol Planning Guide SG24-7280● Available at announce time

► Server Time Protocol Implementation Guide SG24-7281● Available at General Availability (GA)

Education► Introduction to Server Time Protocol (STP)

● Available on Resource Link™ at General Availability (GA)● www.ibm.com/servers/resourcelink/hom03010.nsf?OpenDatabase

STP Web site► www.ibm.com/systems/z/pso/stp.html

Systems Assurance► The IBM team is required to complete a Systems Assurance Review (SAPR Guide

SA06-012) and to complete the Systems Assurance Confirmation Form viaResource Link

Additional Information




Resource Link – the essential site for z9 migration!

Hardware►Purpose and Description documents, HIPER Alerts,

installation planning, education, and libraries for System z9, eServer zSeries, IBM TotalStorage, 2074 Control Unit, 9037 Model 2 Sysplex Timer

Operating Systems and Software►Links to z/OS, z/VM, z/VSE and VSE/ESA

Forums►General discussion forums on supported products

Product support►Support information and services for cross-brand hardware,

operating systems, software, and solutions

Register for an ID Today!www.ibm.com/servers/resourcelink


Additional/Source Informationz/OS Web site:► http://www.ibm.com/servers/eserver/zseries/zos/General Q & A:► http://www.ibm.com/servers/eserver/zseries/faq/Previously announced statements of direction:► http://www.ibm.com/servers/eserver/zseries/zos/zos_sods.htmlIBM System z9 and zSeries Internet Library:► http://www.ibm.com/servers/eserver/zseries/zos/bkserv/Descriptions of courses worldwide:► http://www.ibm.com/services/learningz/OS downloads:► http://www.ibm.com/servers/eserver/zseries/zos/downloads/ShopzSeries:► http://www.ibm.com/software/shopzseriesEPSP Tool► http://techsupport.services.ibm.com/390/psp_main.htmlIBM Resource Link► https://app-06.www.ibm.com/servers/resourcelink/hom03010.nsfServiceLink (IBMLINK2000)► https://www.ibm.com/ibmlink/link2/zSeries Technical Support Software Services ► http://www-1.ibm.com/services/us/its/pdf/swxcel.pdfzSeries IBM TechSupport Portal► http://www-1.ibm.com/servers/eserver/support/zseries/




Compatibilityvs

Exploitation


z/OS and z/OS.e V1.4 Compatibility Support►Supported on z9 EC or z9 BC with FMIDs

and PTFs►Supports running with function:

●Single LCSS (LCSS0)●No more than 15 LPARs●LPAR IDs 00 to 0F (hex)

►Crypto Express2 support requires Web download

z/OS and z/OS.e V1.4 Exploitation Support►Supported on z9 EC or z9 BC with FMIDs

and PTFs►Supports some new z9 functions:

●More on later z/OS releases●Multiple LCSSs●Up to 30 LPARs

►Crypto Express2 support requires Web download

LCSS0Up to 256 CHPIDs

Cannot exploit with Compatibility

support

LCSS1LCSS1

z/OS Compatibility vs. Exploitation on z9

LCSS0 LCSS1Up to 256 CHPIDs

Up to 256 CHPIDs




ICSF


z9: Crypto Software Support - CPACF

Enhancements to CP Assist for Cryptographic Function (CPACF)► Advanced Encryption Standard (AES) for 128-bit keys► Pseudo Random Number Generation (PRNG)► Secure Hash Algorithm 256 (SHA-256)► Data Encryption Standard (DES)► Triple Data Encryption Standard (TDES)► Secure Hash Algorithm (SHA-1)

AES, PRNG and SHA-256 require at a minimum z/OS 1.6 with a new web deliverable




Coprocessor

Coprocessor

Accelerator

Accelerator

Coprocessor

Accelerator

1

3

2

z9 Crypto Express2Configuration

Secure Coprocessor (default)► Provides both Secure key” and “Public

key” functionality and performance equivalent to Crypto Express2 features on z990

► “Secure key” improved performance compared to PCIXCC on z990 (requires multitasking)

► “Public key” equivalent performance to PCICA on z990

► No action required

Accelerator► Provides only “Public key” functionality

with enhanced performance ► Must be configured using the HMC


z9: Crypto Software

New FMID – HCR7730Web download: Cryptographic Support for z/OS V1R6/R7► Replaces web download ICSF 64-bit Virtual Support for z/OS

1.6 and z/OS.e 1.6z/OS HCR7730 ICSF will provide support for new functionality in the z9 hardware. ► Support will be provided for the Crypto Express2 when

configured as an accelerator (also known as fast path) and for clear key AES and SHA-2 functions provided by the CP Assist for Cryptographic Functions (CPACF)

HCR7730 ICSF will provide support for sysplex-wide CKDS "cache" consistency (not specific to z9)► An update to a CKDS record will result in the automatic

update of the DASD copy of the CKDS and the in-storage copies of the CKDS on all sysplex member systems

http://www-1.ibm.com/servers/eserver/zseries/zos/downloads/




z9: Crypto SoftwareNew FMID – HCR7731Web download: Enhancemnets to Cryptographic Support for z/OS and z/OS.eV1R6/R7► Replaces web download Cryptographic Support for z/OS V1R6/R7► Replaces web download ICSF 64-bit Virtual Support for z/OS 1.6 and z/OS.e 1.6

z/OS HCR7731 ICSF includes all prior support plus z9 exploitation support for Remote Key Loading for ATMs and point of sale devices, and implementation of ISO 16609 CBC Mode TDES MAC ► Remote Key Loading refers to the process of loading Data Encryption Standard (DES)

keys to Automated Teller Machines (ATMs) and Point of Sale (POS) devices from a central administrative site without the need for personnel to visit each machine to manually load DES keys. These enhancements provide two important new features:

– The ability to load initial keys to an ATM or a POS device from a remote location.– Enhanced capabilities for exchanging keys with non-CCA cryptographic

systems.

http://www-1.ibm.com/servers/eserver/zseries/zos/downloads/


z9: z/OS and z/OS.e Crypto Support

Integrated in z/OS base level




HCR77315z/OS 1.8 or z/OS.e 1.8





HCR7720z/OS 1.7 or z/OS.e 1.7

HCR77203HCR770B2HCR770AHCR770AHCR770Az/OS 1.6 or z/OS.e 1.6

N/AHCR770B2HCR770A1HCR7708HCR7708z/OS 1.5 or z/OS.e 1.5

N/AHCR770B2HCR770A1HCR77084HCR7706 or HCR77084

z/OS 1.4 or z/OS.e 1.4

Level Required for 64-bit

addressing caller support

Level Required for

Enhanced Secure Key

Support

Level Required for Secure Key

Support

Level Required for

Clear Key Support

Level Shipped in

Base Product

Operating System




z9: z/OS and z/OS.e Crypto Support

[05/2004] z990 and z890 Enhancements to Cryptographic Support

z/OS and z/OS.e 1.7 Enhancements to CPACF (AES, PRNG, and SHA-256) and Crypto Express2 exploitation

All Included

HCR7730[09/2005] Cryptographic Support for z/OS V1R6/R7 and z/OS.e V1R6/R7 (web download no longer available)

CPACF and Crypto Express2 exploitation

Enhancements include Remote Key Loading for ATMs and POSs

All Included

HCR7731[09/2005] Enhancemnets to Cryptographic Support for z/OS and z/OS.e V1R6/R7



All Included

HCR7731[09/2005] Enhancemnets to Cryptographic Support for z/OS and z/OS.e V1R6/R7

Enhancements to CPACF (AES, PRNG, and SHA-256) and Crypto Express2 exploitation

All Included

HCR7730[09/2005] Cryptographic Support for z/OS V1R6/R7 and z/OS.e V1R6/R7 (web download no longer available)

Compatibility support when a Crypto Express2PCI-X adapter is configured as a coprocessor

OA11946HCR7720[12/2004] ICSF 64-bit Virtual Support for z/OS 1.6 and z/OS.e 1.6 (web download no longer available)

All Included

OA09157

OA11946

OA09157

OA11946

OA09157

OA11946

APAR

HCR7731

HCR770B

HCR770B

HCR770A

FMID



N/A – In z/OS base productz/OS and z/OS.e 1.8

Compatibility support when a Crypto Express2 PCI-X adapter is configured as a coprocessor

[05/2004] z990 and z890 Enhancements to Cryptographic Support

z/OS and z/OS.e 1.6



[09/2003] z990 Cryptographic Support(web download no longer available)

z/OS and z/OS.e1.4/1.5

(with z990 ompatibilityfeature or z990 exploitation feature)

CommentsCrypto Web Downloadz/OS Release

OA09157 = Co-Processor

Permits the use of the z9-109 Crypto Express2 Co-Processor as a z990/z890 Crypto Express2

OA11946 = Accelerator toleration

When an Accelerator is defined, ICSF will abend without PTF for OA11946


ICSF Rosetta Stone

Planned 10/2007

9/2006z/OS 1.8HCR7731z/OS or z/OS.e V1.8

TBD5/2006z/OS 1.6 and z/OS 1.7HCR7731Enhancements to Cryptographic Support for z/OS and z/OS.e V1R6/R7

9/20043/2004z/OS 1.5HCR7708z/OS or z/OS.e V1.5

9/2005

9/2005

12/2004

5/2004

9/2004

9/2003

10/2003

6/2003

6/2003

3/2002

Avail

5/2006

10/2006

9/2005

Unsupported code on web

10/2005

5/2004

Unsupported code on web

10/2003

10/2003

9/2004*

EoM

z/OS 1.4HCR7708z/OS V1.4 z990 Exploitation Support or z/OS.e Coexistence Update feature

Cryptographic Support for z/OS V1R6/R7 and z/OS.e V1R6/R7

z/OS or z/OS.e V1.7

ICSF 64-bit Virtual Support for Z/OS V1.6 and z/OS.e V1.6

z990 and z890 Enhancements to Cryptographic Support

z/OS or z/OS.e V1.6

z990 Cryptographic Support

z/OS V1.4 z990 Compatibility Support or z.OS.e z990 Coexistence features

z990 Cryptographic CP Assist Support for z/OS V1.3

z/OS or z/OS.e V1.3 or V1.4

External Name

z/OS 1.7HCR7720

OS/390 2.10, z/OS 1.2, z/OS 1.3, z/OS 1.4 and z/OS 1.5

HCR770B

z/OS 1.6 and z/OS 1.7HCR7730

z/OS 1.6HCR7720

z/OS 1.6

OS/390 2.10, z/OS 1.2, z/OS 1.3, z/OS 1.4, any z/OS 1.4 features, and z/OS 1.5

z/OS 1.4

z/OS 1.3

z/OS 1.3 and 1.4

Applicable z/OS Releases

HCR770A

HCR7708

HCR770A

HCR7708

HCR7706

FMID




OSA Express2


z9: OSA-Express2

z9 OSA-Express2 Ethernet Features

OSA-Express2 OSN (OSA for NCP)GbE

OSA-Express2 OSN (OSA for NCP)1000BASE-TOSN

Non-QDIO, SNA/APPN/HPR and/or TCP/IP1000BASE-T OSE

Protocol-independent when Layer 210 GbE

TCP/IP traffic when Layer 3GbE

QDIO1000BASE-TOSD

OSA-Integrated Console Controller (OSA-ICC) TN3270E, non-SNA DFT to IPL CECs and LPARs, Operating system console operations

1000BASE-T OSC

Purpose/TrafficOSA-Express2 Features

CHPID Type




z9: OSA-Express2

z/OS 1.4 w/z990 Compatibility and higher

z/OS 1.4 w/z990 Exploitation and higher

Yes

Yes

OSA-Express2 Gigabit Ethernet SX and LX for CHPID OSD

CHPID OSN in support of OSA-Express2 OSN

z/OS V1.7YesVLAN management enhancements for OSA-Express2 and features for CHPID OSD

z/OS 1.4 w/z990 Compatibilityz/OS V1.5 for Checksum Offload

YesOSA-Express2 10 Gigabit Ethernet LR CHPID OSD

z/OS 1.4 w/z990 Compatibility and higher

z/OS 1.4 w/Exploitation and higher

Yes

Yes

OSA-Express2 1000BASE-T Ethernet CHPIDs OSC, OSD, OSE

CHPID OSN in support of OSA-Express2 OSN

z/OS 1.6 and higherNoOSA-Express2 Large Send

Operating SystemAPARFunction

z9 OSA-Express2 Requirements


HCD MigrationConsiderations




z/OS V1.7: HCDNew HCD FMID (HCS7720) shipped in z/OS 1.7► Required for z/OS 1.7 ► Requires an upgrade to IODF V5 if updates are needed● Size of IODF reduced significantly● Once z/OS V1R7 is running, updates are only allowed to an IODF that

has been upgraded to the V5 level

HCD compatibility support for pre-z/OS 1.7 systems► APAR OA08197 for z/OS 1.4, z/OS 1.5 and z/OS 1.6● HBB7707 PTF UA17026● HBB7708 PTF UA17027● HBB7709 PTF UA17028

► APAR OA07875 HCD (applies to z/OS 1.4+, z/OS 1.5 and z/OS 1.6)● An IODF generated with HCS7720 (z/OS 1.7) can be used for IPL for

z/OS 1.4, 1.5 and 1.6 and dynamic I/O for z/OS 1.4+, 1.5 and 1.6● Build IOCDS includes both devices in SS-0 and SS-1● Devices in SS-1 are ignored for z/OS 1.4+, 1.5 and 1.6

HCD

BCP IOS


z/OS V1.7 HCD Migration **IODF Version 5**

What happens if a z/OS R7 customer tries to update their IODF without running the Upgrade command? HCD message, CBDA488I: " IODF xxx must be upgraded for the current HCD version.“




z/OS V1.7 HCD: Migration **IODF Version 5**

What happens if a pre-R7 system without the appropriate APAR tries to IPL using a V5 IODF?► Wait State x'0B0' reason 2: The system could not recognize the IODF

specified in the LOADxx parmlib.

What happens if a pre-R7 system without the appropriate APAR tries to read or update a V5 IODF?► HCD message, CBDA467I: "IODF xxx contains a wrong IODF version."


z/OS V1.7 HCD: Migration **IODF Version 5**

What happens if a pre-R7 system WITH the appropriate APAR tries to update a V5 IODF?

● HCD issues message CBDA493I: "Requested action can not be performed on a version 5 IODF on z/OS 1.4 HCD." The inability to update a V5 IODF from a pre-z/OS R7 system if the customer has to fallback from the z/OS R7 release.

If fallback from z/OS R7 is required, options are to STEPLIB or EXPORT/IMPORT.

If pre-z/OS V1.4 Compatibility (z/OS V1.4 base or an OS/390 2.10 base) you CANNOT read, update or activate a V5 IODF.

► HCD message CBDA467I.► IPL wait state x'0B0‘ if z/OS allocation APAR not installed




z/OS 1.7 HCD: Coexistence Considerations

•No restriction to HCD use (read/update)

•IPL

•Dynamic Activate

•No access possible in HCD

•IPL (w/ OA08197)

•No Dynamic Activate

System running

z/OS R4 (HCS6091) w/o Compatibility Feat


•IPL

•Dynamic Activate


•IPL

•Dynamic Activate

•Read access possible w/o upgrade

•Update access requires IODF upgrade

•IPL

•Dynamic Activate

IODF created with z/OS pre-R7

(Version 4 IODF)

•No access possible in HCD

•No IPL

•No Dynamic Activate

Compatibility SPEs installed:Only read / no update in HCDIPLDynamic Activate

Compatibility SPEs not installed:

No access possible in HCDNo IPLNo Dynamic Activate


•IPL

•Dynamic Activate

IODF created with z/OS R7

(Version 5 IODF)

System running

z/OS preR4 (HCS6091)

System running

z/OS R4-6 (HCS7708)w/ Compatibility Feat.

System running

z/OS R7 (HCS7720)

z/OS R7: IODF upgrade function available to migrate from version 4 to version 5 IODF z/OS R4 – R6: Fall-back solution to downgrade from version 5 IODF to version 4 IODF via

Export I/O definitions (Build I/O configuration statements) and Import I/O definitions (Migrate I/O configuration statements)


z9 EC and z9 BCz/OS

Support




Y

Y

N

N

N

N

N

Server Time Protocol (STP)

Y

Y

Y

Y

Y

N

FICO

NError R

ecovery

YYYYYYYYYYYYYYYYYYYYYYYYz/OS V1.8

NYYYYYY9YY8Y7Y6YYYY6YYYYYYYYYz/OS V1.7

NNNNNNY9YY8Y7Y6YYYY6YYYYYYYYY2,

5z/OS V1.6

NNNNNNNNNNNYYYY3,4YYYYYYYYY2z/OS V1.5

NNNNNNNNNNNYYYY3,4YYYYYYYYY2z/OS V1.4 w/z990 Exploitation

NNNNNNNNNNNNNNY3,4YYYYY1Y1YYY0z/OS V1.4 w/z990 Compatibility

NNNNNNNNNNNNNNNNNNNNNNNNz/OS V1.4 BaseI

512 GB

Real

XLC

C/C

++

FICO

NLink Incident R

eporting

VLA

NM

anagement E

nhancements

Hipersockets

support of IPv6

Multiple S

ubchannelSets

zIIPS

upport

MID

AW

Support

Rem

ote Key Loading for A

TMs &

PO

Ss

& ISO

16609 CB

CM

ode TDE

SM

AC

CP

AC

FE

nhancements (A

ES

, SH

A-256, PR

NG

)

Crypto E

xpress2as an accelerator

60 LPA

Rs

OS

Afor N

CP

(CH

PID

Type O

SN

)

RN

IDfor N

ative FICO

N

Crypto E

xpress2as a coprocessor (S

ecure Key)

CP

AC

F(C

lear Key)

FICO

NE

xpress4(4K

MLX

, 10KMLX, or S

X)

OS

A/S

F -IP &

MA

C addressing

OS

A-E

xpress210 G

bE(LR

)

OS

A-E

xpress21000B

AS

E-T

OS

A-E

xpress2G

bE(LX

and SX)

63.75K Subchannel

Separate LP

AR

mgm

t of PU

s

z990 Support

z/OS Support for z9 EC by Release

Summary: z/OS Support for z9 EC by Release


Y

Y

N

N

N

N

N

Server Time Protocol (STP)

Y

Y6

Y4,6

Y3,4

Y3,4

Y3,4

N

Crypto E

xpress2as a coprocessor (S

ecure Key)

Y

Y

Y

Y

Y

N

FICO

NE

rror Recovery

NYYYYYYYYYYYYYYYYYYYYYYz/OS or z/OS.e V1.8

NYYYYYY9YY8Y7Y6YYYYYYYYYYYYz/OS or z/OS.e V1.7

NNNNNNY9YY8Y7Y6YYYYYYYYYYYY5z/OS or z/OS.e V1.6

NNNNNNNNNNNYYYYYYYYYYYY2z/OS or z/OS.e V1.5

NNNNNNNNNNNYYYYYYYYYYYY2

z/OS V1.4 w/z990Exploitation or

z/OS.e V1.4 w/z990 Coexistence Update

NNNNNNNNNNNNNNYYYYY1Y1YYY0

z/OS V1.4 w/z990 Compatibility or

z/OS.e V1.4 w/z990 Coexistence

NNNNNNNNNNNNNNNNNNNNNNNz/OS V1.4 BaseI or

z/OS.e V1.4 BaseI

512 GB

Real

XLC

C/C

++

FICO

NLink Incident R

eporting

VLA

NM

anagement E

nhancements

Hipersockets

support of IPv6

Multiple S

ubchannelSets

zIIPS

upport

MID

AW

Support

Rem

ote Key Loading for A

TMs &

PO

Ss

& IS

O 16609

CB

CM

ode TDE

SM

AC

CP

AC

FE

nhancements (A

ES

, SH

A-256, P

RN

G)

Crypto E

xpress2as an accelerator

30 LPA

Rs

II

OS

Afor N

CP

(CH

PID

Type O

SN

)

RN

IDfor N

ative FICO

N

CP

AC

F(C

lear Key)

FICO

NE

xpress4(4K

MLX

, 10KM

LX, or SX)

OS

A/S

F -IP &

MA

C addressing

OS

A-E

xpress210 G

bE(LR

)

OS

A-E

xpress21000B

AS

E-T

OS

A-E

xpress2G

bE(LX

and SX)

63.75K S

ubchannel

Separate LP

AR

mgm

t of PU

s

z990 Support

z/OS and z/OS.e Support for z9 BC by Release

Summary: z/OS and z/OS.e Support for z9 BC by Release

Legend - Not supported - Supported provided by base release and PTFs identified in 2094DEVICE PSP Bucket

- Supported provided by base release, a Web Deliverable, and PTFs identified in 2094DEVICE PSP Bucket



I – Neither z/OS V1.4 without any z990 features, nor z/OS.e V1.4 without any z990 features, supports z9 BC. Also, neither z/OS V1.4 without any z990 features, nor z/OS.e V1.4 without any z990 features, can participate in a sysplex when a z/OS or Coupling Facility (CF) image in that same sysplex is running on a z990, z890, or z9 server and the LPAR ID of the z/OS or CF image defined is greater than 15 (x"F"). II - z9 BC supports 30, not 60 LPARs Y0 – z990 (and z9) support limited to compatibility. z/OS or z/OS.e can use a single Logical Channel Subsystem (LCSS 0), and IPL in an LPAR whose LPAR ID is less than or equal to x’F’. Compatibility support required z/OS 1.4 with z/OS 1.4 z990 Compatibility Support feature (no longer orderable) or its replacement, the z/OS 1.4 z990 Exploitation Support feature (an unpriced, orderable feature). For z/OS.e, compatibility support required z/OS.e V1.4 with z/OS.e V1.4 z990 Coexistence feature (no longer orderable) or its replacement the z/OS.e V1.4 z990 Coexistence Update feature. Y1 – CHPID type OSN in support of OSA-Express2 requires the z/OS 1.4 z990 Exploitation Support feature (an unpriced, orderable feature. Other CHPID types, (for GbE: OSD; for 10 GbE: OSD; and for 1000BASE-T Ethernet: OSC, OSD, and OSE) are supported with the z/OS 1.4 z990 Compatibility Support feature. Y2 – z990 (and z9) support includes exploitation. z/OS can use any Logical Channel Subsystem, and IPL in an LPAR whose LPAR ID is greater than x’F’, and have more than 15 LPARs (up to 30 on a z990 or z9 BC and up to 60 on a z9 EC). Y3 –CP Assist for Cryptographic Functions (CPACF) for secure key processing requires the z990 Cryptographic Support Web deliverable (which was FMID HCR770A, and is no longer downloadable) or its replacement, the z990 and z890 enhancements to Cryptographic Support Web deliverable (which is FMID HCR770B) Y4 – Crypto Express2 compatibility support when a Crypto Express2 PCI-X adapter is configured as a coprocessor on the System z9 server requires the z990 Cryptographic Support Web deliverable (which was FMID HCR770A, and is no longer downloadable) or its replacement, the z990 and z890 enhancements to Cryptographic Support Web deliverable (which is FMID HCR770B). Note that for z/OS or z/OS.e V1.6 Crypto Express2 compatibility support was also provided with the Integrated Cryptographic Service Facility (ICSF) 64-bit Virtual Support for z/OS V1.6 and z/OS.e V1.6 Web deliverable (which is FMID HCR7720, and is no longer downloadable). The Integrated Cryptographic Service Facility (ICSF) 64-bit Virtual Support for z/OS V1.6 and z/OS.e V1.6 Web deliverable was replaced by the Cryptographic Support for z/OS V1R6/R7 Web deliverable (FMID HCR7730) which provides Crypto Express2 exploitation. Y5 – z990 (and z9) support the additional exploitation for zSeries Application Assist Processors and greater than 16 CP for a single z/OS image. Y6 – Crypto Express2 exploitation when a Crypto Express2 PCI-X adapter is configured as an accelerator or a coprocessor on the System z9 server requires the Cryptographic Support for z/OS V1R6/R7 Web deliverable (which was FMID HCR7730, or the follow-on Enhancements to Cryptographic Support for z/OS V1R6/R7 Web deliverable, which is FMID HCR7731). Y7 – Enhancements to CP Assist for Cryptographic Functions (CPACF) on the System z9 server. The enhancements are support for the Advanced Encryption Standard (AES) for 128-bit keys, Secure Hash Algorithm-256(SHA-256), and Pseudo Random Number Generation PRNG requires the Cryptographic Support for z/OS V1R6/R7 Web deliverable (which was FMID HCR7730, or the follow-on Enhancements to Cryptographic Support for z/OS V1R6/R7 Web deliverable, which is FMID HCR7731). Y8 – Remote Key Loading for ATMs and POSs and ISO 16609 CBC Mode TDES MAC, requires the Enhancements to Cryptographic Support for z/OS V1R6/R7 Web deliverable, which is FMID HCR7731, Y9 – zIIP support requires the IBM System z9 Integrated Information Processor Support for z/OS and z/OS.e V1R6/R7 Web Deliverable. Note: z/OS.e does not run on z9 EC servers.



Description of Features and Web Deliverables z/OS V1.4 z990 Compatibility Support feature: This unpriced, and optional feature is required to allow z/OS V1.4 to run on a z9 BC, z990, or z890 server. It is also required on all systems in a Parallel Sysplex when a z/OS or CF image in that same Parallel Sysplex is running on a z9 BC, z990, or z890 server and the LPAR ID of the operating system or CF image is greater than 15 (x"F"). With regards to cryptography, it provides support for the PCI Cryptographic Accelerator (PCICA) hardware feature and the CP Assist for Cryptographic Functions hardware feature for z/OS V1.4. This feature is no longer orderable. It was replaced by z/OS V1.4 z990 Exploitation Support feature. z/OS V1.4 z990 Exploitation Support feature: This orderable, unpriced and optional feature provides exploitation support for up to four Logical Channel Subsystems and greater than 15 LPARs for z9 BC, z990, and z890 servers. It is required on all z/OS V1.4 systems in a Parallel Sysplex when a z/OS or CF image in that same Parallel Sysplex is running on a z9 BC, z990, or z890 server and the LPAR ID of the operating system or CF image is greater than 15 (x"F"). With regards to cryptography, it provides support for the PCI Cryptographic Accelerator (PCICA) hardware feature and the CP Assist for Cryptographic Functions hardware feature for z/OS V1.4. This feature was mandatory when ordering z/OS V1.4 after February 24, 2004. This feature is no longer orderable. The code can still be obtained by downloading the package from the z/OS Download page. z/OS.e V1.4 z990 Coexistence Feature: This feature allows z/OS.e V1.4 to run on a z9 BC or z890 server. It provides support for z/OS.e V1.4 to use a single Logical Channel Subsystem, and IPL in an LPAR that has an LPAR ID less than 15 (X'F'). It is also required for z/OS.e V1.4 systems running on a z800 to coexist in a Parallel Sysplex when a z/OS or CF image in that same Parallel Sysplex is running on a z9-109, z9 BC, z990, or z890 and the LPAR ID of the operating system or CF is greater than 15 (x"F"). With regards to cryptography, it provides support for the PCI Cryptographic Accelerator (PCICA) hardware feature and the CP Assist for Cryptographic Functions hardware feature for z/OS.e V1.4. This feature is no longer orderable. It was replaced by z/OS.e V1.4 z990 Coexistence Update Feature. z/OS.e V1.4 z990 Coexistence Update Feature: This feature allows z/OS.e V1.4 to run on a z9 BC or z890 server. It allows z/OS.e V1.4 to support two Logical Channel Subsystems and up to 30 LPARs for z/OS.e V1.4 on a z890 or z9 BC; and allows z/OS.e to IPL in LPARs that have an LPAR ID greater than 15 (X'F'). With regards to cryptography, it provides support for the PCI Cryptographic Accelerator (PCICA) hardware feature and the CP Assist for Cryptographic Functions hardware feature for z/OS.e V1.4. It replaces the z/OS.e V1.4 z990 Coexistence feature. This feature was mandatory when ordering z/OS.e V1.4 after February 24, 2004. This feature is no longer orderable. The code can still be obtained by downloading the package from the z/OS Download page. z990 Cryptographic Support (FMID HCR770A): This Web deliverable provides support for z/OS and z/OS.e V1.5 and V1.4 releases on a z890, z990, or z9 server for PCIXCC and Crypto Express2 configured as a coprocessor (z9 servers only) hardware cryptography features, thus enabling these releases for both clear key and secure key cryptography. On May 27, 2004 it was no longer downloadable, and replaced by z990 and z890 Enhancements to Cryptographic Support for z/OS and z/OS.e Web deliverable (FMID HCR770B). z990 and z890 Enhancements to Cryptographic Support for z/OS and z/OS.e (FMID HCR770B): This Web deliverable allows z/OS and z/OS.e V1.6, V1.5, and V1.4 releases on a z890 or z990 server to extend support of the CPACF, PCICA, PCIXCC and Crypto Express2 configured as a coprocessor (z9 servers only) hardware cryptography features to exploit PKE/PKD service enhancements. It is required to exploit the following PKE/PKD service enhancements on z890, z990, or z9 server: Double Length Unique Key Per Transactions (DUKPT), and use of the EMV (Europay Mastercard and Visa) standard. This web deliverable replaced the z990 Cryptographic Support Web deliverable and can be used by any z890, z990 or z9 customer looking to download clear key or secure key cryptography support.



ICSF 64-bit Virtual Support for z/OS and z/OS.e 1.6 (FMID HCR7720): This Web deliverable provides support for callers running in 64-bit addressing mode. This support is included in z/OS V1.7. A limited set of callable services for AMODE(64) callers will be supported on IBM System z processors. They are intended to support System SSL, WebSphere, and Java. This web deliverable is also required to support Card Validation Value (CVV) generation and verification services for 19-digit Personal Account Numbers (PANs) for Crypto Express2 and PCIXCC features on z890, z990, and z9 servers. On September xx, 2005 it was no longer downloadable, and replaced by Cryptographic Support for V1R6/V1R7 and z/OS.e V1R6/R7 (FMID HCR7730), which in turn has been replaced by the Enhancements to Cryptographic Support for z/OS V1R6/R7 and z/OS.e V1R6/R7 on May 26, 2006. Cryptographic Support for V1R6/V1R7 and z/OS.e V1R6/R7 (FMID HCR7730): This Web deliverable includes all prior support plus exploitation support for new encryption functions in the z9 servers. This support includes configuring Crypto Express2 as an accelerator; clear key (CPACF) enhancements for the Advanced Encryption Standard (AES) for 128-bit keys, Secure Hash Algorithm-256(SHA-256), and Pseudo Random Number Generation (PRNG). On May 26, 2006 the Web deliverable was no longer downloadable, and replaced by the Enhancements to Cryptographic Support for z/OS V1R6/R7 and z/OS.e V1R6/R7 on May 26, 2006. Enhancements to Cryptographic Support for z/OS V1R6/R7 and z/OS.e V1R6/R7 (FMID HCR7731): This Web deliverable includes all prior support plus z9 exploitation support for Remote Key Loading for ATMs and point of sale devices, and implementation of ISO 16609 CBC Mode TDES MAC on z/OS V1.6, z/OS V1.7, z/OS.e V1.6 and z/OS.e V1.7. This Web deliverable replaced the Cryptographic Support for z/OS V1R6/R7 and z/OS.e V1R6/R7 Web deliverable on May 26, 2006. IBM zIIP Support for z/OS and z/OS.e V1R6/R7: This Web deliverable enables the redirecting of eligible workloads to the zIIP for z/OS V1.6, z/OS V1.7, z/OS.e V1.6 and z/OS.e V1.7.

Technology

A z/OS System Programmer’s Guide to Migrating to a New IBM System z9 EC or z9 BC Server