Family 3931+01 IBM z16(tm)

IBM United States Sales Manual
Revised: May 17, 2022


Table of contents
Product life cycle datesProduct life cycle datesTechnical descriptionTechnical description
AbstractAbstractPublicationsPublications
HighlightsHighlightsFeaturesFeatures
DescriptionDescriptionAccessoriesAccessories
ModelsModelsSuppliesSupplies


Product life cycle dates

Top rule

Type Model Announced Available Marketing Withdrawn Service Discontinued
3931-A01 2022-04-05 2022-05-31 - -


Back to topBack to top

Abstract

Top rule

Businesses across the world in every industry are investing in digital transformation with the rate and pace increasing over the past several years.(3, 4) IBM z16 is built for hybrid cloud and can help expedite your transformation with new on-chip AI acceleration to enable decision velocity, quantum-safe technologies to designed to help protect your business now and into the future, a flexible infrastructure to meet the resiliency and compliance demands of a constantly changing environment, and with capabilities to accelerate modernization and delivery of additional services.

Predict and automate with accelerated AI

An approach where data gravity and transaction gravity intersect, that co-locates data, transactional systems, and AI inferencing, can deliver insights at speed and scale to enable decision velocity. Decision velocity means delivering insights faster to make decisions to help identify new business opportunities, improve customer experience, and reduce operational risk.

  • IBM z16's on-chip Integrated Accelerator for AI is designed for high-speed, real-time inferencing at scale. The on-chip AI acceleration is designed to add more than 6 TFLOPS of processing power shared by all cores on the chip. This centralized AI design is intended to provide extremely high performance and consistent low- latency inferencing for processing a mix of transactional and AI workloads at speed and scale. Now complex neural network inferencing that leverages real-time data can be executed and deliver insights within high-throughput enterprise workloads in real time while still meeting stringent SLAs.
  • A robust ecosystem of frameworks and open source tools combined with the new IBM Deep Learning Compiler, which generates inferencing programs that are highly optimized for the IBM Z architecture and the Integrated Accelerator for AI, help enable rapid development and deployment of deep learning and machine learning models on IBM Z to accelerate time to market.

Secure with a cyber resilient system

Along with the opportunity created by quantum computing comes the threat to today's public key cryptography. Businesses must start now to prepare for the time when a quantum computer can break today's cryptography. In fact, today's data is at risk for future exposure through "harvest now, decrypt later" attacks.

  • IBM z16 is the industry-first quantum-safe system(2), protected by quantum-safe technology across multiple layers of firmware. Quantum-safe secure boot technology helps protect IBM z16 firmware from quantum attacks through a built-in dual signature scheme with no configuration changes required for enablement.(2)
  • With the new Crypto Express8S (CEX8S), IBM z16 helps deliver quantum-safe APIs that will position businesses to begin using quantum-safe cryptography along with classical cryptography as they begin modernizing existing applications and building new applications.
  • Discovering where and what kind of cryptography is being used is a key first step along the journey to quantum-safety. IBM z16 provides new instrumentation that can be used to track cryptographic instruction execution in the CP Assist for Cryptographic Functions (CPACF). Additionally, the IBM Application Discovery and Delivery Intelligence (ADDI) software product has been enhanced with new crypto discovery capabilities.

To move their enterprises forward in a world that is constantly changing, businesses require an infrastructure that is flexible, secure, and resilient. The risk and potential disruption from extreme weather events, cyberattacks, and more continues to increase. An ever-changing and complex regulatory environment is also driving up the cost to maintain and keep up with regulations.

  • IBM z16 enhancements in resiliency include a new capability called IBM Z Flexible Capacity for Cyber Resiliency. With Flexible Capacity for Cyber Resiliency, you can remotely shift capacity and production workloads between IBM z16 systems at different sites on demand and stay at the alternate site for up to one year. This capability can help demonstrate compliance with regulations that require organizations to be able to dynamically shift production to an alternate site and remain there for an extended period of time. This capability is also designed to help you proactively avoid disruptions from unplanned events. For example, it enables you to move production workload to avoid disruptions from an impending hurricane, flood, or wildfire, as well from planned scenarios such as site facility maintenance.
  • New System Recovery Boost enhancements are also available with IBM z16. The enhancements can provide boosted processor capacity and parallelism for specific events. Client-selected middleware starts and restarts may be boosted to expedite recovery for middleware regions and restore steady-state operations as soon as possible. SVC dump processing and HyperSwap configuration load and reload may be boosted to minimize the impact to running workloads.
  • Parallel Sysplex enhancements include improved Integrated Coupling Adapter Short Reach (ICA SR) performance and Coupling Facility (CF) image scalability, technology and protocol upgrades for coupling links, simplified Dynamic CF Dispatching (DYNDISP) support, and resiliency enhancements for CF cache and lock structures.
  • The IBM Z Security and Compliance Center software product is designed to help simplify and streamline compliance tasks. This solution will help provide a centralized, interactive dashboard for a consolidated view of compliance posture and system-generated evidence in near real time. You can now check the regulatory posture of your systems on demand and more easily identify drift so that it can be remedied quickly.

Modernize for hybrid cloud

IBM z16 delivers technology innovation in AI, security, and resiliency on a flexible infrastructure designed for mission-critical workloads in a hybrid cloud environment. IBM z16 continues to deliver new and improved cloud capabilities on the platform. IBM z16 provides the foundation for application modernization and hybrid cloud velocity by delivering leading hybrid cloud infrastructure to support the optimization of existing mission-critical applications and data. IBM z16 and the accompanying IBM Z and cloud software, which is developed to support a cloud-native experience, delivers a broad set of open and industry-standard tools, including an agile DevOps methodology to accelerate modernization. These capabilities deliver speed to market and agility for both development and operational teams as IBM z16 integrates as a critical component of hybrid cloud.

Businesses can accelerate modernization and delivery of new services by leveraging these key software offerings along with IBM z16:

  • IBM Z and Cloud Modernization Stack to help empower developers to modernize and integrate z/OS applications with services across the hybrid cloud. This solution provides a flexible and integrated platform to support z/OS-based cloud-native development, application, and data modernization and infrastructure automation.
  • Red Hat OpenShift and IBM Cloud Paks running on IBM z16 infrastructure provide the combination of infrastructure, hybrid cloud container platform, and middleware to modernize existing applications and develop cloud-native applications that integrate, extend, and supply data and workloads from IBM z16 across the hybrid cloud with Red Hat OpenShift.

Note: (2) IBM z16 with the Crypto Express8S card offers quantum-safe APIs that provide access to quantum-safe algorithms, which have been selected as finalists during the PQC standardization process conducted by NIST Information Technology Laboratory. Quantum-safe cryptography refers to efforts to identify algorithms that are resistant to attacks by both classical and quantum computers, to keep information assets secure even after a large-scale quantum computer has been built. Source: ETSI Quantum-Safe Cryptography (QSC). These algorithms are used to help ensure the integrity of a number of the firmware and boot processes. IBM z16 is the industry-first system protected by quantum- safe technology across multiple layers of firmware.)
Note: (3) ("COVID-19 and the future of business," IBM Institute for Business Value, September 2020, https://www.ibm.com/thought-leadership/institute-business-value/covid- 19.)
Note: (4) "Forrester Analytics Business Technographics Infrastructure Survey," Forrester.com, 2020, https://www.forrester.com/Business+Technographics+Infrastructure+Surve y+2020/-/E-sus6031?objectid=SUS6031.)

Model abstract 3931-A01

IBM z16*, machine type 3931, provides a scalable, highly available platform that delivers differentiated value to help enable business growth, reduce cost, and protect existing investments.

The IBM z16 platform provides the hardware infrastructure, in a balanced system design, with quantum-safe cryptography and the encryption of data in flight between IBM z16 and IBM DS8900F designed for secure fiber channel endpoint encryption.

IBM z16 provides the flexible infrastructure needed to meet the demands of a digital business. IBM z16 continues to use the extendable system using 19" packaging. The IBM z16 system is 42u in height and is available in one to four frames depending on capacity. It is available in 2 robust power systems including Intelligent PDUs (iPDUs) and Bulk Power Assemblies (BPA). Note: Internal Battery Features are no longer offered.

The IBM Telum processor using 7nm technology runs at 5.2GHz processor frequency. The new processor is supported by a Dual Chip Module driving an integrated Nest and Cache architecture, and new integrated AI Accelerators for high speed inferencing in addition to the cryptography, compression, and sort accelerators. IBM z16 offers 85 partitions, and up to 200 cores to configure (versus 190 on IBM z15).

IBM z16 offers 10 TB RAIM memory per CPC drawer for up to 40 TB per machine all supported by physical memory encryption, IBM Virtual Flash Memory (VFM), zHyperLink Express 1.1, enhanced computing for TKE, Integrated Coupling Adapter Short Reach (ICA SR 1.1), Coupling Express Long Reach (Coupling Express2 LR), and Crypto Express8S hardware security module(HSM) which provides quantum-safe public key and encryption algorithm support.



Back to topBack to top

Highlights

Top rule

Introducing the innovative IBM z16 multiframe system

The IBM Z platform is recognized for its security , resiliency , performance, and scale--relied upon by businesses around the globe for mission-critical workloads and as an essential element of their hybrid cloud infrastructure.(1) IBM z16, the first IBM Z system built with the IBM Telum Processor, extends the platform's capabilities and adds new value with innovative technologies that businesses require as they digitally transform their enterprises. IBM z16 is designed to help businesses:

  • Create value in every customer interaction and optimize decision-making with a new on-chip AI accelerator designed to deliver the speed and scale required to infuse AI inferencing into enterprise workloads while maintaining service level agreements (SLAs)
  • Act now to protect today's data against current and future threats with the industry's first quantum-safe system,(2)new quantum-safe cryptography application programming interfaces (APIs), and crypto discovery tools.
  • Enhance resiliency with flexible capacity to dynamically shift system resources across locations to proactively avoid disruptions
  • Modernize and integrate applications and data in a hybrid cloud environment with a consistent hybrid cloud experience and flexible deployment options to innovate with increased speed and agility
  • Reduce cost and keep up with new and changing regulations with a new compliance solution that helps simplify and streamline compliance tasks

Note: (1) ITIC 2021 Global Server Hardware Server OS Reliability Report, June/July 2021
Note: (2) IBM z16 with the Crypto Express8S card offers quantum-safe APIs that provide access to quantum-safe algorithms, which have been selected as finalists during the PQC standardization process conducted by NIST Information Technology Laboratory. Quantum-safe cryptography refers to efforts to identify algorithms that are resistant to attacks by both classical and quantum computers, to keep information assets secure even after a large-scale quantum computer has been built. Source: ETSI Quantum-Safe Cryptography (QSC). These algorithms are used to help ensure the integrity of a number of the firmware and boot processes. IBM z16 is the industry-first system protected by quantum- safe technology across multiple layers of firmware.

Back to topBack to top

Description

Top rule

This member of the IBM Z family, IBM z16* will fit seamlessly in your data center with its industry-standard sizing, power, and networking. The system features the IBM Telum Processor with its dedicated on-chip accelerator for AI inference to enable real-time AI embedded directly in transactional workloads, as well as improvements for performance, security, and availability. The system is designed to enable you to flexibly scale up to four frames in a single system and integrate additional hardware appliances into an industry-standard form factor. Clients can easily consolidate down to fewer frames or scale-up for growth.

The IBM z16 delivers innovation and benefits in several key areas

Core system

  • IBM z16 has a maximum of 200 client-configurable cores, which is an increase of 10 over IBM z15. IBM z16 single processor capacity is designed to enable equal n-way at common client configurations, approximately 11% greater than on IBM z15 with some variation based on workload and configuration.(5)
  • The largest IBM z16 is expected to provide approximately 17% more total system capacity as compared to the largest IBM z15 with some variation based on workload and configuration. Within each single drawer, IBM z16 provides 25% greater capacity than IBM z15, for standard models and 40% greater capacity on the max config model, enabling efficient scaling of partitions.(5)
  • IBM z16 has a completely redesigned cache subsystem, consisting of semiprivate 32 MB Level-2 (L2) caches per core that are working in concert to provide up to 256 MB virtual Level-3 (L3) cache per chip and up to 2 GB virtual Level-4 (L4) cache per drawer. The result is that virtual L3 and L4 caches provide 1.5 times the cache capacity per core compared to IBM z15.
  • IBM z16 supports up to 10 TB of main memory per drawer and 40 TB per system based on a newly designed memory buffer chip that provides up to DDR4-3200 memory speed, depending on memory size, delivering 50% more memory bandwidth per drawer than IBM z15. This is designed to improve overall workload performance, particularly for data-intensive analytics and AI applications. The memory interface uses transparent memory encryption technology to protect all data leaving the processor chips before it's stored in the memory DIMMs.
  • IBM z16 has 20 new instructions to help improve COBOL and AI applications, including instructions to leverage a new AI accelerator.

Security and cryptography

  • IBM z16 quantum-safe technology is designed to enable you to act now to help future proof your business. IBM z16 leverages quantum- safe technologies to help protect your business-critical infrastructure and data from potential quantum attacks.(2)
  • IBM z16 secure boot technology protects system firmware integrity by using quantum-safe and classical digital signatures to perform a hardware-protected verification of the IML firmware components.(2)
  • The Crypto Express8S (CEX8S) is designed to meet the Federal Information Processing Standards (FIPS) 140-3 at Level 4 for cryptographic modules.
  • IBM's Common Cryptographic Architecture release 8.0 (CCA 8.0) is designed to be certified to meet the hardware security module (HSM) requirements from the Payment Card Industry Security Standards Council (PCI-SSC).
  • The CEX8S with Enterprise PKCS #11 (EP11) firmware offers enhancements that are designed to increase performance significantly in the areas of random number generation as well as message digest calculation.
  • The Trusted Key Entry (TKE) 10.0 level of the licensed internal code (LIC) enables you to manage the CEX8S using the TKE.

Networking and I/O

  • OSA-Express7S 1.2 GbE, 10 GbE, 1000Base-T, and 25 GbE.
  • RoCE Express3 10 GbE and 25 GbE LR and SR, in support of the SMC-R and SMC-Rv2 protocols, as well as use by Linux on IBM Z for all networking communications protocols.
  • FICON Express32S (#0461 and #0462) to help absorb large application and transaction spikes driven by large unpredictable AI and hybrid cloud workloads. Also a key component of the IBM Fibre Channel Endpoint Security solution.
  • Coupling Express2 LR, which provides technology upgrades and currency, along with improved link traffic management protocols compared to previous generations of long-reach coupling links.
  • A new level of coupling facility support, CFLEVEL 25, which provides a variety of enhancements for improved coupling facility performance, scalability, and resiliency. For details, see the following sections in this document:
    • IBM z16 Coupling and Parallel Sysplex enhancements and CFLEVEL 25 support
    • CF cache and lock structure resiliency improvements
    • CF cache structure object residency time monitoring and metrics
  • Crypto Express8S (CEX8S), which is available in 1 HSM (#0909) and 2 HSM (#0908) versions.

Systems management and infrastructure

  • IBM Hardware Management Console (HMC) 2.16.0 offers simplification updates designed to improve workspace and manage system time.
  • The IBM Z Hardware Management Appliance (#0129) provides redundant HMCs and Support Elements (SEs) that run on redundant physical servers inside the Central Processor Complex (CPC) frame. The HMCs and SEs in an HMA have the same physical network redundancy as the standalone HMCs and SEs.
  • Dynamic Partition manager (DPM) continues to enhance its set of capabilities. With IBM z16 DPM is designed to provide a seamless experience to configure low latency SMC-Dv2 network links between two or more logical partitions running on the same physical server, all through a single point of control. This enables system administrators and system programmers to accomplish time-consuming and potentially error-prone operations with an intuitive and guided user experience.

Performance

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 z16, 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, the LSPR also contains performance relationships for z/VM and Linux operating environments.

Single processor capacity of IBM z16 (3931) for equal n-way at common client configurations is approximately 11% greater than on IBM z15 (8561) with some variation based on workload and configuration.(5)The largest IBM z16 (3931-7K0) is expected to provide approximately 17% more capacity than the largest IBM z15 (8561-7J0) with some variation based on workload and configuration.(5)

The IFL and zIIP processors on IBM z16 also provide an optional IBM z16 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.(1)

The LSPR contains the Internal Throughput Rate (ITTR) ratios for IBM z16 and the previous-generation IBM Z processor families based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput that a user may experience will vary depending on 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 LSPR available at the Resource Link website.

IBM Z Integrated Accelerator for AI

IBM Z Integrated Accelerator for AI is designed to provide machine learning acceleration with high throughput and low latency. IBM Telum has a centralized chip-based AI accelerator designed to support real time computing at scale and provides a high data bandwidth interface to the cache and memory hierarchy optimized to deliver high inference throughput. This centralized AI design is intended to provide extremely high performance and consistent low latency inferencing for processing transactional workloads leveraging AI at speed and scale. IBM Z Integrated Accelerator for AI is designed to meet demanding response time requirements of real-time workloads, for instance in the banking and healthcare industry. For example, clients can benefit from the AI acceleration enabled by the IBM Z Integrated Accelerator for AI to detect fraud in real time to reduce revenue loss due to fraud.

Implemented as an architected memory-to-memory instruction accelerating the most heavily used high-level AI functions like matrix multiplication or convolution, the IBM Z Integrated Accelerator for AI has direct access to the application data resulting in reduced data movement and improved performance. The IBM Z Integrated Accelerator for AI is targeted to accelerate deep learning AI models, like recurrent neural networks (RNN) and convolutional neural networks (CNN), at a higher throughput rate and low latency. Enterprises that use IBM CICS Transaction Server for z/OS (CICS TS), IBM Information Management System (IMS) Transaction Manager, IBM z/TPF, or IBM WebSphere Application Server for z/OS can exploit the IBM Z Integrated Accelerator for AI when using deep learning AI models, by using one of the existing options for invoking AI models in their applications.

There is an emerging industry need for organizations to work with existing infrastructure. Data scientists want to simplify operationalizing their existing AI investments when integrating them with IBM Z. IBM z16 supports popular AI frameworks and tooling such as TensorFlow, Spark, SnapML, Pytorch, Open Neural Network Exchange (ONNX), and the IBM Deep Learning Compiler (DLC), with optimizations that leverage the IBM Z Architecture including the AI Accelerator. With technologies and tooling such as ONNX and Watson Machine Learning for z/OS, data scientists can develop and train their models with familiar tools and common platforms such as x86, Power, IBM Z and LinuxONE. They can then port their data science assets and deploy them on IBM Z seamlessly to deliver more consistent, repeatable production qualities of service. By allowing clients to bring their own models for deployment on IBM Z, organizations can leverage their existing investments in people, process and infrastructure. By deploying AI on IBM Z, you can benefit from the quality of service such as scale, resiliency, and security to get the most out of your infrastructure investment.

IBM Deep Learning Compiler (DLC) enables deep learning models to be deployed on IBM Z, exploiting the IBM Integrated Accelerator for AI. The DLC is included as part of Watson Machine Learning for z/OS with enhanced capabilities and model management. It is also available in a community version.

IBM Z Deep Neural Network library (zDNN) is a software library that provides high-level C APIs, which enable simplified exploitation of the IBM Z Integrated Accelerator for AI by AI frameworks and libraries. Additionally, it has been made available through open source channels. The IBM zDNN library provides APIs for the deep learning and machine learning primitives that are accelerated by the IBM Z Integrated Accelerator for AI. AI framework developers, AI compiler developers, as well as runtime providers, can leverage the zDNN accelerated primitive APIs to drive the exploitation of the IBM Z Integrated Accelerator for AI through the new Neural Network Processor Assist (NNPA) facility instruction. The zDNN library enables high- level language exploitation of the optimized NNPA implementation for matrix multiplication, convolution, activation functions, and many other standard DNN primitives. The zDNN library is available with z/OS and for Linux on IBM Z distributions.

IBM Db2 13 for z/OS offers new capabilities to help increase business resiliency, reduce downtime, and enhance application performance and stability--ultimately reducing cost. It provides an innovative database-integrated approach to developing and deploying AI insights within applications. The IBM Db2 SQL Data Insights feature can readily integrate AI within any application to identify and monetize hidden insights within Db2 for z/OS data.

IBM Db2 AI for z/OS 1.5 helps improve database operational performance, security, resource consumption, and connectivity to deliver agility, automation, and self-management through infused AI.

IBM Z Flexible Capacity for Cyber Resiliency

Flexible Capacity for Cyber Resiliency is a new Capacity on Demand (CoD) offering available on IBM z16 machines that allows processing capacity flexibility between an organization's primary site and alternate data centers.

Flexible Capacity for Cyber Resiliency is designed to provide increased flexibility and control to organizations that want to shift production capacity between participating IBM z16 servers at different sites. The capacity of any engine type can be shifted up to 12 times a year and stay at the target machine for up to 12 months after the flexible capacity record activation on the target machine. Capacity shifts can be done under full client control without IBM intervention and can be fully automated using IBM GDPS automation tools. Flexible Capacity for Cyber Resiliency can be combined with other IBM On-Demand offerings.

Flexible Capacity for Cyber Resiliency supports a broad set of use case scenarios:

  • Proactive outage avoidance
    Flexible Capacity for Cyber Resiliency can help protect critical business services from disruption from unplanned events. The ability to shift production capacity and workloads to an alternate site at any time and remain there for an extended period of time can help businesses proactively avoid outages from events such as extreme weather events, rolling power outages, and more.
  • Compliance
    Regulators around the globe are introducing more stringent policies in relation to business continuity and disaster recovery (DR), requiring more comprehensive and extended testing. Many clients have been mandated to switch over full production workloads and operate for a period of 30 days up to 6 months out of their secondary data centers. Flexible Capacity for Cyber Resiliency is designed to help to improve an organization's compliance posture to meet existing and evolving regulatory requirements that require rapid restoration of production workloads.
  • DR and DR testing
    Flexible Capacity for Cyber Resiliency enables you to transfer the capacity needed at the DR site to continue running production workloads. You can automate and test recovery procedures for unplanned outages, including cyberattacks, to provide near-continuous availability and DR.
  • Facility maintenance
    You can run production workloads from an alternate site with all the capacity needed to perform maintenance at the source site.

To accommodate the capacity shift, a new temporary capacity record called a Flexible Capacity Record is introduced. The record will be installed on both the IBM z16 source and the IBM z16 target systems.

The source and target IBM z16 systems must be installed in different locations using z/OS 2.2 or above. The capacity is shifted without automation and then optionally, GDPS 4.4 is enabled to provide automation. Necessary resiliency technology must be enabled, such as system-managed CF structure duplexing, sysplex failure management, and Capacity Provisioning Manager. Other configurations may provide different availability characteristics. Clients may optionally use other third-party tools for automation purposes.

Ordering

Flexible Capacity for Cyber Resiliency can be ordered through e-config. The offering requires an order placed against each serial number (SN) involved in capacity transfer, or one record per SN.

  • Feature codes (FCs) are introduced: Flexible Capacity Authorization (#9933), Flexible Capacity Record (#0376), and billing feature codes (#0317 through #0322, and #0378 through #0386).
  • Flexible Capacity Records are configured using the ODC tab in e-config.
  • The configuration panel displays quantity boxes for IFLs, ICFs, zIIPs, term years (one through five), and a selection list of supported CP capacity software model targets.
  • All parameter fields will be replenishable through an MES to the record.
  • The record is capable of being delivered electronically if the entire MES qualifies.
  • Record validation can only be performed for SNs when placing an order, not across SNs participating in capacity transfer.
  • Flexible Capacity Records will carry forward to future machine type upgrades into IBM z16.

e-config will calculate and auto-add billing FCs for any delta capacity configured to support the capacity transfer. Flexible Capacity for Cyber Resiliency is a prepaid offering, available as a yearly subscription or perpetual license.

Installation and setup

The Flexible Capacity Record is installed and set up on each participating IBM z16 system.

  • On the IBM z16 source system, the permanent capacity is unassigned to the base level.
  • The Flexible Capacity Record is installed and activated on the IBM z16 source system to restore capacity back to the purchased level.
  • On the IBM z16 target system, the new Flexible Capacity Record enables clients to bring the capacity up to the level of the production system when activated. The Flexible Capacity Record remains inactive until capacity is shifted from the base system to the target system.
  • After deactivating the Flexible Capacity Record on the base system, the capacity active through Flexible Capacity Transfer records on the target system is not permitted to exceed the capacity active on the base system before the shift.
  • If GDPS automation is being used, it must be set up with the correct LIC records to add capacity in the target system and remove capacity in the base system site.

System Recovery Boost enhancements

System Recovery Boost for IBM z15 provided boosted capacity and parallelism to accelerate image-level recovery, such as shutdown and startup, and enabled accelerated processing of workload backlogs that occurred as a result of those image-level events following a re-IPL. System Recovery Boost also offered short-term recovery process boosts to mitigate certain Parallel Sysplex recovery impacts and restore steady-state sysplex operation as quickly as possible, and to provide workload catch-up following the recovery. Participating images were eligible to receive an IPL boost of up to 60 minutes, an image shutdown boost of up to 30 minutes, and a pool of 30 minutes per image per day of recovery process boost time. System Recovery Boost provided additional image-level processing capacity and parallelism for the boosting images by making use of two underlying IBM z15 technologies: Speed Boost, enabling subcapacity GP processors to run at full-capacity speed, and zIIP boost, making general-purpose work eligible to run on zIIP processors.

On IBM z15, recovery process boosts could be provided for the following specific Parallel Sysplex recovery events:

  • Sysplex partitioning boosts the planned or unplanned removal of a system from the sysplex
  • CF structure recovery boosts CF structure recovery processing, including CF structure rebuild and duplexing activities
  • CF data sharing member recovery boosts recovery following the termination of a CF locking data-sharing member with locks held
  • HyperSwap recovery boosts the HyperSwap recovery process to recover from the failure of a storage subsystem.

Now, with IBM z16, IBM extends the System Recovery Boost solution once more with additional recovery process boost use cases to provide value for a new set of recovery and diagnostic events, utilizing the same underlying boost technologies used previously. These new use cases are only available when running on IBM z16, or higher, systems.

These new solution enhancements provide boosted processor capacity and parallelism for the following specific events:

  • Client-selected middleware starts and restarts boosts z/OS systems that are performing startup and restart for client- selected started-task middleware regions. By default, no middleware regions are boosted, but clients may configure this function for use by specifying which started-task middleware regions they want to be boost-eligible using WLM Service Definition Classification Rules. The recovery process boost is designed to expedite recovery for the middleware regions and restores steady-state operations as quickly as possible, with additional capacity for workload catch-up once the middleware region is started.
  • SVC dump processing boosts z/OS systems that are performing diagnostic data capture through an SVC dump that is estimated to be over a certain size threshold. By default, no dumps will be boosted, but clients may configure this function for use by using the CHNGDUMP command to set a dump size threshold over which SVC dumps will be boosted. The recovery process boost is designed to minimize the impact of the SVC dump processing on your running workloads and provides additional capacity for workload catch-up following the completion of the SVC dump capture process.
  • HyperSwap configuration load and reload boosts z/OS systems that are participating in a load or reload of a HyperSwap configuration policy. The recovery process boost is also designed to minimize the impact of the HyperSwap configuration change processing on your running workloads and provides additional capacity for workload catch-up following the completion of the configuration change process.

Note that these IBM z16 recovery process boost use cases share the same recovery process boost time pool of 30 minutes per image per day with the Parallel Sysplex recovery use cases that were previously introduced on IBM z15. Furthermore, as was true previously, the use of System Recovery Boost Upgrade temporary capacity record activations for recovery process boosts is not supported. The System Recovery Boost Upgrade temporary capacity is for use only in conjunction with image-level IPL and shutdown boosts.

System reliability, availability, and serviceability

The IBM z16 platform builds upon the reliability, availability, and resilience of predecessor IBM Z server platforms. The intrinsic hard failure rate of the IBM Telum processor chip is at least three times lower than the prior-generation IBM z15 and is designed to reduce the number of recovery and service events over the life of the program. IBM internal laboratory tests were performed on pre-release IBM Telum processor chips to measure the intrinsic hard failure rate. Results may vary.

The cache structure is virtualized; the physical level of shared cache is implemented in a very robust SRAM wipe out correction and sparing design that benefits all virtualization levels. The cache allocation is fluid, dynamically changing the cache size and shape as needed, benefitting processor cores, CBU, and On/Off CoD.

The socket count per drawer is reduced with IBM z16, which simplifies structure and reduces the replaceable part count, which in turn simplifies service actions. The processor cores have expanded interleaving to improve resistance to soft error disturbances. Robustness has been improved as a result of simplifying uncorrectable error handling on many arrays. The memory DIMM has power conversion and regulation located on each DIMM, thereby allowing much tighter power tolerances, which improves reliability of the DRAM.

There are two data cables (SMP) between each drawer that enable workload to be routed to just one cable dynamically. As a result, applications can tolerate a cable with defective wires, and it enables a powerful new service function called concurrent cable repair. The cables have built-in shorts and configuration testing that help ensure the cable is properly plugged before you use it. An added benefit of concurrent cable repair is the reduction in the use of concurrent drawer repair.

The service network infrastructure has been refreshed with IBM z16, positioning the infrastructure for the future. The fill and drain tool water drain function has been improved to decrease the time needed to drain a part being replaced. This improvement is designed to also greatly reduce the time needed to drain the machine during the discontinuation process. The IBM z15 lift tool can be used for IBM z16. This reduces storage requirements for clients with servers on both platforms. Remote Code Load, available on IBM z16, reduces the need for IBM and customer service personnel onsite during firmware upgrades.

Quantum-safe protection

As quantum computing and the related rapidly developing ecosystem matures, the National Institute of Standards and Technology (NIST), as well as industry and academic institutions, are looking at the risk side of quantum technology. IBM recognizes that with any new technology, there are new threats, and as such, appropriate countermeasures may need to be taken.

Quantum technology can be used for incredible good, but in the hands of an adversary, it has the potential to weaken or break core cryptographic primitives that have previously been used to secure systems and communications. This leaves the foundation for digital security at risk. NIST initiated a process to solicit, evaluate, and standardize quantum-safe public-key cryptographic algorithms to address these issues. Quantum-safe cryptography aims to provide protection against attacks that can be initiated against classical and quantum computers.

IBM is a leader in the development of quantum-safe technology and the products that leverage this critical technology. IBM z16 quantum- safe technology enables you to act now to help future-proof your business.(2)IBM z16 leverages quantum-safe technologies to help protect your business-critical infrastructure and data from potential attacks.(2)

IBM z16 secure boot technology protects system firmware integrity by using quantum-safe and classical digital signatures to perform a hardware-protected verification of the Initial Machine Load (IML) firmware components.(2)This protection is anchored in a hardware-based root of trust for the firmware chain of trust.(2)IBM z16 's quantum- safe technology is designed to provide a double layer of protection by using a dual signature scheme that employs classical and quantum-safe cryptographic algorithms to help ensure the server starts safely and securely by keeping unauthorized firmware (malware) from taking over your server during system startup.(2)

Now is the time to start planning for the replacement of hardware, software, and services that use public-key and weak symmetric key cryptography. In addition to the cryptographic capabilities of IBM z16, tools will be provided that can help you discover where and what cryptography is used in applications to aid in developing a cryptographic inventory for migration and modernization planning. IBM z16 will enable future critical client use cases across many industries with the following capabilities:

  • Quantum-safe key generation
  • Quantum-safe encryption
  • Quantum-safe key encapsulation mechanisms
  • Quantum-safe hybrid key exchange schemes
  • Quantum-safe dual digital signature schemes

IBM Application Discovery and Delivery Intelligence (ADDI) Version 6.1 helps you identify potential cryptographic exposures in your COBOL applications so you can easily identify vulnerable cryptographic calls and protect against harvesting of confidential data.

IBM z16 enables you to begin using quantum-safe cryptography along with classical cryptography as you begin to modernize existing applications and build new applications.(2)IBM z16 with Integrated Cryptographic Service Facility (ICSF), CEX8S, TKE 10.0, and other security features provide you the vehicle to take advantage of these quantum-safe capabilities.

Cryptographic enhancements for CCA and Enterprise PKCS #11 (EP11)

CCA CEX8S enhancements

IBM z16 delivers critical cryptographic capabilities that helps address the ever-changing security requirements across the globe around key management and distribution, data management and compliance, and protecting enterprise data. The new CEX8S is designed to meet the FIPS 140-3 at Level 4 for cryptographic modules. IBM's CCA 8.0 is designed to be certified to meet the HSM requirements from the PCI Security Standards Council (PCI SSC). Its unique design eases migration of applications and keys and expands to add new cryptographic algorithm support. CCA 7.0 through 7.4 also meet the PCI HSM requirements, with each release in process to receive certification as early as possible. CCA 8.0 also includes the enhancements from the release CCA 7.4.

The CEX8S with CCA firmware is designed to further offer enhancements that increase performance for both application workloads and TKE workstation domain group administration. The CEX8S with CCA firmware also has a redesigned queueing model that adds fairness for heterogeneous workloads originating from different domains.

CEX8S with CCA firmware includes complete AES-based financial services processing with complete ISO 4 PIN block format and AES-DUKPT support. This includes the new PIN Verify 2 service, which allows secure comparison of ISO 4 PIN blocks to other PIN blocks inside the HSM. The AES processing updates are useful for payment network participants that are upgrading security to newer AES-based security protocols. Signature scheme support is enhanced with EdDSA (Ed448 and Ed25519) and Elliptic Curve Schnorr Digital Signature Algorithm (EC-SDSA), including the secp256k1 curve. The enhanced Elliptic Curve support is useful for protocols that require certificates or signature support using these curves. Data protection service is enhanced with X9.23 random pad for AES encryption services and format preserving encryption (FPE) support, including FF1, FF2, and FF2.1. The added FPE support is commonly used for communication of sensitive data between payment network participants, where the encrypted data must fit into fields and protocols that check the form and character set of the data. Key management is enhanced with X9 TR-31 support for HMAC keys, a PKCS#11 key export mechanism for CCA keys that allows interoperation with various cloud services, and X9 TR-34 remote key exchange enhancements that allow better interaction with unique devices. CCA firmware is further enhanced with Australian financial services algorithm and protocol support for both issuer and acquirer workloads.

CCA quantum-safe cryptography enhancements

The CEX8S with CCA firmware has added secure key support for quantum-safe cryptography private keys for both signature and key encapsulation method (KEM) use cases. The CCA interface adds support for Cryptographic Suite for Algebraic Lattices (CRYSTALS) Dilithium secure private keys of sizes (6,5) and (8,7) for both round 2 and round 3 versions of CRYSTALS-Dilithium, usable for digital signature generation and verification. The CCA interface also adds support for round 2 of the CRYSTALS Kyber 1024 parameter set, a key encapsulation mechanism (KEM), which can be used to protect 32-byte values. These pieces are also combined with Elliptic-curve Diffie--Hellman (ECDH) support to offer clients a complete quantum-safe cryptography hybrid key exchange scheme, implemented with secure CCA private keys for all involved private keys. This is useful for scenarios where data needs enhanced authentication against future quantum computing attacks on conventional cryptography.

CCA - TDES key block

CEX8S with CCA firmware contains enhancements also delivered for CEX7S after the IBM z15 GA1 on September 23, 2019. This includes the first proprietary TDES key block, also known as a key token, to be independently reviewed and confirmed to be compliant with PCISSC PIN Security key block requirements as updated September 30, 2020.

The TDES key block is backward compatible with existing applications and Cryptographic Key Data Set (CKDS). The new TDES key block is implemented starting with z/OS level 2.4, ICSF HCR77D1, and APAR OA60318. The new TDES key block was available for IBM z15, IBM z14, and IBM z13 beginning July 2021 in the appropriate firmware drivers. The independent review is publicly posted. The new PCI PIN compliant CCA TDES key block is useful and required for applications that use TDES keys and cryptography in PCI PIN audited workflows.

EP11 CEX8S enhancements

CEX8S with Enterprise PKCS #11 (EP11) firmware offers enhancements that increase performance significantly in the areas of random number generation as well as message digest calculation.

It adds support for using the Secure Hash Algorithm 2 (SHA-2) and Secure Hash Algorithm 3 (SHA-3) families in conjunction with the RSA-OAEP encryption scheme, which has also been made available for the CEX7S with EP11 firmware since version 4.7.14.

CEX8S with EP11 firmware also adds general support for EdDSA (Ed25519 and Ed448) and ECDH with Montgomery curves (X25519 and X448), which has also been made available for the CEX7S with EP11 firmware since version 4.7.15.

EP11 quantum-safe cryptography enhancements

CEX8S with EP11 firmware has enhanced support for digital signatures with CRYSTALS Dilithium. Additionally, to the already existing security level 4 from round 2, the following security levels are now supported for generating and verifying quantum-safe signatures: round 2 (8,7), round 3 (6,5), and round 3 (8,7).

It is also the first time that CRYSTALS Kyber for quantum-safe encryption and decryption as well as key encapsulation is supported with security levels 768 and 1024.

TKE 10.0 level of LIC

Important upgrade information: You can upgrade from TKE 9.x to TKE 10.0 with the purchase of a 4770 HSM for the TKE. However, you must update your workstation BIOS prior to the upgrade. To do that, you MUST install TKE 9.2 with the latest patches prior installing the TKE 10.0 firmware.

The TKE 10.0 level of LIC is required if you want to manage the CEX8S using the TKE. In addition, TKE 10.0 uses quantum-safe cryptography when the TKE authenticates CEX8S, derives Transport Keys between the TKE's HSM and the target CEX8S, and during the on-demand HSM dual validation check.

  • TKE 10.0 has a domain group limitation. All the HSMs in a TKE domain group must all contain quantum-safe cryptography support (that is, only include CEX8S), or all the HSMs must not contain quantum-safe cryptography support (that is, the HSM's can't include any CEX8S).
  • TKE 10.0 now supports one-time use MFA authentication on an open host.
  • TKE 10.0 contains Configuration Migration Tasks support to enable you to collect and apply data to and from CEX8S and collect data from a pre-CEX8S HSM and apply it to CEX8S HSMs.
  • TKE 10.0 supports a new default wrapping method for the CEX8S HSM.
  • TKE 10.0 added support for a new AES DUKPT key attribute when using TKE to create AES DKYGENKY parts.

TKE 10.0 added support for the EP11 Outbound Authentication (OA) Signature Policy. The EP11 firmware on a CEX8S HSM enables users to configure what OA signatures are returned on responses from the HSM. The TKE OA Signature Policy controls what configuration options you may select when managing the settings from the TKE.

IBM Z Security and Compliance Center

In regulated industries, compliance is a top priority. But the process to collect evidence of information security controls and demonstrate compliance to auditors is manual and time-consuming.

Enterprise-grade security and resiliency features are architected throughout the IBM Z and Linux on IBM Z stack. The IBM Z Security and Compliance Center helps centralize monitoring of compliance related tacks and provides an interactive view of these tasks and potential severity of control deviations.

The IBM Z Security and Compliance Center is designed to help you streamline tracking and reporting of your internal compliance process as follows:

  • Automate collection and validation of relevant facts from key areas of IBM Z/OS and Linux platforms, tracked over time with a browser based dashboard.
  • Predefined profiles will identify potential deviations through built-in goal validation that help demonstrate to auditors the details around the severity of controls deviations from PCI-DSS and NIST SP800-53.

Enterprises using CICS Transaction Server for z/OS (CICS TS), Db2 for z/OS, MQ, or IBM Information Management System (IMS) will be able to use the IBM Z Security and Compliance Center dashboard to quickly and easily determine the extent to which their IBM Z systems meet internal controls and certain industry standards. CICS TS, Db2 for z/OS, MQ, and IMS runtimes will now provide(*)additional information to z/OS to populate this dashboard.

(* Product update to the latest version may be required.)

For more information about IBM Z Security and Compliance Center, see Software Announcement 222-005.

FICON Express32S

FICON Express32S supports a link data rate of 32 Gbps and autonegotiation to 16 Gbps and 8 Gbps for synergy with current- generation switches, directors, and storage devices. With support for native FICON, High Performance FICON for z Systems (zHPF), and Fibre Channel Protocol (FCP), the IBM z16 server is designed to enable an end-to-end 32 Gbps infrastructure to meet the lower latency and increased bandwidth demands of your applications.

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

Throughput for the zHPF protocol

In laboratory measurements, using the zHPF protocol, a single IBM z16 FICON Express32S port delivers up to 5,400 MB/s for a mix of large data block (32x4KB) read/write operations; a 68% increase over an IBM z15 FICON Express16SA port.

Performance data for the FICON zHPF protocol was measured in a controlled environment on IBM z16 using a zOS I/O driver program to execute zHPF I/O operations on FICON Express32S. The FICON Express32S port operated at a 32Gbps link data rate. The workload consisted of a mix of large (32x4KB) sequential read and write data transfer I/O operations. Results may vary.

In laboratory measurements using the zHPF protocol, both ports on IBM z16 FICON Express32S deliver a total combined throughput of up to 9,000 MB/s for a mix of large data block (32x4KB) read/write operations; a 38% increase over the total throughput of IBM z15 FICON Express16SA.

Performance data for the FICON zHPF protocol was measured in a controlled environment on IBM z16 using a zOS I/O driver program to execute zHPF I/O operations on FICON Express32S. The FICON Express32S port operated at a 32Gbps link data rate. The workload consisted of a mix of large (32x4KB) sequential read and write data transfer I/O operations. Results may vary.

Throughput for the FCP protocol

A FICON Express32S adapter, when defined as CHPID type FCP, conforms to the FCP standard to support attachment of Small Computer Systems Interface (SCSI) devices, to complement the classical storage attachment supported by FICON and zHPF channels.

In laboratory measurements, using the FCP protocol, IBM z16 FICON Express32S delivers up to 600,000 IOPS per port for small data block (4KB) read operations; a 52% increase over IBM z15 FICON Express16SA. Performance results are based on laboratory measurements on IBM z16 using an internal Linux on IBM Z microbenchmark to execute FCP I/O operations on FICON Express32S. The FICON Express32S port operated at a 32Gbps link data rate. The workload consisted of 4KB read-only data transfer I/O operations. Results may vary.
In laboratory measurements, using the FCP protocol, a single IBM z16 FICON Express32S port delivers up to 6,400 MB/s for a mix of large data block (64KB) read/write operations; 2x the throughput of an IBM z15 FICON Express16SA port.
Performance results are based on laboratory measurements done on IBM z16 using an internal Linux on IBM Z microbenchmark to execute FCP I/O operations on a single FICON Express32S port. The FICON Express32S port operated at a 32Gbps link data rate. The workload consisted of an even mix of 64KB read/write data transfer I/O operations. Results may vary.
In laboratory measurements, using the FCP protocol, both ports on IBM z16 FICON Express32S deliver a total combined throughput of up to 9,700 MB/s for a mix of large data block (64KB) read/write operations; a 54% increase over the total throughput of IBM z15 FICON Express16SA. Performance results are based on laboratory measurements done on IBM z16 using an internal Linux on IBM Z microbenchmark to execute FCP I/O operations on both ports available on FICON Express32S. Both FICON Express32S ports operated at a 32Gbps link data rate. The workload consisted of an even mix of 64KB read/write data transfer I/O operations. Results may vary.

The FCP protocol is supported by z/VM, z/VSE, 21(st)Century Software VSE(n), and Linux on IBM Z. See the Software requirements section.

Cleaning discipline for FICON Express32S fiber optic cabling With the introduction of 32 Gbps link data rates, it is even more critical to ensure your fiber optic cabling infrastructure performs as expected. Proper fiber optic inspection, cleaning, and maintenance is required to help ensure that the data gets through. With 32 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 inspection and cleaning procedures in place.

Channel subsystem (CSS) scalability

The IBM z16 server, like the IBM z15 and IBM z14 servers, has support for six logical channel subsystems (LCSSs), which are required to support the 85 LPARs for IBM z16, and four subchannel sets per LCSS.

OSA-Express7S 1.2: an Ethernet technology refresh

The OSA-Express7S 25 Gigabit Ethernet short-range (25 GbE SR) feature was introduced on IBM z14, and with IBM z16 an additional long-range OSA-Express7S 1.2 25 GbE LR feature is being introduced to complete the full family of the OSA-Express7S generation of adapters along with a technology refresh of the entire OSA-Express7S 1.1 generation of adapters: 1000BASE-T Ethernet for copper environments along with 25 GbE SR, 10 Gigabit Ethernet (10 GbE), and Gigabit Ethernet (GbE) for single-mode and multimode fiberoptic environments. The performance characteristics of the new features are comparable to their predecessor OSA-Express7S 1.1 features. They also retain the same form factor and port granularity, which is two ports per feature for the 1000BASE-T Ethernet and Gigabit Ethernet features, and one port per feature for the 10 Gigabit Ethernet and 25 Gigabit Ethernet features.

These members of the OSA-Express7S 1.2 family of features (#0454, #0455, #0456, #0457, #0458, #0459, and #0460) are exclusive to the IBM z16 family.

They are supported by z/OS, z/VM, z/VSE, 21(st)Century Software VSE(n), z/TPF, and Linux on IBM Z. See the Software requirements section for more information.

RoCE Express3: an RDMA/Ethernet technology refresh

The RoCE Express2 25 Gigabit Ethernet short-range (25 GbE SR) feature was introduced on IBM z14, and with IBM z16, an additional long-range RoCE Express3 25 GbE LR feature is being introduced along with a technology refresh of the existing single-mode and multimode fiberoptic 10 GbE and 25 GbE offerings. The performance characteristics of the new features are comparable to their predecessor RoCE Express2 and RoCE Express2.1 features. They retain the same form factor and port granularity, which is two ports per feature for each of the 10 Gigabit Ethernet and 25 Gigabit Ethernet features.

These members of the RoCE Express3 family of features (#0440, #0441, #0452, and #0453) are exclusive to the IBM z16 family.

They are supported by z/OS, z/VM, Linux on IBM Z, and KVM (guest support through passthru or macvtap). For more information, see the Software requirements section.

IBM Z Monitoring Suite

IBM Z Monitoring Suite has been enhanced to support the new IBM z16 hardware with additional metrics and alerts for System Recovery Boost and CEX8S card status and performance. This can help enable users to take advantage of these new features with confidence that observability is provided by IBM monitoring tools.

IBM z16 Coupling and Parallel Sysplex enhancements and CFLEVEL 25 support

IBM z16 coupling hardware and firmware, including Coupling Facility Control Code (CFCC) CFLEVEL25, provides a variety of coupling facility (CF) and coupling link enhancements. New capabilities are provided for improved CF performance and scalability, technology and protocol upgrades for both short-reach and long-reach coupling links, simplified Dynamic CF Dispatching (DYNDISP), improved CF cache and lock structure resiliency, and new CF cache structure object residency time monitoring.

Coupling link short-reach protocol efficiency improvements

IBM z16 short-distance ICA SR coupling link protocols have been redesigned to provide reduced latency and improved CF service times for CF requests using these links. The improved CF service times for CF requests can translate into better Parallel Sysplex coupling efficiency and therefore may reduce software costs for the attached z/OS images in the Parallel Sysplex, as synchronous CF requests directly consume z/OS-image processor resources as they are executed. While the amount of improvement clients will see is highly dependent on various workload and configuration specifics, service times for short-distance CF read requests or lock requests may improve by up to 10%, write requests may improve by up to 25%, and duplexed write requests may improve by up to 25%, compared to CF service times on IBM z15 systems.(6)

Specific enhancements for IBM z16 have improved the short-distance coupling link data transfer protocols for CF requests that write data to the CF, have affinitized coupling link buffers to specific groups of coupling facility processors for more efficient execution, and have moved several performance-critical processes for both primary CF requests and secondary cross-invalidate (XI) and list-notification (LN) signals from the firmware into IBM z16 hardware.

These efficiency improvements are maximized when both ends of the coupling link connection reside on IBM z16 systems. However, some improvements are also realized when connecting an IBM z16 system to an IBM z15, IBM z14, or IBM z14 ZR1 generation system.

Short-reach coupling link adapters used on IBM z16 are compatible with existing short-reach coupling links on earlier-generation systems, such as ICA SR and ICA SR1.1 adapters. The existing CS5 coupling link type continues to be used, and short-reach coupling links can be connected from IBM z16 to earlier systems using existing cabling infrastructure.

CF image scalability improvements

IBM z16 coupling facility images are designed to provide improved CF image scalability compared to CF images on previous systems. The CF work manager has been redesigned to partition the available CF processors into small affinity groups of processors and then affinitize CF tasks and all task-related control blocks and data areas to a specific processor affinity group. Furthermore, incoming work received on coupling links and the link buffers associated with them are also affinitized to a specific processor affinity group. This tight relationship between incoming work, executing work, and CF processor affinity groups minimizes the costs of processor cache disruption and movement of CF commands from processor to processor within the CF image as the CF workload is executing, providing improved CF processor scalability for IBM z16 CF images. The resulting effective CF scalability data for IBM z16 CF images will be incorporated into the zPCR and CP3000 capacity-planning tools for planning purposes.

On previous systems, some clients experienced growth constraints when trying to scale a CF image vertically by increasing the number of processors for the CF image beyond the number that would fit on a single processor chip. The scaling curve on earlier systems tended to flatten out when the CF processors spanned multiple processor chips, limiting the CF image's total capacity growth potential as processors were added. With the enhancements made for IBM z16, this flattening out of the scaling curve when the CF processors span multiple processor chips is greatly reduced, meaning that the effective capacity of IBM z16 CF images continues to increase meaningfully all the way up to the maximum of 16 processors in a CF image.

Additionally, to improve the vertical growth potential for IBM z16 CF images, the number of supported CF tasks that can execute concurrently is doubled from 112 to 224.

Adapter technology for long-reach coupling links

Long-reach coupling links on IBM z16 now make use of the Coupling Express2 LR adapter, which provides technology upgrades and improved link throughput management protocols compared to previous generations of long-reach coupling links.

The new Coupling Express2 LR adapters are compatible with existing long-reach coupling links on earlier-generation systems using Coupling Express LR adapters. The existing CL5 coupling link type continues to be used, and long-reach coupling links can be connected from Coupling Express2 LR adapters on IBM z16 systems to Coupling Express LR adapters on earlier-generation systems using existing cabling infrastructure.

Note that Coupling Express LR adapters from previous machine generations cannot be carried forward to IBM z16. Only Coupling Express2 LR new-build adapters may be used to provide long-reach coupling connectivity for IBM z16 systems.

DYNDISP using thin interrupts required for shared-processor CF images

On IBM z15 systems, shared-processor CF images used thin-interrupt- based dispatching (DYNDISP THIN) by default, but support for the older DYNDISP OFF and ON dynamic dispatching options was still available for use. With IBM z16, DYNDISP THIN will be the only available dynamic dispatching option for use with shared-processor CF images. DYNDISP THIN uses interrupt-driven CF dispatching to provide the most efficient processor sharing for CF images, and the best overall shared-processor CF performance and service times. If either DYNDISP OFF or ON is specified for use on an IBM z16 CF image, a warning message will indicate that the CF image will use DYNDISP THIN instead.

Note that for production environments, the use of dedicated- processor CF images remains highly recommended to provide the best possible CF image performance and service times.

CF structure sizing increases for CFLEVEL 25

When migrating coupling facility images to a new, higher CFLEVEL, clients should always make use of the CF Sizer web-based CF structure sizing service at https://www.ibm.com/support/pages/cfsizer. Alternatively, you can use the batch SIZER utility, which may be downloaded from the CF Sizer website, to recalculate CF structure sizes for the new CFLEVEL and make the corresponding changes to their Coupling Facility Resource Management (CFRM) policy INITSIZE or SIZE specifications. CF structure memory size requirements often increase when migrating to a higher CFLEVEL.

IBM z16 CFLEVEL 25 is no exception to this general rule, and in fact the structure size increases may be more noticeable going to CFLEVEL 25 than for some previous CFLEVEL migrations, particularly for structures whose absolute size is small (e.g., 100 MB or less). Clients are urged to carefully resize their CF structures as part of migrating to CFLEVEL 25.

Connectivity considerations and supported maxima

IBM z16 provides coupling link n/n-2 connectivity and Parallel Sysplex n/n-2 hardware coexistence with the IBM z15, IBM z14, and IBM z14 ZR1 generations of IBM Z servers.

The use of IBM z13-generation and IBM z13s-generation systems, or earlier systems, in the same Parallel Sysplex configuration with IBM z16 systems is not supported. As was true on IBM z15 systems, IBM z16 continues to provide support for a maximum of 384 coupling CHPIDs per CEC/system, a maximum of 64 ICP internal coupling CHPIDs per CEC/system, and a maximum of 4 CHPIDs per coupling link port.

Server Time Protocol (STP): time synchronization for Parallel Sysplex

STP is designed to allow events occurring in different IBM Z, Linux on IBM Z, or LinuxONE servers to be properly sequenced in time by synchronizing the clocks of those servers. 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 LIC, presenting a single view of time to the 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 CFs that are time-synchronized to a time value called Coordinated Server Time (CST). The CTN is able to maintain synchronization to Universal Coordinated Time (UTC) through network connectivity and a time synchronization protocol to an external time reference receiving a time signal traceable to UTC.

For IBM Z machines prior to IBM z15, this external time reference would typically be Network Time Protocol (NTP). Starting with IBM z15, this external time reference could also be IEEE 1588 Precision Time Protocol (PTP). Prior to IBM z16, the external time reference network connectivity occurred through the SE Service Word Interface and the internal service network. For clients requiring accuracy to UTC of 100 milliseconds or less, pulse per second (PPS) connectivity is also available.

Direct-connect for STP external time reference

With this, IBM z16 introduces an enhanced method for connecting to a CTN's external time reference. IBM z16 introduces support for connecting the CEC directly to PTP or NTP external time references through your data center network. For example, bypassing the service word interface and internal service network. PTP or NTP traffic will now come into the CEC through Ethernet connectivity to a new adapter card that is in turn connected directly to IBM z16 oscillators. This adapter card features hardware timestamping capabilities, allowing IBM z16 to take full advantage of the accuracy of PTP. It is expected that these enhancements will result in STP being capable of significantly enhanced accuracy to UTC compared to previous IBM Z machines and possibly eliminate the future need for PPS connectivity. Many clients are subject to UTC accuracy regulations, which the enhancements to the external time reference may help you meet. These regulations include the European Securities and Markets Authority (ESMA) directive on markets in financial instruments (MiFID 2) Regulatory Technical Standard (RTS) 25. The regulations also include the US Financial Industry Regulatory Authority (FINRA) rules on financial transaction timing accuracy and the Securities and Exchange Commission (SEC) Rule 613 Consolidated Audit Trail (CAT). Better UTC time accuracy against the external time reference also implies better UTC time accuracy compared to the distributed systems servers, getting tighter time synchronization between all systems involved in the financial transactions systems.

IBM z16 sustainability

IBM has a longstanding commitment to building a more sustainable, equitable future. Back in 1971, IBM formalized its environmental programs and commitment to leadership with the issuance of its Corporate Policy on IBM's Environmental Responsibilities. This was a quarter century before the first International Organization for Standardization (ISO) 14001 environmental management systems standard was published. IBM's activities between then and 2021, when IBM committed to reaching net zero greenhouse gas emissions by 2030 in all 175 countries in which it operates, make it an ideal partner for the increasing number of businesses that consider sustainability a strategic direction. For more information, see the IBM Commits To Net Zero Greenhouse Gas Emissions By 2030 web page.

Continuing in that same spirit, IBM Z is the ideal platform for achieving corporate sustainability goals. Continuing the 25-year history of improved sustainability factors, such as increased system capacity per kW, in every release, IBM z16 is designed to enable even greater sustainability success for businesses.

IBM z16 is built for the modern data center to optimize flexibility and sustainability. An IBM z16 system using the Intelligent Power Distribution Unit (iPDU) power option is designed to save considerable energy compared to IBM z14 and IBM z15 systems utilizing bulk power technology. With the introduction of on-chip AI acceleration, IBM Z continues to deliver key architectural advantages to support your organization's sustainability goals, including:

  • Data center modularity and flexibility
  • Specialty engines to offload I/O processing and perform on-chip AI and encryption
  • Ability to sustain high CPU utilization
  • High reliability and availability, which increases the lifespan of the hardware

These key architectural advantages help make IBM z16 a differentiator in your data center when it comes to sustainability benefits.

IBM continues to focus on environmental design for its products and provides resources to help businesses quantify the impacts. IBM z16 makes available product carbon footprint reports using the Product Attributes to Impact Algorithm (PAIA) to help businesses understand the lifecycle carbon sustainability of the IBM Z hardware within their data centers. IBM z16 provides telemetry information that is useful for the integration into modern data center infrastructure management (DCIM) systems through a set of secure, REST-based web service APIs. IBM z16 environmental telemetry aligns with the latest ASHRAE Tier 1 DCIM Compliance.

The combination of these IBM z16 enhancements with IBM Z's existing sustainability benefits, and also having IBM's overall commitment to sustainability in your corner, means that having an IBM z16 system in your data center will go a long way toward helping you meet your sustainability goals.

Modernize for hybrid cloud

Today's IT leaders are driving new value and differentiation from their core business applications and data by employing a modernization strategy that supports a larger hybrid cloud strategy across their IT landscape.

IBM z16 is designed to be the premier hybrid cloud and AI transactional platform to support that hybrid cloud strategy. IBM z16 is designed to deliver unparalleled value and choice to clients with flexibility for the future beyond what prior generations of IBM Z provided. IBM z16 is designed to bring significant differentiated value to clients by infusing AI at every level of workload and data across hybrid cloud for the most vital workloads driving the globe. Differentiation comes from unmatched support for data gravity between applications and data co-located on IBM z16 systems across Linux on IBM Z and z/OS, achieving real-time AI at scale, and providing you with intelligent and trusted systems and platforms.

Building on this solid foundation of trust and expertise while coupling IBM z16 with Red Hat OpenShift as the innovative, hybrid, multicloud platform built on open source provides a flexible hybrid cloud solution that embraces client choice. With IBM Z and cloud together, clients may lower cost, reduce risk, and help ensure business continuity while supporting modernization and digital transformation initiatives.

IBM z16 and cloud together is the better architecture for business innovation, because it takes a platform approach to provide a single integrated fabric across all those silos. You can have a common cloud experience that enables consistent, agile practices, which supports interoperability and secure integration of workloads and data from on IBM z16 across hybrid cloud, regardless of where the capabilities are required.

IBM z16 and supporting IBM Z and Red Hat software provide an unprecedented combination of speed, reliability, and security along with a cloud-native experience centered on industry standards, open tools, and pioneering intelligence. This combination delivers an open and flexible architecture that helps empower clients to use the best fit IT for their business needs to deliver more value than a public cloud-only approach.

This IBM z16 and supporting IBM Z and Red Hat software can help businesses:

  • Simplify access to applications and data through secure API creation and integration in minutes
  • Leverage agile enterprise DevOps for cloud-native development with open tools and rapid application analysis
  • Standardize IT automation to empower developers with access to open source environments and IBM z16 resources
  • Adopt the right modernization approach for each workload to help ensure cost and value are aligned
  • Enable tighter integration of workloads with a consistent cloud experience
  • Automate processes and deliver intelligent operations for productivity, efficiency, and innovation

IBM z16 helps empower businesses to do this and more through the power of IBM Z and the cloud, where they can leverage agile practices and adopt a "build once, deploy anywhere" approach across a hybrid infrastructure.

z/OS support for IBM z16

New functions in z/OS continue to enhance the role of IBM Z with support for IBM z16 in helping you provide solutions with breakthrough technologies for your critical workloads.

z/OS support for the IBM z16 IBM Z Integrated Accelerator for AI

The IBM Z Integrated Acceleratorr for AI is an on-chip inference accelerator in IBM z16. The z/OS's new zDNN library provides APIs and a toolkit to drive the integrated accelerator for AI through a new NNPA facility instruction, which drives the integrated accelerator for AI.

The zDNN provides support for an exploiter to transform tensor memory layout from standard layout to nonstandard layout, which is required by NNPA. zDNN also provides support for an exploiter to convert tensor element data type from standard types to the NNPA required DLFloat16 format and call deep learning primitives supported on NNPA.

The zDNN is available on both z/OS and Linux on IBM Z distributions. Linux on IBM Z facilitates zCX exploitation of the integrated accelerator for AI when using supported Linux AI frameworks. Exploiters on servers without the integrated accelerator for AI are expected to provide an alternate implementation of primitives. The zDNN is provided on z/OS 2.4 and later.

z/OS support for IBM z16 System Recovery Boost enhancements

As described above, with IBM z16, System Recovery Boost provides support for three new z/OS-oriented use cases for short-duration recovery process boosts:

  • SVC dump processing
  • Client-selected middleware starts and restarts
  • HyperSwap configuration load and reload

z/OS provides the necessary administrative and operational controls in CHNGDUMP to manage which SVC dumps may receive a boost, and in the WLM Service Definition Classification Rules to manage which middleware starts and restarts may receive a boost. Additionally, when running on IBM z16, z/OS display commands for System Recovery boost are enhanced to provide additional information about the current usage of the recovery process boost time pool that is available to the z/OS image, and when that time pool will be refreshed.

In addition to these IBM z16 -specific enhancements, z/OS provides new System Recovery Boost support for dynamically enabling and disabling recovery process boosts for all use cases, which clients can use to better control how the system makes use of the available recovery process boost time. Furthermore, z/OS is providing improved display, monitoring, and SMF logging capabilities that cover both the actual and potential use of recovery process boost time to assist clients in managing and understanding the usage of recovery process boost time in their z/OS images.

The z/OS software support for IBM z16 System Recovery Boost requires PTFs for z/OS 2.4 or 2.5. The z/OS PTFs will be included in a z/OS FIXCAT designated specifically for System Recovery Boost support, named "IBM.Function.SystemRecoveryBoost".

z/OS support for IBM z16 CPACF counters

With IBM z16, IBM provides processor activity instrumentation to count cryptographic operations.

SMF 0 records have been enhanced to indicate the number of crypto counters supported by the current IBM Z hardware.

SMF 30 records have been enhanced to include new crypto counter sections that contain counters for CPACF cryptographic instructions utilized by a job in a given period. These sections are produced only for those instructions that are used. These counters are correlated with z/OS jobs and users for the determination of the algorithms, bit lengths, and key security utilized by a given workload. This data can aid in compliance, performance, and configuration.

  • The SMF 30 self-defining section indicates the length and number of crypto counter sections.
  • The SMF 30 product/subsystem section indicates if the crypto counters are active.

This feature is supported on z/OS 2.4 and later. It requires APAR OA61511.

z/OS support for compliance

z/OS has been enhanced to enable the collection of compliance data from IBM z16 CPACF counters and several z/OS products and components. A new z/OSMF Compliance fact collection REST API sends an ENF86 signal to all systems. Participating products and components will collect and write compliance data to new SMF 1154 records associated with its unique subtype. These new SMF 1154 records may be integrated into solutions such as the IBM z16 IBM Z Security and Compliance Center.

This support requires PTFs for z/OS 2.4 and z/OS 2.5. The PTFs will be identified by fix category designated specifically for compliance data collection support named "IBM.Function.Compliance.DataCollection". See IBM Fix Category Values and Descriptions for information on how to use this fix category to identify and install the specific PTFs that enable compliance data collection.

For additional information about z/OS collection sources and enablement, see:

  • IBM Z Security and Compliance Center, Software Announcement 222-005
  • CICS Transaction Server for z/OS 6.1, Software Announcement 222-092
  • Db2 13 for z/OS powered by AI innovations provides industry scalability, business resiliency and intelligence, Software Announcement 222-003

Compiler support for IBM z16

A key strength of the IBM enterprise compilers, Enterprise COBOL, Enterprise PL/I, and XL C/C++, is the continual support of the latest IBM Z hardware architectures. The latest releases of the compilers (Enterprise COBOL for z/OS 6.4, Enterprise PL/I for z/OS 6.1, and the new Open XL C/C++ 1.1 for z/OS component) make available the ARCH(14) option to exploit the new hardware instructions available on the IBM z16. Application developers can recompile using the new ARCH(14) compiler option to instruct the compiler to generate code to exploit instructions available on IBM z16. This translates into immediate support of IBM z16 and improved application performance without any source code changes.

IBM Open XL C/C++ 1.1 for z/OS is the newest XL C/C++ compiler that is based on the open source LLVM infrastructure. It supports up to the latest C17 and C++17 language standard features, and the latest hardware exploitation capabilities - including exploitation of the latest IBM z16. It is a 64-bit only compiler that runs on z/OS UNIX. Clients can download this web deliverable and run it on zOS 2.4 and 2.5.

The latest releases of IBM SDK Java Technology Edition 8, and IBM Semeru Runtime Certified Edition 11, for Linux on IBM Z and z/OS supports and exploits IBM z16. Powered by Eclipse OpenJ9 technology, the Java Virtual Machine detects the underlying hardware and optimizes existing Java application code with transparent exploitation of new IBM z16 hardware instructions.

IBM Semeru Runtime Certified Edition for z/OS is a new, high- performance 64-bit Java runtime and development kit on z/OS. It supports the new Java 11 language features and includes the OpenJDK Java 11 class libraries and the Eclipse OpenJ9 JVM. Clients can now develop Java applications using Java 11.

The latest release of IBM Automatic Binary Optimizer for z/OS (ABO) 2.2 makes available a new ARCH(14) option to exploit the instructions available on IBM z16. Using ABO 2.2 to optimize existing VS COBOL II 1.3 to Enterprise COBOL 6.4 modules allows these modules to obtain improved computation performance without the need for recompilation.

Open Enterprise Languages -- IBM Open Enterprise SDK for Node.js, IBM Open Enterprise SDK for Python, IBM Open Enterprise SDK for Go, and IBM Open XL C/C++ on z/OS support the current open source language levels and are enabled to run natively on z/OS. They provide new and exciting application modernization options for clients. Performance can also be optimized by co-locating applications written in these languages with core applications and data on IBM Z.

CF cache and lock structure resiliency improvements

IBM z16 CFLEVEL 25 support provides improved resiliency support for CF cache and lock structure usage. The CF now implements a functional retry buffer capability that applies to the subset of CF cache and lock commands that are not perfectly able to be safely retried when an interface control check (IFCC) or other link-related error interrupts the normal request flow to or from the CF image. Retry buffers make it possible for z/OS to always determine the outcome of such CF operations following a transient link error, avoiding any ambiguities related to the CF structure updates made by those requests. z/OS makes use of CF retry buffers to improve the resiliency of these CF structure operations without requiring any software updates by the user function that is exploiting the CF structure for its data-sharing purposes.

z/OS APAR OA60275 provides the z/OS operating system support for retry buffer enhancements for z/OS 2.2 through 2.5.

Additionally, IBM z16 CFLEVEL 25 provides lock structure exploiters with the new capability to dedicate a subset of lock structure record data entries that are reserved for recovery use only. Exploiters may reserve these record data entries and thereby ensure that even when all of the normal record data entries in a lock structure have been used up, the special pool of dedicated recovery-use entries still remain available for use in recovering from this structure-full condition.

z/OS APAR OA60650 provides the z/OS operating system support for reserved lock structure record data entries for z/OS 2.3 through 2.5.

CF cache structure object residency time monitoring and metrics

New CF cache structure monitoring and metrics are provided for IBM z16 CFLEVEL 25 coupling facilities. These metrics provide cache structure exploiters with additional cache object information that can be used to provide improved cache management, either directly by the exploiter or through improved cache usage reporting by the exploiter. New storage class statistics are provided to report on cache directory entry and data area "residency times," defined as the average time between when a cache directory entry or its associated data area are first created, until the time that those cache structure resources are reclaimed for use to satisfy a more-current cache structure request. Residency time metrics can be used to provide insights into the overall cache effectiveness for CF cache structures.

z/OS APAR OA60650 provides the z/OS operating system support for cache structure object residency time metrics for z/OS 2.3 through 2.5.

z/OS upgrade improvements for IBM z16

IBM is making continual enhancements with assistance in z/OS upgrades for the new IBM z16 server. The z/OS IBM z16 Upgrade Workflow, which provides all the necessary information to position z/OS on the IBM z16 server, will be provided in a z/OS program temporary fix (PTF), which has been identified with the SMP/E FIXCAT IBM.Device.Server.z16-3931.RequiredService. Any updates and fixes for the z/OS IBM z16 Upgrade Workflow will be provided with PTFs and service supported through the standard IBM z/OS service process. By including the z/OS IBM z16 Upgrade Workflow both in the z/OS product and in an exported form on the Abstract for the z/OS Upgrade Workflow web page , this important technical material is conveniently available for use while preparing for and learning about your upgrade to IBM z16.

z/OS identifying and installing PTFs for IBM z16

z/OS support is delivered in service (PTFs) for IBM z16, which have been identified using SMP/E fix categories (FIXCATs). These FIXCATs can be used to identify minimum required service, additional recommended service, and service needed for exploitation.

The minimum required PTFs for z/OS have been identified with the SMP/E FIXCAT IBM.Device.Server.z16-3931.RequiredService
PTFs that are recommended to be installed by the IBM service organization are identified with the SMP/E FIXCAT IBM.Device.Server.z16-3931.RecommendedService
IBM z16 exploitation functions, which you may choose to use later after your initial upgrade, have been identified with the SMP/E FIXCAT IBM.Device.Server.z16-3931.Exploitation

Use the SMP/E REPORT MISSINGFIX command with the latest Enhanced HOLDDATA to quickly and easily identify any PTFs that are missing on your system for the category in which you are interested.

IBM Container Hosting Foundation for z/OS 1.0.0

IBM Container Hosting Foundation for z/OS is a z/OS software product (5655-HZ1) that satisfies licensing for the enablement of IBM Z Container Extensions (zCX). IBM Container Hosting Foundation for z/OS is required to run zCX on IBM z16.

IBM zCX Foundation for Red Hat OpenShift (5655-ZCX)

The introduction of zCX provided z/OS clients with an OCI container-based software solution to run their Linux on IBM Z software directly on z/OS. This extends Linux application deployment capability to z/OS clients who join traditional Linux on IBM Z clients and LinuxONE clients.

Red Hat OpenShift is an enterprise-ready Kubernetes container platform built for an open hybrid cloud strategy that provides a consistent application platform to manage hybrid cloud, multicloud, and edge deployments. Red Hat OpenShift on z/OS, using zCX, enables clients to leverage the power of OpenShift with the power of z/OS. This results in application deployment and management of OpenShift with the ability to co-locate applications and workloads that have an affinity for z/OS by bringing those applications and workloads closer to z/OS applications and data.

The availability of Red Hat OpenShift on z/OS with zCX enables a strong union between z/OS and the container orchestration benefits of Red Hat OpenShift. It enables clients to take advantage of the Red Hat OpenShift Container Platform while exploiting z/OS qualities of service, such as scalability, availability, integrated disaster recovery, backup, workload management, and integration with z/OS security.

IBM z/OS Change Tracker: complementary resiliency feature availability

As IBM continues to provide a suite of robust tools to help system programmers manage z/OS, IBM is also offering IBM z/OS Change Tracker, a comprehensive configuration change management tool for tracking, controlling, and managing changes in software, as a priced feature of z/OS 2.5.

With a simple control interface to identify, manage, and audit configuration files, the z/OS Change Tracker is planned to help clients with all aspects of the change configuration management experience, including software management and resiliency. Today, monitoring hundreds of configuration files can be a manual and tedious process, making it difficult to do without the right tools and leaving the potential for undesired system configuration changes. z/OS Change Tracker is also planned to help system programmers quickly understand the differences between two groups of data sets or volumes to see if deployment of software has resulted in identical copies.

z/VM support for IBM z16

The z/VM 7.1 and z/VM 7.2 PTFs for APAR VM66532 provide support to enable guests to exploit function on IBM z16, including:

  • Imbedded AI acceleration designed to reduce the overall time required to execute CPU operations for neural networking processing functions and to help support real-time applications like fraud detection.
  • Compliance-ready CPACF counter support, which provides a means for guests to track cryptographic compliance and instruction use.
  • Breaking Event Address Register (BEAR) enhancement facility designed to improve the ability to debug wild branches.
  • Vector packed decimal enhancements 2, which deliver new instructions intended to provide performance improvements.
  • Reset DAT Protection facility designed to provide a more efficient way to disable DAT protection, such as during copy-on-write or page change tracking operations.
  • Support for the consolidated boot loader designed to provide guest IPL from a SCSI LUN. Note that guest IPL from SCSI, with or without the DUMP option, will now require a minimum guest virtual memory size of 768 MB.
  • RoCE Express3 adapter, enabling guests to exploit Routable RoCE, Zero Touch RoCE, and SMC-R V2 support.
  • CEX8S adapter supported as a dedicated or shared resource. Dedicated guests will be able to take advantage of all functionality available with the CEX8S adapters, including assorted new enhancements and use of quantum-safe APIs.(3)

The PTFs for APAR VM66532 also support CPU/Core topology location information that will be included in z/VM monitor data, providing a better picture of the system for diagnostic and tuning purposes.

The following infrastructure support must be installed on all members within an z/VM Single System Image (SSI) cluster before any member of the cluster is IPLed on IBM z16:

  • z/VM 7.2 with the PTF for APAR VM66504
  • z/VM 7.1 with the PTFs for APARs VM66206 and VM66504

All IBM z16 compatibility support will be in the base of z/VM 7.3. For additional information on z/VM 7.3, see Software Announcement 222-102.

For further details, review the z/VM website at https://www.vm.ibm.com/service/vmreqz16.html and the hardware PSP bucket 3911DEVICE z/VM subset.

z/VM function portal

The z/VM Continuous Delivery News web page is the primary vehicle used by IBM to describe more functions that are planned for z/VM. It is the recommended way to keep track of future development and support plans for the z/VM product. z/VM clients should consider subscribing to this page. Instructions are included on the VM Site File Change Notification web page.

Select z/VM 7.2 enhancements delivered during 2021

The following z/VM 7.2 enhancements were delivered during 2021 and provide additional IBM z16 benefit for z/VM workloads:

  • 4 TB real memory support: With the PTF for APAR VM66173, z/VM delivers support for up to 4 TB of real memory, allowing z/VM systems to address a full 4 TB of first-level (real) memory, doubling the previous supported limit of 2 TB.
  • Dynamic Memory Downgrade support:
    With the PTF for APAR VM66271, Dynamic Memory Downgrade extends the real storage dynamic management characteristics of z/VM by allowing up to 50% of the real memory to be removed from a running z/VM system. A minimum hardware bundle level is required to avoid a possible downgrade stall.
    For additional details, see https://www.vm.ibm.com/memman/dmd.html.
  • Improved Live Guest Relocation for shared cryptography users: With the PTF for APAR VM66496, Live Guest Relocation for APVIRT cryptographic environments is enabled when the type of shared cryptographic resource on the source system does not match the type on the target system.
  • z/XC support:
    With the PTFs for APARs VM66201 (CP), VM66425 (CMS), and VM66489 (Perfkit), z/Architecture Extended Configuration (z/XC) support is provided. Conversational Monitor System (CMS) applications that run in z/Architecture can use multiple address spaces. Programs can use z/Architecture instructions and registers, within the limits of z/CMS support, and can use VM data spaces in the same CMS session.
    IBM z16 requires z/CMS and z/XC support to be configured within guest virtual machines that exploit z/VM HCD support. In addition, once applied, the PTF for IOCP APAR VM66549 will require z/CMS support on any IBM Z or LinuxONE server. IOCP support is in the base of z/VM 7.3 and requires z/CMS.
  • Direct-to-Host Service Download support:
    With the PTF for APAR VM66540, z/VM 7.2 provides an optional way to download service to your z/VM system. A web interface simplifies the downloading of z/VM service that was ordered through IBM Shopz. The service files can be transferred through direct-to-host connection.

VSE support for IBM z16

z/VSE 6.2 and its standalone utilities run entirely in z/Architecture mode.
21(st)Century Software VSE(n)6.3 and its standalone utilities run entirely in z/Architecture mode.

Note: (1) ITIC 2021 Global Server Hardware Server OS Reliability Report, June/July 2021.
Note: (2) IBM z16 with the Crypto Express8S card offers quantum-safe APIs that provide access to quantum-safe algorithms, which have been selected as finalists during the PQC standardization process conducted by NIST Information Technology Laboratory. Quantum-safe cryptography refers to efforts to identify algorithms that are resistant to attacks by both classical and quantum computers, to keep information assets secure even after a large-scale quantum computer has been built. Source: ETSI Quantum-Safe Cryptography (QSC). These algorithms are used to help ensure the integrity of a number of the firmware and boot processes. IBM z16is the industry-first system protected by quantum- safe technology across multiple layers of firmware.
Note: (5) Based on internal measurements. Results may vary by customer based on individual workload, configuration and software levels. Visit LSPR website for more details at: https://www-40.ibm.com/servers/resourcelink/lib03060.nsf/pages/lsprind ex)
Note: (6) Measurements were done with an IBM internal workload generation a representative mix of coupling facility requests on an IBM z16 running two z/OS partitions with 16 GCPs on each partition and coupling facility image(s) with 4 ICFs each running at about 30% utilization. Measured with shared ICA-SR links. The amount of improvement will vary based on workload and configuration.

HMC 2.16.0 highlighted feature enhancements

  • HMC security enhancements:
    • Additional MFA-supported types and support of additional z/OS environment

      Previously, the HMC provided support for MFA types of Time-based One-Time Password (TOTP) and RSA SecurID. HMC 2.16.0 will now provide support for additional MFA types of the following using a server connection to the IBM Z MFA component running in an IBM Z operating system:

      Generic RADIUS - enables support of all various Remote Authentication Dial-In User Service (RADIUS) factor types; Certificates - Personal Identity Verification (PIV) and Common Access Card (CAC)

      Previously, the HMC only supported connections to the IBM Z MFA component in z/OS, and now the HMC 2.16.0 will support connections to the IBM Z MFA component running in z/VM and Linux on IBM Z.

    • PCI-DSS compliance for HMC logon

      HMC 2.16.0 logon controls are being enhanced to address security standards for PCI-DSS.

    • TLS 1.3 support

      HMC 2.16.0 will support TLS 1.3 as well as TLS 1.2.

      Clients can choose to only support TLS 1.3 for HMC/SE, but prior to doing so, clients must ensure that all services or servers connecting through the TLS to the HMC/SE support TLS 1.3. These include remote browsing workstations, LDAP authentication servers, WebServices API connections, Fibre Channel End Point Security, FTPS servers, and Single Object Operations.

      Note that TLS 1.0 and TLS 1.1 support will be removed for 2.16.0 HMCs/SEs. Clients must ensure all connecting servers support TLS 1.2 or TLS 1.3.

    • Reduction of default users shipped with HMC/SE, all default users password change

      In 2020, California instituted an IoT password law requiring any default shipped passwords to be changed on installation or unique per device shipped. This same type of requirement is expanding worldwide, and starting with IBM z16, HMC/SE will require new IBM Z systems default user password changes for all IBM z16 systems.

      To help manage this requirement, the HMC/SE will limit default user IDs or requirement to ACSADMIN and SERVICE.

      ADVANCED, OPERATOR, STORAGEADMIN, and SYSPROG default users will no longer be shipped.

      Default user roles for ADVANCED, OPERATOR, STORAGEADMIN, and SYSPROG will be shipped, and user IDs can be created from those. Any default user IDs that are part of a previous HMC level can be carried forward to new HMC levels as part of a MES Upgrade or through the selection of User Profile Data for the Save/Restore Customizable Console Data or Configure Data Replication tasks.

      As part of the IBM z16 installation, HMC/SE ACSADMIN and SERVICE users will be required to make a password logon change on their first user logon.

      Clients are responsible for maintaining passwords, and they especially need to establish a plan for service users.

      Clients should be ready to provide the user ID and password to an IBM Service Support Representative (SSR) upon arrival to the IBM System when servicing the IBM Z after the initial installation.

      Note that IBM recommends that clients maintain a list of unique service IDs and passwords to accommodate different SSRs servicing the system and avoid sharing user IDs. It is imperative to establish a user ID and password handling process to avoid any delay of service.

    • Changed default certificate expiration

      Newly created HMC/SE certificates will now have a default expiration of 398 days, which is being driven by industry security requirement. Clients have the option to modify thatexpiration time.

      HMC/SE enhancements have been made to notify clients by a Hardware Messagestarting at 90 days and other subsequent various days prior to expiration.

      Clients certificates managed by the HMC/SE include uses for browser, WS APIs, HMCmobile, remote syslog server, Fibre Channel End Point Security, Remote Support Facility(RSF) proxy, and MFA.

  • HMC Workspace enhancements:
    • The HMC dashboard replaces the HMC Home tab's Welcome node

      The toolbar at the top will contain the Helpful link and HMC information. In addition, that HMC dashboard will contain the following four HMC widgets, which provide optional and simplified views of previous actions without a significant overhall of the entire HMC user experience. Additional widgets are expected to be added in the future.

      1-What's new; 2-Systems health; 3-Hardware messages; 4-Frequently used tasks

    • n-mode Power STP Imminent Disruption Signal option

      On IBM Z, losing a Preferred Time Server (PTS) has significant consequences to the timing network and the overall workload execution environment of the IBM Z sysplex. The IBM Z and the HMC have had longtime automated failover protection for various cases that can arise.

      However, for IBM z16, since there is no longer an integrated battery facility, support was added by the HMC to allow the client to configure an option to monitor for n-mode power conditions (wall power or line cord loss), and if detected, an automated failover will occur to the Backup Time Server (BTS). Note that you should provide some backup power method to hold power for 60 seconds on the PTS to allow failover to successfully complete.

      There are also Manage System Time user interface controls to manage to failback to the PTS when the full power state is restored. There are also HMC System Events for client awareness through user interface or automation.

    • Base Control Program internal interface (BCPii) enhancements

      HMC support of BCPii is being enhanced to provide suspend and resume notifications to the operating system side of BCPii when the SE is rebooted for a firmware update, as well as other more rare recovery conditions of when an SE reboot could occur. GDPS will utilize these notifications to generally eliminate BCPii requests while the SE is away. System Automation Processor Operations (SA Proc Ops) and the client's own BCPii automation can also utilize these new notifications.

      The HMC is also adding resiliency for BCPii communication by monitoring for additional conditions of early warning of potential communication issues and executing methods of automatic recovery.

    • HMC Data Replication enhancements

      The HMC Data Replication support provides an underlying communication framework to allow you to configure user management and associated activation profiles, monitor system event notifications, and access other various controls on a single HMC, and then replicate that to other HMCs so that users only have to do the configuration or customization actions once.

      The HMC 2.16.0 has been enhanced to ensure when replication is active, that replication data can only be customized by the user on a primary or peer HMC. Replication data can no longer be changed by a user or automation on a replica HMC other than by the HMC Data Replication framework.

      In addition, the HMC Configure Data Replication task is enhanced to have a panel design similar to other HMC wizard tasks, which guide the user step-by-step through configuration with an underlying focus on the defined role of an HMC as either a primary, replica, or peer.

    • Remote Code Load (RCL) enhancements

      IBM z15 introduced the RCL option for IBM Z firmware, enabling IBM to upgrade the IBM Z system remotely through an IBM Z Remote Support Facility (zRSF) using only the outbound connection from the HMC. Clients can choose what and when to be updated, and IBM monitors the entire process remotely and notifies the client upon completion.IBM z16 has incorporated feedback from that IBM z15 experience, and the following IBM z16 enhancements are included:

      HMC 2.16.0 provides the capability for an HMC to do data replication of the RCL authorization token, allowing it to be used on any HMC in the enterprise.

      IBM Resource Link provides the capability to reschedule an RCL, such as changing the time or date of the load or the bundle level, without requiring the client to do an HMC RCL Cancel.

      IBM HMC Mobile provides the ability to generate the HMC authorization and view and cancel scheduled updates.

      The ability to do a single HMA HMC Remote Code schedule, which ensures both HMCs on the HMAs are updated, including the required action of primary/alternate switch.

  • IBM HMC Mobile enhancements:

    HMC Mobile 4.0 provides enhanced logon support for the new HMC 2.16.0 Multi-Factor Authentication types of Generic RADIUS and certificates as well as support for PCI-DSS compliance.

    HMC Mobile 4.0 additionally provides support for RCL HMC authorization token generation as well as the ability to view and cancel scheduled updates.

  • HMC YouTube videos:

    General documentation on the HMC can be found on HMC Online Help and on IBM Resource Link.

    There is additional information on HMC through YouTube videos, which include subject areas like HMC Overview and Management, Access and Security, HMC Mobile, Manage System Time, and Dynamic Partition Manager.

    Current videos are available on https://ibm.biz/IBM-Z-HMC. This website should also be monitored for videos being added to the IBM HMC playlist, which will include some of the HMC 2.16.0 features and enhancements.

For HMC 2.16.0, there will no longer be support to configure NTP with Autokey because Autokey is known to not be secure.

On HMCs prior to 2.16.0, access to NTP used to have MD5 as the only supported hashing algorithm. MD5 is no longer secure, official support for MD5 has been withdrawn, and its use is discouraged. For HMC 2.16.0, SHA-512 will be the default hashing algorithm to be selected for new defines. MD5 will be allowed because both the server and client must match, and this change needs to be communicated with external NTP server owners.

Enhancements to software pricing Technology Transition Offerings (TTOs)

Complementing the IBM z16 server, IBM is introducing:

  • A TTO called Technology Update Pricing for IBM z16
  • 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)
  • IBM z16 server eligibility for Tailored Fit Pricing for IBM Z offerings

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

When an IBM z16 server is in an actively coupled Parallel Sysplex or a loosely coupled complex, you may choose either aggregated AWLC pricing or aggregated Parallel Sysplex License Charges (PSLC) pricing, subject to all applicable terms and conditions.

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

For additional information about software pricing for the IBM z16 server, see Software Announcement 222-103.

When an IBM z16 server is running z/VSE, you may choose Midrange Workload License Charges (MWLC), subject to all applicable terms and conditions.

For more information about AWLC, CMLC, Tailored Fit Pricing for IBM Z, MzNALC, PSLC, MWLC, or the Technology Update Pricing and Transition Charges for Sysplexes or Multiplexes TTO offerings, see the IBM Z software pricing website.

The CMP offering was withdrawn as of January 1, 2021, as announced in U.S. Software Announcement 220-513. For existing CMP clients, machines currently eligible to be included in an existing 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.

Tailored Fit Pricing for IBM Z - Hardware Consumption Solution

Previously on May 4, 2021, Tailored Fit Pricing for IBM Z -- Hardware Consumption Solution now adds Linux on IBM Z capability. This provides an always on, consumption-based Linux capacity corridor that provides hybrid cloud flexibility and control for unpredictable workload spikes throughout the day.

To be eligible for the new Tailored Fit Pricing for IBM Z - Hardware Consumption Solution for Linux, clients are required to be on IBM z15 or IBM z16 hardware.

Contact your IBM Z Hardware Representative to determine if you qualify for this offering. If it is determined that Tailored Fit Pricing for IBM Z - Hardware Consumption Solution for Linux may be an appropriate solution for a client's unpredictable daily workload, the subscription and maintenance fee will be based upon the size of the clients' variable capacity corridor. The fee for measured usage will be charged if the workload spikes into the corridor. Clients that are outsourcing service providers are not eligible for the Tailored Fit Pricing for IBM Z Hardware Consumption Solution offering.

BTA water

BTA water is available to those clients who want to relocate their IBM 3931. Removed BTA water must be disposed of properly by the client. BTA water is a mixture of deionized (DI) water and 900-990 PPM benzotriazole (BTA), a corrosion inhibitor.

  • IBM machine type 2819 model BTA feature 9849 provides three 20-liter jugs and supports IBM z13 and IBM z14.
  • Feature 9850 provides one 20-liter jug and supports IBM z15 and IBM z16.
  • IBM machine type 3931 with feature 4040 A Frame Radiator, needs one jug plus one spare jug.
  • IBM machine type 3931 with feature 4041 B Frame Radiator, needs one jug plus one spare jug.

Section 508 of the US Rehabilitation Act

IBM z16* 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 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

Models

Top rule

Model summary matrix

Model PU Memory (note 1) PCIe Fanouts PCIe + I/O Drawer
A01 1 - 200 512 GB to 40,000 GB 0 - 48 0 - 12

Notes:

  1. 10TB per CPC drawer

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.

Feature Total CP7s     IFLs   uIFLs  ICFs   uICFs  zIIPs  uzIIPs
        PUs   (#1958)  (#1959 (#1962 (#1960 (#1974 (#1961 (#1975 Option
        Avail Min/Max  Min/Ma Min/Ma Min/Ma Min/Ma Min/Ma Min/Ma SAP
        for                                                      (#1963
        use                                                      Min/Ma
------- ----- -------- ------ ------ ------ ------ ------ ------ ------
0667    39    0 to 39  0 to   0 to   0 to   0 to   0 to   0 to24 0 to 8
                       39     38     39     38     25
0668    82    0 to 82  0 to   0 to   0 to   0 to   0 to   0 to   0 to 8
                       82     81     82     81     54     53
0669    125   0 to 125 0 to   0 to   0 to   0 to   0 to   0 to   0 to 8
                       125    124    125    124    82     81
0670    168   0 to 168 0 to   0 to   0 to   0 to   0 to   0 to   0 to 8
                       168    167    168    167    110    109
0671    200   0 to 200 0 to   0 to   0 to   0 to   0 to   0 to   0 to 8
                       200    199    200    199    132    131

Notes:

  • There are two Spares per system.
  • The total number of PUs purchased cannot exceed the total number available for that model.
  • One CP, one IFL (#1959), or one ICF (#1960) must be installed with the installation of any uIFLs or prior to the installation of any uIFLs, uICFs or uzIIPS.
  • One CP must be installed with the installation of any zIIPs or prior to the installation of any zIIPs.
  • The total number of zIIPs (#1961) purchased cannot exceed twice the number of CPs purchased for any machine.
  • CP4, CP5, and CP6 are limited to a maximum of 39 PUs
  • The number of standard SAPs provided to the customer are as follows:
    • Feature code 0667 = five SAPs
    • Feature code 0668 = ten SAPs
    • Feature code 0669 = fiftteen SAPs
    • Feature code 0670 = twenty SAPs
    • Feature code 0671 = twenty four SAPs

Customer setup (CSU)

Customer setup is not available on this machine.

Devices supported

HMC 2.16.0 Supported CPCs

Machine Family  Machine    Firmware SE
                Type       Driver   Version
--------------- ---------- -------- -------
IBM z16         3931       51       2.16.0
IBM z15         8561, 8562 41       2.15.0
IBM z14 M0x/LMx 3906       36       2.14.1
IBM z14 ZR1/LR1 3907       36       2.14.1

For HMC 2.16.0, there will no longer be support to configure NTP with Autokey because Autokey is known to not be secure and it is not supported.

On HMCs prior to 2.16.0, access to NTP used to have MD5 as the only supported hashing algorithm. MD5 is no longer secure, official support for MD5 has been withdrawn and its use is discouraged. For HMC 2.16.0, SHA-512 will be the default hashing algorithm to be selected for new defines. MD5 will be allowed because both the server and client must match and this change needs to be communicated with external NTP server owners.

Model conversions

From    From  To      To
Machine Model Machine Model
Type          Type
------- ----- ------- ----- ---
3906    M01   3931    A01   (7)
3906    M02   3931    A01   (7)
3906    M03   3931    A01   (7)
3906    M04   3931    A01   (7)
3906    M05   3931    A01   (7)
8561    T01   3931    A01   (7)

Note: (7) Parts removed as a result of a model conversion become the property of IBM.

Feature conversions

The feature conversion list for IBM z16(tm)Model A01 is now available in the Library section of Resource Link.

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

Parts removed as a result of a feature conversion become the property of IBM.



Back to topBack to top

Technical description

Top rule

Physical specifications Physical specifications Hardware requirements Hardware requirements
Operating environment Operating environment Software requirements Software requirements
Limitations Limitations


Physical specifications

The Physical specifications for IBM z16* Model A01 are now available in the Library section of Resource Link in the Installation Manual for Physical Planning (IMPP).

This information can be obtained at Resource Link.

Using the instructions on the Resource Link panels, obtain a user ID and password.

Resource Link has been designed for easy access and navigation.

Operating environment

The Operating environment information for IBM z16* Model A01 is now available in the Library section of Resource Link in the Installation Manual for Physical Planning (IMPP).

This information can be obtained at Resource Link.

Using the instructions on the Resource Link panels, obtain a user ID and password.

Resource Link has been designed for easy access and navigation.

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 2.16.0 plus Machine Change Levels (MCLs) and the Support Element 2.16.0 are planned to be available on May 31, 2022. You should review the PSP buckets for minimum MCLs and software PTF levels before IPLing operating systems.

HMC 2.16.0 Supported CPCs

Machine Family  Machine    Firmware SE
                Type       Driver   Version
--------------- ---------- -------- -------
IBM z16         3931       51       2.16.0
IBM z15         8561, 8562 41       2.15.0
IBM z14 M0x/LMx 3906       36       2.14.1
IBM z14 ZR1/LR1 3907       36       2.14.1

For HMC 2.16.0, there will no longer be support to configure NTP with Autokey because Autokey is known to not be secure and it is not supported.

On HMCs prior to 2.16.0, access to NTP used to have MD5 as the only supported hashing algorithm. MD5 is no longer secure, official support for MD5 has been withdrawn and its use is discouraged. For HMC 2.16.0, SHA-512 will be the default hashing algorithm to be selected for new defines. MD5 will be allowed because both the server and client must match and this change needs to be communicated with external NTP server owners.

Software requirements

IBM z16 requires at a minimum:

  • z/OS 2.5 with PTFs.(8)
  • z/OS 2.4 with PTFs.(8)
  • z/OS 2.3 with PTFs.(8)
  • z/OS 2.2 with PTFs (an extended service contract is required).
(8) IBM z/OS 2.3, or higher, with IBM z16 will require a minimum of 8 GB of memory. When running as a z/VM guest or on an IBM System z Personal Development Tool, a minimum of 2 GB will be required for z/OS 2.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 was introduced for z/OS 2.2 with PTFs to warn you when an LPAR on an IBM z16 system has been configured with less than 8 GB.
  • z/VM 7.3.
  • z/VM 7.2 with PTFs.
  • z/VM 7.1 with PTFs.
  • z/VSE 6.2 with PTFs.
  • 21(t)Century Software VSE(n)6.3.
  • z/TPF 1.1 with PTFs.
  • Linux on IBM Z - IBM plans to support running the following Linux on IBM Z distributions on IBM z16:
    • SUSE Linux Enterprise Server: SLES 15 SP3 with service and SLES 12 SP5 with service.
    • Red Hat Enterprise Linux: RHEL 9.0 with service, RHEL 8.4 with service, and RHEL 7.9 with service.
    • Canonical: Ubuntu 20.04 LTS with service and Ubuntu 22.04 LTS with service.
    • The support statements for IBM z16 also cover the KVM hypervisor on distribution levels that have KVM support.

    For minimum required and recommended distribution levels refer to the IBM Z website. Note: The IBM product "KVM for IBM Z" is out of service and no longer available from IBM. KVM technology is now provided as part of the distributions.

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

FICON Express32S (CHPID type FC), when utilizing FICON or Channel-to-Channel (CTC), requires at a minimum:

  • z/OS 2.5 with PTFs.
  • z/OS 2.4 with PTFs.
  • z/OS 2.3 with PTFs.
  • z/OS 2.2 with PTFs (an extended service contract is required).
  • z/VM 7.3.
  • z/VM 7.2.
  • z/VM 7.1.
  • z/VSE 6.2 with PTFs.
  • 21(st)Century Software VSE(n)6.3.
  • z/TPF 1.1 with PTFs .
  • Linux on IBM Z - IBM plans to support:
    • SUSE Linux Enterprise Server: SLES 15 SP3 with service and SLES 12 SP5 with service.
    • Red Hat Enterprise Linux: RHEL 9.0 with service, RHEL 8.4 with service, and RHEL 7.9 with service.
    • Canonical: Ubuntu 20.04 LTS with service and Ubuntu 22.04 LTS with service.

FICON Express32S (CHPID type FC), for support of zHPF single track operations, requires at a minimum:

  • z/OS 2.5 with PTFs.
  • z/OS 2.4 with PTFs.
  • z/OS 2.3 with PTFs.
  • z/OS 2.3 with PTFs.
  • z/VM 7.3.
  • z/VM 7.2.
  • z/VM 7.1.
  • z/VSE 6.2 with PTFs.
  • 21(st)Century Software VSE(n)6.3.
  • z/TPF 1.1 with PTFs.
  • Linux on IBM Z - IBM plans to support:
    • SUSE Linux Enterprise Server: SLES 15 SP3 with service and SLES 12 SP5 with service.
    • Red Hat Enterprise Linux: RHEL 9.0 with service, RHEL 8.4 with service, and RHEL 7.9 with service.
    • Canonical: Ubuntu 20.04 LTS with service and Ubuntu 22.04 LTS with service.

FICON Express32S (CHPID type FC, for support of zHPF multitrack operations, requires at a minimum:

  • z/OS 2.5 with PTFs.
  • z/OS 2.4 with PTFs.
  • z/OS 2.3 with PTFs.
  • z/VM 7.3.
  • z/VM 7.2.
  • z/VM 7.1.
  • z/VSE 6.2 with PTFs.
  • 21(st)Century Software VSE(n)6.3.
  • z/TPF 1.1 with PTFs.
  • Linux on IBM Z - IBM plans to support:
    • SUSE Linux Enterprise Server: SLES 15 SP3 with service and SLES 12 SP5 with service.
    • Red Hat Enterprise Linux: RHEL 9.0 with service, RHEL 8.4 with service, and RHEL 7.9 with service.
    • Canonical: Ubuntu 20.04 LTS with service and Ubuntu 22.04 LTS with service.

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

  • z/VM 7.3.
  • z/VM 7.2.
  • z/VM 7.1.
  • z/VSE 6.2 with PTFs.
  • 21(st)Century Software VSE(n)6.3.
  • Linux on IBM Z - IBM plans to support:
    • SUSE Linux Enterprise Server: SLES 15 SP3 with service and SLES 12 SP5 with service.
    • Red Hat Enterprise Linux: RHEL 9.0 with service, RHEL 8.4 with service, and RHEL 7.9 with service.
    • Canonical: Ubuntu 20.04 LTS with service and Ubuntu 22.04 LTS with service.

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

  • z/VM 7.3 for guest exploitation.
  • z/VM 7.2 for guest exploitation.
  • z/VM 7.1 for guest exploitation.
  • Linux on IBM Z - IBM plans to support:
    • SUSE Linux Enterprise Server: SLES 15 SP3 with service and SLES 12 SP5 with service.
    • Red Hat Enterprise Linux: RHEL 9.0 with service, RHEL 8.4 with service, and RHEL 7.9 with service.
    • Canonical: Ubuntu 20.04 LTS with service and Ubuntu 22.04 LTS with service.

T10-DIF support by the FICON Express32S features, when defined as CHPID type FCP, require at a minimum:

  • z/VM 7.3 for guest exploitation.
  • z/VM 7.2 for guest exploitation.
  • z/VM 7.1 for guest exploitation.
  • Linux on IBM Z - IBM plans to support:
    • SUSE Linux Enterprise Server: SLES 15 SP3 with service and SLES 12 SP5 with service.
    • Red Hat Enterprise Linux: RHEL 9.0 with service, RHEL 8.4 with service, and RHEL 7.9 with service.
    • Canonical: Ubuntu 20.04 LTS with service and Ubuntu 22.04 LTS with service.

OSA-Express7S GbE LX 1.2 (#0454) and GbE SX 1.2 (#0455) require at a minimum:

CHPID type OSC:

  • z/OS 2.5 with PTFs.
  • z/OS 2.4 with PTFs.
  • z/OS 2.3 with PTFs.
  • z/OS 2.2 with PTFs (an extended service contract is required).
  • z/VM 7.3.
  • z/VM 7.2.
  • z/VM 7.1.
  • z/VSE 6.2 with PTFs.
  • 21(st)Century Software VSE(n)6.3.
  • z/TPF 1.1 with PTFs.
  • Linux on IBM Z - IBM plans to support:
    • SUSE Linux Enterprise Server: SLES 15 SP3 with service and SLES 12 SP5 with service.
    • Red Hat Enterprise Linux: RHEL 9.0 with service, RHEL 8.4 with service, and RHEL 7.9 with service.
    • Canonical: Ubuntu 20.04 LTS with service and Ubuntu 22.04 LTS with service.

CHPID type OSD:

  • z/OS 2.5 with PTFs.
  • z/OS 2.4 with PTFs.
  • z/OS 2.3 with PTFs.
  • z/OS 2.2 with PTFs (an extended service contract is required).
  • z/VM 7.3.
  • z/VM 7.2.
  • z/VM 7.1.
  • z/VSE 6.2 with PTFs.
  • 21(st)Century Software VSE(n)6.3.
  • z/TPF 1.1 with PTFs.
  • Linux on IBM Z - IBM plans to support:
    • SUSE Linux Enterprise Server: SLES 15 SP3 with service and SLES 12 SP5 with service.
    • Red Hat Enterprise Linux: RHEL 9.0 with service, RHEL 8.4 with service, and RHEL 7.9 with service.
    • Canonical: Ubuntu 20.04 LTS with service and Ubuntu 22.04 LTS with service.

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

  • z/OS 2.5 with PTFs.
  • z/OS 2.4 with PTFs.
  • z/OS 2.3 with PTFs.
  • z/OS 2.2 with PTFs (an extended service contract is required).
  • z/VM 7.3.
  • z/VM 7.2.
  • z/VM 7.1.
  • z/VSE 6.2 with PTFs.
  • 21(st)Century Software VSE(n)6.3.
  • z/TPF 1.1 with PTFs.
  • Linux on IBM Z - IBM plans to support:
    • SUSE Linux Enterprise Server: SLES 15 SP3 with service and SLES 12 SP5 with service.
    • Red Hat Enterprise Linux: RHEL 9.0 with service, RHEL 8.4 with service, and RHEL 7.9 with service.
    • Canonical: Ubuntu 20.04 LTS with service and Ubuntu 22.04 LTS with service.

OSA-Express7S 10 GbE LR 1.2 (#0456) and 10 GbE SR 1.2 (#0457) require at a minimum:

CHPID type OSD:

  • z/OS 2.5 with PTFs.
  • z/OS 2.4 with PTFs.
  • z/OS 2.3 with PTFs.
  • z/OS 2.2 with PTFs (an extended service contract is required).
  • z/VM 7.3.
  • z/VM 7.2.
  • z/VM 7.1.
  • z/VSE 6.2 with PTFs.
  • 21(st)Century Software VSE(n)6.3.
  • z/TPF 1.1 with PTFs.
  • Linux on IBM Z - IBM plans to support:
    • SUSE Linux Enterprise Server: SLES 15 SP3 with service and SLES 12 SP5 with service.
    • Red Hat Enterprise Linux: RHEL 9.0 with service, RHEL 8.4 with service, and RHEL 7.9 with service.
    • Canonical: Ubuntu 20.04 LTS with service and Ubuntu 22.04 LTS with service.

OSA-Express7S 25 GbE LR 1.2 (#0460) and OSA-Express7S 25 GbE SR 1.2 (#0459) require at a minimum:

CHPID type OSD:

  • z/OS 2.5 with PTFs.
  • z/OS 2.4 with PTFs.
  • z/OS 2.3 with PTFs.
  • z/OS 2.2 with PTFs (an extended service contract is required).
  • z/VM 7.3.
  • z/VM 7.2.
  • z/VM 7.1.
  • z/VSE 6.2 with PTFs.
  • 21(st)Century Software VSE(n)6.3.
  • z/TPF 1.1 with PTFs.
  • Linux on IBM Z - IBM plans to support:
    • SUSE Linux Enterprise Server: SLES 15 SP3 with service and SLES 12 SP5 with service.
    • Red Hat Enterprise Linux: RHEL 9.0 with service, RHEL 8.4 with service, and RHEL 7.9 with service.
    • Canonical: Ubuntu 20.04 LTS with service and Ubuntu 22.04 LTS with service.

OSA-Express7S 1000BASE-T Ethernet 1.2 (#0458) requires at a minimum:

CHPID type OSC supporting TN3270E and non-SNA DFT:

  • z/OS 2.5 with PTFs.
  • z/OS 2.4 with PTFs.
  • z/OS 2.3 with PTFs.
  • z/OS 2.2 with PTFs (an extended service contract is required).
  • z/VM 7.3.
  • z/VM 7.2.
  • z/VM 7.1.
  • z/VSE 6.2 with PTFs.
  • 21(st)Century Software VSE(n)6.3.
  • z/TPF 1.1 with PTFs.

CHPID type OSD with exploitation of two ports per CHPID:

  • z/OS 2.5 with PTFs.
  • z/OS 2.4 with PTFs.
  • z/OS 2.3 with PTFs.
  • z/OS 2.2 with PTFs (an extended service contract is required).
  • z/VM 7.3.
  • z/VM 7.2.
  • z/VM 7.1.
  • z/VSE 6.2 with PTFs.
  • 21(st)Century Software VSE(n)6.3.
  • z/TPF 1.1 with PTFs.
  • Linux on IBM Z - IBM plans to support:
    • SUSE Linux Enterprise Server: SLES 15 SP3 with service and SLES 12 SP5 with service.
    • Red Hat Enterprise Linux: RHEL 9.0 with service, RHEL 8.4 with service, and RHEL 7.9 with service.
    • Canonical: Ubuntu 20.04 LTS with service and Ubuntu 22.04 LTS with service.

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

  • z/OS 2.5 with PTFs.
  • z/OS 2.4 with PTFs.
  • z/OS 2.3 with PTFs.
  • z/OS 2.2 with PTFs (an extended service contract is required).
  • z/VM 7.3.
  • z/VM 7.2.
  • z/VM 7.1.
  • z/VSE 6.2 with PTFs.
  • 21(st)Century Software VSE(n)6.3.
  • z/TPF 1.1 with PTFs.
  • Linux on IBM Z - IBM plans to support:
    • SUSE Linux Enterprise Server: SLES 15 SP3 with service and SLES 12 SP5 with service.
    • Red Hat Enterprise Linux: RHEL 9.0 with service, RHEL 8.4 with service, and RHEL 7.9 with service.
    • Canonical: Ubuntu 20.04 LTS with service and Ubuntu 22.04 LTS with service.

Checksum offload for IPv6 packets (CHPID type OSD):

  • z/OS 2.5.
  • z/OS 2.4.
  • z/OS 2.3.
  • z/OS 2.2 (an extended service contract is required).
  • z/VM 7.3 for guest exploitation.
  • z/VM 7.2 for guest exploitation.
  • z/VM 7.1 for guest exploitation.
  • Linux on IBM Z - IBM plans to support:
    • SUSE Linux Enterprise Server: SLES 15 SP3 with service and SLES 12 SP5 with service.
    • Red Hat Enterprise Linux: RHEL 9.0 with service, RHEL 8.4 with service, and RHEL 7.9 with service.
    • Canonical: Ubuntu 20.04 LTS with service and Ubuntu 22.04 LTS with service.

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

  • z/OS 2.5.
  • z/OS 2.4.
  • z/OS 2.3.
  • z/OS 2.2 (an extended service contract is required).
  • z/VM 7.3 for guest exploitation.
  • z/VM 7.2 for guest exploitation.
  • z/VM 7.1 for guest exploitation.
  • Linux on IBM Z - IBM plans to support:
    • SUSE Linux Enterprise Server: SLES 15 SP3 with service and SLES 12 SP5 with service.
    • Red Hat Enterprise Linux: RHEL 9.0 with service, RHEL 8.4 with service, and RHEL 7.9 with service.
    • Canonical: Ubuntu 20.04 LTS with service and Ubuntu 22.04 LTS with service.

Large Send for IPv6 packets (CHPID type OSD):

  • z/OS 2.5.
  • z/OS 2.4.
  • z/OS 2.3.
  • z/OS 2.2 (an extended service contract is required).
  • z/VM 7.3 for guest exploitation.
  • z/VM 7.2 for guest exploitation.
  • z/VM 7.1 for guest exploitation.

CHPID type OSE supporting two or four ports per feature:

  • z/OS 2.5.
  • z/OS 2.4.
  • z/OS 2.3.
  • z/OS 2.2 (an extended service contract is required).
  • z/VM 7.3 for guest exploitation.
  • z/VM 7.2 for guest exploitation.
  • z/VM 7.1 for guest exploitation.
  • z/VSE 6.2 with PTFs.
  • 21(st)Century Software VSE(n)6.3.

Crypto Express8S (2 HSM) (#0908) Toleration, which treats Crypto Express8S cryptographic coprocessors and accelerators as Crypto Express7S coprocessors and accelerators, requires at a minimum:

  • z/VM 7.3 for guest exploitation.
  • z/VM 7.2 with PTFs for guest exploitation.
  • z/VM 7.1 with PTFs for guest exploitation.
  • z/VSE 6.2 with PTFs.
  • 21(st)Century Software VSE(n)6.3.
  • Linux on IBM Z - IBM plans to support:
    • SUSE Linux Enterprise Server: SLES 15 SP3 with service and SLES 12 SP5 with service.
    • Red Hat Enterprise Linux: RHEL 9.0 with service, RHEL 8.4 with service, and RHEL 7.9 with service.
    • Canonical: Ubuntu 20.04 LTS with service and Ubuntu 22.04 LTS with service.

Crypto Express8S (1 HSM) (#0909) Toleration requires at a minimum:

  • z/OS 2.5 with PTFs.
  • z/OS 2.4 with PTFs.
  • z/OS 2.3 with PTFs.
  • z/OS 2.2 with PTFs (an extended service contract is required).
  • z/VM 7.3 for guest exploitation.
  • z/VM 7.2 with PTFs for guest exploitation.
  • z/VM 7.1 with PTFs for guest exploitation.
  • z/VSE 6.2 with PTFs.
  • 21(st)Century Software VSE(n)6.3.
  • z/TPF 1.1 with PTFs.
  • Linux on IBM Z - IBM plans to support:
    • SUSE Linux Enterprise Server: SLES 15 SP3 with service and SLES 12 SP5 with service.
    • Red Hat Enterprise Linux: RHEL 9.0 with service, RHEL 8.4 with service, and RHEL 7.9 with service.
    • Canonical: Ubuntu 20.04 LTS with service and Ubuntu 22.04 LTS with service.

Crypto Express8S (1 HSM) (#0909) support of VISA Format Preserving Encryption requires at a minimum:

  • z/OS 2.5 with PTFs.
  • z/OS 2.4 with PTFs.
  • z/OS 2.3 with PTFs.
  • z/OS 2.2 with PTFs (an extended service contract is required).
  • z/VM 7.3 for guest exploitation.
  • z/VM 7.2 with PTFs for guest exploitation.
  • z/VM 7.1 with PTFs for guest exploitation.

Crypto Express8S (1 HSM) (#0909) Exploitation requires at a minimum:

  • z/OS 2.5 with PTFs.
  • z/OS 2.4 with Cryptographic Support for z/OS 2.2 -- z/OS 2.4 (HCR77D1) with PTFs..
  • z/OS 2.3 with Cryptographic Support for z/OS 2.2 -- z/OS 2.4 (HCR77D1) with PTFs.
  • z/OS 2.2 with Cryptographic Support for z/OS 2.2 -- z/OS 2.4 (HCR77D1) with PTFs (an extended service contract is required).
  • z/VM 7.3 for guest exploitation and exploitation within the z/VM TLS/SSL server.
  • z/VM 7.2 with PTFs for guest exploitation and exploitation within the z/VM TLS/SSL server.
  • z/VM 7.1 with PTFs for guest exploitation and exploitation within the z/VM TLS/SSL server.
  • Linux on IBM Z - IBM is working with its Linux distribution partners to provide support in future distribution releases.

Crypto Express8S (1 HSM) (#0909) support of PCI-HSM compliance requires at a minimum:

  • z/OS 2.5 with PTFs.
  • z/OS 2.4 with Cryptographic Support for z/OS 2.2 -- z/OS 2.4 (HCR77D1) with PTFs.
  • z/OS 2.3 with Cryptographic Support for z/OS 2.2 -- z/OS 2.4 (HCR77D1) with PTFs.
  • z/OS 2.2 with Cryptographic Support for z/OS 2.2 -- z/OS 2.4 (HCR77D1) with PTFs (an extended service contract is required).
  • z/VM 7.3 for guest exploitation.
  • z/VM 7.2 with PTFs for guest exploitation.
  • z/VM 7.1 with PTFs for guest exploitation.

10 GbE RoCE Express3 SR (#0440), 10 GbE RoCE Express3 LR (#0441) for Shared Memory Communications - Remote Direct Memory Access (SMC-R) requires at a minimum:

  • z/OS 2.5.
  • z/OS 2.4 with PTFs.
  • z/OS 2.3 with PTFs.
  • z/VM 7.3 for guest exploitation.
  • z/VM 7.2 with PTFs for guest exploitation.
  • z/VM 7.1 with PTFs for guest exploitation.
  • Linux on IBM Z - IBM plans to support:
    • SUSE Linux Enterprise Server: SLES 15 SP3 with service.
    • Red Hat Enterprise Linux: RHEL 9.0 with service and RHEL 8.4 with service.
    • Canonical: Ubuntu 20.04 LTS with service and Ubuntu 22.04 LTS with service.

25 GbE RoCE Express3 SR (#0452) and 25 GbE RoCE Express3 LR (#0453) for Shared Memory Communications - Remote Direct Memory Access (SMC-R) requires at a minimum:

  • z/OS 2.5.
  • z/OS 2.4 with PTFs.
  • z/OS 2.3 with PTFs.
  • z/VM 7.3 for guest exploitation.
  • z/VM 7.2 with PTFs for guest exploitation.
  • z/VM 7.1 with PTFs for guest exploitation.
  • Linux on IBM Z - IBM plans to support:
    • SUSE Linux Enterprise Server: SLES 15 SP3 with service.
    • Red Hat Enterprise Linux: RHEL 9.0 with service and RHEL 8.4 with service.
    • Canonical: Ubuntu 20.04 LTS with service and Ubuntu 22.04 LTS with service.

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

  • z/VM 7.3 for guest exploitation.
  • z/VM 7.2 with PTFs for guest exploitation.
  • z/VM 7.1 with PTFs for guest exploitation.
  • Linux on IBM Z - IBM plans to support:
    • SUSE Linux Enterprise Server: SLES 15 SP3 with service.
    • Red Hat Enterprise Linux: RHEL 9.0 with service and RHEL 8.4 with service.
    • Canonical: Ubuntu 20.04 LTS with service and Ubuntu 22.04 LTS with service.

25 GbE RoCE Express3 SR (#0452)and 25 GbE RoCE Express3 LR (#0453) for Ethernet communications (which does not require a peer OSA) including Single Root I/O Virtualization (SR-IOV) requires at a minimum:

  • z/VM 7.3 for guest exploitation.
  • z/VM 7.2 with PTFs for guest exploitation.
  • z/VM 7.1 with PTFs for guest exploitation.
  • Linux on IBM Z - IBM plans to support:
    • SUSE Linux Enterprise Server: SLES 15 SP3 with service.
    • Red Hat Enterprise Linux: RHEL 9.0 with service and RHEL 8.4 with service,.
    • Canonical: Ubuntu 20.04 LTS with service and Ubuntu 22.04 LTS with service.

10 GbE RoCE Express3 SR (#0440), 10 GbE RoCE Express3 LR (#0441) for TCP/IP requires at a minimum:

  • z/VM 7.3 for guest exploitation.
  • z/VM 7.2 with PTFs for guest exploitation.
  • z/VM 7.1 with PTFs for guest exploitation.
  • Linux on IBM Z - IBM plans to support:
    • SUSE Linux Enterprise Server: SLES 15 SP3 with service .
    • Red Hat Enterprise Linux: RHEL 9.0 with service and RHEL 8.4 with service.
    • Canonical: Ubuntu 20.04 LTS with service and Ubuntu 22.04 LTS with service.

25 GbE RoCE Express3 SR (#0452) and 25 GbE RoCE Express3 LR (#0453) for TCP/IP requires at a minimum:

  • z/VM 7.3 for guest exploitation.
  • z/VM 7.2 with PTFs for guest exploitation.
  • z/VM 7.1 with PTFs for guest exploitation.
  • Linux on IBM Z - IBM plans to support:
    • SUSE Linux Enterprise Server: SLES 15 SP3 with service .
    • Red Hat Enterprise Linux: RHEL 9.0 with service and RHEL 8.4 with service.
    • Canonical: Ubuntu 20.04 LTS with service and Ubuntu 22.04 LTS with service.

IBM Integrated Coupling Adapter Fanout (ICA SR1.1) (#0176) requires at a minimum:

  • z/OS 2.5.
  • z/OS 2.4.
  • z/OS 2.3.
  • z/OS 2.2 (an extended service contract is required).
  • z/VM 7.3 to define, modify, and delete CHPID type CS5 when z/VM is the controlling LPAR for dynamic I/O.
  • z/VM 7.2 to define, modify, and delete CHPID type CS5 when z/VM is the controlling LPAR for dynamic I/O.
  • z/VM 7.1 to define, modify, and delete CHPID type CS5 when z/VM is the controlling LPAR for dynamic I/O.

Support for 384 Coupling CHPIDs, 96 physical ICA SR coupling links, and 64 ICP internal coupling channels requires at a minimum:

  • z/OS 2.5 with PTFs.
  • z/OS 2.4 with PTFs.
  • z/OS 2.3 with PTFs.
  • z/OS 2.2 with PTFs (an extended service contract is required).

Support for CFLEVEL 25 coupling facility enhancements requires at a minimum:

  • z/OS 2.5 with PTFs.
  • z/OS 2.4 with PTFs.
  • z/OS 2.3 with PTFs.
  • z/OS 2.2 with PTFs (an extended service contract is required).
  • z/VM 7.3 for virtual coupling facility guest exploitation.
  • z/VM 7.2 for virtual coupling facility guest exploitation.
  • z/VM 7.1 for virtual coupling facility guest exploitation.

Coupling Express2 LR (#0434) requires at a minimum:

  • z/OS 2.5.
  • z/OS 2.4 with PTFs.
  • z/OS 2.3 with PTFs.
  • z/OS 2.2 with PTFs (an extended service contract is required).
  • z/VM 7.3 to define, modify, and delete CL5 CHPID types when z/VM is the controlling LPAR for dynamic I/O.
  • z/VM 7.2 with PTFs to define, modify, and delete CL5 CHPID types when z/VM is the controlling LPAR for dynamic I/O.
  • z/VM 7.1 with PTFs to define, modify, and delete CL5 CHPID types when z/VM is the controlling LPAR for dynamic I/O.

zHyperLink Express1.1 (#0451) Reads support requires at a minimum:

  • z/OS 2.5.
  • z/OS 2.4 with PTFs.
  • z/OS 2.3 with PTFs.
  • z/OS 2.2 with PTFs (an extended service contract is required).
  • Db2 11 plus PTFs.

zHyperLink Express1.1 (#0451) Writes support requires at a minimum:

  • z/OS 2.5.
  • z/OS 2.4 with PTFs.
  • z/OS 2.3 with PTFs.
  • Db2 12 plus PTFs.

CPU Measurement Facility requires at a minimum:

  • z/OS 2.5 with PTFs.
  • z/OS 2.4 with PTFs.
  • z/OS 2.3 with PTFs.
  • z/VM 7.3.
  • z/VM 7.2 with PTFs.
  • z/VM 7.1 with PTFs.
  • Linux on IBM Z - IBM plans to support:
    • SUSE Linux Enterprise Server: SLES 15 SP3 with service and SLES 12 SP5 with service.
    • Red Hat Enterprise Linux: RHEL 9.0 with service, RHEL 8.4 with service, and RHEL 7.9 with service.
    • Canonical: Ubuntu 20.04 LTS with service and Ubuntu 22.04 LTS with service.

    Note: IBM is working with its Linux distribution partners to provide support for new IBM z16 measurements in future distribution releases.

Quantum-safe API support requires at a minimum:

  • z/OS 2.5 with PTFs.
  • z/OS 2.4 with Cryptographic Support for z/OS 2.2 -- z/OS 2.4 (HCR77D1) with PTFs.
  • z/OS 2.3 with Cryptographic Support for z/OS 2.2 -- z/OS 2.4 (HCR77D1) with PTFs.
  • z/OS 2.2 with Cryptographic Support for z/OS 2.2 -- z/OS 2.4 (HCR77D1) with PTFs (an extended service contract is required).
  • z/VM 7.3 for guest exploitation.
  • z/VM 7.2 with PTFs for guest exploitation.
  • z/VM 7.1 with PTFs for guest exploitation.

IBM Fibre Channel Endpoint Security requires at a minimum:

  • z/OS 2.5.
  • z/OS 2.4 with PTFs.
  • z/OS 2.3 with PTFs.
  • z/OS 2.2 with PTFs (an extended service contract is required).
  • z/VM 7.3.
  • z/VM 7.2 with PTFs.
  • z/VM 7.1 with PTFs.
  • z/VSE 6.2 with PTFs.
  • 21(st)Century Software VSE(n)6.3.
  • Linux on IBM Z - IBM plans to support:
    • SUSE Linux Enterprise Server: SLES 15 SP3 with service.
    • Red Hat RHEL 9.0 with service and Red Hat RHEL 8.4 with service.
    • Canonical: Ubuntu 21.04 LTS, or later.

Secure Execution for Linux requires support in the KVM host and the KVM guest, at a minimum:

  • IBM supports running the following Linux on IBM Z distributions as a KVM host on IBM z16:
    • SUSE Linux Enterprise Server: SLES 15 SP3 with service.
    • Red Hat Enterprise Linux: RHEL 9.0 with service and RHEL 8.4 with service.
    • Canonical: Ubuntu 20.04 LTS with service and Ubuntu 22.04 LTS with service.
  • IBM supports running the following Linux on IBM Z distributions as a KVM guest on IBM z16:
    • SUSE Linux Enterprise Server: SLES 15 SP3 with service and SLES 12 SP5 with service.
    • Red Hat Enterprise Linux: RHEL 9.0 with service, RHEL 8.4 with service, and RHEL 7.9 with service.
    • Canonical: Ubuntu 20.04 LTS with service and Ubuntu 22.04 LTS with service.

System Recovery Boost Resiliency enhancements for IBM z16 require at a minimum:

  • z/OS 2.5 with PTFs.
  • z/OS 2.4 with PTFs.
  • All z/OS PTFs associated with System Recovery Boost are identified with the SMP/E FIXCAT of IBM.Function.SystemRecoveryBoost.

IBM Hardware Management Console Enhancements require at a minimum:

  • z/OS 2.5 with APAR OA60351.

AI on IBM Z requires at a minimum:

  • z/OS 2.5.
  • z/OS 2.4 with PTFs.
  • z/VM 7.3 for Guest Exploitation.
  • z/VM 7.2 with PTFs for Guest Exploitation.
  • z/VM 7.1 with PTFs for Guest Exploitation.
  • Watson Machine Learning for z/OS 2.
  • Watson Machine Learning for z/OS 2.1.
  • Red Hat OpenShift Container Platform 4.10.
  • IzODA 1.1.0.

IBM Z Integrated Accelerator for AI requires at a minimum:

  • z/OS 2.5 with PTFs.
  • z/OS 2.4 with PTFs.
  • Linux on IBM Z - IBM is working with its Linux distribution partners to provide the zDNN library (available at: https://github.com/IBM/zDNN) for future distribution releases.

IBM Cloud Infrastructure Center requires at a minimum:

  • As a managed hypervisor one of the following:
    • z/VM 7.1, or later.
    • KVM based on Red Hat Enterprise Linux (RHEL) 8. 4 with service.
  • As a host environment on z/VM or Red Hat KVM one of the following:
    • RHEL 8.4 with service.

Red Hat OpenShift Container Platform 4.10 requires at a minimum virtual machines based on one of the following:

  • z/VM 7.1, or later.
  • KVM based on Red Hat Enterprise Linux (RHEL) 8.4 with service

IBM Cloud Paks require at a minimum:

  • Red Hat OpenShift Container Platform 4.10.

IBM Cloud Pak for Data on IBM Z requires at a minimum:

  • Red Hat OpenShift Container Platform 4.10.

IBM Enterprise Key Management Foundation - Web Edition 2.1 requires at a minimum:

  • WebSphere Liberty 21.0.0.3.
  • Java SDK80 SR6 FP26 with APAR PH34993.
  • z/OS 2.5.
  • z/OS 2.4.
  • Db2 12.
  • IBM Crypto Express Card (CEX).


Back to topBack to top

Publications

Top rule

The following publications are available now in the "Library" section of Resource Link:

Title                                                          Order
                                                               number
-------------------------------------------------------------- ---------
3931 Installation Manual for Physical Planning (IMPP)          GC28-7015
PR/SM Planning Guide                                           SB10-7178
IOCP User's Guide for ICP IOCP                                 SB10-7177
Planning for Fiber Optic Links (FICON/FCP, Coupling Links,     GA23-1409
OSA, and zHyperLink Express)

The following publication is shipped with the product:

Title                    Order
                         number
------------------------ ---------
3931 Installation Manual GC28-7017

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
------------------------------------------------------------ ---------
3931 Safety Inspection                                       GC28-7014
Service Guide for TKE Workstations (Version 7.0)             GC28-7020
Systems Safety Notices                                       G229-9054
IBM Important Notices                                        G229-9056
Statement of Limited Warranty Part 3 - Warranty Information  GC28-7013
License Agreement for Machine Code                           SC28-6872
License Agreement for Machine Code Addendum for Cryptography GC27-2635
Systems Environmental Notices and User Guide                 Z125-5823

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

Title                                                          Order
                                                               number
-------------------------------------------------------------- ---------
3931 Service Guide                                             GC28-7018
3931 Parts Catalog                                             GC28-7019
Service Guide for 2461 Hardware Management Console             GC28-7021
Service Guide for 2461 Support Element                         GC28-7022
SNMP Application Programming Interfaces                        SB10-7179
Capacity on Demand User's Guide                                SC28-7025
CHPID Mapping Tool User's Guide                                GC28-7024
Hardware Management Console Web Services API (V2.16.0)         SC27-2642
IBM Dynamic Partition Manager (DPM) Guide                      SB10-7182
Secure Service Container User's Guide                          SC28-7028
Stand-Alone IOCP User's Guide                                  SB10-7180
FICON CTC Reference                                            SB10-7181
Maintenance Information for Fiber Optics (FICON/FCP, Coupling  SY27-7697
Links, OSA, and zHyperLink Express)
Integrating the HMC's Broadband RSF into your Enterprise       SC28-7026
Hardware Management Console Security                           SC28-7027
Remote Code Load for IBM Z Firmware                            SC28-7044
SCSI IPL -- Machine Loader Messages                            SC28-7029
OSA-Express Customer's Guide and Reference                     SA22-7935
OSA/SF on the Hardware Management Console                      SC14-7580
OSA Integrated Console Controller User's Guide                 SC27-9003

Resource Link

Publications for IBM Z can be obtained at Resource Link.

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.16.0) will be available from IBM Resource Link and the consoles.

You can also find HMC videos at IBM Z Hardware Management Console Videos.

IBM Documentation

IBM Documentation provides a modernized user experience and makes it easier to find IBM product information for systems hardware, operating systems, and server software. Through a consistent framework, you can efficiently find information and personalize your access. The IBM Z publications are referenced at IBM Documentation.

The following Redbooks publications are available now. To order, contact your IBM representative.

Title                          Order number
------------------------------ ------------
IBM z16 Technical Introduction SG24-8950-00
IBM z16 Technical Guide        SG24-8951-00
IBM z16 Configuration Setup    SG24-8960-00
IBM z16 Connectivity Handbook  SG24-5444-21
IBM Z Functional Matrix        REDP-5157-06

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

For other IBM Redbooks publications, go to the main IBM Redbooks 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

Top rule

Features - No charge Features - No charge Feature availability matrix Feature availability matrix
Features - Chargeable Features - Chargeable Feature descriptions 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 Number Title
-------------- ---------------------
0389           Returning MT Digit 1
0390           Returning MT Digit 2
0391           Returning MT Digit 3
0392           Returning MT Digit 4
0393           Plant of MFG Digit 1
0394           Plant of MFG Digit 2
0395           Serial Number Digit 1
0396           Serial Number Digit 2
0397           Serial Number Digit 3
0398           Serial Number Digit 4
0399           Serial Number Digit 5

Features - Chargeable

Feature Title
Number
------- ---------------------------------
0001    MTU 1-D
0002    MTU 100 -D
0003    MTU 1 -V
0004    MTU 100 -V
0005    GTU 1 - D
0006    GTU 100 - D
0007    GTU 1 -V
0008    GTU 100 -V
0009    GTU 1000 - D
0010    GTU 1000 - V
0012    Exchange Pgm Machine
0013    Exchange Pgm Machine + Covers
0014    Migration Offering Machine
0015    Blue Letter Internal
0032    Non RSF On/Off CoD
0033    Serv Docs Optional Print
0034    OSA-ICC 3215 Enablement
0035    RFID Tag
0036    RFID Tag
0057    TKE Rack Mount
0058    TKE
0093    OEM Generic Indicator
0099    WWPN Persistence
0115    Secure Execution for Linux
0129    IBM Z HW Mgmt Appliance
0137    Fanout Airflow PCIe
0144    TKE Tower
0145    TKE Rack
0156    TKE Rack KMM
0175    PCIe+ fanout
0176    ICA SR1.1
0190    Client Must Provide TKE KMM
0201    3906 w/o TEIO & w/o HtR
0202    3906 w/TEIO & w/o HtR
0203    3906 w/o TEIO & w/HtR
0204    3906 w/TEIO & w/HtR
0233    TKE Rack
0234    TKE Tower
0250    DPM
0253    TFP Monthly Sub 1 MSU
0254    TFP Monthly Sub 100 MSU
0255    TFP Monthly Sub 10000 MSU
0256    Prepaid TFP Sub 1 MSU
0257    Prepaid TFP Sub 100 MSU
0258    Prepaid TFP Sub 10000 MSU
0259    TFP Subscription Months
0260    TFP Hourly 1 MSU
0261    TFP Hourly 100 MSU
0262    TFP Hourly 10000 MSU
0263    TFP Daily 1 MSU
0264    TFP Daily 100 MSU
0265    TFP Daily 10000 MSU
0317    Flexible Cap 1 Unit
0318    Flexible Cap 100 Units
0319    Flexible Cap 10000 Units
0320    Flexible Cap IFL
0321    Flexible Cap ICF
0322    Flexible Cap zIIP
0376    Flexible Capacity Record
0377    Flexible Cap Term Years
0378    Flexible Capacity 1 Unit Year
0379    Flexible Capacity 100 Units Year
0380    Flexible Capacity 10000Units Year
0381    Flexible Cap IFL Year
0382    Flexible Cap 100 IFL Year
0383    Flexible Cap ICF Year
0384    Flexible Cap 100 ICF Year
0385    Flexible Cap zIIP Year
0386    Flexible Cap 100 zIIP Year
0421    PCIe Interconnect Gen4
0434    Coupling Express2 LR
0440    10GbE RoCE Express3 SR
0441    10GbE RoCE Express3 LR
0451    zHyperLink Express1.1
0452    25GbE RoCE Express3 SR
0453    25GbE RoCE Express3 LR
0454    OSA-Express7S GbE LX 1.2
0455    OSA-Express7S GbE SX 1.2
0456    OSA-Express7S 10 GbE LR 1.2
0457    OSA-Express7S 10 GbE SR 1.2
0458    OSA-Express7S 1000BASE-T 1.2
0459    OSA-Express7S 25 GbE SR 1.2
0460    OSA-Express7S 25 GbE LR 1.2
0461    FICON Express32S LX
0462    FICON Express32S SX
0508    Model A01
0546    8561 RCU A Frame w/o Ht Red
0547    8561 RCU B Frame w/o Ht Red
0548    8561 RCU C Frame w/o Ht Red
0549    8561 RCU Z Frame w/o Ht Red
0550    8561 RCU A Frame w/ Ht Red
0551    8561 RCU B Frame w/ Ht Red
0552    8561 RCU C Frame w/ Ht Red
0553    8561 RCU Z Frame w/ Ht Red
0554    8561 WCU A Frame w/o Ht Red
0555    8561 WCU B Frame w/o Ht Red
0556    8561 WCU C Frame w/o Ht Red
0557    8561 WCU Z Frame w/o Ht Red
0558    8561 WCU A Frame w/ Ht Red
0559    8561 WCU B Frame w/ Ht Red
0560    8561 WCU C Frame w/ Ht Red
0561    8561 WCU Z Frame w/ Ht Red
0642    CPC PSU
0644    IBM Virtual Flash Memory
0645    200-208V 30/60A, 3 Ph PDU
0646    380-415V 32A, 3 Ph WYE PDU
0647    Ethernet Switch
0648    Bulk Power Assembly
0667    Max39
0668    Max82
0669    Max125
0670    Max168
0671    Max200
0843    32GB USB Load Media
0846    No Physical Media
0848    32GB USB Backup Media
0851    4770 Crypto Adapter
0882    TKE 10.0 LIC
0891    TKE Smart Card Reader
0900    TKE addl smart cards
0908    Crypto Express8S (2 HSM)
0909    Crypto Express8S (1 HSM)
0983    US TAA Compliance Indicator
1021    STP Enablement
1022    EMEA Special Operations
1121    VFM/Flash Converted, 1to1
1122    VFM/Flash Converted, 1to2
1123    VFM/Flash Converted, 1to3
1146    Endpoint Security Enablement
1746    32 GB Mem DIMM (8/feat)
1747    64 GB Mem DIMM (8/feat)
1748    128 GB Mem DIMM (8/feat)
1749    256 GB Mem DIMM (8/feat)
1750    LICCC Ship Via Net Ind
1955    CP4
1956    CP5
1957    CP6
1958    CP7
1959    IFL
1960    ICF
1961    zIIP
1962    Unassigned IFL
1963    SAP (optional)
1964    32GB Flex Memory
1965    64GB Flex Memory
1966    256GB Flex Memory
1967    64GB VFM Flex Memory
1968    32GB Memory Cap Incr
1969    64GB Memory Cap Incr
1970    256GB Memory Cap Incr
1971    32GB Converted Mem
1972    64GB Converted Mem
1973    256GB Converted Mem
1974    Unassigned ICF
1975    Unassigned zIIP
2825    512 GB Memory
2826    576 GB Memory
2827    640 GB Memory
2828    704 GB Memory
2829    768 GB Memory
2830    896 GB Memory
2831    1024 GB Memory
2832    1152 GB Memory
2833    1280 GB Memory
2834    1408 GB Memory
2835    1536 GB Memory
2836    1664 GB Memory
2837    1792 GB Memory
2838    1920 GB Memory
2839    2048 GB Memory
2840    2304 GB Memory
2841    2560 GB Memory
2842    2816 GB Memory
2843    3072 GB Memory
2844    3328 GB Memory
2845    3584 GB Memory
2846    3840 GB Memory
2847    4352 GB Memory
2848    4864 GB Memory
2849    5376 GB Memory
2850    5888 GB Memory
2851    6400 GB Memory
2852    6912 GB Memory
2853    7424 GB Memory
2854    7936 GB Memory
2855    8448 GB Memory
2856    8960 GB Memory
2857    9472 GB Memory
2858    9984 GB Memory
2859    10496GB Memory
2860    11008 GB Memory
2861    11520 GB Memory
2862    12032 GB Memory
2863    12544 GB Memory
2864    13056 GB Memory
2865    13568 GB Memory
2866    14080 GB Memory
2867    14592 GB Memory
2868    15104 GB Memory
2869    15616 GB Memory
2870    16128 GB Memory
2871    16640 GB Memory
2872    17152 GB Memory
2873    18176 GB Memory
2874    19200 GB Memory
2875    20224 GB Memory
2876    21248 GB Memory
2877    22272 GB Memory
2878    23296 GB Memory
2879    24320 GB Memory
2880    25344 GB Memory
2881    26368 GB Memory
2882    27392 GB Memory
2883    28416 GB Memory
2884    29440 GB Memory
2885    30464 GB Memory
2886    31488 GB Memory
2887    32512 GB Memory
2888    34560 GB Memory
2889    36608 GB Memory
2890    38656 GB Memory
2891    40704 GB Memory
2981    CPC1 Reserve
2982    CPC2 Reserve
3003    Balanced Power Plan Ahead
3017    BPR Pair
3100    Lift Tool Kit
3101    Extension Ladder
3393    Fill and Drain Kit
3863    CPACF Enablement
4023    PCIe+ I/O Drawer
4040    A Frame Radiator
4041    B Frame Radiator
4042    B Frame No Cooling
4043    Z Frame
4044    C Frame
5144    701 Capacity Marker
5145    702 Capacity Marker
5146    703 Capacity Marker
5147    704 Capacity Marker
5148    705 Capacity Marker
5149    706 Capacity Marker
5150    707 Capacity Marker
5151    708 Capacity Marker
5152    709 Capacity Marker
5153    710 Capacity Marker
5154    711 Capacity Marker
5155    712 Capacity Marker
5156    713 Capacity Marker
5157    714 Capacity Marker
5158    715 Capacity Marker
5159    716 Capacity Marker
5160    717 Capacity Marker
5161    718 Capacity Marker
5162    719 Capacity Marker
5163    720 Capacity Marker
5164    721 Capacity Marker
5165    722 Capacity Marker
5166    723 Capacity Marker
5167    724 Capacity Marker
5168    725 Capacity Marker
5169    726 Capacity Marker
5170    727 Capacity Marker
5171    728 Capacity Marker
5172    729 Capacity Marker
5173    730 Capacity Marker
5174    731 Capacity Marker
5175    732 Capacity Marker
5176    733 Capacity Marker
5177    734 Capacity Marker
5178    735 Capacity Marker
5179    736 Capacity Marker
5180    737 Capacity Marker
5181    738 Capacity Marker
5182    739 Capacity Marker
5183    740 Capacity Marker
5184    741 Capacity Marker
5185    742 Capacity Marker
5186    743 Capacity Marker
5187    744 Capacity Marker
5188    745 Capacity Marker
5189    746 Capacity Marker
5190    747 Capacity Marker
5191    748 Capacity Marker
5192    749 Capacity Marker
5193    750 Capacity Marker
5194    751 Capacity Marker
5195    752 Capacity Marker
5196    753 Capacity Marker
5197    754 Capacity Marker
5198    755 Capacity Marker
5199    756 Capacity Marker
5200    757 Capacity Marker
5201    758 Capacity Marker
5202    759 Capacity Marker
5203    760 Capacity Marker
5204    761 Capacity Marker
5205    762 Capacity Marker
5206    763 Capacity Marker
5207    764 Capacity Marker
5208    765 Capacity Marker
5209    766 Capacity Marker
5210    767 Capacity Marker
5211    768 Capacity Marker
5212    769 Capacity Marker
5213    770 Capacity Marker
5214    771 Capacity Marker
5215    772 Capacity Marker
5216    773 Capacity Marker
5217    774 Capacity Marker
5218    775 Capacity Marker
5219    776 Capacity Marker
5220    777 Capacity Marker
5221    778 Capacity Marker
5222    779 Capacity Marker
5223    780 Capacity Marker
5224    781 Capacity Marker
5225    782 Capacity Marker
5226    783 Capacity Marker
5227    784 Capacity Marker
5228    785 Capacity Marker
5229    786 Capacity Marker
5230    787 Capacity Marker
5231    788 Capacity Marker
5232    789 Capacity Marker
5233    790 Capacity Marker
5234    791 Capacity Marker
5235    792 Capacity Marker
5236    793 Capacity Marker
5237    794 Capacity Marker
5238    795 Capacity Marker
5239    796 Capacity Marker
5240    797 Capacity Marker
5241    798 Capacity Marker
5242    799 Capacity Marker
5243    7A0 Capacity Marker
5244    7A1 Capacity Marker
5245    7A2 Capacity Marker
5246    7A3 Capacity Marker
5247    7A4 Capacity Marker
5248    7A5 Capacity Marker
5249    7A6 Capacity Marker
5250    7A7 Capacity Marker
5251    7A8 Capacity Marker
5252    7A9 Capacity Marker
5253    7B0 Capacity Marker
5254    7B1 Capacity Marker
5255    7B2 Capacity Marker
5256    7B3 Capacity Marker
5257    7B4 Capacity Marker
5258    7B5 Capacity Marker
5259    7B6 Capacity Marker
5260    7B7 Capacity Marker
5261    7B8 Capacity Marker
5262    7B9 Capacity Marker
5263    7C0 Capacity Marker
5264    7C1 Capacity Marker
5265    7C2 Capacity Marker
5266    7C3 Capacity Marker
5267    7C4 Capacity Marker
5268    7C5 Capacity Marker
5269    7C6 Capacity Marker
5270    7C7 Capacity Marker
5271    7C8 Capacity Marker
5272    7C9 Capacity Marker
5273    7D0 Capacity Marker
5274    7D1 Capacity Marker
5275    7D2 Capacity Marker
5276    7D3 Capacity Marker
5277    7D4 Capacity Marker
5278    7D5 Capacity Marker
5279    7D6 Capacity Marker
5280    7D7 Capacity Marker
5281    7D8 Capacity Marker
5282    7D9 Capacity Marker
5283    7E0 Capacity Marker
5284    7E1 Capacity Marker
5285    7E2 Capacity Marker
5286    7E3 Capacity Marker
5287    7E4 Capacity Marker
5288    7E5 Capacity Marker
5289    7E6 Capacity Marker
5290    7E7 Capacity Marker
5291    7E8 Capacity Marker
5292    7E9 Capacity Marker
5293    7F0 Capacity Marker
5294    7F1 Capacity Marker
5295    7F2 Capacity Marker
5296    7F3 Capacity Marker
5297    7F4 Capacity Marker
5298    7F5 Capacity Marker
5299    7F6 Capacity Marker
5300    7F7 Capacity Marker
5301    7F8 Capacity Marker
5302    7F9 Capacity Marker
5303    7G0 Capacity Marker
5304    7G1 Capacity Marker
5305    7G2 Capacity Marker
5306    7G3 Capacity Marker
5307    7G4 Capacity Marker
5308    7G5 Capacity Marker
5309    7G6 Capacity Marker
5310    7G7 Capacity Marker
5311    7G8 Capacity Marker
5312    7G9 Capacity Marker
5313    7H0 Capacity Marker
5314    7H1 Capacity Marker
5315    7H2 Capacity Marker
5316    7H3 Capacity Marker
5317    7H4 Capacity Marker
5318    7H5 Capacity Marker
5319    7H6 Capacity Marker
5320    7H7 Capacity Marker
5321    7H8 Capacity Marker
5322    7H9 Capacity Marker
5323    7i0 Capacity Marker
5324    7i1 Capacity Marker
5325    7i2 Capacity Marker
5326    7i3 Capacity Marker
5327    7i4 Capacity Marker
5328    7i5 Capacity Marker
5329    7i6 Capacity Marker
5330    7i7 Capacity Marker
5331    7i8 Capacity Marker
5332    7i9 Capacity Marker
5333    7J0 Capacity Marker
5334    7J1 Capacity Marker
5335    7J2 Capacity Marker
5336    7J3 Capacity Marker
5337    7J4 Capacity Marker
5338    7J5 Capacity Marker
5339    7J6 Capacity Marker
5340    7J7 Capacity Marker
5341    7J8 Capacity Marker
5342    7J9 Capacity Marker
5343    7K0 Capacity Marker
5344    601 Capacity Marker
5345    602 Capacity Marker
5346    603 Capacity Marker
5347    604 Capacity Marker
5348    605 Capacity Marker
5349    606 Capacity Marker
5350    607 Capacity Marker
5351    608 Capacity Marker
5352    609 Capacity Marker
5353    610 Capacity Marker
5354    611 Capacity Marker
5355    612 Capacity Marker
5356    613 Capacity Marker
5357    614 Capacity Marker
5358    615 Capacity Marker
5359    616 Capacity Marker
5360    617 Capacity Marker
5361    618 Capacity Marker
5362    619 Capacity Marker
5363    620 Capacity Marker
5364    621 Capacity Marker
5365    622 Capacity Marker
5366    623 Capacity Marker
5367    624 Capacity Marker
5368    625 Capacity Marker
5369    626 Capacity Marker
5370    627 Capacity Marker
5371    628 Capacity Marker
5372    629 Capacity Marker
5373    630 Capacity Marker
5374    631 Capacity Marker
5375    632 Capacity Marker
5376    633 Capacity Marker
5377    634 Capacity Marker
5378    635 Capacity Marker
5379    636 Capacity Marker
5380    637 Capacity Marker
5381    638 Capacity Marker
5382    639 Capacity Marker
5409    400 Capacity Marker
5410    401 Capacity Marker
5411    402 Capacity Marker
5412    403 Capacity Marker
5413    404 Capacity Marker
5414    405 Capacity Marker
5415    406 Capacity Marker
5416    407 Capacity Marker
5417    408 Capacity Marker
5418    409 Capacity Marker
5419    410 Capacity Marker
5420    411 Capacity Marker
5421    412 Capacity Marker
5422    413 Capacity Marker
5423    414 Capacity Marker
5424    415 Capacity Marker
5425    416 Capacity Marker
5426    417 Capacity Marker
5427    418 Capacity Marker
5428    419 Capacity Marker
5429    420 Capacity Marker
5430    421 Capacity Marker
5431    422 Capacity Marker
5432    423 Capacity Marker
5433    424 Capacity Marker
5434    425 Capacity Marker
5435    426 Capacity Marker
5436    427 Capacity Marker
5437    428 Capacity Marker
5438    429 Capacity Marker
5439    430 Capacity Marker
5440    431 Capacity Marker
5441    432 Capacity Marker
5442    433 Capacity Marker
5443    434 Capacity Marker
5444    435 Capacity Marker
5445    436 Capacity Marker
5446    437 Capacity Marker
5447    438 Capacity Marker
5448    439 Capacity Marker
5449    501 Capacity Marker
5450    502 Capacity Marker
5451    503 Capacity Marker
5452    504 Capacity Marker
5453    505 Capacity Marker
5454    506 Capacity Marker
5455    507 Capacity Marker
5456    508 Capacity Marker
5457    509 Capacity Marker
5458    510 Capacity Marker
5459    511 Capacity Marker
5460    512 Capacity Marker
5461    513 Capacity Marker
5462    514 Capacity Marker
5463    515 Capacity Marker
5464    516 Capacity Marker
5465    517 Capacity Marker
5466    518 Capacity Marker
5467    519 Capacity Marker
5468    520 Capacity Marker
5469    521 Capacity Marker
5470    522 Capacity Marker
5471    523 Capacity Marker
5472    524 Capacity Marker
5473    525 Capacity Marker
5474    526 Capacity Marker
5475    527 Capacity Marker
5476    528 Capacity Marker
5477    529 Capacity Marker
5478    530 Capacity Marker
5479    531 Capacity Marker
5480    532 Capacity Marker
5481    533 Capacity Marker
5482    534 Capacity Marker
5483    535 Capacity Marker
5484    536 Capacity Marker
5485    537 Capacity Marker
5486    538 Capacity Marker
5487    539 Capacity Marker
5827    FQC Bracket & Mounting Hdw
6798    Total SRB Months Ordered
6799    Total SRB Years Ordered
6802    Sys Recovery Boost Record
6803    PRC Tokens
6804    PRC Tokens Alteration
6805    Additional CBU Test
6806    PRC 1 MSU day
6807    PRC 100 MSU days
6808    PRC 10000 MSU days
6809    PRC 1 IFL day
6810    PRC 100 IFL days
6811    PRC 1 ICF day
6812    PRC 100 ICF days
6813    PRC 1 zIIP day
6814    PRC 100 zIIP days
6815    PRC 1 SAP day
6816    PRC 100 SAP days
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
6835    OPO Sales Flag
6836    OPO Sales Flag-Alteration
7805    Flex Cap Perpetual License
7806    Flexible Cap Term License
7816    Top Exit Cabling w/o Tophat
7898    Top Exit Cabling w/Top Hat
7899    Bottom Exit Cabling
7946    30A/400V 3Ph Wye w/Hubbell
7947    32A/380-415V 3Ph Wye
7948    32A/380-415V 3Ph Wye LSZH
7954    60A/250V w/Hubbell
7955    60A/250V w/Cut End
7956    30A/400V Hubbell
7957    32A/380-415V Cut End
7958    32A/380-415V Cut End LSZH
7959    30A/480V Hubbell
7965    60A/250V w/Cut End LSZH
7971    60A/250V 3Ph w/Hubbell
7972    60A/250V 3Ph w/Cut End
7973    60A/250V w/Cut End LSZH
7998    Non Raised Floor Support
8014    19in Earthquake Kit, RF
8015    19in Earthquake Kit, NRF
8023    Zero-Way Processor CP4
8024    1-Way Processor CP4
8025    2-Way Processor CP4
8026    3-Way Processor CP4
8027    4-Way Processor CP4
8028    5-Way Processor CP4
8029    6-Way Processor CP4
8030    7-Way Processor CP4
8031    8-Way Processor CP4
8032    9-Way Processor CP4
8033    10-Way Processor CP4
8034    11-Way Processor CP4
8035    12-Way Processor CP4
8036    13-Way Processor CP4
8037    14-Way Processor CP4
8038    15-Way Processor CP4
8039    16-Way Processor CP4
8040    17-Way Processor CP4
8041    18-Way Processor CP4
8042    19-Way Processor CP4
8043    20-Way Processor CP4
8044    21-Way Processor CP4
8045    22-Way Processor CP4
8046    23-Way Processor CP4
8047    24-Way Processor CP4
8048    25-Way Processor CP4
8049    26-Way Processor CP4
8050    27-Way Processor CP4
8051    28-Way Processor CP4
8052    29-Way Processor CP4
8053    30-Way Processor CP4
8054    31-Way Processor CP4
8055    32-Way Processor CP4
8056    33-Way Processor CP4
8057    34-Way Processor CP4
8058    35-Way Processor CP4
8059    36-Way Processor CP4
8060    37-Way Processor CP4
8061    38-Way Processor CP4
8062    39-Way Processor CP4
8332    1-Way Processor CP5
8333    2-Way Processor CP5
8334    3-Way Processor CP5
8335    4-Way Processor CP5
8336    5-Way Processor CP5
8337    6-Way Processor CP5
8338    7-Way Processor CP5
8339    8-Way Processor CP5
8340    9-Way Processor CP5
8341    10-Way Processor CP5
8342    11-Way Processor CP5
8343    12-Way Processor CP5
8344    13-Way Processor CP5
8345    14-Way Processor CP5
8346    15-Way Processor CP5
8347    16-Way Processor CP5
8348    17-Way Processor CP5
8349    18-Way Processor CP5
8350    19-Way Processor CP5
8351    20-Way Processor CP5
8352    21-Way Processor CP5
8353    22-Way Processor CP5
8354    23-Way Processor CP5
8355    24-Way Processor CP5
8356    25-Way Processor CP5
8357    26-Way Processor CP5
8358    27-Way Processor CP5
8359    28-Way Processor CP5
8360    29-Way Processor CP5
8361    30-Way Processor CP5
8362    31-Way Processor CP5
8363    32-Way Processor CP5
8364    33-Way Processor CP5
8365    34-Way Processor CP5
8366    35-Way Processor CP5
8367    36-Way Processor CP5
8368    37-Way Processor CP5
8369    38-Way Processor CP5
8370    39-Way Processor CP5
8371    1-Way Processor CP6
8372    2-Way Processor CP6
8373    3-Way Processor CP6
8374    4-Way Processor CP6
8375    5-Way Processor CP6
8376    6-Way Processor CP6
8377    7-Way Processor CP6
8378    8-Way Processor CP6
8379    9-Way Processor CP6
8380    10-Way Processor CP6
8381    11-Way Processor CP6
8382    12-Way Processor CP6
8383    13-Way Processor CP6
8384    14-Way Processor CP6
8385    15-Way Processor CP6
8386    16-Way Processor CP6
8387    17-Way Processor CP6
8388    18-Way Processor CP6
8389    19-Way Processor CP6
8390    20-Way Processor CP6
8391    21-Way Processor CP6
8392    22-Way Processor CP6
8393    23-Way Processor CP6
8394    24-Way Processor CP6
8395    25-Way Processor CP6
8396    26-Way Processor CP6
8397    27-Way Processor CP6
8398    28-Way Processor CP6
8399    29-Way Processor CP6
8400    30-Way Processor CP6
8401    31-Way Processor CP6
8402    32-Way Processor CP6
8403    33-Way Processor CP6
8404    34-Way Processor CP6
8405    35-Way Processor CP6
8406    36-Way Processor CP6
8407    37-Way Processor CP6
8408    38-Way Processor CP6
8409    39-Way Processor CP6
8410    1-Way Processor CP7
8411    2-Way Processor CP7
8412    3-Way Processor CP7
8413    4-Way Processor CP7
8414    5-Way Processor CP7
8415    6-Way Processor CP7
8416    7-Way Processor CP7
8417    8-Way Processor CP7
8418    9-Way Processor CP7
8419    10-Way Processor CP7
8420    11-Way Processor CP7
8421    12-Way Processor CP7
8422    13-Way Processor CP7
8423    14-Way Processor CP7
8424    15-Way Processor CP7
8425    16-Way Processor CP7
8426    17-Way Processor CP7
8427    18-Way Processor CP7
8428    19-Way Processor CP7
8429    20-Way Processor CP7
8430    21-Way Processor CP7
8431    22-Way Processor CP7
8432    23-Way Processor CP7
8433    24-Way Processor CP7
8434    25-Way Processor CP7
8435    26-Way Processor CP7
8436    27-Way Processor CP7
8437    28-Way Processor CP7
8438    29-Way Processor CP7
8439    30-Way Processor CP7
8440    31-Way Processor CP7
8441    32-Way Processor CP7
8442    33-Way Processor CP7
8443    34-Way Processor CP7
8444    35-Way Processor CP7
8445    36-Way Processor CP7
8446    37-Way Processor CP7
8447    38-Way Processor CP7
8448    39-Way Processor CP7
8449    40-Way Processor CP7
8450    41-Way Processor CP7
8451    42-Way Processor CP7
8452    43-Way Processor CP7
8453    44-Way Processor CP7
8454    45-Way Processor CP7
8455    46-Way Processor CP7
8456    47-Way Processor CP7
8457    48-Way Processor CP7
8458    49-Way Processor CP7
8459    50-Way Processor CP7
8460    51-Way Processor CP7
8461    52-Way Processor CP7
8462    53-Way Processor CP7
8463    54-Way Processor CP7
8464    55-Way Processor CP7
8465    56-Way Processor CP7
8466    57-Way Processor CP7
8467    58-Way Processor CP7
8468    59-Way Processor CP7
8469    60-Way Processor CP7
8470    61-Way Processor CP7
8471    62-Way Processor CP7
8472    63-Way Processor CP7
8473    64-Way Processor CP7
8474    65-Way Processor CP7
8475    66-Way Processor CP7
8476    67-Way Processor CP7
8477    68-Way Processor CP7
8478    69-Way Processor CP7
8479    70-Way Processor CP7
8480    71-Way Processor CP7
8481    72-Way Processor CP7
8482    73-Way Processor CP7
8483    74-Way Processor CP7
8484    75-Way Processor CP7
8485    76-Way Processor CP7
8486    77-Way Processor CP7
8487    78-Way Processor CP7
8488    79-Way Processor CP7
8489    80-Way Processor CP7
8490    81-Way Processor CP7
8491    82-Way Processor CP7
8492    83-Way Processor CP7
8493    84-Way Processor CP7
8494    85-Way Processor CP7
8495    86-Way Processor CP7
8496    87-Way Processor CP7
8497    88-Way Processor CP7
8498    89-Way Processor CP7
8499    90-Way Processor CP7
8500    91-Way Processor CP7
8501    92-Way Processor CP7
8502    93-Way Processor CP7
8503    94-Way Processor CP7
8504    95-Way Processor CP7
8505    96-Way Processor CP7
8506    97-Way Processor CP7
8507    98-Way Processor CP7
8508    99-Way Processor CP7
8509    100-Way Processor CP7
8510    101-Way Processor CP7
8511    102-Way Processor CP7
8512    103-Way Processor CP7
8513    104-Way Processor CP7
8514    105-Way Processor CP7
8515    106-Way Processor CP7
8516    107-Way Processor CP7
8517    108-Way Processor CP7
8518    109-Way Processor CP7
8519    110-Way Processor CP7
8520    111-Way Processor CP7
8521    112-Way Processor CP7
8522    113-Way Processor CP7
8523    114-Way Processor CP7
8524    115-Way Processor CP7
8525    116-Way Processor CP7
8526    117-Way Processor CP7
8527    118-Way Processor CP7
8528    119-Way Processor CP7
8529    120-Way Processor CP7
8530    121-Way Processor CP7
8531    122-Way Processor CP7
8532    123-Way Processor CP7
8533    124-Way Processor CP7
8534    125-Way Processor CP7
8535    126-Way Processor CP7
8536    127-Way Processor CP7
8537    128-Way Processor CP7
8538    129-Way Processor CP7
8539    130-Way Processor CP7
8540    131-Way Processor CP7
8541    132-Way Processor CP7
8542    133-Way Processor CP7
8543    134-Way Processor CP7
8544    135-Way Processor CP7
8545    136-Way Processor CP7
8546    137-Way Processor CP7
8547    138-Way Processor CP7
8548    139-Way Processor CP7
8549    140-Way Processor CP7
8550    141-Way Processor CP7
8551    142-Way Processor CP7
8552    143-Way Processor CP7
8553    144-Way Processor CP7
8554    145-Way Processor CP7
8555    146-Way Processor CP7
8556    147-Way Processor CP7
8557    148-Way Processor CP7
8558    149-Way Processor CP7
8559    150-Way Processor CP7
8560    151-Way Processor CP7
8561    152-Way Processor CP7
8562    153-Way Processor CP7
8563    154-Way Processor CP7
8564    155-Way Processor CP7
8565    156-Way Processor CP7
8566    157-Way Processor CP7
8567    158-Way Processor CP7
8568    159-Way Processor CP7
8569    160-Way Processor CP7
8570    161-Way Processor CP7
8571    162-Way Processor CP7
8572    163-Way Processor CP7
8573    164-Way Processor CP7
8574    165-Way Processor CP7
8575    166-Way Processor CP7
8576    167-Way Processor CP7
8577    168-Way Processor CP7
8578    169-Way Processor CP7
8579    170-Way Processor CP7
8580    171-Way Processor CP7
8581    172-Way Processor CP7
8582    173-Way Processor CP7
8583    174-Way Processor CP7
8584    175-Way Processor CP7
8585    176-Way Processor CP7
8586    177-Way Processor CP7
8587    178-Way Processor CP7
8588    179-Way Processor CP7
8589    180-Way Processor CP7
8590    181-Way Processor CP7
8591    182-Way Processor CP7
8592    183-Way Processor CP7
8593    184-Way Processor CP7
8594    185-Way Processor CP7
8595    186-Way Processor CP7
8596    187-Way Processor CP7
8597    188-Way Processor CP7
8598    189-Way Processor CP7
8599    190-Way Processor CP7
8600    191-Way Processor CP7
8601    192-Way Processor CP7
8602    193-Way Processor CP7
8603    194-Way Processor CP7
8604    195-Way Processor CP7
8605    196-Way Processor CP7
8606    197-Way Processor CP7
8607    198-Way Processor CP7
8608    199-Way Processor CP7
8609    200-Way Processor CP7
9000    Multi Order Ship Flag
9001    Multi Order Rec Only Flag NB
9002    Multi Order Rec Only Flag MES
9003    RPO Action Flag
9004    Downgraded PUs Per Request
9874    On Off CoD Act 100 IFL Days
9875    On Off CoD Act 100 ICF Days
9876    On Off CoD Act 100 CP Days
9877    On Off CoD Act 100 zIIP Days
9878    On Off CoD Act 100 SAP Days
9888    On Off CoD Act IFL Days
9889    On Off CoD Act ICF Days
9896    On Off COD authorization
9897    On Off CoD Act Cap CP Days
9898    Perm upgr authorization
9899    CIU Activation (Flag)
9900    On Line CoD Buying (Flag)
9904    PRC Tokens Authorization
9908    On Off CoD Act zIIP Days
9909    On Off CoD Act SAP Days
9910    CBU authorization
9913    OPO Sales 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
9930    Boost Authorization
9932    TFP for Z HW Authorization
9933    Flex Capacity Authorization
9975    Height Reduce Ship
9976    Height Reduce for Return
Feature Title
Number
------- -----------------
0157    TKE Table Top KMM

Feature availability matrix

Not applicable.

Feature descriptions


Note: Not all of the following features are available in all countries. Check with your country representative for specific feature availability.

NOTE TO FIELD COMMUNICATIONS:

The following are NO CHARGE feature codes for the machine type: 3931 (IBM z16* Model A01)

(#0329) RCN - Regional Cores Number

Feature code #0329 limits the CPU up to 13 cores per socket according to regulations.

  • Minimum: 0.
  • Maximum: 3.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer setup: No.
  • Limitations: Restricted to China.
  • Field Installable: No.
  • Cable Order: N/A.

Technology Exchange and Migration Offering feature codes (#0389 through #0399):

Required for all geographies which use the Technology Exchange (# 0012) and Migration Offering (#0014) process. During New Build orders where Technology Exchange(#0012) or Migration Offering(#0014) features are also selected, the Machine Type, Serial Number, and Plant of Manufacture must be entered for the machine being replaced during a Technology Exchange or Migration Offering. The eConfig user will select the base CPC S/N from which the donor base information will be translated. This is the S/N of the machine being replaced as a result of this Technology Exchange or Migration Offering order.

(#0389) Returning MT Digit 1

Feature code #0389 returns the first machine type digit of the displacement box of a Technology Exchange(TE) or Migration Offering (MO).

  • Minimum: 0
  • Maximum: 15.
  • Prerequisites: TE (#0012) or MO (#0014).
  • Corequisites: None.
  • Compatibility Conflicts: None.
  • Customer setup: No.
  • Limitations: PRC only.
  • Field Installable: No.
  • Cable Order: N/A.
(#0390) Returning MT Digit 2

Feature code #0390 returns the second machine type digit of the displacement box of a Technology Exchange(TE) or Migration Offering (MO).

  • Minimum: 0
  • Maximum: 15.
  • Prerequisites: TE (#0012) or MO (#0014).
  • Corequisites: None.
  • Compatibility Conflicts: None.
  • Customer setup: No.
  • Limitations: None.
  • Field Installable: N/A.
  • Cable Order: N/A.
(#0391) Returning MT Digit 3

Feature code #0391 returns the third machine type digit of the displacement box of a Technology Exchange(TE) or Migration Offering (MO).

  • Minimum: 0
  • Maximum: 15.
  • Prerequisites: TE (#0012) or MO (#0014).
  • Corequisites: None.
  • Compatibility Conflicts: None.
  • Customer setup: No.
  • Limitations: None.
  • Field Installable: N/A.
  • Cable Order: N/A.
(#0392) Returning MT Digit 4

Feature code #0392 returns the fourth machine type digit of the displacement box of a Technology Exchange(TE) or Migration Offering (MO).

  • Minimum: 0
  • Maximum: 15.
  • Prerequisites: TE (#0012) or MO (#0014).
  • Corequisites: None.
  • Compatibility Conflicts: None.
  • Customer setup: No.
  • Limitations: None.
  • Field Installable: N/A.
  • Cable Order: N/A.
(#0393) Plant of MFG Digit 1

Feature code #0393 returns the first plant of manufacture digit of the displacement box of a Technology Exchange(TE) or Migration Offering (MO).

  • Minimum: 0
  • Maximum: 15.
  • Prerequisites: TE (#0012) or MO (#0014).
  • Corequisites: None.
  • Compatibility Conflicts: None.
  • Customer setup: No.
  • Limitations: None.
  • Field Installable: N/A.
  • Cable Order: N/A.
(#0394) Plant of MFG Digit 2

Feature code #0394 returns the second plant of manufacture digit of the displacement box of a Technology Exchange(TE) or Migration Offering (MO).

  • Minimum: 0
  • Maximum: 15.
  • Prerequisites: TE (#0012) or MO (#0014).
  • Corequisites: None.
  • Compatibility Conflicts: None.
  • Customer setup: No.
  • Limitations: None.
  • Field Installable: N/A.
  • Cable Order: N/A.
(#0395) Serial Number Digit 1

Feature code #0395 returns the first serial number digit of the displacement box of a Technology Exchange(TE) or Migration Offering (MO).

  • Minimum: 0
  • Maximum: 15.
  • Prerequisites: TE (#0012) or MO (#0014).
  • Corequisites: None.
  • Compatibility Conflicts: None.
  • Customer setup: No.
  • Limitations: None.
  • Field Installable: N/A.
  • Cable Order: N/A.
(#0396) Serial Number Digit 2

Feature code #0396 returns the second serial number digit of the displacement box of a Technology Exchange(TE) or Migration Offering (MO).

  • Minimum: 0
  • Maximum: 15.
  • Prerequisites: TE (#0012) or MO (#0014).
  • Corequisites: None.
  • Compatibility Conflicts: None.
  • Customer setup: No.
  • Limitations: None.
  • Field Installable: N/A.
  • Cable Order: N/A.
(#0397) Serial Number Digit 3

Feature code #0397 returns the third serial number digit of the displacement box of a Technology Exchange(TE) or Migration Offering (MO).

  • Minimum: 0
  • Maximum: 15.
  • Prerequisites: TE (#0012) or MO (#0014).
  • Corequisites: None.
  • Compatibility Conflicts: None.
  • Customer setup: No.
  • Limitations: None.
  • Field Installable: N/A.
  • Cable Order: N/A.
(#0398) Serial Number Digit 4

Feature code #0398 returns the fourth serial number digit of the displacement box of a Technology Exchange(TE) or Migration Offering (MO).

  • Minimum: 0
  • Maximum: 15.
  • Prerequisites: TE (#0012) or MO (#0014).
  • Corequisites: None.
  • Compatibility Conflicts: None.
  • Customer setup: No.
  • Limitations: None.
  • Field Installable: N/A.
  • Cable Order: N/A.
(#0399) Serial Number Digit 5

Feature code #0399 returns the fifth serial number digit of the displacement box of a Technology Exchange(TE) or Migration Offering (MO).

  • Minimum: 0
  • Maximum: 15.
  • Prerequisites: TE (#0012) or MO (#0014).
  • Corequisites: None.
  • Compatibility Conflicts: None.
  • Customer setup: No.
  • Limitations: None.
  • Field Installable: N/A.
  • Cable Order: N/A.

NOTE TO FIELD COMMUNICATIONS:

The following are CHARGEABLE feature codes for the new machine type:

3931 (IBM z16* Model A01)

(#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.
  • Cable Order: 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.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None.
  • Customer Setup: No.
  • Limitations: Not available on initial system order.
  • Field Installable: N/A.
  • Cable Order: 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: 0.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None.
  • Customer Setup: No.
  • Limitations: Initial system order only.
  • Field Installable: N/A.
  • Cable Order: 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.
  • Cable Order: N/A.
(#0032) Non RSF 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 Resource Link profile to indicate the On/Off CoD link will be delivered via media/CD Rom. This signals Business Practices to establish a contract addendum that details the requirements for VPD transmission.

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

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

  • Minimum: 0.
  • Maximum: 0.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes.
  • Cable Order: N/A.
(#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: 0.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: Mutually exclusive with #0036.
  • Customer Setup: No.
  • Limitations: Available on box orders in:
----------------- ------------------ -------------------- -----------------
Argentina         Canada             Hong Kong            Peru
Aruba             Chile              Israel               Saint Lucia
Bahamas           China              Jamaica              Sri Lanka
Bangladesh        Columbia           Korea                Singapore
Barbados          Costa Rica         Laos                 Suriname
Belize            Dominican Republic Macao                Taiwan
Bermuda           Ecuador            Malaysia             Thailand
Bolivia           El Salvador        Mexico               Trinidad & Tobago
Brazil            Guatemala          Myanmar              United States
Brunei Darussalam Guyana             Netherlands Antilles Uruguay
Cambodia          Haiti              Nicaragua            Venezuela
                  Honduras           Panama               Vietnam
  • Field Installable: Yes.
  • Cable Order: N/A.
(#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.
  • Customer Setup: No.
  • Limitations: Available on box orders in:
------------------------ ------------------------------ -------------- --------------------
Abu Dhabi                Eastern Europe Direct Business Kyrgyzstan     Russian Federation
Afghanistan              Egypt                          Latvia         Rwanda
Albania                  Equatorial Guinea              Lesotho        Sao Tome & Princip
Algeria                  Eritrea                        Liberia        Slovakia
Angola                   Estonia                        Libya          Slovenia
Austria                  Ethiopia                       Liechtenstein  Spain
Azerbaijan               Finland                        Lithuania      Somolia
Belarus                  Gabon                          Macedonia      South Africa
Belgium                  Gambia                         Madagascar     Sudan
Benin                    Georgia                        Mali           Swaziland
Botswana                 Germany                        Malta          Switzerland
Bosnia                   Greece                         Mauretania     Sweden
Bulgaria                 Ghana                          Middle East DB Syrian Arab Republic
Burkinao Faso            Guadeloupe                     Martinique     Szekesfehervar
Burundi                  Guinea                         Moldova        Tajikistan
Cape Verde               Guinea Bissau                  Montenegro     Tanzania
Cameroon                 Guinea Conocracy               Morocco        Togo
Central African Republic Hungary                        Namibia        Turkey
Chad                     Iceland                        Netherlands    Turkmenistan
Comoros                  India                          New Zealand    Uganda
Congo                    Iran                           Niger          Ukraine
Croatia                  Iraq                           Norway         United Kingdom
Cyprus                   Ireland                        Oman           Uzbekistan
Czech Republic           Italy                          Pakistan       Yemen
Democratic Republic      Ivory Coast                    Poland         Zambia
Denmark                  Jordan                         Portugal       Zimbabwe
Djibouti                 Kuwait                         Romania
  • Field Installable: No.
  • Cable Order: No.
(#0057) TKE Rack Mount

Feature code 0057 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 the Common Cryptographic Architecture (CCA) coprocessor. The TKE workstation has one Ethernet port and supports connectivity to an Ethernet Local Area Network (LAN) operating at 100, or 1000 Mbps. Although customers can carry forward their TKEs on IBM z16 new capabilities will only be delivered on newly manufactured TKEs. The IBM z16 environment can contain both TKEs that have been carried forward and newly manufactured TKEs.
Note: TKE 10.0 is required if you choose to use the TKE to manage a Crypto Express8S. 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 #0057 and #0058
  • Prerequisites: None.
  • Corequisites: #0156 (TKE Rack KMM), or #0190 (Client Must Provide TKE KMM).
  • 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.2 with these readers.
    • You can also order new smart card readers with feature code 0891.

Note: Gemalto CT700 readers will only work with smart cards that have applets loaded from TKE 8.1 or later. You must carry Omnikey Cardman 3821 or IDENTIV
  • Customer setup: No.
  • Limitations: None.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
  • Cable Orders: LAN cabling is a customer responsibility. A Category 5 Unshielded Twisted Pair (UTP) cable terminated with RJ-45 connector is required.
(#0058) TKE

Feature code 0058 is a new purchase of a Tower TKE. You can order up to 10 TKE feature codes 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. Although customers can carry forward their TKEs on IBM z16, new capabilities will only be delivered on newly manufactured TKEs. The IBM z16 environment can contain both TKEs that have been carried forward and newly manufactured TKEs.
Note: TKE 10 is required if you choose to use the TKE to manage a Crypto Express8S. 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 #0057 and #0058.
  • Prerequisites: None.
  • Corequisites: #0156 (TKE Rack KMM), or #0190 (Client Must Provide TKE KMM).
  • 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 10 with these readers.
    • You can also order new smart card readers with feature code 0891.

    Note: Gemalto CT700 readers will only work with smart cards that have applets loaded from TKE 8.1 or later. You must carry Omnikey Cardman 3821 or IDENTIV.
  • Customer setup: No.
  • Limitations: None.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
  • Cable Orders: LAN cabling is a customer responsibility. A Category 5 Unshielded TwistedPair (UTP) cable terminated with RJ-45 connector is required.
(#0093) OEM Generic Indicator

This is an administrative feature code that will be used by Sales for searching iERP/WTAAS for enforcement of warranties and offering templates. Minimum: 0. Maximum: 1. Prerequisites: None. Corequisites: MSS Sales Flag (#3666). Compatibility Conflicts: None known. Customer Setup: Not applicable. Limitations: None. Field Installable: N/A. Cable Order: 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.
  • Cable Order: N/A.
(#0115) Secure Execution for Linux

This is a pricing feature used to initiate the contract for electronic delivery of Secure Execution for Linux.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes.
  • Cable Order: N/A.
(#0129) IBM Z Hardware Management Appliance

Feature code #0129 can be ordered to provide the HMC/SE functionality to be contained within redundant physical servers inside the CPC frame. The Hardware Management Appliance feature will provide, logically, a Primary and Alternate Support Element and two peer Hardware Management Consoles on two physical servers in the CPC frame. This eliminates the need for having to manage a separate physical server or servers for HMC(s) outside of the frame. For the User Interface experience you must use remote browsing controls from your own workstation into HMC within the Hardware Management Appliance. If you have multiple systems, you don't need to order the Hardware Management Appliance feature for all systems. The recommendation is that you consider having the Hardware Management Appliance features on one or two CPCs, but the rest of the CPCs don't need to include Hardware Management Appliance features (those CPCs would have redundant Support Elements). Physical HMCs (both Mini Tower and rack mounted) can still be used if they are installed at the time of an upgrade to IBM z16 and carried forward.

  • Minimum: 0.
  • Maximum: 1.
  • 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. The HMC supports IBM. It can also be used to support IBM z15 model T01, IBM z15 model T02, and IBM z14, IBM z14 model ZR1.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
  • Cable Orders: N/A.
(#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: 0.
  • Maximum: One per Rack Mounted TKE #0057.
  • Prerequisites: The Rack Mounted TKE #0057.
  • 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 Orders: USB, VGA cable, and Power Jumper is included.
(#0157) TKE Table Top Keybd/Monitor/Mouse

Feature code #0157 is a tabletop Monitor with a US English language keyboard. There is a touchpad for pointing, and a country-specific power cord.

  • Minimum: 0.
  • Maximum: One per Tower TKE #0058.
  • Prerequisites: Tower TKE #0058.
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer setup: No.
  • Limitations: NOT available in Japan.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
  • Cable Orders: Power cord, Video cable, and a USB cable are provided.
(#0176) IBM Integrated Coupling Adapter (ICA SR1.1)

The ICA SR1.1 is a 2 port fanout used for short distance coupling connectivity and uses coupling channel type: CS5. It utilizes PCIe Gen3 technology, with x16 lanes that are bifurcated into x8 lanes for coupling. The ICA SR1.1 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 SR1.1 is designed to support up to 4 CHPIDs per port and 8 buffers (i.e. subchannels) per CHPID. The ICA SR1.1 fanout resides in the PCIe fanout slot on the IBM z16 CPC drawer. The ICA SR1.1 can only be used for coupling connectivity between IBM z14, IBM z14 ZR1, IBM z15 model T01, IBM z15 model T02 and IBM z16 CPCs. For cabling requirements, see cabling information provided below. The IBM z16 supports 12 PCIe fanout slots per CPC drawer which can be used for ICA SR1.1 coupling or connectivity to the PCIe I/O drawer in the I/O subsystem. The ICA SR1.1 is compatible with ICA SR links on earlier machines and can interconnect with them.

  • Minimum: None. Order increment is two links/ports.
  • Maximum: 48 (96 ports). The maximum number of all ICA SR1.1 fanout features is limited to 48 per system. If you carry- forward ICA SR and ICA SR1.1 features from a previous machine, the total number of carried-forward features plus new ICA SR1.1 features ordered is also 48 (96 ports).
  • Prerequisites: None.
  • Corequisites: STP enablement (#1021).
  • Compatibility Conflicts: Not compatible with InfiniBand. The ICA SR1.1 is compatible with ICA SR links on earlier machines and can interconnect with them.
  • Customer Setup: No.
  • Limitations:
    • Maximum supported distance is 150 meters (492 feet). This distance cannot be extended through the use of repeaters, DWDMs, etc..
  • Field Installable: Yes.
  • Cable Order: A customer-supplied 24x MTP-MTP cable is required for each port of the ICA SR1.1 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 fibertype options are available with specifications supporting different distances for the ICA SR:
    • 150m: OM4 50/125micrometer multimode fiber optic cable with a fiber bandwidth@ wavelength: 4.7 GHz-km@ 850 nm.
    • 100m: OM3 50/125micrometer multimode fiber optic cable with a fiber bandwidth@ wavelength: 2.0 GHz-km@ 850 nm.
Refer to: IBM Z Planning for Fiber Optic Links (FICON/FCP, Coupling Links, Open Systems Adapters, and zHyperLink Express), GA23-1408.
(#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 or #0157, due to import restrictions, then #0190 is added to the order to inform the client that they must provide a Monitor and Keyboard with a pointing device. The Keyboard must be in the US English language. Both the keyboard and pointing device must be USB and have a proper cable to reach the TKE. The Monitor must be DisplayPort. Its cable must have a male DisplayPort connector and also reach the TKE.

  • Minimum: 0.
  • Maximum: One per Rack Mounted TKE #0057 or #0058.
  • Prequisites: The Rack Mounted TKE #0057 or #0058.
  • Corequisites: None.
  • Compatibility Conflicts: TKE Rack Keybd/Monitor/Mouse #0156 or #0157.
  • Customer setup: No.
  • Limitations: None.
  • Field Installable: N/A.
  • Cable Order: N/A.
(#0201) 3906 w/o TEIO & w/o HtR

This feature provides a means to order and price return packaging materials for installed machines being replaced by a MT 3931 through new build, Migration Offering or Machine Type Upgrade order. Select when system to be returned is MT 3906, 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:
  • Customer Setup: No.
  • Limitations: Radiator-cooled MT 3906 without TEIO and does not require a height reduction.
  • Field Installable: Yes.
  • Cable Orders: N/A.
(#0202) 3906 w/ TEIO & w/o HtR

This feature provides a means to order and price return packaging materials for installed machines being replaced by a MT 3931 through new build, Migration Offering or Machine Type Upgrade order. Select when system to be returned is MT 3906, 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:
  • Customer Setup: No.
  • Limitations: Radiator-cooled MT 3906 with TEIO and does not require a height reduction.
  • Field Installable: Yes.
  • Cable Orders: N/A.
(#0203) 3906 w/o TEIO & w/ HtR

This feature provides a means to order and price return packaging materials for installed machines being replaced by a MT 3931 through new build, Migration Offering or Machine Type Upgrade order. Select when system to be returned is MT 3906, 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:
  • Customer Setup: No.
  • Limitations: Radiator-cooled MT 3906 without TEIO and requires a height reduction.
  • Field Installable: Yes.
  • Cable Orders: N/A.
(#0204) 3906 w/ TEIO & w/ HtR

This feature provides a means to order and price return packaging materials for installed machines being replaced by a MT 3931 through new build, Migration Offering or Machine Type Upgrade order. Select when system to be returned is MT 3906, 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:
  • Customer Setup: No.
  • Limitations: Radiator-cooled MT 3906 with TEIO and requires a height reduction.
  • Field Installable: Yes.
  • Cable Orders: N/A.
(#0250) DPM

Dynamic Partition Manager (DPM) is fully encapsulated firmware shipped and managed via the HMC/HMA. The Dynamic Partition Manager is designed to unify the full platform of IBM z16 virtualization capabilities through state-of-the-art server virtualization technology and seamless integration with network and storage virtualization. Switching a CPC between "Standard PR/SM" and "Dynamic Partition Manager" requires a Power-on reset. No additional media is required to enable or disable the feature.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes.
  • Cable Orders: N/A.
(#0253) TFP Monthly Sub 1 MSU

Used for billing of the contracted subscription on a monthly basis.

  • Minimum: 0.
  • Maximum: 99.
  • Prerequisites: #9932.
  • Corequisites: None.
  • Compatibility Conflicts: Mutually exclusive with #0256, #0257, #0258.
  • Customer Setup: N/A.
  • Limitations: NOT available in People's Republic of China.
  • Field Installable: N/A.
  • Cable Order: N/A.
(#0254) TFP Monthly Sub 100 MSU

Used for billing of the contracted subscription on a monthly basis.

  • Minimum: 0.
  • Maximum: 99.
  • Prerequisites: #9932.
  • Corequisites: None.
  • Compatibility Conflicts: Mutually exclusive with #0256, #0257, #0258.
  • Customer Setup: N/A.
  • Limitations: NOT available in People's Republic of China.
  • Field Installable: N/A.
  • Cable Order: N/A.
(#0255) TFP Monthly Sub 10000 MSU

Used for billing of the contracted subscription on a monthly basis.

  • Minimum: 0.
  • Maximum: 250.
  • Prerequisites: #9932.
  • Corequisites: None.
  • Compatibility Conflicts: Mutually exclusive with #0256, #0257, #0258.
  • Customer Setup: N/A.
  • Limitations: NOT available in People's Republic of China.
  • Field Installable: N/A.
  • Cable Order: N/A.
(#0256) Prepaid TFP Sub 1 MSU

Used for billing of a prepaid subscription.

  • Minimum: 0.
  • Maximum: 99.
  • Prerequisites: #9932.
  • Corequisites: None.
  • Compatibility Conflicts: Mutually exclusive with #0253, #0254, #0255.
  • Customer Setup: N/A.
  • Limitations: NOT available in People's Republic of China.
  • Field Installable: N/A.
  • Cable Order: N/A.
(#0257) Prepaid TFP Sub 100 MSU

Used for billing of a prepaid subscription.

  • Minimum: 0.
  • Maximum: 99.
  • Prerequisites: #9932.
  • Corequisites: None.
  • Compatibility Conflicts: Mutually exclusive with #0253, #0254, #0255.
  • Customer Setup: N/A.
  • Limitations: NOT available in People's Republic of China.
  • Field Installable: N/A.
  • Cable Order: N/A.
(#0258) Prepaid TFP Sub 10000 MSU

Used for billing of a prepaid subscription.

  • Minimum: 0.
  • Maximum: 250.
  • Prerequisites: #9932.
  • Corequisites: None.
  • Compatibility Conflicts: Mutually exclusive with #0253, #0254, #0255.
  • Customer Setup: N/A.
  • Limitations: NOT available in People's Republic of China.
  • Field Installable: N/A.
  • Cable Order: N/A.
(#0259) TFP Subscription Months

Used to price and record a prepaid subscription's duration.

  • Minimum: 0.
  • Maximum: 60.
  • Prerequisites: #9932.
  • Corequisites: None.
  • Compatibility Conflicts: Mutually exclusive with #0253, #0254, #0255.
  • Customer Setup: N/A.
  • Limitations: NOT available in People's Republic of China.
  • Field Installable: N/A.
  • Cable Order: N/A.
(#0260) TFP Hourly 1 MSU

Used for TFP billing based on usage.

  • Minimum: 0.
  • Maximum: 99.
  • Prerequisites: #9932.
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: N/A.
  • Limitations: NOT available in People's Republic of China.
  • Field Installable: N/A.
  • Cable Order: N/A.
(#0261) TFP Hourly 100 MSU

Used for TFP billing based on usage.

  • Minimum: 0.
  • Maximum: 99.
  • Prerequisites: #9932.
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: N/A.
  • Limitations: NOT available in People's Republic of China.
  • Field Installable: N/A.
  • Cable Order: N/A.
(#0262) TFP Hourly 10000 MSU

Used for TFP billing based on usage.

  • Minimum: 0.
  • Maximum: 250.
  • Prerequisites: #9932.
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: N/A.
  • Limitations: NOT available in People's Republic of China.
  • Field Installable: N/A.
  • Cable Order: N/A.
(#0263) TFP Daily 1 MSU

Used for TFP billing based on usage.

  • Minimum: 0.
  • Maximum: 99.
  • Prerequisites: #9932.
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: N/A.
  • Limitations: NOT available in People's Republic of China.
  • Field Installable: N/A.
  • Cable Order: N/A.
(#0264) TFP Daily 100 MSU

Used for TFP billing based on usage.

  • Minimum: 0.
  • Maximum: 99.
  • Prerequisites: #9932.
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: N/A.
  • Limitations: NOT available in People's Republic of China.
  • Field Installable: N/A.
  • Cable Order: N/A.
(#0265) TFP Daily 10000 MSU

Used for TFP billing based on usage.

  • Minimum: 0.
  • Maximum: 250.
  • Prerequisites: #9932.
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: N/A.
  • Limitations: NOT available in People's Republic of China.
  • Field Installable: N/A.
  • Cable Order: N/A.
(#0317) Flexible Cap 1 Unit

Pricing feature code used to facilitate the billing of temporary CP capacity resources configured for Flexible Capacity for Cyber Resiliency under a Perpetual License (#7805). Minimum: 0. Maximum: 99. Prerequisites: None. Corequisites: Flexible Capacity Record (#0376), Flex Cap Perpetual License (#7805). Compatibility Conflicts: #7806. Customer Setup: N/A. Limitations: None. Field Installable: N/A. Cable Orders: N/A.

(#0318) Flexible Cap 100 Units

Pricing feature code used to facilitate the billing of temporary CP capacity resources configured for Flexible Capacity for Cyber Resiliency under a Perpetual License (#7805). Minimum: 0. Maximum: 99. Prerequisites: None. Corequisites: Flexible Capacity Record (#0376), Flex Cap Perpetual License (#7805). Compatibility Conflicts: #7806. Customer Setup: N/A. Limitations: None. Field Installable: N/A. Cable Orders: N/A.

(#0319) Flexible Cap 10000 Units

Pricing feature code used to facilitate the billing of temporary CP capacity resources configured for Flexible Capacity for Cyber Resiliency under a Perpetual License (#7805). Minimum: 0. Maximum: 250. Prerequisites: None. Corequisites: Flexible Capacity Record (#0376), Flex Cap Perpetual License (#7805). Compatibility Conflicts: #7806. Customer Setup: N/A. Limitations: None. Field Installable: N/A. Cable Orders: N/A.

(#0320) Flexible Cap IFL

Pricing feature code used to facilitate the billing of temporary IFL resources configured for Flexible Capacity for Cyber Resiliency under a Perpetual License (#7805). Minimum: 0. Maximum: 250. Prerequisites: None. Corequisites: Flexible Capacity Record (#0376), Flex Cap Perpetual License (#7805). Compatibility Conflicts: #7806. Customer Setup: N/A. Limitations: None. Field Installable: N/A. Cable Orders: N/A.

(#0321) Flexible Cap ICF

Pricing feature code used to facilitate the billing of temporary ICF resources configured for Flexible Capacity for Cyber Resiliency under a Perpetual License (#7805). Minimum: 0. Maximum: 250. Prerequisites: None. Corequisites: Flexible Capacity Record (#0376), Flex Cap Perpetual License (#7805). Compatibility Conflicts: #7806. Customer Setup: N/A. Limitations: None. Field Installable: N/A. Cable Orders: N/A.

(#0322) Flexible Cap zIIP

Pricing feature code used to facilitate the billing of temporary zIIP resources configured for Flexible Capacity for Cyber Resiliency under a Perpetual License (#7805). Minimum: 0. Maximum: 250. Prerequisites: None. Corequisites: Flexible Capacity Record (#0376), Flex Cap Perpetual License (#7805). Compatibility Conflicts: #7806. Customer Setup: N/A. Limitations: None Field Installable: N/A. Cable Orders: N/A.

(#0376) Flexible Capacity Record

This feature enables temporary activation of additional capacity that will facilitate capacity shifts between participating IBM z16 machines on other sites. Minimum: 0. Maximum: 1. Prerequisites: Flex Capacity Authorization (#9933). Corequisites: None. Compatibility Conflicts: None known. Customer Setup: No. Limitations: None. Field Installable: Yes. Cable Order: N/A.

(#0377) Flexible Cap Term Years

This feature is used for setting the expiration date on the Flexible Capacity Record (#0376) under a Term License (#7806). The feature code is also used in the assignment of feature codes (#0378-#0386) for the billing of temporary resources configured for Flexible Capacity for Cyber Resiliency under a Term License (#7806). Minimum: 0. Maximum: 5. Prerequisites: None. Corequisites: Flexible Capacity Record (#0376), Flexible Cap Term License (#7806). Compatibility Conflicts: #7805. Customer Setup: N/A. Limitations: None. Field Installable: N/A. Cable Orders: N/A.

(#0378) Flexible Cap 1 Unit Year

Pricing feature code used to facilitate the billing of temporary CP capacity resources configured for Flexible Capacity for Cyber Resiliency under a Term License (#7806). Minimum: 0. Maximum: 99. Prerequisites: None. Corequisites: Flexible Capacity Record (#0376), Flexible Cap Term License (#7806). Compatibility Conflicts: #7805. Customer Setup: N/A. Limitations: None. Field Installable: N/A. Cable Orders: N/A.

(#0379) Flexible Cap 100 Units Year

Pricing feature code used to facilitate the billing of temporary CP capacity resources configured for Flexible Capacity for Cyber Resiliency under a Term License (#7806). Minimum: 0. Maximum: 99. Prerequisites: None. Corequisites: Flexible Capacity Record (#0376), Flexible Cap Term License (#7806). Compatibility Conflicts: #7805. Customer Setup: N/A. Limitations: None. Field Installable: N/A. Cable Orders: N/A.

(#0380) Flexible Cap 10000Units Year

Pricing feature code used to facilitate the billing of temporary CP capacity resources configured for Flexible Capacity for Cyber Resiliency under a Term License (#7806). Minimum: 0. Maximum: 250. Prerequisites: None. Corequisites: Flexible Capacity Record (#0376), Flexible Cap Term License (#7806). Compatibility Conflicts: #7805. Customer Setup: N/A. Limitations: None. Field Installable: N/A. Cable Orders: N/A.

(#0381) Flexible Cap IFL Year

Pricing feature code used to facilitate the billing of temporary IFL resources configured for Flexible Capacity for Cyber Resiliency under a Term License (#7806). Minimum: 0. Maximum: 99. Prerequisites: None. Corequisites: Flexible Capacity Record (#0376), Flexible Cap Term License (#7806). Compatibility Conflicts: #7805. Customer Setup: N/A. Limitations: None. Field Installable: N/A. Cable Orders: N/A.

(#0382) Flexible Cap 100 IFL Year

Pricing feature code used to facilitate the billing of temporary IFL resources configured for Flexible Capacity for Cyber Resiliency under a Term License (#7806). Minimum: 0. Maximum: 250. Prerequisites: None. Corequisites: Flexible Capacity Record (#0376), Flexible Cap Term License (#7806). Compatibility Conflicts: #7805. Customer Setup: N/A. Limitations: None. Field Installable: N/A. Cable Orders: N/A.

(#0383) Flexible Cap ICF Year

Pricing feature code used to facilitate the billing of temporary ICF resources configured for Flexible Capacity for Cyber Resiliency under a Term License (#7806). Minimum: 0. Maximum: 99. Prerequisites: None. Corequisites: Flexible Capacity Record (#0376), Flexible Cap Term License (#7806). Compatibility Conflicts: #7805. Customer Setup: N/A. Limitations: None. Field Installable: N/A. Cable Orders: N/A.

(#0384) Flexible Cap 100 ICF Year

Pricing feature code used to facilitate the billing of temporary ICF resources configured for Flexible Capacity for Cyber Resiliency under a Term License (#7806). Minimum: 0. Maximum: 250. Prerequisites: None. Corequisites: Flexible Capacity Record (#0376), Flexible Cap Term License (#7806). Compatibility Conflicts: #7805. Customer Setup: N/A. Limitations: None. Field Installable: N/A. Cable Orders: N/A.

(#0385) Flexible Cap zIIP Year

Pricing feature code used to facilitate the billing of temporary zIIP resources configured for Flexible Capacity for Cyber Resiliency under a Term License (#7806). Minimum: 0. Maximum: 99. Prerequisites: None. Corequisites: Flexible Capacity Record (#0376), Flexible Cap Term License (#7806). Compatibility Conflicts: #7805. Customer Setup: N/A. Limitations: None. Field Installable: N/A. Cable Orders: N/A.

(#0386) Flexible Cap 100 zIIP Year

Pricing feature code used to facilitate the billing of temporary zIIP resources configured for Flexible Capacity for Cyber Resiliency under a Term License (#7806). Minimum: 0. Maximum: 250. Prerequisites: None. Corequisites: Flexible Capacity Record (#0376), Flexible Cap Term License (#7806). Compatibility Conflicts: #7805. Customer Setup: N/A. Limitations: None. Field Installable: N/A. Cable Orders: N/A.

(#0434) Coupling Express2 LR

Coupling Express2 LR is a 2-port feature used for long distance coupling connectivity and utilizes coupling channel type CL5. It utilizes 10 GbE 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 (#4023). 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 Coupling Express2 LR supports connectivity back to Coupling Express LR features offered on IBM z15, IBM z14, and IBM z14 model ZR1 servers. 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.

(#0440) 10 GbE RoCE Express3 SR

10 GbE RoCE Express3 SR 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 enables Shared Memory Communications over RDMA (SMC-R) between two CPCs over a layer 2 Ethernet fabric or over a layer 3 IP network when using SMC-Rv2 with RoCEv2. The RoCE feature will also be exploited by Linux on IBM Z Systems for applications that are coded to the native RoCE verb interface or use Ethernet (such as TCP/IP). Single Root I/O Virtualization (SR-IOV) for 10 GbE RoCE Express3 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.

  • Minimum: 0.
  • Maximum: 16 features (32 ports). The card is orderable by ports, in increments of 2.
  • Prerequisites: None.
  • Corequisites: PCIe+ I/O drawer (#4021).
  • Compatibility Conflicts: None known. IBM recommends using only 10 GbE or 25 GbE in an environment, not both.
  • Customer setup: No.
  • Limitations: Total limit of 16 RoCE Express2 + RoCE Express2.1 + RoCE Express3 adapters for the machine.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
  • 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.
(#0441) 10 GbE RoCE Express3 LR

10 GbE RoCE Express3 LR 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 enables Shared Memory Communications over RDMA (SMC-R) between two CPCs over a layer 2 Ethernet fabric or over a layer 3 IP network when using SMC-Rv2 with RoCEv2. The RoCE feature will also be exploited by Linux on IBM Z Systems for applications that are coded to the native RoCE verb interface or use Ethernet (such as TCP/IP). Single Root I/O Virtualization (SR-IOV) for 10 GbE RoCE Express3 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.

  • Minimum: 0.
  • Maximum: 16 features (32 ports). The card is orderable by ports, in increments of 2.
  • Prerequisites: None.
  • Corequisites: PCIe+ I/O drawer (#4021).
  • Compatibility Conflicts: None known. IBM recommends using only 10 GbE or 25 GbE in an environment, not both.
  • Customer setup: No.
  • Limitations: Total limit of 16 RoCE Express2 + RoCE Express2.1 + RoCE Express3 adapters for the machine.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
  • 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.
(#0451) zHyperLink Express1.1

zHyperLink Express1.1 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 IBM z15 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 (#4021). 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. Total limit of 16 zHyperlink Express + zHyperlink Express1.1 adapters for the machine Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM. 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

(#0452) 25GbE RoCE Express3 SR

25GbE RoCE Express3 SR 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 enables Shared Memory Communications over RDMA (SMC-R) between two CPCs over a layer 2 Ethernet fabric or over a layer 3 IP network when using SMC-Rv2 with RoCEv2. The RoCE feature will also be exploited by Linux on IBM Z Systems for applications that are coded to the native RoCE verb interface or use Ethernet (such as TCP/IP). Single Root I/O Virtualization (SR-IOV) for 25 GbE RoCE Express3 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.

  • Minimum: 0.
  • Maximum: 16 features (32 ports). The card is orderable by ports, in increments of 2.
  • Prerequisites: None.
  • Corequisites: PCIe+ I/O drawer (#4021).
  • Compatibility Conflicts: None known. IBM recommends using only 10 GbE or 25 GbE in an environment, not both.
  • Customer setup: No.
  • Limitations: Total limit of 16 RoCE Express2 + RoCE Express2.1 + RoCE Express3 adapters for the machine.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
  • 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.
(#0453) 25GbE RoCE Express3 LR

25GbE RoCE Express3 LR 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 enables Shared Memory Communications over RDMA (SMC-R) between two CPCs over a layer 2 Ethernet fabric or over a layer 3 IP network when using SMC-Rv2 with RoCEv2. The RoCE feature will also be exploited by Linux on IBM Z Systems for applications that are coded to the native RoCE verb interface or use Ethernet (such as TCP/IP). Single Root I/O Virtualization (SR-IOV) for 25 GbE RoCE Express3 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. Minimum: 0. Maximum: 16 features (32 ports). The card is orderable by ports, in increments of 2. Prerequisites: None. Corequisites: PCIe+ I/O drawer (#4021). Compatibility Conflicts: None known. IBM recommends using only 10 GbE or 25 GbE in an environment, not both. Customer setup: No. Limitations: Total limit of 16 RoCE Express2 + RoCE Express2.1 + RoCE Express3 adapters for the machine. Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM. 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.

(#0454) OSA-Express7S GbE LX 1.2

OSA-Express7S Gigabit Ethernet (GbE) long wavelength (LX) 1.2 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-Express7S and OSA-Express6S features. Prerequisites: None. Corequisites: PCIe I/O drawer (#4021). Compatibility Conflicts: The OSA-Express7S GbE LX 1.2 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-Express7S and OSAExpress6S features. Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM. 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.

(#0455) OSA-Express7S GbE SX 1.2

OSA-Express7S Gigabit Ethernet (GbE) short wavelength (SX) 1.2 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-Express7S and OSA-Express6S features. Prerequisites: None. Corequisites: PCIe I/O drawer (#4021). Compatibility Conflicts: The OSA-Express7S GbE SX 1.2 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-Express7S and OSAExpress6S features. Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM. 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.

(#0456) OSA-Express7S 10 GbE LR 1.2

OSA-Express7S 10 Gigabit Ethernet (GbE) long reach (LR) 1.2 feature has one PCIe adapter and one port per feature. The port supports channel path identifier (CHPID) type OSD (TCP/IP, Layer 2, Layer 3 traffic). 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-Express7S and OSA-Express6S features. Prerequisites: None. Corequisites: PCIe I/O drawer (#4021). Compatibility Conflicts: The OSA-Express7S 10 GbE LR 1.2 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-Express7S and OSAExpress6S features. Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM. 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.

(#0457) OSA-Express7S 10 GbE SR 1.2

OSA-Express7S 10 Gigabit Ethernet (GbE) short reach (SR) 1.2 feature has one PCIe adapter and one port per feature. The port supports channel path identifier (CHPID) type OSD (TCP/IP, Layer 2, Layer 3 traffic). 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-Express7S and OSA-Express6S features. Prerequisites: None. Corequisites: PCIe I/O drawer (#4021). Compatibility Conflicts: The OSA-Express7S 10 GbE LR 1.2 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-Express7S and OSAExpress6S features. Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM. 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.

(#0458) OSA-Express7S 1000BASE-T 1.2

OSA-Express7S 1000BASE-T Ethernet 1.2 feature has one PCIe adapter and two ports. The two ports share one channel path identifier (CHPID). The following CHPID types 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

Each port supports attachment to a 1000BASE-T (1000 Mbps or 1 Gbps) Ethernet Local Area Network (LAN). The feature supports auto- negotiation and automatically adjusts to 100 or 1000 Mbps, depending upon the LAN. When the feature is set to auto-negotiate, the target device must also be set to auto-negotiate. 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: 0.
  • Maximum: 48 features; any mix of OSA-Express7S and OSA-Express6S features.
  • Prerequisites: None.
  • Corequisites: PCIe I/O drawer (#4021).
  • Compatibility Conflicts: When the OSA-Express7S feature is set to auto-negotiate, the target device must also be set to auto-negotiate. Both ends must match (auto-negotiate on or off).
  • Customer setup: No.
  • Limitations:
    • Total limit of 48 features for the machine. Any mix of OSA-Express7S and OSAExpress6S features.
    • The 1000BASE-T feature supports full-duplex operation exclusively.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
  • Cable Order: A customer-supplied cable is required. The OSA-Express7S 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).
(#0459) OSA-Express7S 25 GbE SR 1.2

OSA-Express7S 25 Gigabit Ethernet (GbE) short reach (SR) 1.2 feature has one PCIe adapter and one port per feature. The port supports channel path identifier (CHPID) type OSD. The 10 GbE feature is designed to support attachment to a multimode fiber 25 gigabits per second (Gbps) Ethernet Local Area Network (LAN) or Ethernet switch capable of 25 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-Express7S and OSA-Express6S features.
  • Prerequisites: None.
  • Corequisites: PCIe I/O drawer (#4021).
  • Compatibility Conflicts:
    • The OSA Express7S 25 GbE feature does not auto-negotiate to a slower speed.
    • The OSA-Express7S 25 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-Express7S and OSAExpress6S features.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
  • 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.
(#0460) OSA-Express7S 25 GbE LR 1.2

OSA-Express7S 25 Gigabit Ethernet (GbE) long reach (LR) 1.2 feature has one PCIe adapter and one port per feature. The port supports channel path identifier (CHPID) type OSD. The 10 GbE feature is designed to support attachment to a multimode fiber 25 gigabits per second (Gbps) Ethernet Local Area Network (LAN) or Ethernet switch capable of 25 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-Express7S and OSA-Express6S features.
  • Prerequisites: None.
  • Corequisites: PCIe I/O drawer (#4021).
  • Compatibility Conflicts:
    • The OSA Express7S 25 GbE feature does not auto-negotiate to a slower speed.
    • The OSA-Express7S 25 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-Express7S and OSAExpress6S features.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
  • 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.
(#0461) FICON Express32S LX

FICON Express 32S 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 8 gigabits per second (Gbps), 16 Gbps, or 32 Gbps depending upon the capability of the attached switch or device. The link speed is auto negotiated, 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 Express32S 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 Express32S LX feature is encryption capable in support of IBM Fibre Channel Endpoint Security (Enablement feature code #1146). The FICON Express32S 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 Express32S 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 Express32S LX feature utilizes a long wavelength (LX) 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. LX may also be referred to as LW by vendors.

  • Minimum: None. At least one I/O feature (FICON) must be present in a server.
  • Maximum: 192.
  • Prerequisites: None.
  • Corequisites: PCIe I/O drawer (#4021).
  • 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 (#4021).
    • The FICON Express32S LX feature does not support auto-negotiation to 1, 2 or 4 Gbps. To avoid performance degradation at extended distance, FICON switches or directors for buffer credit provisioning may be required.
    • For unrepeated distances for FICON Express32S LX refer to Planning for Fiber Optic Links, GA23-1408 available in the Library section of Resource Link: http://www.ibm.com/servers/resourcelink
    • Both ports of the adapter need to be defined as either FC or FCP CHPIDs. A mix of FC and FCP CHPIDs on the same adapter is not supported.
  • 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.
(#0462) FICON Express32S SX

FICON Express32S 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 8 gigabits per second (Gbps), 16 Gbps, or 32 Gbps depending upon the capability of the attached switch or device. The link speed is auto negotiated, 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 Express32S 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 Express32S SX feature is encryption capable in support of IBM Fibre Channel Endpoint Security (Enablement feature code #1146). The FICON Express32S 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 Express32S 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 Express32S 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) must be present in a server.
  • Maximum: 192.
  • Prerequisites: None.
  • Corequisites: PCIe I/O drawer (#4021).
  • 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 (#4021).
    • The FICON Express32S SX feature does not support auto-negotiation to 1, 2 or 4 Gbps. To avoid performance degradation at extended distance, FICON switches or directors for buffer credit provisioning may be required.
    • For unrepeated distances for FICON Express32S SX refer to Planning for Fiber Optic Links, GA23-1408 available in the Library section of Resource Link: http://www.ibm.com/servers/resourcelink
    • Both ports of the adapter need to be defined as either FC or FCP CHPIDs. A mix of FC and FCP CHPIDs on the same adapter is not supported.
  • 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.
(#0546) 8561 RCU A Frame w/o Ht Red

This feature provides a means to order and price return packaging materials for installed machines being replaced by a MT 3931 through new build, Migration Offering or Machine Type Upgrade order. Select when system to be returned is a MT 8561 radiator-cooled machine and does not require a height reduction (#9976). Minimum: 0. Maximum: 1. Prerequisites: None. Corequisites: None. Compatibility Conflicts: Mutually exclusive with #0547, #0548, #0549, #0550, #0551, #0552, #0553, #0554, #0555, #0556, #0557, #0558, #0559, #0560, #0561, #0201, #0202, #0203, and #0204. Customer Setup: No. Limitations: Radiator-cooled MT 8561 A-frame that does not require a height reduction. Field Installable: Yes. Cable Order: N/A.

(#0547) 8561 RCU B Frame w/o Ht Red

This feature provides a means to order and price return packaging materials for installed machines being replaced by a MT 3931 through new build, Migration Offering or Machine Type Upgrade order. Select when system to be returned is a MT 8561 radiator-cooled machine and does not require a height reduction (#9976).

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: Mutually exclusive with #0546, #0548, #0549, #0550, #0551, #0552, #0553, #0554, #0555, #0556, #0557, #0558, #0559, #0560, #0561, #0201, #0202, #0203, and #0204.
  • Customer Setup: No.
  • Limitations: Radiator-cooled MT 8561 B-frame that does not require a height reduction.
  • Field Installable: Yes.
  • Cable Order: N/A.
(#0548) 8561 RCU C Frame w/o Ht Red

This feature provides a means to order and price return packaging materials for installed machines being replaced by a MT 3931 through new build, Migration Offering or Machine Type Upgrade order. Select when system to be returned is a MT 8561 radiator-cooled machine and does not require a height reduction (#9976).

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: Mutually exclusive with #0546, #0547, #0549, #0550, #0551, #0552, #0553, #0554, #0555, #0556, #0557, #0558, #0559, #0560, #0561, #0201, #0202, #0203, and #0204.
  • Customer Setup: No.
  • Limitations: Radiator-cooled MT 8561 C-frame that does not require a height reduction.
  • Field Installable: Yes.
  • Cable Order: N/A.
(#0549) 8561 RCU Z Frame w/o Ht Red

This feature provides a means to order and price return packaging materials for installed machines being replaced by a MT 3931 through new build, Migration Offering or Machine Type Upgrade order. Select when system to be returned is a MT 8561 radiator-cooled machine and does not require a height reduction (#9976).

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: Mutually exclusive with #0546, #0547, #0548, #0550, #0551, #0552, #0553, #0554, #0555, #0556, #0557, #0558, #0559, #0560, #0561, #0201, #0202, #0203, and #0204.
  • Customer Setup: No.
  • Limitations: Radiator-cooled MT 8561 Z-frame that does not require a height reduction.
  • Field Installable: Yes.
  • Cable Order: N/A.
(#0550) 8561 RCU A Frame w/ Ht Red

This feature provides a means to order and price return packaging materials for installed machines being replaced by a MT 3931 through new build, Migration Offering or Machine Type Upgrade order. Select when system to be returned is a MT 8561 radiator-cooled machine and requires a height reduction (#9976).

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: Mutually exclusive with #0546, #0547, #0548, #0549, #0551, #0552, #0553, #0554, #0555, #0556, #0557, #0558, #0559, #0560, #0561, #0201, #0202, #0203, and #0204.
  • Customer Setup: No.
  • Limitations: Radiator-cooled MT 8561 A-frame that requires a height reduction.
  • Field Installable: Yes.
  • Cable Order: N/A.
(#0551) 8561 RCU B Frame w/ Ht Red

This feature provides a means to order and price return packaging materials for installed machines being replaced by a MT 3931 through new build, Migration Offering or Machine Type Upgrade order. Select when system to be returned is a MT 8561 radiator-cooled machine and requires a height reduction (#9976).

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: Mutually exclusive with #0546, #0547, #0548, #0549, #0550, #0552, #0553, #0554, #0555, #0556, #0557, #0558, #0559, #0560, #0561, #0201, #0202, #0203, and #0204.
  • Customer Setup: No.
  • Limitations: Radiator-cooled MT 8561 B-frame that requires a height reduction.
  • Field Installable: Yes.
  • Cable Order: N/A.
(#0552) 8561 RCU C Frame w/ Ht Red

This feature provides a means to order and price return packaging materials for installed machines being replaced by a MT 3931 through new build, Migration Offering or Machine Type Upgrade order. Select when system to be returned is a MT 8561 radiator-cooled machine and requires a height reduction (#9976).

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: Mutually exclusive with #0546, #0547, #0548, #0549, #0550, #0551, #0553, #0554, #0555, #0556, #0557, #0558, #0559, #0560, #0561, #0201, #0202, #0203, and #0204.
  • Customer Setup: No.
  • Limitations: Radiator-cooled MT 8561 C-frame that requires a height reduction.
  • Field Installable: Yes.
  • Cable Order: N/A.
(#0553) 8561 RCU Z Frame w/ Ht Red

This feature provides a means to order and price return packaging materials for installed machines being replaced by a MT 3931 through new build, Migration Offering or Machine Type Upgrade order. Select when system to be returned is a MT 8561 radiator-cooled machine and requires a height reduction (#9976).

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: Mutually exclusive with #0546, #0547, #0548, #0549, #0550, #0551, #0552, #0554, #0555, #0556, #0557, #0558, #0559, #0560, #0561, #0201, #0202, #0203, and #0204.
  • Customer Setup: No.
  • Limitations: Radiator-cooled MT 8561 Z-frame that requires a height reduction.
  • Field Installable: Yes.
  • Cable Order: N/A.
(#0554) 8561 WCU A Frame w/o Ht Red

This feature provides a means to order and price return packaging materials for installed machines being replaced by a MT 3931 through new build, Migration Offering or Machine Type Upgrade order. Select when system to be returned is a MT 8561 water-cooled machine and does not require a height reduction (#9976).

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: Mutually exclusive with #0546, #0547, #0548, #0549, #0550, #0551, #0552, #0553, #0555, #0556, #0557, #0558, #0559, #0560, #0561, #0201, #0202, #0203, and #0204.
  • Customer Setup: No.
  • Limitations: Water-cooled MT 8561 A-frame that does not require a height reduction.
  • Field Installable: Yes.
  • Cable Order: N/A.
(#0555) 8561 WCU B Frame w/o Ht Red

This feature provides a means to order and price return packaging materials for installed machines being replaced by a MT 3931 through new build, Migration Offering or Machine Type Upgrade order. Select when system to be returned is a MT 8561 water-cooled machine and does not require a height reduction (#9976).

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: Mutually exclusive with #0546, #0547, #0548, #0549, #0550, #0551, #0552, #0553, #0554, #0556, #0557, #0558, #0559, #0560, #0561, #0201, #0202, #0203, and #0204.
  • Customer Setup: No.
  • Limitations: Water-cooled MT 8561 B-frame that does not require a height reduction.
  • Field Installable: Yes.
  • Cable Order: N/A.
(#0556) 8561 WCU C Frame w/o Ht Red

This feature provides a means to order and price return packaging materials for installed machines being replaced by a MT 3931 through new build, Migration Offering or Machine Type Upgrade order. Select when system to be returned is a MT 8561 water-cooled machine and does not require a height reduction (#9976).

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: Mutually exclusive with #0546, #0547, #0548, #0549, #0550, #0551, #0552, #0553, #0554, #0555, #0557, #0558, #0559, #0560, #0561, #0201, #0202, #0203, and #0204.
  • Customer Setup: No.
  • Limitations: Water-cooled MT 8561 C-frame that does not require a height reduction.
  • Field Installable: Yes.
  • Cable Order: N/A.
(#0557) 8561 WCU Z Frame w/o Ht Red

This feature provides a means to order and price return packaging materials for installed machines being replaced by a MT 3931 through new build, Migration Offering or Machine Type Upgrade order. Select when system to be returned is a MT 8561 water-cooled machine and does not require a height reduction (#9976).

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: Mutually exclusive with #0546, #0547, #0548, #0549, #0550, #0551, #0552, #0553, #0554, #0555, #0556, #0558, #0559, #0560, #0561, #0201, #0202, #0203, and #0204.
  • Customer Setup: No.
  • Limitations: Water-cooled MT 8561 Z-frame that does not require a height reduction.
  • Field Installable: Yes.
  • Cable Order: N/A.
(#0558) 8561 WCU A Frame w/ Ht Red

This feature provides a means to order and price return packaging materials for installed machines being replaced by a MT 3931 through new build, Migration Offering or Machine Type Upgrade order. Select when system to be returned is a MT 8561 water-cooled machine and requires a height reduction (#9976).

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: Mutually exclusive with #0546, #0547, #0547, #0549, #0550, #0551, #0552, #0553, #0554, #0555, #0556, #0557, #0559, #0560, #0561, #0201, #0202, #0203, and #0204.
  • Customer Setup: No.
  • Limitations: Water-cooled MT 8561 A-frame that requires a height reduction.
  • Field Installable: Yes.
  • Cable Order: N/A.
(#0559) 8561 WCU B Frame w/ Ht Red

This feature provides a means to order and price return packaging materials for installed machines being replaced by a MT 3931 through new build, Migration Offering or Machine Type Upgrade order. Select when system to be returned is a MT 8561 water-cooled machine and requires a height reduction (#9976).

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: Mutually exclusive with #0546, #0547, #0547, #0549, #0550, #0551, #0552, #0553, #0554, #0555, #0556, #0557, #0558, #0560, #0561, #0201, #0202, #0203, and #0204.
  • Customer Setup: No.
  • Limitations: Water-cooled MT 8561 B-frame that requires a height reduction.
  • Field Installable: Yes.
  • Cable Order: N/A.
(#0560) 8561 WCU C Frame w/ Ht Red

This feature provides a means to order and price return packaging materials for installed machines being replaced by a MT 3931 through new build, Migration Offering or Machine Type Upgrade order. Select when system to be returned is a MT 8561 water-cooled machine and requires a height reduction (#9976).

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: Mutually exclusive with #0546, #0547, #0547, #0549, #0550, #0551, #0552, #0553, #0554, #0555, #0556, #0557, #0558, #0559, #0561, #0201, #0202, #0203, and #0204.
  • Customer Setup: No.
  • Limitations: Water-cooled MT 8561 C-frame that requires a height reduction.
  • Field Installable: Yes.
  • Cable Order: N/A.
(#0561) 8561 WCU Z Frame w/ Ht Red

This feature provides a means to order and price return packaging materials for installed machines being replaced by a MT 3931 through new build, Migration Offering or Machine Type Upgrade order. Select when system to be returned is a MT 8561 water-cooled machine and requires a height reduction (#9976).

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: Mutually exclusive with #0546, #0547, #0547, #0549, #0550, #0551, #0552, #0553, #0554, #0555, #0556, #0557, #0558, #0559, #0560, #0201, #0202, #0203, and #0204.
  • Customer Setup: No.
  • Limitations: Water-cooled MT 8561 Z-frame that requires a height reduction.
  • Field Installable: Yes.
  • Cable Order: N/A.
(#0644) IBM Virtual Flash Memory (VFM)

Provides up to 6.0 TB of virtual flash memory in 512GB increments.

  • Minimum: 0.
  • Maximum: 12. 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.
  • Cable Order: N/A.
(#0648) Bulk Power Assembly (BPA)

Provides universal input of three phase 200-480v AC power. There are configuration restrictions when choosing bulk power. See the Installation manual for Physical Planning (IMPP), and the Technical Delivery Assessment (TDA) checklist for details.

  • Minimum: 0.
  • Maximum: 2 - one in the A frame and if present, one in the B frame or the C frame.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: Mutually exclusive with iPDU.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: No.
  • Cable Order: N/A.
(#0667) Max39

Processor drawer physical capacity marker. The Max39 has a maximum configurable capacity of 39 cores supporting the z/OS, z/VM, z/VSE, 21 st Century Software VSE n, z/TPF, and Linux on IBM Z operating systems.

  • Minimum: 0.
  • Maximum: 1
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes.
  • Cable Order: N/A.
(#0668) Max82

Processor drawer physical capacity marker. The Max82 has a maximum configurable capacity of 82 cores supporting the z/OS, z/VM, z/VSE, 21 st Century Software VSE n, z/TPF, and Linux on IBM Z operating systems.

  • Minimum: 0.
  • Maximum: 1
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes.
  • Cable Order: N/A.
(#0669) Max125

Processor drawer physical capacity marker. The Max125 has a maximum configurable capacity of 125 cores supporting the z/OS, z/VM, z/VSE, 21 st Century Software VSE n, z/TPF, and Linux on IBM Z operating systems.

  • Minimum: 0.
  • Maximum: 1
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes.
  • Cable Order: N/A.
(#0670) Max168

Processor drawer physical capacity marker. The Max168 has a maximum configurable capacity of 168 cores supporting the z/OS, z/VM, z/VSE, 21 st Century Software VSE n, z/TPF, and Linux on IBM Z operating systems.

  • Minimum: 0.
  • Maximum: 1
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes.
  • Cable Order: N/A.
(#0671) Max200

Processor drawer physical capacity marker. The Max200 has a maximum configurable capacity of 200 cores supporting the z/OS, z/VM, z/VSE, 21 st Century Software VSE n, z/TPF, and Linux on IBM Z operating systems.

  • Minimum: 0.
  • Maximum: 1
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: Not available in China.
  • Field Installable: Yes.
  • Cable Order: N/A.
(#0843) 32GB USB Load Media

This is an optional feature which replaces DVD/CD to provide the ability to load data via USB.

  • Minimum: 0.
  • Maximum: 99.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: Intended for ONE use.
  • Field Installable: Yes.
  • Cable Order: N/A.
(#0846) No Physical Media

This is an optional feature which replaces DVD/CD and will provide the ability to load data electronically with no physical media required.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisite: None.
  • Compatibility Conflicts: None known.
  • Customer setup: No.
  • Limitations: None known.
  • Field Installable: Yes.
  • Cable Orders: N/A.
(#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.
  • Cable Order: N/A.
(#0851) 4770 TKE Crypto Adapter

The stand-alone crypto adapter is ordered when you are doing an upgrade to #0085/0087 TKE Rack Mount or #0086/0088TKE.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: Your current workstation is a feature code #0085/0087 TKE Rack Mount or #0086/0088 TKE.
  • Corequisite: None.
  • 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: N/A.
(#0882) TKE 10.0 LIC

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

  • Minimum: 0.
  • Maximum: 10.
  • Prerequisites: TKE workstation (#0057 or 0058).
  • Corequisites: CPACF (#3863) or Crypto Express (#0908, #0909)
  • Compatibility Conflicts:
  • Customer setup: No.
  • Limitations: Loose piece MES upgrades are not allowed in China due to country restrictions.
  • Field Installable: Yes. Parts removed as a result of feature change become the property of IBM.
  • Cable Order: N/A.
(#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 Express8S 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 Express8S feature that is defined as an IBM Enterprise PKCS #11 (EP11) coprocessor. The TKE 10.0 level of LIC (#0882) 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 10.0 workstation, and 20 smart cards. Minimum: 0. Maximum: 20. Prerequisites: CP Assist for Cryptographic Function (#3863) and Crypto Express8S (#0908 or 0909). Corequisites: TKE workstation (#0057 or 0058) with 10/0 level of LIC (#0882) 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.

(#0900) TKE addl smart cards

Feature code #0900 provides a 5 pack of 2 blank smart cards, yielding a total of 10 blank smart cards.

  • Minimum: 0.
  • Maximum: 99.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None Known.
  • Customer setup: No.
  • Limitations: None known.
  • Field Installable: Yes.
  • Cable Orders: N/A.
(#0908) Crypto Express8S (2 HSM)

The Crypto Express8S feature is designed to satisfy IBM Z server security requirements. It contains two PCIe HSMs which can each 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 modules, which are contained in the Crypto Express8S feature, are designed to conform to the Federal Information Processing Standard (FIPS) 140-3 at Level 4. It supports User Defined Extension(UDX) services to implement cryptographic functions and algorithms (when defined as an IBM CCA coprocessor).

  • Minimum: None or one.
  • Maximum: 30 cards, 60 total HSMs.
  • Prerequisites: CP Assist for Cryptographic Function (CPACF) (#3863).
  • Corequisites: TKE workstation (#0057 or 0058) is optional when used to manage a Crypto Express8S feature that is defined as a CCA coprocessor in normal mode but is mandatory when used to manage a Crypto Express8S 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: Loose piece MES upgrades are not allowed in China due to country restrictions.
  • Field Installable: Yes. Parts removed as a result of feature change become the property of IBM.
  • Cable Order: None.
(#0909) Crypto Express8S (1 HSM)

The Crypto Express8S feature is designed to satisfy IBM Z server security requirements. It contains one PCIe HSM 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 Express8S feature, is designed to conform to the Federal Information Processing Standard (FIPS) 140-3 at Level 4. It supports User Defined Extension(UDX) services to implement cryptographic functions and algorithms (when defined as an IBMCCA coprocessor).

  • Minimum: None or two. An initial order is two features, one thereafter.
  • Maximum: 16 cards, 16 total HSMs.
  • Prerequisites: CP Assist for Cryptographic Function (CPACF) (#3863).
  • Corequisites: TKE workstation (#0057 or 0058) is optional when used to manage a Crypto Express8S feature that is defined as a CCA coprocessor in normal mode but is mandatory when used to manage a Crypto Express8S 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: Loose piece MES upgrades are not allowed in China due to country restrictions.
  • Field Installable: Yes. Parts removed as a result of feature change become the property of IBM.
  • Cable Order: None.
(#1021) STP enablement

The STP feature provides 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) and to the operating system images running on the hypervisor. For time synchronization across servers, 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, (#0176) Integrated Coupling Adapter (ICA-SR1.1), or Coupling Express2 LR adapter (#0434).
  • 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.
(#1146) Endpoint Security Enablement

IBM Fibre Channel Endpoint Security is an end-to-end solution that helps ensure all data flowing on Fibre Channel links within and across datacenters flows between trusted entities. Feature code #1146 turns on the Fibre ChannelEndpoint Security panels on the HMC so set-up can be done.

  • Minimum: 0.
  • Maximum: 192 features (384 ports).
  • Prerequisites: CPACF enablement (#3863).
  • Corequisites: FICON Express32S (#0461 or 0462) or FICON Express16SA (#0436 or #0437).
  • Compatibility Conflicts: None.
  • Customer Setup: No.
  • Limitations: Not available in China and Russia due to country restrictions.
  • Field Installable: Yes.
  • Cable Order: N/A.
(#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. (#1955) 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, 21 st Century Software VSE n, z/TPF, and Linux on IBM Z operating systems.

  • Minimum: 0.
  • Maximum: 39.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes.
  • Cable Orders: N/A.
(#1955) 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, 21 st Century Software VSE n, z/TPF, Linux on IBM Z (including KVM) operating systems.

  • Minimum: 0.
  • Maximum: 39.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Field Installable: Yes.
  • Cable Orders: N/A.
(#1956) 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, 21 st Century Software VSE n, z/TPF, and Linux on IBM Z (including KVM) operating systems.

  • Minimum: 0.
  • Maximum: 39.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Field Installable: Yes.
  • Cable Orders: N/A.
(#1957) 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, 21 st Century Software VSE n, z/TPF, and Linux on IBM Z (including KVM) operating systems.

  • Minimum: 0.
  • Maximum: 39.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Field Installable: Yes.
  • Cable Orders: N/A.
(#1958) 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, 21 st Century Software VSE n, z/TPF, and Linux on IBM Z (including KVM) operating systems.

  • Minimum: 0.
  • Maximum: 200.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Field Installable: Yes.
  • Cable Orders: N/A.
(#1959) 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 z16.

  • Minimum: 0.
  • Maximum: 200.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Field Installable: Yes.
  • Cable Orders: N/A.
(#1960) 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: 200.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Field Installable: Yes.
  • Cable Orders: N/A.
(#1961) 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: 132.
  • 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.
  • Cable Orders: N/A.
(#1962) Unassigned Integrated Facility for Linux (uIFL)

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

  • Minimum: 0.
  • Maximum: 199.
  • Prerequisites: Prerequisites: One CP4 (#1955), CP5 (#1956), CP6 (#1957), CP7 (#1958), IFL (#1959), or ICF (#1960).
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Field Installable: Yes.
  • Cable Orders: N/A.
(#1963) 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 (#1955), CP5 (#1956), CP6 (#1957), CP7 (#1958), IFL (#1959), or ICF (#1960).
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Field Installable: Yes.
  • Cable Orders: N/A.
(#1974) Unassigned Internal Coupling Facility (uICF)

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

  • Minimum: 0.
  • Maximum: 200.
  • Prerequisites: Prerequisites: One CP4 (#1955), CP5 (#1956), CP6 (#1957), CP7 (#1958), IFL (#1959), or ICF (#1960).
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Field Installable: Yes.
  • Cable Orders: N/A.
(#1975) Unassigned IBM z Integrated Information Processor (uzIIP)

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

  • Minimum: 0.
  • Maximum: 132.
  • Prerequisites: Prerequisites: One CP4 (#1955), CP5 (#1956), CP6 (#1957), CP7 (#1958), IFL (#1959), ICF (#1960) or zIIP (#1961).
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Field Installable: Yes.
  • Cable Orders: N/A.
(#2981) CPC1 Reserve - Reserves space for IO drawer sequencing.

Customers must follow requirements as defined in the Installation Manual for Physical Planning (IMPP) on Resource Link for usage of this feature within warranty. Requirements include statements regarding weight, airflow, power draw, cabling, and positioning of equipment to be added into this reserved space.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: 1 CPC drawer.
  • Corequisite: None.
  • Compatibility Conflicts: Customers should assess growth requirements of their equipment prior to ordering this feature. Once this space is reserved for separately installed components, it will prevent future MES's of IO drawers into that space. The purpose of this feature is to reserve space for a future CPC drawer MES.
  • Customer setup: No. IBM Z installer must install the IBM Z shipped hardware prior to the Customer installing any separate components.
  • Limitations: See full description embedded to IBM z16 IMPP in Resource Link: http://www.ibm.com/servers/resourcelink/
  • Field Installable: Yes.
  • Cable Order: N/A.
(#2982) CPC2 Reserve - Reserves space for IO drawer sequencing.

Customers must follow requirements as defined in the Installation Manual for Physical Planning (IMPP) on Resource Link for usage of this feature within warranty. Requirements include statements regarding weight, airflow, power draw, cabling, and positioning of equipment to be added into this reserved space.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: 2 or fewer CPC drawers.
  • Corequisite: None.
  • Compatibility Conflicts: Customers should assess growth requirements of their equipment prior to ordering this feature. Once this space is reserved for separately installed components, it will prevent future MES's of IO drawers into that space. The purpose of this feature is to reserve space for a future CPC drawer MES.
  • Customer setup: No. IBM Z installer must install the IBM Z shipped hardware prior to the Customer installing any separate components.
  • Limitations: See full description embedded to IBM z16 IMPP in Resource Link: http://www.ibm.com/servers/resourcelink/
  • Field Installable: Yes.
  • Cable Order: N/A.
(#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: Bulk Power Assembly (#0648).
  • Corequisites: May require additional 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.
(#3100) Lift tool kit

This feature supplies new rails to permit CPC drawers to slide in/out of the IBM z16 frame. It is selected to assist with repairs and upgrades. assist with repairs and upgrades.

  • 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.
(#3101) Extension ladder

This feature supplies an extension ladder to help service the top of the machine. It is selected to assist with repairs and upgrades.

  • 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.
(#3393) Fill and Drain kit

This feature supplies hoses as well as the fill/drain tool that's needed for initial installation as well as for service activities.

  • 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.
(#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 confidentiality: 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 z16'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 IBM z16 CPACF instructions for SHA-3 hashing, TRNG (True Random Number Generation), Message-Security-Assist extension 9, and Improved performance of AES GCM encryption. New IBM z16 CPACF counter support, which provides a means for guests to track cryptographic compliance and instruction usage.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisite: Crypto Express8S (#0908 or #0909) or Crypto Express7S (#0898 or 0899) or Crypto Express6S (#0893).
  • Compatibility Conflicts: None known.
  • Customer setup: No.
  • Limitations: None.
  • Field Installable: Yes.
(#4023) 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 Express8S), the storage area network (FICON Express32S and zHyperLink Express1.1), the Ethernet local area network (OSA-Express7S 1.2, and RoCE Express3), and Coupling Express2 LR. The PCIe+ I/O drawer contains16 I/O slots. The number of PCIe+ I/O drawers is automatically determined by the number of Crypto Express8S, FICON Express32S, zHyperLink Express1.1, OSA-Express7S 1.2, RoCE Express3, or Coupling Express2 LR features ordered.

  • Minimum: 0.
  • Maximum: 12 for PDU-based systems and 10 for BPA based systems.
  • 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.
(#4040) 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.
(#4041) B 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.
(#4042) B Frame -- No cooling
  • 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.
(#4043) Z Frame
  • 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.
(#4044) C Frame
  • 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.
(#6798) Total SRB Months Ordered

eConfig applies this feature code during machine type upgrade pricing orders if there is less than a quantity of full year(s) of SRB record price required to be charged.

  • Minimum: 1.
  • Maximum: 11.
  • Prerequisites: Boost Authorization (#9930).
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes.
  • Cable Order: N/A.
(#6799) Total SRB Years Ordered

eConfig applies this feature code during machine type upgrade pricing orders if there is less than a quantity of full year(s) of SRB record price required to be charged.

  • Minimum: 1.
  • Maximum: 5.
  • Prerequisites: Boost Authorization (#9930).
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes.
  • Cable Order: N/A.
(#6802) Sys Recovery Boost Record

This feature code will enable temporary activation of additional physical zIIP processors to be used in conjunction with System Recovery Boost.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: Boost Authorization (#9930).
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes.
  • Cable Order: N/A.
(#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) Records Ordered.
  • Prerequisites: Capacity Back UP (CBU) Records Ordered (#6818).
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes.
  • Cable Order: N/A.
(#6806) PRC 1 MSU day

Pricing feature for OOCOD in the PRC (#9904) 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: PRC Tokens Authorization (#9904).
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: Restricted to Peoples Republic of China.
  • Field Installable: Yes.
  • Cable Order: N/A.
(#6807) PRC 100 MSU days

Pricing feature for OOCOD in the PRC (#9904) 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: PRC Tokens Authorization (#9904).
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: Restricted to Peoples Republic of China.
  • Field Installable: Yes.
  • Cable Order: N/A.
(#6808) PRC 10000 MSU days

Pricing feature for OOCOD in the PRC (#9904) 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: PRC Tokens Authorization (#9904).
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: Restricted to Peoples Republic of China.
  • Field Installable: Yes.
  • Cable Order: N/A.
(#6809) PRC 1 IFL day

Pricing feature for OOCOD in the PRC (#9904) 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: PRC Tokens Authorization (#9904).
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: Restricted to Peoples Republic of China.
  • Field Installable: Yes.
  • Cable Order: N/A.
(#6810) PRC 100 IFL days

Pricing feature for OOCOD in the PRC (#9904) 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: 250.
  • Prerequisites: PRC Tokens Authorization (#9904).
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: Restricted to Peoples Republic of China.
  • Field Installable: Yes.
  • Cable Order: N/A.
(#6811) PRC 1 ICF day

Pricing feature for OOCOD in the PRC (#9904) 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: PRC Tokens Authorization (#9904).
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: Restricted to Peoples Republic of China.
  • Field Installable: Yes.
  • Cable Order: N/A.
(#6812) PRC 100 ICF days

Pricing feature for OOCOD in the PRC (#9904) 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: 250.
  • Prerequisites: PRC Tokens Authorization (#9904).
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: Restricted to Peoples Republic of China.
  • Field Installable: Yes.
  • Cable Order: N/A.
(#6813) PRC 1 zIIP day

Pricing feature for OOCOD in the PRC (#9904) 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: PRC Tokens Authorization (#9904).
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: Restricted to Peoples Republic of China.
  • Field Installable: Yes.
  • Cable Order: N/A.
(#6814) PRC 100 zIIP days

Pricing feature for OOCOD in the PRC (#9904) 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: 250.
  • Prerequisites: PRC Tokens Authorization (#9904).
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: Restricted to Peoples Republic of China.
  • Field Installable: Yes.
  • Cable Order: N/A.
(#6815) PRC 1 SAP day

Pricing feature for OOCOD in the PRC (#9904) 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: PRC Tokens Authorization (#9904).
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: Restricted to Peoples Republic of China.
  • Field Installable: Yes.
  • Cable Order: N/A.
(#6816) PRC 100 SAP days

Pricing feature for OOCOD in the PRC (#9904) 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: 250.
  • Prerequisites: PRC Tokens Authorization (#9904).
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: Restricted to Peoples Republic of China.
  • Field Installable: Yes.
  • Cable Order: N/A.
(#6817) Total CBU Years Ordered

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

  • Minimum: 1.
  • Maximum: Five (5).
  • Prerequisites: CBU Records Ordered (#6818).
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: Not applicable.
  • Limitations: None.
  • Field Installable: Yes.
  • Cable Order: N/A.
(#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.
  • Cable Order: N/A.
(#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: CBU Records Ordered (#6818).
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes.
  • Cable Order: N/A.
(#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: CBU Records Ordered (#6818).
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes.
  • Cable Order: N/A.
(#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: CBU Records Ordered (#6818).
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes.
  • Cable Order: N/A.
(#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: CBU Records Ordered (#6818).
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes.
  • Cable Order: N/A.
(#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: CBU Records Ordered (#6818).
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes.
  • Cable Order: N/A.
(#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: CBU Records Ordered (#6818).
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes.
  • Cable Order: N/A.
(#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: CBU Records Ordered (#6818).
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes.
  • Cable Order: N/A.
(#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: CBU Records Ordered (#6818).
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes.
  • Cable Order: N/A.
(#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: CBU Records Ordered (#6818).
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes.
  • Cable Order: N/A.
(#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: CBU Records Ordered (#6818).
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes.
  • Cable Order: N/A.
(#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: CBU Records Ordered (#6818).
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: No.
  • Limitations: None.
  • Field Installable: Yes.
  • Cable Order: N/A.
(#7805) Flex Cap Perpetual License

This feature is ordered to record, in the machine data, the type of use license the for which customer has contracted. Under a perpetual license the customer pays once, and then retains the rights to the capacity (for the life of the current machine and future upgrades along qualified upgrade paths, N-1, N-2). Minimum: 0. Maximum: 1. Prerequisites: None. Corequisites: Flexible Capacity Record (#0376), Flex Capacity Authorization (#9933). Compatibility Conflicts: #7806, Flexible Cap Term License. Customer Setup: Not applicable. Limitations: None. Field Installable: N/A. Cable Order: N/A

(#7806) Flexible Cap Term License

This feature is ordered to record, in the machine data, the type of use license for which the customer has contracted. Under a term license the customer pays for the capacity for a period of 1 year and may buy up to 5 years at one time. Any unused term carries forward to qualified upgrades. Minimum: 0. Maximum: 1. Prerequisites: None. Corequisites: Flexible Capacity Record (#0376), Flex Capacity Authorization (#9933). Compatibility Conflicts: #7805, Flexible Cap Perpetual License. Customer Setup: Not applicable. Limitations: None. Field Installable: N/A. Cable Order: N/A

(#7816) Top exit cabling w/o Tophat

When top exit cabling without the tophat 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, B, C, or Z frame. Top exit I/O cabling applies to all of your fiber optic cables (FICON Express, OSA-Express, ICA SR 1.1, RoCE Express, zHyperLink Express, and Coupling Express2 LR) as well as your copper cables for the OSA-Express 1000BASE-T Ethernet features.

Top exit 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 cabling w/o Tophat (#7816) is selected, the power cord selection can be top exit or bottom exit. In a non-raised floor environment, if Basic Top exit cabling is selected then a top exit 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: Top exit I/O power cord.
  • 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: Cabling is a customer responsibility.
(#7898) Top exit cabling w/Top Hat

When top exit 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, B, C, or Z frame. Top exit I/O cabling applies to all of your fiber optic cables (FICON Express, OSA-Express, ICA SR1.1, RoCE Express, zHyperLink Express, and Coupling Express2 LR) as well as your copper cables for the OSA-Express 1000BASE-T Ethernet features.

Top exit 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 cabling w/Top Hat (#7898) 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: 4.
  • Prerequisites: None.
  • Corequisites: Top exit I/O power cord.
  • 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: Cabling is a customer responsibility.
(#7899) Bottom exit cabling

When bottom exit 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 bottom of the frame, either the A, B, C, or Z frame. Bottom exit cabling applies to all of your fiber optic cables (FICON Express, OSA-Express, ICA SR1.1, RoCE Express, zHyperLink Express, and Coupling Express2 LR) as well as your copper cables for the OSA-Express 1000BASE-T Ethernet features.

Bottom exit 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.

In a raised floor environment, if Bottom exit cabling (#7899) is selected, the power cord selection can be top exit or bottom exit. In a non-raised floor environment, if Bottom exit cabling is selected then a bottom exit 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: Bottom exit power cord.
  • 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: Cabling is a customer responsibility.
(#7998) Non-Raised Floor Support

This feature will be used for information purposes to issue warning messages where needed, and to assist in the correct selection of Earthquake Kits, and IO Cabling support options.

  • Minimum: 0.
  • Maximum: 1 (for a two-frame system).
  • Prerequisites: None.
  • Corequisites: Top exit cabling (#7816 or #7898) and a top exit power cord.
  • Compatibility Conflicts: Mutually exclusive with water cooling.
  • 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.
  • Cable Order: N/A.
(#8014) 19 in Earthquake Kit, RF

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.

  • Minimum: 0.
  • Maximum: 4.
  • Prerequisites: None.
  • Corequisites: A Frame Radiator (#4040) and C Frame (#4044).
  • Compatibility Conflicts: Mutually exclusive with features #7998 and #8015.
  • Customer setup: No.
  • Limitations: None known.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
  • Cable Order: N/A.
(#8015) 19 in Earthquake Kit, NRF

This feature applies to a non 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.

  • Minimum: 0.
  • Maximum: 4.
  • Prerequisites: None.
  • Corequisites: A Frame Radiator (#4040) and C Frame (#4044).
  • Compatibility Conflicts: Mutually exclusive with features #8014.
  • Customer setup: No.
  • Limitations: None known.
  • Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
  • Cable Order: N/A.
(#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 (CoD) Buying (#9900).
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: Not applicable.
  • Limitations: None.
  • Field Installable: Yes.
  • Cable Order: N/A.
(#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 (CoD) Buying (#9900).
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: Not applicable.
  • Limitations: None.
  • Field Installable: Yes.
  • Cable Order: N/A.
(#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.
  • Cable Order: N/A.
(#9904) PRC Tokens Authorization

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

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: PRC Tokens (#6803).
  • Corequisites: None.
  • Compatibility Conflicts: None known.
  • Customer Setup: Not applicable.
  • Limitations: None.
  • Field Installable: Yes.
  • Cable Order: N/A.
(#9910) CBU Authorization

This feature enables the purchase of Capacity back up (CBU). This feature is generated when CBU Records Ordered (#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: CBU Records Ordered (#6818).
  • Compatibility Conflicts: None known.
  • Customer Setup: Not applicable.
  • Limitations: None.
  • Field Installable: Yes.
  • Cable Order: N/A.
(#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.
  • Cable Order: N/A.
(#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.
  • Cable Order: N/A.
(#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.
  • Cable Order: N/A.
(#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.
  • Cable Order: N/A.
(#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.
  • Cable Order: N/A.
(#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.
  • Cable Order: N/A.
(#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.
  • Cable Order: N/A.
(#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.
  • Cable Order: N/A.
(#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.
  • Cable Order: N/A.
(#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.
  • Cable Order: N/A.
(#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.
  • Cable Order: N/A.
(#9930) Boost Authorization

This feature is ordered to enable the ordering of Sys Recovery Boost Record (#6802). It drives the necessary contracts to use the Boost Record.

  • Minimum: 0.
  • Maximum: 1.
  • Prerequisites: None.
  • Corequisites: Sys Recovery Boost Record (#6802).
  • Compatibility Conflicts: None known.
  • Customer Setup: Not applicable.
  • Limitations: None.
  • Field Installable: Yes.
  • Cable Order: N/A.
(#9932) TFP for zHW Authorization

Used to initiate the contract for electronic delivery of Tailored Fit Pricing(TFP). Minimum: 0. Maximum:1. Prerequisites: Feature #9900 and #9896. Corequisites: None. Compatibility Conflicts: None known. Customer Setup: No. Limitations: NOT available in People's Republic of China. Field Installable: N/A. Cable Order: N/A.

(#9933) Flex Capacity Authorization

This feature is ordered to enable the ordering of the Flexible Capacity Record (#0376). It drives the necessary contracts to use the Flexible Capacity Record within the terms of the Flexible Capacity for Cyber Resiliency feature offering. Minimum: 0. Maximum: 1. Prerequisites: None. Corequisites: Flexible Capacity Record (#0376). Compatibility Conflicts: None known. Customer Setup: Not applicable. Limitations: None. Field Installable: N/A. Cable Order: N/A.

(#9975) Height reduction for shipping

This feature is required if it is necessary to reduce the shipping height of the IBM z16. 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.
  • Customer Setup: Not applicable.
  • Limitations: See corequisites above.
  • Field Installable: N/A.
  • Cable Order: N/A.
(#9976) Frame height reduction for return

This is for conversions from a IBM z14 (3906) or a IBM z15 (8561) to an IBM z16 (3931) only. The frame height reduction provides then tools and instructions to reduce the height of a IBM z14 or IBM z15 when returned to IBM on an upgrade to an IBM z16 from a IBM z14 or IBM z15.

  • 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.
  • Customer Setup: Not applicable.
  • Limitations: See corequisites above.
  • Field Installable: N/A.
  • Cable Order: N/A.


Back to topBack to top

Accessories

Top rule

Not applicable.

Customer replacement parts

Not applicable.



Back to topBack to top

Supplies

Top rule

Not applicable.

Supplemental media

Not applicable.



Back to topBack to top

Trademarks

Top rule

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

Terms of use

IBM products and services which are announced and available in your country can be ordered under the applicable standard agreements, terms, conditions, and prices in effect at the time. IBM reserves the right to modify or withdraw this Sales Manual at any time without notice. This Sales Manual is provided for your information only. Additional terms of use are located at

Terms of use


© IBM Corporation 2022.