Family 3906+01 IBM z14

IBM United States Sales Manual
Revised:  November 06, 2018.

Table of contents
TOC Link Product life cycle dates TOC Link Technical description
TOC Link Abstract TOC Link Publications
TOC Link Highlights TOC Link Features
TOC Link Description TOC Link Accessories
TOC Link Product positioning TOC Link Supplies
TOC Link Models  

 
Product life cycle dates
Type Model Announced Available Marketing Withdrawn Service Discontinued
3906-M01 2017/07/172017/09/13 - -
3906-M02 2017/07/172017/09/13 - -
3906-M03 2017/07/172017/09/13 - -
3906-M04 2017/07/172017/09/13 - -
3906-M05 2017/07/172017/09/13 - -

Back to topBack to top
 
Abstract

IBM z14 provides the cornerstone for the trust economy

The world is in the midst of a transformation. It's having a profound effect on us as individuals, in business, and in society at large. As businesses adapt to capitalize on digital, trust will be the currency that drives this new economy.

Trust is the foundation of digital relationships. Consumer, client, and partner expectations have grown. They demand security, transparency, and greater value in every interaction and transaction as this new currency is exchanged.

Data is the new source of business value and differentiation. The ability to rapidly derive actionable insights will enable progressively smarter business decisions and improve customer experiences, leading to new revenue streams. Data protection is paramount for trust across the ecosystem.

Digital experiences are delivered through the cloud. Businesses must be open and connected in order to drive innovation at speed. They must accelerate development and delivery of secure, scalable services with new economic models.

The IBM z14, designed for trusted digital experiences

IBM z14 (z14), machine type 3906, provides a scalable, highly available platform that delivers differentiated value to enable business growth, reduce cost, and protect existing investments. The IBM z14 platform provides the hardware infrastructure, in a balanced system design, with the encryption capabilities that now make it possible to create a fortified perimeter around critical business data. z14 provides the infrastructure to meet the demands of a digital business. z14 continues in the same footprint as its predecessor z13, 42u in height with a 38u height reduction. It runs at 5.2GHz processor frequency, offers 8 TB memory/drawer for up to 32 TB per machine, 85 partitions, and up to 170 cores to configure (versus 141 on z13). z14 also offers IBM Virtual Flash Memory (VFM), Dynamic Partition Manager (DPM), zHyperLink Express, enhanced computing for TKE and HMC, Coupling Express LR for long range coupling connectivity, and a design for pervasive encryption allowing you to encrypt many new data sets transparently.

Model abstract 3906-M01

The 3906-M01 supports 256 to 8000 GB of memory, from 1 to 33 processor units (PUs), up to 4 IFB coupling fanouts, and up to 10 PCIe fanouts. The PCIe I/O drawers (#4013) house up to 80 I/O cards in support of cryptography (Crypto Express6S), the storage area network (FICON Express16S+ and IBM zHyperLink Express), the Ethernet local area network (OSA-Express6S and 10GbE RoCE Express2), Coupling Express LR, and compression (zEDC Express).

Model abstract 3906-M02

The 3906-M02 supports 256 to 16192 GB of memory, from 1 to 69 processor units (PUs), up to 8 IFB coupling fanouts, and up to 20 PCIe fanouts. The PCIe I/O drawers (#4013) house up to 160 I/O cards in support of cryptography (Crypto Express6S), the storage area network (FICON Express16S+ and IBM zHyperLink Express), the Ethernet local area network (OSA-Express6S and 10GbE RoCE Express2), Coupling Express LR, and compression (zEDC Express).

Model abstract 3906-M03

The 3906-M03 supports 256 to 24384 GB of memory, from 1 to 105 processor units (PUs), up to 12 IFB coupling fanouts, and up to 30 PCIe fanouts. The PCIe I/O drawers (#4013) house up to 160 I/O cards in support of cryptography (Crypto Express6S), the storage area network (FICON Express16S+ and IBM zHyperLink Express), the Ethernet local area network (OSA-Express6S and 10GbE RoCE Express2), Coupling Express LR, and compression (zEDC Express).

Model abstract 3906-M04

The 3906-M04 supports 256 to 32576 GB of memory, from 1 to 141 processor units (PUs), up to 16 IFB coupling fanouts, and up to 40 PCIe fanouts. The PCIe I/O drawers (#4013) house up to 160 I/O cards in support of cryptography (Crypto Express6S), the storage area network (FICON Express16S+ and IBM zHyperLink Express), the Ethernet local area network (OSA-Express6S, and 10GbE RoCE Express2), Coupling Express LR, and compression (zEDC Express).

Model abstract 3906-M05

The 3906-M05 supports 256 to 32576 GB of memory, from 1 to 170 processor units (PUs), up to 16 IFB coupling fanouts, and up to 40 PCIe fanouts. The PCIe I/O drawers (#4013) house up to 160 I/O cards in support of cryptography (Crypto Express6S), the storage area network (FICON Express16S+ and IBM zHyperLink Express), the Ethernet local area network (OSA-Express6S and 10GbE RoCE Express2), Coupling Express LR, and compression (zEDC Express).
Back to topBack to top
 

Highlights

This product extends IBM Z leadership with:

  • Agile innovation through a trusted cloud infrastructure

    With IBM z14 you can rapidly develop and deliver high-quality services deployed on a trusted cloud infrastructure that is flexible, efficient, and resilient, and includes enhanced security features.

    • The use of pervasive encryption for most extended format data sets can help address compliance requirements around encryption of data on disk and tape devices.
    • High-performance processors, large memory, and synchronous I/O to storage are designed to deliver significant performance improvements, driving faster user response times.
    • The scale is designed to help you manage more workloads at less cost with increases in capacity per core and increases in single system capacity.
    • Developers and administrators with no mainframe resources can rapidly develop new services, and monitor and provision resources without the need for new specialized skills.
  • Trusted insight built into everything you do with advanced cognitive and analytics processing

    With IBM z14 in the era of cognitive business you can build trusted insight into everything you do for smart operations, intelligent transactions and interactions, as well as intuitive business processes. The IBM z14 provides the ideal hardware platform for running these cognitive and analytical workloads.

    • Clients can build new cognitive and analytical applications by taking advantage of data natively created on IBM Z using industry-standard tools like Apache Spark.
    • Clients can help enhance the productivity of data scientists and improve time to value of Machine Learning (ML). Deploying ML on IBM Z gains the benefits of data gravity, high security, and IBM Z resiliency.
    • Integrated IBM Z data sources allow clients to capture new business value by leveraging insights from dark transactional data in their systems of insight.
  • IBM Blockchain, driving next-generation business networks

    With IBM z14 you can help ensure compliance and protect your business network by deploying Blockchain on IBM Z. IBM Z is the system of record for major organizations around the globe, handling the most sensitive data and critical transactions. Blockchain is a distributed ledger technology that is transforming businesses. IBM is building a blockchain for business where security, availability, and performance are fundamental. With support for pervasive encryption, as well as improvements to I/O performance, z14 provides the perfect platform for this next generation of ledgers for any industry.


Back to topBack to top
 
Description

The newest member of the IBM Z family, the IBM z14 (z14), (TM), is designed to be the cornerstone for a trust economy. IBM z14 provides a scalable, highly available platform that delivers differentiated value to enable business growth, reduce cost, and protect existing investments.

  • More total system capacity as compared to the z13 for exceptional scale in a single footprint.
  • Faster uniprocessor performance as compared to z13.
  • 170 cores to configure (versus 141 on z13).
  • Up to 32 terabytes (TB) of available Redundant Array of Independent Memory (RAIM) real memory per server to help improve transaction response times, lower CPU costs, simplify capacity planning, enlarge in-memory buffer pools, and ease deploying memory-intensive workloads.
  • 2x more on-chip cache per core, compared to z13, to minimize memory waits while maximizing the throughput of concurrent workloads -- perfectly optimized for data serving.
  • A design for pervasive encryption allowing you to encrypt many new data sets transparently, which can help you to provide an envelope of protection around data placed on IBM Z. This includes cryptographic performance improvements with the Crypto Express6S (#0893) and the IBM Z processor based cryptography with the CP Assist for Cryptographic Functions that helps enable the protection of data in flight or at rest.
  • Hardware accelerated encryption on every core with the Central Processor Assist for Cryptographic Function (CPACF) feature which is designed to provide faster encryption and decryption than previous servers.
  • Economies of scale with next-generation multithreading (SMT) for Linux and zIIP eligible workloads, new support for the I/O System Assist Processor (SAP), 2x AES performance over z13, a True Random Number Generator, SHA3 support, and RSA/ECC acceleration.
  • New instructions in Single Instruction Multiple Data (SIMD) which are designed to give a performance boost for traditional workloads using COBOL and new applications like analytics.
  • FICON Express16S+ (#0427, 0428) which is designed with a boost in I/O rates and a reduction in single stream latency to help absorb large application and transaction spikes driven by large unpredictable analytic and mobile workloads.
  • Improved compression ratio (using Huffman coding) and order-preserving compression for the on-chip compression coprocessor which results in fewer CPU cycles to enable further compression of data, improving memory, transfer, and disk efficiency.
  • 10 GbE RoCE Express2 with 4x more virtual functions per adapter and a performance improvement.
  • Coupling Express LR (#0433), for long range coupling connectivity. It is a replacement for the existing InfiniBand 1x HCA3-O LR coupling links.
  • IBM Hardware Management Console (HMC) 2.14 with simplification updates to improve workspace and manage system time. New security features include Multifactor Authentication and a new HMC Mobile application for monitor and recover action controls.
  • IBM Secure Service Container (formerly called z Appliance Container Infrastructure -- zACI) which can be used to create isolated partitions for protecting data and applications automatically --helping to keep them safe from insider threats as well as external cybercriminals.
  • IBM Dynamic Partition Manager enhancements which provide a simplified, consumable, enhanced IBM Z experience, reducing the barriers of adoption for new and existing Linux on z Systems, KVM, and z/VM clients.
  • Trusted Key Entry (TKE) 9.0 License Internal Code (LIC).
  • Optimized z/OS Platform for Apache Spark.
  • Java performance: support for reducing program pauses during Java Garbage Collection.
  • IBM Virtual Flash Memory (#0604), the replacement for the Flash Express features (#0402, #0403), offering up to 6.0 TB of virtual flash memory in 1.5 TB increments for improved application availability and to handle paging workload spikes.
  • IBM zHyperLink Express (#0431), which uses a direct connect short distance link (zHyperLink) to deliver low latency connectivity between z14 and FICON storage systems. Working in conjunction with your existing FICON SAN infrastructure, zHyperLink Express delivers the next generation of I/O for IBM Z storage.
  • Nonraised floor option, offering flexible possibilities for the data center.
  • Optional water cooling, providing the ability to cool systems with user-chilled water.
  • Optional high-voltage dc power, which can help IBM Z clients save on their power bills.
  • Optional top exit power and I/O cabling designed to provide increased flexibility.
  • New ASHRAE class A3 for robustness, data center flexibility, and energy savings.
  • The inclusion of IBM zAware function for cutting-edge pattern recognition analytics for fast insight into system health as part of the IBM software product IBM Operations Analytics for z Systems(tm)V3.1 - see announcement letter 216-373 dated September 13, 2016.
  • Upgradability to IBM z14 from IBM z13 and IBM zEnterprise EC12 and upgradability within the IBM z14 family.

The performance advantage

IBM's Large Systems Performance Reference (LSPR) method is designed to provide comprehensive z/Architecture processor capacity ratios for different configurations of Central Processors (CPs) across a wide variety of system control programs and workload environments. For IBM z14, the z/Architecture processor capacity indicator is defined with a 4XX, 5XX, 6XX, or 7XX notation, where XX is the number of installed CPs.

In addition to the general information provided for z/OS V2.2, the LSPR also contains performance relationships for z/VM, KVM, and Linux operating environments.

The capacity per processor engine of an IBM z14 (3906) processor is expected to provide approximately a 10% increase over that of a z13 (2964), with some variation, based on workload and configuration. The largest IBM z14 (3906-7H0) is expected to provide up to 35% more capacity than the largest z13 (2964-7E1). The IFL and zIIP processors on the IBM z14 also provide an optional IBM z14 multithreading technology capability; with the multithreading function enabled, the performance capacity of an IFL or zIIP is expected to typically be up to 25% higher than without the multithreading function enabled.

The LSPR contains the Internal Throughput Rate Ratios (ITRRs) for IBM z14 and the previous-generation IBM Z processor families based upon measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput that any user may experience will vary depending upon considerations such as the level of multiprogramming in the user's job stream, the I/O configuration, the workload processed, and the LPAR configuration. Therefore, no assurance can be given that an individual user will achieve throughput improvements equivalent to the performance estimates stated.

For more detailed performance information, consult the Large Systems Performance Reference (LSPR) available at the Resource Link website.

Next-generation availability

The IBM z14 processor builds upon the Reliability, Availability and Serviceability (RAS) of the z13 family, with the following RAS improvements:

  • IBM z14 Level 3 cache enhancements using powerful symbol ECC that now spreads cache data over multiple physical cache arrays. This enables the detection and correction of multibit errors, making the Level 3 cache more resilient and fault tolerant.
  • Preemptive DRAM marking added to main memory to isolate and recover failures more quickly.
  • Improved small array error handling in the processor cores.
  • Additional error thresholding to the processor core to isolate "sick but not dead" failure scenarios.
  • An increase in the number of "Resource Groups" (from 2 to 4) to reduce the impact of firmware updates and failures.

Common Criteria Evaluation Assurance Level 5+ (EAL 5+) certification

The IBM z14 is designed for Common Criteria Evaluation Assurance Level 5+ (EAL5+) certification for security of logical partitions. This means that the IBM z14 is designed to prevent an application running on one operating system image on one LPAR from accessing application data running on a different operating system image on another LPAR on the server.

Common Cryptographic Architecture (CCA) enhancements

PCI PTS HSM compliance

The Crypto Express6S coprocessor with CCA 6.0 is designed to comply with the Payment Card Industry (PCI) Pin Transaction Security (PTS) Hardware Security Module (HSM) Standard. PCI security standards are developed by the Payment Card Industry Security Standards Council to help ensure security in the payment card industry with guidance and direction to HSM vendors to help meet the security needs of the financial payments industry.

The requirements in PCI PTS HSM standards are intended to enhance security for operations that process sensitive data with requirements in key management, HSM API functions, device physical security, controls during manufacturing and delivery, device administration, and a number of other areas.

The Crypto Express6S manufacturing and delivery processes are enhanced with IBM z14 to comply with PCI PTS HSM and with CCA 6.0 introduces several new capabilities both for PCI PTS HSM compliance mode and for general use:

  1. A new derived key hierarchy so that PCI PTS HSM compliance-tagged key tokens may be used alongside existing keys and services in a nondisruptive fashion -- with existing master keys.

  2. Nondisruptive transition to PCI PTS HSM mode: Using TKE 9.0, a domain of the Crypto Express6S coprocessor with CCA 6.0 may be placed in PCI PTS HSM compliant mode with no disruption to other domains or to normal/legacy services using the domain that is moved to PCI PTS HSM compliant mode.

  3. Secure Audit Log hosted from the Crypto Express6S coprocessor with CCA 6.0. Required by the PCI PTS HSM standard, this audit log covers all administrative actions and is managed by TKE 9.0. The new audit log is nondisruptive to normal application processing for domains where it is active.

  4. Secure public key infrastructure: The Crypto Express6S coprocessor with CCA 6.0 adds native X.509 certificate support including PKCS #10 certificate request generation through a new PKI hosted from the coprocessor. Trust chain certificates are managed via TKE 9.0.

  5. Migration planning assistance through active application reporting. The Crypto Express6S coprocessor with CCA 6.0 can report in real time what operations and keys will need attention if they are planned for use with PCI PTS HSM compliant-tagged keys. Report details and activity depend on host access library/operating system configuration.

  6. CPACF exportable AES cipher key support added for AES cipher keys created using new options in CCA 6.0.

Trusted Key Entry (TKE) 9.0 Licensed Internal Code (LIC)

The following functions are planned to be supported in the TKE 9.0 level of LIC:

  • Crypto Express6S Coprocessor support: TKE 9.0 is required for managing Crypto Express6S cryptographic coprocessors and manages them through the same Crypto Module notebook functions as previous generations of Cryptographic modules.
  • Key material copy to alternate zone: TKE 9.0 allows you to copy key material from smart cards in one TKE zone to smart cards in another zone. You might have old 1024 bit strength TKE zones, and may wish to move/copy the key material in those zones into a new, stronger TKE zone. To use this new feature you create new TKE and/or EP11 smart cards on your TKE 9.0 system. You enroll the new TKE and/or EP11 smart cards in an alternate zone. This allows you to copy smart card content from a smart card enrolled in the alternate zone.
  • Save TKE data directory structure with files to USB: TKE data can be saved to, or restored from, removable media in the same directory structure they were found on the TKE.
  • Create key parts without opening a host: The TKE application now has the ability for administrators to create key parts without opening a host. This allows the key administrator to create key parts while being offline or before any hosts are defined. This feature can be found in the TKE application under the Utilities > Create CCA key parts pull down menu.
  • New TKE Audit Log application: There is a new TKE Audit Log application available for the Privileged Mode Access ID of AUDITOR. This application provides a new, easy-to-use interface to view the TKE workstation security audit records from the TKE workstation.
  • Heartbeat audit record: TKE workstations cut an audit record when the TKE boots or when no audit events have occurred during a client-configured duration of time. The record shows the serial number of the TKE local crypto adapter and indicates if the local crypto adapter has been changed since the last check.
  • Performance improvements for domain groups: With CCA 5.3 and later firmware levels, and TKE 9.0, performance may be improved for operations performed with large domain groups. For example, consider a domain group of 85 domains and a Clear New Master Key Register operation is performed from the TKE. The number of TKE commands issued to the Crypto Express coprocessor from the TKE will be reduced from 85 to 1, thereby reducing the time to complete the operation.
  • Master key part entry on EP11: Known master key parts can now be entered and saved on smart cards for coprocessors configured in EP11 mode using TKE 9.0. This enables key custodians to manage EP11 master key parts in a fashion that is consistent with coprocessors configured in CCA mode.
  • Smart card readers: With TKE 9.0, if you have HID/OMNIKEY smart card readers you may continue to use them. See the TKE User's Guide for more detailed smart card reader information.
  • New certificate manager for domains: Every domain will now have the ability to manage a set of parent X.509 certificates for validating operating X.509 certificates used by applications running in the domain. The Crypto Express6S with CCA 6.0 is designed to meet the PCI-HSM PIN Transaction Security v3.0, 2016 standard.

    The following features are related to support for the Crypto Express6S with CCA 6.0.

  • Domain mode management: With CCA 6.0, individual domains are in one of the following modes:
    • Normal mode
    • Imprint mode
    • Compliant mode

    Imprint and compliant modes were added to help customers migrate to a PCI-HSM compliant mode and meet PCI-HSM PIN Transaction Security v3.0, 2016 requirements. TKE is required to manage Host Crypto Module domains in imprint and compliant mode.

  • Set clock: With TKE 9.0, you now have the ability to set the host crypto module's clock. The clock must be set before a domain can be placed in imprint mode.
  • Domain-specific Host Crypto Module Audit Log management: Domains in imprint mode or compliant mode on a Crypto Express6S maintain a domain-specific module audit log. The TKE provides a feature for downloading the audit records so they can be viewed.
  • Domain-specific roles and authorities: Domains in imprint mode or compliant mode on a Crypto Express6S must be managed using domain-specific roles and authorities. The TKE provides new management features for the domain-specific roles and authorities. The roles are subject to forced dual control policies which prevent roles from being able to both issue and cosign a command. Refer to the TKE User's Guide for detailed information on how to manage imprint and compliant mode domains.
  • Setup PCI Environment Wizard: To help simplify the management of a PCI compliant domain, the TKE now provides a setup wizard that will create a minimum set of required dual control roles and authorities needed to manage a PCI compliant domain. Refer to the TKE User's Guide for detailed information on how to manage imprint and compliant mode domains.

FICON Express16S+

With the introduction of FICON Express16S+ on the IBM z14, you now have additional growth opportunities for your storage area network (SAN).

FICON Express16S+ supports a link data rate of 16 gigabits per second (Gbps) and autonegotiation to 4 or 8 Gbps for synergy with existing switches, directors, and storage devices. With support for native FICON, High Performance FICON for z Systems (zHPF), and Fibre Channel Protocol (FCP), the IBM z14 server enables you to position your SAN for even higher performance -- helping you to prepare for an end-to-end 16 Gbps infrastructure to meet the lower latency and increased bandwidth demands of your applications.

The FICON Express16S+ adapter will work with your existing fiber optic cabling environment, both single mode and multimode optical cables. The FICON Express16S+ feature running at end-to-end 16 Gbps link speeds will provide reduced latency for large read/write operations and increased bandwidth compared to the FICON Express8S feature.

Increased throughput for the zHPF protocol: In laboratory measurements using FICON Express16S+ in a z14 with the zHPF protocol and small data transfer I/O operations, FICON Express16S+ operating at 16 Gbps achieved a maximum of 300,000 IOs/sec. In laboratory measurements, using FICON Express16S+ in a z14 with the zHPF protocol and a mix of large sequential read and write data transfer I/O operations, FICON Express16S+ operating at 16 Gbps achieved a maximum throughput of 3200 MB/sec (reads + writes) compared to a maximum of 2560 MB/sec (reads + writes) achieved with FICON Express16S operating at 16 Gbps. This performance data was measured in a controlled environment running an I/O driver program under z/OS. The actual throughput or performance 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.

Increased throughput for the FCP protocol: A FICON Express16S+ feature, when defined as CHPID type FCP, conforms to the Fibre Channel Protocol (FCP) standard to support attachment of SCSI devices, to complement the classical storage attachment supported by FICON and zHPF channels. In laboratory measurements, using FICON Express16S+ in an IBM z14 with the FCP protocol for small data transfer I/O operations, FICON Express16S+ operating at 16 Gbps achieved a maximum of 380,000 IOs/sec, compared to the maximum of 110,000 IOs/sec achieved with FICON Express16S operating at 16 Gbps. In laboratory measurements, using FICON Express16S+ in an IBM z14 with the FCP protocol and FICON Express16S+ operating at 16 Gbps, FICON Express16S+ achieved a maximum throughput of 3200 MB/sec (reads + writes). This represents approximately a 25% increase in throughput. The actual throughput or performance 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.

The FCP protocol is supported by z/VM, z/VSE, KVM, and Linux on IBM z Systems. Refer to the Software requirements section.

Cleaning discipline for FICON Express16S fiber optic cabling: With the introduction of 16 Gbps link data rates, it is even more critical to ensure your fiber optic cabling infrastructure performs as expected. Proper fiber optic cleaning and maintenance is required to help ensure that the "data gets through." With 16 Gbps link data rates over multimode fiber optic cabling, link loss budgets and distances are reduced. Single mode fiber optic cabling is more "reflection sensitive." With high link data rates and single mode fiber optic cabling there is also less margin for error. The cabling is no longer scratch-tolerant and contaminants such as dust and oil can present a problem. To keep the data flowing, proper handling of fiber trunks and jumper cables is critical as well as thorough cleaning of fiber optic connectors. Work with your data center personnel or IBM personnel to ensure you have fiber optic cleaning procedures in place.

Channel subsystem (CSS) scalability: The IBM z14 server, like the IBM z13 server, has support for six logical channel subsystems (LCSSs) which are required to support the 85 LPARs for IBM z14, and four subchannel sets.

OSA-Express6S - an Ethernet technology refresh

A new generation of Ethernet features is being introduced for use in the PCIe I/O drawer and continues to be supported by the 16 GBps PCIe Gen3 host bus. This is an introduction of the full family of features - 1000BASE-T Ethernet for copper environments, in addition to 10 Gigabit Ethernet (10 GbE) and Gigabit Ethernet (GbE) for single-mode and multimode fiber optic environments. The performance characteristics are comparable to the OSA-Express5S features. They also retain the same form factor and port granularity - two ports per feature for the 1000BASE-T Ethernet and Gigabit Ethernet features, and one port per feature for the 10 Gigabit Ethernet features.

The OSA-Express6S family of features (#0422, #0423, #0424, #0425, #0426) is exclusive to the z14. They are supported by z/OS, z/VM, z/VSE, z/TPF, Linux on z Systems, and KVM hypervisor. Refer to the Software requirements section.

IBM Virtual Flash Memory

IBM Virtual Flash Memory (VFM) is the replacement for the Flash Express features (#0402, #0403) which were available on the IBM zEC12 and IBM z13. No application changes are required to change from IBM Flash Express to VFM.

IBM Virtual Flash Memory is designed to help improve availability and handling of paging workload spikes when running z/OS V2.3, V2.2, or V2.1, or on z/OS V1.13*. With this support, z/OS is designed to help improve system availability and responsiveness by using VFM across transitional workload events such as market openings, and diagnostic data collection. z/OS is designed to help improve processor performance by supporting middleware exploitation of pageable large (1 MB) pages.

Using VFM can help availability by reducing latency from paging delays that can occur at the start of the workday or during other transitional periods. It is also designed to help eliminate delays that can occur when collecting diagnostic data during failures. VFM can also be used in Coupling Facility images to provide extended capacity and availability for workloads making use of WebSphere MQ Shared Queues structures.

VFM can therefore help organizations meet their most demanding service level agreements and compete more effectively. VFM is designed to be easy to configure, and to provide rapid time to value.

* z/OS V1.13 has additional requirements. See the Software Requirements section.

IBM zHyperLink Express

IBM zHyperLink Express is a direct connect short distance, IBM Z I/O adapter offering extremely low latency connectivity to FICON storage systems. Working in conjunction with your existing FICON SAN infrastructure, zHyperLink fosters a new I/O paradigm for IBM mainframes. zHyperLink improves application response time, cutting I/O sensitive workload response time by up to 50% without requiring application changes. zHyperLink Express is a 2 port adapter which resides in the PCIe I/O drawer and supports direct connectivity to FICON storage systems at distances up to 150 m.

Note: This response time estimate is based on IBM internal measurements and projections that assume 75% or more of the workload response time is associated with read DASD I/O and the storage system random read cache hit ratio is above 80%. The actual performance that any user will experience may vary.

Dynamic Partition Manager (DPM)

Dynamic Partition Manager (DPM) provides simplified hardware and virtual infrastructure management, including partition lifecycle and integrated dynamic I/O management for Linux running in an LPAR, under KVM on z, and under z/VM 6.4. Using DPM, an environment can be created, provisioned, and modified without disrupting running workloads, and monitored for troubleshooting. Currently, DPM supports FCP storage. Enhancements to DPM simplify the installation of the Linux operating system, and support additional hardware adapters. These enhancements include:

  • Support for autoconfiguration of devices to simplify Linux operating system installation, where Linux distribution installers exploit function
  • Secure FTP through HMC for booting and installing an operating system via FTP
  • Support for OSA-Express6S, FICON Express 16S+, Crypto Express6S, and RoCE Express2 adapters

A CPC can be configured in either the Dynamic Partition Manager mode or PR/SM mode. The mode is enabled prior to the CPC power-on reset (POR).

Dynamic Partition Manager mode requires two OSA-Express 1000BASE-T Ethernet features for primary and backup connectivity (OSA-Express6S 1000BASE-T Ethernet, #0426 or OSA-Express5S 1000BASE-T Ethernet, #0417), along with associated cabling (HW for DPM, #0016).

The IBM Secure Service Container

The IBM Secure Service Container is a framework for securely deploying software appliances on IBM Z and LinuxONE. Currently, there are three offerings that exploit the Secure Service Container:

  • IBM Blockchain High Security Business Network
  • IBM Operations Analytics for z Systems - zAware
  • IBM z/VSE Network Appliance

The Secure Service Container consists of both a firmware framework and a software framework.

The following is an enhancement to the z14 IBM Secure Service Container firmware framework:

  • Simplification - Dynamic Partition Manager support for dynamic resource management and creation of Secure Service Container LPARs without needing to re-IML.

The following are enhancements that have recently been made to the IBM Secure Service Container software framework:

  • Security
    • Enable secure boot of appliance via system unique key smart card access such that the Secure Service Container or system administrator cannot utilize privileged credentials to see or access the key.
    • Runtime and tamper protection via BTRFS Filesystems for root and data volumes.
  • Appliance management
    • Support the addition of FCP (and ECKD) storage to different disk pools via the appliance UI.
    • Support network configurations managed by IPv4, IPv6, and VLAN configurations from the appliance UI.
    • Enable appliance updates including import from a prior, saved and exported configuration -- avoid losing configuration data (going back to a "Factory Install"--like state); particularly useful for Blockchain, which typically utilizes many concurrently running instances.
    • Support different users and groups via Local LDAP server and UI management.
    • Support starting appliance installer from a running appliance without having to interface with the HMC.
  • Usability
    • Avoid appliance spoofs by ensuring that a trusted and uniquely signed instance of an appliance is booted only in one LPAR, not multiple LPARs.

z/Architecture mode

As announced on January 14, 2015 with Announcement letter 115-001, beginning with IBM z14, all IBM Z systems will only support operating systems running in z/Architecture mode. This applies to operating systems running native on PR/SM as well as operating systems running as second-level guests. IBM operating systems that run in ESA/390 mode are either no longer in service or only currently available with extended service contracts, and they are not usable on systems beginning with IBM z14. However, IBM z14 does provide ESA/390-compatibility mode, an environment supporting a subset of DAT-off ESA/390 applications in a hybrid architectural mode.

All 24-bit and 31-bit problem state application programs originally written to run on the ESA/390 architecture will be unaffected by this change.

z/OS support for the IBM z14

Functions in z/OS continue to enhance the role of IBM Z, with support for the IBM z14 and its role in helping you provide solutions for a trusted digital economy. Capabilities designed to optimize high availability, performance, security, and operational flexibility can help organizations grow and to secure their most critical transaction environments.

In addition to base processor support, z/OS provides the support for these IBM z14 functions and features -- Engine for digital transformation:

  • Improved cryptographic capabilities that can be leveraged to begin implementation of IBM's pervasive data encryption strategy .
  • The IBM zHyperLink Express feature (also, refer to the "IBM zHyperLink Express" section of this announcement).
  • Cryptography enhancements available with the Crypto Express6s feature.
  • Asynchronous Memory Clear using System Assist Processors (SAPs).
  • Additional new I/O attachment options including the OSA-Express6S, RoCE Express2, and FICON Express 16S+ features.
  • Coupling Facility Level (CFLEVEL) 22 and new Coupling link features (also, refer to the "Parallel Sysplex enhancements" section of this announcement).
  • The Guarded Storage Facility, exploited by IBM SDK for z/OS, Java Technology Edition, Version 8 (5655-DGG).
  • The Instruction Execution Protection Facility.
  • IBM Virtual Flash Memory.

Refer to the Software Requirements section of this announcement for the minimum z/OS requirements for the IBM z14 and its features.

Container Pricing for IBM Z:

IBM is introducing Container Pricing for IBM Z for qualified solutions running on IBM z13 and z14 servers. Container Pricing will provide simplified software pricing for qualified solutions, combining flexible deployment options with competitive economics that are directly relevant to those solutions.

Container Pricing can scale from collocated solutions within existing LPARs, through to separate LPARs, up to multiple-LPAR solutions, without directly impacting the cost of unrelated workloads.

Additionally, Container Pricing will simplify pricing and billing on the IBM Z platform, by superseding a number of existing price offerings and by fully automating the billing process.

IBM initially announces three solutions that will be enabled with Container Pricing:

  • The New Application Solution will provide a highly competitive stand-alone priced offering for new z/OS applications, such as CICS TS or WebSphere applications. The New Application Solution is the strategic replacement for the current zCAP and IWP priced offerings.
  • The Application Development and Test Solution will provide highly competitive stand-alone pricing for z/OS based development and test workloads. Modern DevOps tooling can be optionally added at uniquely discounted prices.
  • The Payments Solution will provide a 'per payment' pricing option for IBM Financial Transaction Manager for z/OS deployments. This new offering directly ties operational cost to business value by basing the price on the number of payments processed, rather than capacity used to process them.

Container Pricing for IBM Z is planned to be available by year end 2017 and enabled in z/OS V2.2 and z/OS V2.3 with the PTFs for APARs associated with fix category IBM.Function.PricingInfrastructure. z/OS will enhance both the Workload Manager capability of z/OS (z/OS WLM) and the Sub-Capacity Reporting Tool (SCRT) to support Container Pricing. This includes:

  • The introduction of a new Tenant Resource Group capability within z/OS WLM to allow the metering and optional capping of workloads, along with the ability to map those workloads directly to Container Pricing.
  • Enhancements to SCRT to capture eligible Container Pricing workloads, allowing for the billing of those solutions independently of traditional Sub-Capacity pricing.

z/VM support for the IBM z14

With the PTF for APAR VM65942, planned to be available August 25, 2017, z/VM V6.3 and V6.4 provide support that will enable guests to exploit function supported by z/VM on IBM z14, which includes:

  • z/Architecture support: The z/VM Stand-Alone Program Loader (SAPL) utility, DASD Dump Restore (DDR), and the Stand-Alone Dump utility have been enhanced to run entirely in z/Architecture mode. z/Architecture support for these utilities is in the base of z/VM V6.4 and provided for z/VM V6.3 with the available PTF for APAR VM65856. z/Architecture support for the Stand-Alone Dump utility is in the base of z/VM V6.4 and provided for z/VM V6.3 with the available PTFs for APARs VM65921 and VM65922.
  • Hardware facilities: z/VM will enable guest use of new instructions and capabilities available on IBM z14.
  • ESA/390-compatibility mode for guests: IBM z14 does not support the full ESA/390 architectural mode. However, IBM z14 does provide ESA/390-compatibility mode, an environment supporting a subset of DAT-off ESA/390 applications in a hybrid architectural mode. z/VM will provide the support necessary for DAT-off guests to run in this new compatibility mode, which allows guests such as CMS, GCS, and those that start in ESA/390 mode briefly before switching to z/Architecture mode to continue to run on IBM z14.

    The available PTF for APAR VM65976 provides infrastructure support for ESA/390 compatibility mode within z/VM V6.2, V6.3, and V6.4, and must be installed on all members of an SSI cluster before any z/VM V6.3 or V6.4 member of the cluster is run on an IBM z14 server.

  • Support for Crypto Express6S: z/VM support for the new Crypto Express6S (CEX6S) adapter is included for both shared and dedicated guest use. As with the prior crypto adapter support, the CEX6S adapter can be configured as an accelerator or as an IBM Common Cryptographic Architecture (CCA) coprocessor for shared or dedicated use by z/Architecture guests. When the CEX6S adapter is configured as an IBM Enterprise Public-Key Cryptography Standards (PKCS) #11 (EP11) coprocessor, the domains on the adapter can be dedicated to z/Architecture guests, but not shared. With Crypto Express6S support and support for the new and enhanced CPACF functions, z/VM V6.3 and V6.4 provide the prerequisite IBM z14 encryption support to enable exploitation by guests in support of pervasive encryption of data in flight and at rest.
  • Dynamic I/O support: Dynamic I/O support is provided for managing the configuration of OSA-Express6S OSD CHPIDs, FICON Express16S+ FC and FCP CHPIDs, Regional Crypto Enablement (RCE), zHyperLink Express, and RoCE Express2 functions. The available PTF for APAR VM65865 provides dynamic I/O support for the Coupling Express LR adapter in z/VM V6.3 and z/VM V6.4, and is applicable to z13, z13s, and z14.
  • RoCE Express2 support: Guest exploitation support for RoCE Express2 allows the adapters to be brought online and attached to supporting guests for exploitation.
  • Improved memory management support: The IBM z14 processor design allows greater concurrency in address translation. This improvement may increase z/VM workloads' performance compared to z13, particularly when z/VM is configured to exploit multithreading.

Installing z/VM on the IBM z14:

z/VM V6.3 cannot be installed directly on an IBM z14 server. Instead, z/VM V6.3 must be installed on a prior IBM Z server and the PTFs for APARs VM65942, VM65921, and VM65922 must be applied prior to moving the image to z14. After applying all required service and before IPLing z/VM V6.3 on an IBM z14 server, an updated SAPL must be installed by using the updated SALIPL MODULE provided by the PTF for APAR VM65856. Otherwise, z/VM V6.3 will not successfully IPL on a z14 server. In addition, after applying the PTFs for APARs VM65921 and VM65922, the stand-alone dump program must be re-installed using the updated SDINST utility.

z/VM V6.4 can be installed directly on a z14 server with an image obtained from IBM after August 25, 2017. The PTF for APAR VM65942 must be applied immediately after installing z/VM V6.4.

Guest exploitation support for the Instruction Execution Protection Facility:

With the PTF for APAR VM65986, planned to be available December 15, 2017, z/VM V6.4 will provide support for guest exploitation of the IBM z14 Instruction Execution Protection Facility. This facility provides functionality to help improve the security of programs running on IBM Z by allowing virtual memory elements to be identified as containing only data. If an attempt is made to fetch an instruction from an address in such an element or if an address in such an element is the target of an execute-type instruction, a Protection Exception will occur.

Guest exploitation support for pause-less garbage collection:

With the PTF for APAR VM65987, planned to be available December 15, 2017, z/VM V6.4 will provide support for guest exploitation of the z14 Guarded Storage Facility. This facility is designed to improve the performance of garbage-collection processing by various languages, in particular Java.

Encrypted paging support:

With the PTF for APAR VM65993, planned to be available December 15, 2017, z/VM V6.4 will provide support for encrypted paging, in support of the z14 pervasive encryption philosophy of encrypting data in flight and at rest. Ciphering will occur as data moves between active memory and a paging volume owned by z/VM. Included in the support is the ability to dynamically control whether a running z/VM system is encrypting this data.

Sub-capacity pricing terms for z/VM and select z/VM-based programs:

Sub-capacity pricing for the z/VM V6 operating environment is available to clients running z/VM Version 6 Release 3 or higher. Software pricing at less than full machine capacity can provide more flexibility and improved cost of computing as a client manages the volatility and growth of new workloads. For more information about Sub-capacity pricing terms for z/VM and z/VM-based programs, see announcement letter 217-267, dated July 17, 2017.

z/VM continuous delivery philosophy:

IBM has adopted a new practice for z/VM, known as the continuous delivery (CD) support model, for delivering new function via PTFs to assist enterprises in receiving function more quickly. IBM will deliver new function via PTFs, while continuing to recognize that base stability is a critical component. Clients will continue to receive the same world-class support and assistance from IBM to which they are accustomed as part of the standard Software Subscription and Support (S&S) offering. The z/VM service page provides details on new z/VM functions that have been or will be provided using this continuous delivery model and allows for subscribing to be alerted when new functions have been made available.

Additional z/VM V6.4 enhancements during 2017:

The following enhancements for z/VM V6.4 are planned during 2017:

  • Concurrent I/O support for the IBM XIV Storage System: With the available PTF for APAR VM65929, the z/VM SCSI container enables multiple I/O requests to be issued concurrently to EDEVICEs backed by IBM XIV Storage System hardware, which may improve performance. This support particularly benefits EDEVICE paging I/O or volumes containing multiple minidisks.
  • Distributed IUCV enhancements: With the available PTF for APAR VM65872, the rules for Distributed IUCV CONNECT in a single system image (SSI) environment are revised. This support allows IUCV CONNECT to work in cases that were originally restricted, primarily because they involved a Multiconfiguration Virtual Machine (IDENTITY) user.

    This support also makes it easier for an administrator to change the Distributed IUCV policy for an SSI cluster. Previously, the Distributed IUCV policy within an active SSI cluster could be changed only by shutting down all members at the same time. As this new support is applied to each system, it will be possible for that member to join the cluster regardless of its Distributed IUCV configuration.

  • NICDEF security control enhancements: With the PTFs for APARs VM65925, VM65926, and VM65931, planned to be available August 4, 2017, the NICDEF directory statement is enhanced to provide a set of new operands referred to as Directory Network Authorization (DNA). With DNA, a system administrator can configure and consolidate a virtual NIC device and its network properties in a centralized location - z/VM's User Directory. Operational differences between PORTBASED and USERBASED VSwitches have been eliminated with this support. A system administrator has the option to manage a VSwitch by user, by port number, or using a combination of the two methods. While the management of USERBASED and PORTBASED VSwitches is simplified, Live Guest Relocation of a guest connected to a VSwitch still requires the destination system to have a VSwitch with a PORTBASED or USERBASED designation matching that of the source system.
  • RACF security policy enhancements: With the available PTFs for APARs VM65930 and VM65982, the z/VM RACF Security Server feature supports the following security policy enhancements:
    • Read-Only Auditor (ROAUDIT): This new user role allows many of the common auditing tasks to be performed without the ability to modify settings or manipulate audit logs.
    • XAUTOLOG..ON control: This enhancement introduces new security policy requirements for the ON operand of the CP XAUTOLOG command. This changes default behavior of this operand when an ESM is installed on your system.
    • List the current VMXEVENT profile: This enhancement updates the SETEVENT LIST command to provide an authorized user with the names of the VMXEVENT profiles activated and in use by RACF.

      Note: The PTF for APAR VM65923 provides infrastructure support in z/VM V6.2, V6.3, and V6.4 and must be installed on all the members of an SSI cluster before any V6.4 member is running with the PTF for APAR VM65930.

  • Crypto Express APVIRT support for the z/VM TLS/SSL server and LDAP/VM: With the available PTF for APAR PI72106, the z/VM System SSL cryptographic library is updated to offload cryptographic operations to Crypto Express hardware associated with your IBM Z or LinuxONE hardware, which may improve performance. This support is intended for clear-key RSA operations. To enable this support, add the CRYPTO APVIRTUAL statement to the pertinent service virtual machine entries in the z/VM User Directory.
  • EAV minidisk support: With the PTFs for APARs VM65943 and VM65945, planned to be available August 25, 2017, enhanced EAV support for 3390-A DASD devices supporting 28-bit cylinder addresses is provided. This support will allow non-fullpack minidisks to reside anywhere on the volume, including beyond the current restriction of the 64K cylinder boundary (0-65519), and up to the one terabyte limit currently supported.
  • Dump processing enhancements: With the available PTF for APAR VM65989, the amount of time it takes for z/VM to write a hard abend or snap dump to 3390 DASD may be reduced. The improvements were achieved via changes to the I/O channel program used to write central memory to z/VM spool space located on 3390 DASD. This APAR also provides support for reducing dump size by excluding PGMBKs from snap dumps.
  • Alternate subchannel set dynamic I/O support: With the PTF for APAR VM65942, planned to be available August 25, 2017, z/VM V6.4 provides dynamic I/O commands within the z/VM hypervisor for supporting define, modify, and delete of a device within either the default or alternate subchannel sets. HCD support is currently not available.

z/VSE support for the IBM z14

z/Architecture support: Starting with z/VSE V5.2, z/VSE and its stand-alone utilities run entirely in z/Architecture mode.

Access to a Parallel Sysplex environment

Parallel Sysplex is a synergy between hardware and software - a highly advanced technology for clustering designed to enable the aggregate capacity of multiple z/OS systems to be applied against common workloads. z/OS combined with z14, z13, z13s, zEC12, and zBC12 servers, Coupling Facilities, Server Time Protocol (STP), Parallel Sysplex InfiniBand (PSIFB) 1x and 12x coupling links, and ICA SR and CE LR coupling links, depending on processor type, allows you to harness the power of multiple systems as though they were a single logical computing system.

Coupling links provide a path to transmit and receive Coupling Facility (CF) data as well as Server Time Protocol (STP) timekeeping messages. The CF data may be exchanged between z/OS and the CF or between CFs.

STP - Time synchronization for Parallel Sysplex Server Time Protocol (STP) is designed to allow events occurring in different servers to be properly sequenced in time. STP is designed for servers that have been configured in a Parallel Sysplex or a basic sysplex (without a Coupling Facility), as well as servers that are not in a sysplex but need time synchronization.

STP is a server-wide facility that is implemented in the Licensed Internal Code (LIC), presenting 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 between servers. The STP design introduced a concept called Coordinated Timing Network (CTN), a collection of servers and Coupling Facilities that are time-synchronized to a time value called Coordinated Server Time.

STP enhancements

IBM z14 will introduce an additional stratum level 4 for Server Time Protocol (STP) synchronization. With the additional stratum level, STP can synchronize systems up to 3 steps away from the Current Time Server (CTS). Prior systems allowed synchronization only up to level 3, or up to 2 steps from the CTS. This additional stratum level is not intended for long-term use; rather, it is specifically intended for short-term use during configuration changes for large timing networks, to avoid some of the cost and complexity caused by being constrained to a 3-stratum timing configuration.

IBM z14 will also introduce a new Graphical User Display for the STP network and configuration. The new user interface has been revamped for a quick, intuitive view of the various pieces of the STP relationship network map, including the status of the components of the timing network. The new z14 support allows the new level of HMC to manage older systems using the same new interface.

Parallel Sysplex enhancements

A number of exciting new enhancements are available for IBM z14 for use within Parallel Sysplex environments.

For long range coupling connectivity, the new Coupling Express Long Reach (CE LR) link (FC # 0433) is available with z14. This CE LR link is concurrently being made available on, and is compatible with z13 and z13s systems, which allows for sysplex connectivity back to these systems. Unlike the 1x IFB InfiniBand coupling links, which were plugged into the processor drawer, the CE LR link is plugged within a PCIe I/O drawer slot, taking advantage of more industry-standard I/O technology, such as converged Ethernet. The location inside the PCIe I/O drawer allows users to fan links out across multiple 2-port CE LR cards, up to a maximum of 32 features (64 links maximum) for z14 and z13 servers, and up to a maximum of 16 features (32 links maximum) for z13s servers, in 2 link increments. Compared to the HCAO-3 IFB InfiniBand LR with 4-port and 4-link increments, the CE LR link allows for more granularity when scaling up or completing maintenance. Link performance is similar to the InfiniBand 1x coupling link and uses identical single mode fiber. The CE LR link provides point-to-point coupling connectivity at distances of 10 km unrepeated and 100 km with a qualified dense wavelength division multiplexing (DWDM) device.

Per prior Statements of Direction, IBM will remove support for both the HCA3-O LR fanout for 1x IFB InfiniBand coupling links and the HCA3-O fanout for the 12x IFB InfiniBand coupling links for future high-end and midrange IBM Z systems. The z14 server will be the last high-end IBM Z server to support HCA3-O LR 1x IFB InfiniBand coupling links or HCA3-O 12x IFB InfiniBand coupling links, while z13s is the last midrange IBM Z server to support the HCA3-O LR 1x IFB InfiniBand coupling links or HCA3-O 12x IFB InfiniBand coupling links.

IBM Z enterprises should plan to migrate off of InfiniBand coupling links.

  • For high-speed short-range coupling connectivity, enterprises should migrate to the Integrated Coupling Adapter (ICA-SR).
  • For long-range coupling connectivity, enterprises should migrate to the new CE LR coupling adapter. For long-range coupling connectivity requiring a DWDM, enterprises will need to determine their desired DWDM vendor's plan to qualify the CE LR. Reference Hardware Announcement 117-031, dated March 2017.

Coupling Facility (CF) processor scalability: The IBM z14 provides a new level of the Coupling Facility Control Code (CFCC), CFLEVEL 22, which provides new capabilities as described below. Coupling Facility work management and dispatching changes for IBM z14 CFLEVEL 22 allow improved efficiency and scalability for Coupling Facility images. Together, these changes will improve the processor scalability and throughput for a CF image.

  • First, ordered work queues have been eliminated from the CF in favor of first-in / first-out queues, avoiding the overhead of maintaining ordered queues.
  • Second, protocols for system-managed duplexing have been simplified to avoid the potential for latching deadlocks between duplexed structures.
  • Third, the CF image is now able to use its processors in a specialized manner to perform specific work management functions when the number of processors in the CF image exceeds a threshold.

CF list notification enhancements: There are significant enhancements in z14 CFLEVEL 22 to CF notifications that inform users about the status of shared objects within a Coupling Facility. The combination of these notification enhancements provides flexibility to accommodate notification preferences among various CF exploiters, and yields more consistent, timely notifications.

  • First, structure notifications can use a round-robin scheme for delivering immediate and deferred notifications that avoids excessive "shotgun" notifications, reducing notification overhead.
  • Second, there is now an option for delivering "aggressive" notifications, which can drive a notification when new elements are added to a queue, providing initiative to get new work processed in a timely manner.
  • Third, notifications can now be driven when a queue transitions between full and not-full, allowing exploiters to redrive messages that could not previously be written to a full queue.

Coupling link constraint relief : IBM z14 provides additional physical coupling link connectivity compared to z13. The maximum number of physical ICA SR coupling links (ports) is increased from a maximum of 40 per CEC to 80 per CEC. These higher limits on z14 support higher levels of connectivity and physical consolidation using ICA SR, as well as the concurrent use of InfiniBand coupling, ICA SR, and CE LR links, for coupling link technology migration purposes.

CF encryption: z/OS V2.3 provides support for end-to-end encryption for both CF data in flight and data at rest in CF structures (as part of a more pervasive encryption solution). Host-based CPACF encryption is used for high performance and low latency. IBM z14 CFLEVEL 22 CF images are not required, but are recommended in order to simplify some sysplex recovery and reconciliation scenarios involving encrypted CF structures. (Note that the CF image itself never decrypts, nor encrypts, any data). IBM z14 z/OS images are not required, but are recommended for the improved AES CBC encrypt/decrypt performance that z14 provides.

Hardware Management Console (HMC)

HMC/SE user interface: The z14 Hardware Management Console and Support Element will support only the Tree Style user interface. The Classic Style user interface is no longer supported.

The following enhancements have been made to the Tree Style user interface to aid with new users of Tree Style as well as address pain points of existing users.

  • A new Masthead with Favorites and Search controls will help users quickly find and launch tasks.
  • Tasks will now open in tabs within the user interface (instead of separate browser windows) to make finding and managing running tasks easier.
  • There is also the ability to have the task tab 'pop-out' into a separate window, giving users the ability to have a similar parallel task display window as on previous Tree Style controls and allowing the task displays to be viewed on other physical displays.

Manage System Time: The Manage System Time task replaces the System (Sysplex) Time task on HMC. The new Manage System Time task provides a simplified workflow for system time management including:

  • Improved help tools to complement and improve system administrator skills:
    • Inline definition of technical terms.
  • Improved user experience with visual representation of configuration panels:
    • Guidance provided within the workflows.
    • Topology displays of system time networks.
    • Errors surfaced in visualization for easier problem resolution of setup errors.
  • Single point of system time management for multiple systems.

IBM Hardware Management Console (HMC) 2.14.0 security enhancements: New security features in the Hardware Management Console (HMC) 2.14.0 available with IBM z14 include Multifactor Authentication, Enhanced Computing in support of NIST Standard 800-147B, Crypto Compliance Levels, FTP through HMC, SNMP/BCPii API Security Controls, Secure Console to Console Communication Enhancements, Remote Browser IP Address Limiting, and more.

  • Multifactor Authentication: The Hardware Management Console will now offer an optional control of Multifactor Authentication in addition to the userid/password controls provided today. If the Multifactor option is selected for a given user, that user will now be required to enter a second authentication factor using a TOTP (Time-based One-Time Password) defined by RFC 6238. RFC 6238 is implemented by freely available smartphone and web apps utilizing a secret key provided per HMC user.
  • HMC Mobile for Z and LinuxONE: New iOS and Android mobile apps are planned to be available for the HMC 2.14.0 supporting z14, z13, and z13s systems. HMC Mobile will help enable HMC users to securely monitor and manage systems from anywhere. The apps provide system and partition views, status monitoring, hardware messages, operating system messages, and the ability to receive push notifications from the HMC using the existing zRSF (z Systems Remote Support Facility) connection. HMC Mobile is disabled by default and, once enabled, provides a robust set of security controls. Administrators can restrict usage to specific HMC users and IP addresses, require the use of app passwords, enable multifactor authentication, restrict the app to read-only access, and more.
  • Firmware tamper detection : z14 will also offer an enhancement on the Support Element that provides notification if tampering with booting of firmware on the server (CPC) is detected. This enhancement is designed to meet the BIOS Protection Guidelines recommended and published by the National Institute of Standards and Technology (NIST) in Special Publication 800-147B. If tampering is detected, the Support Element will issue a customer alert via a warning or a lock of the Support Element, depending on the configuration. If "call home" support is enabled on a z14 Hardware Management Console managing the Support Element, additional analysis of the Support Element will be performed and displayed by IBM Resource Link.

    In addition to this support, the Hardware Management Console also has been enhanced to provide attempted tamper monitoring and reporting. A newly manufactured Hardware Management Console directly ordered with z14, or at a later time, is required for this protection. Any detected events of attempted tampering will be logged and will issue a customer alert via a warning or a lock of the Hardware Management Console, depending on setup configuration. In addition, if "call home" support is enabled on the Hardware Management Console, supplementary analysis of events logged by the Hardware Management Console will be available on IBM Resource Link.

    Although customers can carry forward their Hardware Management Consoles on z14, these tamper protection capabilities will be delivered only on newly manufactured Hardware Management Consoles. The z14 environment can contain both Hardware Management Consoles that have been carried forward and newly manufactured Hardware Management Consoles.

  • IBM Enhanced Remote Support Facility: The IBM Enhanced Remote Support Facility was first introduced on zEC12/zBC12 systems and for those systems and z13/z13s, both the Enhanced and Legacy Remote Support Facility support could be utilized. The Enhanced support provided improved problem data uploads and fix data downloads. z14 processors will no longer connect to the legacy IBM Support Facility.
    • z14 HMCs supporting older z10EC/z10BC - z13 systems will still require connections to the legacy IBM Support Facility.
    • z14 HMCs supporting only z14 systems only require IBM Enhanced Support Facility connections.
    • A connection to the IBM Enhanced Support Facility is required to support z14 HMCs regardless of the CPC they are supporting.

    If you had not previously configured firewalls and proxy support with the ability to connect to the Enhanced Support Facility, this will be required for z14 HMC and CPC connections per above rules.

  • Global OSA/SF: The HMC Global OSA/SF will now provide a global view of all OSA PCHIDs and the monitoring and diagnostic information previously available in the Query Host command.
  • New characters supported for Load parms: Starting with z14 the Load parameter for Load task, Activation Load and Image Profiles will now allow three new characters: @#$. z13/z13s or older systems support a character set of A-Z, 0-9, "." (period) and " " (blanks). z14 systems will support a character set of A-Z, 0-9, "." (period), " " (blanks), "@", "#", and "$".
  • FTP through HMC: To maximize security features, IBM recommends that customers keep their IBM Z on a dedicated network with one HMC network used for that network and the second HMC network used for outward communication (IBM Support Facility, remote browsing, automation). However, for systems prior to z14, this created a security challenge for FTP operations originating from the SE. Customers have to either put their FTP server on the IBM Z dedicated network or put their IBM Z on their intranet network.

    Starting with z14, all FTP operations originating from the SE will be proxied through a managing HMC. This now allows the FTP SE originated operations to follow IBM security recommendations. In addition, all HMC/SE tasks that support FTP will provide three options of FTP: FTP, FTPS, and SFTP.

    • FTPS is SSL based and uses certificates to authenticate servers.
    • SFTP is SSH based and uses SSH keys to authenticate servers.
    • Username and passwords are required for client authentication in all three protocols.
  • Console to console communications: HMC consoles have used anonymous cipher suites for some inter-console communication purposes. These cipher suites, while providing encryption and integrity validation, do not provide cryptographic authentication. Network security scanners can detect this, and anonymous cipher suites may not be acceptable to some customers' security policies. Starting with the IBM z14 HMC/SE, the console to console communications solution, when security is enabled, will no longer use anonymous cipher suites and will begin using an industry standard based password driven cryptography system. This system provides cryptographic encryption, integrity validation, and authentication.
  • SNMP/BCPii API enhancements: Prior to z14, when you enabled SNMP BCPii via controls for the HMC/SE, it was enabled for all LPARs to have equal send and receive command capability. Starting with z14 there are new "BCPii Permission" controls which allow you to have granular LPAR/System BCPii command controls. The HMC/SE can be configured for Enable/disable send capability, Enable/disable receive capability, Enable for all senders, and Enable for list of origin partitions. These controls can be specified for CPC via the System Details task (HMC or SE) or can be specified for Images via the Image profile and Change LPAR Security task (HMC or SE). Some additional changes have been made to improve the performance for z/OS BCPii, for query operations Profiles, LPAR Controls/Security data, and EC/MCL data.
  • Removal of Common Infrastructure Module (CIM) Management Interface: The HMC 2.14.0 will no longer support the Hardware Console Common Infrastructure Module (CIM) Management Interface. The Hardware Management Console Simple Network Management Protocol (SNMP), and Web Services Application Programming Interfaces (APIs) will continue to be supported.

Enhancements to software pricing Technology Transition Offerings:

Complementing the z14 server, IBM is introducing:

  • A new Technology Transition Offering (TTO) called Technology Update Pricing for the IBM z14.
  • New and revised Transition Charges for Sysplexes or Multiplexes TTOs for actively coupled Parallel Sysplexes (z/OS), Loosely Coupled Complexes (z/TPF), and Multiplexes (z/OS and z/TPF).

Technology Update Pricing for the IBM z14 extends the software price/performance provided by AWLC and CMLC for z14 servers. The new and revised Transition Charges for Sysplexes or Multiplexes offerings provide a transition to Technology Update Pricing for the IBM z14 for customers who have not yet fully migrated to z14 servers. This ensures that aggregation benefits are maintained and also phases in the benefits of Technology Update Pricing for the IBM z14 pricing as customers migrate.

When a z14 server is in an actively coupled Parallel Sysplex or a Loosely Coupled Complex, you may choose either aggregated Advanced Workload License Charges (AWLC) pricing or aggregated Parallel Sysplex License Charges (PSLC) pricing, subject to all applicable terms and conditions.

When a z14 server is part of a Multiplex under Country Multiplex Pricing (CMP) terms, Country Multiplex License Charges (CMLC), Multiplex zNALC (MzNALC), and Flat Workload License Charges (FWLC) are the only pricing metrics available, subject to all applicable terms and conditions.

When a z14 server is running z/VSE, you may choose Mid-Range Workload License Charges (MWLC), subject to all applicable terms and conditions.

For more information about AWLC, CMLC, MzNALC, PSLC, MWLC, or the Technology Update Pricing and Transition Charges for Sysplexes or Multiplexes TTO offerings, refer to the Software Pricing website.

Machines eligible to participate in Country Multiplex Pricing

The z14 is the first new generation of IBM Z hardware since the introduction of Country Multiplex Pricing (CMP).

At the time a client first implements a Multiplex, machines currently eligible to be included in the new Multiplex cannot be older than two generations prior to the most recently available server. The most recent server at any given point in time will be considered generation N, and the prior two generations as N-1 and N-2 respectively.

IBM Z hardware family generations concurrent with the general availability of the z14:

Full name            Short Machine CMP
                     name  type    Machine
                                   Generation
                                   as of 13
                                   Sep 2017
-------------------- ----- ------- ----------
IBM z14              z14   3906    N
IBM z13              z13   2964    N-1
IBM z13s             z13s  2965    N-1
IBM zEnterprise EC12 zEC12 2827    N-2
IBM zEnterprise BC12 zBC12 2828    N-2
IBM zEnterprise 196  z196  2817    N-3
IBM zEnterprise 114  z114  2818    N-3

Concurrent with the general availability of the z14, the z196 and z114 machines will be designated as previously eligible CMP machines.

Clients are not eligible to create a Multiplex until machines running z/OS or z/TPF (along with any associated CBU machines) that are older than generation N-2 are upgraded, or that workload is transferred to eligible machines, or the older ineligible machines are converted to no longer run z/OS nor z/TPF software. Once a client establishes a Multiplex they may keep the machines originally included in their Multiplex indefinitely, including any machines subsequently designated as previously eligible. Going forward, any machine to be added to an existing Multiplex must conform to the machine types that satisfy the generation N, N-1, and N-2 criteria at the time that machine is added.

Upon the general availability of the z14 (generation N), clients who are still using a generation N-3 machine (z196 or z114) will have a 3-month grace period to transition into CMP while including that generation N-3 machine. This means the client's first CMP invoice must happen the month following 90 days from the general availability of the z14 (September 13, 2017) which means any transition into CMP for a client with a z196 or z114 machine running z/OS or z/TPF must occur no later than January 1, 2018.

Accessibility by people with disabilities

A US Section 508 Voluntary Product Accessibility Template (VPAT) containing details on accessibility compliance can be found on the IBM Accessibility website.

Section 508 of the US Rehabilitation Act

IBM z14 servers are capable on delivery, when used in accordance with IBM's associated documentation, of satisfying the applicable requirements of Section 508 of the Rehabilitation Act of 1973, 29 U.S.C. Section 794d, as implemented by 36 C.F.R. Part 1194, provided that any Assistive Technology used with the Product properly interoperates with it.

IBM makes no representation about the Section 508 status of these third-party products included in this offering. Contact the vendor for specific, current information on the Section 508 status of these products.
Back to topBack to top
 

Product positioning

IT today is experiencing a time of exponential growth in data and transaction volumes driven by digital transformation. Businesses must be able to manage, store, and protect the information, and, most important, use it for competitive advantage. This is creating the demand to apply intelligence and insight to the data to build new services wrapped for a customized user experience. From a user perspective, IT must create an environment where users have confidence that data is protected and available from anywhere and any device. This ability to be fast and flexible in delivery of new services, with insight and security, will differentiate a business. The z14 delivers unique capabilities to help with that differentiation.

At the core of every enterprise lies core business data, assets which if lost or compromised could often cause irreparable damage. Core business data is also often governed by regulatory requirements designed to protect data and safeguard privacy, often with high penalties in the event of loss or inadvertent disclosure. Internal and external pressures to protect customer data have changed the perspective around how core business data should be handled and protected. Establishing a "perimeter" around core data using encryption is one of the most impactful ways to protect data and prevent against loss. The objective is to create a fortified perimeter around core business data, wherever it may physically reside. The IBM z14 platform provides pervasive encryption capabilities designed to enable you to protect data efficiently, and without requiring application changes.

The IBM z14 platform provides the hardware infrastructure, in a balanced system design, with the encryption capabilities that now make it possible to create a fortified perimeter around critical business data. The Central Processor Assist for Cryptographic Function (CPACF), is standard on every z14 core, and is enabled via feature code #3863. The CPACF has both the cryptographic suite and performance characteristics that can enable bulk encryption of sensitive business data that makes it possible to fortify, intrinsically protecting business data using encryption technology. Working with the new Crypto Express6S feature (#0893), the key materials used to create this fortified data perimeter are protected, using the IBM Z unique protected key CPACF in which the keys used in the encryption process are not visible to the applications and operating system in clear text form.

The IBM Z operating environments, such as z/OS, are designed to take advantage of the z14 platform imbedding the use of the z14 cryptographic engines within the operating environment to help create an environment where policies can be enforced that govern intrinsic data protection, helping clients build the perimeter around business data.

The z14 provides the infrastructure to meet the demands of a digital business. With up to 170 configurable cores, z14 has performance and scaling advantages over prior generations, and more capacity than the z13 141-way. The FICON Express16S+ features (#0427 and 0428) deliver an increase in I/O rates and in link bandwidth, and a reduction in single-stream latency, providing the system the ability to absorb large applications and transaction spikes driven by unpredictable mobile and IoT devices. Next-generation SMT on z14 delivers improved virtualization performance to benefit Linux. High-speed connectivity out to the data is critical in achieving exceptional levels of transaction throughput. The IBM zHyperLink Express adapter (#0431) is a direct connect short distance, IBM Z I/O adapter offering extremely low latency connectivity to FICON storage systems.

With up to 32 TB of real memory, z14 can open opportunities such as in-memory data marts, large buffer pools for data access, and in-memory analytics while giving you the necessary room to tune applications for optimal performance. By exploiting the Vector Packed Decimal Facility that allows packed decimal operations to be performed in registers rather than memory, using new fast mathematical computations, compilers, such as Enterprise COBOL for z/OS, V6.2, Enterprise PL/I for z/OS, V5.2, z/OS V2.3 XL C/C++, the COBOL optimizer, Automatic Binary Optimizer for z/OS, V1.3, and Java, are optimized on z14. These compilers and optimizer are designed to help improve application performance, reduce CPU usage, and reduce operating costs. Java improvements and the use of crypto acceleration will deliver additional improvements in throughput per core, which gives a natural boost to z/OS Connect EE, WebSphere Liberty in CICS, Spark for z/OS, and IBM Java for Linux on z Systems.

To take advantage of new unstructured data, businesses on IBM Z can leverage the use of application programming interfaces (APIs) that can help with the creation and delivery of innovative new services. Linux on z Systems brings additional value to the platform in the form of the co-location advantages in performance and operational efficiency by running Linux side-by-side with z/OS, z/VSE, or z/TPF, as well as providing a unique Linux platform for any Linux solution requiring high availability, security, or scalability. Linux on z Systems supports a wealth of new IBM, ISV, and open source products. Many are familiar to application developers, such as Go, Python, Scala, Node.js, Docker, Spark, MongoDB, PostgreSQL, and MariaDB. Access to data previously unavailable, without the need for Extract Transform and Load (ETL), will allow development of intelligent transactions and intuitive business processes.
Back to topBack to top
 

Models

Model summary matrix

Model PU Memory (Notes 1 and 2) IFB Coupling Fanouts PCIe Fanouts PCIe IO Drawer (Note 3)
M01 1 to 33 256 to 8000 GB 4 2 to 10 0 to 3 (Note 4)
M02 1 to 69 8512 to 16,192 GB 8 2 to 20 0 to 5
M03 1 to 105 16,704 to 24,384 GB 12 2 to 30 0 to 5
M04 1 to 141 24,896 to 32,576 GB 16 2 to 40 0 to 5
M05 1 to 170 24,896 to 32,576 GB 16 2 to 40 0 to 5

  1. An additional 192 GB of memory is shipped and reserved for HSA. One additional memory channel is dedicated for RAIM. Every fifth DIMM configured is reserved for this purpose.

  2. IBM Virtual Flash Memory (VFM) may reduce the amount of memory per model.

  3. Offerings are the same for both air cooled machines and water cooled machines.

  4. Three physical drawers, 2.5 accessible drawers

Processor Unit Summary

Listed below are the minimums and maximums of processor units (PUs) that may be purchased permanently. The feature codes affected are listed in parentheses.

Model Total PUs Available for Use CP7s (#1932) Min/Max IFLs (#1933) Min/Max uIFLs (#1937) Min/Max IFCs (#1934) Min/Max zIIPs (#1936) Min/Max Optional SAPs (#1935) Min/Max
M01 33 0 to 33 0 to 33 0 to 32 0 to 33 0 to 22 0 to 4
M02 69 0 to 69 0 to 69 0 to 68 0 to 69 0 to 46 0 to 8
M03 105 0 to 105 0 to 105 0 to 104 0 to 105 0 to 70 0 to 12
M04 141 0 to 141 0 to 141 0 to 140 0 to 141 0 to 94 0 to 16
M05 170 0 to 170 0 to 170 0 to 169 0 to 170 0 to 112 0 to 16

Notes:

  1. There are two Spares per system.

  2. The total number of PUs purchased cannot exceed the total number available for that model.

  3. One CP, one IFL (#1933), or one ICF (#1934) must be installed with the installation of any uIFLs or prior to the installation of any uIFLs.

  4. One CP must be installed with the installation of any zIIPs or prior to the installation of any zIIPs.The total number of zIIPs (#1936) purchased cannot exceed twice the number of CPs purchased for any machine.

  5. CP4, CP5, and CP6 are limited to a maximum of 33 PUs regardless of model.

  6. The number of SAPs provided to the customer as standard PUs are as follows:
    • Model M01 = five SAPs
    • Model M02 = ten SAPs
    • Model M03 = fifteen SAPs
    • Model M04 = twenty SAPs
    • Model M05 = twenty three SAPs

Customer setup (CSU)

Customer setup is not available on this machine.

Devices supported

The hardware requirements for the IBM Z servers, their features and functions are identified. A new driver level is required. HMC (V2.14.0) plus MCLs and the Support Element (V2.14.0) are available on September 13, 2017 .

You should review the PSP buckets for minimum Machine Change Levels (MCLs) and software PTF levels before IPLing operating systems.

Peripheral hardware and device attachments

IBM devices previously attached to IBM System z10, z196, zEC12, z13 and zSeries servers are supported for attachment to IBM z14 channels, unless otherwise noted. The subject I/O devices must meet the FICON and Fibre Channel Protocol (FCP) architectures to be supported. I/O devices that meet OEMI architecture requirements are supported only using an external converter. Prerequisite Engineering Change Levels may be required. For further detail, contact IBM service personnel.

While the z14 supports devices as described above, IBM does not commit to provide support or service for an IBM device that has reached its End of Service effective date as announced by IBM.

Note: IBM cannot confirm the accuracy of performance, compatibility, or any other claims related to non-IBM products. Questions regarding the capabilities of non-IBM products should be addressed to the suppliers of those products.

Information on switches and directors qualified for IBM Z FICON and FCP channels can be found in the Library section of Resource Link:

  • https://www.ibm.com/servers/resourcelink

Model conversions

From    From  To      To
Machine Model Machine Model     Description
type          type
------- ----- ------- ----- --- --------------
2827    H20   3906    M01   (1) H20 r to M01 a
2827    H20   3906    M02   (1) H20 r to M02 a
2827    H20   3906    M03   (1) H20 r to M03 a
2827    H20   3906    M04   (1) H20 r to M04 a
2827    H20   3906    M05   (1) H20 r to M05 a
2827    H20   3906    M01   (1) H20 r to M01 w
2827    H20   3906    M02   (1) H20 r to M02 w
2827    H20   3906    M03   (1) H20 r to M03 w
2827    H20   3906    M04   (1) H20 r to M04 w
2827    H20   3906    M05   (1) H20 r to M05 w
2827    H43   3906    M01   (1) H43 r to M01 a
2827    H43   3906    M02   (1) H43 r to M02 a
2827    H43   3906    M03   (1) H43 r to M03 a
2827    H43   3906    M04   (1) H43 r to M04 a
2827    H43   3906    M05   (1) H43 r to M05 a
2827    H43   3906    M01   (1) H43 r to M01 w
2827    H43   3906    M02   (1) H43 r to M02 w
2827    H43   3906    M03   (1) H43 r to M03 w
2827    H43   3906    M04   (1) H43 r to M04 w
2827    H43   3906    M05   (1) H43 r to M05 w
2827    H66   3906    M01   (1) H66 r to M01 a
2827    H66   3906    M02   (1) H66 r to M02 a
2827    H66   3906    M03   (1) H66 r to M03 a
2827    H66   3906    M04   (1) H66 r to M04 a
2827    H66   3906    M05   (1) H66 r to M05 a
2827    H66   3906    M01   (1) H66 r to M01 w
2827    H66   3906    M02   (1) H66 r to M02 w
2827    H66   3906    M03   (1) H66 r to M03 w
2827    H66   3906    M04   (1) H66 r to M04 w
2827    H66   3906    M05   (1) H66 r to M05 w
2827    H89   3906    M01   (1) H89 r to M01 a
2827    H89   3906    M02   (1) H89 r to M02 a
2827    H89   3906    M03   (1) H89 r to M03 a
2827    H89   3906    M04   (1) H89 r to M04 a
2827    H89   3906    M05   (1) H89 r to M05 a
2827    H89   3906    M01   (1) H89 r to M01 w
2827    H89   3906    M02   (1) H89 r to M02 w
2827    H89   3906    M03   (1) H89 r to M03 w
2827    H89   3906    M04   (1) H89 r to M04 w
2827    H89   3906    M05   (1) H89 r to M05 w
2827    HA1   3906    M01   (1) HA1 r to M01 a
2827    HA1   3906    M02   (1) HA1 r to M02 a
2827    HA1   3906    M03   (1) HA1 r to M03 a
2827    HA1   3906    M04   (1) HA1 r to M04 a
2827    HA1   3906    M05   (1) HA1 r to M05 a
2827    HA1   3906    M01   (1) HA1 r to M01 w
2827    HA1   3906    M02   (1) HA1 r to M02 w
2827    HA1   3906    M03   (1) HA1 r to M03 w
2827    HA1   3906    M04   (1) HA1 r to M04 w
2827    HA1   3906    M05   (1) HA1 r to M05 w
2827    H20   3906    M01   (1) H20 w toM01 w
2827    H20   3906    M02   (1) H20 w toM02 w
2827    H20   3906    M03   (1) H20 w toM03 w
2827    H20   3906    M04   (1) H20 w toM04 w
2827    H20   3906    M05   (1) H20 w toM05 w
2827    H43   3906    M01   (1) H43 w toM01 w
2827    H43   3906    M02   (1) H43 w toM02 w
2827    H43   3906    M03   (1) H43 w toM03 w
2827    H43   3906    M04   (1) H43 w toM04 w
2827    H43   3906    M05   (1) H43 w toM05 w
2827    H66   3906    M01   (1) H66 w toM01 w
2827    H66   3906    M02   (1) H66 w toM02 w
2827    H66   3906    M03   (1) H66 w toM03 w
2827    H66   3906    M04   (1) H66 w toM04 w
2827    H66   3906    M05   (1) H66 w toM05 w
2827    H89   3906    M01   (1) H89 w toM01 w
2827    H89   3906    M02   (1) H89 w toM02 w
2827    H89   3906    M03   (1) H89 w toM03 w
2827    H89   3906    M04   (1) H89 w toM04 w
2827    H89   3906    M05   (1) H89 w toM05 w
2827    HA1   3906    M01   (1) HA1 w toM01 w
2827    HA1   3906    M02   (1) HA1 w toM02 w
2827    HA1   3906    M03   (1) HA1 w toM03 w
2827    HA1   3906    M04   (1) HA1 w toM04 w
2827    HA1   3906    M05   (1) HA1 w toM05 w
2964    N30   3906    M01   (1) N30 a to M01 a
2964    N30   3906    M02   (1) N30 a to M02 a
2964    N30   3906    M03   (1) N30 a to M03 a
2964    N30   3906    M04   (1) N30 a to M04 a
2964    N30   3906    M05   (1) N30 a to M05 a
2964    N30   3906    M01   (1) N30 a to M01 w
2964    N30   3906    M02   (1) N30 a to M02 w
2964    N30   3906    M03   (1) N30 a to M03 w
2964    N30   3906    M04   (1) N30 a to M04 w
2964    N30   3906    M05   (1) N30 a to M05 w
2964    N63   3906    M01   (1) N63 a to M01 a
2964    N63   3906    M02   (1) N63 a to M02 a
2964    N63   3906    M03   (1) N63 a to M03 a
2964    N63   3906    M04   (1) N63 a to M04 a
2964    N63   3906    M05   (1) N63 a to M05 a
2964    N63   3906    M01   (1) N63 a to M01 w
2964    N63   3906    M02   (1) N63 a to M02 w
2964    N63   3906    M03   (1) N63 a to M03 w
2964    N63   3906    M04   (1) N63 a to M04 w
2964    N63   3906    M05   (1) N63 a to M05 w
2964    N96   3906    M01   (1) N96 a to M01 a
2964    N96   3906    M02   (1) N96 a to M02 a
2964    N96   3906    M03   (1) N96 a to M03 a
2964    N96   3906    M04   (1) N96 a to M04 a
2964    N96   3906    M05   (1) N96 a to M05 a
2964    N96   3906    M01   (1) N96 a to M01 w
2964    N96   3906    M02   (1) N96 a to M02 w
2964    N96   3906    M03   (1) N96 a to M03 w
2964    N96   3906    M04   (1) N96 a to M04 w
2964    N96   3906    M05   (1) N96 a to M05 w
2964    NC9   3906    M01   (1) NC9 a to M01 a
2964    NC9   3906    M02   (1) NC9 a to M02 a
2964    NC9   3906    M03   (1) NC9 a to M03 a
2964    NC9   3906    M04   (1) NC9 a to M04 a
2964    NC9   3906    M05   (1) NC9 a to M05 a
2964    NC9   3906    M01   (1) NC9 a to M01 w
2964    NC9   3906    M02   (1) NC9 a to M02 w
2964    NC9   3906    M03   (1) NC9 a to M03 w
2964    NC9   3906    M04   (1) NC9 a to M04 w
2964    NC9   3906    M05   (1) NC9 a to M05 w
2964    NE1   3906    M01   (1) NE1 a to M01 a
2964    NE1   3906    M02   (1) NE1 a to M02 a
2964    NE1   3906    M03   (1) NE1 a to M03 a
2964    NE1   3906    M04   (1) NE1 a to M04 a
2964    NE1   3906    M05   (1) NE1 a to M05 a
2964    NE1   3906    M01   (1) NE1 a to M01 w
2964    NE1   3906    M02   (1) NE1 a to M02 w
2964    NE1   3906    M03   (1) NE1 a to M03 w
2964    NE1   3906    M04   (1) NE1 a to M04 w
2964    NE1   3906    M05   (1) NE1 a to M05 w
2964    N30   3906    M01   (1) N30 w to M01 w
2964    N30   3906    M02   (1) N30 w to M02 w
2964    N30   3906    M03   (1) N30 w to M03 w
2964    N30   3906    M04   (1) N30 w to M04 w
2964    N30   3906    M05   (1) N30 w to M05 w
2964    N63   3906    M01   (1) N63 w to M01 w
2964    N63   3906    M02   (1) N63 w to M02 w
2964    N63   3906    M03   (1) N63 w to M03 w
2964    N63   3906    M04   (1) N63 w to M04 w
2964    N63   3906    M05   (1) N63 w to M05 w
2964    N96   3906    M01   (1) N96 w to M01 w
2964    N96   3906    M02   (1) N96 w to M02 w
2964    N96   3906    M03   (1) N96 w to M03 w
2964    N96   3906    M04   (1) N96 w to M04 w
2964    N96   3906    M05   (1) N96 w to M05 w
2964    NC9   3906    M01   (1) NC9 w to M01 w
2964    NC9   3906    M02   (1) NC9 w to M02 w
2964    NC9   3906    M03   (1) NC9 w to M03 w
2964    NC9   3906    M04   (1) NC9 w to M04 w
2964    NC9   3906    M05   (1) NC9 w to M05 w
2964    NE1   3906    M01   (1) NE1 w to M01 w
2964    NE1   3906    M02   (1) NE1 w to M02 w
2964    NE1   3906    M03   (1) NE1 w to M03 w
2964    NE1   3906    M04   (1) NE1 w to M04 w
2964    NE1   3906    M05   (1) NE1 w to M05 w
3906    M01   3906    M02   (1) M01 a to M02 a
3906    M01   3906    M03   (1) M01 a to M03 a
3906    M01   3906    M04   (1) M01 a to M04 a
3906    M02   3906    M03   (1) M02 a to M03 a
3906    M02   3906    M04   (1) M02 a to M04 a
3906    M03   3906    M04   (1) M03 a to M04 a
3906    M01   3906    M02   (1) M01 w to M02 w
3906    M01   3906    M03   (1) M01 w to M03 w
3906    M01   3906    M04   (1) M01 w to M04 w
3906    M02   3906    M03   (1) M02 w to M03 w
3906    M02   3906    M04   (1) M02 w to M04 w
3906    M03   3906    M04   (1) M03 w to M04 w

Note: (1) Parts removed or replaced become the property of IBM and must be returned.

Feature conversions

The feature conversion list for IBM z14 is now available in the Library section of Resource Link. This list can be obtained at Resource Link by accessing the following website:

https://www.ibm.com/servers/resourcelink/lib03011.nsf/pages/39 06FeatureConversions?OpenDocument

Using the instructions on the Resource Link panels, obtain a user ID and password. Resource Link has been designed for easy access and navigation.
Back to topBack to top
 

Technical description
TOC Link Physical specifications TOC Link Operating environment TOC Link Limitations
TOC Link Hardware requirements TOC Link Software requirements


Physical specifications

Physical specifications - IBM z14 Air Cooled Machine

Dimensions (rounded to the nearest 0.1 in or 0.1 cm):

Systems with all covers

                                 Depth Width Height
                                 (3)
-------------------------------- ----- ----- ------
Inches                           73.5  63.6  79.3
Centimeters                      186.7 156.5 201.3
Inches (O/H I/O cable exit)      73.5  72.7  84.8(2)
Centimeters (O/H I/O cable exit) 186.7 184.7 215.3

Note: (2) The height with overhead I/O cable exit differs from the standard height only with the optional optical cable organizer feature installed.

Note: (3) System depth for air cooled machines with thin covers is reduced by 14.7 in (37.33cm).

Systems with all covers and height reduction

            Depth Width Height
            (4)
----------- ----- ----- ------
Inches      73.5  61.6  70.3
Centimeters 186.7 156.5 178.5

Note: (4) System depth for air cooled machines with thin covers is reduced by 14.7 in (37.33 cm).

Each frame with one side cover and without packaging

            Depth Width Height
            (5)
----------- ----- ----- ------
Inches      50.0  30.7  79.3
Centimeters 127.0 78.0  201.3

Note: (5) System depth for air cooled machines with thin covers is reduced by 14.7 in (37.33 cm).

Each frame on casters with one side cover and with packaging (domestic)

            Depth Width Height
            (6)
----------- ----- ----- ------
Inches      57.4  32.4  79.8
Centimeters 145.8 82.2  202.6

Note: (6) System depth for air cooled machines with thin covers is reduced by 14.7 in (37.33 cm).

Each frame with one side cover and with packaging (ARBO crate)

            Depth Width Height
            (7)
----------- ----- ----- ------
Inches      63.4  36.5  87.6
Centimeters 161.0 92.7  222.5

Note: (7) System depth for air cooled machines with thin covers is reduced by 14.7 in (37.33 cm).

Approximate weight:

System with IBF feature

                        Newbuild Newbuild
                        Minimum  Maximum
                        System   System
                        Model    Model
                        M01 No   M05 Max
                        I/O      # of I/O
                        drawer   drawers
----------------------- -------- --------
kg                      1461     2705
lb                      3219     5961
kg (O/H I/O cable exit) 1531     2775
lb (O/H I/O cable exit) 3375     6117

System without IBF feature

                        Newbuild Newbuild
                        Minimum  Maximum
                        System   System
                        Model    Model
                        M01 No   M05 Max
                        I/O      # of I/O
                        drawer   drawers
----------------------- -------- --------
kg                      1258     2400
lb                      2772     5290
kg (O/H I/O cable exit) 1328     2471
lb (O/H I/O cable exit) 2928     5446

To ensure installability and serviceability in non-IBM industry-standard racks, review the installation planning information for any product-specific installation requirements.

The dc power feature has no effect on the machine dimensions and weight.

Physical specifications - IBM z14 Water Cooled Machine

Dimensions (rounded to the nearest 0.1 in or 0.1 cm):

Systems with all covers

                                 Depth Width Height
-------------------------------- ----- ----- ------
Inches                           77.5  61.6  79.3
Centimeters                      196.9 156.5 201.3
Inches (O/H I/O cable exit)      77.5  72.7  84.8(8)
Centimeters (O/H I/O cable exit) 196.9 184.7 215.3

Note: (8) The height with overhead I/O cable exit differs from the standard height only with the optional optical cable organizer feature installed.

Systems with all covers and height reduction

            Depth Width Height
----------- ----- ----- ------
Inches      77.5  61.6  70.3
Centimeters 196.9 156.5 178.5

Each frame with one side cover and without packaging

            Depth Width Height
----------- ----- ----- ------
Inches      54.0  30.7  79.3
Centimeters 137.2 78.0  201.3

Each frame on casters with one side cover and with packaging (domestic)

            Depth Width Height
----------- ----- ----- ------
Inches      61.4  32.4  79.8
Centimeters 156.0 82.2  202.6

Each frame with one side cover and with packaging (ARBO crate)

            Depth Width Height
----------- ----- ----- ------
Inches      68.0  36.5  87.6
Centimeters 171.7 92.7  222.5

Approximate weight:

System with IBF feature

                        Newbuild Newbuild
                        Minimum  Maximum
                        System   System
                        Model    Model
                        M01 No   M05 Max
                        I/O      # of I/O
                        drawer   drawers
----------------------- -------- --------
kg                      1518     2752
lb                      3346     6065
kg (O/H I/O cable exit) 1589     2823
lb (O/H I/O cable exit) 3502     6221

System without IBF feature

                        Newbuild Newbuild
                        Minimum  Maximum
                        System   System
                        Model    Model
                        M01 No   M05 Max
                        I/O      # of I/O
                        drawer   drawers
----------------------- -------- --------
kg                      1343     2447
lb                      2961     5394
kg (O/H I/O cable exit) 1589     2518
lb (O/H I/O cable exit) 3081     5550

To ensure installability and serviceability in non-IBM industry-standard racks, review the installation planning information for any product-specific installation requirements.

The dc power feature has no effect on the machine dimensions and weight.

Operating environment

Operating environment - IBM z14 Air Cooled Machine

Environmental class - ASHRAE 3

Temperature: 5 to 40 degrees C (41 to 104 degrees F) for all models up to 900 meters above sea level; maximum ambient reduces 1 degree C per 300 meters above 900 meters.

Relative Humidity: 8 to 85 (percent) Wet Bulb (Caloric Value): 25 degrees C (77 degrees F)

Operating Mode Max Dew Point: 24 degrees C (75.2 degrees F) - Operating Mode

Electrical Power (maximum)

Utility      M01      M02      M03      M04      M05      Power
                                                          Factor
------------ -------- -------- -------- -------- -------- ------
200-240 V ac 10.4 kVA 19.0 kVA 23.3 kVA 28.3 kVA 29.9 kVA 0.996
380-415 V ac 10.6 kVA 19.3 kVA 23.8 kVA 28.9 kVA 30.6 kVA 0.978
480 V ac     10.9 kVA 20.0 kVA 24.7 kVA 29.9 kVA 31.6 kVA 0.961
400 V dc     10.1 kW  18.3 kW  22.6 kW  27.4 kW  29.0 kW  -

Capacity of Exhaust: 6370 cubic meters / hour (3800 CFM)

Noise level:

  • Typical Configuration (Model M02):
    • Declared A-Weighted Sound Power Level, LWAd(B) = 7.8
    • Declared A-Weighted Sound Pressure Level, LpAm(dB) = 59
  • Maximum Configuration (Model M05):
    • Declared A-Weighted Sound Power Level, LWAd(B) = 8.1
    • Declared A-Weighted Sound Pressure Level, LpAm(dB) = 62

Leakage and Starting Current: 70 mA / 170 A (approximately 100 microseconds)

Leakage and Starting Current: 70 mA / 170 A (approximately 100 microseconds)

Systems

To ensure installability and serviceability in non-IBM industry-standard racks, review the installation planning information for any product-specific installation requirements.

Operating environment - IBM z14 Water Cooled Machine

Environmental class - ASHRAE 3

Temperature: 5 to 40 degrees C (41 to 104 degrees F) for all models up to 900 meters above sea level; maximum ambient reduces 1 degree C per 300 meters above 900 meters.

Relative Humidity: 8 to 85 (percent) Wet Bulb (Caloric Value): 25 degrees C (77 degrees F)

Operating Mode Max Dew Point: 24 degrees C (75.2 degrees F) - Operating Mode

Electrical Power (maximum)

Utility      M01      M02      M03      M04      M05      Power
                                                          Factor
------------ -------- -------- -------- -------- -------- ------
200-240 V ac 10.0 kVA 18.1 kVA 22.3 kVA 26.4 kVA 27.9 kVA 0.996
380-415 V ac 10.2 kVA 18.6 kVA 22.9 kVA 27.1 kVA 28.6 kVA 0.978
480 V ac     10.5 kVA 19.3 kVA 23.7 kVA 28.1 kVA 29.6 kVA 0.958
400 V dc     9.7 kW   17.7 kW  21.6 kW  25.6 kW  27.6 kW  -

Capacity of Exhaust: 5950 cubic meters / hour (3500 CFM)

Noise level:

  • Typical Configuration (Model M02)
    • Declared A-Weighted Sound Power Level, LWAd(B) = 7.9
    • Declared A-Weighted Sound Pressure Level, LpAm(dB) = 60
  • Maximum Configuration (Model M05)
    • Declared A-Weighted Sound Power Level, LWAd(B) = 8.0
    • Declared A-Weighted Sound Pressure Level, LpAm(dB) = 61

Leakage and Starting Current: 70 mA / 170 A (approximately 100 microseconds)

Systems

To ensure installability and serviceability in non-IBM industry-standard racks, review the installation planning information for any product-specific installation requirements.

Limitations

Not applicable.

Hardware requirements

The hardware requirements for the IBM Z servers, features, and functions are identified. A new driver level is required. HMC (V2.14.0) plus MCLs and the Support Element (V2.14.0) are planned to be available on September 13, 2017.

You should review the PSP buckets for minimum Machine Change Levels (MCLs) and software PTF levels before IPLing operating systems.

HMC system support

The functions available on the Hardware Management Console (HMC) version 2.14.0, as described, apply exclusively to IBM z14. However, the HMC version 2.14.0 will also support the systems listed in the table below.

Family   Machine Type Firmware SE      Ensemble
                      Driver   Version Node
                                       Potential
-------- ------------ -------- ------- ---------
z14      3906         32       2.14.0  Yes
z13      2964         27       2.13.1  Yes
z13s     2965         27       2.13.1  Yes
zBX Node 2458 Mod 004 22       2.13.0  Required
zBC12    2828         15       2.12.1  Yes
zEC12    2827         15       2.12.1  Yes
z114     2818         93       2.11.1  Yes
z196     2817         93       2.11.1  Yes
z10 BC   2098         79       2.10.2  No
z10 EC   2097         79       2.10.2  No

Peripheral hardware and device attachments

IBM devices previously attached to IBM z114, z196, zBC12, zEC12, z13s, and z13 servers are supported for attachment to IBM z14 channels, unless otherwise noted. The subject I/O devices must meet the FICON and Fibre Channel Protocol (FCP) architectures to be supported. I/O devices that meet OEMI architecture requirements are supported only using an external converter. Prerequisite Engineering Change Levels may be required. For further detail, contact IBM service personnel.

While the IBM z14 supports devices as described above, IBM does not commit to provide support or service for an IBM device that has reached its End of Service effective date as announced by IBM.

Note: IBM cannot confirm the accuracy of performance, compatibility, or any other claims related to non-IBM products. Questions regarding the capabilities of non-IBM products should be addressed to the suppliers of those products.

Information on switches and directors qualified for IBM Z FICON and FCP channels can be found in the Library section of Resource Link .

Software requirements

IBM z14 requires at a minimum:

  • z/OS V2.3 with PTFs.(10)
  • z/OS V2.2 with PTFs.
  • z/OS V2.1 with PTFs.
  • z/OS V1.13 (compatibility only, extended support contract for IBM Software Support Services for z/OS required with PTFs).
  • z/VM V6.4 with PTFs (compatibility including Crypto Express6S and OSA-Express6S support, z/Architecture IPL).
  • z/VM V6.3 with PTFs (compatibility including Crypto Express6S and OSA-Express6S support, z/Architecture IPL).
  • z/VSE V6.2 with PTFs.
  • z/VSE V6.1 with PTFs.
  • z/VSE V5.2 with PTFs.
  • z/TPF V1.1 with PTFs (compatibility, including Crypto Express6S and OSA-Express6S support)
  • Linux on z Systems - IBM plans to support running the following Linux on z Systems distributions on IBM z14:
    • SUSE SLES 12 SP2 with service and SUSE SLES 11 SP4 with service.
    • Red Hat RHEL 7.3 with service and Red Hat RHEL 6.9 with service.
    • Ubuntu 16.04 LTS (or higher) with service.
    • IBM will be working to support the KVM hypervisor which is offered with the following Linux distributions: SLES 12 SP2 with service, and Ubuntu 16.04 LTS (or higher) with service.

      Note: For minimum required and recommended distribution levels refer to the IBM Z website.

  • KVM for IBM z 1.1.2 with latest Fixpack (toleration mode, until End of Service in March 2018).

Note: (10) IBM z/OS V2.3 with IBM z14 will require a minimum of 8 GB of memory. When running as a z/VM guest or on a IBM System z Personal Development Tool, a minimum of 2 GB will be required for z/OS V2.3. If the minimum is not met, a warning WTOR will be issued at IPL. Continuing with less than the minimum memory could impact availability. A migration health check is planned to be introduced for z/OS V2.2 and z/OS V2.1 with PTFs to warn you when an LPAR on a z14 system has been configured with less than 8 GB.

The following software requirements are listed for features and capabilities supported on IBM z14:

FICON Express16S+ (CHPID type FC) when utilizing FICON or Channel-To-Channel (CTC), requires at a minimum:

  • z/OS V2.3.
  • z/OS V2.2 with PTFs.
  • z/OS V2.1 with PTFs.
  • z/OS V1.13 (compatibility only, extended support contract for IBM Software Support Services for z/OS required).
  • z/VM V6.4.
  • z/VM V6.3.
  • z/VSE V6.2 with PTFs.
  • z/VSE V6.1 with PTFs.
  • z/VSE V5.2 with PTFs.
  • z/TPF V1.1 with PTFs.
  • Linux on z Systems:
    • SLES 12 SP2 with service and SLES 11 SP4 with service.
    • RHEL 7.3 with service and RHEL 6.9 with service.
    • Ubuntu 16.04 LTS (or higher) with service.
    • IBM will be working to support the KVM hypervisor which is offered with the following Linux distributions: SLES 12 SP2 with service, and Ubuntu 16.04 LTS (or higher) with service.

      Note: For minimum required and recommended distribution levels refer to the IBM Z website.

  • KVM for IBM z 1.1.2 with latest Fixpack (toleration mode, until End of Service March 2018).

FICON Express16S+ (CHPID type FC) for support of zHPF single-track operations requires at a minimum:

  • z/OS V2.3.
  • z/OS V2.2 with PTFs.
  • z/OS V2.1 with PTFs.
  • z/OS V1.13 (compatibility only, extended support contract for IBM Software Support Services for z/OS required with PTFs).
  • z/VM V6.4.
  • z/VM V6.3 for guest exploitation.
  • z/VSE V6.2 with PTFs.
  • z/TPF V1.1 with PTFs.
  • Linux on z Systems:
    • SLES 12 SP2 with service and SLES 11 SP4 with service.
    • RHEL 7.3 with service and RHEL 6.9 with service.
    • Ubuntu 16.04 LTS (or higher) with service.
    • IBM will be working to support the KVM hypervisor which is offered with the following Linux distributions: SLES 12 SP2 with service, and Ubuntu 16.04 LTS (or higher) with service.

      Note: For minimum required and recommended distribution levels refer to the IBM Z website.

  • KVM for IBM z 1.1.2 with latest Fixpack (toleration mode, until End of Service in March 2018).

FICON Express16S+ (CHPID type FC) for support of zHPF multitrack operations requires at a minimum:

  • z/OS V2.3.
  • z/OS V2.2 with PTFs.
  • z/OS V2.1 with PTFs.
  • z/OS V1.13 (compatibility only, extended support contract for IBM Software Support Services for z/OS required with PTFs).
  • z/VM V6.4.
  • z/VM V6.3 for guest exploitation.
  • z/VSE V6.2 with PTFs.
  • Linux on z Systems:
    • SLES 12 SP2 with service and SLES 11 SP4 with service.
    • RHEL 7.3 with service and RHEL 6.9 with service.
    • Ubuntu 16.04 LTS (or higher) with service.
    • IBM will be working to support the KVM hypervisor which is offered with the following Linux distributions: SLES 12 SP2 with service, and Ubuntu 16.04 LTS (or higher) with service.

      Note: For minimum required and recommended distribution levels refer to the IBM Z website.

  • KVM for IBM z 1.1.2 with latest Fixpack (toleration mode, until End of Service in March 2018).

FICON Express16S+ (CHPID type FCP) for support of SCSI devices requires at a minimum:

  • z/VM V6.4.
  • z/VM V6.3.
  • z/VSE V6.2 with PTFs.
  • z/VSE V6.1 with PTFs.
  • z/VSE V5.2 with PTFs.
  • Linux on z Systems:
    • SLES 12 SP2 with service and SLES 11 SP4 with service.
    • RHEL 7.3 with service and RHEL 6.9 with service.
    • Ubuntu 16.04 LTS (or higher) with service.

      Note: For minimum required and recommended distribution levels refer to the IBM Z website.

FICON Express16S+ (CHPID type FCP) support of hardware data router requires at a minimum:

  • z/VM V6.4 for guest exploitation.
  • z/VM V6.3 for guest exploitation.
  • Linux on z Systems:
    • SLES 12 SP2 with service and SLES 11 SP4 with service.
    • RHEL 7.3 with service and RHEL 6.9 with service.
    • Ubuntu 16.04 LTS (or higher) with service.
    • IBM will be working to support the KVM hypervisor which is offered with the following Linux distributions: SLES 12 SP2 with service, and Ubuntu 16.04 LTS (or higher) with service.

      Note: For minimum required and recommended distribution levels refer to the IBM Z website.

  • KVM for IBM z 1.1.2 with latest Fixpack (toleration mode, until End of Service in March 2018).

T10-DIF support by the FICON Express16S+ features when defined as CHPID type FCP requires at a minimum:

  • z/VM V6.4 for guest exploitation.
  • z/VM V6.3 for guest exploitation.
  • Linux on z Systems:
    • SLES 12 SP2 with service (DIF and DIX) and SLES 11 SP4 with service (DIF and DIX).
    • RHEL 7.3 with service (DIF and DIX) and RHEL 6.9 with service (DIF only).
    • Ubuntu 16.04 LTS (or higher) with service (DIF and DIX).
    • IBM will be working to support the KVM hypervisor which is offered with the following Linux distributions: SLES 12 SP2 with service, and Ubuntu 16.04 LTS (or higher.) with service.

      Note: For minimum required and recommended distribution levels refer to the IBM Z website.

  • KVM for IBM z 1.1.2 with latest Fixpack (toleration mode, until End of Service in March 2018).

OSA-Express6S GbE LX (#0422) and GbE SX (#0423) require at a minimum:

CHPID type OSD:

  • z/OS V2.3.
  • z/OS V2.2.
  • z/OS V2.1.
  • z/OS V1.13 (compatibility only, extended support contract for IBM Software Support Services for z/OS required).
  • z/VM V6.4 with PTFs.
  • z/VM V6.3 with PTFs.
  • z/VSE V6.2 with PTFs.
  • z/VSE V6.1 with PTFs.
  • z/VSE V5.2 with PTFs.
  • z/TPF V1.1 with PTFs.
  • Linux on z Systems:
    • SLES 12 SP2 with service and SLES 11 SP4 with service.
    • RHEL 7.3 with service and RHEL 6.9 with service.
    • Ubuntu 16.04 LTS (or higher) with service.
    • IBM will be working to support the KVM hypervisor which is offered with the following Linux distributions: SLES 12 SP2 with service, and Ubuntu 16.04 LTS (or higher) with service.

      Note: For minimum required and recommended distribution levels refer to the IBM Z website.

  • KVM for IBM z 1.1.2 with latest Fixpack (toleration mode, until End of Service in March 2018).

CHPID type OSD without maximum port exploitation (one port on the PCIe adapter is available for use):

  • z/OS V2.3.
  • z/OS V2.2.
  • z/OS V2.1.
  • z/OS V1.13 (compatibility only, extended support contract for IBM Software Support Services for z/OS required).
  • z/VM V6.4 with PTFs.
  • z/VM V6.3 with PTFs.
  • z/VSE V6.2 with PTFs.
  • z/VSE V6.1 with PTFs.
  • z/VSE V5.2 with PTFs.
  • z/TPF V1.1 with PTFs.
  • Linux on z Systems:
    • SLES 12 SP2 with service and SLES 11 SP4 with service.
    • RHEL 7.3 with service and RHEL 6.9 with service.
    • Ubuntu 16.04 LTS (or higher) with service.
    • IBM will be working to support the KVM hypervisor which is offered with the following Linux distributions: SLES 12 SP2 with service, and Ubuntu 16.04 LTS (or higher) with service.

      Note: For minimum required and recommended distribution levels refer to the IBM Z website.

  • KVM for IBM z 1.1.2 with latest Fixpack (toleration mode, until End of Service in March 2018).

OSA-Express6S 10 GbE LR (#0424) and 10 GbE SR (#0425) require at a minimum:

CHPID type OSD:

  • z/OS V2.3.
  • z/OS V2.2.
  • z/OS V2.1.
  • z/OS V1.13 (compatibility only, extended support contract for IBM Software Support Services for z/OS required).
  • z/VM V6.4 with PTFs.
  • z/VM V6.3 with PTFs.
  • z/VSE V6.2 with PTFs.
  • z/VSE V6.1 with PTFs.
  • z/VSE V5.2 with PTFs.
  • z/TPF V1.1 with PTFs.
  • Linux on z Systems:
    • SLES 12 SP2 with service and SLES 11 SP4 with service.
    • RHEL 7.3 with service and RHEL 6.9 with service.
    • Ubuntu 16.04 LTS (or higher) with service.
    • IBM will be working to support the KVM hypervisor which is offered with the following Linux distributions: SLES 12 SP2 with service, and Ubuntu 16.04 LTS (or higher) with service.

      Note: For minimum required and recommended distribution levels refer to the IBM Z website.

  • KVM for IBM z 1.1.2 with latest Fixpack (toleration mode, until End of Service in March 2018).

CHPID type OSX for access control to the intra-ensemble data network (IEDN) from IBM z14 to Unified Resource Manager functions:

  • z/OS V2.3.
  • z/OS V2.2.
  • z/OS V2.1.
  • z/OS V1.13 (compatibility only, extended support contract for IBM Software Support Services for z/OS required).
  • z/VM V6.4 to define, modify, and delete OSX CHPID types when z/VM is the controlling LPAR for dynamic I/O.
  • z/VM V6.3 to define, modify, and delete OSX CHPID types when z/VM is the controlling LPAR for dynamic I/O.
  • z/VSE V6.2 with PTFs.
  • z/VSE V6.1 with PTFs.
  • z/VSE V5.2 with PTFs.
  • z/TPF V1.1 with PTFs.
  • Linux on z Systems:
    • SLES 12 SP2 with service and SLES 11 SP4 with service.
    • RHEL 7.3 with service and RHEL 6.9 with service.
    • Ubuntu 16.04 LTS (or higher) with service.
    • IBM will be working to support the KVM hypervisor which is offered with the following Linux distributions: SLES 12 SP2 with service, and Ubuntu 16.04 LTS (or higher) with service.

      Note: For minimum required and recommended distribution levels refer to the IBM Z website.

  • KVM for IBM z 1.1.2 with latest Fixpack (toleration mode, until End of Service in March 2018).

OSA-Express6S 1000BASE-T Ethernet (#0426) requires at minimum:

CHPID type OSC supporting TN3270E and non-SNA DFT:

  • z/OS V2.3.
  • z/OS V2.2.
  • z/OS V2.1.
  • z/OS V1.13 (compatibility only, extended support contract for IBM Software Support Services for z/OS required).
  • z/VM V6.4.
  • z/VM V6.3.
  • z/VSE V6.2 with PTFs.
  • z/VSE V6.1 with PTFs.
  • z/VSE V5.2 with PTFs.
  • z/TPF V1.1 (support for port 0 only).

CHPID type OSD with exploitation of two ports per CHPID:

  • z/OS V2.3.
  • z/OS V2.2.
  • z/OS V2.1.
  • z/OS V1.13 (compatibility only, extended support contract for IBM Software Support Services for z/OS required).
  • z/VM V6.4 with PTFs.
  • z/VM V6.3 with PTFs.
  • z/VSE V6.2 with PTFs.
  • z/VSE V6.1 with PTFs.
  • z/VSE V5.2 with PTFs.
  • z/TPF V1.1 with PTFs.
  • Linux on z Systems:
    • SLES 12 SP2 with service and SLES 11 SP4 with service.
    • RHEL 7.3 with service and RHEL 6.9 with service.
    • Ubuntu 16.04 LTS (or higher) with service.

      Note: For minimum required and recommended distribution levels refer to the IBM Z website.

CHPID type OSD without maximum port exploitation (one port on the PCIe adapter is available for use):

  • z/OS V2.3.
  • z/OS V2.2.
  • z/OS V2.1.
  • z/OS V1.13 (compatibility only, extended support contract for IBM Software Support Services for z/OS required).
  • z/VM V6.4 with PTFs.
  • z/VM V6.3 with PTFs.
  • z/VSE V6.2 with PTFs.
  • z/VSE V6.1 with PTFs.
  • z/VSE V5.2 with PTFs.
  • z/TPF V1.1.
  • Linux on z Systems:
    • SLES 12 SP2 with service and SLES 11 SP4 with service.
    • RHEL 7.3 with service and RHEL 6.9 with service.
    • Ubuntu 16.04 LTS (or higher) with service.
    • IBM will be working to support the KVM hypervisor which is offered with the following Linux distributions: SLES 12 SP2 with service, and Ubuntu 16.04 LTS (or higher) with service.

      Note: For minimum required and recommended distribution levels refer to the IBM Z website.

  • KVM for IBM z 1.1.2 with latest Fixpack (toleration mode, until End of Service in March 2018).

Checksum offload for IPv6 packets (CHPID type OSD):

  • z/OS V2.3.
  • z/OS V2.2.
  • z/OS V2.1.
  • z/OS V1.13 (compatibility only, extended support contract for IBM Software Support Services for z/OS required).
  • z/VM V6.4 for guest exploitation.
  • z/VM V6.3 for guest exploitation.

Checksum offload for LPAR-to-LPAR traffic for IPv4 and IPv6 packets (CHPID type OSD):

  • z/OS V2.3.
  • z/OS V2.2.
  • z/OS V2.1.
  • z/OS V1.13 (compatibility only, extended support contract for IBM Software Support Services for z/OS required).
  • z/VM V6.4 for guest exploitation.
  • z/VM V6.3 for guest exploitation.

Large Send for IPv6 packets (CHPID type OSD):

  • z/OS V2.3.
  • z/OS V2.2.
  • z/OS V2.1.
  • z/OS V1.13 (compatibility only, extended support contract for IBM Software Support Services for z/OS required.
  • z/VM V6.4 for guest exploitation.
  • z/VM V6.3 for guest exploitation.

CHPID type OSE supporting 4 or 2 ports per feature:

  • z/OS V2.3.
  • z/OS V2.2.
  • z/OS V2.1.
  • z/OS V1.13 (compatibility only, extended support contract for IBM Software Support Services for z/OS required).
  • z/VM V6.4.
  • z/VM V6.3.
  • z/VSE V6.2.
  • z/VSE V6.1.
  • z/VSE V5.2.

CHPID type OSM for intranode management network (INMN):

  • z/OS V2.3.
  • z/OS V2.2.
  • z/OS V2.1.
  • z/OS V1.13 (compatibility only, extended support contract for IBM Software Support Services for z/OS required with PTFs).
  • z/VM V6.4 to define, modify, and delete CHPID type OSM when z/VM is the controlling LPAR for dynamic I/O.
  • z/VM V6.3 to define, modify, and delete CHPID type OSM when z/VM is the controlling LPAR for dynamic I/O.
  • Linux on z Systems:
    • SLES 12 SP2 with service and SLES 11 SP4 with service.
    • RHEL 7.3 with service and RHEL 6.9 with service.
    • Ubuntu 16.04 LTS (or higher) with service.

      Note: For minimum required and recommended distribution levels refer to the IBM Z website.

Crypto Express6S (#0893) Toleration, which treats Crypto Express6S cryptographic coprocessors and accelerators as Crypto Express5 coprocessors and accelerators, requires at a minimum:

  • z/OS V2.3 with PTFs.
  • z/OS V2.2 with PTFs or:
    • z/OS V2.2 with Cryptographic Support for z/OS V1R13 - z/OS V2R2 (HCR77B1) with PTFs, or
    • z/OS V2.2 with Cryptographic Support for z/OS V2R1 - z/OS V2R2 (HCR77CO) with PTFs.
  • z/OS V2.1 with PTFs or:
    • z/OS V2.1 with Cryptographic Support for z/OS V1R13 - z/OS V2R1 (HCR77A1) with PTFs or
    • z/OS V2.1 with Enhanced Cryptographic Support for z/OS V1R13 - z/OS V2R1 (HCR77B0) with PTFs or
    • z/OS V2.1 with Cryptographic Support for z/OS V1R13 - z/OS V2R2 (HCR77B1) with PTFs or
    • z/OS V2.1 with Cryptographic Support for z/OS V2R1 - z/OS V2R2 (HCR77CO) with PTFs.
  • z/VM V6.4 with PTFs for guest exploitation and exploitation within the z/VM TLS/SSL server.
  • z/VM V6.3 with PTFs for guest exploitation.
  • z/VSE V6.2 with PTFs.
  • z/VSE V6.1 with PTFs.
  • z/VSE V5.2 with PTFs.
  • z/TPF V1.1 with PTFs .
  • Linux on z Systems: IBM is working with its Linux distribution partners to provide support via maintenance or future distribution releases for:
    • SLES 12 SP2 with service and SLES 11 SP4 with service.
    • RHEL 7.3 with service and RHEL 6.9 with service.
    • Ubuntu 16.04 LTS (or higher) with service.
    • IBM will be working to support the KVM hypervisor which is offered with the following Linux distributions: SLES 12 SP2 with service, and Ubuntu 16.04 LTS (or higher) with service.
    • NOTE: For minimum required and recommended distribution levels refer to the IBM Z website.
  • KVM for IBM z 1.1.2 with latest Fixpack (toleration mode, until End of Service in March 2018).

Crypto Express6S (#0893) support of VISA Format Preserving Encryption requires at a minimum:

  • z/OS V2.3.
  • z/OS V2.2.
  • z/OS V2.1 with the Enhanced Cryptographic Support for z/OS V1R13-z/OS V2R1 (HCR77B0) web deliverable installed.
  • z/VM V6.4 with PTFs for guest exploitation.
  • z/VM V6.3 with PTFs for guest exploitation.

Crypto Express6S (#0893) support of greater than 16 Domains requires at a minimum:

  • z/OS V2.3.
  • z/OS V2.2
  • z/OS V2.1 with the Enhanced Cryptographic Support for z/OS V1R13-z/OS V2R1 (HCR77B0) web deliverable installed.
  • z/VM V6.4 with PTFs for guest exploitation and exploitation within the z/VM TLS/SSL server.
  • z/VM V6.3 with PTFs for guest exploitation.
  • z/VSE V6.2 with PTFs.
  • z/VSE V6.1 with PTFs.
  • z/VSE V5.2 with PTFs.
  • Linux on z Systems:
    • SLES 12 SP2 with service and SLES 11 SP4 with service.
    • RHEL 7.3 with service and RHEL 6.9 with service.
    • Ubuntu 16.04 LTS (or higher) with service.
    • IBM will be working to support the KVM hypervisor which is offered with the following Linux distributions: SLES 12 SP2 with service, and Ubuntu 16.04 LTS (or higher) with service.

      Note: For minimum required and recommended distribution levels refer to the IBM Z website.

  • KVM for IBM z 1.1.2 with latest Fixpack (toleration mode, until End of Service in March 2018).

Crypto Express6S (#0893) Exploitation requires at a minimum:

  • z/OS V2.1 with Cryptographic Support for z/OS V2R1 - z/OS V2R3 (HCR77C1).
  • z/OS V2.2 with Cryptographic Support for z/OS V2R1 - z/OS V2R3 (HCR77C1).
  • z/OS V2.3 with Cryptographic Support for z/OS V2R1 - z/OS V2R3 (HCR77C1).
  • z/VM 6.4 with PTFs for guest exploitation.
  • z/VM 6.3 with PTFs for guest exploitation.
  • z/TPF V1.1 with support for Crypto Express6S (APAR PJ44689).
  • Linux on z Systems: IBM is working with its Linux distribution partners to provide support in future distribution releases.

Crypto Express6S (#0893) support of PCI-HSM compliance requires at a minimum:

  • z/OS V2.1 with Cryptographic Support for z/OS V2R1 - z/OS V2R3 (HCR77C1).
  • z/OS V2.2 with Cryptographic Support for z/OS V2R1 - z/OS V2R3 (HCR77C1).
  • z/OS V2.3 with Cryptographic Support for z/OS V2R1 - z/OS V2R3 (HCR77C1).
  • z/VM 6.4 with PTFs for guest exploitation.
  • z/VM 6.3 with PTFs for guest exploitation.

10GbE RoCE Express2 (#0412) for Shared Memory Communications - Remote Direct Memory Access (SMC-R) requires at a minimum:

  • z/OS V2.3.
  • z/OS V2.2 with PTFs.
  • z/OS V2.1 with PTFs.
  • z/VM V6.4 with PTFs for guest exploitation.
  • z/VM V6.3 with PTFs for guest exploitation.
  • Linux on z Systems: IBM is working with its Linux distribution partners to include support in future distribution releases.

10GbE RoCE Express2 (#0412) for Ethernet communications (which does not require a peer OSA) including Single Root I/O Virtualization (SR-IOV) requires at a minimum:

  • z/VM V6.4 with PTFs for guest exploitation.
  • z/VM V6.3 with PTFs for guest exploitation.
  • Linux on z Systems: IBM is working with its Linux distribution partners to provide support via maintenance or future distribution releases for:
    • SLES 12 SP2.
    • RHEL 7.
    • Ubuntu 16.04 LTS (or higher) with service.
    • IBM will be working to support the KVM hypervisor which is offered with the following Linux distributions: SLES 12 SP2 with service, and Ubuntu 16.04 LTS (or higher) with service.

      Note: For minimum required and recommended distribution levels refer to the IBM Z website.

  • KVM for IBM z 1.1.2 with latest Fixpack (toleration mode, until End of Service in March 2018).

IBM Integrated Coupling Adapter Fanout (ICA SR) (#0172) requires at a minimum:

  • z/OS V2.3.
  • z/OS V2.2.
  • z/OS V2.1 with PTFs.
  • z/OS V1.13 (compatibility only, extended support contract for IBM Software Support Services for z/OS required with PTFs).
  • z/VM 6.4 to define, modify, and delete CHPID type CS5 when z/VM is the controlling LPAR for dynamic I/O.
  • z/VM V6.3 to define, modify, and delete CHPID type CS5 when z/VM is the controlling LPAR for dynamic I/O.

Support for 256 Coupling CHPIDs requires at a minimum:

  • z/OS V2.3.
  • z/OS V2.2.
  • z/OS V2.1 with PTFs.
  • z/OS V1.13 (compatibility only, extended support contract for IBM Software Support Services for z/OS required with PTFs).
  • z/VM V6.4 for guest exploitation.
  • z/VM V6.3 for guest exploitation.

Coupling Express LR (#0433) requires at a minimum:

  • z/OS V2.3 with PTFs.
  • z/OS V2.2 with PTFs.
  • z/OS V2.1 with PTFs.
  • z/OS V1.13 (compatibility only, extended support contract for IBM Software Support Services for z/OS required with PTFs).
  • z/VM V6.4 with PTFs to define, modify, and delete CL5 CHPID types when z/VM is the controlling LPAR for dynamic I/O.
  • z/VM V6.3 with PTFs to define, modify, and delete CL5 CHPID types when z/VM is the controlling LPAR for dynamic I/O.

CF Scalability Enhancements requires at a minimum:

  • z/OS V2.3.
  • z/OS V2.2 with PTFs.
  • z/OS V2.1 with PTFs.
  • z/OS V1.13 (compatibility only, extended support contract for IBM Software Support Services for z/OS required with PTFs).
  • z/VM 6.4 for guest coupling exploitation.
  • z/VM 6.3 for guest coupling exploitation.

CF List Notification Enhancements requires at a minimum:

  • z/OS V2.3.
  • z/OS V2.2 with PTFs.
  • z/OS V2.1 with PTFs.
  • z/OS V1.13 (compatibility only, extended support contract for IBM Software Support Services for z/OS required with PTFs).
  • z/VM 6.4 for guest coupling exploitation.
  • z/VM 6.3 for guest coupling exploitation.

zHyperLink Express (#0431) requires at a minimum:

  • z/OS V2.3 with PTFs.
  • z/OS V2.2 with PTFs.
  • z/OS V2.1 with PTFs.

zEDC Express (#0420) requires at a minimum:

  • z/OS V2.3 with the zEnterprise data Compression (zEDC) for z/OS feature.
  • z/OS V2.2 with the zEnterprise data Compression (zEDC) for z/OS feature.
  • z/OS V2.1 with the zEnterprise data Compression (zEDC) for z/OS feature.
  • z/VM V6.4 for guest exploitation.
  • z/VM V6.3 for guest exploitation.
  • Linux on z Systems:
    • SLES 12 SP2 with service.
    • RHEL 7.3 with service.
    • Ubuntu 16.04 LTS (or higher) with service.
    • IBM will be working to support the KVM hypervisor which is offered with the following Linux distributions: SLES 12 SP2 with service, and Ubuntu 16.04 LTS (or higher) with service.

      Note: For minimum required and recommended distribution levels refer to the IBM Z website.

  • KVM for IBM z 1.1.2 with latest Fixpack (toleration mode, until End of Service in March 2018).

IBM Virtual Flash Memory (VFM) (#0604) requires at a minimum:

  • z/OS V2.3.
  • z/OS V2.2.
  • z/OS V2.1.
  • z/OS V1.13 with PTFs, the z/OS V1.13 RSM Enablement Offering web deliverable installed, and an extended support contract for IBM Software Support Services. The web deliverable is available at the z/OS downloads website.

XL C/C++ support of ARCH(12) and TUNE(12) parameters requires at a minimum:

  • z/OS V2.3 with PTFs.

Transactional memory requires at a minimum:

  • z/OS V2.3.
  • z/OS V2.2.
  • z/OS V2.1.
  • z/OS V1.13 (compatibility only, extended support contract for IBM Software Support Services for z/OS required with PTFs).
  • z/VM V6.4 for guest exploitation.
  • Linux on z Systems:
    • SLES 12 SP2 with service and SLES 11 SP4 with service.
    • RHEL 7.3 with service and RHEL 6.9 with service.
    • Ubuntu 16.04 LTS (or higher) with service.

2 GB Large Pages requires at a minimum:

  • z/OS V2.3.
  • z/OS V2.2.
  • z/OS V2.1.
  • z/OS V1.13 with PTFs, the z/OS V1.13 RSM Enablement Offering web deliverable installed, and an extended support contract for IBM Software Support Services. The web deliverable is available at the z/OS downloads website.
  • z/TPF V1.1 with PTFs.
  • Linux on z Systems: IBM is working with its Linux distribution partners to provide support via future distribution releases.

z/OS global resource serialization (GRS) support for FICON CTCs requires at a minimum:

  • z/OS V2.3.
  • z/OS V2.2.
  • z/OS V2.1.
  • z/OS V1.13 with an extended support contract for IBM Software Support Services and PTFs.

Guarded Storage requires at a minimum:

  • z/OS V2.3.
  • z/OS V2.2 with PTFs.
  • z/VM V6.4 with PTFs for guest exploitation (December 15, 2017 availability).
  • Linux on z Systems: IBM is working with its Linux distribution partners to provide support via future distribution releases.

Instruction Execution Protection Facility requires at a minimum:

  • z/OS V2.3.
  • z/OS V2.2 with PTFs.
  • z/VM V6.4 with PTFs for guest exploitation (December 15, 2017 availability).
  • Linux on z Systems: IBM is working with its Linux distribution partners to provide support via future distribution releases.

Back to topBack to top
 
Publications

The following publications are available now in the Library section of Resource Link (TM):

Title                                                     Order
                                                          number
--------------------------------------------------------- ---------
IBM 3906 Installation Manual for Physical Planning (IMPP) GC28-6965
PR/SM (TM) Planning Guide                                 SB10-7169
IOCP User's Guide for ICP                                 SB10-7172
Planning for Fiber Optic Links                            GA23-1408

The following publications are shipped with the product and will be available at planned availability in the Library section of Resource Link:

Title                                                          Order
                                                               number
-------------------------------------------------------------- ---------
IBM 3906 Installation Manual                                   GC28-6964
IBM 3906 Service Guide                                         GC28-6966
Service Guide for TKE Workstations (Version 7.0)               GC28-6980
Systems Safety Notices                                         G229-9054
IBM Important Notices                                          G229-9056
IBM 3906 Safety Inspection                                     GC28-6963
Systems Environmental Notices and User Guide                   Z125-5823
Statement of Limited Warranty                                  GC28-6979
License Agreement for Machine Code                             SC28-6872
License Agreement for Machine Code Addendum for Elliptic Curve GC27-2635
Cryptography

The following publications will be available at planned availability in the Library section of Resource Link:

Title                                                    Order
                                                         number
-------------------------------------------------------- ---------
IBM 3906 Parts Catalog                                   GC28-6967
Service Guide for 2461 HMC                               GC28-6981
Service Guide for 2461 Support Element                   GC28-6982
Service Guide for HMCs and SEs                           GC28-6983
Hardware Management Console Security                     SC28-6987
SNMP Application Programming Interfaces                  SB10-7171
Capacity on Demand User's Guide                          SC28-6985
CHPID Mapping Tool User's Guide                          GC28-6984
Hardware Management Console Web Services API (V2.14.0)   SC27-2636
IBM Dynamic Partition Manager (DPM) Guide                SB10-7170
Secure Service Container User's Guide                    SC28-6978
Integrating the HMC's Broadband RSF into your Enterprise SC28-6986
SCSI IPL - Machine Loader Messages                       SC28-6948
Stand-Alone IOCP User's Guide                            SB10-7173
Ensemble Workload Resource Group Management Guide        GC27-2633
Ensemble Planning Guide                                  GC27-2631
OSA-Express Customer Guide and Reference                 SA22-7935
OSA Integrated Console Controller User's Guide           SC27-9003
OSA/SF on the Hardware Management Console                SC14-7580
FICON CTC Reference                                      SB10-7174
Maintenance Information for Fiber Optic Links            SY27-7696

Resource Link: Publications for IBM Z can be obtained at the Resource Link website.

Using the instructions on the Resource Link panels, obtain a user ID and password. Resource Link has been designed for easy access and navigation.

HMC and SE console documentation

At planned availability, the Hardware Management Console (HMC) and Support Element (SE) console documentation (Version 2.14.0) will be available from IBM Knowledge Center. IBM Knowledge Center provides you with a single information center where you can access product documentation for IBM systems hardware, operating systems, and server software. Through a consistent framework, you can efficiently find information and personalize your access.

Title         Order number
------------- ------------
IBM z14       SG24-8450-00
IBM z14       SG24-8451-00
IBM z14       SG24-8460-00
IBM z Systems SG24-5444-17
IBM z Systems REDP-5157-02

To download these Redbooks publications, go to the IBM zEnterprise System Redbooks website.

For other IBM Redbooks publications, go to the main IBM Redbooks website.

IBM Knowledge Center provides you with a single information center where you can access product documentation for IBM systems hardware, operating systems, and server software. Through a consistent framework, you can efficiently find information and personalize your access. See the IBM Knowledge Center website.

To access the IBM Publications Center Portal, go to the IBM Publications Center website.

The Publications Center is a worldwide central repository for IBM product publications and marketing material with a catalog of 70,000 items. Extensive search facilities are provided. A large number of publications are available online in various file formats, which can currently be downloaded.
Back to topBack to top
 

Features
TOC Link Features - No charge TOC Link Features - Chargeable TOC Link Feature descriptions


Features - No charge

COLOR: A specify code is not required.

VOLTAGE: A specify code for line cord feature codes is required and will be provided by the configurator based on the country code of the order.

LANGUAGE: A specify code for language is required and will be provided by the configurator based on the country code of the order.

Feature Code Title
------------ -----------------------------
0012         Exchange Pgm Machine
0013         Exchange Pgm Machine + Covers
0014         Migration Offering Machine
0015         Blue Letter Internal
0099         WWPN Persistence
0186         Client Must Provide Mouse
0187         Client Must Provide HMC Keybd
0188         Client Must Provide HMC KMM
0189         Client Must Provide TKE Keybd
0190         Client Must Provide TKE KMM
0191         Client Must Provide Display

Features - Chargeable

Feature Code Title
------------ ----------------------------
0016         HW for DPM
0017         Customized MRReport
0018         Cost Analysis Sizing
0019         Manage FW Suite
0020         Automate FW Suite
0025         Ensemble membership
0032         Non RSF On/Off CoD
0034         OSA-ICC 3215 Enablement
0035         RFID Tag
0036         RFID Tag
0037         RFID Tag
0072         Air w/o TEIO & w/o HtrR
0073         Air w/o TEIO & w/HtR
0074         Air w/ TEIO & w/o HtR
0075         Air w/TEIO & w/HtR
0076         Wat w/o TEIO & w/o HtrR
0077         Wat w/o TEIO & w/ HtR
0078         Wat w/TEIO & w/o HtR
0079         Wat w/TEIO & w/HtR
0080         TKE Rack Mount w/4768
0081         TKE w/4768
0082         HMC
0083         HMC Rack Mount
0085         TKE Rack Mount w/4768
0086         TKE w/4768
0103         Linux Hosting Foundation
0104         Container Hosting Foundation
0105         Air w/o TEIO & w/o HtrR
0106         Air w/o TEIO & w/HtR
0107         Air w/TEIO & w/o HtR
0108         Air w/TEIO & w/HtR
0109         Wat w/o TEIO & w/o HtrR
0110         Wat w/o TEIO & w/HtR
0111         Wat w/TEIO & w/o HtR
0112         Wat w/TEIO & w/HtR
0116         1 CPE Capacity Unit
0117         100 CPE Capacity Unit
0118         10000 CPE Capacity Unit
0119         1 CPE Capacity Unit-IFL
0120         100 CPE Capacity Unit-IFL
0121         1 CPE Capacity Unit-ICF
0122         100 CPE Capacity Unit-ICF
0125         1 CPE Capacity Unit-zIIP
0126         100 CPE Capacity Unit-zIIP
0127         1 CPE Capacity Unit-SAP
0128         100 CPE Capacity Unit-SAP
0148         HMC Table Top KMM
0152         Mouse
0153         HMC Tower Keyboard
0154         HMC Rack Keybd/Monitor/Mouse
0155         TKE Tower Keyboard
0156         KE Rack Keybd/Monitor/Mouse
0157         TKE Table Top KMM
0170         HCA3-O LR Fanout
0171         HCA3-O Fanout
0172         ICA SR Fanout
0412         10 GbE RoCE Express2
0420         zEDC Express
0422         OSA-Express6S GbE LX
0423         OSA-Express6S GbE SX
0424         OSA-Express6S 10 GbE LR
0425         OSA-Express6S 10 GbE SR
0426         OSA-Express 1000BASE-T
0427         FICON Express16S+ LX
0428         FICON Express16S+ SX
0429         OSA-Express7S 25 GbE SR
0430         25GbE RoCE Express2
0431         zHyperLink Express
0433         Coupling Express LR
0604         IBM Virtual Flash Memory
0609         IBM Db2 Analytics Accelerator on Z
0844         4768 TKE Crypto Adapter
0848         32GB USB Backup Media
0849         TKE workstation w/4768
0879         TKE 9.0 LIC
0880         TKE 9.1 LIC
0891         TKE Smart Card Reader
0893         Crypto Express6S
0900         TKE addl smart cards
1021         STP Enablement
1750         LICCC Ship Via Net Ind
1929         CP4
1930         CP5
1931         CP6
1932         CP7
1933         IFL
1934         ICF
1935         SAP (optional)
1936         zIIP
1937         Unassigned IFL
1990         32GB Preplanned memory
1999         64GB VFM Preplanned Memory
2000         Line Cord Plan Ahead
3003         Balanced Power Plan Ahead
3103         Universal Lift Tool Upg Kit
3105         Universal Lift Tool/Ladder
3216         Internal Battery IBF
3379         FDT Adapter Kit
3380         Fill and Drain Kit
3863         CPACF Enablement
4013         PCIe I/O Drawer
4029         A Fr Radiator
4030         A Fr Water
6096         Flat Panel Display
6805         Additional CBU Test
6817         Total CBU Years Ordered
6818         CBU Records Ordered
6820         Single CBU CP-Year
6821         25 CBU CP-Year
6822         Single CBU IFL Year
6823         25 CBU IFL Year
6824         Single CBU ICF Year
6825         25 CBU ICF Year
6828         Single CBU zIIP Year
6829         25 CBU zIIP Year
6830         Single CBU SAP Year
6831         25 CBU SAP Year
6832         CBU Replenishment
6833         Capacity for Planned Event
7801         14ft Water Hose
7923         FQC Bracket & Mounting Hdw
7924         LC Duplex 6.6 ft Harness
7925         LC Duplex 8.5ft Harness
7926         LC Duplex 12 ft Harness
7942         Top Exit I/O Cabling
7949         Side Covers
7998         Non Raised Floor Support
8003         4-in-1 Bolt Down Kit
8004         3-in-1 Bolt Down Kit-W
8005         Bolt Down Kit, NRF
9896         On/Off CoD authorization
9898         Perm upgr authorization
9900         On-Line CoD Buying (Flag)
9910         CBU authorization
9912         CPE authorization
9917         1 MSU day
9918         100 MSU days
9919         10000 MSU days
9920         1 IFL day
9921         100 IFL days
9922         1 ICF day
9923         100 ICF days
9924         1 zIIP day
9925         100 zIIP days
9928         1 SAP day
9929         100 SAP days
9970         Weight Distribution Kit
9975         Height Reduce Ship
9976         Height reduce for return

Feature descriptions

(#0148) HMC Table Top KMM

Feature code #0148 is a table top Monitor with a keyboard in the language of choice. There is a touchpad for pointing. Included is a country specific power cord.

  • Minimum: Zero
  • Maximum: One per Tower HMC #0082
  • Prerequisites: Tower HMC #0082
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
  • Cable Order: Power cord, Video cable, and a USB cable are provided.
(#0157) TKE Table Top KMM

Feature code #0157 is a table top Monitor with an US English keyboard #103P. There is a touchpad for pointing. Included is a country specific power cord.

  • Minimum: Zero
  • Maximum: One per Tower TKE #0086
  • Prerequisites: Tower TKE #0086
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
  • Cable Order: Power cord, Video cable, and a USB cable are provided.
(#0186) Client Must Provide Mouse

Feature code #0186 is a non-selectable feature code. If instructed by IBM to de-select feature code #0152, due to import restrictions, then #0186 is added to the order to inform the client that they must provide a USB optical mouse with a finger wheel.

  • Minimum: None.
  • Maximum: One per Tower HMC #0082 and/or Tower TKE #0086.
  • Prerequisites: Tower HMC #0082 and/or Tower TKE #0086.
  • Corequisites: None.
  • Compatibility Conflicts: Mouse #0152.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: N/A.
  • Cable Order: N/A.
(#0187) Client Must Provide HMC Tower KeyBd

Feature code #0187 is a non-selectable feature code. If instructed by IBM to de-select feature code #0153, due to import restrictions, then #0187 is added to the order to inform the client that they must provide a USB Keyboard in the proper language.

  • Minimum: None.
  • Maximum: One per Tower HMC #0082.
  • Prerequisites: Tower HMC #0082.
  • Corequisites: None.
  • Compatibility Conflicts: HMC Tower Keyboard #0153.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: N/A.
  • Cable Order: N/A.
(#0188) Client Must Provide HMC KMM

Feature code #0188 is a non-selectable feature code. If instructed by IBM to de-select feature code #0154, due to import restrictions, then #0188 is added to the order to inform the client that they must provide a 1u Rack Mounted Monitor and Keyboard with a built in pointing device. The Keyboard must be in the proper language. Both the keyboard and pointing device must be USB and have a proper cable to reach the HMC. The Monitor must be VGA. Its cable must have a male HD15 connector and also reach the HMC.

  • Minimum: None.
  • Maximum: One per Rack Mounted HMC #0083.
  • Prequisites: The Rack Mounted HMC #0083.
  • Corequisites: None.
  • Compatibility Conflicts: HMC Rack Keybd/Monitor/Mouse #0154.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: N/A.
  • Cable Order: N/A.
(#0189) Client Must ProvideTKE Tower KeyBd

Feature code #0189 is a non-selectable feature code. If instructed by IBM to de-select feature code #0155, due to import restrictions, then #0189 is added to the order to inform the client that they must provide a USB Keyboard in US English.

  • Minimum: None.
  • Maximum: One per Tower TKE #0086.
  • Prerequisites: Tower TKE #0086.
  • Corequisites: None.
  • Compatibility Conflicts: TKE Tower Keyboard #0155.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: N/A.
  • Cable Order: N/A.
(#0190) Client Must Provide TKE KMM

Feature code #0190 is a non-selectable feature code. If instructed by IBM to de-select feature code #0156, due to import restrictions, then #0190 is added to the order to inform the client that they must provide a 1u Rack Mounted Monitor and Keyboard with a built in pointing device. The Keyboard must be in US English. Both the keyboard and pointing device must be USB and have a proper cable to reach the TKE. The Monitor must be VGA. Its cable must have a male HD15 connector and also reach the TKE.

  • Minimum: None.
  • Maximum: One per Rack Mounted TKE #0085.
  • Prequisites: The Rack Mounted TKE #0085.
  • Corequisites: None.
  • Compatibility Conflicts: TKE Rack Keybd/Monitor/Mouse #0156.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: N/A.
  • Cable Order: N/A.
(#0191) Client Must Provide Display

Feature code #0191 is a non-selectable feature code. If instructed by IBM to de-select feature code #6096, due to import restrictions, then #0191 is added to the order to inform the client that they must provide a Table Top Display. The Display must be VGA. Its cable must have a male HD15 connector and reach the HMC or TKE.

  • Minimum: None.
  • Maximum: One per Tower HMC #0082 and/or Tower TKE #0086.
  • Prequisites: The Tower HMC #0082 and/or Tower TKE #0086.
  • Corequisites: None.
  • Compatibility Conflicts: Display #6096.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: N/A.
  • Cable Order: N/A.
(#0012) Exchange Pgm Machine

Feature code #0012 is an information only feature code which is required to initiate an order to be fulfilled through the Technology Exchange program.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: N/A.
(#0013) Exchange Pgm Machine + Covers

Feature code #0013 is an information only feature code which is required to initiate an order to be fulfilled through the Technology Exchange program. System provided will include covers.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisite: None.
  • Corequisites: None.
  • Compatibility Conflicts: None.
  • Customer Setup: No.
  • Limitations: Not available on initial system order.
  • Field Installable: N/A.
(#0014) Migration Offering Machine

Feature code #0014 is an information only feature code which is required to initiate an order to be fulfilled through a Migration Offering.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None.
  • Customer Setup: No.
  • Limitations: Initial system order only. Not offered in Japan.
  • Field Installable: N/A.
(#0015) Blue Letter Internal

Feature code #0015 is an information only feature code which is required to initiate an order for an IBM internal or SO customer.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None.
  • Customer Setup: No.
  • Limitations: Machine Type Upgrade MES only. US only.
  • Field Installable: N/A.
(#0099) WWPN Persistence

Feature code #0099 is an information only feature code which is required to initiate an ordering option to maintain IO serial numbers when a newly purchased system will replace an existing system within the customer's data center. This option eliminates the need to reconfigure zoning in SAN switches and LUN masking in storage controllers.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: N/A.
(#0016) HW for DPM

This feature code provides the cabling required for OSA-Express6S 1000 BASE-T Ethernet (#0426) or OSA-Express5S 1000BASE-T Ethernet (#0417) features defined as CHPID type OSM connectivity which is used with Dynamic Partition Manager (DPM).

Note: The OSA-Express6S 1000BASE-T Ethernet or OSA-Express5S 1000BASE-T Ethernet features cannot be shared and must be dedicated for usage by Dynamic Partition Manager when configured.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: Two OSA-Express 1000BASE-T Ethernet features are required, for primary and backup connectivity (OSA-Express6S 1000BASE-T Ethernet #0426 or OSA-Express5S 1000BASE-T Ethernet #0417). A port is defined as CHPID type OSM .
  • Compatibility Conflicts: The OSA-Express6S 1000BASE-T Ethernet or OSA-Express5S 1000BASE-T Ethernet features cannot be shared and must be dedicated for usage by Dynamic Partition Manager when configured.
  • Customer Setup: No.
  • Limitations: Dynamic Partition Manager can be ordered along with Ensemble Membership (FC #0025) but they cannot both be enabled at the same time on the system. Dynamic Partition Manager supports Linux, running in an LPAR, on KVM on z hypervisor, and on z/VM 6.4.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
  • Cable Order: Two 3.2 meter (10.5 feet) Category 6 copper cables with RJ-45 connectors of each end are provided. Installation is performed by service personnel.
(#0017) Customized MRReport

This feature code is strictly for S/390 Manufacturing 1 Poughkeepsie Product Assistance Center to create and to charge customers for a Customized MRREPORT for zSystem machines. U.S CUSTOMERS - Contact Poughkeepsie Product Assistance Center for the customized MRReport. WORLD TRADE CUSTOMERS. Do not order this FC prior to contacting HELPS390 at IBMFR for assistance.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: No.
(#0018) Cost Analysis Sizing

This feature code is used to charge a fee for time spent on the request that requires extensive IBM Development and Engineering review, evaluation, consultation and cost analysis. When the feature code is eventually ordered, the cost for the evaluation and sizing may, in some cases, be deducted from the quoted price.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: No.
(#0019) Manage F W Suite

This feature is used to enable the base set of tiered function associated with the IBM z Unified Resource Manager. The Manage suite includes core operational controls, installation and configuration management, energy monitoring, hypervisor management, and intraensemble data network (IEDN) management, as well as virtual server lifecycle management. The Manage suite is included in the base IBM z14 at no charge for CPs, IFLs, and zIIPs. One of the two tiered suites of functionality for the IBM z Unified Resource Manager must be ordered. These suites are cumulative. Manage (#0019) is the base suite. If the next level suite, Automate Suite (#0020), is ordered, Manage Suite (#0019) is automatically included.

  • Minimum: None or one if using IBM z Unified Resource Manager.
  • Maximum: One.
  • Prerequisites: None.
  • Corequisites: Either #0019 or #0020 must be ordered. If the Automate Suite (#0020) is ordered, the Manage suite (#0019) is automatically included.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None known.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
(#0020) Automate Suite

This feature is used to enable the Automate suite of functionality associated with the IBM z Unified Resource Manager. The Automate Suite includes representation of resources in a workload context, goal-oriented monitoring and management of resources, and energy management. The Automate Suite is included in the base IBM z14 at no charge for CPs and IFL, and zIIPs. One of the two tiered suites of functionality for the IBM z Unified Resource Manager must be ordered. These suites are cumulative. Manage (#0019) is the base suite. If the next level suite, Automate Suite (#0020), is ordered, Manage suite (#0019) is automatically included.

  • Minimum: None or one if using IBM z Unified Resource Manager.
  • Maximum: One.
  • Prerequisites: None.
  • Corequisites: Either #0019 or #0020 must be ordered. If the Automate Suite (#0020) is ordered, the Manage suite (#0019) is automatically included.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None known.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
(#0025) Ensemble membership

This feature ships the appropriate cabling for connectivity to the intranode management network (INMN).

Ensemble membership requires that the IBM z14 have two OSA-Express5S 1000BASE-T Ethernet or OSA-Express6S 1000BASE-T Ethernet features defined as CHPID type OSM for connectivity to the intranode management network (INMN). Communication across the INMN is exclusively for the purpose of enabling the IBM z Unified Resource Manager of the Hardware Management Console (HMC) to perform its various management disciplines (such as performance management, network virtualization management, energy management, etc.).

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: Two OSA-Express 1000BASE-T Ethernet features are required, for primary and backup connectivity (OSA-Express6S 1000BASE-T Ethernet #0426 or OSA-Express5S 1000BASE-T Ethernet #0417). A port is defined as CHPID type OSM.
  • Compatibility Conflicts: The OSA-Express6S 1000BASE-T Ethernet or OSA-Express5S 1000BASE-T Ethernet features cannot be shared and must be dedicated for usage by Dynamic Partition manager when configured.
  • Customer Setup: No.
  • Limitations: Ensemble membership can be ordered along with HW for DPM (#0016) but they cannot both be enabled at the same time on the system.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
  • Cable Order: Two 3.2 meter (10.5 feet) Category 6 copper cables with RJ-45 connectors of each end are provided. Installation is performed by service personnel.
(#0032) NonRSF Connection for On/Off Capacity on Demand (On/Off CoD)

The purpose of this feature code is to allow for alternative delivery of On/Off CoD records to customers, by allowing for the downloading of record from the Resource Link web site, verses the normal electronic call home delivery. Feature code 0032 will be added to the ResourceLink profile to indicate the On/Off CoD link will be delivered via media/CDRom. This signals Business Practices to establish a contract addendum that details the requirements for VPD transmission, billing practices, warranty terms.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: No.
(#0034) OSA-ICC 3215 Enablement

The purpose of this FC is to provide OSA-ICC 3215 enablement for TPF.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes.
(#0035) RFID Tag

This feature code supplies RFID tracking tags that enable the customer to monitor and/or inventory hardware in their data centers.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: Mutually exclusive with #0036 and #0037.
  • Customer Setup: No.
  • Limitations: Available on box orders in the following:
    Argentina         Chile             Israel              Saint Lucia
    Aruba             China             Jamaica             Sri Lanka
    Bahamas           Colombia          Korea               Singapore
    Bangladesh        Costa Rica        Laos                Suriname
    Barbados          Dominican         Macao               Taiwan
                      Republic
    Belize            Ecuador           Malaysia            Thailand
    Bermuda           El Salvador       Mexico              Trinidad & Tobago
    Bolivia           Guatemala         Myanmar             United States
    Brazil            Guyana            NetherlandsAntilles Uruguay
    Brunei Darussalam Haiti             Nicaragua           Venezuela
    Cambodia          Honduras          Panama              Viet Nam
    Canada            Hong Kong         Peru
    
  • Field Installable: Yes.
(#0036) RFID Tag

This feature code supplies RFID tracking tags that enable the customer to monitor and/or inventory hardware in their data centers.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: Mutually exclusive with #0035 and #0037.
  • Customer Setup: No.
  • Limitations: Available on box orders in the following:
    Abu Dhabi       Egypt             Lesotho           Senegal
    Afghanistan     Equatorial Guinea Liberia           Serbia
    Albania         Eritrea           Libya             Seychelles
    Algeria         Estonia           Liechtenstein     Slovakia
    Angola          Ethiopia          Lithuania         Slovenia
    Armenia         France            Luxembourg        Sierra Leone
    Austria         Finland           Macedonia         Spain
    Azerbaijan      Gabon             Madagascar        Somolia
    Belarus         Gambia            Mali              South Africa
    Belgium         Georgia           Malta             Sudan
    Benin           Germany           Mauretania        Swaziland
    Bosnia          Ghana             Martinique        Sweden
    Botswana        Greece            Middle East DB    Switzerland
    Bulgaria        Guadeloupe        Moldova           Syrian Arab Republic
    Burkinao Faso   Guinea            Montenegro        Szekesfehervar
    Burundi         Guinea Bissau     Morocco           Tajikistan
    Cape Verde      Guinea Conocracy  Namibia           Tanzania
    Bulgaria        Guadeloupe        Moldova           Syrian Arab Republic
    Burkinao Faso   Guinea            Montenegro        Szekesfehervar
    Burundi         Guinea Bissau     Morocco           Tajikistan
    Cape Verde      Guinea Conocracy  Namibia           Tanzania
    Cameroon        Hungary           Netherlands       Togo
    Central African Iceland           New Zealand       Turkey
    Republic
    Chad            India             Niger             Turkmenistan
    Comoros         Iran              Norway            Uganda
    Congo           Iraq              Oman              Ukraine
    Croatia         Ireland           Pakistan          United Kingdom
    Cyprus          Italy             Poland            Uzbekistan
    Czech Republic  Ivory Coast       Portugal          Yemen
                    Jordan            Romania           Zambia
    DemocraticRepub
    Denmark         Kuwait            Russian           Zimbabwe
                                      Federation
    Djibouti        Kyrgyzstan        Rwanda
    Eastern Europe  Latvia            Sao Tome 1
    Direct Business                   Princip
    
  • Field Installable: Yes.
(#0037) RFID Tag

This feature code supplies RFID tracking tags that enable the customer to monitor and/or inventory hardware in their data centers.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: Mutually exclusive with #0035 and #0036.
  • Customer Setup: No.
  • Limitations: Available on box orders in Japan.
  • Field Installable: Yes.
(#0072) Air w/o TEIO & w/o HtrR

Feature provides a means to order and price return packaging materials for installed machines being replaced by a MT 3906 through a new build, Migration Offering or Machine Type Upgrade order. Select when system to be returned is MT 2827, radiator cooled and without Top Exit IO feature (#7942) and does not require a height reduction (#9976).

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: Mutually exclusive with #0073, #0074, #0075,# 0076, #0077, #0078, #0079,#0105, #0106, #0107, #0108, #0109, #0110, #0111, and #0112.
  • Customer Setup: No.
  • Limitations: Not available as a standalone MES.
  • Field Installable: Yes.
(#0073) Air w/o TEIO & w/HtrR

Feature provides a means to order and price return packaging materials for installed machines being replaced by a MT 3906 through a new build, Migration Offering or Machine Type Upgrade order. Select when system to be returned is MT 2827, radiator cooled and without Top Exit IO feature (#7942) but requires a height reduction (#9976).

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: Mutually exclusive with #0072, #0074, #0075, #0076, #0077, #0078, #0079, #0105, #0106, #0107, #0108, #0109, #0110, #0111 and #0112.
  • Customer Setup: No.
  • Limitations: Not available as a standalone MES.
  • Field Installable: Yes.
(#0074) Air w/TEIO & w/o HtR

Feature provides a means to order and price return packaging materials for installed machines being replaced by a MT 3906 through a new build, Migration Offering or Machine Type Upgrade order. Select when system to be returned is MT 2827, radiator cooled and with Top Exit IO feature (#7942) and does not require a height reduction (#9976).

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: Mutually exclusive with #0072, #0073, #0075, #0076, #0077, #0078, #0079, #0015, # 0106, #0107, #0108 ,#0109, #0110, #0111 and #0112.
  • Customer Setup: No.
  • Limitations: Not available as a standalone MES.
  • Field Installable: Yes.
(#0075) Air w/TEIO & w/HtR

Feature provides a means to order and price return packaging materials for installed machines being replaced by a MT 3906 through a new build, Migration Offering or Machine Type Upgrade order. Select when system to be returned is MT 2827, radiator cooled and with Top Exit IO feature (#7942) and requires a height reduction (#9976).

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: Mutually exclusive with #0072, #0073, #0074, #0076, #0077, #0078, #0079, #0105, #0106, #0107, #0108, #0109, #0110, #0111, and #0112.
  • Customer Setup: No.
  • Limitations: Not available as a standalone MES.
  • Field Installable: Yes.
(#0076) Wat w/o TEIO & w/o HtrR

Feature provides a means to order and price return packaging materials for installed machines being replaced by a MT 3906 through a new build, Migration Offering or Machine Type Upgrade order. Select when system to be returned is MT 2827, water cooled and without Top Exit IO feature (#7942) and does not require a height reduction (#9976).

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: Mutually exclusive with #0072, #0073, #0074, #0075, #0077, #0078, #0079, #0105, #0106, #0107, #0108, #0109, #0110, #0111, and #0112.
  • Customer Setup: No.
  • Limitations: Not available as a standalone MES.
  • Field Installable: Yes.
(#0077) Wat w/o TEIO & w/HtrR

Feature provides a means to order and price return packaging materials for installed machines being replaced by a MT 3906 through a new build, Migration Offering or Machine Type Upgrade order. Select when system to be returned is MT 2827, water cooled and without Top Exit IO feature (#7942) but requires a height reduction (#9976).

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: Mutually exclusive with #0072, #0073, #0074, #0075, #0076, #0078, #0079, #0105, #0106, #0107, #0108, #0109, #0110, #0111, and #0112.
  • Customer Setup: No.
  • Limitations: Not available as a standalone MES.
  • Field Installable: Yes.
(#0078) Wat w/TEIO & w/o HtR

Feature provides a means to order and price return packaging materials for installed machines being replaced by a MT 3906 through a new build, Migration Offering or Machine Type Upgrade order. Select when system to be returned is MT 2827, water cooled and with Top Exit IO feature (#7942) and does not require a height reduction (#9976).

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: Mutually exclusive with #0072, #0073, #0074, #0075, #0076, #0077, #0079, #0105, #0106, #0107, #0108, #0109, #0110, #0111, and #0112.
  • Customer Setup: No.
  • Limitations: Not available as a standalone MES.
  • Field Installable: Yes.
(#0079) Wat w/TEIO & w/HtR

Feature provides a means to order and price return packaging materials for installed machines being replaced by a MT 3906 through a new build, Migration Offering or Machine Type Upgrade order. Select when system to be returned is MT 2827, water cooled and with Top Exit IO feature (#7942) and requires a height reduction (#9976).

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: Mutually exclusive with #0072, #0073, #0074, #0075, #0076, #0077, #0078, #0105, #0106, #0107, #0108, #0109, #0110, #0111, and #0112.
  • Customer Setup: No.
  • Limitations: Not available as a standalone MES.
  • Field Installable: Yes.
(#0080) TKE Rack Mount w/4768

Feature code 0080 is a RACK Mounted TKE at Version 9.0 (#0879). The only way to create a (#0080) is to upgrade an existing (#0097) RACK Mounted TKE. This upgrade requires the TKE LIC to be upgraded to TKE 9.0 and the TKE local crypto adapter to be changed from a 4767 to a 4768.

Note: TKE 9.0 is required if you choose to use the TKE to manage a Crypto Express6S. TKE 9.0 is also required to manage the new CCA mode PCI-HSM settings which are available on the Crypto Express6S. A TKE is required to manage any Crypto Express feature that is running in IBM Enterprise PKCS #11 (EP11) mode. CCA in PCI-HSM mode and EP11 also require a smartcard reader plus FIPS certified smart cards.

  • Minimum: 0.
  • Maximum: 10.
  • Prequisites: (#0097).
  • Corequisites: TKE 9.0 LIC (#0879) and MT 4768 adapter (#0844). If TKE is used to manage an EP11 mode module, the PCI-HSM setting of a Crypto Express6S, or use the TKE Configuration Migration Tasks application, smart card readers and smart cards are required.
  • Compatibility Conflicts: There are smart card reader and smart card considerations:
    • You can carry your smart card readers from feature code 0885 or 0891 forward. Existing smart cards can be used on TKE 9.0 with these readers.
    • You can also order new smart card readers with feature code #0891.

    Note: If you have smart cards with applets not supported by the new smart card reader, you must create new smart cards on TKE 8.1 or later and copy the content from the old smart cards to the new smart cards. The new smart cards can be created and copied on a TKE 8.1 system. If the copies are done on TKE 9.0, the source smart card must be placed in an older smart card reader from feature code 0885 or 0891.

  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
  • Cable Order: LAN cabling is a customer responsibility. A Category 5 Unshielded Twisted Pair (UTP) cable terminated with RJ-45 connector is required.
(#0081) TKE w/4768

Feature code 0081is a TOWER TKE at Version 9.0 (#0879). The only way to create a (#0081) is to upgrade an existing (#0098) TOWER TKE IS TKE local crypto adapter to be changed from a 4767 to a 4768.

Note: TKE 9.0 is required if you choose to use the TKE to manage a Crypto Express6S. TKE 9.0 is also required to manage the new CCA mode PCI-HSM settings which are available on the Crypto Express6S. A TKE is required to manage any Crypto Express feature that is running in IBM Enterprise PKCS #11 (EP11) mode. CCA in PCI-HSM mode and EP11 also require a smartcard reader plus FIPS certified smart cards.

  • Minimum: 0.
  • Maximum: 10.
  • Prequisites: (#0098).
  • Corequisites: TKE 9.0 LIC (#0879) and MT 4768 adapter (#0844).
  • Compatibility Conflicts: There are smart card reader and smart card considerations:
    • You can carry your smart card readers from feature code 0885 or 0891 forward. Existing smart cards can be used on TKE 9.0 with these readers.
    • You can also order new smart card readers with feature code #0891.

    Note: If you have smart cards with applets not supported by the new smart card reader, you must create new smart cards on TKE 8.1 or later and copy the content from the old smart cards to the new smart cards. The new smart cards can be created and copied on a TKE 8.1 system. If the copies are done on TKE 9.0, the source smart card must be placed in an older smart card reader from feature code 0885 or 0891.

  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
  • Cable Order: LAN cabling is a customer responsibility. A Category 5 Unshielded Twisted Pair (UTP) cable terminated with RJ-45 connector is required.
(#0082) HMC

The Hardware Management Console (HMC) has been enhanced to provide attempted tamper protection monitoring and reporting. A newly manufactured HMC ordered with IBM z14, or ordered at a later time, is required for this protection. Any attempted tampering events detected will be logged and will issue a customer alert via a warning or a lock of the HMC, depending on setup configuration. In addition, if call home support is enabled on the HMC, additional analysis of events logged by the HMC will be available on IBM Resource Link. The HMC is a workstation designed to provide a single point of control and single system image for managing local or remote hardware elements. Connectivity is supplied using an Ethernet Local Area Network (LAN) devoted exclusively to accessing the supported local and remote servers. The HMC is designed to support, exclusively, the HMC application. The HMC is supplied with two Ethernet ports capable of operating at 10, 100, or 1000 Mbps. It can act as a primary or alternate HMC. Although customers can carry forward their HMCs on IBM z14, these tamper protection capabilities will only be delivered on newly manufactured HMCs. The IBM z14 environment can contain both HMCs that have been carried forward and newly manufactured HMCs.

  • Minimum: In an ensemble, Two; otherwise None.
  • Maximum: Ten (10), combination of #0082 and #0083.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None.
  • Customer Setup: No.
  • Limitations: The HMC is for the exclusive use of the HMC application. Customer applications cannot reside on the HMC. TCP/IP is the only supported communication protocol. The HMC supports IBM z14. It can also be used to support z13, z13s, zEC12, and zBC12 z196, z114, z10 EC, and z10 BC servers. They must be upgraded to a new AROM level.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
  • Cable Order: Cables are shipped with the HMC. The Ethernet cables are Category 5 Unshielded Twisted Pair (UTP) with an RJ-45 connector on each end.
(#0083) HMC Rack Mount:

Feature code 0083 is a 1u Rack Mounted HMC. These rack mounted HMC components are 19 inch rack mountable components that can be placed in customer 19 inch racks. The Hardware Management Console (HMC) has been enhanced to provide attempted tamper protection monitoring and reporting. A newly manufactured HMC ordered with IBM z14 or ordered at a later time, is required for this protection. Any attempted tampering events detected will be logged and will issue a customer alert via a warning or a lock of the HMC, depending on setup configuration. In addition, if call home support is enabled on the HMC, additional analysis of events logged by the HMC will be available on IBM Resource Link. The HMC is a workstation designed to provide a single point of control and single system image for managing local or remote hardware elements. Connectivity is supplied using an Ethernet Local Area Network (LAN) devoted exclusively to accessing the supported local and remote servers. The HMC is designed to support, exclusively, the HMC application. The HMC is supplied with two Ethernet ports capable of operating at 10, 100, or 1000 Mbps. It can act as a primary or alternate HMC. Although customers can carry forward their HMCs on IBM z14, these tamper protection capabilities will only be delivered on newly manufactured HMCs. The IBM z14 environment can contain both HMCs that have been carried forward and newly manufactured HMCs.

  • Minimum: In an ensemble, Two; otherwise None.
  • Maximum: Ten (10), combination of #0082 and #0083.
  • Prerequisites: The rack mount unit is plugged in a customer supplied frame, not the IBM z frame, and requires customer supplied PDUs.
  • Corequisites: None.
  • Compatibility Conflicts: None.
  • Customer Setup: No.
  • Limitations: The HMC is for the exclusive use of the HMC application. Customer applications cannot reside on the HMC. TCP/IP is the only supported communication protocol. The HMC supports IBM z14. It can also be used to support z13, z13s, zEC12, zBC12, z196, z114, z10 EC, and z10 BC servers. They must be upgraded to a new AROM level.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
  • Cable Order: Cables are shipped with the HMC. The Ethernet cables are Category 5 Unshielded Twisted Pair (UTP) with an RJ-45 connector on each end.
(#0085) TKE Rack Mount w/4768

Feature code 0085 is a new purchase of a 1u Rack Mounted TKE. These rack mounted TKE components are 19 inch rack mountable components that can be placed in customer 19 inch racks. A client provided shelf is recommended for holding any USB Smart Card readers. You can order up to 10 TKE feature code per CPC. The Trusted Key Entry (TKE) workstation is a combination of hardware and software, network connected to one or more servers, and designed to provide a secure, hardware-based compliance-level method for master and operational key entry as well as local and remote management of the cryptographic coprocessor features. This feature provides basic key management -- key identification, exchange, separation, update, backup, as well as security administration. This feature is optional when used to manage a Crypto Express feature that is running in Common Cryptographic Architecture (CCA) coprocessor. The TKE workstation has one Ethernet port and supports connectivity to an Ethernet Local Area Network (LAN) operating at 10, 100, or 1000 Mbps. The TKE has been enhanced to provide attempted tamper protection monitoring and reporting. A newly manufactured TKE ordered with IBM z14, or ordered at a later time, is required for this protection. Any attempted tampering events detected will be logged and will issue a customer alert via a warning or a lock of the TKE, depending on setup configuration. Although customers can carry forward their TKEs on IBM z14, these tamper protection capabilities will only be delivered on newly manufactured TKEs. The IBM z14 environment can contain both TKEs that have been carried forward and newly manufactured TKEs.

Note: TKE 9.0 is required if you choose to use the TKE to manage a Crypto Express6S. TKE 9.0 is also required to manage the new CCA mode PCI-HSM settings which are available on the Crypto Express6S. A TKE is required to manage any Crypto Express feature that is running in IBM Enterprise PKCS #11 (EP11) mode. CCA in PCI-HSM mode and EP11 also require a smartcard reader plus FIPS certified smart cards.

  • Minimum: 0.
  • Maximum: 10, combination of #0085, and #0086.
  • Prerequisites: None.
  • Corequisite: None.
  • Compatibility Conflicts: If you have smart cards and smart card readers from previous generations of TKEs in your environment, be aware of the following smart card and smart card reader considerations:
    • You can carry your smart card readers from feature code 0885 or 0891 forward. Existing smart cards can be used on TKE 9.0 with these readers.
    • You can also order new smart card readers with feature code #0891.

    Note: If you have smart cards with applets not supported by the new smart card reader, you must create new smart cards on TKE 8.1 or later and copy the content from the old smart cards to the new smart cards. The new smart cards can be created and copied on a TKE 8.1 system. If the copies are done on TKE 9.0, the source smart card must be placed in an older smart card reader from feature code 0885 or 0891.

  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes. Parts removed as a result of feature change become the property of IBM.
  • Cable Order: LAN cabling is a customer responsibility. A Category 5 Unshielded Twisted Pair (UTP) cable terminated with RJ-45 connector is required.
(#0086) TKE w/4768:

Feature code 0086 is a new purchase of Tower TKE. You can order up to 10 TKE feature code per CPC. The Trusted Key Entry (TKE) workstation is a combination of hardware and software, network connected to one or more servers, and designed to provide a secure, hardware-based compliance-level method for master and operational key entry as well as local and remote management of the cryptographic coprocessor features.

This feature provides basic key management -- key identification, exchange, separation, update, backup, as well as security administration. This feature is optional when used to manage a Crypto Express feature that is running in Common Cryptographic Architecture (CCA) coprocessor.

The TKE workstation has one Ethernet port and supports connectivity to an Ethernet Local Area Network (LAN) operating at 10, 100, or 1000 Mbps. The TKE has been enhanced to provide attempted tamper protection monitoring and reporting. A newly manufactured TKE ordered with IBM z14, or ordered at a later time, is required for this protection. Any attempted tampering events detected will be logged and will issue a customer alert via a warning or a lock of the TKE, depending on setup configuration. Although customers can carry forward their TKEs on IBM z14, these tamper protection capabilities will only be delivered on newly manufactured TKEs. The IBM z14 environment can contain both TKEs that have been carried forward and newly manufactured TKEs.

Note: TKE 9.0 is required if you choose to use the TKE to manage a Crypto Express6S. TKE 9.0 is also required to manage the new CCA mode PCI-HSM settings which are available on the Crypto Express6S. A TKE is required to manage any Crypto Express feature that is running in IBM Enterprise PKCS #11 (EP11) mode. CCA in PCI-HSM mode and EP11 also require a smartcard reader plus FIPS certified smart cards.

  • Minimum: 0.
  • Maximum: 10, combination of #0085, and #0086.
  • Prerequisites: None.
  • Corequisite: None.
  • Compatibility Conflicts: If you have smart cards and smart card readers from previous generations of TKEs in your environment, be aware of the following smart card and smart card reader considerations:
    • You can carry your smart card readers from feature code 0885 or 0891 forward. Existing smart cards can be used on TKE 9.0 with these readers.
    • You can also order new smart card readers with feature code #0891.

    Note: If you have smart cards with applets not supported by the new smart card reader, you must create new smart cards on TKE 8.1 or later and copy the content from the old smart cards to the new smart cards. The new smart cards can be created and copied on a TKE 8.1 system. If the copies are done on TKE 9.0, the source smart card must be placed in an older smart card reader from feature code 0885 or 0891.

  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes. Parts removed as a result of feature change become the property of IBM.
  • Cable Order: LAN cabling is a customer responsibility. A Category 5 Unshielded Twisted Pair (UTP) cable terminated with RJ-45 connector is required.
(#0103) Linux Hosting Foundation

This feature is ordered in conjunction with IBM Secure Service Container software product. This feature enables support access for Secure Service Containers that house single applications.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None.
  • Customer Setup: Not applicable.
  • Limitations: None.
  • Field Installable: Yes.
(#0104) Container Hosting Foundation

This feature is ordered in conjunction with IBM Secure Service Container software product. This feature enables support access for Secure Service Containers for multiple applications.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None.
  • Customer Setup: Not applicable.
  • Limitations: None.
  • Field Installable: Yes.
(#0105) Air w/o TEIO & w/o HtrR

Feature provides a means to order and price return packaging materials for installed machines being replaced by a MT 3906 through a new build, Migration Offering or Machine Type Upgrade order. Select when system to be returned is MT 2964, radiator cooled and without Top Exit IO feature (#7942) and does not require a height reduction (#9976).

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: Mutually exclusive with #0072, #0073, #0074, #0075, #0076, #0077, #0078, #0079, #0106, #0107, #0108, #0109, #0110, #0111, and #0112.
  • Customer Setup: No.
  • Limitations: Not available as a standalone MES.
  • Field Installable: Yes.
(#0106) Air w/o TEIO & w/HtR

Feature provides a means to order and price return packaging materials for installed machines being replaced by a MT 3906 through a new build, Migration Offering or Machine Type Upgrade order. Select when system to be returned is MT 2964, radiator cooled and without Top Exit IO feature (#7942) but requires a height reduction (#9976).

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: Mutually exclusive with #0072, #0073, #0074, #0075, #0076, #0077, #0078, #0079, #0105, #0107, #0108, #0109, #0110, #0111, and #0112.
  • Customer Setup: No.
  • Limitations: Not available as a standalone MES.
  • Field Installable: Yes.
(#0107) Air w/TEIO & w/o HtR

Feature provides a means to order and price return packaging materials for installed machines being replaced by a MT 3906 through a new build, Migration Offering or Machine Type Upgrade order. Select when system to be returned is MT 2964, radiator cooled and with Top Exit IO feature (#7942) and does not require a height reduction (#9976).

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: Mutually exclusive with #0072, #0073, #0074, #0075, #0076, #0077, #0078, #0079, #0105, #0106, #0108, #0109, #0110, #0111, and #0112.
  • Customer Setup: No.
  • Limitations: Not available as a standalone MES.
  • Field Installable: Yes.
(#0108) Air w/TEIO & w/HtR

Feature provides a means to order and price return packaging materials for installed machines being replaced by a MT 3906 through a new build, Migration Offering or Machine Type Upgrade order. Select when system to be returned is MT 2964, radiator cooled and with Top Exit IO feature (#7942) but requires a height reduction (#9976).

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: Mutually exclusive with #0072, #0073, #0074, #0075, #0076, #0077, #0078, #0079, #0105, #0106, #0107, #0109, #0110, #0111, and #0112.
  • Customer Setup: No.
  • Limitations: Not available as a standalone MES.
  • Field Installable: Yes.
(#0109) Wat w/o TEIO & w/o HtrR

Feature provides a means to order and price return packaging materials for installed machines being replaced by a MT 3906 through a new build, Migration Offering or Machine Type Upgrade order. Select when system to be returned is MT 2964, water cooled and without Top Exit IO feature (#7942) and does not require a height reduction (#9976).

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: Mutually exclusive with #0072, #0073, #0074, #0075, #0076, #0077, #0078, #0079, #0105, #0106, #0107, #0108, #0110, #0111, and #0112.
  • Customer Setup: No.
  • Limitations: Not available as a standalone MES.
  • Field Installable: Yes.
(#0110) Wat w/o TEIO & w/HtR

Feature provides a means to order and price return packaging materials for installed machines being replaced by a MT 3906 through a new build, Migration Offering or Machine Type Upgrade order. Select when system to be returned is MT 2964, water cooled and without Top Exit IO feature (#7942) but requires a height reduction (#9976).

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: Mutually exclusive with #0072, #0073, #0074, #0075, #0076, #0077, #0078, #0079, #0105, #0106, #0107, #0108, #0109, #0111, and #0112.
  • Customer Setup: No.
  • Limitations: Not available as a standalone MES.
  • Field Installable: Yes.
(#0111) Wat w/TEIO & w/o HtR

Feature provides a means to order and price return packaging materials for installed machines being replaced by a MT 3906 through a new build, Migration Offering or Machine Type Upgrade order. Select when system to be returned is MT 2964, water cooled and with Top Exit IO feature (#7942) and does not require a height reduction (#9976).

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: Mutually exclusive with #0072, #0073, #0074, #0075, #0076, #0077, #0078, #0079, #0105, #0106, #0107, #0108, #0109, #0110, and #0112.
  • Customer Setup: No.
  • Limitations: Not available as a standalone MES.
  • Field Installable: Yes.
(#0112) Wat w/TEIO & w/HtR

Feature provides a means to order and price return packaging materials for installed machines being replaced by a MT 3906 through a new build, Migration Offering or Machine Type Upgrade order. Select when system to be returned is MT 2964, water cooled and with Top Exit IO feature (#7942) and requires a height reduction (#9976).

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: Mutually exclusive with #0072, #0073, 30074, #0075, #0076, #0077, #0078, #0079, #0105, #0106, #0107, #0108, #0109, #0110, and #0111.
  • Customer Setup: No.
  • Limitations: Not available as a standalone MES.
  • Field Installable: Yes.
(#0116) 1 CPE Capacity Unit

Pricing feature code equal to the remainder of three days multiplied by the number of CPE Capacity Units divided by 100 purchased in a given Capacity for Planned Event record.

  • Minimum: 0.
  • Maximum: 99.
  • Prerequisites: None.
  • Corequisites: Capacity for Planned Event (CPE) (#6833).
  • Compatibility Conflicts: None known.
  • Customer Setup: Not applicable.
  • Limitations: None.
  • Field Installable: Yes.
(#0117) 100 CPE Capacity Unit

Pricing feature equal to the quotient of three days multiplied by the number of CPE Capacity Units purchased in a given pre-paid Capacity for Planned Event record divided by 100.

  • Minimum: 0.
  • Maximum: 99.
  • Prerequisites: 1 CPE Capacity Unit (#0116).
  • Corequisites: Capacity for Planned Event (CPE) (#6833).
  • Compatibility Conflicts: None known.
  • Customer Setup: Not applicable.
  • Limitations: None.
  • Field Installable: Yes.
(#0118) 10000 CPE Capacity Unit

Pricing feature equal to the quotient of three days multiplied by the number of CPE Capacity Units purchased in a given pre-paid Capacity for Planned Event record divided by 10,000.

  • Minimum: 0.
  • Maximum: 250.
  • Prerequisites: 100 CPE Capacity Unit (#0117).
  • Corequisites: Capacity for Planned Event (CPE) (#6833).
  • Compatibility Conflicts: None known.
  • Customer Setup: Not applicable.
  • Limitations: None.
  • Field Installable: Yes.
(#0119) 1 CPE Capacity Unit-IFL

Pricing feature equal to the remainder of the three days multiplied by the number of temporary Integrated Facility for Linux (IFL) features in a given Capacity for Planned event record divided by 100.

  • Minimum: 0.
  • Maximum: 99.
  • Prerequisites: None.
  • Corequisites: Capacity for Planned Event (CPE) (#6833) .
  • Compatibility Conflicts: None known.
  • Customer Setup: Not applicable.
  • Limitations: None.
  • Field Installable: Yes.
(#0120) 100 CPE Capacity Unit-IFL:

Pricing feature equal to the quotient of three days multiplied by the number of temporary Integrated Facility for Linux (IFL) features in a given Capacity for Planned event record divided by 100.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: 1 CPE Capacity Unit-IFL (#0119).
  • Corequisites: Capacity for Planned Event (CPE) (#6833).
  • Compatibility Conflicts: None known.
  • Customer Setup: Not applicable.
  • Limitations: None.
  • Field Installable: Yes.
(#0121) 1 CPE Capacity Unit-ICF

Pricing feature equal to the remainder of the three days multiplied by the number of temporary Internal Coupling Facility (ICF) features in a given Capacity for Planned event record divided by 100.

  • Minimum: 0.
  • Maximum: 99.
  • Prerequisites: None.
  • Corequisites: Capacity for Planned Event (CPE) (#6833).
  • Compatibility Conflicts: None known.
  • Customer Setup: Not applicable.
  • Limitations: None.
  • Field Installable: Yes.
(#0122) 100 CPE Capacity Unit-ICF

Pricing feature equal to the quotient of three days multiplied by the number of temporary Internal Coupling Facility (ICF) features in a given Capacity for Planned event record divided by 100.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: 1 CPE Capacity Unit-ICF (#0121).
  • Corequisites: Capacity for Planned Event (CPE) (#6833).
  • Compatibility Conflicts: None known.
  • Customer Setup: Not applicable.
  • Limitations: None.
  • Field Installable: Yes.
(#0125) 1 CPE Capacity Unit-zIIP

Pricing feature equal to the remainder of the three days multiplied by the number of temporary IBM z Integrated Information Processor (zIIP) features in a given Capacity for Planned event record divided by 100.

  • Minimum: 0.
  • Maximum: 99.
  • Prerequisites: None.
  • Corequisites: Capacity for Planned Event (CPE) (#6833).
  • Compatibility Conflicts: None known.
  • Customer Setup: Not applicable.
  • Limitations: None.
  • Field Installable: Yes.
(#0126) 100 CPE Capacity Unit-zIIP:

Pricing feature equal to the quotient of three days multiplied by the number of temporary IBM z Integrated Information Processor (zIIP) features in a given Capacity for Planned event record divided by 100.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: 1 CPE Capacity Unit-zIIP (#0125).
  • Corequisites: Capacity for Planned Event (CPE) (#6833).
  • Compatibility Conflicts: None known.
  • Customer Setup: Not applicable.
  • Limitations: None.
  • Field Installable: Yes.
(#0127) 1 CPE Capacity Unit-SAP

Pricing feature equal to the remainder of the three days multiplied by the number of temporary System Assist Processor (SAP) features in a given Capacity for Planned event record divided by 100.

  • Minimum: 0.
  • Maximum: 99.
  • Prerequisites: None.
  • Corequisites: Capacity for Planned Event (CPE) (#6833).
  • Compatibility Conflicts: None known.
  • Customer Setup: Not applicable.
  • Limitations: None.
  • Field Installable: Yes.
(#0128) 100 CPE Capacity Unit-SAP

Pricing feature equal to the quotient of three days multiplied by the number of temporary System Assist Processor (SAP) features in a given Capacity for Planned event record divided by 100.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: 1 CPE Capacity Unit-SAP (#0127).
  • Corequisites: Capacity for Planned Event (CPE) (#6833).
  • Compatibility Conflicts: None known.
  • Customer Setup: Not applicable.
  • Limitations: None.
  • Field Installable: Yes.
(#0152) Mouse

Feature code #0152 is a USB optical mouse with a finger wheel.

  • Minimum: One per Tower HMC #0082 or Tower TKE #0086.
  • Maximum: One per Tower HMC #0082 or Tower TKE #0086.
  • Prerequisites: Tower HMC or Tower TKE.
  • Corequisites: None.
  • Compatibility Conflicts: None.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
  • Cable Order: USB cable is provided and attached.
(#0153) HMC Tower Keyboard

Feature code #0153 is a USB keyboard, in the language specified.

  • Minimum: One per Tower HMC #0082.
  • Maximum: One per Tower HMC. #0082.
  • Prerequisites: Tower HMC #0082.
  • Corequisites: A language selection is required #0235 to #0249.
  • Compatibility Conflicts: None.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
  • Cable Order: USB cable is provided and attached.
(#0154) HMC Rack Keybd/Monitor/Mouse

Feature code #0154 is a 1u Rack Mounted Display and Keyboard with a built in Pointing device. The Keyboard will come in the language specified.

  • Minimum: One per Rack Mounted HMC #0083.
  • Maximum: One per Rack Mounted HMC #0083.
  • Prequisites: The Rack Mounted HMC #0083.
  • Corequisites: A language selection is required #0235 to #0249.
  • Compatibility Conflicts: None.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
  • Cable Order: USB, VGA cable, and Power Jumper is included.
(#0155) TKE Tower Keyboard

Feature code #0155 is a USB keyboard, in the English language.

  • Minimum: One per Tower TKE #0086.
  • Maximum: One per Tower TKE #0086.
  • Prerequisites: Tower TKE #0086.
  • Corequisites: None.
  • Compatibility Conflicts: None.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
  • Cable Order: USB cable is provided and attached.
(#0156) TKE Rack Keybd/Monitor/Mouse

Feature code #0156 is a 1u Rack Mounted Display and Keyboard with a built in Pointing device. The Keyboard will come in the English language.

  • Minimum: One per Rack Mounted TKE #0085.
  • Maximum: One per Rack Mounted TKE #0085.
  • Prequisites: The Rack Mounted TKE #0085.
  • Corequisites: None.
  • Compatibility Conflicts: None.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
  • Cable Order: USB, VGA cable, and Power Jumper is included.
(#0170) HCA3-O LR fanout for 1x InfiniBand

The 1x InfiniBand coupling links utilize the Host Channel Adapter3 optical long reach (HCA3-O LR) fanout. This fanout is designed to support single data rate (SDR) at 2.5 gigabits per second (Gbps) or double data rate (DDR) at 5 Gbps.

Note: The Infiniband link data rates of 5Gbps or 2.5Gbps do not represent the performance of the link. The actual performance is dependent upon many factors including latency through the adapters, cable lengths, and the type of workload.

To access DWDM vendor qualification letters go to:

http://www.ibm.com/servers/resourcelink/
  • On the left, click on "Library"
  • In the middle you will see "Hardware products for servers"
  • Click on "z Systems Qualified Wavelength Division Multiplexer (WDM) products for GDPS solutions"
  • Click on the vendor of your choice to view the qualification letters

The HCA3-O LR fanout has four ports/links and resides in the processor nest on the front of the Central Processor Complex (CPC) drawer. It is compatible with the HCA2-O LR fanout, which has two ports/links.

1x InfiniBand coupling links complement 12x InfiniBand coupling links and are designed to satisfy extended distance requirements.

  • Minimum: None. Order increment is four ports/links (one HCA3-O LR fanout).
  • Maximum: 16 (64 ports). The maximum number of all HCA3-O LR fanout features is limited to 16 per system.
  • Prerequisites: None.
  • Corequisites: STP enablement (#1021).
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations:
    • An unrepeated distance of 10km (6.2 miles) is supported. Greater distances are supported when attached to an IBM Z -qualified optical networking solution.
    • The HCA3-O LR fanout for 1x InfiniBand is offered on z14, z13, z13s, zEC12, and zBC12 servers.
  • Field Installable: Yes.
  • Cable Order: A customer-supplied cable is required. A 9/125 micrometer single mode fiber optic cable terminated with an LC Duplex connector is required (same connector used with ISC-3). A cable is required for each port on the fanout.

Refer to Planning for Fiber Optic Links, GA23-1408, and to Maintenance for Fiber Optic Links, SY27-7696 which can be found in the Library section of Resource Link at

http://www.ibm.com/servers/resourcelink
(#0171) HCA3-O fanout for 12x InfiniBand

The 12x InfiniBand coupling links utilize the Host Channel Adapter3 optical (HCA3-O) fanout. This fanout is designed to support a link data rate of 6 GigaBytes per second (GBps).

Note: A link data rate of 6 GBps does not represent the actual performance of the link.

The HCA3-O fanout has two ports/links and resides in the processor nest on the front of the Central Processor Complex (CPC) drawer.

12x InfiniBand coupling links complement 1x InfiniBand coupling links and are designed to satisfy short distance requirements.

12x InfiniBand can be used for Server Time Protocol (STP) message passing.

  • Minimum: None. Order increment is two ports/links (one HCA3-O fanout).
  • Maximum: 16 (32 ports). The maximum number of all HCA3-O fanout features is limited to 16 per system.
  • Prerequisites: None.
  • Corequisites: STP enablement (#1021).
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations:
    • Maximum supported distance is 150 meters (492 feet). It cannot be repeated.
  • Field Installable: Yes.
  • Cable Order: A customer-supplied 12x IB-DDR cable is required for each port. The cable is an OM3 50/125 micrometer multimode fiber optic cable with a fiber bandwidth @ wavelength: 2000 MHz-km @ 850 nm. It is a 24-fiber cable with duplex 12x multi-fiber push-on (MPO) connectors. There are 12 fibers for transmit and 12 fibers for receive.

Refer to Planning for Fiber Optic Links, GA23-1408, and to Maintenance for Fiber Optic Links, SY27-7696 which can be found in the Library section of Resource Link at

http://www.ibm.com/servers/resourcelink
(#0172) IBM Integrated Coupling Adapter (ICA SR) fanout

The ICA SR is a 2 port fanout used for short distance coupling connectivity and utilizes coupling channel type: CS5. It utilizes PCIe Gen3 technology, with x16 lanes that are bifurcated into x8 lanes for coupling. The ICA SR is designed to drive distances up to 150m and support a link data rate of 8 GigaBytes per second (GBps).

Note: A link data rate of 8 GBps does not represent the actual performance of the link.

The ICA SR is designed to support up to 4 CHPIDs per port and 8 buffers (i.e. subchannels) per CHPID. The ICA SR fanout resides in a PCIe fanout slot on the z14 CPC drawer. The ICA SR can only be used for coupling connectivity between z14, z13, and z13s CPCs. Also, the ICA SR cannot be connected to HCA3-O or HCA3-O LR coupling fanouts. The ICA SR fanout requires new cabling. See cabling information provided below.

The z14 supports 10 PCIe fanout slots per CPC drawer which can be used for ICA SR coupling or connectivity to the PCIe I/O drawer in the I/O subsystem utilizing a PCIe I/O fanout. The ICA SR is only compatible with another ICA SR. IBM recommends that you order ICA SR features (#0172) on the z14 processors used in a Parallel Sysplex to help ensure coupling compatibility with future processor generations.

  • Minimum: None. Order increment is two links/ports.
  • Maximum: 40 (80 ports). The maximum number of all ICA SR fanout features is limited to 40 per system.
  • Prerequisites: None.
  • Corequisites: STP enablement (#1021).
  • Compatibility Conflicts: Only compatible with another ICA SR.
  • Customer Setup: No.
  • Limitations:
    • Maximum supported distance is 150 meters (492 feet). It cannot be repeated.
    • The ICA SR feature is only offered on z14, z13, and z13s servers.
  • Field Installable: Yes.
  • Cable Order: A customer-supplied 24x MTP-MTP cable is required for each port of the ICA SR fanout. It is single 24-fiber cable with Multi-fiber Termination Push-on (MTP) connectors. Internally, the single cable houses 12 fibers for transmit and 12 fibers for receive. Two fiber type options are available with specifications supporting different distances for the ICA SR:
    • 150m: OM4 50/125 micrometer multimode fiber optic cable with a fiber bandwidth @ wavelength: 4.7 GHz-km @ 850 nm.
    • 100m: OM3 50/125 micrometer multimode fiber optic cable with a fiber bandwidth @ wavelength: 2.0 GHz-km @ 850 nm.

Refer to Planning for Fiber Optic Links, GA23-1408, and to Maintenance for Fiber Optic Links, SY27-7696 which can be found in the Library section of Resource Link at

http://www.ibm.com/servers/resourcelink
(#0412) 10GbE RoCE Express2

10GbE RoCE Express2 provides a natively attached PCIe I/O Drawer based Ethernet feature that supports 10 Gbps Converged Enhanced Ethernet (CEE) and RDMA over CEE (RoCE). The RoCE feature, in conjunction with an OSA feature, enables shared memory communications between two CPCs using a shared switch. The RoCE feature will also be exploited by Linux on z Systems for applications that are coded to the native RoCE verb interface or use Ethernet (such as TCP/IP). This native exploitation does not require a peer OSA.

Single Root I/O Virtualization (SR-IOV) for 10 GbE RoCE allows a PCIe device to appear to be multiple separate physical PCIe devices. The SR-IOV specification is an industry standard specification to help promote interoperability. This provides the ability for that PCIe device to present multiple instances of itself up to the OS instance or hypervisor. RoCE continues to support SMC-R for z/OS to z/OS communication or for Linux for z Systems to Linux for z Systems communication.

  • Minimum: 0.
  • Maximum: 8. Orderable by ports, in increments of 2, up to16 ports (8 features).
  • Prerequisites: None.
  • Corequisites: PCIe I/O drawer (#4013).
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: Total limit of 8 RoCE Express + RoCE Express2 adapters for the machine.
  • Field Installable: Yes.
(#0420) zEDC Express

The IBM zEnterprise Data Compression (zEDC) acceleration capability in z/OS and the zEDC Express feature are designed to help improve cross-platform data exchange, reduce CPU consumption, and save disk space. There is one PCIe adapter/compression coprocessor per feature. The zEDC Express feature can be shared by up to 15 LPARs.

  • Minimum: None or one. A minimum of two is recommended.
  • Maximum: 16.
  • Prerequisites: None.
  • Corequisites: PCIe I/O drawer (#4013) and zEDC for z/OS feature.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property IBM.
  • Cable Order: None.
(#0422) OSA-Express6S GbE LX

The OSA-Express6S Gigabit Ethernet (GbE) long wavelength (LX) feature has one PCIe adapter and two ports. The two ports share one channel path identifier (CHPID type OSD exclusively - TCP/IP, Layer 2, Layer 3 traffic). The ports support attachment to a one gigabit per second (Gbps) Ethernet Local Area Network (LAN). Each port can be defined as a spanned channel and can be shared among logical partitions and across logical channel subsystems.

  • Minimum: 0.
  • Maximum: 48 features; any mix of OSA-Express6S and OSA-Express5S features.
  • Prerequisites: None.
  • Corequisites: PCIe I/O drawer (#4013).
  • Compatibility Conflicts: The OSA-Express6S GbE LX feature supports use of an LC Duplex connector. Ensure the attaching or downstream device has a long wavelength (LX) transciever. The sending and receiving transceivers must be the same (LX-to-LX).
  • Customer Setup: No.
  • Limitations: Total limit of 48 features for the machine. Any mix of OSA-Express6S and OSA-Express5S features.
  • Field Installable: Yes.
  • Cable Order: A customer-supplied cable is required. A 9 micron single mode fiber optic cable terminated with an LC Duplex connector.
(#0423) OSA-Express6S GbE SX

The OSA-Express6S Gigabit Ethernet (GbE) short wavelength (SX) feature has one PCIe adapter and two ports. The two ports share one channel path identifier (CHPID type OSD exclusively - TCP/IP, Layer 2, Layer 3 traffic). The ports support attachment to a one gigabit per second (Gbps) Ethernet Local Area Network (LAN). Each port can be defined as a spanned channel and can be shared among logical partitions and across logical channel subsystems.

  • Minimum: 0.
  • Maximum: 48 features; any mix of OSA-Express6S and OSA-Express5S features.
  • Prerequisites: None.
  • Corequisites: PCIe I/O drawer (#4013).
  • Compatibility Conflicts: The OSA-Express6S GbE SX feature supports use of an LC Duplex connector. Ensure the attaching or downstream device has a short wavelength (SX) transceiver. The sending and receiving transceivers must be the same (SX-to-SX).
  • Customer Setup: No.
  • Limitations: Total limit of 48 features for the machine. Any mix of OSA-Express6S and OSA-Express5S features.
  • Field Installable: Yes.
  • Cable Order: A customer-supplied cable is required. A 9 micron single mode fiber optic cable terminated with an LC Duplex connector.
(#0424) OSA-Express6S 10 GbE LR

The OSA-Express6S 10 Gigabit Ethernet (GbE) long reach (LR) feature has one PCIe adapter and one port per feature. The port supports channel path identifier (CHPID) types OSD (TCP/IP, Layer 2, Layer 3 traffic), and OSX (intraensemble data network - IEDN). The 10 GbE feature is designed to support attachment to a single mode fiber 10 Gigabit per second (Gbps) Ethernet Local Area Network (LAN) or Ethernet switch capable of 10 Gbps. The port can be defined as a spanned channel and can be shared among logical partitions within and across logical channel subsystems.

  • Minimum: 0.
  • Maximum: 48 features; any mix of OSA-Express6S and OSA-Express5S features.
  • Prerequisites: None.
  • Corequisites: PCIe I/O drawer (#4013).
  • Compatibility Conflicts: The OSA-Express6S 10 GbE LR feature supports use of an industry standard small form factor LC Duplex connector. Ensure the attaching or downstream device has a long reach (LR) transceiver. The sending and receiving transceivers must be the same (LR-to-LR).
  • Customer Setup: No.
  • Limitations:
    • Total limit of 48 features for the machine. Any mix of OSA-Express6S and OSA-Express5S features.
    • When defined as CHPID type OSX, the 10 GbE port provides connectivity and access control to the intraensemble data network (IEDN) from a z14, z13, z13s, zEC12, or zBC12 z196, or z114 to an IBM z BladeCenter Extension (zBX).
  • Field Installable: Yes.
  • Cable Order: A customer-supplied cable is required. A 9 micron single mode fiber optic cable terminated with an LC Duplex connector is required for connecting this feature to the selected device.
(#0425) OSA-Express6S 10 GbE SR

The OSA-Express6S 10 Gigabit Ethernet (GbE) short reach (SR) feature has one PCIe adapter and one port per feature. The port supports channel path identifier (CHPID) types OSD and OSX. The 10 GbE feature is designed to support attachment to a multimode fiber 10 gigabits per second (Gbps) Ethernet Local Area Network (LAN) or Ethernet switch capable of 10 Gbps. The port can be defined as a spanned channel and can be shared among logical partitions within and across logical channel subsystems.

  • Minimum: None.
  • Maximum: 48 features; any mix of OSA-Express6S and OSA-Express5S features.
  • Prerequisites: None.
  • Corequisites: PCIe I/O drawer (#4013).
  • Compatibility Conflicts: The OSA-Express6S 10 GbE SR feature supports use of an industry standard small form factor LC Duplex connector. Ensure the attaching or downstream device has a short reach (SR) transceiver. The sending and receiving transceivers must be the same (SR-to-SR).
  • Customer Setup: No.
  • Limitations:
    • Total limit of 48 features for the machine. Any mix of OSA-Express6S and OSA-Express5S features.
    • When defined as CHPID type OSX, the 10 GbE port provides connectivity and access control to the intraensemble data network (IEDN) from a z14, z13, z13s, zEC12, or zBC12, z196, or z114 to an IBM z BladeCenter Extension (zBX).
  • Field Installable: Yes.
  • Cable order: A customer-supplied cable is required. A 50 or a 62.5 micron multimode fiber optic cable terminated with an LC Duplex connector is required for connecting each port on this feature to the selected device.
(#0426) OSA-Express6S 1000BASE-T

The OSA-Express6S 1000BASE-T Ethernet feature has one PCIe adapter and two ports. The two ports share one channel path identifier (CHPID). The following CHPIDs are supported:

  1. OSC (TN3270E and non-SNA DFT)
  2. OSD (TCP/IP, Layer 2, Layer 3 traffic)
  3. OSE (SNA/APPN/HPR traffic and TCP/IP passthru)
  4. OSM (Intranode management network - INMN)

Each port supports attachment to a 1000BASE-T (1000 Mbps or 1 Gbps) Ethernet Local Area Network (LAN). The feature supports autonegotiation and automatically adjusts to 100 or 1000 Mbps, depending upon the LAN. When the feature is set to autonegotiate, the target device must also be set to autonegotiate. The feature supports 100 Mbps or 1000 Mbps (1 Gbps) full duplex. It can be defined as a spanned channel and can be shared among LPARs within and across LCSSs.

When configured at 1 Gbps, the 1000BASE-T Ethernet feature supports jumbo frames when in QDIO mode (CHPID type OSD).

  • Minimum: None.
  • Maximum: 48 features; any mix of OSA-Express6S and OSA-Express5S features.
  • Prerequisites: None.
  • Corequisites: PCIe I/O drawer (#4013).
  • Compatibility Conflicts: When the OSA-Express6S feature is set to autonegotiate, the target device must also be set to autonegotiate. Both ends must match (autonegotiate on or off).
  • Customer Setup: No.
  • Limitations:
    • Total limit of 48 features for the machine. Any mix of OSA-Express6S and OSA-Express5S features.
    • The 1000BASE-T feature supports full-duplex operation exclusively.
    • Using CHPID type OSM - OSA-Express for Unified Resource Manager, provides connectivity to the intranode management network (INMN) from z13 to Unified Resource Manager functions.
  • Field Installable: Yes.
  • Cable Order: A customer-supplied cable is required. The OSA-Express6S 1000BASE-T Ethernet feature supports use of an EIA/TIA Category 5 Unshielded Twisted Pair (UTP) cable terminated with an RJ-45 connector with a maximum length of 100 meters (328 feet).
(#0427) FICON Express16S+ LX

The FICON Express16S+ LX (long wavelength) feature conforms to the Fibre Connection (FICON) architecture, the High Performance FICON for z Systems (zHPF) architecture, and the Fibre Channel Protocol (FCP) architecture (supporting attachment to SCSI devices), providing connectivity between a combination of servers, directors, switches, and devices (control units, disk, tape, printers) in a storage area network (SAN). Each of the two independent ports/channels is capable of 4 gigabits per second (Gbps), 8 Gbps, or 16 Gbps depending upon the capability of the attached switch or device. The link speed is autonegotiated, point-to-point, and is transparent to users and applications. Each of the channels utilizes a small form factor pluggable (SFP) optic and is designed to be individually repaired without affecting the other channels.

FICON Express16S+ LX (CHPID type FC or FCP) can be defined as a spanned channel and can be shared among logical partitions and across logical channel subsystems. The FICON Express16S+ LX feature also supports cascading (the connection of two FICON Directors in succession) to minimize the number of cross-site connections and help reduce implementation costs for disaster recovery applications, GDPS, and remote copy. Each FICON Express16S+ LX channel can be defined independently, for connectivity to servers, switches, directors, disks, tapes, and printers as:

  1. CHPID type FC - FICON, High Performance FICON for z Systems (zHPF), and FICON Channel-to-Channel (CTC). FICON, FICON CTC, and zHPF protocols are supported simultaneously.

  2. CHPID type FCP - Fibre Channel Protocol which supports attachment to SCSI devices directly or through Fibre Channel switches or directors.

The FICON Express16S+ LX feature utilizes a long wavelength (LX) laser as the optical transceiver and supports use of a 9 micron single mode fiber optic cable terminated with an LC Duplex connector. LX may also be referred to as LW by vendors.

  • Minimum: None. At least one I/O feature (FICON) or coupling link feature (12x InfiniBand, 1x InfiniBand) must be present in a server.
  • Maximum: 160 features (320 channels) in PCIe I/O drawer (#4013).
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: Ensure the attaching/downstream device has a long wavelength (LX) transceiver. The sending and receiving transceivers must be the same (LX-to-LX).
  • Customer Setup: No.
  • Limitations:
    • Can only be installed in PCIe I/O drawer (#4013).
    • The FICON Express16S+ LX feature does not support autonegotiation to 1 or 2 Gbps.
    • The FICON Express16S+ LX feature is designed to support distances up to 10 kilometers (6.2 miles) over 9 micron single mode fiber optic cabling without performance degradation. To avoid performance degradation at extended distance, FICON switches or directors for buffer credit provisioning may be required.
  • Field Installable: Yes.
  • Cable Order: A customer-supplied cable is required. A 9 micron single mode fiber optic cable terminated with an LC Duplex connector is required for connecting this feature to the selected device.
(#0428) FICON Express16S+ SX

The FICON Express16S+ SX (short wavelength) feature conforms to the Fibre Connection (FICON) architecture, the High Performance FICON for z Systems (zHPF) architecture, and the Fibre Channel Protocol (FCP) architecture (supporting attachment to SCSI devices), providing connectivity between a combination of servers, directors, switches, and devices (control units, disk, tape, printers) in a storage area network (SAN).

Each of the two independent ports/channels is capable of 4 gigabits per second (Gbps), 8 Gbps, or 16 Gbps depending upon the capability of the attached switch or device. The link speed is autonegotiated, point-to-point, and is transparent to users and applications. Each of the channels utilizes a small form factor pluggable (SFP) optic and is designed to be individually repaired without affecting the other channels. FICON Express16S+ SX (CHPID type FC or FCP) can be defined as a spanned channel and can be shared among logical partitions and across logical channel subsystems.

The FICON Express16S+ SX feature also supports cascading (the connection of two FICON Directors in succession) to minimize the number of cross-site connections and help reduce implementation costs for disaster recovery applications, GDPS, and remote copy.

Each FICON Express16S+ SX channel can be defined independently for connectivity to servers, switches, directors, disks, tapes, and printers as:

  1. CHPID type FC - FICON, High Performance FICON for z Systems (zHPF), and FICON Channel-to-Channel (CTC). FICON, FICON CTC, and zHPF protocols are supported simultaneously.

  2. CHPID type FCP - Fibre Channel Protocol which supports attachment to SCSI devices directly or through Fibre Channel switches or directors.

The FICON Express16S+ SX feature utilizes a short wavelength (SX) laser as the optical transceiver, and supports use of a 50 micron multimode fiber optic cable or a 62.5 micron multimode fiber optic cable terminated with an LC Duplex connector.

Note: IBM does not support a mix of 50 and 62.5 micron fiber optic cabling in the same link. SX may also be referred to as SW by vendors.

  • Minimum: None. At least one I/O feature (FICON) or coupling link feature (12x InfiniBand, 1x InfiniBand) must be present in a server.
  • Maximum: 160 features (320 channels) in PCIe I/O drawer (#4013).
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: Ensure the attaching/downstream device has a short wavelength (SX) transceiver. The sending and receiving transceivers must be the same (SX to SX).
  • Customer Setup: No.
  • Limitations:
    • Can only be installed in PCIe I/O drawer (#4013).
    • The FICON Express16S+ SX feature does not support autonegotiation to 1 or 2 Gbps. To avoid performance degradation at extended distance, FICON switches or directors for buffer credit provisioning may be required.
    • For unrepeated distances for FICON Express16S+ SX refer to Planning for Fiber Optic Links, GA23-1408 available in the Library section of Resource Link:
      http://www.ibm.com/servers/resourcelink
  • Field Installable: Yes.
  • Cable Order: A customer-supplied cable is required. A 50 or a 62.5 micron multimode fiber optic cable terminated with an LC Duplex connector is required for connecting each port on this feature to the selected device.
(#0429) OSA-Express7S 25 GbE SR

Description: The OSA-Express7S 25 Gigabit Ethernet (GbE) short reach (SR) feature can add significant speed and a new Network Interface Card (NIC) module unit, and benefits from prior level OSA-Express6S 10 GbE performance and reliability. There is one PCIe adapter and one port per feature. This adapter allows for some potential consolidation of prior level adapters.

  • Maximum Number of Features: 48
  • Minimum Number of Features: 0
  • Prerequisites: None
  • Corequisites: None.
  • Compatibility conflicts: None.
  • Limitations: Consult ResourceLink for adapter consolidation planning.
  • Field/Plant Installable: Yes.
  • Customer setup: No
  • Cable Order: No
(#0430) 25GbE RoCE Express2

Description: The 25GbE RoCE Express2 with z14 GA2 code can provide flexibility for clients to consolidate adapters or increase overall speed, while still seeing high reliability and performance established on prior adapters. There is one PCIe adapter, one PCHID, and two ports per feature. Note that the benefit of the (#0430)25GbE RoCE Express2 is only recognized when connected to another (#0430) 25GbE RoCE Express2, so planning teams may need to order multiple features when upgrading from prior adapters.

  • Maximum Number of Features: 8 (Any combination of(#0412) 1 (#0430)
  • Minimum Number of Features: 0
  • Prerequisites: None
  • Corequisites: (#0430)25GbE RoCE Express2 requires the connection endpoint to also be (#0430) 25GbE RoCE Express2
  • Compatibility conflicts: None
  • Limitations: Consult ResourceLink for adapter consolidation planning.
  • Field/Plant Installable: Yes
  • Customer setup: No
  • Cable Order: No
(#0431) IBM zHyperLink Express

IBM zHyperLink Express is a short distance, IBM Z I/O adapter which works in conjunction with a FICON SAN infrastructure. This feature is a 2 port adapter which resides in the z14 PCIe I/O drawer and supports direct connectivity to FICON storage systems at distances up to 150m.

  • Minimum: 0.
  • Maximum: 16 (32 ports).
  • Prerequisites: PCIe I/O drawer (#4013).
  • Corequisites: FICON connectivity to each storage system connected via zHyperLinks.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: 150m max distance in a point to point configuration.
  • Field Installable: Yes.
  • Cable Order: A customer-supplied 24x MTP-MTP cable is required for each port of the zHyperLink Express feature. It is single 24-fiber cable with Multi-fiber Termination Push-on (MTP) connectors. Internally, the single cable houses 12 fibers for transmit and 12 fibers for receive. Two fiber type options are available with specifications supporting different distances for the zHyperLink Express:
    • 150m: OM4 50/125 micrometer multimode fiber optic cable with a fiber bandwidth @ wavelength: 4.7 GHz-km @ 850 nm.
    • 100m: OM3 50/125 micrometer multimode fiber optic cable with a fiber bandwidth @ wavelength: 2.0 GHz-km @ 850 nm.
(#0433) Coupling Express LR

Coupling Express LR (CE LR) is a 2-port feature used for long distance coupling connectivity and utilizes a new coupling channel type: CL5. It utilizes 10GbE RoCE technology and is designed to drive distances up to 10km unrepeated and support a link data rate of 10 Gigabits per second (Gbps). For distance requirements greater than 10km, clients must utilize a Dense Wavelength Division Multiplexer (DWDM). The DWDM vendor must be qualified by IBM Z.

To access DWDM vendor qualification letters go to:

http://www.ibm.com/servers/resourcelink/
  • On the left, click on "Library"
  • In the middle you will see "Hardware products for servers"
  • Click on "z Systems Qualified Wavelength Division Multiplexer (WDM) products for GDPS solutions"
  • Click on the vendor of your choice to view the qualification letters

Note: A link data rate of 10 Gbps does not represent the actual performance of the link.

  • Minimum: 0.
  • Maximum: 32 features (64 ports). The card is orderable by ports, in increments of 2.
  • Prerequisites: None known.
  • Corequisites: PCIe I/O drawer (#4013). STP enablement (#1021).
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations:
    • An unrepeated distance of 10km (6.2 miles) is supported. Greater distances are supported when attached to an IBM Z -qualified optical networking solution (i.e. DWDM).
    • The CE LR feature is offered on z14, z13, and z13s servers.
  • Field Installable: Yes.
  • Cable Order: A customer-supplied cable is required. A 9/125 micrometer single mode fiber optic cable terminated with an LC Duplex connector is required. A cable is required for each port on the feature.
(#0604) IBM Virtual Flash Memory (VFM)

Provides up to 6.0 TB of virtual flash memory in 1.5 TB increments. Virtual Flash Memory is a replacement for zFlash Express memory.

  • Minimum: 0.
  • Maximum: 4. VFM memory ordered reduces the maximum orderable memory for the model.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes.
(#0609) IBM Db2 Analytics Accelerator on Z (IDAA on Z)

IBM Db2 Analytics Accelerator on Z hardware delivers a new deployment option on IBM z14. This deployment option is based on the premier IBM analytical engine, Db2 Warehouse software, and provides support for IBM z14, within Integrated Facility for LinuxB. (IFL) processors (purchased seperately) and without the need to attach a separate appliance. IDAA on Z also requires the purchase of 2.5TB of memory.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: CPC Drawer, additional 2.5TB of Memory and 35 IFLs.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None known.
  • Field Installable: Yes. Parts removed as a result of feature removals become the property of IBM.
  • Cable order: None.
(#0844) 4768 TKE Crypto Adapter

The stand-alone crypto card is ordered when you are doing one of the upgrades listed above using #0080, #0081, or #0849.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: (#0842) or (#0847) or (#0097) or (#0098).
  • Corequisite: Your current workstation is a feature code 0842, 0847, 0092, or 0098. (This is a prerequisite not a co requisite)
  • Compatibility Conflicts: None.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes. Parts removed as a result of feature change become the property of IBM.
  • Cable Order: None.
(#0848) 32GB USB Backup Media

An optional feature which will provide additional backup coverage for configurations which require additional coverage.

  • Minimum: 0.
  • Maximum: 99.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None Known.
  • Customer Setup: No.
  • Limitations: None known.
  • Field Installable: Yes.
(#0849) TKE workstation w/4768

Feature code 0849 is a TOWER TKE at Version 9.0 (#0879). The only way to build a (#0849) is to upgrade an existing (#0847) TOWER TKE or existing (#0842) TOWER TKE to TKE 9.0. This upgrade requires the TKE LIC to be upgraded to TKE 9.0 and the TKE local crypto adapter to be changed from a 4765 or 4767 to a 4768.

Note: TKE 9.0 is required if you choose to use the TKE to manage a Crypto Express6S. TKE 9.0 is also required to manage the new CCA mode PCI-HSM settings which are available on the Crypto Express6S. A TKE is required to manage any Crypto Express feature that is running in IBM Enterprise PKCS #11 (EP11) mode. CCA in PCI-HSM mode and EP11 also require a smartcard reader plus FIPS certified smart cards.

  • Minimum: 0.
  • Maximum: 10.
  • Prerequisites: (#0842) or (#0847).
  • Corequisite: TKE 9.0 LIC (#0879) and MT 4768 adapter (#0844).
  • Compatibility Conflicts: There are smart card reader and smart card considerations:
    • You can carry your smart card readers from feature code 0885 or 0891 forward. Existing smart cards can be used on TKE 9.0 with these readers.
    • You can also order new smart card readers with feature code #0891.

    Note: If you have smart cards with applets not supported by the new smart card reader, you must create new smart cards on TKE 8.1 or later and copy the content from the old smart cards to the new smart cards. The new smart cards can be created and copied on a TKE 8.1 system. If the copies are done on TKE 9.0, the source smart card must be placed in an older smart card reader from feature code 0885 or 0891.

  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes. Parts removed as a result of feature change become the property of IBM.
  • Cable Order: LAN cabling is a customer responsibility. A Category 5 Unshielded Twisted Pair (UTP) cable terminated with RJ-45 connector is required.
(#0879) TKE 9.0 LIC

The Trusted Key Entry (TKE) 9.0 level of Licensed Internal Code (LIC) is installed in a TKE workstation (#0080, 0081, 0085, 0086, or 0849). TKE 9.0 LIC is a no-charge enablement feature which is loaded prior to shipment when a TKE workstation is ordered. The TKE 9.0 LIC includes support for the Smart Card Reader (#0891).

  • Minimum: 0.
  • Maximum: 10.
  • Prerequisites: TKE workstation (#0080, 0081, 0085, 0086, or 0849).
  • Corequisites: CPACF (#3863) or Crypto Express6S (#0893).
  • Compatibility Conflicts: TKE workstations with TKE 9.0 LIC can also be used to control IBM z13, z13s, zEC12, zBC12, z196, and z114 servers.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes. Parts removed as a result of feature change become the property of IBM.
(#0880) TKE 9.1 LIC

Description: The Trusted Key Entry (TKE) 9.1 level of Licensed Internal Code (LIC) is installed in a TKE workstation (#0080, 0081, 0085, 0086, or 0849). TKE 9.1 LIC is a no-charge enablement feature which is loaded prior to shipment when a TKE workstation is ordered. The TKE 9.1 LIC includes support for the Smart Card Reader (#0891) and (#0895)

z14 Models M01-M05 (MT 3906) :

  • Maximum Number of Features: 10
  • Minimum Number of Features: 0
  • Prerequisites: TKE workstation (#0080, 0081, 0085, 0086, or 0849).
  • Corequisites: CPACF (#3863) or Crypto Express6S (#0893).
  • Compatibility: TKE workstations with TKE 9.1 LIC can also be used to control IBM z13, z13s, zEC12, zBC12, z196, and z114 servers.
  • Limitations: None
  • Field/Plant Installable: Yes
  • Customer setup: No
  • Cable Order: None
(#0891) TKE Smart Card Reader

The TKE Smart Card Reader feature supports the use of smart cards, which resemble a credit card in size and shape, but contain an embedded microprocessor, and associated memory for data storage. Access to and the use of confidential data on the smart cards is protected by a user-defined Personal Identification Number (PIN). This feature is optional when used with the TKE workstation to manage a Crypto Express6S feature that is defined as a Common Cryptographic Architecture (CCA) coprocessor. This feature is required when used with the TKE workstation to manage a Crypto Express6S feature that is defined as an IBM Enterprise PKCS #11 (EP11) coprocessor.

The TKE 9.0 level of LIC (#0879) allows the storing of the following on smart cards:

  • CCA master and operational key parts.
  • Crypto Adapter Logon keys - keys used to sign onto the TKE workstation when using smart card profiles.
  • Authority Signature Key - key associated with an authority index on a Crypto Express feature.
  • EP11 master key material and administrator certificates.
  • Migration zones - used in the process of migrating data from one feature to another.

One (1) feature includes two Smart Card Readers, two cables to connect to the TKE 9.0 workstation, and 20 smart cards.

  • Minimum: 0.
  • Maximum: 20.
  • Prerequisites: CP Assist for Cryptographic Function (#3863) or Crypto Express6S (#0893 or 0890).
  • Corequisites: TKE workstation (#0080, 0081, 0085, 0086 or 0849) with 9.0 level of LIC (#0879) for secure key parts entry and Crypto hardware management or ISPF panels for clear key entry and Crypto hardware management. If EP11 is to be defined, smart cards used require FIPS certification.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes.
  • Cable Order: None. External cables to connect two Smart Card Readers to the TKE workstation are shipped with the feature.
(#0893) Crypto Express6S

The Crypto Express6S feature is designed to satisfy IBM Z server security requirements. It contains one PCIe adapter which can be configured as a coprocessor supporting secure key transactions or as an accelerator for Secure Sockets Layer (SSL) operations. This feature can be configured, via the Service Element (SE) panels, in one of three ways: as an IBM Common Cryptographic Architecture (CCA) coprocessor, as an IBM Enterprise PKCS #11 (EP11) coprocessor, or as an accelerator. The tamper-resistant hardware security module, which is contained on the Crypto Express6S feature, is designed to conform to the Federal Information Processing Standard (FIPS) 140-2 Level 4 Certification. It supports User Defined Extension (UDX) services to implement cryptographic functions and algorithms (when defined as an IBM CCA coprocessor).

  • Minimum: None or two. An initial order is two features, one thereafter.
  • Maximum: 16.
  • Prerequisites: CP Assist for Cryptographic Function (CPACF) (#3863).
  • Corequisites: TKE workstation (#0080, 0081, 0085, 0086 or 0849) is optional when used to manage a Crypto Express6S feature that is defined as a CCA coprocessor in normal mode, but is mandatory when used to manage a Crypto Express6S feature that is defined as a CCA coprocessor in PCI-HSM mode or that is defined as an EP11 coprocessor (CCA in PCI-HSM mode and EP11 also require a smartcard reader plus smart cards with FIPS certification).
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes. Parts removed as a result of feature change become the property of IBM.
  • Cable Order: None.
(#0900) TKE additional Smart Cards

Description: TKE Smart Cards contain an embedded microprocessor, and associated memory for data storage. Access to and the use of confidential data on the smart cards is protected by a user-defined Personal Identification Number (PIN). Cards are FIPS certified blank 10-packs. TKE 9.1 is the minimum supported release for the (#0900) (blue) smart card. You may not use the (#0900) smart card on any TKE below TKE 9.1

  • Maximum Number of Features: 99
  • Minimum Number of Features: 0
  • Prerequisites: None
  • Corequisites: TKE 9.1 LIC (#0880)
  • Compatibility conflicts: Only usable on TKE 9.1 or later.
  • Limitations: None
  • Field/Plant Installable: Yes
  • Customer setup: Yes
  • Cable Order: None.
(#1021) STP enablement

Time synchronization and time accuracy: If you require time synchronization across multiple servers (for example you have a Parallel Sysplex) or you require time accuracy either for one or more IBM Z servers or you require the same time across heterogeneous platforms (IBM Z, Unix, AIX, etc) you can meet these requirements by implementing Server Time Protocol (STP).

Server Time Protocol is a server-wide facility that is implemented in the Licensed Internal Code (LIC) 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 coupling links.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: For STP message passing to provide time synchronization across multiple IBM Z servers, either (#0170) HCA3-O LR fanout for 1x InfiniBand, or (#0171) HCA3-O fanout for 12x InfiniBand, (#0172) IBM Integrated Coupling Adapter (ICA SR) fanout, or (#0433) Coupling Express LR (CE LR) adapter.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None known.
  • Field Installable: Yes. Delivered in vital product data (VPD) enablement media. Parts removed as a result of feature conversions become the property of IBM.
  • Cable Order: None.
(#1750) Licensed Internal Code (LIC) ship using Net Indicator

This indicator flag is added to orders that are Licensed Internal Code (LIC) only and delivered by web tools. No hardware is shipped. The flag is generated by the system and is not orderable.

(#1929) Central Processor 4 (CP4)

Processor Unit characterization option. The CP4 is the Processor Unit purchased and activated supporting the z/OS, z/VM, z/VSE, z/TPF, Linux on z Systems and KVM on z operating systems.

  • Minimum: 0.
  • Maximum: 33.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Field Installable: Yes.
(#1930) Central Processor 5 (CP5)

Processor Unit characterization option. The CP5 is the Processor Unit purchased and activated supporting the z/OS, z/VM, z/VSE, z/TPF, Linux on z Systems and KVM on z operating systems.

  • Minimum: 0.
  • Maximum: 33.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Field Installable: Yes.
(#1931) Central Processor 6 (CP6)

Processor Unit characterization option. The CP6 is the Processor Unit purchased and activated supporting the z/OS, z/VM, z/VSE, z/TPF, Linux on z Systems and KVM on z operating systems.

  • Minimum: 0.
  • Maximum: 33.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Field Installable: Yes.
(#1932) Central Processor 7 (CP7)

Processor Unit characterization option. The CP7 is the Processor Unit purchased and activated supporting the z/OS, z/VM, z/VSE, z/TPF, Linux on z Systems and KVM on z operating systems.

  • Minimum: 0.
  • Maximum: 170.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Field Installable: Yes.
(#1933) Integrated Facility for Linux (IFL)

Processor Unit characterization option. The IFL is a Processor Unit that is purchased and activated for exclusive use of Linux on IBM z14.

  • Minimum: 0.
  • Maximum: 170.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Field Installable: Yes.
(#1934) Internal Coupling Facility (ICF)

Processor Unit characterization option. The ICF is a Processor Unit purchased and activated for exclusive use by the Coupling Facility Control Code (CFCC).

  • Minimum: 0.
  • Maximum: 170.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Field Installable: Yes.
(#1935) System Assist Processor (SAP), optional

Processor Unit characterization option. The purpose of the SAP feature is to designate Processor Units to be used specifically for assisting I/O operations. The optional SAP is a Processor Unit that is purchased and activated for use as a SAP. This optional SAP is a chargeable feature.

  • Minimum: 0.
  • Maximum: 16.
  • Prerequisites: One CP4 (#1929), CP5 (#1930), CP6 (#1931), CP7 (#1932), IFL (#1933), or ICF (#1934).
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Field Installable: Yes.
(#1936) IBM z Integrated Information Processor (zIIP)

Processor Unit characterization option. The zIIP is a Processor Unit purchased and activated to accept all zIIP-eligible work.

  • Minimum: 0.
  • Maximum: 112.
  • Prerequisites: For every 2 zIIPs installed there must be a corresponding CP permanently purchased and installed.
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None known.
  • Field Installable: Yes.
(#1937) Unassigned Integrated Facility for Linux (IFL)

Processor Unit characterization option. An unassigned IFL is a Processor Unit purchased for future use as an IFL (#1919). It is offline and available for use.

  • Minimum: 0.
  • Maximum: 169.
  • Prerequisites: One CP4 (#1929), CP5 (#1930), CP6 (#1931), CP7 (#1932), IFL (#1933), or ICF (#1934).
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Field Installable: Yes.
(#1990) 32GB PrePlanned Memory:

Preplanned Memory provides the ability to plan for non-disruptive memory upgrades. The hardware required is pre-plugged based on a target capacity specified by the customer. This pre-plugged hardware will be enabled via a LICCC order placed by the customer when he has determined additional memory capacity is needed.

  • Minimum: 0.
  • Maximum: 250.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None known.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
  • Cable Order: None.
(#1999) 64GB IBM Virtual Flash Memory PrePlanned Memory

Preplanned Memory provides the ability to plan for non-disruptive memory upgrades. The hardware required is pre-plugged based on a target capacity calculated by the configurator when flexible memory has been selected. This pre-plugged hardware will be enabled via a LICCC order.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: Flexible memory option.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None known.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
  • Cable Order: None.
(#2000) Line cord plan ahead

This option provides the ability to plan ahead for the second set of line cords. Must be same feature selection as initial set. The Plan Ahead function provides the means of ordering now, the hardware that will be required in the future to help avoid a disruptive hardware install in the future.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: Line cords must be same feature selection as initial set.
  • Customer Setup: No.
  • Limitations: None known.
  • Field Installable: No.
(#3003) Balanced Power Plan Ahead

Phase currents are minimized when they are balanced among the three input phases. Balanced Power Plan Ahead is designed to allow you to order the full complement of bulk power regulators (BPRs) on any configuration, to help ensure that the configuration will be in a balanced power environment.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: May require additional internal battery features (#3216) and line cords. Configuration tool will determine. Second set of line cords is a corequisite.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None known.
  • Field Installable: Yes. It is disruptive.
  • Cable Order: None.
(#3103) Universal lift tool upgr kit

This feature supplies new rails to permit CPC drawers to slide in/out of the IBM z14 frame when carrying forward feature code #3759 from zEC12, zBC12 or systems.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: #3759.
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None known.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
  • Cable Order: None.
(#3105) Universal lift tool/ladder

This feature supplies the full kit required for the service of IBM z14 systems. It includes new rails to permit CPC drawers to slide in/out of the IBM z14 frame.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None known.
  • Field Installable: Yes. One #3105 is required per site. Two #3105 are recommended for larger sites. Parts removed as a result of feature conversions become the property of IBM.
  • Cable Order: None.
(#3216) Internal Battery (IBF)

The IBF is the internal battery backup feature offered on IBM z14. When selected, the actual number of IBFs is determined based on the power requirements and model. The batteries are installed in pairs.

  • Minimum: 0 or one pair.
  • Maximum: Three pairs.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None known.
  • Field Installable: Yes.
  • Cable Order: None.
(#3379) Fill and Drain adapter kit

This feature supplies new hose attachments which are required for the service of IBM z14 systems when carrying forward feature code #3378 from zEC12.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: #3378.
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None known.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
  • Cable Order: None.
(#3380) Fill and Drain kit

This feature supplies the full fill and drain kit required for the service of IBM z14 systems. It includes the hose adapters/fittings required for connection of a IBM z14.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None known.
  • Field Installable: Yes. One #3380 is required per site. Two #3380 are recommended for larger sites. Parts removed as a result of feature conversions become the property of IBM.
  • Cable Order: None.
(#3863) CP Assist for Cryptographic Function (CPACF) enablement

CPACF, supporting clear and protected key encryption, is activated using the no-charge enablement feature (#3863). It offers the following:

  • For data privacy and confidentially: Data Encryption Standard (DES), Triple Data Encryption Standard (TDES), Advanced Encryption Standard (AES) for 128-bit, 192-bit and 256-bit keys.
  • For data integrity: Secure Hash Algorithm-1 (SHA-1) 160-bit, and SHA-2 for 224-, 256-, 384-and 512-bit support. SHA-3 for 224-, 256- 384-, 512 bit support, and SHAKE for 128-, and 256 bit support. SHA-1, SHA-2 and SHA3 are shipped enabled on all IBM z14 's and do not require the no-charge enablement feature.
  • For Key Generation: Pseudo Random Number Generation (PRNG), Deterministic Random Number Generation (DRNG), and True Random number generation (TRNG).
  • New z14 CPACF instructions for SHA-3 hashing, TRNG (True Random NumberGeneration), and Improved performance of AES GCM encryption.

For new servers, shipped from the factory, CPACF enablement (#3863) is loaded prior to shipment. For other than new shipments, Licensed Internal Code is shipped on media. The function is enabled using the Support Element (SE).

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisite: Crypto Express6S (#0893) or Crypto Express5S (#0890).
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes.
(#4013) PCIe I/O drawer

The Peripheral Component Interconnect Express (PCIe) I/O drawer is a physical resource used to house I/O cards in support of cryptography (Crypto Express6S), Regional Crypto Enablement (RCE), the storage area network (FICON Express16S or FICON Express16S+, and IBM zHyperLink Express), the Ethernet local area network (OSA-Express5S, OSA-Express6S, and 10GbE RoCE Express, 10GbE RoCE Express2), Coupling Express LR, and compression (zEDC Express). The PCIe I/O drawer contains 32 I/O slots; 16 I/O slot in the front and 16 I/O slots in the rear. The number of PCIe I/O drawers is automatically determined by the number of Crypto Express6S, RCE, FICON Express16S, FICON Express16S+, zHyperLink Express, OSA-Express5S, OSA-Express6S, RoCE Express, RoCE Express2, Coupling Express LR, or zEDC Express features ordered.

  • Minimum: 0.
  • Maximum: 5.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
  • Cable Order: Cables for I/O features are a customer responsibility.
(#4029) A Frame - Radiator
  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None known.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
  • Cable Order: None.
(#4030) A Frame - Water
  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None known.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
  • Cable Order: None.
(#6096) Flat-panel display

The display offers the benefits of a flat-panel monitor including improved use of space and reduced energy consumption compared to CRT monitors.

  • Minimum: 0.
  • Maximum: Ten (10).
  • Prerequisites: HMC #0082 or TKE #0086.
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes. Parts removed as a result of feature conversion become the property of IBM.
  • Cable Order: None.
(#6805) Additional CBU Test

An additional test activation that can be purchased with each CBU temporary entitlement record. There can be no more than 15 tests per CBU TER.

  • Minimum: 0.
  • Maximum: 15 per each instance of #6818, Capacity back up, CBU.
  • Prerequisites: Capacity back up (#6818).
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes.
(#6817) Capacity back up (CBU) years

Used to set the expiration date of a Capacity back up (CBU) temporary entitlement record.

  • Minimum: 0.
  • Maximum: Five (5).
  • Prerequisites: Capacity back up (#6818).
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: Not applicable.
  • Limitations: None.
  • Field Installable: Yes.
(#6818) Capacity back up (CBU) records ordered

This feature code corresponds to the number of different CBU Temporary Entitlement Records (TERs) ordered. Each CBU TER contains configuration data corresponding to the number of years, number of tests, and various engine types.

  • Minimum: 0.
  • Maximum: Eight (8) per ordering session.
  • Prerequisites: None.
  • Corequisites: CBU Authorization (#9910).
  • Compatibility Conflicts: None known.
  • Customer Setup: The CBU TER must be installed using the HMC Configuration Manager before it can be activated.
  • Limitations: None.
  • Field Installable: Yes.
(#6820) Single CBU CP-year

Pricing feature equal to the number of CBU years multiplied by the number of temporary CP capacity features, if less than 25 or the remainder after dividing by 25.

  • Minimum: 0.
  • Maximum: 24.
  • Prerequisites: Capacity back up (#6818).
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes.
(#6821) 25 CBU CP-year

Pricing feature equal to the quotient of the number of CBU years multiplied by the temporary Central Processor (CP) capacity features divided by 25.

  • Minimum: 0.
  • Maximum: 250.
  • Prerequisites: Capacity back up (#6818).
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes.
(#6822) Single CBU IFL Year : Pricing feature equal to the
number of CBU years multiplied by the number of temporary IFL features, if less than 25 or the remainder after dividing by 25.
  • Minimum: 0.
  • Maximum: 24.
  • Prerequisites: Capacity back up (#6818).
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes.
(#6823) 25 CBU IFL-Year

Pricing feature equal to the quotient of the number of CBU years multiplied by the number of temporary IFL features divided by 25.

  • Minimum: 0.
  • Maximum: 250.
  • Prerequisites: Capacity back up (#6818).
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes.
(#6824) Single CBU ICF-Year

Pricing feature equal to the number of CBU years multiplied by the number of temporary ICF features, if less than 25 or the remainder after dividing by 25.

  • Minimum: 0.
  • Maximum: 24.
  • Prerequisites: Capacity back up (#6818).
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes.
(#6825) 25 CBU ICF-Year

Pricing feature equal to the quotient of the number of CBU years multiplied by the number of temporary Internal Coupling Facility (ICF) features divided by 25.

  • Minimum: 0.
  • Maximum: 250.
  • Prerequisites: Capacity back up (#6818).
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes.
(#6828) Single CBU zIIP-Year

Pricing feature equal to the number of CBU years multiplied by the number of temporary zIIP features, if less than 25 or the remainder after dividing by 25.

  • Minimum: 0.
  • Maximum: 24.
  • Prerequisites: Capacity back up (#6818).
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes.
(#6829) 25 CBU zIIP-Year

Pricing feature equal to the quotient of the number of CBU years multiplied by the number of temporary zIIP features divided by 25.

  • Minimum: 0.
  • Maximum: 250.
  • Prerequisites: Capacity back up (#6818).
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes.
(#6830) Single CBU SAP-Year

Pricing feature equal to the number of CBU years multiplied by the number of temporary SAP features, if less than 25 or the remainder after dividing by 25.

  • Minimum: 0.
  • Maximum: 24.
  • Prerequisites: Capacity back up (#6818).
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes.
(#6831) 25 CBU SAP-Year

Pricing feature equal to the quotient of the number of CBU years multiplied by the number of temporary System Assist Processor (SAP) features divided by 25.

  • Minimum: 0.
  • Maximum: 250.
  • Prerequisites: Capacity back up (#6818).
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes.
(#6832) CBU Replenishment

This feature is used to restore the ability to activate a CBU TER. Each CBU TER comes with a default of one activation. An activation enables the resources required for disaster recovery. After an activation, no subsequent activations nor any additional testing of this CBU TER can occur until this feature is ordered.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: Capacity back up (#6818).
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes.
(#6833) Capacity for Planned Event (CPE)

This feature code corresponds to the number of different CPE Temporary Entitlement Records (TERs) ordered.

  • Minimum: 0.
  • Maximum: Eight (8) per ordering session.
  • Prerequisites: None.
  • Corequisites: CPE authorization (#9912).
  • Compatibility Conflicts: None known.
  • Customer Setup: The CBU TER must be installed using the HMC Configuration Manager before it can be activated.
  • Limitations: None.
  • Field Installable: Yes.
(#7801) 14ft Water hoses

This feature supplies the water hose required for water cooled systems. It is supplied when ordering water cooled features #1028, #1029, #1030, #1031, or #1032.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: #1028, #1029, #1030, #1031, or #1032.
  • Corequisites: None.
  • Compatibility Conflicts: None.
  • Customer Setup: No.
  • Limitations: #7801 is mutually exclusive with non-raised floor option #7998.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
  • Cable Order: None.
h4.Fiber Quick Connect (#7923, #7924, #7925, #7926)

The Fiber Quick Connect (FQC) features, bracket and mounting hardware (#7923) and LC Duplex 6.6 feet (2 meter) harnesses (#7924), are optional features for factory installation of the IBM Fiber Transport System (FTS) fiber harnesses for connection to FICON LX adapters (#0409, #0418 or #0427) in a PCIe I/O drawer. FQC is offered on a frame-roll so the cabling is pre-plugged for carry forward cards. Fiber Quick Connect is for factory installation only, and is available on new servers and on initial upgrades to IBM z14. FQC is not available as an MES to an existing IBM z14. Each direct-attach fiber harness connects to six FICON LX channels at one end and one coupler in a multi-terminated push-on connector (MTP) coupler bracket at the opposite end.

When FQC is ordered, the configuration tool selects the required number of MTP mounting brackets and mounting hardware based upon the FICON LX feature quantity.

Note: FQC supports all of the FICON LX adapters. FQC cannot be ordered for selected channels.

(#7942) Top exit I/O cabling

When top exit I/O cabling is selected on an order, the required infrastructure is provided. Frame extensions are added to each corner of the system with this option. Routing of cabling from I/O drawers or PCIe I/O drawers will exit out the top of the frame (either the "A" or the "Z" frame). Top exit I/O cabling applies to all of your fiber optic cables (FICON Express, OSA-Express, 12x InfiniBand, 1x InfiniBand, ICA SR, and Coupling Express LR) as well as your copper cables for the OSA-Express 1000BASE-T Ethernet features.

Top exit I/O cabling is designed to provide you with an additional option. Instead of all of your cabling exiting under the server and/or under the raised floor, you now have the flexibility to choose the option that best meets the requirements of your data center. Top exit I/O cabling can also help to increase air flow.

In a raised floor environment, if Top exit I/O cabling (#7942) is selected, the power cord selection can be top exit or bottom exit. In a non-raised floor environment, if Top exit I/O cabling is selected then a top exit I/O power cord must also be selected as these are co-requisites with the non-raised floor option (#7998).

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: Cannot coexist with side covers (#7949).
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
  • Cable Order: Cabling is a customer responsibility.
(#7949) Side covers

Supplies a set of 2 side covers required for IBM z14.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: Mutually exclusive with #7942 and #7998.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
  • Cable Order: None.
(#7998) Non-Raised Floor Support
  • Minimum: 0.
  • Maximum: 1. (for a two-frame system)
  • Corequisites: Top exit I/O cabling (#7942) and a top exit power cord.
  • Limitations: Water cooling is mutually exclusive with the non-raised floor support (#7998).
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
(#8003) 4-in-1 Bolt Down Kit

This feature applies to a raised-floor environment. This feature supplies the kit of parts that is designed to help secure the frames and their contents from damage when exposed to vibrations and shocks such as those in a seismic event. The kit includes hardware to cover all four floor depth options, 6 to 9 inches (15 to 23 cm), 9 to 13 inches (23 to 33 cm) 12 to 22 inches (30 to 56 cm), and 12 to 36 inches (30 to 91 cm).

  • Minimum: 0.
  • Maximum: 1. (for a two-frame system)
  • Prerequisites: None.
  • Corequisites: A Frame Radiator (4029).
  • Compatibility Conflicts: Mutually exclusive with features 7998, 8004 and 8005.
  • Customer Setup: No.
  • Limitations: None known.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
(#8004) 3 in1 Bolt Down Kit-W

This feature applies to a raised-floor environment. This feature supplies the kit of parts that is designed to help secure the frames and their contents from damage when exposed to vibrations and shocks such as those in a seismic event. The kit includes hardware to cover all three floor depth options, 9 to 13 inches (23 to 33 cm) 12 to 22 inches (30 to 56 cm), and 12 to 36 inches (30 to 91 cm).

  • Minimum: 0.
  • Maximum: 1 (for a two-frame system).
  • Prerequisites: None.
  • Corequisites: A Frame Water (4030).
  • Compatibility Conflicts: Mutually exclusive with features 7998, 8003 and 8005.
  • Customer Setup: No.
  • Limitations: None known.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
(#8005) Bolt-Down Kit, non-raised floor (NRF)

This feature supplies the kit of parts that are designed to help secure the frames and its contents from damage when exposed to vibrations and shocks such as those in a seismic event.

  • Minimum: 0.
  • Maximum: 1 (for a two-frame system).
  • Corequisites: A Fr Radiator (#4029 and Non-raised floor support (#7998).
  • Compatibility Conflicts: Mutually exclusive with features 8003 and 8004.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
(#9896) On/Off CoD Authorization

This feature is ordered to enable the ordering of On/Off Capacity on Demand (On/Off CoD) through Resource Link.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: On-Line Capacity on Demand (#9900).
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: Not applicable.
  • Limitations: None.
  • Field Installable: Yes.
(#9898) Permanent Upgrade authorization

This feature is ordered to enable the ordering of Licensed Internal Code Configuration Control (LICCC) enabled, permanent capacity upgrades through Resource Link.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: On-Line Capacity on Demand (#9900).
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: Not applicable.
  • Limitations: None.
  • Field Installable: Yes.
(#9900) On-Line Capacity on Demand (CoD) Buying

This feature is ordered to enable purchasing either permanent capacity upgrades or temporary capacity upgrades through Resource Link.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: Not applicable.
  • Limitations: None.
  • Field Installable: Yes.
(#9910) CBU Authorization

This feature enables the purchase of Capacity back up (CBU). This feature is generated when Capacity back up (#6818) is ordered, or it can be ordered by itself. This feature along with On Line Capacity on Demand (#9900) is required to order CBU through Resource Link.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: Capacity back up (#6818).
  • Compatibility Conflicts: None known.
  • Field Installable: Yes.
(#9912) CPE Authorization

This feature is ordered to enable the purchase of Capacity for Planned Event (CPE). This feature is generated when Capacity for Planned Event (#6833) is ordered. This feature along with On Line Capacity on Demand (#9900) is required to order CPE through Resource Link.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: Capacity for Planned Event (#6833).
  • Compatibility Conflicts: None known.
  • Customer Setup: Not applicable.
  • Limitations: None.
  • Field Installable: Yes.
(#9917) 1 MSU-day

Pricing feature used to facilitate the billing of On/Off Capacity on Demand (On/Off CoD) temporary Central Processor (CP) resource tokens purchased through Resource Link. Million Service Unit (MSU)

  • Minimum: 0.
  • Maximum: 99.
  • Prerequisites: On-Line Capacity on Demand Buying (#9900).
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: Not applicable.
  • Limitations: None.
  • Field Installable: Yes.
(#9918) 100 MSU-days

Pricing feature used to facilitate the billing of On/Off Capacity on Demand (On/Off CoD) temporary CP resource tokens purchased through Resource Link.

  • Minimum: 0.
  • Maximum: 99.
  • Prerequisites: On-Line Capacity on Demand Buying (#9900).
  • Corequisites: 1 MSU-day (#9917).
  • Compatibility Conflicts: None known.
  • Customer Setup: Not applicable.
  • Limitations: None.
  • Field Installable: Yes.
(#9919) 10,000 MSU-days

Pricing feature used to facilitate the billing of On/Off Capacity on Demand (On/Off CoD) temporary CP resource tokens purchased through Resource Link.

  • Minimum: 0.
  • Maximum: 250.
  • Prerequisites: On-Line Capacity on Demand Buying (#9900).
  • Corequisites: 1 MSU-day (#9917), 100 MSU-days (#9918).
  • Compatibility Conflicts: None known.
  • Customer Setup: Not applicable.
  • Limitations: None.
  • Field Installable: Yes.
(#9920) 1 IFL-day

Pricing feature used to facilitate the billing of On/Off Capacity on Demand (On/Off CoD) temporary Integrated Facility for Linux (IFL) resource tokens purchased through Resource Link.

  • Minimum: 0.
  • Maximum: 99.
  • Prerequisites: On-Line Capacity on Demand Buying (#9900).
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: Not applicable.
  • Limitations: None.
  • Field Installable: Yes.
(#9921) 100 IFL-days

Pricing feature used to facilitate the billing of On/Off Capacity on Demand (On/Off CoD) temporary IFL resource tokens purchased through Resource Link.

  • Minimum: 0
  • Maximum: 250.
  • Prerequisites: On-Line Capacity on Demand Buying (#9900).
  • Corequisites: 1 IFL-day (#9920).
  • Compatibility Conflicts: None known.
  • Customer Setup: Not applicable.
  • Limitations: None.
  • Field Installable: Yes.
(#9922) 1 ICF-day

Pricing feature used to facilitate the billing of On/Off Capacity on Demand (On/Off CoD) temporary Internal Coupling Facility (ICF) resource tokens purchased through Resource Link.

  • Minimum: 0.
  • Maximum: 99.
  • Prerequisites: On-Line Capacity on Demand Buying (#9900).
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: Not applicable.
  • Limitations: None.
  • Field Installable: Yes.
(#9923) 100 ICF-days

Pricing feature used to facilitate the billing of On/Off Capacity on Demand (On/Off CoD) temporary ICF resource tokens purchased through Resource Link.

  • Minimum: 0.
  • Maximum: 250.
  • Prerequisites: On-Line Capacity on Demand Buying (#9900).
  • Corequisites: 1 ICF-day (#9921).
  • Compatibility Conflicts: None known.
  • Customer Setup: NA.
  • Limitations: None.
  • Field Installable: Yes.
(#9924) 1 zIIP-day

Pricing feature used to facilitate the billing of On/Off Capacity on Demand (On/Off CoD) temporary IBM z Integrated Information Processor (zIIP) resource tokens purchased through Resource Link.

  • Minimum: 0.
  • Maximum: 99.
  • Prerequisites: On-Line Capacity on Demand Buying (#9900).
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: Not applicable.
  • Limitations: None.
  • Field Installable: Yes.
(#9925) 100 zIIP-days

Pricing feature used to facilitate the billing of On/Off Capacity on Demand (On/Off CoD) temporary zIIP resource tokens purchased through Resource Link.

  • Minimum: 0.
  • Maximum: 250.
  • Prerequisites: On-Line Capacity on Demand Buying (#9900).
  • Corequisites: 1 zIIP-day (#9924).
  • Compatibility Conflicts: None known.
  • Customer Setup: Not applicable.
  • Limitations: None.
  • Field Installable: Yes.
(#9928) 1 SAP-day

Pricing feature used to facilitate the billing of On/Off Capacity on Demand (On/Off CoD) temporary System Assist Processor (SAP) resource tokens purchased through Resource Link.

  • Minimum: 0.
  • Maximum: 99.
  • Prerequisites: On-Line Capacity on Demand Buying (#9900).
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: Not applicable.
  • Limitations: None.
  • Field Installable: Yes.
(#9929) 100 SAP-days

Pricing feature used to facilitate the billing of On/Off Capacity on Demand (On/Off CoD) temporary SAP resource tokens purchased through Resource Link.

  • Minimum: 0.
  • Maximum: 250.
  • Prerequisites: On-Line Capacity on Demand Buying (#9900).
  • Corequisites: 1 SAP-day (#9928).
  • Compatibility Conflicts: None known.
  • Customer Setup: Not applicable.
  • Limitations: None.
  • Field Installable: Yes.
(#9970) Weight distribution kit

The weight distribution plate is designed to distribute the weight of a frame over two floor panels in a raised-floor installation and to eliminate a highly concentrated load on a single floor panel.

Certain configuration racks can weigh up to 2450 pounds per frame. The concentrated load on a caster or a leveling foot can be half of the total frame weight. For a multiple-system installation, it is possible that one floor panel could have two casters from two adjacent systems on it, and potentially induce a highly concentrated load onto a single floor panel.

Customers are responsible for consulting with the floor tile manufacturer to determine the load rating of the floor tile and the pedestal structure supporting the floor tiles.

Depending on the type of raised floors and the floor panels, additional panel supports (pedestals) may be required to restore or improve the structural integrity of the panel.

Note: Cable cutouts on a floor panel will significantly reduce the floor tile load rating.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: Mutually exclusive with # 7998.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
  • Cable Order: None.
(#9975) Height reduction for shipping

This feature is required if it is necessary to reduce the shipping height of the IBM z14. This feature should be selected only when it has been deemed necessary for delivery clearance purposes. It should be ordered only IF ABSOLUTELY essential. This feature elongates the install time and increases the risk of cabling errors during the install activity.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: To ship the return packaging and instructions, one or both feature codes Height reduction for shipping (#9975), Frame height reduction for return (#9976), must be selected.
  • Compatibility Conflicts: None known.
(#9976) Frame height reduction for return

This is for conversions from a zEC12 (2827) or z13 (2964) to a z14 (3906) only. The frame height reduction provides the tools and instructions to reduce the height of a zEC12 or a z13 when returned to IBM on an upgrade to a z14 from a zEC12 or z13.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: To ship the return packaging and instructions, one or both feature codes Height reduction for shipping (#9975), Frame height reduction for return (#9976), must be selected.
  • Compatibility Conflicts: None known.

Back to topBack to top
 
Accessories

Not applicable.

Customer replacement parts

Not applicable.
Back to topBack to top
 

Supplies

Not applicable.

Supplemental media

Not applicable.

Trademarks

(R), (TM), * Trademark or registered trademark of International Business Machines Corporation.

** Company, product, or service name may be a trademark or service mark of others.

UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company Limited.
 © IBM Corporation 2018.
Back to topBack to top

Contact IBM

Feedback