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
A z/OS System Programmer’s Guide to
Migrating to a New IBM System z9 EC
or z9 BC Server
Greg Daynes
gdaynes@us.ibm.com
STSM - z/OS Installation and Deployment Architect
IBM Systems
2 February 2007© 2007 IBM Corporation IBM Systems
Trademarks
The 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 countries
Linux 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*
DFSMSdfp
DFSMSdss
DFSMShsm
DFSMSrmm
DFSORT
e-business logo*
Enterprise Storage Server*
ESCON*
FICON*
GDPS*
Geographically Dispersed Parallel Sysplex
HiperSockets
HyperSwap
IBM*
IBM eServer
IBM e(logo)server*
IBM logo*
IMS
Language Environment*
MQSeries*
Multiprise*
MVS
NetView*
OMEGAMON*
On Demand Business logo
OS/390*
Parallel Sysplex*
PR/SM
Processor Resource/Systems Manager
RACF*
Redbook
Resource Link
RMF
S/360
S/370
S/390*
Sysplex Timer*
SystemPac*
System z9
Tivoli*
TotalStorage*
Virtualization Engine
VM/ESA*
VSE/ESA
VTAM*
WebSphere*
xSeries*
z/Architecture
z/OS*
z/VM*
z/VSE
zSeries*

Agenda
IBM System z9 Overview
z9 EC and z9 BC Support by z/OS Releases
Migration Considerations
► “Inherited” Considerations
► Multisystem/Sysplex Considerations
► Other Migration Considerations
Migration Paths
► General Recommendations and Considerations
► Recommended Paths for Supported z/OS Releases
Summary
Backup
► 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 PUs
4 models – Up to 32-way
Specialty Engines
► CP, IFL, ICF, zAAP
On Demand Capabilities
► CUoD, CIU, CBU, On/Off CoD
Memory – up to 256 GB
Channels
► Four LCSSs
► Up to 1024 ESCON® channels
► Up to 240 FICON Express2 channels
► Token-Ring, GbE, 1000BASE-T
Ethernet
► Coupling Links
Crypto Express2
Parallel Sysplex clustering
HiperSockets™
– up to 16
Up to 30 logical partitions
Operating Systems
► z/OS, z/VM®, VSE/ESA™, z/VSE™,
TPF, z/TPF, Linux® on zSeries
Announced 4/04 – zSeries
Superscalar Server with 5 PUs
1 model – Up to 4-way
► 28 capacity settings
Specialty Engines
► CP, IFL, ICF, zAAP
Channel
► Two LCSSs
► Up to 420 ESCON channels
► Up to 80 FICON Express2 channels
► Networking Adapters (OSA)
► Coupling Links
Crypto Express2
HiperSockets – up to 16
Operating 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 PUs
Granular Offerings for up to 8 CPs
Specialty Engines
► CP, IFL, ICF, zAAP, zIIP
Channels
► Four LCSSs
► Multiple Subchannel Sets
► MIDAW facility
► 63.75 subchannels
► Up to 336 FICON channels
► Enhanced FICON Express2 and 4
► 10 GbE, GbE, 1000BASE-T
► Coupling Links
Configurable Crypto Express2
Enhanced Availability
Operating 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
High levels of Granularity available
► 73 Capacity Indicators
Specialty Engines
► CP, IFL, ICF, zAAP, zIIP
Channels
► Two LCSSs
► Multiple Subchannel Sets
► MIDAW facility
► 63.75 subchannels
► Up to 112 FICON channels
► Enhanced FICON Express2 4 Gbps
► 10 GbE, GbE, 1000BASE-T
► Coupling Links
Enhanced Availability
Operating 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/ maintainable
MBA/STI fanout cards
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 enhancements
Microcode 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 CoD
Enhancements
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
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
Hot pluggable/ maintainable
MBA/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
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.

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 links
Allows concurrent migration from an ETR network with proper planning
Allows coexistence with ETR network
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 z9
Base 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.e
orders
z/OS V1.1, V1.2, V1.3 and z/OS.e V1.3
Any OS/390 release
Note: 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
supportforz/O
S
V1.4
and
V1.5
is
planned
to
be
withdrawn
M
arch
2007
Determining Your Level of z/OS V1.4 or z/OS.e V1.4
Check 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 Support
z9 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 Output
OA11665, 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
2094DEVIC
E
or2096DEVICE
PSP
Bucketforlatestservice
required
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 LPARs
Note: Assumes all FMIDs from compatibility feature and 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
► 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 APARsOA09157
OA11946
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 OSD
In 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.
► Multiple Logical Channel Subsystems
Note: Assumes all FMIDs from exploitation support feature and PTF service from the z990 PSP
are installed
Plus
► OSA-Express2 Gigabit Ethernet SX and LX for CHPID OSD
► OSA-Express2 1000BASE-T Ethernet for CHPID types OSC, OSD, and OSE
► Crypto Express2, compatibility support when Crypto Express2 adapter is configured as a
coprocessor
►► Up to 60 Logical Partitions (15 LPARs perUp to 60 Logical Partitions (15 LPARs per LCSSLCSS))
●● Up to 30 Logical Partitions (15Up to 30 Logical Partitions (15 LPARsLPARs perper 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) forRequest Node Identification Data (RNID) for FICONFICON
►► OSAOSA--Express2Express2 OSNOSN -- Open Systems Adapter forOpen 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)
BCP IOS
HCD
OA11238
OA07875
OSAOSA--Express2Express2 OSNOSN -- Open Systems Adapter forOpen 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 IOS
HCD
OA11238
OA07875
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)
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)
► Broadcast for IPv4 Packets
Note: Assumes PTF service from the z990 PSP are installed
Plus
► OSA-Express2 Gigabit Ethernet SX and LX for CHPID OSD and OSN
● Includes Checksum offload
► OSA-Express2 1000BASE-T Ethernet for CHPID types OSC, OSD, OSE, and OSN
► Crypto Express2, compatibility support when Crypto Express2 adapter is configured as a
coprocessor
► 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

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.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)

► zSeries Application Assist Processors (zAAPs)
► Up to 32 CPs for a single LPAR
Note: 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
► 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
►► 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 calledload feature (also called OSAOSA--Express2Express2 Large Send)Large Send)
►► IBM System z9 Integrated Information Processor (IBMIBM System z9 Integrated Information Processor (IBM zIIPzIIP) Support) Support
zIIP Web Deliverable
BCP, 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/IP
SNA
PK02490, PK21685
OA11148
TCP Segmentation Off-load feature (also called OSA
Large Send)
See charts 18 and 22All PTFs listed for previous z/OS levels (V1.4 & V1.5)
HCD
BCP, DFSMS
OA06830 +
APARs in Functional
MIDAW PSP Bucket
MIDAW Support
ICSF Web DeliverableN/ACrypto Express2 configured as a accelerator
ICSF Web DeliverableN/AEnhancements to CPACF (AES, PRNG, SHA-256)
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.6
Plus
►► MultipleMultiple 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 enhancementsVLAN 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 (IBMIBM System z9 Integrated Information Processor (IBM zIIPzIIP) Support) Support
►► Server Time Protocol (Server Time Protocol (STPSTP))

BCP, HCD, HCM,
System Automation for
z/OS
OA13344
See Functional STP
PSP Bucket
Server Time Protocol
zIIP Web Deliverable
BCP, 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
IBM System z9 Integrated Information Processor (IBM
zIIP) Support
HCDOA11709, OA12570Additional HCD Support and Model S54 Support
In baseN/AFICON link incident reporting
In baseN/AWild branch diagnosis improvement
TCP/IPPK05337VLAN Management enhancements
C/C++PK05323XLC C/C++ Enable ARCH(7)/TUNE(7) compiler options
EREP
BCP (IOS)
DFSMS
IR53369
OA11862, OA13311
OA13077
See charts 18, 22 and
28
All PTFs listed for previous z/OS levels (V1.5 and V1.6)
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.

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

Recommended

Recommended

More Related Content

What's hot

What's hot (9)

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

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

More from IBM India Smarter Computing

More from IBM India Smarter Computing (20)

Recently uploaded

Recently uploaded (20)

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