Family 3931+02 IBM LinuxONE Emperor 4

IBM Latin America Sales Manual
Revised: September 13, 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-LA1 2022-09-13 2022-09-14 - -


Back to topBack to top

Abstract

Top rule

CEOs see sustainability as the number one challenge of the next two to three years as their businesses continue their digital transformation. Improving IT efficiency is an opportunity for businesses as it is estimated that data centers globally already use 200 to 250 TW of electricity, about 1% of total electricity consumed.(1)As data and transaction volumes grow and as new cyber threats are addressed, those numbers will only get bigger.

Why? Because modern infrastructure has been largely commoditized. LinuxONE Emperor 4 is built at a cost point to deliver core functionality, which means whether you are trying to manage growth in data, growth in transactions, or deliver advanced functionality through new software, you can add more servers and that equals more energy. This model is simply not sustainable. A better approach is needed.

The LinuxONE Emperor 4 delivers an optimized architecture built to handle the multi-workload needs of a modern scalable digital business with the highest quality of service and the utmost efficiency. Powered by up to 200 high-performance Telum processors, the LinuxONE Emperor 4 delivers massive scalability to support hundreds of workloads in a single system, doing the work of 2000 cores of the compared x86 servers.(2)The Telum processor also features additional compute resources for dedicated workloads such as on-chip AI processing, and dedicated crypto processors that deliver protection at speed and scale. So, what does LinuxONE deliver for your business?

Support your sustainability ambitions with IT efficiency

The optimized architecture in LinuxONE enables you to grow workloads and add advanced IT functionality with a negligible increase in energy usage. It provides better performance with fast cores (5.2 GHz), larger caches, and more of them, on-chip accelerations, like compression, encryption, and AI, hardware optimizations for Java, and specialized I/O processors. It also resolves complexity and optimizes queries by enabling big databases to be held on a single server without creating shards.

That's why many businesses, including those like Plastic Bank and Newlight Technologies that are known for sustainable practices, leverage LinuxONE at the core of their businesses Deliver continuous service at scale

LinuxONE handles data and transactions at massive scale, with the ability to vary capacity on demand to reflect fluctuating business volumes and the ability to prioritize resources according to the business value of each workload. Protect data and apps critical to business

LinuxONE features confidential computing that isolates hundreds of workloads in a single system to protect against internal and external threats and with pervasive encryption, including quantum-safe technologies, to protect data against current and future threats, in a system that can run over 20 billion secure transactions per day.(3)

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.

  • With the new Crypto Express8S (CEX8S), LinuxONE Emperor 4 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.(4)
  • Discovering where and what kind of cryptography is being used is a key first step along the journey to quantum-safety. LinuxONE Emperor 4 provides new instrumentation that can be used to track cryptographic instruction execution in the CP Assist for Cryptographic Functions (CPACF).
  • The new 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.

For these reasons many businesses in the emerging digital assets market are turning to LinuxONE to protect their business and their customers. LinuxONE Emperor 4 is a quantum-safe system, protected by quantum-safe technology across multiple layers of firmware. Quantum-safe secure boot technology helps protect LinuxONE Emperor 4 firmware from quantum attacks through a built-in dual signature scheme with no configuration changes required for enablement.(4)

Predict and automate with on-chip AI acceleration

Decision velocity means delivering insights faster to make decisions to help identify new business opportunities, improve customer experience, and reduce operational risk.

  • The on-chip LinuxONE Emperor 4 Integrated Accelerator for AI is designed for high-speed 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.

Whether you are a start-up or one of the world's largest enterprises, now there is a LinuxONE solution for you, on premises or in the IBM Cloud. LinuxONE can help you respond to the ever-changing demands of digital business, to protect against cyberattacks and help you move forward with your sustainability goals. And, as part of an open hybrid cloud platform, LinuxONE gives you more flexibility and choice as you optimize workload building and deployment to meet the needs of your business.
Note: (2) IBM internal tests show that when running IBM WebSphere and Db workloads, IBM LinuxONE Emperor 4 requires 16 times fewer cores than the compared x86 servers. If you scale this up to a complete IT solution, this means when running this workload, the LinuxONE Emperor 4 Max 125 would be doing the work of about 2000 cores of the compared x86 servers.

DISCLAIMER: This is an IBM internal study designed to replicate a typical IBM customer workload usage in the marketplace. Results may vary. The core consolidation study targeted comparison of the following IBM LinuxONE and x86 servers: An IBM LinuxONE Emperor 4 Max 125 system consists of three CPC drawers containing 125 configurable processor units (IFLs or zIIPs) and two I/O drawers to support both network and external storage. Lenovo ThinkSystem SR650 (2U) with two 2nd Gen Intel()Xeon()Platinum processors 2.1 GHz, 16 cores per CPU. Both the x86-based and LinuxONE solutions had access to the same storage array. The workloads consisted of a transactional application running on WebSphere Application Server and IBM Db2 simulating core online banking functions. The actual test results were extrapolated to the stated above x86 servers using IDC QPI metrics and IBM sizing methodology using the following assumptions on a typical IT environment of a banking client using x86 servers. The production IT environment has 16 x86 servers running at 50% average utilization. There are 48 x86 servers in the nonproduction IT environments: development (4 environments with 2 servers each, 8 servers total), development test environment (4 servers), system integration test environment (8 servers), performance test environment (16 servers), user acceptance test environment (4 servers), production fix test environment (8 servers). A typical average CPU utilization is 7% across all non-production environments. An equivalent LinuxONE Emperor 4 solution requires a single Max 125 server running at 85% average utilization across all IT environments separated using LPAR technology.
Note: (3) With IBM LinuxONE Emperor 4, execute up to 20 billion HTTPS transactions per day with OLTP microservice applications running on Red Hat OpenShift Container Platform

DISCLAIMER: Performance result is extrapolated from IBM internal tests running in an IBMLinuxONE Emperor 4LPAR with 24 dedicated cores, 560 GB memory and DASD storage the Acme Air microservice benchmark (https://github.com/blueperf/acmeair-mainservice-java) onRed HatOpenShift Container Platform (RHOCP) 4.9 using RHEL 8.4 KVM. On 4 RHOCP Compute nodes 4 Acme Air instances were running in parallel, each driven remotely from JMeter 5.2.1 with 384 parallel users. The KVM guests with RHOCP Compute nodes were configured with 12 vCPUs and 64 GB memory each. The KVM guests with RHOCPManagement nodes and RHOCP Infrastructure nodes were configured with 4 vCPUs and 16 GB memory each. Results may vary.
Note: (4) LinuxONE Emperor 4 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).

Model abstract 3931-LA1

IBM LinuxONE Emperor 4, machine type 3931, provides a scalable, sustainable, highly available platform that delivers differentiated value to help enable business growth, reduce cost, and improve performance efficiency.

The IBM LinuxONE Emperor 4 platform provides the hardware infrastructure, in a balanced system design, with the encryption of data in flight between IBM LinuxONE Emperor 4 and IBM DS8900F for secure fiber channel endpoint encryption.

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

The new 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 LinuxONE Emperor 4 offers 85 partitions, and up to 200 cores to configure.

IBM LinuxONE Emperor 4 offers up to 10TB RAIM memory per CPC drawer for up to 40TB per machine all supported by physical memory encryption, NVMe 1.1, enhanced computing for TKE, Coupling Express Long Reach (Coupling Express2 LR), and Crypto Express8S allowing for Quantum-Safe system and HSM encryption.



Back to topBack to top

Highlights

Top rule

CEOs see sustainability as the number one challenge of the next two to three years and as their businesses continue their digital transformation. Improving IT efficiency is an opportunity for businesses as it is estimated that data centers globally already use 200 to 250 TW of electricity, about 1% of total electricity consumed.(1)And as data and transaction volumes grow and as new cyber threats are addressed, those numbers will get bigger.

The IBM LinuxONE Emperor 4 is a uniquely architected design that is built to handle the multi-workload needs of a modern scalable digital business with the highest quality of service and the upmost efficiency. Powered by up to 200 high-performance Telum processors, the LinuxONE Emperor 4 delivers massive scalability to support multiple workloads in a single system. The Telum processor also features additional compute resources for dedicated workloads such as on-chip AI processing, and dedicated crypto processors deliver protection at speed and scale. So, what does LinuxONE Emperor 4 deliver for your business?

  • Reduce your carbon footprint and improve efficiency with an energy efficient system
  • Deliver consistent service with a system built for "7 9's" (99.99999%) application availability, built to execute proactive outage avoidance actions on demand to respond to the increasing rate of natural disasters and power outages
  • Manage data and transactions at massive scale with increased efficiency and respond to changing requirements on demand
  • Protect today's data against current and future threats with the quantum-safe system, new quantum-safe cryptography application programming interfaces (APIs), and crypto discovery tools
  • Build privacy by isolating workloads at scale and with granularity to protect the applications and data
  • 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)
  • Reduce cost and keep up with new and changing regulations with a compliance solution that helps simplify and streamline compliance tasks

Note: (1) IT sustainability beyond the data center

Back to topBack to top

Description

Top rule

The latest member of the LinuxONE family, LinuxONE Emperor 4, 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 LinuxONE Emperor 4 delivers innovation and benefits in several key areas

Core system

  • LinuxONE Emperor 4 has a maximum of 200 client-configurable cores, which is an increase of 10 over IBM LinuxONE III. The LinuxONE Emperor 4 single processor capacity is designed to enable equal n-way at common client configurations, approximately 9% greater than on LinuxONE III with some variation based on workload and configuration.(4)
  • The largest LinuxONE Emperor 4 is expected to provide approximately 17% more total system capacity as compared to the largest LinuxONE III with some variation based on workload and configuration. Within each single drawer, LinuxONE Emperor 4 provides 25% greater capacity than LinuxONE III for standard models and 40% greater capacity on the maximum configuration model, enabling efficient scaling of partitions.(4)
  • LinuxONE Emperor 4 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 LinuxONE III.
  • LinuxONE Emperor 4 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 LinuxONE III. This is designed to improve overall workload performance, particularly for data-intensive analytics and AI applications. The new memory interface uses transparent memory encryption technology to protect all data leaving the processor chips before it's stored in the memory DIMMs.

Security and cryptography

  • LinuxONE Emperor 4 quantum-safe technology is designed to enable you to act now to help protect your business. LinuxONE Emperor 4 leverages quantum-safe technologies to help protect your business- critical infrastructure and data from potential quantum attacks.(5)
  • LinuxONE Emperor 4 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.(5)
  • IBM Secure Boot for Linux allows validation of signed Linux kernels to prevent non-approved Linux kernels from booting, based on a previously validated root of trust established for the firmware Bootloader.
  • The new 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. FICON Express32S is also a key component of the IBM Fibre Channel Endpoint Security solution.
  • 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.
  • Dynamic Partition Manager (DPM) continues to enhance its capabilities. With LinuxONE Emperor 4, 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.

A flexible and standardized configuration

LinuxONE Emperor 4 provides offering simplification and enables you to flexibly scale up to four frames in a single system and integrate additional hardware appliances into an industry-standard form factor. This will benefit existing clients through potential consolidation down to fewer frames and allows an easier scale-up path for growth.

LinuxONE Emperor 4 sustainability

IBM has a longstanding commitment to building a more sustainable, equitable future. 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, LinuxONE, which is a separate brand built on the long and notable history of the IBM zSystems line of processors, is the ideal platform for achieving corporate sustainability goals. LinuxONE has inherited some of the best IBM zSystems features, including a focus on efficiency improvement that spans more than 20 years and a commitment to increasing system capacity per kW in every release. Continuing this long program history of improved sustainability factors, LinuxONE Emperor 4 is designed to enable even greater sustainability success for businesses.

LinuxONE Emperor 4 is built for the modern data center to optimize flexibility and sustainability. With the introduction of on-chip AI acceleration, LinuxONE Emperor 4 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, encryption, and compression
  • Ability to sustain high CPU utilization
  • High reliability and availability, which increases the lifespan of the hardware

These key architectural advantages help make LinuxONE Emperor 4 a differentiator in your data center, especially when consolidating workloads from x86, when it comes to sustainability benefits.

For example, consolidating Linux workloads on 5 IBM LinuxONE Emperor4 systems instead of running them on compared x86 servers under similar conditions can reduce energy consumption by 75%, space by 50%, and the CO2e footprint by over 850 metric tons annually. This is equivalent to consuming about 362,000 fewer litres (95,600 gallons) of gasoline each year.(6)

IBM continues to focus on environmental design for its products and provides resources to help businesses quantify the impacts. LinuxONE Emperor 4 makes available product carbon footprint reports using the Product Attributes to Impact Algorithm (PAIA) to help businesses understand the lifecycle carbon sustainability of the LinuxONE hardware within their data centers. LinuxONE Emperor 4 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. Emperor 4 environmental telemetry aligns with the latest ASHRAE Tier 1 DCIM Compliance.

IBM has focused on the environmental attributes of its product packaging and shipping since the late 1980s. IBM directly procures source paper and paper-based or wood-based packaging from forests that are sustainably managed and certified as such. It also collaborates with suppliers to use recycled and recyclable materials and to promote reuse. When LinuxONE systems are shipped, the use of virgin packaging materials is reduced by 60% thanks to the implementation of high- recycled-content polyethylene cushions. Even the wooden shipping crates are sustainable as they are reusable and typically last up to five shipments.

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

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 to unlock significant innovation, 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. LinuxONE Emperor 4 quantum-safe technology is designed to enable you to act now to help future-proof your business.(4)

At the infrastructure level, LinuxONE Emperor 4 offers secure boot technology that 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 during the system start-up process.(4)This protection is anchored in a hardware-based root of trust for the firmware chain of trust.(4)LinuxONE Emperor 4 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.(4)Also, Pervasive Encryption, a solution that enables data encryption at rest, has strengthened its internal key handling support by leveraging quantum-safe protections, including a hybrid key exchange mechanism using CRYSTALS-Kyber and ECDH and a dual signing scheme using CRYSTALS-Dilithium and ECDSA.

The Crypto Express8S adapter is supported by z/VM 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.

Now is the time to start planning for the replacement of hardware, software, and services that use public-key and weak symmetric key cryptography. LinuxONE Emperor 4 will enable future critical client use cases across many industries with the following capabilities:

  • Generation of Quantum-safe keys
  • Quantum-safe encryption
  • Quantum-safe key encapsulation mechanisms
  • Quantum-safe hybrid key exchange schemes
  • Quantum-safe dual digital signature schemes

Take advantage of the Pervasive Encryption support on LinuxONE Emperor 4 to protect your data at rest using quantum-safe encryption methods. This approach enables companies to encrypt all their data by default with little compute overhead. LinuxONE Emperor 4 enables you to begin using quantum-safe cryptography along with classical cryptography as you begin to modernize existing applications and build new applications.(3)

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

CCA CEX8S enhancements

LinuxONE Emperor 4 delivers critical cryptographic capabilities that help 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 Common Cryptographic Architecture (CCA) 8.0 is designed to be certified to meet the hardware security module (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.

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 the 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 agreement 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 - new 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.(7)

The new TDES key block is backward compatible with existing applications and Cryptographic Key Data Set (CKDS). 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.(8)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 to 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 HSMs 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.

LinuxONE Emperor 4 Integrated Accelerator for AI

The LinuxONE Emperor 4 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. LinuxONE Emperor 4 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 LinuxONE Emperor 4 Integrated Accelerator for AI to detect fraud in real time to reduce revenue financial loss due to fraud and increase security.

Implemented as an architected memory-to-memory instruction accelerating the most heavily used high-level AI functions like matrix multiplication or convolution, the LinuxONE Emperor 4 Integrated Accelerator for AI has direct access to the application data, resulting in reduced data movement and improved performance. LinuxONE Emperor 4 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. With LinuxONE, organizations can perform AI analysis near their data, addressing latency to deliver insights where and when they are needed.

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 LinuxONE. LinuxONE supports AI frameworks and tooling such as TensorFlow, SnapML, and the IBM Deep Learning Compiler (DLC), with optimizations that leverage the LinuxONE Architecture, including the AI accelerator. Models developed with other popular AI frameworks like PyTorch and Spark can leverage the AI accelerator using the Open Neural Network Exchange (ONNX) technology. With technologies and tooling such as ONNX, data scientists can develop and train their models with familiar tools and common platforms such as x86, IBM Power, IBM zSystems, and LinuxONE. They can then port their data science assets and deploy them on LinuxONE seamlessly to deliver more consistent, repeatable production qualities of service. By allowing clients to bring their own models for deployment on LinuxONE, organizations can leverage their existing investments in people, process, and infrastructure. By deploying AI on LinuxONE, you can benefit from the qualities 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 LinuxONE, exploiting the LinuxONE Emperor 4 Integrated Accelerator for AI. The DLC is included as part of ICR as ONNX-MLIR 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 LinuxONE Emperor 4 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 LinuxONE Emperor 4 Integrated Accelerator for AI. AI framework developers, AI compiler developers, and runtime providers can leverage the zDNN accelerated primitive APIs to drive the exploitation of the LinuxONE Emperor 4 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 for LinuxONE.

TensorFlow is a popular open source platform for AI. TensorFlow is enhanced to target supported operations to the LinuxONE Emperor 4 Integrated Accelerator for AI.

TensorFlow models, trained on any platform, can be deployed for inference on IBM zSystems and leverage the LinuxONE Emperor 4 Integrated Accelerator for AI. TensorFlow with support for the Integrated Accelerator for AI is planned to be available for use on LinuxONE. It will initially be available through the IBM LinuxONE Container Image Repository.

SnapML , a machine learning library developed by IBM Research, provides high-speed training and inference of popular machine learning models on modern computing systems. SnapML is enhanced to exploit the LinuxONE Emperor 4 Integrated Accelerator for AI for types of tree-based traditional machine learning models.

  • SnapML on LinuxONE can be exploited to provide optimized execution of models created and trained in XGBOOST, LightGBM, and Scikit-Learn.
  • On LinuxONE, tree-based models such as gradient boosting and random forest exploit the AI accelerator for inference.
  • SnapML is available for install through PyPI on LinuxONE and as an available machine learning library in Cloud Pak for Data.

Cloud Pak for Data is a cloud-native data and AI platform that helps modernize data management, analytics, and AI to help your clients drive outcomes for their business faster. Built on Red Hat OpenShift, the Cloud Pak for Data platform delivers an open information architecture with integrated capabilities from IBM and IBM partners to help clients achieve their AI aspirations and confidently leverage their enterprise data within a secured, resilient private cloud infrastructure. For additional information, see the IBM Cloud Pak for Data solution brief.

IBM Z Flexible Capacity for Cyber Resiliency

IBM Z Flexible Capacity for Cyber Resiliency is a new capacity on demand offering available on LinuxONE Emperor 4 machines, that allows processing capacity flexibility between primary site and alternate data centers.

IBM Z Flexible Capacity for Cyber Resiliency is designed to provide increased flexibility and control to organizations who want to shift production capacity between participating LinuxONE Emperor 4 machines at different sites. Capacity 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.

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

  • Proactive Avoidance: Protect critical business services from natural disasters, get support when your resources are scarce during pandemic crisis, and avoid rolling power outages. Additionally, migrate critical workloads to an alternate site before the business gets impacted and run your work on the target machine for up to one year.
  • Compliance: Regulators around the globe are introducing more stringent policies in relation to business continuity and disaster recovery requiring more comprehensive and extended testing mandating clients switch over full production loads and operate for a period of from 30 days up to 6 months out of their secondary data center. IBM Z Flexible Capacity for Cyber Resiliency is designed to help to improve an organization's compliance posture to meet existing and evolving regulatory requirements requiring rapid restoration of production workloads.
  • DR and DR Testing: Transfer the capacity needed at the DR site to continue running production workloads. Automate and test recovery procedures for unplanned outages, including cyber attacks to provide near-continuous availability and disaster recovery.
  • Facility Maintenance: Run production workloads from an alternate site with all the capacity needed to perform maintenance at the source site with the capacity needed.

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

Disclaimer: The LinuxONE Emperor 4 systems must be installed in different locations. GDPS Version 4.4 is needed for IBM provided 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.

LinuxONE Virtual Servers and Bare Metal Servers

Clients' desire to adopt hybrid means that there needs to be additional deployment options when purchasing from IBM. There will always be a strong need for on-premises workloads, but clients are looking for new methods for things like Development and Testing or temporary additional capacity, such as during peak season. For that, they need an off-premises solution that provides the same chip architecture and platform that they are invested in.

For that, IBM offers both Virtual Servers and Bare Metal Servers built on the LinuxONE platform and deployed through the IBM Cloud catalog. These offerings unlock new use cases for the same workloads that run well on the LinuxONE platform, like databases with license consolidation. And, because the offerings are built using a private network, instances are protected from outsider access and no data flows over the public internet. It is a "best of both worlds" situation where clients have more flexibility than ever before with deciding how to build their solutions using LinuxONE. LinuxONE Virtual Servers offers clients preconfigured profiles consistent with how Virtual Servers are offered both at IBM and at other vendors. There are instances where virtualization is managed by IBM and clients can simply start building their applications using s390x architecture. These instances are slices of a core, meaning that clients can deploy a fraction of a core to test a new application and pay hourly only while the instance is running, offering a much lower barrier to entry to the platform. LinuxONE Bare Metal provides dedicated cores, without virtualization, for clients to simply rent compute power and have free reign to build from the ground up. It is an extension of the on-premises value proposition, with near identical performance so clients can take advantage of additional cores when they need them. Choose from a variety of profiles based on number of cores, with associated allocations of RAM and disk.

IBM Cloud Hyper Protect Services

The IBM Cloud Hyper Protect Services are a portfolio of products offered through the IBM Cloud catalog that provide security differentiation in the public cloud. They are built on LinuxONE technology such as secure execution that allows for a confidential computing solution. Products include IBM Cloud Hyper Protect Crypto Services, IBM Cloud Hyper Protect Virtual Servers, IBM Cloud Hyper Protect DBaaS for PostgreSQL, and IBM Cloud Hyper Protect for MongoDB, with more in development. Each provides a slice of IBM's technology for consumption in the public cloud, and each instance is provisioned inside a secure enclave protecting the data from internal and external threats.

With these products, the hardware is maintained by IBM in data centers around the world, but clients can provision instances according to the size that they need and are billed according to consumption. These offerings can be provisioned on their own or with any other combination of products from the IBM Cloud catalog. In this way, clients can build complete hybrid cloud solutions that use the best of on-premises and public cloud together. Crypto Services is a combination of hardware security module (HSM) as well as a key management service. This two- in-one product offers Keep Your Own Key (KYOK) technology that provides the ability to maintain control of the entire key hierarchy.

Database-as-a-service is a managed database with two types: MongoDB and PostgreSQL. Day-to-day maintenance is handled by IBM, but clients gain security and high availability advantages by default without specialized skills.

Finally, Virtual Servers are an infrastructure-as-a-service offering that enables clients to build their applications in a confidential computing environment. It includes Secure Build, which is a protection against unauthorized code, such as malware, from being injected into a virtual server.

IBM Z Security and Compliance Center

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

The IBM Z Security and Compliance Center helps centralize monitoring of compliance in near real time and provides an interactive view of compliance posture and severity around control deviations.

The IBM Z Security and Compliance Center is designed to simplify the compliance experience for LinuxONE through some key functionality designed around pain points in current compliance operations:

  • Automate collection and validation of relevant evidence from key areas of LinuxONE 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 Linux distributions like Red Hat Enterprise Linux, SUSE Linux Enterprise Server, and Ubuntu Enterprise Server on IBM zSystems and LinuxONE will be able to use the IBM Z Security and Compliance Center dashboard to quickly and easily determine the extent to which their IBM zSystems and LinuxONE meet internal controls and certain industry standards. In addition to enterprise Linux evidence collection Linux support, the IBM Z Security and Compliance Center also collects and validates compliance evidence from Oracle Database and PostgreSQL Community Version and Fijitsu Enterprise PostgreSQL on IBM zSystems and LinuxONE.

Leverage IBM LinuxONE Expert Care to maximize and accelerate value

IBM LinuxONE Expert Care provides a best-in-class support experience, offering a tiered approach to post-warranty maintenance and support, designed to keep the IBM LinuxONE system up to date for optimal performance and minimum downtime.

IBM LinuxONE Expert Care is a cost-effective way to maintain a resilient, high-performing enterprise system, with predicable maintenance costs, while freeing up in-house IT staff to pursue other strategic business initiatives.

Highlights include:

Tier 1: LinuxONE Expert Care Advanced provides post-warranty hardware maintenance coverage. Elements include:

  • Customizable length of coverage
  • Same-day 24x7 hardware service and parts replacement
  • Hardware firmware fixes and updates - remote or onsite
  • Installation, usage and configuration recommendations
  • Automated case creation and predictive issue alerts

Tier 2: LinuxONE Expert Care Premium will provide all elements of Tier 1 (Advanced), plus additional software support and services elements as follows:

  • 9x5 Software and OS Q&A / Usage support
  • Enhanced response times - 30 Minutes, severities 1 & 2
  • Dedicated Technical Account Manager (TAM) a critical product-based support role that will serve as the key client interface for in-scope hardware and software, delivering partnership and consultancy, as well as direct engagement on high-priority support cases.

Key tasks fulfilled by the TAM include:

  • Assists in Call Home enablement
  • Assist in Predictive Support through Call Home Connect Cloud enablement
  • Provide software roadmap and life cycle information
  • Provides high impact pervasive (HIPER) information for client impact avoidance
  • Provides best practices documentation
  • Priority handling of Severity 1 and Severity 2 problems
  • Engages the appropriate support resources and provides an escalation path as needed. Participates in managed

    escalations as required

  • Delivers relationship management including welcome calls, support plan, monthly reporting, and quarterly meetings

  • Facilitates change management by communicating planned events to appropriate support team

Linux

Using open source Linux solutions is a smart way to run your IT and cloud services. LinuxONE Emperor 4 is designed to be an integral part of your hybrid IT, Linux, and cloud platforms. With LinuxONE Emperor 4, you can run and transform your IT environment with industry-leading levels of data privacy, security, and resiliency. LinuxONE Emperor 4 demonstrates a perfect infrastructure for all kinds of Linux solutions and cloud services. Linux based solutions are available from IBM, ISVs, and the open source community. The Linux based solutions can leverage LinuxONE Emperor 4 strengths such as the on-chip AI acceleration, encryption, and compression support, the high I/O bandwidth, the immense total server capacity, and high workload density. LinuxONE Emperor 4 provides:

  • Maximum scalability
  • High security levels with pervasive encryption for consumable data protection and ultimate security inside LinuxONE Emperor 4
  • Resilience and continuous availability without risk of downtime, providing high levels of security and governance
  • Agility and portability through tooling for cloud-native development
  • Open APIs to unleash and amplify core assets
  • Efficient operations with rapid deployment, configuration, and management of virtual Linux servers

Modernize for hybrid cloud

LinuxONE Emperor 4 delivers new technology innovation in AI, security, and resiliency on a flexible infrastructure designed for mission-critical workloads in a Linux and hybrid cloud environment. With LinuxONE Emperor 4 technology as an infrastructure cornerstone, you can accelerate your modernization as you integrate LinuxONE Emperor 4 seamlessly into your hybrid cloud.

LinuxONE Emperor 4 technology and its cloud solutions empower developers with the agility to accelerate the development of new cloud-native workloads and to accelerate the modernization of existing workloads that can be integrated with new digital services. LinuxONE Emperor 4 continues to deliver new and improved capabilities for Linux and cloud deployments. It cannot only be used as the enterprise Linux platform, but it can also be the foundation for application modernization and on-premises cloud as part of a hybrid cloud approach.

With the multiple virtualization technologies, LPARs, IBM z/VM, and KVM, LinuxONE Emperor 4 enables the deployment of more virtual servers, for both noncontainerized and cloud-native workloads, in a single server than any other platform through legendary scalability, system management, and performance.

  • The IBM Dynamic Partition Manager is designed to perform simplified configuration for Linux users, allowing them to quickly configure LPARs, as easily as other virtualized environments.
  • IBM z/VM delivers extremely high levels of security, scalability, and efficiency, providing a robust foundation for on-premises cloud computing using both containerized and noncontainerized workloads. z/VM based virtual machines support Linux distributions and the Red Hat OpenShift Container Platform. z/VM can host up to thousands of virtual servers on a single system.
  • KVM virtualization allows clients to make use of Linux administration skills. KVM is delivered with Linux distributions, enables the open virtualization ecosystem, and is optimized to benefit from Secure Execution as well as other LinuxONE Emperor 4 capabilities. KVM-based virtual machines support Linux distributions, and Red Hat Enterprise Linux KVM supports the Red Hat OpenShift Container Platform.

Virtualization is foundational to delivering infrastructure as a service (IaaS), a basic building block for cloud computing. IBM Cloud Infrastructure Center is a ready-to-use IaaS management solution, and together with z/VM and KVM, it can provide a consistent, industry- standard user experience for defining, instantiating, and managing the lifecycle of virtual infrastructure. Cloud Infrastructure Center provides simplified infrastructure management, deployment capabilities for Linux images for noncontainerized workloads, support to simplify and automate Red Hat OpenShift clusters deployment, and industry- standard-based integration with cloud management tools using OpenStack-compatible APIs across the enterprise.

The Linux operating system on LinuxONE Emperor 4 provides an impressive Linux and private cloud environment. Linux is the base to run all kind of workloads, especially for workloads that require high levels of resilience, flexibility, and security. Noncontainerized Linux workloads, running in virtual machines, such as MongoDB, can be easily managed and integrated into hybrid cloud by using IBM Cloud Infrastructure Center.

Container technologies are available from the Linux distribution partners and from the open source community to be deployed on a Linux distribution. Red Hat's OpenShift Container Platform comes with an included operating system and is running in z/VM and Red Hat KVM-based virtual machines. Finally, the Red Hat OpenShift Container Platform and IBM Cloud Paks running on LinuxONE Emperor 4 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 LinuxONE Emperor 4 across the hybrid cloud. Red Hat's OpenShift comes with its included operating system and is running in z/VM and Red Hat KVM-based virtual machines. Also, other container technologies are available from the Linux distribution partners and from the open source community to be deployed on a LinuxONE Emperor 4 distribution.

Modernizing applications through IBM Cloud Paks

Building containerized applications from scratch requires a significant investment in cloud resources, talent, and management tools. With a known shortage of cloud-native skills and short project timelines, IBM clients are seeking enterprise-grade and preintegrated software to accelerate digital transformation and innovation. IBM Cloud Paks are AI-powered software designed for the hybrid cloud landscape. Clients are automating, predicting, and optimizing business processes and modernizing business models at a faster pace without compromising capabilities, security, and resiliency.

LinuxONE helps clients meet their sustainability goals while enabling teams to consistently develop, deploy, and orchestrate cloud- native applications, while taking advantage of the security, resiliency, and scalability of LinuxONE infrastructure.

Why LinuxONE for Digital Asset Custody

The adoption of digital assets, like cryptocurrencies, is rapidly accelerating as the technology matures and regulations become clearer. With an overall market value of over $2T, digital assets have emerged as a disruptive new asset class, attracting the interest of startups, FinTech platforms, and institutional finance organizations looking to leverage higher yields and greater efficiencies and to gain access to untapped markets. As regulations permit, financial institutions are looking to provide their clients access to new forms of liquidity, lending, borrowing, trading, and transactional services. Digital asset custody is the foundation for these use cases that will unlock future market opportunities.

All stakeholders in the digital asset industry are exposed to some degree of risk when it comes to managing private keys used to sign transactions. Control over private keys is synonymous with control over digital assets; if you control the private key, you control the asset. Maintaining control over private keys at enterprise scale is extremely challenging and poses a major risk when managing millions of wallets. Enterprise institutional digital asset custody requires infrastructure with higher levels of protection and trusted processes to create scalable solutions that establish confidence in end customers.

IBM Digital Asset Infrastructure, powered by LinuxONE, provides the building blocks to create end-to-end solutions for storing and transferring large quantities of digital assets in highly secure wallets, providing technology to create a warm wallet solution with the security of cold storage. Through partnership with leading custody platforms, IBM Digital Asset Infrastructure is designed to enable clients of all sizes to execute a strategy that supports agility to trade, compliance with regulations, and leverages hardware- based security to provide additional assurances that help reduce overall risk profile.

IBM Digital Asset Infrastructure benefits include:

  • Scale to millions of wallets.

    Unlike solutions that require key storage in an HSM, on LinuxONE, private keys are protected using envelope encryption with a master key stored in an HSM designed to meet the Federal Information Processing Standards (FIPS) 140-3 at Level 4, the highest level of certification commercially available. This capability enables a single HSM to scale to millions of wallets with no physical limits on key storage.

  • Secure critical platform components in highly isolated hardware- protected Trusted Execution Environments.

    When architecting a digital asset solution involving the exchange of funds, it is important to consider the exploitation of sensitive data by both insider and external threats. Exploitation of applications, data, and policies can lead to irreversible loss of funds as well as loss of confidence from end customers.

    Deploying applications and databases in IBM Secure Execution for Linux Trusted Execution Environments isolate workloads to restrict access to data.

  • Remove operational risks such as unauthorized policy rule manipulation or malicious code insertion.

    When deploying wallets and databases with keys, it is crucial to verify that an insider cannot deploy malware or backdoors in the deployment process and to confirm the correct software image was deployed. The Secure Build Server creates a trusted CI/CD pipeline by providing audit-as-deploy processes to reduce the risk of malicious code being deployed into production.

  • Migrate seeds off-chain without fees, whitelisting, or revealing to blockchain explorers or end users.

    Often financial institutions begin their journey into digital assets working with a third-party custodian. Institutions can have multiple custodians and need future flexibility to bring these assets in-house to retain ownership of the keys and assets. How can they migrate wallets and seeds, which can be responsible for millions of dollars, between providers?

  • "Bring-Your-Own-Seed" enables clients to avoid on-chain transaction fees and provides a flexible and secure methodology to prevent vendor lock-in, IBM included.
  • Transact directly from offline, air-gapped cold storage.

    Cold storage is used to keep assets secured offline and typically without internet access, requiring a high level of isolation, typically implemented using air-gapped servers. This type of implementation poses challenges when moving from cold to warm storage, often involving USB sticks and manual key transit, leading to both operational and security risks.

    Only LinuxONE provides partitions that are certified with Common Criteria EAL 5+ isolation. This certification demonstrates a higher level of isolation than air-gapped servers.

z/VM support for IBM LinuxONE Emperor 4

The z/VM 7.1 and z/VM 7.2 PTFs for APAR VM66532 provide support to enable guests to exploit function on IBM LinuxONE Emperor 4, 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.

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 a z/VM Single System Image (SSI) cluster before any member of the cluster is IPLed on LinuxONE Emperor 4:

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

All IBM LinuxONE Emperor 4 compatibility support will be in the base of z/VM 7.3.

For further details, see the z/VM service required for the IBM z16 website and the hardware PSP bucket 3911DEVICE z/VM subset.

z/VM new function portal

The z/VM Continuous Delivery News web page is the primary vehicle used by IBM to describe new 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. For instructions, see 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 LinuxONE Emperor 4 benefits 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 Dynamic Memory Downgrade information.
  • 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 LinuxONE Emperor 4 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 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.

KVM support for LinuxONE Emperor 4

  • Newer versions of KVM provide a CPU model to enable guests to exploit function on LinuxONE Emperor 4, 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 several classes of programming errors.
    • 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 handle page table changes in several scenarios.
    • CEX8S adapter supported with dedicated crypto domains. Dedicated crypto domains in the 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.
    • To exploit those features in a KVM guest, the CPU model for LinuxONE Emperor 4 must be available on the KVM host and is part of RHEL 8.5 Advanced Virtualization and later, SLES 15 SP4 and later, and Ubuntu 21.10 and later.

FICON Express32S

FICON Express32S supports a link data rate of 32 Gbps and auto- negotiation 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 zSystems (zHPF), and Fibre Channel Protocol (FCP), the LinuxONE Emperor 4 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 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, LinuxONE Emperor 4 FICON Express32S delivers up to 600,000 IOPS per port for small data block (4 KB) read operations, a 52% increase over LinuxONE III FICON Express16SA. Performance results are based on laboratory measurements on LinuxONE Emperor 4 using an internal microbenchmark to execute FCP I/O operations on FICON Express32S. The FICON Express32S port operated at a 32 Gbps link data rate. The workload consisted of 4 KB read-only data transfer I/O operations.
    Note: Results may vary.
  • In laboratory measurements using the FCP protocol, a single LinuxONE Emperor 4 FICON Express32S port delivers up to 6,400 MB/s for a mix of large data block (64 KB) read/write operations, 2 times the throughput of an LinuxONE III FICON Express16SA port.
  • Performance results are based on laboratory measurements done on LinuxONE Emperor 4 using an internal microbenchmark to execute FCP I/O operations on a single FICON Express32S port. The FICON Express32S port operated at a 32 Gbps link data rate. The workload consisted of an even mix of 64 KB read/write data transfer I/O operations.
    Note: Results may vary.
  • In laboratory measurements using the FCP protocol, both ports on LinuxONE Emperor 4 FICON Express32S deliver a total combined throughput of up to 9,700 MB/s for a mix of large data block (64 KB) read/write operations, a 54% increase over the total throughput of LinuxONE III FICON Express16SA. Performance results are based on laboratory measurements done on LinuxONE Emperor 4 using an internal LinuxONE microbenchmark to execute FCP I/O operations on both ports available on FICON Express32S. Both FICON Express32S ports operated at a 32 Gbps link data rate. The workload consisted of an even mix of 64 KB read/write data transfer I/O operations.
    Note: Results may vary.

The FCP protocol is supported by z/VM and the various Linux distribution. See the Software requirements section for more information.

HMC 2.16.0 highlighted feature enhancements

HMC security enhancements:

  • Additional MFA-supported types and support of additional environments.

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

    The HMC 2.16.0 supports connections to the IBM Z MFA component running in z/VM and LinuxONE.

  • 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, Web Services API connections, Fibre Channel End Point Security, FTPS servers, and Single Object Operations.
    Note: 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 LinuxONE Emperor 4, HMC/SE will require new LinuxONE systems default user password changes for all LinuxONE Emperor 4 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 an 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 LinuxONE Emperor 4 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 LinuxONE 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 requirements. Clients have the option to modify that expiration time.

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

    Client certificates managed by the HMC/SE include uses for browser, WS APIs, IBM HMC Mobile, 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 HMC widgets, which provide optional and simplified views of previous actions without a significant overhaul of the entire HMC user experience:

    • What's new
    • Systems health
    • Hardware messages
    • Frequently used tasks

    Additional widgets are expected to be added in the future.

  • n-mode Power STP Imminent Disruption Signal option.

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

    However, for LinuxONE Emperor 4, because 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: 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 rarer 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 must 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 like 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.

    LinuxONE Emperor III includes the RCL option for LinuxONE firmware, enabling IBM to upgrade the LinuxONE 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.

    LinuxONE Emperor 4 has incorporated feedback from that LinuxONE III experience, and the following LinuxONE Emperor 4 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.
    • 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.

For current videos, see the IBM Z Hardware Management Console Videos website. Monitor the website for videos being added to the IBM HMC playlist, which will include some of the new 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.
Note: (5) Based on internal measurements. Results may vary by client based on individual workload, configuration, and software levels. See the website for more details.
Note: (6) Consolidating Linux workloads on 5 IBM LinuxONE systems instead of running them on compared x86 servers under similar conditions can reduce energy consumption by 75%, space by 50%, and the CO2e footprint by over 850 metric tons annually.

DISCLAIMER: Compared 5 IBM Machine Type 3931 Max 125 model consists of three CPC drawers containing 125 configurable cores (CPs, zIIPs, or IFLs) and two I/O drawers to support both network and external storage versus 192 x86 systems with a total of 10364 cores. IBM Machine Type 3931 power consumption was based on inputs to the IBM Machine Type 3931 IBM Power Estimation Tool for a memo configuration. x86 power consumption was based on March 2022 IDC QPI power values for 7 Cascade Lake and 5 Ice Lake server models, with 32 to 112 cores per server. All compared x86 servers were 2 or 4 socket servers. IBM Z and x86 are running 24x7x365 with production and non-production workloads. Savings assumes a Power Usage Effectiveness (PUE) ratio of 1.57 to calculate additional power for data center cooling. PUE is based on Uptime Institute 2021 Global Data Center Survey ( https://uptimeinstitute.com/about-ui/press-releases/u ptime-institute-11th-annual-global-data-center-survey ). CO2e and other equivalencies that are based on the EPA GHG calculator ( https://www.epa.gov/energy/greenhouse-gas-equivalenci es-calculator ) use U.S. National weighted averages. Results may vary based on client-specific usage and location.
Note: (7) (PCI HSM) CERTIFICATION for CEX7S 7.3 (cert# 4-20358)
Note: (8) (PCI-HSM) CERTIFICATION for CCA 6.6/CEX6S (3w review) (WRAPENH3) (cert# 4-20333)

Enter your title here

HMC 2.16.0 highlighted feature enhancements

  • HMC security enhancements:
    • Additional MFA-supported types and support of additional environments

      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 LinuxONE MFA component running in an IBM LinuxONE 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)

      HMC 2.16.0 will support connections to the Emperor 4 MFA component running in z/VM and Linux on Emperor 4.

    • 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 and IBM LinuxONE Emperor 4, HMC/SE will require new IBM Z systems default user password changes for all IBM z16 systems and IBM LinuxONE Emperor 4 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 LinuxONE Emperor 4 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 LinuxONE 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 that expiration time.

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

      Clients certificates managed by the HMC/SE include uses for browser, WS APIs, HMC mobile, 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 LinuxONE, losing a Preferred Time Server (PTS) has significant consequences to the timing network and the overall workload execution environment of the IBM LinuxONE The IBM LinuxONE and the HMC have had longtime automated fail over protection for various cases that can arise.

      However, for Emperor 4, 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 LinuxONE introduced the RCL option for IBM Z firmware, enabling IBM to upgrade the IBM LinuxONE 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. zL1 has incorporated feedback from that IBM LinuxONE IIIexperience, and the following zL1 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 new 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.

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, IBM z14, IBM LinuxONE Emperor, and IBM LinuxONE Emperor II.
    • Feature 9850 provides one 20-liter jug and supports IBM z15, IBM z16, LinuxONE III, and LinuxOne Emperor 4.
    • 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

Accessibility Compliance Status

IBM LinuxONE Emperor 4 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 (note 2)
LA1 1 - 200 512GB to 40,704GB 0 - 48 0 - 12

Notes:

  1. Max 10TB per CPC drawer. Max dependent on power configuration.
  2. Max I/O Drawer count dependent on power configuration and CPC drawer count.

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 PUs Avail for use CPs (#1955) Min/Max IFLs (#1959) Min/Max uIFLs (#1962) Min/Max Optional SAP (#1963) Min/Max
0655 39 0 to 1 1 to 39 0 to 38 0 to 8
0656 82 0 to 1 1 to 82 0 to 81 0 to 8
0657 125 0 to 1 1 to 125 0 to 124 0 to 8
0658 168 0 to 1 1 to 168 0 to 167 0 to 8
0659 200 0 to 1 1 to 200 0 to 199 0 to 8

Notes:

  1. A LinuxONE Emperor 4 supports 1 sub-capacity general purpose processor (#1955). Active capacity must always equal the purchased capacity.
  2. General purpose processors cannot be used with CBU CP features.
  3. CBU IFL and CBU SAP features are allowed.
  4. At least one Integrated Facility for Linux (IFL) (#1959) and at most one CP (#1955) is required.
  5. One CP(#1955) or one IFL (#1959) must be installed with the installation of any uIFLs or prior to the installation of any uIFLs .
  6. The total number of PUs purchased cannot exceed the total number available
  7. There are two Spares per system
  8. The number of standard SAPs provided to the customer are as follows:
    Feature code 0655 = five SAPs
    Feature code 0656 = ten SAPs
    Feature code 0657 = fifteen SAPs
    Feature code 0658 = twenty SAPs
    Feature code 0659 = twenty four SAPs

Customer setup (CSU)

Customer setup is not available on this machine.

Devices supported

Not applicable.

Model conversions

From Machine Type From Model To Machine Type To Model
3931 LA1 3931 A01 (*)

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

Feature conversions

From To
M/T F/C M/T F/C Description
3931 1959 3931 1963 (*) IFL to SAP(opt)
3931 1959 3931 1962 (*) IFL to uIFL
3931 1963 3931 1959 (*) SAP(opt) to IFL
3931 1963 3931 1962 (*) SAP(opt) to uIFL
3931 1962 3931 1959 (*) uIFL to IFL
3931 1962 3931 1963 (*) uIFL to SAP(opt)
3931 0509 3931 0508 (*) LA1 to A01
3931 0667 3931 0668 (*) Max39 to Max82
3931 0667 3931 0669 (*) Max39 to Max125
3931 0668 3931 0669 (*) Max82 to Max125
3931 8023 3931 8024 (*) 400 to 401
3931 8024 3931 8023 (*) 401 to 400



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 LinuxONE Emperor 4 Model LA1 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 LinuxONE Emperor 4 Model LA1 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 zSystems servers, features, and functions are identified. A new driver level is required.

HMC (V2.16.0) plus MCLs and the Support Element (V2.16.0) are planned to be available on September 13, 2022. You should review the PSP buckets for minimum Machine Change Levels (MCLs) and software PTF levels before IPLing operating systems.

Machine family Machine type Firmware driver SE version
LinuxONE Emperor 4 3931 51 2.16.0
LinuxONE LT1 and LT2 8561, 8562 41 2.15.0
LinuxONE Emperor II 3906 36 2.14.1
LinuxONE Rockhopper II 3907 36 2.14.1

Hardware requirements

The hardware requirements for the IBM zSystems servers, features, and functions are identified. A new driver level is required.

HMC (V2.16.0) plus MCLs and the Support Element (V2.16.0) are planned to be available on September 13, 2022. You should review the PSP buckets for minimum Machine Change Levels (MCLs) and software PTF levels before IPLing operating systems.

Machine family Machine type Firmware driver SE version
LinuxONE Emperor 4 3931 51 2.16.0
LinuxONE LT1 and LT2 8561, 8562 41 2.15.0
LinuxONE Emperor II 3906 36 2.14.1
LinuxONE Rockhopper II 3907 36 2.14.1

Software requirements

IBM LinuxONE Emperor 4 requires at a minimum:

  • z/VM 7.3
  • z/VM 7.2 with PTFs
  • z/VM 7.1 with PTFs
  • Linux: IBM supports running the following Linux on IBM Z distributions on IBM LinuxONE Emperor 4:
    • 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 22.04 LTS with service and Ubuntu 20.04 LTS with service.
    • The support statements for IBM LinuxONE Emperor 4 also cover the KVM hypervisor on distribution levels that have KVM support:
      • SLES 15 SP3 with service and SLES 12 SP5 with service
      • RHEL 9.0 with service and RHEL8.4 with service
      • Ubuntu 22.04 LTS with service and Ubuntu 20.04 LTS with service
    • For the minimum required and recommended distribution levels, see Linux on IBM Z tested platforms website.

    The support statements for LinuxONE Emperor 4 also cover the KVM hypervisor on distribution levels that have KVM support:

    • Supported distributions are supported as KVM guests.
    • Supported distributions except RHEL 7.9 are supported as KVM hosts.

Linux distributions named here are minimum levels; for example, "RHEL 8.4" implies "RHEL 8.6".

The following software requirements are listed for features and capabilities supported on LinuxONE Emperor 4:

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

  • z/VM 7.3
  • z/VM 7.2
  • z/VM 7.1
  • Linux: IBM supports:
    • 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 22.04 LTS with service and Ubuntu 20.04 LTS with service

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

  • z/VM 7.3
  • z/VM 7.2
  • z/VM 7.1
  • Linux: IBM supports:
    • 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 22.04 LTS with service and Ubuntu 20.04 LTS with service

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

  • z/VM 7.3
  • z/VM 7.2
  • z/VM 7.1
  • Linux: IBM supports:
    • 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 22.04 LTS with service and Ubuntu 20.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
  • Linux: IBM supports:
    • 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 22.04 LTS with service and Ubuntu 20.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: IBM supports:
    • 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 22.04 LTS with service and Ubuntu 20.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: IBM supports:
    • 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 22.04 LTS with service and Ubuntu 20.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/VM 7.3
  • z/VM 7.2
  • z/VM 7.1
  • Linux: IBM supports:
    • 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 22.04 LTS with service and Ubuntu 20.04 LTS with service

CHPID type OSD:

  • z/VM 7.3
  • z/VM 7.2
  • z/VM 7.1
  • Linux: IBM supports:
    • 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 22.04 LTS with service and Ubuntu 20.04 LTS with service

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

  • z/VM 7.3
  • z/VM 7.2
  • z/VM 7.1
  • Linux: IBM supports:
    • 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 22.04 LTS with service and Ubuntu 20.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/VM 7.3
  • z/VM 7.2
  • z/VM 7.1
  • Linux: IBM supports:
    • 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 22.04 LTS with service and Ubuntu 20.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/VM 7.3
  • z/VM 7.2
  • z/VM 7.1
  • Linux: IBM supports:
    • 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 22.04 LTS with service and Ubuntu 20.04 LTS with service

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

CHPID type OSD with exploitation of two ports per CHPID:

  • z/VM 7.3
  • z/VM 7.2
  • z/VM 7.1
  • Linux: IBM supports:
    • 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 22.04 LTS with service and Ubuntu 20.04 LTS with service

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

  • z/VM 7.3
  • z/VM 7.2
  • z/VM 7.1
  • Linux: IBM supports:
    • 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 22.04 LTS with service and Ubuntu 20.04 LTS with service

Checksum offload for IPv6 packets (CHPID type OSD):

  • z/VM 7.3 for guest exploitation
  • z/VM 7.2 for guest exploitation
  • z/VM 7.1 for guest exploitation
  • Linux: IBM supports:
    • 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 22.04 LTS with service and Ubuntu 20.04 LTS with service

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

  • z/VM 7.3 for guest exploitation
  • z/VM 7.2 for guest exploitation
  • z/VM 7.1 for guest exploitation
  • Linux: IBM supports:
    • 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 22.04 LTS with service and Ubuntu 20.04 LTS with service

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
  • Linux: IBM supports:
    • 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 22.04 LTS with service and Ubuntu 20.04 LTS with service
    • For secure key cryptography downloads for CCA and EP11 are available here

Crypto Express8S (1 HSM) (#0909) Toleration 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: IBM supports:
    • 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 22.04 LTS with service and Ubuntu 20.04 LTS with service
    • For secure key cryptography downloads for CCA and EP11 are available here

Crypto Express8S (1 HSM) (#0909) support of VISA Format Preserving Encryption 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: IBM supports exploitation with CCA (downloadable here for use with:
    • SUSE Linux Enterprise Server: SLES 15 SP3 with service and SLES 12 SP5 with service
    • Red Hat Enterprise Linux: RHEL 9.00 with service, RHEL 8.4 with service, and RHEL 7.9 with service
    • Canonical: Ubuntu 22/04 LTS with service and Ubuntu 20.04 LTS with service

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

  • 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. IBM is working on providing new downloadables of CCA and EP11 (Enterprise PKCS) that exploit new features of Crypto Express8S.

Crypto Express8S (1 HSM) (#0909) support of PCI-HSM compliance 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: IBM supports exploitation with CCA (downloadable here for use with:
    • SUSE Linux Enterprise Server: SLES 15 SP3 with service and SLES 12 SP5 with service
    • Red Hat Enterprise Linux: RHEL 9.00 with service, RHEL 8.4 with service, and RHEL 7.9 with service
    • Canonical: Ubuntu 22/04 LTS with service and Ubuntu 20.04 LTS with service

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/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: IBM supports:
    • SUSE Linux Enterprise Server: SLES 15 SP3 with service and SLES 12 SP5 with service
    • Red Hat Enterprise Linux: RHEL 9.0 with service and RHEL 8.4 with service
    • Canonical: Ubuntu 22.04 LTS with service and Ubuntu 20.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/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: IBM supports:
    • SUSE Linux Enterprise Server: SLES 15 SP3 with service and SLES 12 SP5 with service
    • Red Hat Enterprise Linux: RHEL 9.0 with service and RHEL 8.4 with service
    • Canonical: Ubuntu 22.04 LTS with service and Ubuntu 20.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: IBM supports:
    • 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 22.04 LTS with service and Ubuntu 20.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: IBM supports:
    • 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 22.04 LTS with service and Ubuntu 20.04 LTS with service

10 GbE RoCE Express3 SR (#0440), 10 GbE RoCE Express3 LR (#441) 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: IBM supports:
    • 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 22.04 LTS with service and Ubuntu 20.04 LTS with service

25 GbE RoCE Express 3 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: IBM supports:
    • 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 22.04 LTS with service and Ubuntu 20.04 LTS with service

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

  • 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
  • Linux: Although Linux does not exploit coupling links directly, coupling facilities can be used for STP timing purposes. IBM supports STP with:
    • 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 22.04 LTS with service and Ubuntu 20.04 LTS with service

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

  • 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 to define, modify, and delete CL5 CHPID types when z/VM is the controlling LPAR for dynamic I/O
  • z/VM 7.1 to define, modify, and delete CL5 CHPID types when z/VM is the controlling LPAR for dynamic I/O
  • Linux: Although Linux does not exploit coupling links directly, coupling facilities can be used for STP timing purposes. IBM supports STP with:
    • 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 22.04 LTS with service and Ubuntu 20.04 LTS with service

CPU Measurement Facility requires at a minimum:

  • z/VM 7.3
  • z/VM 7.2 with PTFs
  • z/VM 7.1 with PTFs
  • Linux: IBM supports:
    • 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 22.04 LTS with service and Ubuntu 20.04 LTS with service

Quantum-safe API support 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

IBM Fibre Channel Endpoint Security requires at a minimum:

  • z/VM 7.3
  • z/VM 7.2 with PTFs
  • z/VM 7.1 with PTFs
  • Linux: IBM supports:
    • 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 22.04 LTS with service and Ubuntu 20.04 LTS with service

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

  • IBM supports running the following Linux distributions as a KVM host on IBM LinuxONE Emperor 4:
    • 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 distributions as a KVM guest on IBM LinuxONE Emperor 4:
    • SUSE Linux Enterprise Server: SLES 15 SP3 with service
    • Red Hat Enterprise Linux: RHEL 9.0 with service, RHEL 8.4 with service, and RHEL 7.9 with service
    • Canonical: Ubuntu 22.04 LTS with service and Ubuntu 20.04 LTS with service

IBM LinuxONE Emperor 4 Integrated Accelerator for AI 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: Applications intending to leverage the Integrated Accelerator for AI may require the zDNN library to be present. The zDNN library is provided with the following Linux distributions:
    • SUSE Linux Enterprise Server: SLES 15 SP4 with service
    • Red Hat Enterprise Linux: RHEL 8.6 with service
    • Canonical: Ubuntu 22.04 LTS with service
  • IBM is working with its Linux distribution partners to provide the zDNN library 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 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 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:

  • IBM WebSphere Liberty 21.0.0.3
  • Java SDK80 SR6 FP26 with APAR PH34993
  • 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, OSA, and zHyperLink Express) GA23-1409

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 Links, OSA, and zHyperLink Express) SY27-7697
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

You can find information about Linux on IBM Z and IBM LinuxONE at this 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.

For HMC videos, go to the IBM Z Hardware Management Console Videos web page.

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. For IBM zSystems publications, go to IBM Documentation.

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

Title Order number
Technical Introduction SG24-8950-00
Technical Guide SG24-8951-00
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.

National language support

Not applicable.



Back to topBack to top

Features

Top rule

Features - No charge Features - No charge Feature descriptions Feature descriptions
Features - Chargeable Features - Chargeable Feature exchanges Feature exchanges
Feature availability matrix Feature availability matrix


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
FOR CHINA ONLY  
0329 RCN - Regional Cores Number
FOR CHINA ONLY  

Features - Chargeable

Feature Number Title
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
0032 Non RSF On/Off CoD
0033 Serv Docs Optional Print
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 CPC
0144 TKE Tower
0145 TKE Rack
0156 TKE Rack KMM
0157 TKE Table Top 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
0317 Flexible Cap 1 Unit
0318 Flexible Cap 100 Units
0319 Flexible Cao 10000 Units
0320 Flexible Cap IFL
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
0421 PCIe Interconnect Gen4
0434 Coupling Express2 LR
0440 10GbE RoCE Express3 SR
0441 10GbE RoCE Express3 LR
0448 NVMe Carrier1.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 Exp 32S LX
0462 FICON Exp 32S SX
0448 NVMe Carrier1.1
0509 Model LA1
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
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
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
1959 IFL
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
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
3666 MSS Sales Flag D
3667 MSS Sales Flag C
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
5409 400 Capacity Marker
5410 401 Capacity Marker
5827 FQC Bracket & Mounting Hdw
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
6815 PRC 1 SAP day
6816 PRC 100 SAP days
6817 Total CBU Years Ordered
6818 CBU Records Ordered
6822 Single CBU IFL Year
6823 25 CBU IFL 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
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
9878 On Off CoD Act 100 SAP Days
9888 On Off CoD Act IFL Days
9896 On Off COD authorization
9898 Perm upgr authorization
9899 CIU Activation (Flag)
9900 On Line CoD Buying (Flag)
9904 PRC Tokens Authorization
9909 On Off CoD Act SAP Days
9910 CBU authorization
9912 CPE 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
9933 Flex Capacity Authorization
9975 Height Reduce Ship

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.
(#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.
(#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 website, versus 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.
(#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 Jamacia 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 codes per CPC. The Trusted Key Entry (TKE) workstation is a combination of hardware and software, network connected to one or more servers.The purpose of the feature is to is to provide secure, hardware-based compliance-levelmechanisms for managing all administrative settings of a Crypto Express features running in Common CryptographicArchitecture (CCA) mode or IBM Enterprise PKCS #11 (EP11) mode. The 3 most important groups of administrativesettings managed from this feature are the Crypto Express:

  • User Registry
  • Master Keys
  • List of Crypto Express services applications are allowed to use.

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 LinuxONE Emperor 4, new capabilities will only be delivered on newly manufactured TKEs. The LinuxONE Emperor 4 environment can contain both TKEs that have been carried forward and newly manufactured TKEs.

  • 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. The purpose of the feature is to is to provide secure, hardware-based compliance-level mechanisms for managing all administrative settings of a Crypto Express features running in Common Cryptographic Architecture (CCA) mode or IBM Enterprise PKCS #11 (EP11) mode. The 3 most important groups of administrative settings managed from this feature are the Crypto Express:

  • User Registry
  • Master Keys
  • List of Crypto Express services applications are allowed to use.

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 LinuxONE Emperor 4, new capabilities will only be delivered on newly manufactured TKEs. The LinuxONE Emperor 4 environment can contain both TKEs that have been carried forward and newly manufactured TKEs.
Note: This feature is optional if you are running all Crypto Express features in Common Cryptographic Architecture(CCA) normal mode. This feature is required if you need to manage administrative setting of Crypto Express features running in:

  • Cryptographic Architecture (CCA) PCI-D$SI mode
  • IBM Enterprise PKCS #11 (EP11) mode

    In both cases smart card readers and smart cards are also required.

  • TKE level 10.0 is required if you choose to use the TKE to manage a Crypto Express&S feature.
  • 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 Twisted Pair (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 that is required to initiate an ordering option to maintain I/O 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 free of charge 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: N/A.
  • 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 HMCs 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 LinuxONE Emperor 4 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 LinuxONE III models LT1 and LT2, and IBM LinuxONE Emperor II, and IBM LinuxONE Rockhopper II.
  • 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 150 m 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 (that is, subchannels) per CHPID. The ICA SR1.1 fanout resides in the PCIe fanout slot on the IBM LinuxONE Emperor 4 CPC drawer. The ICA SR1.1 can only be used for coupling connectivity between IBM LinuxONE Emperor II, IBM LinuxONE Rockhopper II, IBM LinuxONE III models LT1 and LT2, and LinuxONE Emperor 4 CPCs. These coupling links can also be interconnected with z16, z15 and z14 generation machines for timing synchronization. For cabling requirements, see cabling information provided below. The LinuxONE Emperor 4 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, and so on.
  • 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:
    • 150 m: OM4 50/125 micrometer multimode fiber optic cable with a fiber bandwidth @ wavelength: 4.7 GHz-km @ 850 nm.
    • 100 m: OM3 50/125 micrometer multimode fiber optic cable with a fiber bandwidth @ wavelength: 2.0 GHz-km @ 850 nm.
See 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 nonselectable feature code. If instructed by IBM to de-select feature code 0156 or 0157 due to import restrictions, then feature 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 and 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 the system to be returned is MT 3906, radiator cooled, and without Top Exit I/O 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 and 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 the system to be returned is MT 3906, radiator cooled and with Top Exit I/O 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 and 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 the system to be returned is MT 3906, radiator cooled, and without Top Exit I/O 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 and 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 the system to be returned is MT 3906, radiator cooled, and with Top Exit I/O 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 LinuxONE Emperor 4 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.
(#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) and 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) and 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) and 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) and 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 LinuxONE Emperor 4 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) and 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) and 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) and 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 10000 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: 250. Prerequisites: None. Corequisites: Flexible Capacity Record (#0376) and 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) and 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) and 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 10 km unrepeated and support a link data rate of 10 gigabits per second (Gbps). For distance requirements greater than 10 km, clients must utilize a Dense Wavelength Division Multiplexer (DWDM). The DWDM vendor must be qualified by IBM zSystems. To access DWDM vendor qualification letters go to IBM Resource LinkLink. . On the left, click Library . In the middle, you will see "Hardware products for servers". Click z Systems Qualified Wavelength Division Multiplexer (WDM) products for GDPS solutions . Click 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 10 km (6.2 miles) is supported. Greater distances are supported when attached to an IBM zSystems-qualified optical networking solution, such as DWDM. The Coupling Express2 LR supports connectivity back to Coupling Express LR features offered on IBM z15, z14, z14 model ZR1 servers, LinuxONE III LT1 and LT2, and LinuxONE Emperor 4 and Rockhopper 4 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.
(#0448) IBM Adapter for NVMe1.1

IBM adapter for client-supplied NVMe solid-state drives (SSD). The drives are obtained by the client from the NVMe SSD vendor directly or from other non-IBM sources, and IBM service installs the vendor SSD drive into the IBM Adapter for NVMe1.1 on-site. Minimum: 0. Maximum: 16. Prerequisites: None. Corequisites: This feature is only supported on IBM LinuxONE models. Compatibility conflicts: None. Customer setup: No. Limitations: The SSDs must be of a specific form factor and meet all of the requirements/specifications as outlined in the Installation Manual for Physical Planning (IMPP) , GC28-7015 which can be obtained at Resource Link , . GC28-7015 which can be obtained at Resource Link. Field installable: Yes. IBM parts removed as a result of feature conversions become the property of IBM. Client maintains ownership of SSDs. Cable orders: None.

(#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/VM and Linux 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/VM and Linux 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/VM and Linux 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/VM and Linux 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/VM and Linux 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.
(#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 LinuxONE 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 and LinuxONE 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 Channel Endpoint 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/VM and Linux 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/VM and Linux (including KVM) operating systems.

  • Minimum: 0.
  • Maximum: 39.
  • 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.

  • Minimum: 0.
  • Maximum: 200.
  • Prerequisites: None.
  • Corequisites: None.
  • Compatibility Conflicts: 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.
(#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 LinuxONE shipped hardware prior to the Customer installing any separate components.
  • Limitations: See full description embedded to IBM LinuxONE Emperor 4 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 LinuxONE shipped hardware prior to the Customer installing any separate components.
  • Limitations: See full description embedded to zL1 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 LinuxONE Emperor 4 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 LinuxONE '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 zL1 CPACF instructions for SHA-3, TRNG (True Random Number Generation), Message-Security-Assist extension 9/LinuxONE III features. New zL1 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)
  • 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), 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, 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.
(#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.
(#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.
(#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.
(#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.
(#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 LinuxONE Emperor 4. 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.

Feature exchanges

Not applicable.



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.