Family 2817+01 IBM zEnterprise 196
IBM United States Sales Manual
Revised: April 22, 2014.
| Table of contents | ||||||||||||
|
 |
| Product life cycle dates |
 |
| Type Model | Announced | Available | Marketing Withdrawn | Service Discontinued |
|---|---|---|---|---|
| 2817-M15 | 2010/07/22 | 2010/09/10 | 2014/06/30 | - |
| 2817-M32 | 2010/07/22 | 2010/09/10 | 2014/06/30 | - |
| 2817-M49 | 2010/07/22 | 2010/09/10 | 2014/06/30 | - |
| 2817-M66 | 2010/07/22 | 2010/09/10 | 2014/06/30 | - |
| 2817-M80 | 2010/07/22 | 2010/09/10 | 2014/06/30 | - |
Back to top
|
|
| Abstract |
|
|
The IBM 2817 is a IBM System z. It deploys an integrated hardware platform that brings mainframe and distributed technologies together - a system that can start to replace individual islands of computing and that can work to reduce complexity, improve security, and bring applications closer to the data they need.
Model abstract 2817-M15
The IBM 2817 System z Model M15 has 1 to 15 PUs and 32 to 704 GB memory.
Model abstract 2817-M32
The IBM 2817 System z Model M32 has 1 to 32 PUs and 32 to 1520 GB memory.
Model abstract 2817-M49
The IBM 2817 System z Model M49 has 1 to 49 PUs and 32 to 2288 GB memory.
Model abstract 2817-M66
The IBM 2817 System z Model M66 has 1 to 66 PUs and 32 to 3056 GB memory.
Model abstract 2817-M80
The IBM 2817 System z Model M80 has
1 to 80 PUs and 32 to 3056 GB memory.
Back to top
|
|
| Highlights |
|
|
IBM zEnterprise System(TM) is a first-of-a-kind workload-optimized multiplatform technology offering. The system consists of the IBM zEnterprise 196 (z196) central processor complex (CPC), the IBM zEnterprise Unified Resource Manager, and built-in support for the IBM zEnterprise BladeCenter Extension (zBX) Model 002. The IBM zEnterprise 196 is designed with improved scalability, performance, security, resiliency, availability, and virtualization. The z196 Model M80 provides up to 1.6 times the total system capacity of the z10 EC Model E64, and all z196 models provide up to twice the available memory of the z10 EC. The zBX infrastructure works with the IBM zEnterprise 196 to enhance System z virtualization and management to deliver an integrated hardware platform that spans System z mainframe and POWER7 technologies. The IBM zEnterprise Unified Resource Manager, delivered with the z196, is designed to deliver end-to-end virtualization and management along with the ability to optimize technology deployment according to individual workload requirements.
zEnterprise System is designed to deliver:
- Improved total system capacity in a 96-way core design.
- Improved performance of all workloads
- Massive scalability for secure data serving and transaction processing and large-scale consolidation
- Up to 80 cores that are customer-configurable
- Quad-core 5.2 GHz processor chips with 100+ new instructions that enable improved code efficiency, and are designed to help improve the execution of CPU-intensive workloads.
- Up to 3 terabytes (TB) of available real memory per server for growing application needs (with up to 1 TB real memory per LPAR).
- Improved availability in the memory subsystem with redundant array of independent memory (RAIM).
- Availability improvement - concurrent add/delete of I/O drawer.
- Increased scalability with 45 available subcapacity settings.
- Crypto Express3 cryptographic enhancements.
- Auto-renewal of On/Off Capacity on Demand records which is designed to eliminate the need to manually replenish your On/Off CoD records.
- Purchase of unassigned CP or IFL capacity via Customer Initiated Upgrade.
- Up to 128 coupling CHPIDs (double that of z10) and up to 80 physical external coupling links (12x InfiniBand, 1x InfiniBand, ISC-3), a 25% increase compared to z10.
- Up to 72 I/O, networking, and crypto features.
- Up to 240 ESCON channels.
- Up to 32 HiperSockets (double the number available on z10 EC).
- Energy efficiencies - more performance to help you run
more efficiently in the same footprint.
- Energy monitoring capability and power save option for the processor, which is designed to provide a 25 - 30% reduction in power consumption depending on the system configuration
- Optional water cooling, providing the ability to cool systems with user-chilled water
- Optional high-voltage DC power, which can save System z customers 1-3%, on average, on their power bills
- Top exit I/O cabling, which is designed to provide increased flexibility and increase air flow in raised-floor environments.
- &fwshort, enabling management and virtualization of
heterogeneous workloads. Unified Resource Manager manages the deployment
of heterogeneous hardware resources based on individual workload
requirements by providing:
- Performance management
- Integrated private data network
- Virtual server lifecycle management
- Hypervisor management
- Integrated operational controls
- Management as system z firmware
Back to top
|
|
| Description |
|
|
IT today is all about creating an infrastructure that is dynamic and scalable as well as being flexible enough to satisfy both the needs of mission-critical work and the development and deployment of new workloads. This infrastructure must be able to make sense of data, a company's most valuable asset, with insight rather than hindsight, and it must allow a business to use IT to gain a competitive edge. In building such systems, multiplatform solutions have become the norm for handling computational acceleration and specialized processing. As these heterogeneous systems grow, the end-to-end management can become a burden on resources and the IT budget. A technology is needed that can go to a new dimension in computing, where smarter systems and smarter software work together to address the needs of the business.
Today IBM is introducing IBM zEnterprise System(TM) - a system that combines the gold standard of enterprise computing with built-in function to extend IBM's mainframe-like governance and qualities of service to special-purpose workload optimizers and general-purpose application serving. End-to-end management is enabled for this heterogeneous environment by the IBM zEnterprise Unified Resource Manager, which provides energy monitoring and management, goal-oriented policy management, increased security, virtual networking, and data management, consolidated in a single interface that can be tied to business requirements. The IBM zEnterprise System is comprised of the IBM zEnterprise 196, the IBM zEnterprise Unified Resource Manager, built-in support for the IBM zEnterprise BladeCenter Extension (zBX), and optimizers or IBM blades.
The IBM zEnterprise 196 is designed with improved scalability, performance, security, resiliency, availability, and virtualization. The new 96-way core design delivers massive scalability for secure data serving and transaction processing for large-scale consolidation. As environmental concerns raise the focus on energy consumption, the IBM zEnterprise 196 central processor complex (CPC) is designed with new energy efficiencies that can reduce energy use and save floor space when consolidating workloads from distributed servers. For clients looking to build green datacenters, optional water cooling and high-voltage DC power allow a bold step into the future of cooler computing and increased energy efficiency without changing the system footprint.
The IBM zEnterprise Unified Resource Manager manages System z ensembles -- collections of one or more zEnterprise System nodes in which each node is comprised of a z196 and its optionally attached IBM zEnterprise BladeCenter Extension (zBX) model 002. An ensemble can consist of a single z196 with no zBX attached, or two to eight CPCs where at least one of the z196s has a zBX attached. The resources of a zEnterprise System ensemble are managed and virtualized as a single pool of resources integrating system and workload management across the multisystem, multitier, multiarchitecture environment.
When IBM zEnterprise BladeCenter Extension (zBX) is attached to IBM zEnterprise 196, the zBX infrastructure works with the z196 to support the multiplatform environment, combining mainframe and distributed technologies. The zBX can support IBM Smart Analytics Optimizer for DB2 for z/OS, V1.1 (5697-AQT) and certain POWER7 blades.
The IBM Smart Analytics Optimizer for DB2 for z/OS, V1.1 (5697-AQT) is designed to deliver improved service through accelerated and accurate business insight. This workload-optimized, appliance-like add-on is installed in the zBX and connects to DB2, providing transparency to all applications. The optional POWER7 blade is installed in the zBX, enabling application integration with System z transaction processing, messaging, and data serving capabilities. The blades are managed as part of a single logical virtualized environment by IBM zEnterprise Unified Resource Manager.
IBM Global Technology Services (GTS) and Systems Lab Services can help you assess and perform application fit-for-purpose analysis, and design an IBM zEnterprise System that integrates IT strategy and business priority. This includes developing the business case and high-level transition plan, and a roadmap for an adaptable and efficient infrastructure. GTS and Systems Lab Services can also enable you to build and run a smarter IBM zEnterprise System environment. With these services, you can migrate effectively and efficiently to an IBM zEnterprise System, create a more cost-effective and manageable computing environment with server, storage, and network optimization, integration, and implementation, and effectively run and manage the IBM zEnterprise System with maintenance and technical support services.
The IBM System z10 Enterprise Class and IBM System z10 Business Class can now use operational controls on the Hardware Management Console (HMC) to manage IBM Smart Analytics Optimizer for DB2 for z/OS V1.1 (5697-AQT). This is a heterogeneous Business Intelligence (BI) infrastructure that is a single entity with minimal risk and improved costs. With today's announcement, the HMC provides extended support to manage the IBM zEnterprise BladeCenter Extension (zBX) Model 001 and IBM Smart Analytics Optimizer for DB2 for z/OS V1.1 (5697-AQT) capabilities.
The System z10 is also simplifying key management with Trusted Key Entry (TKE) workstation enhancements by allowing a writable USB-attached media to be used to help install TKE license Internal Code (LIC).
The IBM zEnterprise System (TM) offers a total systems approach to delivering advanced heterogeneous systems management functions that is unmatched in the industry. The announcement of zEnterprise System takes technology to the next level. The IBM zEnterprise System consists of the hardware management subsystems -- CPC, memory, I/O, power/packaging/cooling -- and platform management firmware that is designed to enable you to run heterogeneous workloads under the management of one system with IBM zEnterprise System (IBM zEnterprise 196 + IBM zEnterprise BladeCenter Extension (zBX) + IBM zEnterprise Unified
The IBM zEnterprise System is designed to provide:
- Enablement of new workloads and improved management of heterogeneous workloads with Unified Resource Manager
- Improved performance - on average 40% faster processor unit than z10 EC
- Larger capacity with 80 user-configurable processor units
- Flexibility - offered by 45 subcapacity settings
- Improved power efficiency - 1.6x improvement (vs z10 EC)
- Investment protection
- Improved availability with a redesign of the memory subsystem
- Improved reliability with new multichip module (MCM) design
- New power delivery technology with triple redundancy
- Increased memory - up to 3 TB memory (with up to 1 TB real memory per LPAR)
- Crypto Express3 cryptographic enhancements
- I/O rejuvenation
- Doubling of coupling CHPIDs vs z10 EC (up to 128), and up to 80 physical external coupling links (12x InfiniBand, 1x InfiniBand, ISC-3), a 25% increase compared to z10
- Double the number of HiperSockets vs z10 EC (up to 32)
- Availability enhancements such as allowing Concurrent Add/Delete of I/O drawers
- Optional water cooling
- Optional high-voltage DC power
- Optional top exit I/O cabling
- Static power save mode
- New Capacity on Demand architecture and enhancements
- Auto-renewal of On/Off Capacity on Demand records
- Purchase of unassigned CP or IFL capacity via Customer Initiated Upgrade
The performance advantage
IBM's Large Systems Performance Reference (LSPR) method is designed to provide comprehensive z/Architecture processor capacity ratios for different configurations of Central Processors (CPs) across a wide variety of system control programs and workload environments. For z196, the z/Architecture processor capacity indicator is defined with a (7XX) notation, where XX is the number of installed CPs.
In addition to the general information provided for z/OS 1.11, the LSPR also contains performance relationships for z/VM and Linux operating environments.
The performance of a z196 (2817) processor is expected to be 1.3 to 1.5 times the performance of a z10 EC (2097) based on workload and model. The largest z196 (2817-780) is expected to exceed 1.6 times the capacity of the largest z10 (2097-764).
The LSPR contains the Internal Throughput Rate Ratios (ITRRs) for the z196 and the previous-generation zSeries processor families based upon measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput that any user may experience will vary depending upon considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve throughput improvements equivalent to the performance ratios stated.
For more detailed performance information, consult the Large Systems Performance Reference (LSPR) available at:
https://www-304.ibm.com/servers/resourcelink/lib03060.nsf/pages/lsprindex
Building a smarter business infrastructure
Introducing IBM zEnterprise Unified Resource Manager.
In today's IT infrastructure, silos of computing are not aligned with the businesses they support. Additionally, corporations struggle with regulatory compliance, volume of information, integrity, and security. These limitations, along with resource constraints and difficulties managing complexity and change, present increasing challenges in managing the IT infrastructure.
A smarter business infrastructure provides integrated visibility, control, and automation across all business and IT assets. The smarter business infrastructure is highly optimized to do more with less and facilitates the intelligent use of the information available. By managing and mitigating risks and utilizing flexible delivery choices, a smarter business infrastructure addresses the challenges facing business today.
Implementing a smarter business infrastructure is a strategy that can help to provide better visibility, control, and automation across the business, drive up levels of efficiency and optimization of both resources and people, bring order to the information explosion, and manage risk more productively. In addition, this type of strategy positions the infrastructure to leverage new types of delivery choices that can flex as needed, such as cloud computing, helping clients address today's most persistent business and IT constraints.
IBM zEnterprise 196 provides a smarter business infrastructure through the introduction of the IBM zEnterprise Unified Resource Manager, which manages System z ensembles - collections of one or more zEnterprise System nodes in which each node is comprised of a z196 and its optionally attached IBM zEnterprise BladeCenter Extension (zBX) model 002. An ensemble can consist of a single z196 with no zBX attached, using an OSA loopback cable, or two to eight CPCs where at least one of the z196s has a zBX attached. The resources of a zEnterprise System ensemble are managed and virtualized as a single pool of resources integrating system and workload management across the multisystem, multitier, multiarchitecture environment. Management actions for the ensemble are conducted from a designated primary Hardware Management Console. This HMC must be paired with an alternate HMC also designated to manage the ensemble, that can take over if the primary fails, in order to improve availability.
The functions of the Unified Resource Manager are grouped into two suites of tiered functionality that enable different levels of capability - Manage suite and Automate suite. Initial Manage suite functions are being delivered concurrently with the availability of the z196 with feature code #0019. An enhanced set of Manage suite functions (#0019), as well as a set of Automate suite functions, with feature code #0020, are being delivered concurrently with the availability of IBM zEnterprise BladeCenter Extension (zBX).
- The Manage suite is included in the base zEnterprise System as no charge for CPs, IFLs, zIIPs, and zAAPs. There is a charge for blades and IBM Smart Analytics Optimizer.
- The Automate suite is included in the base zEnterprise System as no charge for CPs, zIIPs, and zAAPs. There is a charge for IFLs, blades, and IBM Smart Analytics Optimizer.
The Unified Resource Manager is designed to provide the following initial Manage suite functions:
- Monitoring and trend reporting of CPU energy efficiency, which can be helpful in managing the costs of deployed workloads
- Delivery of system activity using a new user interface monitors dashboard (augmenting the existing System Activity Display), enabling a broader and more granular view of system resource consumption
The Unified Resource Manager is designed to provide the following enhanced Manage suite functions:
- Integrated hardware management across all elements of the system,
including operational controls, which is designed to deliver:
- Licensed internal code (LIC) inventory, update, and service
- Hardware and LIC problem detection, reporting, and call home
- Field-guided repair and verification
- Physical hardware configuration, backup, and restore
- Primary/alternate replication and recovery for the HMC
- Integrated hardware management, including operational controls, which provides a single point of control, a consistent interface, and comprehensive insight across the elements of the system to better manage operations, change control, and service
- Enhanced Monitoring and reporting of CPU energy efficiency with the ability to query maximum potential power
- Fully automatic and coherent integrated resource discovery and inventory for all elements of the system without requiring user configuration, deployment of discovery libraries or sensors, or user scheduling of resource discovery. These integrated functions enable a simplified deployment methodology, decreasing complexity, and increasing accuracy and completeness for discovery and inventory.
- A private and physically isolated OSA-Express3 1000BASE-T Ethernet internal management network (the intranode management network - INMN), operating at 1 Gbps, that connects all zEnterprise System resources (CPCs, BladeCenters, blades, top-of-rack switches, power distribution units, and hypervisors) for management purposes. This INMN is pre-wired, internally switched, configured, and managed with full redundancy for high availability. These characteristics of the INMN enable simplified and secure management with no effect on customer data traffic. The intranode management network (INMN) is exclusive to the IBM zEnterprise System and is supported by z/OS and z/VM. Refer to the Software requirements section.
- A private and secure OSA-Express3 10 Gigabit Ethernet intraensemble data network (IEDN) that connects all elements of a zEnterprise System ensemble. The IEDN is access-controlled using integrated virtual local area network (VLAN) provisioning. This requires no external customer-managed switches or routers, which helps to reduce the need for firewalls and encryption, and simplifies network configuration and management, while providing full redundancy for high availability. IEDN management provides enforcement of strict access control across heterogeneous environments, further augmenting security and simplicity. The intraensemble data network is exclusive to zEnterprise System and is supported by z/OS and z/VM. Refer to the Software requirements section.
- Hypervisors, which, except for z/VM, are shipped, deployed, and serviced, as zEnterprise System LIC and are booted automatically at power on reset. All hypervisors (PR/SM, z/VM, and PowerVM) are isolated on the internal management network, providing intrusion prevention, integrity, secure virtual switches with integrated configuration, and monitoring, as well as problem management and reporting. Managed through the Unified Resource Manager, hypervisors become part of the trusted compute base and, except for z/VM, are deployed and maintained from a single point of control.
- Virtual server lifecycle management, which enables directed and dynamic virtual server provisioning across all hypervisors (PR/SM, z/VM, and PowerVM) from a single, uniform point of control. This enables integrated storage and network configuration and ensemble membership integrity. Virtual server lifecycle management provides an authoritative understanding of server, storage, and network elements within an ensemble. Augmenting the existing z/VM virtual server management functions available on System z10, this support now also permits virtual servers to be created and deleted, and allows real and virtual networking resources to be managed by the Unified Resource Manager.
The Unified Resource Manager is designed to provide the following Automate suite functions:
- Representation of the physical and virtual resources that are used in the context of a deployed business function as a named workload. Workload representation enables focus on business goals rather than individual elements and better aligns resources with business needs.
- Ability to define a performance service level policy and to enable performance monitoring, reporting, and resource optimization that are aligned with customer-defined workload service levels by allowing virtual CPU capacity to be adjusted automatically across virtual servers within a hypervisor. Automatic CPU adjustments are supported for z/VM and POWER7 blades.
- Static power savings and energy management capabilities. For more information see the Static power save mode description below.
POWER7 blades are supported in the zBX, providing logical device integration between System z and POWER7 for multi-tiered applications. POWER7 blades, along with PowerVM, are licensed separately and are enabled and managed, as part of the ensemble, by the Unified Resource Manager. For more information on POWER7 blades refer to: "IBM BladeCenter P701 and P702 Express blades deliver world's first IBM POWER7 processor-based blades to the marketplace" Hardware Announcement 110-061, dated April 13, 2010.
IBM Smart Analytics Optimizer for DB2 for z/OS, V1.1 (5697-AQT) is being supported in the zBX, providing data-in-memory support to deliver significant performance and/or lower cost per transaction for queries redirected to the solution. It is enabled and managed, as part of the ensemble, by the Unified Resource Manager.
For more information on IBM zEnterprise BladeCenter Extension (zBX), refer to Hardware Announcement 110-177, System z BladeCenter Extension dated July, 22, 2010.
Reliability and availability enhancements
With the introduction of the IBM zEnterprise 196, IBM continues to deliver enterprise reliability and availability with enhancements to the memory subsystem, multichip module (MCM) design, and power delivery technology.
Major redesign of memory subsystem for improved availability: IBM's most robust error correction to date can be found in the memory subsystem. A new redundant array of independent memory (RAIM) technology is being introduced to provide protection at the dynamic random access memory (DRAM), dual inline memory module (DIMM), and memory channel level. Three full DRAM failures per rank can be corrected. DIMM level failures, including components such as the controller application specific integrated circuit (ASIC), the power regulators, the clocks, and the board, can be corrected. Memory channel failures such as signal lines, control lines, and drivers/receivers on the MCM can be corrected. Upstream and downstream data signals can be spared using two spare wires on both the upstream and downstream paths. One of these signals can be used to spare a clock signal line (one up stream and one down stream). Together these improvements are designed to deliver System z's most resilient memory subsystem to date.
Improved reliability of multichip module (MCM) design: IBM zEnterprise 196 has an improved MCM design with encapsulated processor unit connectors and soft error rate (SER) hardened latches throughout the design.
New power delivery technology with triple redundancy for increased reliability: With z196, we are introducing voltage transformation module (VTM) technology with triple redundancy on the VTM. This redundancy protects processor workloads from loss of voltage due to VTM failures. Triple redundancy is used by z196 on the environmental sensors (humidity and altitude), for increased reliability.
CP Assist for Cryptographic Function (CPACF) enhancements: The following are exploitation of Message-Security-Assist Extension 4:
New instructions:
- Cipher Message with CFB (KMF)
- Cipher Message with Counter (KMCTR)
- Cipher Message with OFB (KMO)
New function codes for existing instructions:
- Compute intermediate Message Digest (KIMD) adds KIMD, an extension for GHASH
More information on CPACF can be found in "IBM System z10 - Delivering security-rich offerings to protect your data", IBM United States Hardware Announcement 109-678, dated October 20, 2009.
This Crypto function is exclusive to z196.
Crypto Express3 enhancements
Crypto Express3 represents the newest-generation cryptographic feature designed to complement the cryptographic functions of CP Assist for Cryptographic Function (CPACF). The Crypto Express3 feature, residing in the I/O cage or I/O drawer of the z196, continues to support all of the cryptographic functions available on Crypto Express3 on z10.
For more information on Crypto Express3 refer to " IBM System z10 - Delivering security-rich offerings to protect your data" Hardware Announcement 109-678, dated October 20, 2009.
Concurrent Driver Upgrade (CDU) and Concurrent Patch Apply (CPA), a process to reduce outages for new releases. With concurrent driver upgrade and concurrent patch apply, most new cryptographic functions can be applied without cryptographic coprocessor card off / on. It is now possible to upgrade Common Cryptographic Architecture (CCA), segment 3, licensed internal code without any performance impact during the upgrade. However, some levels of CCA or hardware changes still require cryptographic coprocessor card vary off / on.
This Crypto function is exclusive to z196.
When one or both of the two PCIe adapters of a Crypto Express3 feature are configured as a coprocessor, the following cryptographic enhancements are supported:
- ANSI X9.8 PIN security, which facilitates compliance with
the processing requirements defined in the new version of the ANSI X9.8
and ISO 9564 PIN Security Standards and provides added security for
transactions that require Personal Identification Numbers (PINs).
This Crypto function is exclusive to z196 and is supported by z/OS and z/VM. Refer to the Software requirements section.
- Enhanced Common Cryptographic Architecture (CCA) - a key
wrapping to comply with ANSI X9.24-1 key bundling requirements, a
Common Cryptographic Architecture (CCA) key token wrapping method using
Cipher Block Chaining (CBC) mode in combination with other techniques to
satisfy the key bundle compliance requirements in standards including
ANSI X9.24-1 and the recently published Payment Card Industry Hardware
Security Module (PCI HSM) standard.
This Crypto function is exclusive to z196 and is supported by z/OS and z/VM. Refer to the Software requirements section.
- Secure Keyed-Hash Message Authentication Code (HMAC) - a
method for computing a message authentication code using a secret key and
a secure hash function. HMAC is defined in the standard FIPS (Federal
Information Processing Standard) 198, "The Keyed-Hash Message
Authentication Code ". The new CCA functions support HMAC using SHA-1,
SHA-224, SHA-256, SHA-384, and SHA-512 hash algorithms. The HMAC keys
are variable-length and are securely encrypted so that their values are
protected.
This Crypto function is exclusive to z196 and is supported by z/OS and z/VM. Refer to the Software requirements section.
- Elliptical Curve Cryptography Digital Signature Algorithm
- an emerging public-key algorithm to eventually replace RSA cryptography
in many applications. ECC is capable of providing digital signature
functions and key agreement functions. The new CCA functions provide ECC
key generation and key management and provide digital signature
generation and verification functions compliance with the ECDSA method
described in ANSI X9.62 "Public Key Cryptography for the Financial
Services Industry: The Elliptical Curve Digital Signature Algorithm
(ECDSA)". ECC uses keys that are shorter than RSA keys for equivalent
strength-per-key-bit. With RSA impractical at key lengths with
strength-per-key-bit equivalent to AES-192 and AES-256, the
strength-per-key-bit
is substantially greater in an algorithm that uses elliptic curves.
This Crypto function is exclusive to z196 and is supported by z/OS and z/VM. Refer to the Software requirements section
When one or both of the two PCIe adapters of a Crypto Express3 feature are configured as an accelerator, the following cryptographic enhancement is supported:
- Modulus Exponent (ME) and Chinese Remainder Theorem (CRT),
RSA encryption and decryption with key lengths greater than 2048-bits and
up to 4096-bits.
This Crypto function is exclusive to z196 and is supported by z/OS and z/VM. Refer to the Software requirements section.
Trusted Key Entry 7.0 Licensed Internal Code (LIC)
- ECC Master Key Support: From the Trusted Key Entry (TKE) workstation, administrators can generate key material, load or clear the new ECC master key register, or clear the old ECC master key register. The ECC key material can be stored on the TKE or on a smart card.
- CBC Default Settings Support: The TKE provides function that allows the TKE user to set the default key wrapping method used by the host crypto module.
- TKE Audit Record Upload Configuration Utility Support: The TKE Audit Record Upload Configuration Utility allows TKE workstation audit records to be sent to a System z host and saved on the host as z/OS System Management Facilities (SMF) records. The SMF records have a record type of 82 (ICSF) and a subtype of 29. TKE workstation audit records are sent to the same TKE Host Transaction Program that is used for Trusted Key Entry operations.
- USB Flash Memory Drive Support: The TKE workstation now supports a USB flash memory drive as a removable media device. When a TKE application displays media choices, the application allows you to choose a USB flash memory drive if the IBM-supported drive is plugged into a USB port on the TKE and it has been formatted for the specified operation.
- Stronger PIN Strength Support: TKE smart cards created on TKE 7.0 require a 6-digit PIN rather than a 4-digit PIN. TKE smart cards that were created prior to TKE 7.0 continue to use 4-digit PINs and will work on TKE 7.0 without changes. You can take advantage of the stronger PIN strength by initializing new TKE smart cards and copying the data from the old TKE smart cards to the new TKE smart cards.
- Stronger Password Requirements for TKE Passphrase User Profile
Support: New rules are required for the passphrase used for passphrase
logon to the TKE workstation crypto adapter. The passphrase must:
- Be 8 to 64 characters long
- Contain at least 2 numeric and 2 non-numeric characters
- Not contain the user ID
- These rules are enforced when you define a new user profile for passphrase logon, or when you change the passphrase for an existing profile. Your current passphrases will continue to work.
Third subchannel set You now have the ability to extend the amount of addressable storage capacity to help facilitate storage growth with the introduction of a third subchannel set - an additional 64K subchannels - to help complement other functions such as "large" or extended addressing volumes and HyperPAV. This may also help to facilitate consistent device address definitions, simplifying addressing schemes for congruous devices.
The first subchannel set (SS0) allows definitions of any type of device (such as bases, aliases, secondaries, and those other than disk that do not implement the concept of associated aliases or secondaries). The second and third subchannel sets (SS1 and SS2) can now both be designated for use for disk alias devices (of both primary and secondary devices) and/or Metro Mirror secondary devices only.
The third subchannel set applies ESCON, FICON and zHPF protocols, and is supported by z/OS and Linux on System z. Refer to the Software requirements section.
An I/O infrastructure for increased granularity and capacity flexibility With the introduction of z196, we are also introducing increased granularity for your I/O infrastructure with the addition of an I/O drawer, a companion to the I/O cage.
Purchase the I/O you need for your storage area network (ESCON and FICON), local area network (Open Systems Adapter), Parallel Sysplex (ISC-3), and security requirements (Crypto Express3) and the configurator tool selects the I/O packaging necessary to best optimize your infrastructure.
First offered on the z10 BC, the modular I/O drawer (8 slots) can be hot plugged in the field. This design allows installation of I/O based upon application growth and connectivity growth, obviating the requirement for plan ahead of I/O cages (28 slots) and I/O drawers.
Access to the SAN with FICON Express8
FICON Express8 provides growth opportunities for your storage area network (SAN) with its capability to autonegotiate the link data rate, providing synergy with existing switches, directors, and storages devices whether they are capable of 2 Gbps, 4 Gbps, or 8 Gbps.
FICON Express8 supports your storage devices using Fibre Connection (FICON), High Performance FICON for System z (zHPF), or Fibre Channel Protocol (FCP). You can have a point-to-point connection between z196 and a device or utilize a SAN, incorporating switches and directors in the configuration. FICON Express8 is designed to help you prepare for an end-to-end 8 Gbps infrastructure to meet the increased bandwidth demands of your applications.
FICON Express8 supports your traditional applications using the FICON architecture. Using zHPF, an extension to the FICON architecture, it also provides optimizations for online transaction processing (OLTP) workloads to help improve the execution of small block I/O requests, whether single-track or multitrack operations. zHPF streamlines the FICON architecture and reduces the overhead on the channel processors, control unit ports, switch ports, and links by improving the way channel programs are written and processed. The control unit must be zHPF-capable. zFS, HFS, PDSE, and other applications that use large data transfers with Media Manager are expected to benefit. For more information on the benefits of zHPF, refer to the I/O connectivity Web site and the FICON Express8 technical papers:
http://www-03.ibm.com/systems/z/hardware/connectivity/
In July of 2009 we extended zHPF support to multitrack operations (for example reading 16x4k bytes/IO), also resulting in reduced overhead and improved performance but limiting transfers to 64k worth of data in a single operation.
We are now further extending zHPF support of multitrack operations to include even larger data transfers - fully supporting multiple tracks of data and removing the 64k byte data transfer limit. We are now raising the limit on the amount of data that can be transferred in a single operation, allowing the channel to operate at rates that are designed to fully exploit the bandwidth of a FICON Express channel.
Extension to multitrack operations for zHPF applies to the FICON Express8 and FICON Express4 features when configured as CHPID type FC using the zHPF path, and to z/OS. Refer to the Software requirements section. The control unit must support zHPF. Otherwise, extended mulitrack operations is transparent to the control unit.
FICON Express8 for channel consolidation: FICON Express8 may also allow for the consolidation of existing FICON Express, FICON Express2, or FICON Express4 channels onto fewer FICON Express8 channels while maintaining and enhancing performance. You can carry forward your FICON Express4 features to z196. FICON Express and FICON Express2 are not supported.
To request assistance for ESCON or FICON channel consolidation analysis using the zCP3000 tool, contact your IBM representative. They will assist you with a capacity planning study to estimate the number of FICON channels that can be consolidated onto FICON Express8.
Your IBM representative can also assist you with ESCON to FICON channel migration.
Assigning WWPNs to physical Fibre Channel Protocol (FCP) ports:
This support extends the capabilities of the worldwide port name (WWPN) prediction tool to physical Fibre Channel Protocol (FCP) channel/ports, allowing the tool to now show WWPNs for both virtual and physical ports ahead of system installation time. In addition, you can retain your storage area network (SAN) configuration if a FICON feature is replaced instead of altering your SAN configuration based upon the FICON feature's "burned in" WWPN.
This enhancement applies to all of the FICON features supported on z196 when configured as CHPID type FCP, supporting attachment to SCSI devices. It is transparent to operating systems. For an update to the WWPN prediction tool, refer to the Tools section of Resource Link at planned availability of z196.
- www.ibm.com/servers/resourcelink
z/OS discovery and autoconfiguration for FICON channels: With z196 and z/OS, a new function, z/OS discovery and autoconfiguration (zDAC), is designed to automatically perform a number of I/O configuration definition tasks for new and changed disk and tape controllers connected to a switch or director when attached to a FICON channel. When new controllers are added to an I/O configuration or changes are made to existing controllers, the system is designed to discover them and propose configuration changes based on a policy you define in the hardware configuration dialog (HCD). Your policy can include preferences for availability and bandwidth including parallel access volume (PAV) definitions, control unit numbers, and device number ranges.
zDAC is designed to perform discovery for all systems in a sysplex that support the function. The proposed configuration will incorporate the current contents of the I/O definition file (IODF) with additions for newly installed and changed control units and devices. zDAC is designed to help simplify I/O configuration on z196 running z/OS and reduce complexity and setup time.
zDAC applies to all FICON features supported on z196 when configured as CHPID type FC and is supported by z/OS. zDAC is exploited by the IBM System Storage DS8700. Refer to the Software requirements section.
Access to high-speed intraserver network - HiperSockets
A single logical partition can now connect up to 32 HiperSockets, double the number of HiperSockets previously supported. With HiperSockets, you have independent, integrated, virtual local area networks (LANs). No physical cabling or external connections are required. HiperSockets supports Internet Protocol version 4 (IPv4) and IPv6.
Up to 32 HiperSockets are supported by z/OS, z/VM, zVSE, and Linux on System z. Refer to the Software requirements section.
HiperSockets network traffic analyzer (HS NTA) for Linux on System z environments:
An enhancement to the HiperSockets architecture is designed to help simplify problem isolation and resolution. You now have the capability to trace Layer 2 and Layer 3 HiperSockets network traffic.
HS NTA allows Linux on System z to control the trace for the internal virtual LAN, to capture the records into host memory and storage (file systems). Linux on System z tools can be used to format, edit, and process the trace records for analysis by system programmers and network administrators. Refer to the Software requirements section.
HiperSockets network traffic analyzer is supported on IBM zEnterprise 196 and IBM System z10.
Access to the LAN with OSA-Express3
The OSA-Express3 family of local area network (LAN) adapters is designed for use in high-speed enterprise backbones, for local area network connectivity between campuses, to connect server farms to the mainframe, and to consolidate file servers onto the mainframe.
The OSA-Express3 features incorporated a hardware data router in the design, as well as a faster microprocessor and PCIe bus; functions and components that help to reduce latency and improve throughput. Choose the features that satisfy your infrastructure requirements, now and in the future.
OSA-Express3 Ethernet features:
- 10 Gigabit Ethernet long reach (10 GbE LR) for single mode fiber infrastructures; supports 10 Gbps link data rate
- 10 Gigabit Ethernet short reach (10 GbE SR) for multimode fiber infrastructures; supports 10 Gbps link data rate
- Gigabit Ethernet long wavelength (GbE LX) for single mode fiber infrastructures; supports 1 Gbps link data rate
- Gigabit Ethernet short wavelength (GbE SX) for multimode fiber infrastructures; supports 1 Gbps link data rate
- 1000BASE-T Ethernet for Category 5 or Category 6 copper infrastructures; autonegotiates to 10, 100, or 1000 Mbps
The OSA-Express3 Ethernet features support:
- Queued Direct Input/Output (QDIO) - uses memory queues and a
signaling protocol to directly exchange data between the OSA
microprocessor and the network software for high-speed communication.
- QDIO Layer 2 (Link layer) - for IP (IPv4, IPv6) or non-IP (AppleTalk DECnet, IPX, NetBIOS, or SNA) workloads. Using this mode the Open Systems Adapter (OSA) is protocol-independent and Layer-3 independent. Packet forwarding decisions are based upon the Medium Access Control (MAC) address.
- QDIO Layer 3 (Network or IP layer) - for IP workloads. Support for packet forwarding is based upon IP address or virtual MAC address. Guests may share OSA's MAC address or guests may have their own unique virtual MAC address.
CHPID Applicable Purpose/Traffic
type features
----- ----------- ----------------------------------------------------
OSC 1000BASE-T OSA-Integrated Console Controller (OSA-ICC).
Supports TN3270E, non-SNA DFT to IPL CPCs & LPs.
OSD All Queue Direct Input/Output (QDIO) architecture;
TCP/IP traffic when Layer 3 (uses IP address) and
Protocol-independent when Layer 2 (uses MAC address).
OSE 1000BASE-T Non-QDIO; For SNA/APPN/HPR traffic and TCP/IP
passthru traffic.
OSM 1000BASE-T OSA-Express for Unified Resource Manager.
Connectivity to intranode management network
(INMN) from z196 to Unified Resource Manager
functions.
OSN GbE OSA-Express for NCP; Appears to OS as a device
1000BASE-T supporting channel data link control (CDLC)
protocol. Enables Network Control Program (NCP)
channel-related functions such as loading and
dumping to NCP. Provides LP-to-LP connectivity
OS to IBM Communication Controller for Linux (CCL).
OSX 10 GbE OSA-Express for zBX. Provides connectivity
and access control to the intraensemble
data network (IEDN) from z196 to
Unified Resource Manager functions.
For network performance-inbound workload queuing: z/OS workloads are becoming more diverse; each type of workload may have unique service level requirements. OSA-Express-3 introduces inbound workload queuing (IWQ), which creates multiple input queues and allows OSA to differentiate workloads "off the wire" and then assign work to a specific input queue (per device) to z/OS. With each input queue representing a unique type of workload, each having unique service and processing requirements, the IWQ function allows z/OS to preassign the appropriate processing resources for each input queue. This approach allows multiple concurrent z/OS processing threads to then process each unique input queue (workload), avoiding traditional resource contention. In a heavily mixed workload environment, this "off the wire" network traffic separation provided by OSA-Express3 IWQ reduces the conventional z/OS processing required to identify and separate unique workloads, which results in improved overall system performance and scalability.
A primary objective of IWQ is to provide improved performance for business-critical interactive workloads by reducing contention created by other types of workloads. The types of z/OS workloads that are identified and assigned to unique input queues are:
- z/OS Sysplex Distributor traffic - Network traffic that is associated with a distributed dynamic virtual IP address (DVIPA) is assigned a unique input queue allowing, the Sysplex Distributor traffic to be immediately distributed to the target host.
- z/OS bulk data traffic - Network traffic that is dynamically associated with a streaming (bulk data) TCP connection is assigned to a unique input queue allowing, the bulk data processing to be assigned the appropriate resources and isolated from critical interactive workloads.
IWQ is supported on z196 and z10 and is exclusive to OSA-Express3 CHPID types OSD and OSX (exclusive to z196). IWQ is also supported by the z/OS operating system and by z/VM for guests. Refer to the Software requirements section.
For network management - query and display OSA configuration: Previously, OSA-Express system architecture introduced the capability for operating systems to dynamically register the OSA configuration. This approach significantly improved the OSA-Express usability by reducing the burden placed on the system administrator to manually configure OSA-Express for each unique operating system configuration. Traditionally, the Open Systems Adapter Support Facility (OSA/SF) has provided the administrator with the ability to monitor the OSA configuration.
As additional complex functions have been added to OSA, the ability for the system administrator to display, monitor, and verify the specific current OSA configuration unique to each operating system has become more complex. OSA-Express3 introduces the capability for the operating system to directly query and display the current OSA configuration information (similar to OSA/SF). z/OS exploits this new OSA capability by introducing a new TCP/IP operator command called Display OSAINFO. Display OSAINFO allows the operator to monitor and verify the current OSA configuration, which helps to improve the overall management, serviceability, and usability of OSA-Express3.
Display OSAINFO is exclusive to OSA-Express3 CHPID types OSD, OSM, and OSX, the z/OS operating system, and z/VM for guest exploitation. Refer to the Software requirements section.
Access to a Parallel Sysplex environment
Parallel Sysplex is a synergy between hardware and software - a highly advanced technology for clustering designed to enable the aggregate capacity of multiple z/OS systems to be applied against common workloads. z/OS combined with z196, z10 and z9 machines, coupling facilities, Server Time Protocol (STP), and coupling links (InfiniBand, ISC-3), allows you to harness the power of multiple systems as though they were a single logical computing system.
Coupling links provide a path to transmit/receive Coupling Facility (CF) data as well as Server Time Protocol (STP) time keeping messages. The CF data may be exchanged between z/OS and the CF or between CFs. The primary Coupling Facility configuration options are a stand-alone Coupling Facility or a CF LPAR on a server.
The primary ways to configure Coupling facilities are:
- Stand-alone Coupling Facility, an option where the Coupling Facility LPAR running the CFCC code is not co-located with z/OS images of its Parallel Sysplex on the same System z server. This option provides for failure isolation, so that a single failure does not affect the z/OS images and the CF at the same time. The server itself may be configured with Integrated Coupling Facility specialty engines.
- Internal Coupling Facility, an option where the Coupling Facility is co-located with z/OS images of its Parallel Sysplex on the same System z server. This option can be used as a backup Coupling Facility in a data sharing environment or as the primary facility in a resource sharing environment.
InfiniBand coupling links are high-speed links, up to 6 GBps for 12x InfiniBand and up to 5 Gbps for 1x InfiniBand:
- 12x InfiniBand for short distances - up to 150 meters (492 feet)
- 1x InfiniBand for longer distances - up to 10 km (6.2 miles) unrepeated
InterSystem Channel-3 (ISC-3) links continue to be offered, as a migration aid, supporting a link data rate of 2 Gbps. ISC-3 is supported at the same distance as 1x InfiniBand. Internal coupling links (ICs) can also be used for internal communication between coupling facilities (CFs) defined in LPARs and z/OS images on the same server.
Note: The InfiniBand link data rates do not represent the performance of the link. The actual performance is dependent upon many factors including latency through the adapters, cable lengths, and the type of workload. Systems Lab Services can assist your migration to PSIFB coupling links by providing services to assess the impact of the migration or to assist with the implementation of the migration.
Parallel Sysplex Enhancements
As data sharing workloads continue to grow, the Parallel Sysplex infrastructure needs to anticipate the increased requirements for coupling resources. To do this, we have added connectivity capabilities to support larger data sharing environments.
Connectivity improvements with up to 80 coupling links: The IBM zEnterprise 196 increases the number of external coupling links allowed from 64 to 80. This allows the full configuration of 32 PSIFB links and 48 ISC-3 links to be used. In addition, one can also configure up to 32 (internal) IC links for coupling between images defined on the same server. Having more coupling links is important to provide sufficient coupling connectivity for larger single Parallel Sysplexes, as well as for configurations where the same server hosts multiple Parallel Sysplexes and Coupling Facility images.
Connectivity improvements with 128 CHPIDs per server: To support larger Parallel Sysplexes with ever-increasing amounts of data sharing traffic to the Coupling Facility, the throughput and capacity of more coupling CHPIDs are also required. With z196, we have increased the number of coupling CHPIDs per server from 64 to 128. Since IFB links allow for multiple (logical) CHPIDs over the same (physical) link, this can also allow for larger Parallel Sysplexes without requiring more coupling link hardware.
Coupling Facility Control Code Level 17
Connectivity improvements with up to 2047 structures: CFCC Level 17 increases the number of structures that can be allocated in a CFCC image from 1023 to 2047. Allowing more CF structures to be defined and used in a sysplex permits more discrete data sharing groups to operate concurrently, and can help environments requiring many structures to be defined, such as to support SAP or service providers. z196 and CFCC level 17 provide improved serviceability of Coupling Facilities with enhanced data collection and triggering of nondisruptive CF dumps. Refer to the Software requirements section.
STP - time synchronization for Parallel Sysplex
Server Time Protocol (STP) is designed to allow events occurring in different servers to be properly sequenced in time. STP is designed for servers that have been configured in a Parallel Sysplex or a basic sysplex (without a coupling facility), as well as servers that are not in a sysplex but need time synchronization.
STP is a server-wide facility that is implemented in the Licensed Internal Code (LIC), presenting a single view of time to Processor Resource/Systems Manager (PR/SM). STP uses a message-based protocol in which timekeeping information is passed over externally defined coupling links between servers. The coupling links that can be used to transport STP messages include 12x or 1x InfiniBand (IFB) links and InterSystem Channel-3 (ISC-3) links configured in peer mode. These can be the same links that already are being used in a Parallel Sysplex for coupling facility (CF) message communication. STP can also use ICB-3 and ICB-4 links on servers that support them.
The STP design introduced a concept called Coordinated Timing Network (CTN). A Coordinated Timing Network (CTN) is a collection of servers and coupling facilities that are time-synchronized to a time value called Coordinated Server Time.
A CTN can be configured in two ways:
- STP-only CTN which does not require a Sysplex Timer.
- Mixed CTN (External Time Reference (ETR) and STP) which requires a Sysplex Timer. The Sysplex Timer provides the timekeeping information in a Mixed CTN. Even though the z196 does not support attachment to a Sysplex Timer, it can participate in a Mixed CTN that has either a z10 or z9 synchronized to the Sysplex Timer. This maintains the capability for enterprises to concurrently migrate from an existing ETR network to a Mixed CTN and from a Mixed CTN to an STP-only CTN.
Water Cooling
z196 introduces water cooling unit (WCU) technology, which provides the ability to cool systems with user-chilled water. In order to allow users to remove additional heat produced by non-MCM components in the system such as power, memory, and I/O to water, z196 also supports the exhaust air heat exchange, which is standard on systems with the WCU.
Conversions from machine refrigeration unit (MRU) to WCU require a frame roll, and will not be done in the field.
High-voltage DC power
In data centers today, many businesses are paying increasing electric bills and are also running out of power. High-voltage DC power, an optional feature on z196, increases the voltage directly into the system. This can save System z users 1-3%, on average, on their power bills without having to go through a step-down.
High-voltage DC power is added to the universal power input that is available on the z196. The voltage level is in the range of 380V-570V DC, and requires 2 or 4 x 60A line cord(s), depending on configuration. These line cords (#8965, #8963) are offered on new build as well as MES orders.
Top exit I/O cabling
On z196 you now have the option of ordering the infrastucture to support top exit of your fiber optic cables (ESCON, FICON, OSA, 12x InfiniBand, 1x InfiniBand, and ISC-3) as well as your copper cables for the 1000BASE-T Ethernet features.
Top exit I/O cabling is designed to provide you with an additional option. Instead of all of your cables 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. This option is offered on new build as well as MES orders.
Static power save mode
With the introduction of static power save mode, IBM is continuing to help provide energy management capabilities to facilitate energy savings. You now have the ability to reduce the power consumption of the IBM zEnterprise 196.
Static power save mode is designed to reduce power consumption on z196 when full performance is not required. It can be switched on and off during runtime with no disruption to currently running workloads, aside from the change in performance. On air-cooled models, Static power save mode can be entered once in a calendar day.
Using the Hardware Management Console (HMC), as well as the Active Energy Manager (AEM), you can use static power save mode for:
- Periods of lower utilization - weekends, third shift
- Capacity backup systems - systems used for emergency backup; keep them "running" but reduce energy consumption. Systems can quickly be brought back to full performance.
This could result in a 20% - 30% reduction in power consumption (depending on system configuration). If you have also implemented dynamic control of cooling (for example, through the integration of Active Energy Manager with facility management applications) the air conditioning for the cooling zone can be turned down and additional energy can be saved.
Static power save mode is supported by z/OS and z/VM. Refer to the Software requirements section.
Access to Capacity on Demand
CAPACITY ON DEMAND - TEMPORARY CAPACITY:
z196 uses the Capacity on Demand (CoD) architecture implemented on z10. This architecture improved the capability to access and manage processing capacity on a temporary basis, providing increased flexibility for On Demand environments.
Capacity Back Up (CBU) gives you temporary access to dormant processor units (PUs), intended to replace capacity lost within the enterprise due to a disaster. CP capacity or any and all specialty engine types (ICF, IFL, SAP, zAAP, zIIP) can be added up to what the physical hardware model can contain for up to 10 days for a test activation or 90 days for true disaster recovery. The CBU entitlement records (#6818) contain an expiration date that is established at the time of order and is dependent upon the quantity of CBU years (#6817).
You have the capability to extend your CBU entitlements through the purchase of additional CBU years. The number of #6817 per instance of #6818 remains limited to five. Fractional years are rounded up to the near whole integer when calculating this limit. One test activation is provided for each additional CBU year added to the CBU entitlement record. The number of test activations per CBU entitlement record coincides with the number of years assigned to the CBU record. This equates to one test activation per year for each CBU entitlement purchased. Additional test activations are available in quantities of one and the number of test activations is limited at 15 per CBU record.
Capacity for Planned Events (CPE): Temporary access to dormant processing units (PUs), intended to replace capacity lost within the enterprise due to a planned event such as a facility upgrade or system relocation. CP capacity or any and all specialty engine types (zIIP, zAAP, SAP, IFL, ICF) can be added up to what the physical hardware model can contain for up to 3 days.
On/Off Capacity on Demand (On/Off CoD): Temporary access to dormant PUs, intended to augment the existing capacity of a given system. On/Off CoD helps you contain workload spikes that may exceed permanent capacity such that Service Level Agreements cannot be met and business conditions do not justify a permanent upgrade. As on System z10, On/Off CoD can be pre-or post-paid, token or non-token.
Capacity provisioning: An installed On/Off CoD record is a necessary prerequisite for automated control of temporary capacity through z/OS MVS Capacity Provisioning. z/OS MVS Capacity Provisioning allows you to set up rules defining the circumstances under which additional capacity should be provisioned in order to fulfill a specific business need. The rules are based on criteria such as a specific application, the maximum additional capacity that should be activated, and time and workload conditions. This support provides a fast response to capacity changes and ensures sufficient processing power is available with the least possible delay even if workloads fluctuate. Refer to z/OS MVS Capacity Provisioning User's Guide (SA33-8299) for more information.
CAPACITY ON DEMAND - PERMANENT CAPACITY:
Customer Initiated Upgrade (CIU) facility: When your business needs additional capacity quickly, Customer Initiated Upgrade (CIU) is designed to deliver it. CIU is designed to allow you to respond to sudden increased capacity requirements by requesting a z196 PU and/or memory upgrade via the Web, using IBM Resource Link, and downloading and applying it to your z196 server using your system's Remote Support connection. Further, with the Express option on CIU, an upgrade may be made available for installation as fast as within a few hours after order submission.
Permanent upgrades: Orders (MESs) of all PU types and memory for System z196 servers that can be delivered by Licensed Internal Code, Configuration Control (LICCC) are eligible for CIU delivery. CIU upgrades may be performed up to the maximum available processor and memory resources on the installed server, as configured. While capacity upgrades to the server itself are concurrent, your software may not be able to take advantage of the increased capacity without performing an Initial Programming Load (IPL).
Plan ahead memory: As on System z10, memory upgrades can be preplanned to be nondisruptive. The preplanned memory feature adds the necessary physical memory required to support target memory sizes. If you anticipate an increase in memory requirements, a "target" logical memory size can now be specified in the configuration tool along with a "starting" logical memory size. The configuration tool then calculates the physical memory required to satisfy this target memory. Should additional physical memory be required, it is fulfilled with the preplanned memory features.
Capacity on Demand - enhancements
Auto renewal of On/Off CoD allows you to choose the automatic renewal of installed On/Off CoD records to automatically update the expiration date of those records.
Order Permanent Upgrade now allows you to order additional unassigned capacity by providing you with the options to adjust the system's total and active capacity levels. You are billed for the purchase of any new capacity, however no charges are made for deactivation of the capacity as long as new capacity is purchased.
On/Off CoD Administrative Test provides you the capability to test the Capacity on Demand process, for training and API testing. This differs from the On/Off CoD no-charge test in that no capacity is activated with the test.
With your z196, for Capacity on Demand records shipped with the system, such as CBU and/or CPE, up to 4 come pre-installed instead of being staged on the Service Element. If more than 4 records are ordered with the system, none will be installed and all will be staged. IBM installation service representatives will assist you with the installation of the staged records.
HMC system support
The new functions available on the Hardware Management Console (HMC) version 2.11.0, as described, apply exclusively to z196. However, the HMC version 2.11.0 will also support the systems listed in the table below.
The 2.11.0 HMC now supports up to two 10/100/1000 Mbps Ethernet LANs.
Family Machine Type Firmware Driver SE Version z10 BC 2098 79 2.10.2 z10 EC 2097 79 2.10.2 z9 BC 2096 67 2.9.2 z9 EC 2094 67 2.9.2 z890 2086 55 1.8.2 z990 2084 55 1.8.2 z800 2066 3G 1.7.3 z900 2064 3G 1.7.3 9672 G6 9672/9674 26 1.6.2 9672 G5 9672/9674 26 1.6.2
HMC Security
- Security Improvements
The Monitor System Events task now allows for security logs to result in email notifications using the same type of filters and rules that are used for both Hardware and Operating System messages.
The Password Profiles task now allows for the removal of pre-defined password rules by the access administrator.
- Offload Support for Customer Audit
The Audit and Log Management task adds the ability to offload a number of HMC and SE files (Audit Log, Console Event Log, Console Service History, Tasks Performed Log, and Security Logs). You can now offload to removable media as well as to remote locations via FTP. The offloaded data is available in two forms: human (HTML) readable and machine (XML) readable. Offloading can be manually initiated via the new Audit and Log Management task or scheduled via the Scheduled Operations task.
- HMC User ID Templates and Patterns
This function allows the ability to manage adding and removing HMC users in an environment where an LDAP server is the central authority for specifying which users have access to an HMC.
- View Only User IDs/Access for HMC/SE
HMC and SE User ID support allows the ability to create users who have View Only access to select tasks. The new View Only tasks are the existing tasks with minor modifications to their GUI controls to prevent any actions from being taken.
Monitoring
- Environmental Efficiency Statistics Task
The Environmental Efficiency Statistics task adds the ability to show historical power consumption and thermal information as well as a historical summary of processor and channel utilization. The data is presented in table form, graphical ("histogram") form, and it can also be exported to a Comma Separated Value (CSV) file.
- Monitors Dashboard Task provides the following
capabilities:
- A tree-based view of resources in the IBM System z.
- Allows a user to view aggregated activity when looking at large configurations.
- Allows for more detail for objects with smaller scope.
- Supports new graphical ways of displaying data such as history charts.
Future changes to the existing activity task will be minimized.
HMC User Interface Improvements
- Classic UI and User Settings Task Improvements
The User Settings and Console Default User Settings console actions now have a 'Classic Style' tab. This tab allows users to change the look of the Classic UI.
- Additional Control over the Toggle Lock and Details Tasks
In prior releases, all Task Roles contain the Toggle Lock task and the Details tasks for the various managed objects. The Customize User Controls task now includes the Toggle Lock and Details tasks which gives the administrator the ability to remove these tasks for certain users.
- Allow setting Acceptable Status for Multiple Objects
In prior releases setting up Acceptable Status on a new install requires the user to set the status one object at a time. A new field, "Save as default", was added to each Acceptable Status task to allow the user to change the acceptable status for all of the currently defined objects of that type.
LPAR Controls Enhancements
- Change LPAR Controls - Export to File
The Change LPAR Controls task adds the ability to export the Change LPAR Controls table data to a Comma Separated Value (CSV) file. This support is only available when a user is connected to the HMC remotely via a web browser.
- Change LPAR Controls Scheduled Operation now allows the partition capping value to be specified. Details about an existing Change LPAR Controls scheduled operation can now be viewed on the Support Element.
Capacity on Demand
- Auto-renewal of post-paid On/Off CoD records
Resource Link will monitor all installed On/Off CoD records. Every 90 days, Resource Link will generate a replenishment record for each installed record that will move the expiration date out 180 days. The record must be "enabled" for auto-renewal. The next time the system connects to RETAIN, a replenishment record is pushed to the system and installed. Once set, no customer renewal action is required.
- On/Off CoD Administrative Test
Resource Link re-introduces the "Order Administrative On/Off CoD test". This option supports standard order flow, including approval steps that allow for testing of processes / procedures without any resulting Hardware or Software charges.
- Other CoD Enhancements
Ordering options were added to Resource Link to allow the purchase of unassigned CP or IFL capacity and to allow users to explore capacity needs / upgrade options prior to purchasing a permanent engine upgrade.
SNMP and CIM API Enhancements
- SNMP v3.0 API Support adds authentication and privacy security enhancements to the HMC Java API's. Users need to configure SNMPv3 authentication parameters using the Customize API Settings task.
- HMC SNMP and CIM API Enhancements
The SNMP and CIM APIs now allow dynamic changes to the logical partition Group Capacity setting, and allow User ID audit reports to be generated and retrieved.
HMC Hardware
- Removable Writable Media to Replace HMC DVD-RAM
A removable writable media was added as an alternate to the HMC DVD-RAM. This media is the USB Flash Memory Drive (UFD).
- HMC/SE Customer and SE Networks Gigabit LAN
The Ethernet switch hardware used to interconnect various parts of the system has been upgraded. The SMC Networks switch now contains 16 ports which support 1 GB speeds.
Removal of Dynamic ICF Expansion Option
- Remove Support for Dynamic ICF Expansion Option
Activation Profiles removed support for Dynamic ICF expansion both across ICFs and across pool of shared CPs. The following logical Processor Assignment selections for a Coupling Facility mode logical partition were removed:
- Dedicated and not dedicated internal coupling facility processors
- Dedicated internal coupling facility processors and not dedicated central processors
Advanced Workload License Charges
IBM is introducing a new software pricing structure, called Advanced Workload License Charges (AWLC), for eligible z/OS and z/TPF software programs running on a z196. AWLC is the default pricing metric for standalone z196 servers. IBM will also provide a transition program from Workload License Charges to AWLC for sysplex customers who have not yet fully migrated to z196 servers. This ensures that aggregation benefits are maintained and also phases in the benefits of AWLC pricing as customers migrate.
Solution Edition Series
The System z Solution Edition Series delivers mainframe qualities of service at attractive prices for new workloads. Offerings will continue to be enhanced to leverage new zEnterprise platform and IBM software functionality.
Accessibility by people with disabilities
A U.S. Section 508 Voluntary Product Accessibility Template (VPAT) containing details on accessibility compliance can be requested at:
http://www.ibm.com/able/product_accessibility/index.html
Section 508 of the US Rehabilitation Act
IBM zEnterprise 196 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.
Back to top
|
|
| Product positioning |
|
|
The IBM zEnterprise System (TM) offers a total systems approach to delivering advanced heterogeneous systems management function that is unmatched in the industry. The announcement of zEnterprise System takes systems technology to the next level. The IBM zEnterprise System consists of the traditional subsystems -- CPC, Memory, I/O and power/packaging/cooling -- and new platform management firmware that is designed to enable you to run heterogeneous workloads under the management of one system.
The IBM zEnterprise System is a powerful yet flexible server that
thinks beyond technology to drive business innovation. The server is
designed to offer relief from increasing IT costs, particularly those
associated with server sprawl. The zEnterprise System is designed to
provide a secure, highly virtualized platform for application
development. Its CPC has 80 user-customizable processor units (PUs) in a
single footprint, providing the opportunity for growth. The IBM
zEnterprise 196 is built on the inherent strengths of the System z
platform, including scalability, availability, security, reliability, and
world-class virtualization.
Back to top
|
|
| Models |
|
|
Model summary matrix
| Model | PUs | Memory |
|---|---|---|
| M15 | 1 to 15 | 32 to 704 GB |
| M32 | 1 to 32 | 32 to 1520 GB |
| M49 | 1 to 49 | 32 to 2288 GB |
| M66 | 1 to 66 | 32 to 3056 GB |
| M80 | 1 to 80 | 32 to 3056 GB |
Note: A portion of the total memory is delivered and reserved for fixed HSA.
Note: The maximum amount of memory that can be configured for a single LPAR is 1TB.
Note: All PU conversions can be performed concurrently.
Processor Unit Summary
Listed below are the minimums and maximums of processor units that customers may permanently purchase. The feature codes affected are identified in parentheses.
Total CP7s(1) IFLs uIFLs ICFs zAAPs zIIPs SAPs
PUs (#1880) (#1881) (1886) (#1882) (#1884) (#1885) (#1883)
Model Avail Min/Max Min/Max Min/Max Min/Max Min/Max Min/Max Min/Max
----- ----- ------- ------- ------- ------- ------- ------- -------
M15 15 0 - 15 0 - 15 0 - 14 0 - 15 0 - 07 0 - 07 0 - 04
M32 32 0 - 32 0 - 32 0 - 31 0 - 16 0 - 16 0 - 16 0 - 10
M49 49 0 - 49 0 - 49 0 - 48 0 - 16 0 - 24 0 - 24 0 - 15
M66 66 0 - 66 0 - 66 0 - 65 0 - 16 0 - 33 0 - 33 0 - 20
M80 80 0 - 80 0 - 80 0 - 79 0 - 16 0 - 40 0 - 40 0 - 18
Notes:
- (1) A z196 with subcapacity CPs can have a maximum of 15 subcapacity features CP4 (#1877), CP5 (#1878), or CP6 (#1879)
- One CP (#1877, #1878, #1879, or #1880), IFL (#1881) or ICF (#1882) is required for any model.
- The total number of PUs purchased can not exceed the total number available for that model.
- One CP (#1877, #1878, #1879 or #1880) must be installed with the installation of any uIFLs that are installed, or prior to the installation of any uIFLs.
- One CP (#1877, #1878, #1879 or #1880) must be installed with the installation of any zAAPs that are installed, or prior to the installation of any zAAPs.
- The total number of zAAPs purchased must be equal to the number of CPs (#1877, #1878, #1879, or #1880) purchased for any machine.
- One CP (#1877, #1878, #1879 or #1880) must be installed with the installation of any zIIPs that are installed, or prior to the installation of any zIIPs.
- The total number of zIIPs purchased must be equal to the number of CPs (#1877, #1878, #1879, or #1880) purchased for any machine.
- There are two spares per system.
- The number of SAPs provided to the customer as standard
PUs are as follows:
- Model M15 = Three SAPs
- Model M32 = Six SAPs
- Model M49 = Nine SAPs
- Model M66 = Twelve SAPs
- Model M80 = Fourteen SAPs
Customer setup (CSU)
Customer setup is not available on this machine.
Devices supported
Peripheral hardware and device attachments
IBM devices previously attached to IBM System z9, System z10 and zSeries servers are supported for attachment to IBM zEnterprise 196 channels, unless otherwise noted. The subject I/O devices must meet ESCON or FICON architecture requirements to be supported. I/O devices that meet OEMI architecture requirements are supported only using an external converter. Prerequisite Engineering Change Levels may be required. For further detail, contact IBM service personnel.
While the z196 supports devices as described above, IBM does not commit to provide support or service for an IBM device that has reached its End of Service effective date as announced by IBM.
Note: IBM cannot confirm the accuracy of performance, compatibility, or any other claims related to non-IBM products. Questions regarding the capabilities of non-IBM products should be addressed to the suppliers of those products.
Information on switches and directors qualified for IBM System z FICON and FCP channels can be found in the Library section of Resource Link.
- http://www.ibm.com/servers/resourcelink/
Model conversions
Not available.
Back to top
|
|
| Technical description |
|
|
Physical specifications |
Operating environment |
Limitations |
|
Hardware requirements |
Software requirements |
Physical specifications
Physical Specifications - AIR Cooled Machine
Dimensions (rounded to the nearest 0.1" or 0.1cm):
Depth Width Height
----- ----- ------
Complete installed system
- Inches 71.0 61.6 79.3
- Centimeter 180.3 156.5 201.3
- Inches (O/H IO cable exit) 71.0 72.7 84.8
- Centimeter (O/H IO cable exit) 180.3 184.7 215.3
Each Frame unpacked on casters with one side cover
- Inches 50.0 30.2 79.3
- Centimeter 127.0 76.7 201.3
- Inches (O/H IO cable exit) 50.0 30.5 79.3
- Centimeter (O/H IO cable exit) 127.0 77.4 201.3
Each Frame uncrated on casters with all packaging
A-Frame with height reduction
- Inches 56.5 32.5 71.0
- Centimeter 143.5 82.5 180.3
A-Frame no height reduction
- Inches 56.5 32.5 80.0
- Centimeter 143.5 82.5 203.2
Z-Frame with height reduction
- Inches 55.0 32.0 71.0
- Centimeter 139.7 81.3 180.3
Z-Frame no height reduction
- Inches 55.0 32.0 80.0
- Centimeter 139.7 81.3 203.2
Crated frames (in ARBO crate)
A-Frame
- Inches 63.7 36.9 90.6
- Centimeter 161.6 93.7 230.2
Z-Frame
- Inches 63.7 36.9 90.6
- Centimeter 161.6 93.7 230.2
Approximate weight:
New Build New Build
Minimum Maximum
System System
Model M15 Model M80
One I/O Cage Max # of I/O Cages
------------ ------------------
System with IBF Feature
- kg 1448.0 2271.0
- lb 3258.0 5110.0
- kg (O/H IO cable exit) 1532.4 2355.4
- lb (O/H IO cable exit) 3448.0 5300.0
System without IBF Feature
- kg 1248.0 1968.0
- lb 2807.0 4430.0
- kg (O/H IO cable exit) 1332.4 2052.4
- lb (O/H IO cable exit) 2997.0 4620.0
To ensure installability and serviceability in non-IBM industry-standard racks, review the installation planning information for any product-specific installation requirements.
The DC Power feature has no effect on the machine dimensions and weight.
Physical Specifications - WATER Cooled Machine
Dimensions (rounded to the nearest 0.1" or 0.1cm):
Depth Width Height
----- ----- ------
System with all covers
- Inches 75.0 61.6 79.3
- Centimeter 190.5 156.5 201.3
- Inches (O/H IO cable exit) 75.0 72.7 84.8
- Centimeter (O/H IO cable exit) 190.5 184.7 215.3
Each Frame unpacked on casters with one side cover
- Inches 54.0 30.2 79.3
- Centimeter 137.2 76.7 201.3
- Inches (O/H IO cable exit) 54.0 30.5 79.3
- Centimeter (O/H IO cable exit) 137.2 77.4 201.3
Each Frame uncrated on casters with all packaging
A-Frame with height reduction
- Inches 63.0 32.5 71.0
- Centimeter 160.0 82.5 180.3
A-Frame no height reduction
- Inches 63.0 32.5 80.0
- Centimeter 160.0 82.5 203.2
Z-Frame with height reduction
- Inches 59.0 32.0 71.0
- Centimeter 149.9 81.3 180.3
Z-Frame no height reduction
- Inches 59.0 32.0 80.0
- Centimeter 149.9 81.3 203.2
Crated frames (in ARBO crate)
A-Frame
- Inches 68.0 36.9 90.6
- Centimeter 172.7 93.7 230.2
Z-Frame
- Inches 63.7 36.9 90.6
- Centimeter 161.6 93.7 230.2
Approximate weight:
New Build New Build
Minimum Maximum
System System
Model M15 Model M80
One I/O Cage Max # of I/O Cages
------------ ------------------
System with IBF Feature
- kg 1540.0 2296.0
- lb 3465.0 5167.0
- kg (O/H IO cable exit) 1624.4 2380.4
- lb (O/H IO cable exit) 3655.0 5357.0
System without IBF Feature
- kg 1340.0 2019.0
- lb 3014.0 4543.0
- kg (O/H IO cable exit) 1424.4 2103.4
- lb (O/H IO cable exit) 3204.0 4733.0
To ensure installability and serviceability in non-IBM industry-standard racks, review the installation planning information for any product-specific installation requirements.
The DC Power feature has no effect on the machine dimensions and weight.
Operating environment
Operating Environment - AIR Cooled Machine
- Temperature:
- 10 to 32 degrees C (50 to 89 degrees F) for all models up to 900 meters; maximum ambient reduces 1 degree C per 300 meters above 900 meters
- Relative Humidity: 8 to 80% (percent)
- Wet Bulb (Caloric Value): 23 degrees C (73 degrees F) Operating Mode
- Max Dew Point: 17 degrees C (62.6 degrees F) - Operating Mode
- Electrical Power:
- 27.8 kVA (typically 0.99 PF at 200V)
- 28.4 kVA (typically 0.97 PF at 380V)
- 28.95 kVA (typically 0.95 PF at 480V)
- Capacity of Exhaust: 5950 cubic meters / hour (3500 CFM)
- Acoustical noise level (nominal conditions):
- Typical Configuration: Model M32, 1 I/O cage, 1 I/O drawer
- Declared A-Weighted Sound Power Level, LWAd(B) = 7.7
- Declared A-Weighted Sound Pressure Level, LpAm(dB) = 59
- Maximum Configuration: Model M80, 2 I/O cages, 2 I/O drawers
- Declared A-Weighted Sound Power Level, LWAd(B) = 8.1
- Declared A-Weighted Sound Pressure Level, LpAm(dB) = 62
- Typical Configuration: Model M32, 1 I/O cage, 1 I/O drawer
- Leakage and Starting Current: 70 mA / 270 A (~10ms)
Operating Environment - WATER Cooled Machine
- Temperature:
- 10 to 32 degrees C (50 to 89 degrees F) for all models up to 900 meters; maximum ambient reduces 1 degree C per 300 meters above 900 meters
- Relative Humidity: 8 to 80% (percent)
- Wet Bulb (Caloric Value): 23 degrees C (73 degrees F) Operating Mode
- Max Dew Point: 17 degrees C (62.6 degrees F) - Operating Mode
- Electrical Power:
- 27.8 kVA (typically 0.99 PF at 200V)
- 28.4 kVA (typically 0.97 PF at 380V)
- 28.95 kVA (typically 0.95 PF at 480V)
- Capacity of Exhaust: 5950 cubic meters / hour (3500 CFM)
- Acoustical noise level (nominal conditions):
- Typical Configuration: Model M32, 1 I/O cage, 1 I/O drawer
- Declared A-Weighted Sound Power Level, LWAd(B) = 7.8
- Declared A-Weighted Sound Pressure Level, LpAm(dB) = 59
- Maximum Configuration: Model M80, 2 I/O cages, 2 I/O drawers
- Declared A-Weighted Sound Power Level, LWAd(B) = 8.0
- Declared A-Weighted Sound Pressure Level, LpAm(dB) = 61
- Typical Configuration: Model M32, 1 I/O cage, 1 I/O drawer
- Leakage and Starting Current: 70 mA / 270 A (~10ms)
To ensure installability and serviceability in non-IBM industry-standard racks, review the installation planning information for any product-specific installation requirements.
Limitations
Hardware requirements
The hardware requirements for the IBM zEnterprise 196 and its features and functions are identified.
A new driver level is required.
HMC (V2.11.0) plus MCLs and the Support Element (V2.11.1) are available on September 10, 2010.
You should review the PSP buckets for minimum Machine Change Levels (MCLs) and software PTF levels before IPLing operating systems.
Peripheral hardware and device attachments
IBM devices previously attached to IBM System z9, System z10, and zSeries servers are supported for attachment to IBM zEnterprise 196 channels, unless otherwise noted. The subject I/O devices must meet ESCON or FICON architecture requirements to be supported. I/O devices that meet OEMI architecture requirements are supported only using an external converter. Prerequisite Engineering Change Levels may be required. For further detail, contact IBM service personnel.
While the z196 supports devices as described above, IBM does not commit to provide support or service for an IBM device that has reached its End of Service effective date as announced by IBM.
Note: IBM cannot confirm the accuracy of performance, compatibility, or any other claims related to non-IBM products. Questions regarding the capabilities of non-IBM products should be addressed to the suppliers of those products.
Information on switches and directors qualified for IBM System z FICON and FCP channels can be found in the Library section of Resource Link.
- http://www.ibm.com/servers/resourcelink/
Software requirements
Operating System Support
Listed are the operating systems and the minimum versions and releases supported by IBM zEnterprise 196, its functions, and its features. Select the releases appropriate to your operating system environments.
Note: Refer to the z/OS, z/VM, z/VSE subsets of the 2817DEVICE Preventive Service Planning (PSP) bucket prior to installing a z196.
IBM zEnterprise 196 requires at a minimum:
- z/OS V1.12 with PTFs.
- z/OS V1.11 with PTFs.
- z/OS V1.10 with PTFs.
- z/OS V1.9 (1) with PTFs.
- z/OS V1.8 (2) with the IBM Lifecycle Extension for z/OS V1.8 (5638-A01) with required maintenance.
- z/OS V1.7 (3) with the IBM Lifecycle Extension for z/OS V1.7 (5637-A01) with required maintenance.
- z/VM V6.1 with PTFs.
- z/VM V5.4 with PTFs.
- z/VSE V4.1 with PTFs.
- z/TPF V1.1
- Linux on System z distributions:
- Novell SUSE SLES 10 and SLES 11.
- Red Hat RHEL 5.
Note: (1) z/OS V1.9 supports zEnterprise System, however, z/OS V1.9 support will be withdrawn September 30, 2010. After that date, the IBM z/OS Lifecycle Extension for z/OS V1.9 (5646-A01) is required for zEnterprise System. Talk to your IBM representative for details. No exploitation of new zEnterprise System functions is available with z/OS V1.9. Certain functions and features of the zEnterprise System require later releases of z/OS. For the complete list of software support, see the PSP buckets and the Software requirements section.
Note: (2) z/OS V1.8 support was withdrawn September 30, 2009. However, with the z/OS Lifecycle Extension (5638-A01), z/OS V1.8 supports the zEnterprise System. Talk to your IBM representative for details. No exploitation of new zEnterprise System functions is available with z/OS V1.8. Certain functions and features of the zEnterprise System require later releases of z/OS. For the complete list of software support, see the PSP buckets and the Software requirements section.
Note: (3) z/OS V1.7 support was withdrawn September 30, 2008. However, with the z/OS Lifecycle Extension (5637-A01), z/OS V1.7 supports the zEnterprise System. Talk to your IBM representative for details. No exploitation of new zEnterprise System functions is available with z/OS V1.7. Certain functions and features of the zEnterprise System require later releases of z/OS. For the complete list of software support, see the PSP buckets and the Software requirements section.
IBM zEnterprise Unified Resource Manager requires at a minimum:
- z/OS V1.12 with PTFs.
- z/OS V1.11 with PTFs.
- z/OS V1.10 with PTFs.
Older versions of z/OS will tolerate, but do not exploit, IBM zEnterprise Unified Resource Manager.
- z/VM 6.1 with PTFs for enablement of virtual server lifecycle management and support for managing real and virtual networking resources by the Unified Resource Manager.
CP Assist for Cryptographic Function (CPACF) (#3863) enhancements require at a minimum:
- z/OS V1.10, z/OS V1.11, or z/OS V1.12 with the Cryptographic Support
for z/OS V1R10-V1R12 Web deliverable planned to be available September
10, 2010. This may be obtained at:
- http://www.ibm.com/systems/z/os/zos/downloads/
- z/VM V5.4 with PTFs for guest exploitation.
- z/VSE V4.1 and later supports the CPACF features with the functionality supported on IBM System z10.
- z/TPF V1.1.
- Linux on System z distributions:
- Review Novell and Red Hat distribution support statements for a current list of supported hardware.
Crypto Express3 requires at a minimum:
- z/OS V1.10, z/OS V1.11, or z/OS V1.12 with the Cryptographic Support
for z/OS V1R10-V1R12 Web deliverable planned to be available September
10, 2010. This may be obtained at:
- http://www.ibm.com/systems/z/os/zos/downloads/
- z/VM V5.4 with PTFs for guest exploitation.
Note: z/VM V5.4 and later support clear-and secure-key operations.
- z/VSE V4.2 and IBM TCP/IP for VSE/ESA (TM) V1.5.0 with PTFs.
Note: z/VSE supports clear-key RSA operations only.
- z/TPF V1.1 (acceleration mode only).
- Linux on System z distributions:
- Review Novell and Red Hat distribution support statements for current list of supported hardware. Several current distributions support Crypto Express3 in toleration mode. Refer to each distribution for future exploitation support statements for Crypto Express3, as needed.
Crypto Express3 (when defined as a coprocessor) supporting ANSI X9.8 PIN security requires at a minimum:
- z/OS V1.10, z/OS V1.11, or z/OS V1.12 with the Cryptographic Support
for z/OS V1R10-V1R12 Web deliverable planned to be available September
10, 2010. This may be obtained at:
- http://www.ibm.com/systems/z/os/zos/downloads/
- z/VM V5.4 with PTFs for guest exploitation.
- Linux on System z:
- Support is planned for a future release of Common Cryptographic Architecture Support Program for Linux on System z.
Crypto Express3 (when defined as a coprocessor) supporting Enhanced CCA key wrapping requires at a minimum:
- z/OS V1.10, z/OS V1.11, or z/OS V1.12 with the Cryptographic Support
for z/OS V1R10-V1R12 Web deliverable planned to be available September
10, 2010. This may be obtained at:
- http://www.ibm.com/systems/z/os/zos/downloads/
- z/VM V5.4 with PTFs for guest exploitation.
- Linux on System z:
- Support is planned for a future release of Common Cryptographic Architecture Support Program for Linux on System z.
Crypto Express3 (when defined as a coprocessor) supporting Secure Keyed-Hash Message Authentication Code (HMAC) requires at a minimum:
- z/OS V1.10, z/OS V1.11, or z/OS V1.12 with the Cryptographic Support
for z/OS V1R10-V1R12 Web deliverable, planned to be available first
quarter 2011, in addition to PTFs. This may be obtained at:
- http://www.ibm.com/systems/z/os/zos/downloads/
- z/VM V5.4 with PTFs for guest exploitation.
- Linux on System z:
- Support is planned for a future release of Common Cryptographic Architecture Support Program for Linux on System z.
Crypto Express3 (when defined as a coprocessor) supporting Elliptical Curve Cryptography (ECC) Digital Signature algorithm requires at minimum:
- z/OS V1.10, z/OS V1.11, or z/OS V1.12 with the Cryptographic Support
for z/OS V1R10-V1R12 Web deliverable planned to be available September
10, 2010. This may be obtained at:
- http://www.ibm.com/systems/z/os/zos/downloads/
- z/VM V5.4 with PTFs for guest exploitation.
- Linux on System z:
- Support is planned for a future release of Common Cryptographic Architecture Support Program for Linux on System z.
Crypto Express3 (when defined as an accelerator) supporting Modulus Exponent (ME) and Chinese Remainder Theorem (CRT) requires at a minimum:
- z/VM V5.4 with PTFs for guest exploitation.
- Linux on System z distributions:
- Linux on System z - IBM is working with its Linux distribution partners to include support in future Linux on System z distribution releases.
Third subchannel set requires at a minimum:
- z/OS V1.12 with PTFs.
- z/OS V1.11 with PTFs.
- z/OS V1.10 with PTFs.
- Linux on System z distributions:
- Novell SUSE SLES 10 and SLES 11.
- Red Hat RHEL 5.
FICON Express8 (CHPID type FC) when utilizing native FICON or Channel-To-Channel (CTC) requires at a minimum:
- z/OS V1.7(3).
- z/VM V5.4.
- z/VSE V4.1.
- z/TPF V1.1.
FICON Express8 (CHPID type FC) for support of zHPF single-track operations requires at a minimum:
- z/OS V1.10 with PTFs.
- z/OS V1.9 (1) with PTFs.
- z/OS V1.8 (2) with PTFs.
- z/OS V1.7 (3) with PTFs.
- Linux on System z distributions:
- Novell SUSE SLES 11 SP1.
- IBM is working with its Linux distribution partners to include support in future Linux on System z distribution releases.
FICON Express8 (CHPID type FC) for support of zHPF multitrack operations requires at a minimum:
- z/OS V1.10 with PTFs.
- z/OS V1.9 (1) with PTFs.
FICON Express8 and FICON Express4 (CHPID type FC) supporting extension to zHPF multitrack operations requires at a minimum:
- z/OS V1.12 with PTFs.
- z/OS V1.11 with PTFs.
- z/OS V1.10 with PTFs.
FICON Express8 (CHPID type FCP) for support of SCSI devices requires at a minimum:
- z/VM V5.4 with PTFs.
- z/VSE V4.1.
- Linux on System z distributions:
- Novell SUSE SLES 10 and SLES 11.
- Red Hat RHEL 5.
z/OS discovery and autoconfiguration (zDAC) for FICON Express8 and FICON Express4 channels (CHPID type FC) requires at a minimum:
- z/OS V1.12 with PTFs.
Up to 32 HiperSockets (CHPID type IQD) requires at a minimum:
- z/OS V1.12 with PTFs.
- z/OS V1.11 with PTFs.
- z/OS V1.10 with PTFs.
- z/VM V5.4 with PTFs.
- z/VSE V4.1.
- Linux on System z distributions:
- Novell SUSE SLES 10 and SLES 11.
- Red Hat RHEL 5.
HiperSockets network traffic analyzer (HS NTA) on IBM zEnterprise 196 and System z10 requires at a minimum:
- z/VM V5.4 with PTFs for guest exploitation.
- Linux on System z distributions:
- Novell SUSE SLES 11 SP1.
IBM is working with its Linux distribution partners to include support in future Linux on System z distribution releases.
Note: OSA-Express3 GbE and 1000BASE-T contain two ports per PCIe adapter. The ports "share" one channel path identifer (CHPID). There may be two or four ports per feature, depending upon feature number. OSA-Express3 10 GbE SR and LR contain one port per PCIe adapter. There are two ports per feature.
CHPID Applicable Purpose/Traffic
type Features
----- ----------- -------------------------------------------------
OSC 1000BASE-T OSA-Integrated Console Controller (OSA-ICC)
Supports TN3270E, non-SNA DFT to IPL CPCs & LPs.
OSD All Queue Direct Input/Output (QDIO) architecture;
TCP/IP traffic when Layer 3 (uses IP address) and
Protocol-independent when Layer 2 (uses MAC address).
OSE 1000BASE-T Non-QDIO; For SNA/APPN/HPR traffic and TCP/IP
passthru traffic.
OSM 1000BASE-T OSA-Express for Unified Resource Manager.
Connectivity to intranode management network
(INMN) from z196 to Unified Resource Manager
functions.
OSN GbE OSA-Express for NCP; Appears to OS as a device
1000BASE-T supporting channel data link control (CDLC)
protocol. Enables Network Control Program (NCP)
channel-related functions such as loading and
dumping to NCP. Provides LP-to-LP connectivity
OS to IBM Communication Controller for Linux (CCL).
OSX 10 GbE OSA-Express for zBX. Provides connectivity
and access control to the intraensemble
data network (IEDN) from z196 to
Unified Resource Manager functions.
OSA-Express3 GbE LX (#3362) and GbE SX (#3363 and #3373) requires at minimum:
CHPID type OSD with exploitation of all four ports:
- z/OS V1.10.
- z/OS V1.9(1) with PTFs.
- z/OS V1.8(2) with PTFs.
- z/VM V5.4 with PTFs.
- z/VSE V4.1 with PTFs.
- z/TPF V1.1 PUT 4 with PTFs.
- Linux on System z distributions:
- Novell SUSE SLES 10 SP2 and SLES 11.
- Red Hat RHEL 5.2.
CHPID types OSD without maximum port exploitation (one port per PCIe adapter is available for use; two ports per feature):
- z/OS V1.7 (3).
- z/VM V5.4.
- z/VSE V4.1.
- z/TPF V1.1.
- Linux on System z distributions:
- Novell SUSE SLES 10 and SLES 11.
- Red Hat RHEL 5.
CHPID type OSN supporting OSA-Express for NCP (Does not use ports; all communication is LPAR-to-LPAR):
- z/OS V1.9 (1).
- z/OS V1.8 (2).
- z/OS V1.7 (3).
- z/VM V5.4.
- z/VSE V4.1.
- z/TPF V1.1 PUT 4 with APARs.
- Linux on System z distributions:
- Novell SUSE SLES 10 and SLES 11.
- Red Hat RHEL 5.
OSA-Express3 1000BASE-T (#3367 and #3369) requires at minimum:
CHPID type OSC supporting TN3270E and non-SNA DFT:
- z/OS V1.8(2).
- z/OS V1.7(3).
- z/VM V5.4.
- z/VSE V4.1.
CHPID type OSD with exploitation of all four ports:
- z/OS V1.10.
- z/OS V1.9(1) with PTFs.
- z/OS V1.8(2) with PTFs.
- z/VM V5.4 with PTFs.
- z/VSE V4.1 with PTFs.
- z/TPF V1.1 PUT 4 with APARs.
- Linux on System z distributions - for four ports per feature (#3367):
- Novell SUSE SLES 10 SP2 and SLES 11.
- Red Hat RHEL 5.2.
- Linux on System z distributions - for two ports per feature (#3369):
- Novell SUSE SLES 10 and SLES 11.
- Red Hat RHEL 5.
CHPID type OSD without maximum port exploitation (one port per PCIe adapter is available for use; two ports per feature):
- z/OS V1.7 (3).
- z/VM V5.4.
- z/VSE V4.1.
- z/TPF V1.1.
- Linux on System z distributions:
- Novell SUSE SLES 10 and SLES 11.
- Red Hat RHEL 5.
CHPID type OSE supporting 4 or 2 ports per feature:
- z/OS V1.8 (2).
- z/VM V5.4.
- z/VSE V4.1.
CHPID type OSM for intranode management network:
- z/OS V1.12 with PTFs.
- z/OS V1.11 with PTFs.
- z/OS V1.10 with PTFs.
- z/VM V6.1 with PTFs.
- z/VM V5.4 with PTFs to define, modify, and delete OSM CHPID types when z/VM is the controlling LPAR for dynamic I/O.
- IBM is working with its Linux distribution partners to include support in future Linux on System z distribution releases.
CHPID type OSN supporting OSA-Express for NCP:
Note: CHPID type OSN does not use ports. All communication is LPAR-to-LPAR.
- z/OS V1.7(3).
- z/VM V5.4.
- z/VSE V4.1.
- z/TPF V1.1.
- Linux on System z distributions:
- Novell SUSE SLES 10 and SLES 11.
- Red Hat RHEL 5.
OSA-Express3 10 GbE LR (#3370) requires at a minimum:
CHPID type OSD:
- z/OS V1.7 (3).
- z/VM V5.4.
- z/VSE V4.1.
- z/TPF V1.1.
- Linux on System z distributions:
- Novell SUSE SLES 10 and SLES 11.
- Red Hat RHEL 5.
CHPID type OSX for intraensemble data network:
- z/OS V1.12 with PTFs.
- z/OS V1.11 with PTFs.
- z/OS V1.10 with PTFs.
- z/VM V6.1 with PTFs.
- z/VM V5.4 with PTFs to define, modify, and delete OSX CHPID types when z/VM is the controlling LPAR for dynamic I/O.
- IBM is working with its Linux distribution partners to include support in future Linux on System z distribution releases.
Display OSAINFO for OSA-Express3 CHPID types OSD, OSM (exclusive to IBM zEnterprise 196), and OSX (exclusive to IBM zEnterprise 196) on z196 and z10 requires at a minimum:
- z/OS V1.12 with PTFs.
Inbound workload queuing (IWQ) for OSA-Express3 CHPID types OSD and OSX (exclusive to IBM zEnterprise 196) on z196 and z10 requires at a minimum:
- z/OS V1.12 with PTFs.
- z/VM V5.4 with PTFs for guest exploitation.
12x InfiniBand and 1x InfiniBand coupling links require at a minimum:
- z/OS V1.10 with PTFs.
- z/OS V1.9 (1) with PTFs.
- z/OS V1.8 (2) with PTFs.
- z/OS V1.7 (3) with PTFs.
- z/VM V5.4 to define, modify, and delete an InfiniBand coupling link, CHPID type CIB, when z/VM is the controlling LPAR for dynamic I/O.
Coupling Facility Control Code Level 17
Exploiting the new functions of Coupling Facility Control Code Level 17, including support for up to 2047 Coupling Facility structures, requires at a minimum:
- z/OS V1.12 with PTFs.
- z/OS V1.11 with PTFs.
- z/OS V1.10 with PTFs.
- z/VM V5.4 for guest virtual coupling.
Static power save mode requires at a minimum:
- z/OS V1.12 with PTFs.
- z/OS V1.11 with PTFs.
- z/OS V1.10 with PTFs.
- z/VM V6.1 with PTFs.
- z/VM V5.4 with PTFs.
Back to top
|
|
| Publications |
|
|
The following publications are available now in the Library section of Resource Link (TM):
Title Order Number
------------------------------------------------------ ------------
System Overview SA22-1086
Installation Manual - Physical Planning (IMPP) GC28-6897
PR/SM (TM) Planning Guide SB10-7155
IOCP User's Guide SB10-7037
CHPID Mapping Tool User's Guide GC28-6825
Functional Matrix ZSW0-1335
zBX Installation Manual for Physical Planning 2458-001 GC28-6887
zBX Installation Manual for Physical Planning 2458-002 GC27-2611
The following publications are shipped with the product and are available in the Library section of Resource Link:
Title Order Number
-------------------------------------------------- ------------
Installation Manual GC28-6890
Service Guide GC28-6892
Safety Inspection GC28-6894
Safety Notices G229-9054
Environmental Notices and User Guide Z125-5823
Statement of Limited Warranty GC28-6883
License Agreement for Machine Code SC28-6872
License Agreement for Machine Code Addendum for
Elliptical Curve Cryptography GC27-2612
Service Guide for TKE Workstations GC28-6901
The following publications will be available at planned availability in the Library section of Resource Link:
Title Order Number
------------------------------------------------------ ------------
Application Programming Interfaces for Java API-JAVA
Application Programming Interfaces SB10-7030
Capacity on Demand User's Guide SC28-2605
Common Information Model (CIM) Management Interface SB10-7154
Hardware Management Console Operations Guide (V2.11.0) SC28-6895
Parts Catalog GC28-6898
SCSI IPL - Machine Loader Messages SC28-6839
Service Guide for HMCs and SEs GC28-6861
Stand-Alone IOCP User's Guide SB10-7152
Support Element Operations Guide (V2.11.0) SC28-6896
OSA-Express Customer's Guide and Reference SA22-7935
OSA-Express3 Integrated Console Controller Dual-Port
User's Guide SC23-2266
Coupling Links I/O Interface Physical Layer SA23-0395
ESCON and FICON CTC Reference SB10-7034
ESCON I/O Interface Physical Layer SA23-0394
Fiber Optic Cleaning Procedures SY27-2604
Fibre Channel Connection (FICON) I/O Interface
Physical Layer SA24-7172
Maintenance Information for Fiber Optic Links SY27-2597
Planning for Fiber Optic Links GA23-0367
z/Architecture Principles of Operation SA22-7832
z/Architecture Reference Summary SA22-7871
The following publications will be available on November 19, 2010 in the Library section of Resource Link:
Title Order Number
-------------------------------------------------- ------------
Hardware Management Console and Support Element
Operations Guide for Ensembles SC27-2606
Ensemble Performance Management Guide GC27-2607
Ensemble Planning and Configuring Guide GC27-2608
Introduction to Ensembles GC27-2609
Publications for IBM zEnterprise 196 can be obtained at Resource Link by accessing the following Web site:
- www.ibm.com/servers/resourcelink
Using the instructions on the Resource Link panels, obtain a user ID and password. Resource Link has been designed for easy access and navigation.
The following publications are shipped with the IBM zEnterprise BladeCenter Extension (zBX) product and are available in the Library section of Resource Link:
Title Order Number
------------------------------------------------- ------------
zBX Service Guide GC28-6884
zBX Installation Manual 2458-001 GC28-6885
zBX Installation Manual 2458-002 GC27-2610
zBX Safety Inspection GC28-6889
Statement of Limited Warranty GC28-6883
Safety Notices G229-9054
Environmental Notices and User Guide Z125-5823
Back to top
|
|
| Features |
|
|
|
Features - No charge |
Features - Chargeable |
Features - No charge
Machine
Description Type Model Feature
------------------------------------- ------ ----- -------
IBM zEnterprise 196 2817 M15
IBM zEnterprise 196 2817 M32
IBM zEnterprise 196 2817 M49
IBM zEnterprise 196 2817 M66
IBM zEnterprise 196 2817 M80
Service Docs Optional Print 0033
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.
Features - Chargeable
Machine
Description Type Model Feature
----------------------------- ------- ----- -------
IBM zEnterprise 196 2817 M15
M32
M49
M66
M80
MTU 1 - D 0001
MTU 100 - D 0002
MTU 1 - V 0003
MTU 100 - V 0004
GTU 1 - D 0005
GTU 100 - D 0006
GTU 1 - V 0007
GTU 100 - V 0008
Detach zBX 0030
Attach zBX 0031
Manage FW DP 0040
Automate FW DP 0044
Ethernet switch(1) 0070
HMC w/Dual EN 0090
HMC w/Dual EN 0091
I/O Cage ISC-D Airflow 0113
I/O Cage Full Card Airflow 0114
1 CPE Capacity Unit 0116
100 CPE Capacity Unit 0117
10000 CPE Capacity Unit 0118
1 CPE Capacity Unit-IFL 0119
100 CPE Capacity Unit-IFL 0120
1 CPE Capacity Unit-ICF 0121
100 CPE Capacity Unit-ICF 0122
1 CPE Capacity Unit-zAAP 0123
100 CPE Capacity Unit-zAAP 0124
1 CPE Capacity Unit-zIIP 0125
100 CPE Capacity Unit-zIIP 0126
1 CPE Capacity Unit-SAP 0127
100 CPE Capacity Unit-SAP 0128
CPC -Air 0158
CPC -Water 0159
HCA2-C Fanout 0162
HCA2-O fanout for 12x IFB 0163
Fanout Airflow 0165
HCA2-O LR fanout for 1x IFB 0168
ISC-Mother Card 0217
ISC-Daughter Card 0218
ISC-3 link on F/C 0218 0219
Manage Firmware Suite 0019
Automate Firmware Suite 0020
Ensemble membership 0025
Manage FW ISAOPT 0039
Manage FW Pwr Blade 0041
Automate FW ISAOPT 0043
Automate FW Pwr Blade 0045
Automate FW IFL 0052
IFB-MP Daughter Card 0326
STI-A8 Mother Card 0327
STI-A4 Mother Card 0328
TKE workstation 0841
TKE 7.0 LIC 0860
Crypto Express3 0864
TKE addl smart cards 0884
TKE Smart Card Reader 0885
UID Label for DoD 0998
STP Enablement 1021
EMEA Special Operations 1022
16 GB Mem DIMM(5/feat)-A 1616
16 GB Mem DIMM(5/feat)-W 1617
32 GB Mem DIMM(5/feat)-A 1632
32 GB Mem DIMM(5/feat)-W 1633
4 GB Mem DIMM(5/feat)-A 1640
4 GB Mem DIMM(5/feat)-W 1641
LICCC Ship Via Net Ind 1750
Preplanned memory 1996
16GB Memory Capacity Incr 1901
16GB Ftr Converted memory 1902
Line Cord Plan Ahead 2000
16-Port ESCON Card 2323
ESCON Channel port 2324
32 GB Memory 2425
64 GB Memory 2427
96 GB Memory 2429
128 GB Memory 2431
160 GB Memory 2433
192 GB Memory 2435
224 GB Memory 2437
256 GB Memory 2439
320 GB Memory 2441
384 GB Memory 2443
448 GB Memory 2445
512 GB Memory 2447
608 GB Memory 2449
704 GB Memory 2451
US English 2924
France 2928
German 2929
Spanish - Non Spain 2930
Spain 2931
Italian 2932
Canadian French 2935
Portuguese 2978
Brazilian Portuguese 2979
UK English 2980
Norwegian 2983
Sweden Finland 2987
Netherlands 2988
Belgian French 2989
Denmark 2993
Swiss French, German 2997
Balanced Power Plan Ahead 3003
BPR Pair Air Model 3004
BPD Pair Air Model 3005
BPR Pair Water Model 3006
BPD Pair Water Model 3007
Internal Battery IBF-ED 3212
FICON Express8 10KM LX 3325
FICON Express8 SX 3326
OSA-Express3 GbE LX 3362
OSA-Express3 GbE SX 3363
OSA-Express3 1000BASET-EN 3367
OSA-Express3 10 GbE LR 3370
Fill and Drain Kit 3377
Universal Lift Tool/Ladder 3759
CPACF Enablement 3863
I/O Drawer-Air 4000
I/O Cage-Air 4002
I/O Drawer-Water 4004
I/O Cage-Water 4005
A Frame w/o Cargo-Water 4017
A Frame w Cargo-Water 4018
Luxembourg-Belgium ordered 5560
Iceland-Ordered in Denmark 5561
China-Ordered in Hong Kong 5562
Flat panel display 6096
Power Sequence Controller 6501
Additional CBU Test 6805
CBU Records Ordered 6818
FQC Bracket/Mount HW-A 7900
MT-RJ 6 ft harness-A 7902
MT-RJ 8.5 ft harness-A 7903
MT-RJ 5 ft harness-A 7904
MT-RJ 3.5 ft harness-A 7905
LC Dup 6 ft harness-A 7906
LC Dup 8.5 ft harness-A 7908
FQC Bracket/Mount HW-W 7910
MT-RJ 6 ft harness-W 7912
MT-RJ 8.5 ft harness-W 7913
MT-RJ 5 ft harness-W 7914
MT-RJ 3.5 ft harness-W 7915
LC Dup 6.6 ft harness-W 7916
LC Dup 8.5 ft harness-W 7918
Top exit I/O cabling 7942
(NOT TAIWAN)
Side covers 7949
3-in-1 Bolt Down Kit-A 8008
3-in-1 Bolt Down Kit-W 8009
14ft 380-570V DC line cord 8963
14ft 200V 3ph cord 8993
14ft 480V 3ph line cord 8983
Multi Order Ship Flag 9000
Multi Order Rec Only-NB 9001
Multi Order Rec Only-MES 9002
RPO Action Flag 9003
Downgraded PUs Per Request 9004
On/Off CoD Act IFL Day 9888
On/Off CoD Act ICF Day 9889
On/Off CoD Act zAAP Day 9893
On/Off COD authorization 9896
On/Off CoD Act Cap CP Day 9897
Perm upgr authorization 9898
CIU Activation (Flag) 9899
On Line CoD Buying (Flag) 9900
On/Off CoD Act zIIP Day 9908
On/Off CoD Act SAP Day 9909
CBU authorization 9910
CPE authorization 9912
OPO sales authorization 9913
1 MSU day 9917
100 MSU days 9918
10000 MSU days 9919
1 IFL day 9920
100 IFL days 9921
1 ICF day 9922
100 ICF days 9923
1 zIIP day 9924
100 zIIP days 9925
1 zAAP day 9926
100 zAAP days 9927
1 SAP day 9928
100 SAP days 9929
Site Tool Kit 9968
Weight Distribution Kit 9970
Height Reduce Ship 9975
Height Reduce for Return 9976
CP4 1877
CP5 1878
CP6 1879
CP7 1880
IFL 1881
ICF 1882
SAP (optional) 1883
zAAP 1884
zIIP 1885
Unassigned IFL 1886
Total CBU Years Ordered 6817
Single CBU CP-Year 6820
25 CBU CP-Year 6821
Single CBU IFL-Year 6822
25 CBU IFL-Year 6823
Single CBU ICF-Year 6824
25 CBU ICF-Year 6825
Single CBU zAAP-Year 6826
25 CBU zAAP-Year 6827
Single CBU zIIP-Year 6828
25 CBU zIIP-Year 6829
Single CBU SAP-Year 6830
25 CBU SAP-Year 6831
CBU Replenishment 6832
Capacity for Planned Event 6833
OPO Sales Flag 6835
OPO Sales Flag Alteration 6836
Feature Converted CBU CP 6837
Feature Converted CBU IFL 6838
Feature Converted CBU ICF 6839
Feature Converted CBU zAAP 6840
Feature Converted CBU zIIP 6841
Feature Converted CBU SAP 6842
1-Way Processor CP4 1751
2-Way Processor CP4 1752
3-Way Processor CP4 1753
4-Way Processor CP4 1754
5-Way Processor CP4 1755
6-Way Processor CP4 1756
7-Way Processor CP4 1757
8-Way Processor CP4 1758
9-Way Processor CP4 1759
10-Way Processor CP4 1760
11-Way Processor CP4 1761
12-Way Processor CP4 1762
13-Way Processor CP4 1763
14-Way Processor CP4 1764
15-Way Processor CP4 1765
1-Way Processor CP5 1766
2-Way Processor CP5 1767
3-Way Processor CP5 1768
4-Way Processor CP5 1769
5-Way Processor CP5 1770
6-Way Processor CP5 1771
7-Way Processor CP5 1772
8-Way Processor CP5 1773
9-Way Processor CP5 1774
10-Way Processor CP5 1775
11-Way Processor CP5 1776
12-Way Processor CP5 1777
13-Way Processor CP5 1778
14-Way Processor CP5 1779
15-Way Processor CP5 1780
1-Way Processor CP6 1781
2-Way Processor CP6 1782
3-Way Processor CP6 1783
4-Way Processor CP6 1784
5-Way Processor CP6 1785
6-Way Processor CP6 1786
7-Way Processor CP6 1787
8-Way Processor CP6 1788
9-Way Processor CP6 1789
10-Way Processor CP6 1790
11-Way Processor CP6 1791
12-Way Processor CP6 1792
13-Way Processor CP6 1793
14-Way Processor CP6 1794
15-Way Processor CP6 1795
0-Way Processor CP7 1796
1-Way Processor CP7 1797
2-Way Processor CP7 1798
3-Way Processor CP7 1799
4-Way Processor CP7 1800
5-Way Processor CP7 1801
6-Way Processor CP7 1802
7-Way Processor CP7 1803
8-Way Processor CP7 1804
9-Way Processor CP7 1805
10-Way Processor CP7 1806
11-Way Processor CP7 1807
12-Way Processor CP7 1808
13-Way Processor CP7 1809
14-Way Processor CP7 1810
15-Way Processor CP7 1811
401 Capacity Marker 7202
402 Capacity Marker 7203
403 Capacity Marker 7204
404 Capacity Marker 7205
405 Capacity Marker 7206
406 Capacity Marker 7207
407 Capacity Marker 7208
408 Capacity Marker 7209
409 Capacity Marker 7210
410 Capacity Marker 7211
411 Capacity Marker 7212
412 Capacity Marker 7213
413 Capacity Marker 7214
414 Capacity Marker 7215
415 Capacity Marker 7216
501 Capacity Marker 7217
502 Capacity Marker 7218
503 Capacity Marker 7219
504 Capacity Marker 7220
505 Capacity Marker 7221
506 Capacity Marker 7222
507 Capacity Marker 7223
508 Capacity Marker 7224
509 Capacity Marker 7225
510 Capacity Marker 7226
511 Capacity Marker 7227
512 Capacity Marker 7228
513 Capacity Marker 7229
514 Capacity Marker 7230
515 Capacity Marker 7231
601 Capacity Marker 7232
602 Capacity Marker 7233
603 Capacity Marker 7234
604 Capacity Marker 7235
605 Capacity Marker 7236
606 Capacity Marker 7237
607 Capacity Marker 7238
608 Capacity Marker 7239
609 Capacity Marker 7240
610 Capacity Marker 7241
611 Capacity Marker 7242
612 Capacity Marker 7243
613 Capacity Marker 7244
614 Capacity Marker 7245
615 Capacity Marker 7246
700 Capacity Marker 7247
701 Capacity Marker 7248
702 Capacity Marker 7249
703 Capacity Marker 7250
704 Capacity Marker 7251
705 Capacity Marker 7252
706 Capacity Marker 7253
707 Capacity Marker 7254
708 Capacity Marker 7255
709 Capacity Marker 7256
710 Capacity Marker 7257
711 Capacity Marker 7258
712 Capacity Marker 7259
713 Capacity Marker 7260
714 Capacity Marker 7261
715 Capacity Marker 7262
IBM zEnterprise 196 2817 M15
Model M15 - Air Cooled 1125
Model M15 - Water Cooled 1130
A Frame w/o Cargo-Air 4015
A Frame w Cargo-Air 4016
IBM zEnterprise 196 2817 M32
Model M32 - Air Cooled 1126
Model M32 - Water Cooled 1131
IBM zEnterprise 196 2817 M49
Model M49 - Air Cooled 1127
Model M49 - Water Cooled 1132
IBM zEnterprise 196 2817 M66
Model M66 - Air Cooled 1128
Model M66 - Water Cooled 1133
IBM zEnterprise 196 2817 M80
Model M80 - Air Cooled 1129
Model M80 - Water Cooled 1134
IBM zEnterprise 196 2817 M32
M49
M66
M80
800 GB Memory 2453
896 GB Memory 2455
1008 GB Memory 2457
1136 GB Memory 2459
1264 GB Memory 2461
1392 GB Memory 2463
1520 GB Memory 2465
A Fr multinode w/o Cargo-A 4019
A Fr multinode w Cargo-A 4020
16-Way Processor CP7 1812
17-Way Processor CP7 1813
18-Way Processor CP7 1814
19-Way Processor CP7 1815
20-Way Processor CP7 1816
21-Way Processor CP7 1817
22-Way Processor CP7 1818
23-Way Processor CP7 1819
24-Way Processor CP7 1820
25-Way Processor CP7 1821
26-Way Processor CP7 1822
27-Way Processor CP7 1823
28-Way Processor CP7 1824
29-Way Processor CP7 1825
30-Way Processor CP7 1826
31-Way Processor CP7 1827
32-Way Processor CP7 1828
716 Capacity Marker 7263
717 Capacity Marker 7264
718 Capacity Marker 7265
719 Capacity Marker 7266
720 Capacity Marker 7267
721 Capacity Marker 7268
722 Capacity Marker 7269
723 Capacity Marker 7270
724 Capacity Marker 7271
725 Capacity Marker 7272
726 Capacity Marker 7273
727 Capacity Marker 7274
728 Capacity Marker 7275
729 Capacity Marker 7276
730 Capacity Marker 7277
731 Capacity Marker 7278
732 Capacity Marker 7279
IBM zEnterprise 196 2817 M49
M66
M80
1776 GB Memory 2467
2032 GB Memory 2469
2288 GB Memory 2471
33-Way Processor CP7 1829
34-Way Processor CP7 1830
35-Way Processor CP7 1831
36-Way Processor CP7 1832
37-Way Processor CP7 1833
38-Way Processor CP7 1834
39-Way Processor CP7 1835
40-Way Processor CP7 1836
41-Way Processor CP7 1837
42-Way Processor CP7 1838
43-Way Processor CP7 1839
44-Way Processor CP7 1840
45-Way Processor CP7 1841
46-Way Processor CP7 1842
47-Way Processor CP7 1843
48-Way Processor CP7 1844
49-Way Processor CP7 1845
733 Capacity Marker 7280
734 Capacity Marker 7281
735 Capacity Marker 7282
736 Capacity Marker 7283
737 Capacity Marker 7284
738 Capacity Marker 7285
739 Capacity Marker 7286
740 Capacity Marker 7287
741 Capacity Marker 7288
742 Capacity Marker 7289
743 Capacity Marker 7290
744 Capacity Marker 7291
745 Capacity Marker 7292
746 Capacity Marker 7293
747 Capacity Marker 7294
748 Capacity Marker 7295
749 Capacity Marker 7296
IBM zEnterprise 196 2817 M66
M80
2544 GB Memory 2473
2800 GB Memory 2475
3056 GB Memory 2477
50-Way Processor CP7 1846
51-Way Processor CP7 1847
52-Way Processor CP7 1848
53-Way Processor CP7 1849
54-Way Processor CP7 1850
55-Way Processor CP7 1851
56-Way Processor CP7 1852
57-Way Processor CP7 1853
58-Way Processor CP7 1854
59-Way Processor CP7 1855
60-Way Processor CP7 1856
61-Way Processor CP7 1857
62-Way Processor CP7 1858
63-Way Processor CP7 1859
64-Way Processor CP7 1860
65-Way Processor CP7 1861
66-Way Processor CP7 1862
750 Capacity Marker 7297
751 Capacity Marker 7298
752 Capacity Marker 7299
753 Capacity Marker 7300
754 Capacity Marker 7301
755 Capacity Marker 7302
756 Capacity Marker 7303
757 Capacity Marker 7304
758 Capacity Marker 7305
759 Capacity Marker 7306
760 Capacity Marker 7307
761 Capacity Marker 7308
762 Capacity Marker 7309
763 Capacity Marker 7310
764 Capacity Marker 7311
765 Capacity Marker 7312
766 Capacity Marker 7313
IBM zEnterprise 196 2817 M80
67-Way Processor CP7 1863
68-Way Processor CP7 1864
69-Way Processor CP7 1865
70-Way Processor CP7 1866
71-Way Processor CP7 1867
72-Way Processor CP7 1868
73-Way Processor CP7 1869
74-Way Processor CP7 1870
75-Way Processor CP7 1871
76-Way Processor CP7 1872
77-Way Processor CP7 1873
78-Way Processor CP7 1874
79-Way Processor CP7 1875
80-Way Processor CP7 1876
767 Capacity Marker 7314
768 Capacity Marker 7315
769 Capacity Marker 7316
770 Capacity Marker 7317
771 Capacity Marker 7318
772 Capacity Marker 7319
773 Capacity Marker 7320
774 Capacity Marker 7321
775 Capacity Marker 7322
776 Capacity Marker 7323
777 Capacity Marker 7324
778 Capacity Marker 7325
779 Capacity Marker 7326
780 Capacity Marker 7327
Note: (1) Ethernet switch (#0070) is not available in the following countries: Belize, Egypt, Haiti, Moldavia, Nicaragua, Oman, and Qatar. For alternatives, refer to the Ethernet LAN switch support section of Installation Manual - Physical Planning (IMPP), offering ID GC28-6897.
On IBM zEnterprise 196 we will continue to deliver a significant level of price performance and investment protection. We will allow carry forward of speciality engines and memory, with a charge to carry forward these assets. See your IBM sales representative for details.
The following features are not orderable on the IBM zEnterprise 196 models. If they are installed at the time of an upgrade to the z196 they may be retained.
Description Feature Code --------------------------------- ------------ HMC 0084 SE-EN Switch (former HUB) 0089 FICON Express4 10KM LX 3321 FICON Express4 SX 3322 FICON Express4 4KM LX 3324 OSA-Express2 GbE LX 3364 OSA-Express2 GbE SX 3365 OSA-Express2 1000BASET-EN 3366 17 inch panel display 6094 21 inch panel display 6095 6ft 250V Line Cord, Chi 8992 6ft 480V 30A Line Cord, Chi 8994
Note: 1. Memory DIMMs do NOT physically carry forward
Note: 2. Support Elements do NOT carry forward
Note: 3. FICON Express, f/c 2319 and 2320, are NOT supported on z196
Note: 4. FICON Express2, f/c 3319 and 3320, are NOT supported on z196
Note: 5. Crypto Express2, f/c 0863, is NOT supported on z196
Note: 6. OSA-Express2 10 GbE LR,f/c 3368, is NOT supported on z196
(#0019) Manage suite
(No Longer Available as of June 30, 2015)
This feature is used to enable the base set of tiered function associated with the IBM zEnterprise Unified Resource Manager. The Manage suite includes core operational controls, installation and configuration management, energy monitoring, hypervisor management, intranode management network (INMN) and intraensemble data network (IEDN) management, as well as virtual server lifecycle management. The Manage suite is included in the base zEnterprise System at no charge for CPs, IFLs, zIIPs, and zAAPs. There is a charge for blades and IBM Smart Analytics Optimizer. One of the two tiered suites of functionality for the Unified Resource Manager must be ordered. These suites are cumulative. Manage (#0019) is the base suite. If the next level suite, Automate (#0020), is ordered, Manage suite (#0019) is automatically included.
- Minimum: None or one if using IBM zEnterprise Unified Resource Manager.
- Maximum: One.
- Prerequisites: None.
- Corequisites: Either #0019 or #0020 must be ordered. If the Automate suite (#0020) is ordered, the Manague suite (#0019) is automatically included.
- Compatibility Conflicts: None known.
- Customer Setup: No.
- Limitations: None known.
- Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
(#0020) Automate suite
(No Longer Available as of June 30, 2015)
This feature is used to enable the Automate suite of functionality associated with the IBM zEnterprise Unified Resource Manager. The Automate suite includes representation of resources in a workload context, goal-oriented monitoring and management of resources, and energy management. The Automate suite is included in the base zEnterprise System at no charge for CPs, zIIPs, and zAAPs. There is a charge for IFLs, blades, and IBM Smart Analytics Optimizer. One of the two tiered suites of functionality for the Unified Resource Manager must be ordered. These suites are cumulative. Manage (#0019) is the base suite. If the next level suite, Automate (#0020), is ordered, Manage suite (#0019) is automatically included.
- Minimum: None or one if using IBM zEnterprise Unified Resource Manager.
- Maximum: One.
- Prerequisites: None.
- Corequisites: Either #0019 or #0020 must be ordered. If the Automate suite (#0020) is ordered, the Manague suite (#0019) is automatically included.
- Compatibility Conflicts: None known.
- Customer Setup: No.
- Limitations: None known.
- Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
(#0025) Ensemble membership
(No Longer Available as of June 30, 2014)
This feature ships the appropriate cabling for connectivity to the intranode management network (INMN).
Ensemble membership requires that the z196 have two OSA-Express3 1000BASE-T features defined as CHPID type OSM for connectivity to the intranode management network (INMN). Communication across the INMN is exclusively for the purpose of enabling the Unified Resource Manager of the Hardware Management Console (HMC) to perform its various management disciplines (such as performance management, network virtualization management, energy management, etc.)
- Minimum: None.
- Maximum: One.
- Prerequisites: None.
- Corequisites: Two OSA-Express3 1000BASE-T features (#3367) are required, for primary and backup connectivity. A port is defined as CHPID type OSM.
- 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: Two 3.2 meter (10.5 feet) Category 6 copper cables with RJ-45 connectors on each end are provided. Installation is performed by service personnel.
(#0030) Detach zBX
(No Longer Available as of June 30, 2015)
This feature code and the feature code 0031 are used to complete the detach of a zBX from a z114 or z196 and the attachment of that same zBX to another z114 or z196. This feature code is for the detachment of the zBX to a z114 or z196. The blade entitlements and ensemble management feature codes remain with the z196 and z114 from which the zBX is detached. The blade entitlements and ensemble management feature codes must be purchased for the z114 or z196 to which the zBX is to be attached unless that z114 or z196 currently has blade entitlements and ensemble management feature codes. To complete the detach and attach, one must have the serial numbers for each z114 or z196 participating in the detach and attach of the zBX. The zBX must be attached to the receiving z114 or z196 and it may not be parked or left not installed. The z114 or z196 to which the zBX is to be attached must have the same customer number and country code as the z114 or z196 from which the zBX is detached. Please review the prequisites and limitations.
- Minimum: 0
- Maximum: 1
- Prerequisites: DR93 with bundle 27 or higher for z196
- Corequisites: FC #0031 with Machine Type 2817 or Machine Type 2818 on the receiving machine
- Compatibility Conflicts: None :
- Customer Setup: No
- Limitations: The z114 or z196 to which the zBX is to be attached must have the same customer number and country code as the z114 or z196 from which the zBX is detached.
(#0031) Attach zBX:
This feature code and the feature code 0030 are used to complete the detach of a zBX from a z114 or z196 and the attachment of that same zBX to another z114 or z196. This feature code is for the attachment of the zBX to a z114 or z196. The blade entitlements and ensemble management feature codes remain with the z196 and z114 from which the zBX is detached. The blade entitlements and ensemble management feature codes must be purchased for the z114 or z196 to which the zBX is attached unless that z114 or z196 currently has blade entitlements and ensemble management feature codes. To complete the detach and attach, one must have the serial numbers for each z114 or z196 participating in the detach and attach of the zBX. The zBX must be attached to the receiving z114 or z196 it may not be parked or left not installed. The z114 or z196 from which the zBX is detached must have the same customer number and country code at the z114 or z196 to which the zBX is attached. Please review the prequisites and limitations.
- Minimum: 0
- Maximum: 1
- Prerequisites: DR93 with bundle 27 or higher for z196
- Corequisites: FC #0030 with Machine Type 2817 or Machine Type 2818 on the machine from which the zBX is detached
- Compatibility Conflicts: None
- Customer Setup: No
- Limitations: The z114 or z196 to which the zBX is to be attached must have the same customer number and country code as the z114 or z196 from which the zBX is attached.
(#0033) Service Docs Optional Print
(No Longer Available as of June 30, 2014)
Declining this feature will result in the following guides to not be shipped in paper format. The guides however continue to be available, and printable, from the documentation DVD that is shipped with every machine
- Service Guide
- Install Guide
- Safety inspection guide
Rules on useage:
- Do not de-select the hard copy document if this is the first machine at this location (Same address, same building and same floor)
- Allow de-selection of subsequent copies if multiple machines are ordered/shipped in the same timeframe.
- Do not de-select the hard copy document at this location if this is a "dark account" (raised floor that does not allow laptops and/or media inside)
Specifications:
- Minimum: 0.
- Maximum: 1
- Initial Order/MES/Both/Supported: Both
- Prerequisites: None
- Corequisites: None
- Compatibility Conflicts: None known
- Customer Setup: N/A
- Limitations: None known
- Field Installable: Yes
- Return parts MES: Does not apply
(#0040) Manage FW DP:
(No Longer Available as of June 30, 2015)
- Prerequisites: None.
- Corequisites: None
- Compatibility Conflicts: None known.
- Customer Setup: No.
- Limitations: None.
- Field Installable: Yes.
(#0044) Automate FW DP:
(No Longer Available as of June 30, 2015)
- Prerequisites: None.
- Corequisites:
- Compatibility Conflicts: None known.
- Customer Setup: No.
- Limitations: None.
- Field Installable: Yes.
(#0070) Ethernet switch
(No Longer Available as of June 30, 2014)
This description is for information purposes only. The 1GB switch is required to manage the Ethernet connections between the Hardware Management Consoles (HMCs) and the Support Elements (SEs).
- Minimum: None.
- Maximum: Ten (10). The configuration tool default is a quantity of one (1). The number can be decreased to a quantity of zero (0) if you already have an Ethernet hub or can be increased up to ten (10) if you require additional hubs.
- Prerequisites: None.
- Corequisites: None.
- Compatibility Conflicts: None known.
- Customer Setup: No.
- Limitations: Not available in the following countries: Belize, Egypt, Haiti, Moldavia, Nicaragua, Oman, and Qatar. For alternatives, refer to the Ethernet LAN switch support section of Installation Manual - Physical Planning (IMPP), offering ID GC28-6897.
- Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
- Cable Order: None. The appropriate cables are supplied with the Support Element.
(#0090) Hardware Management Console
(No Longer Available as of September 30, 2012)
The HMC is a workstation designed to provide a single point of control and single system image for managing local or remote hardware elements. Connectivity is supplied using an Ethernet Local Area Network (LAN) devoted exclusively to accessing the supported local and remote servers. The HMC is designed to support, exclusively, the HMC application. The HMC is supplied with two Ethernet ports capable of operating at 10, 100, or 1000 Mbps. It can act as a primary or alternate HMC.
- Minimum: None.
- Maximum: Ten (10).
- Prerequisites: None.
- Corequisites: None
- Compatibility Conflicts: None known.
- Customer Setup: No.
- Limitations: The HMC is for the exclusive use of the HMC application. Customer applications cannot reside on the HMC. TCP/IP is the only supported communication protocol. The HMC supports z196s. It can also be used to support z10 EC, z10 BC, z9 EC, z9 BC, z990, and z890 servers. They must be upgraded to a new AROM level.
- Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
- Cable Order: Cables are shipped with the HMC. The Ethernet cables are Category 5 Unshielded Twisted Pair (UTP) with an RJ-45 connector on each end.
(#0091) Hardware Management Console
(No Longer Available as of June 30, 2014)
The HMC is a workstation designed to provide a single point of control and single system image for managing local or remote hardware elements. Connectivity is supplied using an Ethernet Local Area Network (LAN) devoted exclusively to accessing the supported local and remote servers. The HMC is designed to support, exclusively, the HMC application. The HMC is supplied with two Ethernet ports capable of operating at 10, 100, or 1000 Mbps. It can act as a primary or alternate HMC.
- Minimum: In an ensemble, Two; otherwise None.
- Maximum: Ten (10).
- Prerequisites: None.
- Corequisites: None.
- Compatibility Conflicts: None known.
- Customer Setup: No.
- Limitations: The HMC is for the exclusive use of the HMC application. Customer applications cannot reside on the HMC. TCP/IP is the only supported communication protocol. The HMC supports z196s. It can also be used to support z10 EC, z10 BC, z9 EC, z9 BC, z990, and z890 servers. They must be upgraded to a new AROM level.
- Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
- Cable Order: Cables are shipped with the HMC. The Ethernet cables are Category 5 Unshielded Twisted Pair (UTP) with an RJ-45 connector on each end.
(#0116) 1 CPE Capacity Unit
(No Longer Available as of June 30, 2015)
Pricing feature code equal to the remainder of three days multiplied by the number of CPE Capacity Units divided by 100 purchased in a given Capacity for Planned Event record.
- Minimum: None.
- Maximum: 99
- Prerequisites: None.
- Corequisites: #6833
- Compatibility Conflicts: None known.
- Customer Setup: NA.
- Limitations: None.
- Field Installable: Yes.
(#0117) 100 CPE Capacity Unit
(No Longer Available as of June 30, 2015)
Pricing feature equal to the quotient of three days multiplied by the number of CPE Capacity Units purchased in a given pre-paid Capacity for Planned Event record divided by 100.
- Minimum: None.
- Maximum: 99
- Prerequisites: #0116
- Corequisites: #6833
- Compatibility Conflicts: None known.
- Customer Setup: NA.
- Limitations: None.
- Field Installable: Yes.
(#0118) 10000 CPE Capacity Unit
(No Longer Available as of June 30, 2015)
Pricing feature equal to the quotient of three days multiplied by the number of CPE Capacity Units purchased in a given pre-paid Capacity for Planned Event record divided by 10,000.
- Minimum: None.
- Maximum: 250
- Prerequisites: #0117
- Corequisites: #6833
- Compatibility Conflicts: None known.
- Customer Setup: NA.
- Limitations: None.
- Field Installable: Yes.
(#0119) 1 CPE Capacity Unit-IFL
(No Longer Available as of June 30, 2015)
Pricing feature equal to the remainder of the three days multiplied by the number of temporary Integrated Facility for Linux (IFL) features in a given Capacity for Planned event record divided by 100.
- Minimum: None.
- Maximum: 99
- Prerequisites: None.
- Corequisites: #6833
- Compatibility Conflicts: None known.
- Customer Setup: NA.
- Limitations: None.
- Field Installable: Yes.
(#0120) 100 CPE Capacity Unit-IFL
(No Longer Available as of June 30, 2015)
Pricing feature equal to the quotient of three days multiplied by the number of temporary Integrated Facility for Linux (IFL) features in a given Capacity for Planned event record divided by 100.
- Minimum: None.
- Maximum: 1
- Prerequisites: #0119
- Corequisites: #6833
- Compatibility Conflicts: None known.
- Customer Setup: NA.
- Limitations: None.
- Field Installable: Yes.
(#0121) 1 CPE Capacity Unit-ICF
(No Longer Available as of June 30, 2015)
Pricing feature equal to the remainder of the three days multiplied by the number of temporary Internal Coupling Facility (ICF) features in a given Capacity for Planned event record divided by 100.
- Minimum: None.
- Maximum: 99
- Prerequisites: None.
- Corequisites: #6833.
- Compatibility Conflicts: None known.
- Customer Setup: NA.
- Limitations: None.
- Field Installable: Yes.
(#0122) 100 CPE Capacity Unit-ICF
(No Longer Available as of June 30, 2015)
Pricing feature equal to the quotient of three days multiplied by the number of temporary Internal Coupling Facility (ICF) features in a given Capacity for Planned event record divided by 100.
- Minimum: None.
- Maximum: 1
- Prerequisites: #0121.
- Corequisites: #6833.
- Compatibility Conflicts: None known.
- Customer Setup: NA.
- Limitations: None.
- Field Installable: Yes.
(#0123) 1 CPE Capacity Unit-zAAP
(No Longer Available as of June 30, 2015)
Pricing feature equal to the remainder of the three days multiplied by the number of temporary System z Application Assist Processor (zAAP) features in a given Capacity for Planned event record divided by 100.
- Minimum: None.
- Maximum: 99
- Prerequisites: None.
- Corequisites: #6833
- Compatibility Conflicts: None known.
- Customer Setup: NA.
- Limitations: None.
- Field Installable: Yes.
(#0124) 100 CPE Capacity Unit-zAAP
(No Longer Available as of June 30, 2015)
Pricing feature equal to the quotient of three days multiplied by the number of temporary System z Application Assist Processor (zAAP) features in a given Capacity for Planned event record divided by 100.
- Minimum: None.
- Maximum: 1
- Prerequisites: #0123
- Corequisites: #6833
- Compatibility Conflicts: None known.
- Customer Setup: NA.
- Limitations: None.
- Field Installable: Yes.
(#0125) 1 CPE Capacity Unit-zIIP
(No Longer Available as of June 30, 2015)
Pricing feature equal to the remainder of the three days multiplied by the number of temporary System z Integrated Information Processor (zIIP) features in a given Capacity for Planned event record divided by 100.
- Minimum: None.
- Maximum: 99
- Prerequisites: None.
- Corequisites: #6833
- Compatibility Conflicts: None known.
- Customer Setup: NA.
- Limitations: None.
- Field Installable: Yes.
(#0126) 100 CPE Capacity Unit-zIIP
(No Longer Available as of June 30, 2015)
Pricing feature equal to the quotient of three days multiplied by the number of temporary System z Integrated Information Processor (zIIP) features in a given Capacity for Planned event record divided by 100.
- Minimum: None.
- Maximum: 1
- Prerequisites: #0125
- Corequisites: #6833
- Compatibility Conflicts: None known.
- Customer Setup: NA.
- Limitations: None.
- Field Installable: Yes.
(#0127) 1 CPE Capacity Unit-SAP
(No Longer Available as of June 30, 2015)
Pricing feature equal to the remainder of the three days multiplied by the number of temporary System Assist Processor (SAP) features in a given Capacity for Planned event record divided by 100.
- Minimum: None.
- Maximum: 99
- Prerequisites: None.
- Corequisites: #6833
- Compatibility Conflicts: None known.
- Customer Setup: NA.
- Limitations: None.
- Field Installable: Yes.
(#0128) 100 CPE Capacity Unit-SAP
(No Longer Available as of June 30, 2015)
Pricing feature equal to the quotient of three days multiplied by the number of temporary System Assist Processor (SAP) features in a given Capacity for Planned event record divided by 100.
- Minimum: None.
- Maximum: 1
- Prerequisites: #0127
- Corequisites: #6833
- Compatibility Conflicts: None known.
- Customer Setup: NA.
- Limitations: None.
- Field Installable: Yes.
Internal coupling link (IC)
This description is for information purposes only. ICs are not identified as a feature. The Internal coupling link (IC) is for internal communication between coupling facilities (CFs) defined in logical partitions (LPARs) and z/OS images on the same server. ICs do have a Channel Path Identifier (CHPID), which is type ICP, and are assigned using I/O control program (IOCP) or hardware configuration definition (HCD). There is no physical hardware. Care should be taken to ensure the planned use of ICs and external coupling links (active ISC-3 links, 12x InfiniBand, 1x InfiniBand) ordered does not exceed 128 CHPIDs and 80 physical links per server. ICs (CHPID type ICP) can be defined as a spanned channel and can be shared among LPARs within and across LCSSs.
- Minimum: None.
- Maximum: 32 ICs.
- Prerequisites: None.
- Corequisites: None.
- Compatibility Conflicts: Compatibility mode is not supported.
- Customer Setup: ICs must be defined in the IOCDS using either IOCP or HCD.
- Limitations: The maximum number of coupling link CHPIDs combined (ICs, 12x InfiniBand, 1x InfiniBand, and active ISC-3 links) cannot exceed 128 CHPIDs and 80 physical links per server.
- Field Installable: Yes.
- Cable Order: None. There are no external cables.
(#0163) HCA2-O fanout for 12x InfiniBand
(No Longer Available as of June 30, 2014)
12x InfiniBand coupling links utilize the Host Channel Adapter2 optical (HCA2-O) fanout. This fanout is designed to support single data rate (SDR) at 3 gigabytes per second (3 GBps) or double data rate (DDR) at 6 GBps. The speed is auto-negotiated and is determined by the capability of the attached System z server.
Note: A link data rate of 3 GBps (when attached to a System z9) or 6 GBps (when attached to a IBM zEnterprise 196 or System z10) does not represent the actual performance of the link.
The HCA2-O fanout has two ports/links and resides in the processor nest on the front of the book in the central processor complex (CPC) cage.
12x InfiniBand coupling links are designed to replace Integrated Cluster Bus 4 (ICB-4), which is not supported on z196, and to complement 1x InfiniBand and ISC-3.
12x InfiniBand can be used for Server Time Protocol (STP) message passing.
- Minimum: None. Order increment is two ports/links (one HCA2-O fanout).
- Maximum: Sixteen (16) features and 32 ports/links.
- Prerequisites: None.
- Corequisites: None.
- Compatibility Conflicts: None known.
- Customer Setup: No.
- Limitations:
- Maximum supported distance is 150 meters (492 feet). It cannot be repeated.
- Maximum number of physical coupling links combined cannot exceed 80 per machine (12x InfiniBand, 1x InfiniBand, and ISC-3).
- Maximum of 16 InfiniBand fanouts (#0163 HCA2-O fanout for 12x InfiniBand and #0168 HCA2-O LR fanout for 1x InfiniBand).
- Maximum of 128 coupling CHPIDs (ICP, CIB, CFP) per server.
- Each 12x InfiniBand fanout supports defining up to 16 CHPIDs spread across the two ports. No more than 8 CHPIDs spread across the two ports on a fanout is recommended.
- z196 & z10 negotiate to 3 GBps when connected to a z9
- Field Installable: Yes.
- Cable Order: A customer-supplied 12x IB-DDR cable is required. The cable is an OM3 50/125 micrometer multimode fiber optic cable with a fiber bandwidth @ wavelength: 2000 MHz-km @ 850 nm. It is a 24-fiber cable with duplex 12x multi-fiber push-on (MPO) connectors. There are 12 fibers for transmit and 12 fibers for receive.
Refer to System z Planning for Fiber Optic Links (ESCON, FICON, InfiniBand, Coupling Links, and Open System Adapters), GA23-0367, and to Installation Manual - Physical Planning (IMPP), GC28-6897, which can be found in the Library section of Resource Link at:
- www.ibm.com/servers/resourcelink
(#0168) HCA2-O LR fanout for 1x InfiniBand
(No Longer Available as of December 31, 2011)
1x InfiniBand coupling links utilize the Host Channel Adapter2 optical long reach (HCA2-O LR) fanout. This fanout is designed to support single data rate (SDR) at 2.5 gigabits per second (Gbps) or double data rate (DDR) at 5 Gbps.
Note: A link data rate of 2.5 Gbps or 5 Gbps does not represent the actual performance of the link. The speed is auto-negotiated and is determined by the capability of the attached Dense Wavelength Division Multiplexer (DWDM) to which it is attached. The DWDM vendor must be qualified by System z.
The HCA2-O LR fanout has two ports/links and resides in the processor nest on the front of the book in the central processor complex (CPC) cage.
1x InfiniBand coupling links complement 12x InfiniBand coupling links, are designed to satisfy extended distance requirements, and to facilitate a migration from ISC-3 coupling links to InfiniBand coupling links.
1x InfiniBand coupling links can be used for Server Time Protocol (STP) message passing.
- Minimum: None. Order increment is two ports/links (one HCA2-O LR fanout).
- Maximum: Sixteen (16) features and 32 ports/links.
- Prerequisites: None.
- Corequisites: None.
- 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 a System z-qualified optical networking solution.
- Maximum number of coupling links combined cannot exceed 80 per machine (12x InfiniBand, 1x InfiniBand, and ISC-3).
- Maximum of 16 InfiniBand fanouts (#0163 HCA2-O fanout for 12x InfiniBand and #0168 HCA2-O LR fanout for 1x InfiniBand).
- Maximum of 128 coupling CHPIDs (ICP, CIB, CFP) per server. Each InfiniBand link supports definition of multiple CIB CHPIDs, up to 16 per fanout. No more than 8 CHPIDs spread across the two ports on a fanout is recommended.
- 1x InfiniBand is supported on z196 and z10. It is not supported on z9.
- Field Installable: Yes.
- Cable Order: A customer-supplied cable is required. A 9/125 micrometer single mode fiber optic cable terminated with an LC Duplex connector is required (same connector used with ISC-3). Two cables are required, one for each of the two ports on the fanout.
Refer to System z Planning for Fiber Optic Links (ESCON, FICON, InfiniBand, Coupling Links, and Open System Adapters), GA23-0367, and to Installation Manual - Physical Planning (IMPP), GC28-6897, which can be found in the Library section of Resource Link at:
- www.ibm.com/servers/resourcelink
(#0170) HCA3-O LR fanout for 1x InfiniBand
(No Longer Available as of June 30, 2014)
1x InfiniBand coupling links utilize the Host Channel Adapter3 optical long reach (HCA3-O LR) fanout. This fanout is designed to support single data rate (SDR) at 2.5 gigabits per second (Gbps) or double data rate (DDR) at 5 Gbps.
Note: A link data rate of 2.5 Gbps or 5 Gbps does not represent the actual performance of the link. The speed is auto-negotiated and is determined by the capability of the attached Dense Wavelength Division Multiplexer (DWDM) to which it is attached. The DWDM vendor must be qualified by System z.
To access DWDM vendor qualification letters go to:
- http://www.ibm.com/servers/resourcelink/
- On the left, click on "Library"
- In the middle you will see "Hardware products for servers"
- Click on "System z Qualified Wavelength Division Multiplexer (WDM) products for GDPS solutions"
- Click on the vendor of your choice to view the qualification letters
The HCA3-O LR fanout has four ports/links and resides in the processor nest on the front of the book in the central processor complex (CPC). It is compatible with the HCA2-O LR fanout, which has two ports/links.
1x InfiniBand coupling links complement 12x InfiniBand coupling links, are designed to satisfy extended distance requirements, and to facilitate a migration from ISC-3 coupling links to InfiniBand coupling links.
1x InfiniBand coupling links can be used for Server Time Protocol (STP) message passing.
- Minimum: None. Order increment is four ports/links (one HCA3-O LR fanout).
- Maximum: 12. The maximum number of all HCA2 and HCA3 fanout features is limited to 16 per system.
- Prerequisites: None.
- Corequisites: STP enablement (#1021).
- Compatibility Conflicts: None known.
- Customer Setup: No.
- Limitations:
- An unrepeated distance of 10 km (6.2 miles) is supported. Greater distances are supported when attached to a System z-qualified optical networking solution.
- 1x InfiniBand is supported on z196, z114, and z10. It is not supported on z9.
- Field Installable: Yes.
- Cable Order: A customer-supplied cable is required. A 9/125 micrometer single mode fiber optic cable terminated with an LC Duplex connector is required (same connector used with ISC-3). Two cables are required, one for each of the two ports on the fanout.
Refer to System z Planning for Fiber Optic Links (ESCON, FICON, InfiniBand, Coupling Links, and Open System Adapters), GA23-0367, and to Installation Manual - Physical Planning (IMPP), GC28-6897, which can be found in the Library section of Resource Link at:
- www.ibm.com/servers/resourcelink
(#0171) HCA3-O fanout for 12x InfiniBand
(No Longer Available as of June 30, 2014)
12x InfiniBand coupling links utilize the Host Channel Adapter3 optical (HCA3-O) fanout. This fanout is designed to support a link data rate of 6 GBps and is designed to support improved throughput compared to HCA2-O fanout for 12x InfiniBand (#0163)
Note: A link data rate of of 6 GBps does not represent the actual performance of the link.
The HCA3-O fanout has two ports/links and resides in the processor nest on the front of the book in the central processor complex (CPC).
12x InfiniBand coupling links are designed to replace Integrated Cluster Bus 4 (ICB-4), which is not supported on z196, and to complement 1x InfiniBand and ISC-3.
12x InfiniBand can be used for Server Time Protocol (STP) message passing.
- Minimum: None. Order increment is two ports/links (one HCA3-O fanout).
- Maximum: 16. The maximum number of all HCA2 and HCA3 fanout features is limited to 16 per system.
- Prerequisites: None.
- Corequisites: STP enablement (#1021).
- Compatibility Conflicts: None known.
- Customer Setup: No.
- Limitations:
- Maximum supported distance is 150 meters (492 feet). It cannot be repeated.
- The HCA3-O fanout for 12x InfiniBand (#0171) is not supported when attaching a z196 or z114 to a z9.
- Field Installable: Yes.
- Cable Order: A customer-supplied 12x IB-DDR cable is required. The cable is an OM3 50/125 micrometer multimode fiber optic cable with a fiber bandwidth @ wavelength: 2000 MHz-km @ 850 nm. It is a 24-fiber cable with duplex 12x multi-fiber push-on (MPO) connectors. There are 12 fibers for transmit and 12 fibers for receive.
Refer to System z Planning for Fiber Optic Links (ESCON, FICON, InfiniBand, Coupling Links, and Open System Adapters), GA23-0367, and to Installation Manual - Physical Planning (IMPP), GC28-6897, which can be found in the Library section of Resource Link at:
- www.ibm.com/servers/resourcelink
(#0217, #0218) InterSystem Channel-3 (ISC-3)
(No Longer Available as of June 30, 2014)
(#0219) InterSystem Channel-3 (ISC-3)
(No Longer Available as of June 30, 2015)
The InterSystem Channel-3 (ISC-3) feature is a member of the family of coupling link options. An ISC-3 feature can have up to four links per feature. The ISC-3 feature is used by coupled servers to pass information back and forth over 2 Gigabits per second (Gbps) links in a Parallel Sysplex environment. The z196 ISC-3 feature is compatible with ISC-3 features on z10 EC, z10 BC, z9 EC, and z9 BC servers. While 12x InfiniBand is used for short distances between servers (up to 150 meters - 492 feet), ISC-3 (as well as 1x InfiniBand) supports an unrepeated distance of up to 10 kilometers (6.2 miles) between servers when operating at 2 Gbps. Extended distance for ISC-3 is available through RPQ. ISC-3 (CHPID type CFP - peer) can be defined as a spanned channel and can be shared among LPARs within and across LCSSs. ISC-3 complements 1x InfiniBand.
The ISC-3 feature is composed of a mother card (ISC-M #0217) and two daughter cards (ISC-D #0218). Each daughter card has two ports or links, for a total of four links per feature. Each link is activated using Licensed Internal Code Configuration Control (LICCC) with ISC links #0219. The ISC-D is not orderable. When the quantity of ISC links (#0219) is selected, the appropriate number of ISC-Ms and ISC-Ds is selected by the configuration tool. Additional ISC-Ms may be ordered up to the maximum of ISC-Ds required or twelve (12), whichever is the smaller number. The link is defined in peer (CHPID type CFP) mode only. Compatibility mode is not supported.
Each link utilizes a long wavelength (LX) laser as the optical transceiver, and supports use of a 9 micron single mode fiber optic cable terminated with an industry standard small form factor LC Duplex connector.
- Minimum: None. Links are ordered in increments of one. It is recommended that initial orders include two links.
- Maximum: 12 features, 48 links (4 links per feature).
- Prerequisites: None.
- Corequisites: STP enablement (#1021).
- Compatibility Conflicts: The ISC-3 feature has an optical transceiver that supports an LC Duplex connector only. A single mode fiber optic cable with an SC Duplex connector is not supported with this feature.
- Customer Setup: No.
- Limitations:
- Limitations: The maximum number of coupling link CHPIDs combined (ICs, 12x IinfiniBand, 1x InfiniBand, and active ISC-3 links) cannot exceed 128 CHPIDs and 80 physical links per server.
- The unrepeated distance between 2 Gbps ISC-3 links is limited to 10 kilometers (6.2 miles). If greater distances are desired, an RPQ request should be submitted.
- 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.
(#0404) OSA-Express4S Gigabit Ethernet LX
(No Longer Available as of June 30, 2014)
This feature resides exclusively in the PCIe I/O drawer (#4003, #4006). The OSA-Express4S Gigabit Ethernet (GbE) long wavelength (LX) feature has one PCIe adapter and two ports. The two ports share a channel path identifier (CHPID type OSD exclusively). 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: None.
- Maximum: 48 features in PCIe I/O drawer (#4003, #4006); any mix of OSA-Express4S features. Each OSA-Express3 or OSA-Express2 feature installed in an I/O cage/drawer reduces by two (2) the number of OSA-Express4S features allowed.
- Prerequisites: None.
- Corequisites: None.
- Compatibility Conflicts: The OSA-Express4S GbE LX feature supports use of an LC Duplex connector. Ensure the attaching or 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 (#4003, #4006).
- CHPID type OSN (OSA-Express for NCP) is not supported on OSA-Express4S.
- 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 each port on this feature to the selected device. If multimode fiber optic cables are being reused, a pair of Mode Conditioning Patch cables are required, one for each end of the link.
(#0405) OSA-Express4S Gigabit Ethernet SX
(No Longer Available as of June 30, 2014)
This feature resides exclusively in the PCIe I/O drawer (#4003, #4006). The OSA-Express4S Gigabit Ethernet (GbE) short wavelength (SX) feature has one PCIe adapter and two ports. The two ports share a channel path identifier (CHPID type OSD exclusively). 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: None.
- Maximum: 48 features in PCIe I/O drawer (#4003, #4006); any mix of OSA-Express4S features. Each OSA-Express3 or OSA-Express2 feature installed in an I/O cage/drawer reduces by two (2) the number of OSA-Express4S features allowed.
- Prerequisites: None.
- Corequisites: None.
- Compatibility Conflicts: The OSA-Express4S GbE SX feature supports use of an LC Duplex connector. Ensure the attaching or downstream device has a short wavelength (SX) transceiver. The sending and receiving transceivers must be the same (SX to SX).
- Customer Setup: No.
- Limitations:
- Can only be installed in PCIe I/O drawer (#4003, #4006).
- CHPID type OSN (OSA-Express for NCP) is not supported on OSA-Express4S.
- 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.
(#0406) OSA-Express4S 10 Gigabit Ethernet LR
(No Longer Available as of June 30, 2014)
This feature resides exclusively in the PCIe I/O drawer (#4003, #4006). The OSA-Express4S 10 Gigabit Ethernet (GbE) long reach (LR) feature has one PCIe adapter and one port per feature. The port supports channel path identifier (CHPID) types OSD and OSX. The 10 GbE feature is designed to support attachment to a single mode fiber 10 Gigabits per second (Gbps) Ethernet Local Area Network (LAN) or Ethernet switch capable of 10 Gbps. The port can be defined as a spanned channel and can be shared among logical partitions within and across logical channel subsystems.
- Minimum: None.
- Maximum: 48 features in PCIe I/O drawer (#4003, #4006); any mix of OSA-Express4S features. Each OSA-Express3 or OSA-Express2 feature installed in an I/O cage/drawer reduces by two (2) the number of OSA-Express4S features allowed.
- Prerequisites: None.
- Corequisites: None.
- Compatibility Conflicts: The OSA-Express4S 10 GbE LR feature supports use of an industry standard small form factor LC Duplex connector. Ensure the attaching or downstream device has a long reach (LR) transceiver. The sending and receiving transceivers must be the same (LR-to-LR which may also be referred to as LW or LX).
- Customer Setup: No.
- Limitations:
- Can only be installed in PCIe I/O drawer (#4003, #4006).
- When defined as CHPID type OSX, the 10 GbE port provides connectivity and access control to the intraensemble data network (IEDN) from z196 or z114 to zEnterprise BladeCenter Extension (zBX)
- Field Installable: Yes.
- Cable Order: A customer-supplied cable is required. A 9 micron single mode fiber optic cable terminated with an LC Duplex connector is required for connecting this feature to the selected device.
(#0407) OSA-Express4S 10 Gigabit Ethernet SR
(No Longer Available as of June 30, 2014)
This feature resides exclusively in the PCIe I/O drawer (#4003, #4006). The OSA-Express4S 10 Gigabit Ethernet (GbE) Short Reach (SR) feature has one PCIe adapter and one port per feature. The port supports channel path identifier (CHPID) types OSD and OSX. The 10 GbE feature is designed to support attachment to a multimode fiber 10 Gigabits per second (Gbps) Ethernet Local Area Network (LAN) or Ethernet switch capable of 10 Gbps. The port can be defined as a spanned channel and can be shared among logical partitions within and across logical channel subsystems.
- Minimum: None.
- Maximum: 48 features in PCIe I/O drawer (#4003, #4006); any mix of OSA-Express4S features. Each OSA-Express3 or OSA-Express2 feature installed in an I/O cage/drawer reduces by two (2) the number of OSA-Express4S features allowed.
- Prerequisites: None.
- Corequisites: None.
- Compatibility Conflicts: The OSA-Express4S 10 GbE SR feature supports use of an industry standard small form factor LC Duplex connector. Ensure the attaching or downstream device has a Short Reach (SR) transceiver. The sending and receiving transceivers must be the same (SR-to-SR).
- Customer Setup: No.
- Limitations:
- Can only be installed in PCIe I/O drawer (#4003, #4006).
- When defined as CHPID type OSX, the 10 GbE port provides connectivity and access control to the intraensemble data network (IEDN) from z196 or z114 to zEnterprise BladeCenter Extension (zBX)
- Field Installable: Yes.
- Cable Order: A customer-supplied cable is required. A 50 or a 62.5 micron multimode fiber optic cable terminated with an LC Duplex connector is required for connecting each port on this feature to the selected device.
(#0409) FICON Express8S 10KM LX
(No Longer Available as of June 30, 2014)
This feature resides exclusively in the PCIe I/O drawer (#4003, #4006). The FICON Express8S 10KM LX (long wavelength) feature conforms to the Fibre Connection (FICON) architecture, the High Performance FICON for System z (zHPF) architecture, and the Fibre Channel Protocol (FCP) architecture, 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 2 gigabits per second (Gbps), 4 Gbps, or 8 Gbps depending upon the capability of the attached switch or device. The link speed is autonegotiated, point-to-point, and is transparent to users and applications. Each of the channels utilizes a small form factor pluggable (SFP) optic and is designed to be individually repaired without affecting the other channels.
FICON Express8S 10KM 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 Express8S 10KM 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 Express8S 10KM LX channel can be defined independently, for connectivity to servers, switches, directors, disks, tapes, and printers as:
- CHPID type FC - FICON, High Performance FICON for System z (zHPF), and FICON Channel-to-Channel (CTC). FICON, FICON CTC, and zHPF protocols are supported simultaneously.
- CHPID type FCP - Fibre Channel Protocol which supports attachment to SCSI devices directly or through Fibre Channel switches or directors.
The FICON Express8S 10KM LX feature utilizes a long wavelength (LX) laser as the optical transceiver and supports use of a 9/125 micrometer single mode fiber optic cable terminated with an LC Duplex connector. LX may also be referred to as LW by vendors.
- Minimum: None. At least one I/O feature (ESCON or FICON) or coupling link feature (12x InfiniBand, 1x InfiniBand, or ISC-3) must be present in a server.
- Maximum: 160 features (320 channels) in PCIe I/O drawer (#4003, #4006).
- Prerequisites: None.
- Corequisites: None.
- Compatibility Conflicts: None known. 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 (#4003, #4006).
- The FICON Express8S 10KM LX feature does not support FICON Bridge (CHPID type FCV).
- The FICON Express8S 10KM LX feature does not support autonegotiation to 1 Gbps.
- The FICON Express8S 10 KM LX feature is designed to support distances up to 10 kilometers (6.2 miles) over 9 micron single mode fiber optic cabling without performance degradation. To avoid performance degradation at extended distance, FICON switches or directors (for buffer credit provision) or Dense Wavelength Division Multiplexers (for buffer credit simulation) may be required.
- Field Installable: Yes.
- Cable Order: A customer-supplied cable is required. A 9 micron single mode fiber optic cable terminated with an LC Duplex connector is required for connecting this feature to the selected device.
(#0410) FICON Express8S SX
(No Longer Available as of June 30, 2014)
This feature resides exclusively in the PCIe I/O drawer (#4003, #4006). The FICON Express8S SX (short wavelength) feature conforms to the Fibre Connection (FICON) architecture, the High Performance FICON for System z (zHPF) architecture, and the Fibre Channel Protocol (FCP) architecture, 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 2 gigabits per second (Gbps), 4 Gbps, or 8 Gbps depending upon the capability of the attached switch or device. The link speed is autonegotiated, point-to-point, and is transparent to users and applications. Each of the channels utilizes a small form factor pluggable (SFP) optic and is designed to be individually repaired without affecting the other channels. FICON Express8S 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 Express8S 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 Express8S SX channel can be defined independently for connectivity to servers, switches, directors, disks, tapes, and printers as:
- CHPID type FC - FICON, High Performance FICON for System z (zHPF), and FICON Channel-to-Channel (CTC). FICON, FICON CTC, and zHPF protocols are supported simultaneously.
- CHPID type FCP - Fibre Channel Protocol which supports attachment to SCSI devices directly or through Fibre Channel switches or directors.
The FICON Express8S SX feature utilizes a short wavelength (SX) laser as the optical transceiver, and supports use of a 50/125 micrometer multimode fiber optic cable or a 62.5/125-micrometer 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 (ESCON or FICON) or coupling link feature (12x InfiniBand, 1x InfiniBand, or ISC-3) must be present in a server.
- Maximum: 160 features (320 channels) in PCIe I/O drawer (#4003, #4006).
- Prerequisites: None.
- Corequisites: None.
- Compatibility Conflicts: None known. 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 (#4003, #4006).
- The FICON Express8S SX feature does not support FICON Bridge (CHPID type FCV).
- The FICON Express8S SX feature does not support autonegotiation to 1 Gbps.
- FICON Express8S LX is designed to support distances up to 10 kilometers (6.2 miles) without performance degradation. To avoid performance degradation at extended distance, FICON switches or directors (for buffer credit provision) or Dense Wavelength Division Multiplexers (for buffer credit simulation) may be required.
- For unrepeated distances for FICON Express8S SX refer to System
z Planning for Fiber Optic Links (GA23-0367) available in the
Library section of Resource Link.
www.ibm.com/servers/resourcelink
- Field Installable: Yes.
- Cable Order: A customer-supplied cable is required. A 50 or a 62.5 micron multimode fiber optic cable terminated with an LC Duplex connector is required for connecting each port on this feature to the selected device.
(#0841) TKE workstation
(No Longer Available as of June 30, 2014)
This is an optional feature. The Trusted Key Entry (TKE) workstation is a combination of hardware and software, network-connected to the server, and designed to provide a security-rich, flexible method for master and operational key entry as well as local and remote management of the cryptographic coprocessor features (Crypto Express3 when defined as a coprocessor - the default configuration). This optional feature provides basic key management -- key identification, exchange, separation, update, backup, as well as security administration. The TKE workstation has one Ethernet port and supports connectivity to an Ethernet Local Area Network (LAN) operating at 10, 100, or 1000 Mbps.
If Trusted Key Entry is required on a z196, then a TKE workstation with TKE 7.0 LIC (#0860) must be used. TKE workstations with TKE 7.0 LIC can also be used to control z10 EC, z10 BC, z9 EC, z9 BC, z990, and z890 servers.
- Minimum: None.
- Maximum: Ten (10).
- Prerequisites: CP Assist for Cryptographic Function (#3863) and Crypto Express3 (#0864).
- Corequisite: TKE 7.0 LIC (#0860) loaded on TKE workstation prior to shipment.
- Compatibility Conflicts: None known.
- Customer Setup: No.
- Limitations: Crypto Express2 (#0863) is not supported on z196.
- Field Installable: Yes. Parts removed as a result of feature change become the property of IBM.
- Cable Order: LAN cabling is a customer responsibility. A Category 5 Unshielded Twisted Pair (UTP) cable terminated with RJ-45 connector is required.
(#0860) TKE 7.0 LIC
(No Longer Available as of September 20, 2013)
The Trusted Key Entry (TKE) 7.0 level of Licensed Internal Code (LIC) is installed in a TKE workstation (#0841). TKE 7.0 LIC is a no-charge enablement feature which is loaded prior to shipment when a TKE workstation is ordered. The TKE 7.0 LIC includes support for the Smart Card Reader (#0885)
- Minimum: None.
- Maximum: Ten (10).
- Prerequisites: TKE workstation (#0841).
- Corequisites: CPACF (#3863), Crypto Express3 (#0864).
- Compatibility Conflicts: None known.
- Customer Setup: No.
- Limitations: None.
- Field Installable: Yes. Parts removed as a result of feature change become the property of IBM.
(#0864) Crypto Express3
(No Longer Available as of June 30, 2014)
The Crypto Express3 feature is designed to satisfy high-end server security requirements. It contains two PCIe adapters which are configured independently, either as a coprocessor supporting secure key transactions or as an accelerator for Secure Sockets Layer (SSL) acceleration.
The tamper-resistant hardware security module, which is contained on the Crypto Express3 feature, is designed to conform to the Federal Information Processing Standard (FIPS) 140-2 Level 4 Certification, and supports User Defined Extension (UDX) services to implement cryptographic functions and algorithms (when defined as a coprocessor).
- Minimum: None or two. An initial order is two features.
- Maximum: 8 features (16 PCIe adapters, two PCIe adapters per feature).
- Prerequisites: CP Assist for Cryptographic Function (CPACF) (#3863).
- Corequisites: TKE workstation (#0839, #0840, #0841) if you require security-rich, flexible key entry or remote key management if not using Integrated Cryptographic Service Facility (ICSF) panels.
- Compatibility Conflicts: None known.
- Customer Setup: No.
- Limitations: None.
- Field Installable: Yes. Parts removed as a result of feature change become the property of IBM.
- Cable Order: None.
(#0867) TKE 7.1 LIC
(No Longer Available as of September 20, 2013)
The Trusted Key Entry (TKE) 7.1 level of Licensed Internal Code (LIC) is installed in a TKE workstation (#0841). TKE 7.1 LIC is a no-charge enablement feature which is loaded prior to shipment when a TKE workstation is ordered. The TKE 7.1 LIC includes support for the Smart Card Reader (#0885)
- Minimum: None.
- Maximum: Ten (10).
- Prerequisites: TKE workstation (#0841).
- Prerequisites: CP Assist for Cryptographic Function (#3863); Crypto Express3 (#0864).
- Compatibility Conflicts: TKE workstations with TKE 7.1 LIC can be used to control z196, z114, z10 EC, and z10 BC servers.
- Customer Setup: No.
- Limitations: None.
- Field Installable: Yes. Parts removed as a result of feature change become the property of IBM.
(#0884) TKE additional smart cards
(No Longer Available as of June 30, 2014)
These are Java-based smart cards which provide a highly efficient cryptographic and data management application built-in to read-only memory for storage of keys, certificates, passwords, applications, and data. The TKE blank smart cards are compliant with FIPS 140-2 Level 2.
- Minimum: None. Order increment is one. When one is ordered a quantity of 10 smart cards are shipped.
- Maximum: 99 (990 blank Smart Cards).
- Prerequisites: CP Assist for Cryptographic Function (#3863), Crypto Express3 (#0864).
- Corequisites: TKE workstation (#0841) with 7.0 level of LIC (#0860) for secure key parts entry and cryptographic hardware management or ISPF panels for clear key entry and cryptographic hardware management, and TKE Smart Card Reader (#0885).
- Compatibility Conflicts: None known.
- Customer Setup: No.
- Limitations: None
- Field Installable: Yes.
- Cable Order: Not applicable.
(#0885) TKE Smart Card Reader
(No Longer Available as of June 30, 2014)
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).
The TKE 7.0 level of LIC continues to allow the storing of key parts on diskettes or paper, or optionally on smart cards, or to use a TKE authority key stored on a diskette, or optionally on a smart card, and to log on to the Cryptographic Coprocessor using a passphrase, or optionally a logon key pair. One (1) feature includes two Smart Card Readers, two cables to connect to the TKE 7.0 workstation, and 20 smart cards.
- Minimum: None.
- Maximum: Ten (10).
- Prerequisites: CP Assist for Cryptographic Function (#3863), Crypto Express3 (#0864).
- Corequisites: TKE workstation (#0841) with 7.0 level of LIC (#0860) for secure key parts entry and Crypto hardware management or ISPF panels for clear key entry and Crypto hardware management.
- 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.
(#1021) STP enablement
(No Longer Available as of June 30, 2015)
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 System z servers or you require the same time across heterogeneous platforms (System z, Unix, AIX, etc) you can meet these requirements by implementing Server Time Protocol (STP).
Server Time Protocol is a server-wide facility that is implemented in the Licensed Internal Code (LIC) and presents a single view of time to Processor Resource/Systems Manager (PR/SM). STP uses a message-based protocol in which timekeeping information is passed over coupling links. InterSystem Channel-3 (ISC-3), 12x InfiniBand, or 1x InfiniBand can be used for STP message exchanges.
(#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 such as Customer Initiated Upgrade (CIU). There are no parts. The flag is generated by the system and not orderable.
(#1877) Central Processor 4 (CP4)
(No Longer Available as of June 30, 2015)
Processor Unit (PU) characterization option. The CP4 is the Processor Unit purchased and activated supporting the z/OS, z/VM, and z/VSE operating systems.
- Minimum number of features: None.
- Maximum number of features: 15.
- Prerequisites: None.
- Corequisites: None.
- Compatibility Conflicts: Cannot coexist with #1878, #1879, or #1880
- Field Installable: Yes.
(#1878) Central Processor 5 (CP5)
(No Longer Available as of June 30, 2015)
Processor Unit (PU) characterization option. The CP5 is the Processor Unit purchased and activated supporting the z/OS, z/VM, and z/VSE operating systems.
- Minimum number of features: None.
- Maximum number of features: 15.
- Prerequisites: None.
- Corequisites: None.
- Compatibility Conflicts: Cannot coexist with #1877, #1879, or #1880.
- Field Installable: Yes.
(#1879) Central Processor 6 (CP6)
(No Longer Available as of June 30, 2015)
Processor Unit (PU) characterization option. The CP6 is the Processor Unit purchased and activated supporting the z/OS, z/VM, and z/VSE operating systems.
- Minimum number of features: None.
- Maximum number of features: 15.
- Prerequisites: None.
- Corequisites: None.
- Compatibility Conflicts: Cannot coexist with #1877, #1878, or #1880.
- Field Installable: Yes.
(#1880) Central Processor 7 (CP7)
(No Longer Available as of June 30, 2015)
Processor Unit (PU) characterization option. The CP7 is the Processor Unit purchased and activated supporting the z/OS, z/VM, and z/VSE operating systems.
- Minimum number of features: None.
- Maximum number of features: 80.
- Prerequisites: None.
- Corequisites: None.
- Compatibility Conflicts: Cannot coexist with #1877, #1878, or #1879.
- Field Installable: Yes.
(#1881) Integrated Facility for Linux (IFL)
(No Longer Available as of June 30, 2015)
Processor Unit (PU) characterization option. The IFL is a Processor Unit that is purchased and activated for exclusive use of Linux on z196.
- Minimum number of features: None.
- Maximum number of features: 80.
- Prerequisites: None.
- Corequisites: None.
- Compatibility Conflicts: None known.
- Field Installable: Yes.
(#1882) Internal Coupling Facility (ICF)
(No Longer Available as of June 30, 2015)
Processor Unit (PU) characterization option. The ICF is a Processor Unit purchased and activated for exclusive use by the Coupling Facility Control Code (CFCC).
- Minimum number of features: None.
- Maximum number of features: 16.
- Prerequisites: None.
- Corequisites: None.
- Compatibility Conflicts: None known.
- Field Installable: Yes.
(#1883) System Assist Processor (SAP), optional
(No Longer Available as of June 30, 2015)
Processor Unit (PU) characterization option. 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 number of features: None.
- Maximum number of features: 20.
- Prerequisites: One CP4 (#1877), CP5 (#1878), CP6 (#1879), CP7 (#1880), IFL (#1881), or ICF (#1882).
- Corequisites: None.
- Compatibility Conflicts: None known.
- Field Installable: Yes.
(#1884) System z Application Assist Processor (zAAP)
(No Longer Available as of June 30, 2015)
Processor Unit (PU) characterization option. The zAAP is a specialized Processor Unit that provides a Java execution environment for a z/OS environment.
- Minimum number of features: None.
- Maximum number of features: 40.
- Prerequisites: For each zAAP installed there must be a corresponding CP permanently purchased and installed.
- Corequisites: None.
- Compatibility Conflicts: None known.
- Customer Setup: No.
- Limitations: None known.
- Field Installable: Yes.
(#1885) System z Integrated Information Processor (zIIP)
(No Longer Available as of June 30, 2015)
Processor Unit (PU) characterization option. The zIIP is a subcapacity Processor Unit purchased and activated to accept eligible work from z/OS.
- Minimum number of features: None.
- Maximum number of features: 40.
- Prerequisites: For each zIIP installed there must be a corresponding CP permanently purchased and installed.
- Corequisites: None.
- Compatibility Conflicts: None known.
- Customer Setup: No.
- Limitations: None known.
- Field Installable: Yes.
(#1886) Unassigned Integrated Facility for Linux (IFL)
(No Longer Available as of June 30, 2015)
Processor Unit characterization option. An unassigned IFL is a Processor Unit purchased for future use as an IFL (#1881). It is offline and unavailable for use.
- Minimum number of features: None.
- Maximum number of features: 79.
- Prerequisites: None.
- Corequisites: None.
- Compatibility Conflicts: None known.
- Field Installable: Yes.
(#1901) 16GB Memory Capacity Increment
(No Longer Available as of June 30, 2015)
Incremental memory feature that provides a count of each 16GB of memory being added to active memory or the activation of Preplanned memory. When preplanned memory is being activated one feature #1901 is added for each feature #1996 activated. Features must result in valid memory offering size.
- Minimum number of features: None.
- Maximum number of features: 189.
- Prerequisites: Preplanned memory (#1996)
- Corequisites: None.
- Compatibility Conflicts: None known.
- Customer Setup: Not applicable.
- Limitations: None.
- Field Installable: Yes.
(#1902) 16GB FTR Converted Memory
(No Longer Available as of June 30, 2015)
Pricing feature issued on upgrades from z9 or z10 for capacity above the first 64GB of memory carried forward.
- Minimum: None.
- Maximum: 95.
- Prerequisites: None.
- Corequisites: None.
- Compatibility Conflicts: None known.
- Customer Setup: No.
- Limitations: None.
- Field Installable: Yes.
(#1996) Preplanned memory
(No Longer Available as of June 30, 2015)
Preplanned memory features are used to build the physical infrastructure for Flexible memory or Plan Ahead memory. Each feature equates to 16 GB of physical memory.
- Minimum number of features: None.
- Maximum number of features: 191.
- Prerequisites: None.
- Corequisites: None.
- Compatibility Conflicts: Can't exist on any z196 model configured with the maximum memory for that model.
- Customer Setup: Not applicable.
- Limitations: None.
- Field Installable: Yes.
(#2000) Line cord plan ahead
(No Longer Available as of June 30, 2014)
This option provides the ability to plan ahead for the second set of line cords. Must be same feature selection as initial set. The Plan Ahead function provides the means of ordering now, the hardware that will be required in the future to help avoid a disruptive hardware install in the future.
- Minimum: None
- Maximum: One.
- Prerequisites: None
- Corequisites: None
- Compatibility Conflicts: Line cords must be same feature selection as initial set.
- Customer Setup: No.
- Limitations: None known.
- Field Installable: No.
(#2323) 16-port ESCON
(No Longer Available as of June 30, 2014)
The Enterprise Systems Connection (ESCON) channel supports the ESCON architecture and provides the capability to directly attach to ESCON-supported Input/Output (I/O) devices (storage, disk, printers, control units) in a switched point-to-point topology at unrepeated distances of up to 3 kilometers (1.86 miles) at a link data rate of 17 MegaBytes (MB) per second. The ESCON channel utilizes 62.5 micron multimode fiber optic cabling terminated with an MT-RJ connector. The high density ESCON feature has 16 ports or channels, 15 of which can be activated for customer use. One channel is always reserved as a spare, in the event of a failure of one of the other channels.
Feature 2323 cannot be ordered. The configuration tool selects the quantity of features based upon the order quantity of ESCON channel (#2324), distributing the channels across features for high availability. After the first pair, ESCON features are installed in increments of one.
- Minimum: None. At least one I/O feature (ESCON or FICON) or coupling link feature (12x InfiniBand, 1x InfiniBand, or ISC-3) must be present in a server.
- Maximum: 16 features. A maximum of 240 active channels, 15 channels per feature.
- Prerequisites: None.
- Corequisites: ESCON channel (#2324).
- Compatibility Conflicts: None known.
- Customer Setup: No.
- Limitations: The unrepeated distance between ESCON channels is limited to 3 kilometers (1.86 miles) using 62.5 micron multimode fiber optic cables. If greater distances are desired, an RPQ request should be submitted.
- Field Installable: Yes.
- Cable Order: A customer-supplied cable is required. A 62.5 micron multimode fiber optic cable terminated with an MT-RJ connector is required.
(#2324) ESCON channel port
(No Longer Available as of June 30, 2015)
ESCON channels are available on a channel (port) basis in increments of four. The channel quantity is selected and Licensed Internal Code Configuration Control (LICCC) is shipped to activate the desired quantity of channels on the 16-port ESCON feature (#2323) not to exceed 15 per feature. One is always available as a spare. Each channel utilizes a Light Emitting Diode (LED) as the optical transceiver, and supports use of a 62.5 micron multimode fiber optic cable terminated with a small form factor, industry-standard MT-RJ connector.
- Minimum: None. At least one I/O feature (ESCON or FICON) or coupling link feature (12x InfiniBand, 1x InfiniBand, or ISC-3) must be present in a server.
- Maximum: 240 channels.
- Prerequisites: None.
- Corequisites: None.
- Compatibility Conflicts: The 16-port ESCON feature has a small form factor optical transceiver that supports an MT-RJ connector only. A multimode fiber optic cable with an ESCON Duplex connector is not supported with this feature.
- Customer Setup: No.
- Limitations: The unrepeated distance between ESCON channels is limited to 3 kilometers (1.86 miles) using 62.5 micron multimode fiber optic cables. If greater distances are desired, an RPQ request should be submitted.
- Field Installable: Yes.
- Cable Order: A customer-supplied cable is required. A 62.5 micron multimode fiber optic cable terminated with an MT-RJ connector is required.
(#3003) Balanced Power Plan Ahead
(No Longer Available as of June 30, 2014)
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: None.
- Maximum: One.
- Prerequisites: None.
- Corequisites: May require additional internal battery features (#3212) and line cords. Configuration tool will determine.
- Compatibility Conflicts: None known.
- Customer Setup: No.
- Limitations: None known.
- Field Installable: Yes. It is disruptive.
- Cable Order: None.
(#3212) Internal Battery (IBF)
(No Longer Available as of June 30, 2014)
The IBF is the internal battery backup feature offered on a z196. When selected, the actual number of IBFs is determined based on the power requirements and model. The batteries are installed in pairs.
- Minimum number of features: None.
- Maximum number of features: Six. (installed in pairs).
- Prerequisites: None.
- Corequisites: None.
- Compatibility Conflicts: None known.
(#3325) FICON Express8 10KM LX
(No Longer Available as of June 30, 2014)
The FICON Express8 10KM LX (long wavelength) feature conforms to the Fibre connection (FICON) architecture, the High Performance FICON for System z (zHPF) architecture, and the Fibre Channel Protocol (FCP) architecture, 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 four independent ports/channels is capable of 2 gigabits per second (Gbps), 4 Gbps, or 8 Gbps depending upon the capability of the attached switch or device. The link speed is autonegotiated, point-to-point, and is transparent to users and applications. Each of the channels utilizes a small form factor pluggable (SFP) optic and is designed to be individually repaired without affecting the other channels.
FICON Express8 10KM LX (CHPID type FC or FCP) can be defined as a spanned channel and can be shared among LPARs within and across LCSSs.
The FICON Express8 10KM 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 Express8 10KM LX channel can be defined independently, for connectivity to servers, switches, directors, disks, tapes, and printers as:
- Native FICON, High Performance FICON for System z (zHPF), and FICON Channel-to-Channel (CTC) - (CHPID type FC); native FICON and zHPF protocols are supported simultaneously.
- Fibre Channel Protocol (CHPID type FCP), which supports attachment to SCSI devices directly or through Fibre channel switches or directors.
The FICON Express8 10KM LX feature utilizes a long wavelength (LX) laser as the optical transceiver and supports use of a 9/125 micrometer single mode fiber optic cable terminated with an LC Duplex connector. LX may also be referred to as LW by vendors.
- Minimum: None. At least one I/O feature (ESCON or FICON) or coupling link feature (12x InfiniBand, 1x InfiniBand, or ISC-3) must be present in a server.
- Maximum: 72 features; can be any combination of FICON Express8 and FICON Express4 features.
- Prerequisites: None.
- Corequisites: None.
- Compatibility Conflicts: None known. 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:
- The FICON Express8 10KM LX feature does not support FICON Bridge (CHPID type FCV).
- The FICON Express8 10KM LX feature does not support autonegotiation to 1 Gbps.
- The FICON Express8 10 KM LX feature is designed to support distances up to 10 kilometers (6.2 miles) over 9 micron single mode fiber optic cabling without performance degradation. To avoid performance degradation at extended distance, FICON switches or directors (for buffer credit provision) or Dense Wavelength Division Multiplexers (for buffer credit simulation) may be required.
- Field Installable: Yes.
- Cable Order: A customer-supplied cable is required. A 9/125 micrometer single mode fiber optic cable terminated with an LC Duplex connector is required for connecting this feature to the selected device.
(#3326) FICON Express8 SX
(No Longer Available as of June 30, 2014)
The FICON Express8 SX (short wavelength) feature conforms to the Fibre connection (FICON) architecture, the High Performance FICON for System z (zHPF) architecture, and the Fibre Channel Protocol (FCP) architecture, 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 four independent ports/channels is capable of 2 gigabits per second (Gbps), 4 Gbps, or 8 Gbps depending upon the capability of the attached switch or device. The link speed is autonegotiated, point-to-point, and is transparent to users and applications. Each of the channels utilizes a small form factor pluggable (SFP) optic and is designed to be individually repaired without affecting the other channels. FICON Express8 SX (CHPID type FC or FCP) can be defined as a spanned channel and can be shared among LPARs within and across LCSSs.
The FICON Express8 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 Express8 SX channel, can be defined independently for connectivity to servers, switches, directors, disks, tapes, and printers as:
- Native FICON, High Performance FICON for System z (zHPF), and FICON Channel-to-Channel (CTC) - (CHPID type FC); native FICON and zHPF protocols are supported simultaneously.
- Fibre Channel Protocol (CHPID type FCP), which supports attachment to SCSI devices directly or through Fibre Channel switches or directors
The FICON Express8 SX feature utilizes a short wavelength (SX) laser as the optical transceiver, and supports use of a 50/125 micrometer multimode fiber optic cable or a 62.5/125-micrometer 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 (ESCON or FICON) or coupling link feature (12x InfiniBand, 1x InfiniBand, or ISC-3) must be present in a server.
- Maximum: 72 features; can be any combination of FICON Express8 and FICON Express4 features.
- Prerequisites: None.
- Corequisites: None.
- Compatibility Conflicts: None known. 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:
- The FICON Express8 SX feature does not support FICON Bridge (CHPID type FCV).
- The FICON Express8 SX feature does not support autonegotiation to 1 Gbps.
- FICON Express8 is designed to support distances up to 10 kilometers (6.2 miles) without performance degradation. To avoid performance degradation at extended distance, FICON switches or directors (for buffer credit provision) or Dense Wavelength Division Multiplexers (for buffer credit simulation) may be required.
- For unrepeated distances for FICON Express8 SX refer to System z
Planning for Fiber Optic Links (GA23-0367) available in the
Library section of Resource Link.
www.ibm.com/servers/resourcelink
- Field Installable: Yes.
- Cable Order: A customer-supplied cable is required. A 50/125 micrometer multimode fiber optic cable, or a 62.5/125 micrometer multimode fiber optic cable terminated with an LC Duplex connector is required for connecting this feature to the selected device.
(#3362) OSA-Express3 Gigabit Ethernet LX
(No Longer Available as of June 30, 2014)
The OSA-Express3 Gigabit Ethernet (GbE) long wavelength (LX) feature has two PCIe adapters and four independent ports. Two ports reside on a PCIe adapter and share a channel path identifier (CHPID). Each port supports attachment to a one Gigabit per second (Gbps) Ethernet Local Area Network (LAN). OSA-Express3 GbE LX supports CHPID types OSD and OSN. It can be defined as a spanned channel and can be shared among LPARs within and across LCSSs.
- Minimum: None.
- Maximum: 24 features. The maximum quantity of all OSA-Express3 and OSA-Express2 features cannot exceed 24 features per server.
- Maximum ports: 96 ports.
- Prerequisites: None.
- Corequisites: None.
- Compatibility Conflicts: The OSA-Express3 GbE LX feature supports use of an LC Duplex connector. Ensure the attaching or downstream device has a long wavelength (LX) transceiver. The sending and receiving transceivers must be the same (LX to LX).
- Customer Setup: No.
- Limitations: None known.
- 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 each port on this feature to the selected device. If multimode fiber optic cables are being reused, a pair of Mode Conditioning Patch cables are required, one for each end of the link.
(#3363) OSA-Express3 GbE SX
(No Longer Available as of June 30, 2014)
The OSA-Express3 Gigabit Ethernet (GbE) short wavelength (SX) feature has two PCIe adapters and four independent ports. Two ports reside on a PCIe adapter and share a channel path identifier (CHPID). Each port supports attachment to a one Gigabit per second (Gbps) Ethernet Local Area Network (LAN). OSA-Express3 GbE SX supports CHPID types OSD and OSN. It can be defined as a spanned channel and can be shared among LPARs within and across LCSSs.
- Minimum: None.
- Maximum: 24 features. The maximum quantity of all OSA-Express3 and OSA-Express2 features cannot exceed 24 features per server.
- Maximum ports: 96 ports.
- Prerequisites: None.
- Corequisites: None.
- Compatibility Conflicts: The OSA-Express3 GbE SX feature supports use of an LC Duplex connector. Ensure the attaching or downstream device has a short wavelength (SX) transceiver. The sending and receiving transceivers must be the same (SX to SX).
- Customer Setup: No.
- Limitations: None known.
- 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.
(#3367) OSA-Express3 1000BASE-T Ethernet
(No Longer Available as of June 30, 2014)
The OSA-Express3 1000BASE-T Ethernet feature has two PCIe adapters and four independent ports. Two ports reside on a PCIe adapter and share a channel path identifier (CHPID). Each port supports attachment to either a 10BASE-T (10 Mbps), 100BASE-TX (100 Mbps), or 1000BASE-T (1000 Mbps or 1 Gbps) Ethernet Local Area Network (LAN). The feature supports autonegotiation and automatically adjusts to 10, 100, or 1000 Mbps, depending upon the LAN. When the feature is set to autonegotiate, the target device must also be set to autonegotiate. The feature supports the following settings: 10 Mbps half or full duplex, 100 Mbps half or full duplex, 1000 Mbps (1 Gbps) full duplex. OSA-Express3 1000BASE-T Ethernet supports CHPID types OSC, OSD, OSE, OSM, and OSN. 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 operates in full duplex mode only and supports jumbo frames when in QDIO mode (CHPID type OSD).
- Minimum: None.
- Maximum: 24 features, 96 ports (four ports per feature). The maximum quantity of all OSA-Express3 and OSA-Express2 features cannot exceed 24 features per server.
- Prerequisites: None.
- Corequisites: None.
- Compatibility Conflicts: When the OSA-Express3 feature is set to autonegotiate, the target device must also be set to autonegotiate. Both ends must match (autonegotiate on or off).
- Customer Setup: No.
- Limitations:
- For CHPID type OSN supporting the Network Control Program (NCP) and the channel data link control (CDLC) protocol note that none of the ports are used for external communication. OSA-Express for NCP does not use ports. All communication is LPAR-to-LPAR. Thus, if both CHPIDs on an OSA-Express3 feature are defined as CHPID type OSN, then none of the four ports are used for external communication.
- When using CHPID type OSM - OSA-Express for Unified Resource Manager, provides connectivity to the intranode m nagement network (INMN) from z196 to Unified Resource Manager functions
- Field Installable: Yes.
- Cable Order: A customer-supplied cable is required. The
OSA-Express3 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).
Note: No cable is required when a port is defined as CHPID type OSN.
(#3370) OSA-Express3 10 Gigabit Ethernet LR
(No Longer Available as of June 30, 2014)
The OSA-Express3 10 Gigabit Ethernet (GbE) long reach (LR) feature has two PCIe adapters and two ports per feature. One port resides on each PCIe adapter and has its own channel path identifier (CHPID). The 10 GbE feature is designed to support attachment to a 10 Gigabits per second (Gbps) Ethernet Local Area Network (LAN) or Ethernet switch capable of 10 Gbps. OSA-Express3 10 GbE LR supports CHPID types OSD and OSX. It can be defined as a spanned channel and can be shared among LPARs within and across LCSSs.
- Minimum: None.
- Maximum: 24 features. The maximum quantity of all OSA-Express3 and OSA-Express2 features cannot exceed 24 features per server.
- Prerequisites: None.
- Corequisites: None.
- Compatibility Conflicts: The OSA-Express3 10 GbE LR feature supports use of an industry standard small form factor LC Duplex connector. Ensure the attaching or downstream device has a long reach (LR) transceiver. The sending and receiving transceivers must be the same (LR to LR which may also be referred to as LW or LX).
- Customer Setup: No.
- Limitations: When defined as CHPID type OSX, the 10 GbE port provides connectivity and access control to the intraensemble data network (IEDN) from z196 to zBX
- Field Installable: Yes.
- Cable Order: A customer-supplied cable is required. A 9 micron single mode fiber optic cable terminated with an LC Duplex connector is required for connecting this feature to the selected device.
(#3863) CP Assist for Cryptographic Function (CPACF) enablement
(No Longer Available as of June 30, 2015)
CPACF, supporting clear key encryption, is activated using the no-charge enablement feature (#3863). For every Processor Unit defined as a Central Processor (CP) or an Integrated Facility for Linux (IFL) it offers the following
- For data privacy and confidentially: Data Encryption Standard (DES),
Triple Data Encryption Standard (TDES), Advanced Encryption Standard
(AES) for 128-bit, 192-bit and 256-bit keys,
- For data integrity: Secure Hash Algorithm-1 (SHA-1) 160-bit, and SHA-2 for 224-, 256-, 384-and 512-bit support. SHA-1 and SHA-2 are shipped enabled on all z196s and do not require the no-charge enablement feature.
- For key generation: Pseudo Random Number Generation (PRNG), Random Number Generation Long (RNGL) - 8 bytes to 8096 bytes, Random Number Generation Long (RNG) with up to 4096-bit key RSA support,
- For message authentication code (MAC): Single-key MAC, Double-key MAC
- For data integrity: Secure Hash Algorithm-1 (SHA-1) 160-bit, and SHA-2 for 224-, 256-, 384-and 512-bit support. SHA-1 and SHA-2 are shipped enabled on all z196s and do not require the no-charge enablement feature.
For new servers, shipped from the factory, CPACF enablement (#3863) is loaded prior to shipment. For other than new shipments, Licensed Internal Code is shipped by an enablement diskette. The function is enabled using the Support Element (SE).
- Minimum: None.
- Maximum: One.
- Prerequisites: None.
- Corequisite: Crypto Express3 (#0864).
- Compatibility Conflicts: None known.
- Customer Setup: No.
- Limitations: None.
- Field Installable: Yes.
(#4000) I/O drawer-air
(No Longer Available as of June 30, 2014)
The I/O drawer for air-cooled machines is a physical resource used to house I/O cards in support of the storage area network (ESCON, FICON Express8, FICON Express4) Crypto Express3, coupling links (ISC-3), the Ethernet local area network (OSA-Express3, OSA-Express2), and turning on/off control units from the central processor complex using the Power Sequence Controller (PSC). The drawer contains 8 I/O slots, 4 I/O slots in the front, and 4 I/O slots in the rear.
The number of drawers is automatically determined by the number of features ordered or carried forward on an upgrade.
- Minimum: None.
- Maximum: Two.
- Prerequisites: None.
- Corequisites: None.
- Compatibility Conflicts: None known.
- Customer Setup: No.
- Limitations: None known.
- Field Installable: Yes. Parts removed become the property of IBM.
- Cable Order: Cables for I/O features are a customer responsibility.
(#4002) I/O cage-air
(No Longer Available as of June 30, 2014)
The I/O cage for air-cooled machines is a physical resource used to house I/O cards in support of the storage area network (ESCON, FICON Express8, FICON Express4) Crypto Express3, coupling links (ISC-3), the Ethernet local area network (OSA-Express3, OSA-Express2), and turning on/off control units from the central processor complex using the Power Sequence Controller (PSC). The cage contains 28 I/O slots, 16 I/O slots in the front and 12 I/O slots in the rear.
The number of drawers is automatically determined by the number of features ordered or carried forward on an upgrade.
- Minimum: None.
- Maximum: Two.
- Prerequisites: None.
- Corequisites: None.
- Compatibility Conflicts: None known.
- Customer Setup: No.
- Limitations: None known.
- Field Installable: Yes. Parts removed become the property of IBM.
- Cable Order: Cables for I/O features are a customer responsibility.
(#4003) PCIe I/O drawer-air
(No Longer Available as of June 30, 2014)
The Peripheral Component Interconnect Express (PCIe) I/O drawer for air-cooled machines is a physical resource used to house I/O cards for the storage area network (FICON Express8S) and the Ethernet local area network (OSA-Express4S). The drawer contains 32 I/O slots, 16 I/O slots in the front and 16 I/O slots in the rear. The number of drawers is automatically determined by the number of FICON Express8S or OSA-Express4S features ordered.
- Minimum: None.
- Maximum: Five.
- Prerequisites: None.
- Corequisites: None.
- Compatibility Conflicts: None known.
- Customer Setup: No.
- Limitations: None known.
- Field Installable: Yes. Parts removed become the property of IBM.
- Cable Order: Cables for I/O features are a customer responsibility.
(#4004) I/O drawer-water
(No Longer Available as of June 30, 2014)
The I/O drawer for water-cooled machines is a physical resource used to house I/O cards in support of the storage area network (ESCON, FICON Express8, FICON Express4) Crypto Express3, coupling links (ISC-3), the Ethernet local area network (OSA-Express3, OSA-Express2), and turning on/off control units from the central processor complex using the Power Sequence Controller (PSC). The drawer contains 8 I/O slots, 4 I/O slots in the front and 4 I/O slots in the rear.
The number of drawers is automatically determined by the number of features ordered or carried forward on an upgrade.
- Minimum: None.
- Maximum: Two.
- Prerequisites: None.
- Corequisites: None.
- Compatibility Conflicts: None known.
- Customer Setup: No.
- Limitations: None known.
- Field Installable: Yes. Parts removed become the property of IBM.
- Cable Order: Cables for I/O features are a customer responsibility.
(#4005) I/O cage-water
(No Longer Available as of June 30, 2014)
The I/O cage for water-cooled machines is a physical resource used to house I/O cards in support of the storage area network (ESCON, FICON Express8, FICON Express4) Crypto Express3, coupling links (ISC-3), the Ethernet local area network (OSA-Express3, OSA-Express2), and turning on/off control units from the central processor complex using the Power Sequence Controller (PSC). The cage contains 28 I/O slots, 16 I/O slots in the front and 12 I/O slots in the rear.
The number of drawers is automatically determined by the number of features ordered or carried forward on an upgrade.
- Minimum: None.
- Maximum: Two.
- Prerequisites: None.
- Corequisites: None.
- Compatibility Conflicts: None known.
- Customer Setup: No.
- Limitations: None known.
- Field Installable: Yes. Parts removed become the property of IBM.
- Cable Order: Cables for I/O features are a customer responsibility.
(#4006) PCIe I/O drawer-water
(No Longer Available as of June 30, 2014)
The Peripheral Component Interconnect Express (PCIe) I/O drawer for water-cooled machines is a physical resource used to house I/O cards for the storage area network (FICON Express8S) and the Ethernet local area network (OSA-Express4S). The drawer contains 32 I/O slots, 16 I/O slots in the front and 16 I/O slots in the rear. The number of drawers is automatically determined by the number of FICON Express8S or OSA-Express4S features ordered.
- Minimum: None.
- Maximum: Five.
- Prerequisites: None.
- Corequisites: None.
- Compatibility Conflicts: None known.
- Customer Setup: No.
- Limitations: None known.
- Field Installable: Yes. Parts removed become the property of IBM.
- Cable Order: Cables for I/O features are a customer responsibility.
(#6096) Flat-panel display
(No Longer Available as of June 30, 2014)
The display offers the benefits of a flat-panel monitor including improved use of space and reduced energy consumption compared to CRT monitors.
- Minimum: None.
- Maximum: Ten (10).
- Prerequisites: None.
- Corequisites: None.
- Compatibility Conflicts: None known.
- Customer Setup: No.
- Limitations: None
- Field Installable: Yes. Parts removed as a result of feature conversion become the property of IBM.
- Cable Order: None.
(#6501) Power Sequence Controller (PSC)
(No Longer Available as of June 30, 2014)
The power sequence controller provides the ability to turn control units on and off from the central processor complex (CPC). The PSC feature consists of one PSC24V card, one PSC Y-cable, and two PSC relay boxes that are mounted near the I/O cages within the server. The PSC24V card always displaces one I/O feature in an I/O cage or I/O drawer.
- Minimum number of features: None.
- Maximum number of features: Two on air cooled models and One on water cooled models.
- Prerequisites: One I/O cage or I/O drawer per #6501 feature.
- Corequisites: None.
- Compatibility Conflicts: None known.
- Limitations: There may be instances where the maximum number of features is limited to one feature (based upon model and I/O configuration). Can not be added via loose-piece MES.
(#6805) Additional CBU Test
(No Longer Available as of June 30, 2015)
An additional test activation that can be purchased with each CBU temporary entitlement record. There can be no more than 15 tests per CBU TER.
- Minimum: 0.
- Maximum: 15 per each instance of #6818, Capacity back up, CBU.
- Prerequisites: #6818
- Corequisites: None.
- Compatibility Conflicts: None known.
- Customer Setup: No.
- Limitations: None.
- Field Installable: Yes.
(#6817) One 1 CBU year
(No Longer Available as of June 30, 2015)
Used to set the expiration date of a Capacity back up (CBU) temporary entitlement record.
- Minimum number of features: One.
- Maximum number of features: Five (5).
- Prerequisites: Capacity back up (#6818).
- Corequisites: None.
- Compatibility Conflicts: None known.
- Customer Setup: Not applicable.
- Limitations: None.
- Field Installable: Yes.
(#6818) Capacity back up (CBU)
(No Longer Available as of June 30, 2015)
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 number of features: None.
- Maximum number of features: Eight (8) per ordering session.
- Prerequisites: None.
- Corequisites: CBU Authorization (#9910).
- Compatibility Conflicts: None known.
- Customer Setup: The CBU TER must be installed using the HMC Configuration Manager before it can be activated.
- Limitations: None.
- Field Installable: Yes.
(#6820) Single CBU CP-year
(No Longer Available as of June 30, 2015)
Pricing feature equal to the remainder of the number of CBU years multiplied by the number of temporary CP capacity features divided by 25.
- Minimum: None.
- Maximum: 24.
- Prerequisites: Capacity back up (#6818).
- Corequisites: None.
- Compatibility Conflicts: None known.
- Customer Setup: No.
- Limitations: None.
- Field Installable: Yes.
(#6821) 25 CBU CP-year
(No Longer Available as of June 30, 2015)
Pricing feature equal to the quotient of the number of CBU years multiplied by the temporary Central Processor (CP) capacity features divided by 25.
- Minimum: None.
- Maximum: 250.
- Prerequisites: Capacity back up (#6818).
- Corequisites: None.
- Compatibility Conflicts: None known.
- Customer Setup: No.
- Limitations: None.
- Field Installable: Yes.
(#6822) Single CBU IFL Year
(No Longer Available as of June 30, 2015)
Pricing feature equal to the remainder of the number of CBU years multiplied by the number of temporary Integrated Facility for Linux (IFL) features divided by 25.
- Minimum: None.
- Maximum: 24.
- Prerequisites: Capacity back up (#6818).
- Corequisites: None.
- Compatibility Conflicts: None known.
- Customer Setup: No.
- Limitations: None.
- Field Installable: Yes.
(#6823) 25 CBU IFL Year
(No Longer Available as of June 30, 2015)
Pricing feature equal to the quotient of the number of CBU years multiplied by the number of temporary IFL features divided by 25.
- Minimum: None.
- Maximum: 250.
- Prerequisites: Capacity back up (#6818).
- Corequisites: None.
- Compatibility Conflicts: None known.
- Customer Setup: No.
- Limitations: None.
- Field Installable: Yes.
(#6824) Single CBU ICF-Year
(No Longer Available as of June 30, 2015)
Pricing feature equal to the remainder of the number of CBU years multiplied by the number of temporary ICF features divided by 25.
- Minimum: None.
- Maximum: 24.
- Prerequisites: Capacity back up (#6818).
- Corequisites: None.
- Compatibility Conflicts: None known.
- Customer Setup: No.
- Limitations: None.
- Field Installable: Yes.
(#6825) 25 CBU ICF-Year
(No Longer Available as of June 30, 2015)
Pricing feature equal to the quotient of the number of CBU years multiplied by the number of temporary Internal Coupling Facility (ICF) features divided by 25.
- Minimum: None.
- Maximum: 250.
- Prerequisites: Capacity back up (#6818).
- Corequisites: None.
- Compatibility Conflicts: None known.
- Customer Setup: No.
- Limitations: None.
- Field Installable: Yes.
(#6826) Single CBU zAAP-Year
Pricing feature equal to the remainder of the number of CBU years multiplied by the number of temporary zAAP features divided by 25.
- Minimum: None.
- Maximum: 24.
- Prerequisites: Capacity back up (#6818).
- Corequisites: None.
- Compatibility Conflicts: None known.
- Customer Setup: No.
- Limitations: None.
- Field Installable: Yes.
(#6827) 25 CBU zAAP-Year
Pricing feature equal to the quotient of the number of CBU years multiplied by the number of temporary System z Application Assist Processor (zAAP) features divided by 25.
- Minimum: None.
- Maximum: 250.
- Prerequisites: Capacity back up (#6818).
- Corequisites: None.
- Compatibility Conflicts: None known.
- Customer Setup: No.
- Limitations: None.
- Field Installable: Yes.
(#6828) Single CBU zIIP-Year
Pricing feature equal to the remainder of the number of CBU years multiplied by the number of temporary System z Integrated Information Processor (zIIP) features divided by 25.
- Minimum: None.
- Maximum: 24.
- Prerequisites: Capacity back up (#6818).
- Corequisites: None.
- Compatibility Conflicts: None known.
- Customer Setup: No.
- Limitations: None.
- Field Installable: Yes.
(#6829) 25 CBU zIIP-Year
Pricing feature equal to the quotient of the number of CBU years multiplied by the number of temporary zIIP features divided by 25.
- Minimum: None.
- Maximum: 250.
- Prerequisites: Capacity back up (#6818).
- Corequisites: None.
- Compatibility Conflicts: None known.
- Customer Setup: No.
- Limitations: None.
- Field Installable: Yes.
(#6830) Single CBU SAP-Year
Pricing feature equal to the remainder of the number of CBU years multiplied by the number of temporary SAP features divided by 25.
- Minimum: None.
- Maximum: 24.
- Prerequisites: Capacity back up (#6818).
- Corequisites: None.
- Compatibility Conflicts: None known.
- Customer Setup: No.
- Limitations: None.
- Field Installable: Yes.
(#6831) 25 CBU SAP-Year
Pricing feature equal to the quotient of the number of CBU years multiplied by the number of temporary System Assist Processor (SAP) features divided by 25.
- Minimum: None.
- Maximum: 250.
- Prerequisites: Capacity back up (#6818).
- Corequisites: None.
- Compatibility Conflicts: None known.
- Customer Setup: No.
- Limitations: None.
- Field Installable: Yes.
(#6832) CBU Replenishment
(No Longer Available as of June 30, 2015)
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: None.
- Maximum: One.
- Prerequisites: Capacity back up (#6818).
- Corequisites: None.
- Compatibility Conflicts: None known.
- Customer Setup: No.
- Limitations: None.
- Field Installable: Yes.
(#6833) Capacity for Planned Event (CPE)
(No Longer Available as of June 30, 2015)
This feature code corresponds to the number of different CPE Temporary Entitlement Records (TERs) ordered.
- Minimum: None.
- Maximum: Eight (8) per ordering session.
- Prerequisites: None.
- Corequisites: CPE authorization (#9912).
- Compatibility Conflicts: None known.
- Customer Setup: The CBU TER must be installed using the HMC Configuration Manager before it can be activated.
- Limitations: None.
- Field Installable: Yes.
(#7900 - #7919) Fiber Quick Connect
(No Longer Available as of June 30, 2014)
Note: Features #7901,#7907,#7909,#7911,#7917,#7919 still available.
The Fiber Quick Connect (FQC) features are optional features for factory installation of the IBM Fiber Transport System (FTS) fiber harnesses for connection to ESCON and FICON LX channels in an I/O cage or I/O drawer. Fiber Quick Connect is for factory installation only, and is available on new servers and on initial upgrades to z196. FQC is not available as an MES to an existing z196. Each direct-attach fiber harness connects to six ESCON or FICON LX channels at one end and one coupler in a Multi-Terminated Push-On Connector (MTP) coupler bracket at the opposite end. Each bracket has positions for 10 MTP connectors to be plugged, each MTP supporting 12 fiber pairs (six ESCON or FICON LX channels), for a total of 120 fiber pairs for each MTP coupler bracket.
When FQC is ordered, the configuration tool selects the required number of MTP mounting brackets and mounting hardware based upon the ESCON and FICON LX feature quantity.
Note: FQC supports all of the ESCON and FICON LX channels. FQC cannot be ordered for selected channels.
(#7942) Top exit I/O cabling
(No Longer Available as of June 30, 2014)
This description is for information purposes only. When top exit I/O cabling is selected on an order, the required infrastructure is provided. Frame extensions are added to each corner of the system with this option. Routing of cabling from I/O cages and/or I/O drawers will exit out the top of the frame (either the "A" or the "Z" frame). Top exit I/O cabling applies to all of your fiber optic cables (ESCON, FICON, OSA, 12x InfiniBand, 1x InfiniBand, and ISC-3) as well as your copper cables for the 1000BASE-T Ethernet features.
Top exit I/O cabling is designed to provide you with an additional option. Instead of all of your cabling exiting under the server and/or under the raised floor, you now have the flexibility to choose the option that best meets the requirements of your data center. Top exit I/O cabling can also help to increase air flow.
- Minimum: None
- Maximum: One.
- Prerequisites: None
- Corequisites: None
- Compatibility Conflicts: Cannot coexist with side covers (#7949).
- Customer Setup: No.
- Limitations: This feature #7942 is mutually exclusive with the Side Cover feature (#7949). If #7949 is on the order, #7942 cannot be ordered. Power cables continue to be a floor exit only.
- Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
- Cable Order: Cabling is a customer responsibility.
(#8008) Frame bolt down kit for air cooled machines
(No Longer Available as of June 30, 2014)
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.
- Minimum: None.
- Maximum: One. (for a two-frame system)
- Prerequisites: None.
- Corequisites: None.
- Compatibility Conflicts: Features 8008 and 8009 are mutually exclusive with each other.
- Customer Setup: No.
- Limitations: None known.
- Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
(#8009) Frame bolt down kit for water cooled machines
(No Longer Available as of June 30, 2014)
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.
- Minimum: None.
- Maximum: One. (for a two-frame system)
- Prerequisites: None.
- Corequisites: None.
- Compatibility Conflicts: Features 8008 and 8009 are mutually exclusive with each other.
- Customer Setup: No.
- Limitations: None known.
- Field Installable: Yes. Parts removed as a result of feature conversions become the property of IBM.
(#9896) On/Off CoD Authorization
(No Longer Available as of June 30, 2015)
This feature is ordered to enable the ordering of On/Off Capacity on Demand (On/Off CoD) through Resource Link.
- Minimum number of features: One.
- Maximum number of features: One.
- Prerequisites: On Line Capacity on Demand (#9900).
- Corequisites: None.
- Compatibility Conflicts: None known.
- Customer Setup: Not applicable.
- Limitations: None.
- Field Installable: Yes.
(#9898) Permanent Upgrade authorization
(No Longer Available as of June 30, 2015)
This feature is ordered to enable the ordering of Licensed Internal Code Configuration Control (LICCC) enabled, permanent capacity upgrades through Resource Link.
- Minimum number of features: One.
- Maximum number of features: One.
- Prerequisites: On Line Capacity on Demand (#9900).
- Corequisites: None.
- Compatibility Conflicts: None known.
- Customer Setup: Not applicable.
- Limitations: None.
- Field Installable: Yes.
(#9900) On Line Capacity on Demand (CoD) Buying
(No Longer Available as of June 30, 2015)
This feature is ordered to enable purchasing either permanent capacity upgrades or temporary capacity upgrades through Resource Link.
- Minimum number of features: One.
- Maximum number of features: One.
- Prerequisites: None.
- Corequisites: None.
- Compatibility Conflicts: None known.
- Customer Setup: Not applicable.
- Limitations: None.
- Field Installable: Yes.
(#9910) CBU Authorization
(No Longer Available as of June 30, 2015)
This feature enables the purchase of Capacity back up (CBU). This feature is generated when Capacity back up (#6818) is ordered, or it can be ordered by itself. This feature along with On Line Capacity on Demand (#9900) is required to order CBU through Resource Link.
- Minimum number of features: One.
- Maximum number of features: One.
- Prerequisites: None.
- Corequisites: Capacity back up (#6818).
- Compatibility Conflicts: None known.
- Field Installable: Yes.
(#9912) CPE Authorization
(No Longer Available as of June 30, 2015)
This feature is ordered to enable the purchase of Capacity for Planned Event (CPE). This feature is generated when Capacity for Planned Event (#6833) is ordered. This feature along with On Line Capacity on Demand (#9900) is required to order CPE through Resource Link.
- Minimum number of features: One.
- Maximum number of features: One.
- Prerequisites: None.
- Corequisites: Capacity for Planned Event (#6833).
- Compatibility Conflicts: None known.
- Customer Setup: Not applicable.
- Limitations: None.
- Field Installable: Yes.
(#9917) 1 MSU-day
(No Longer Available as of June 30, 2015)
Pricing feature is 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 number of features: None.
- Maximum number of features: 99.
- Prerequisites: On-Line Capacity on Demand (#9900).
- Corequisites: None.
- Compatibility Conflicts: None known.
- Customer Setup: Not applicable.
- Limitations: None.
- Field Installable: Yes.
(#9918) 100 MSU-days
(No Longer Available as of June 30, 2015)
Pricing feature is used to facilitate the billing of On/Off Capacity on Demand (On/Off CoD) temporary CP resource tokens purchased through Resource Link.
- Minimum number of features: None.
- Maximum number of features: 99.
- Prerequisites: On-Line Capacity on Demand (#9900).
- Corequisites: 1 MSU-day (#9917)
- Compatibility Conflicts: None known.
- Customer Setup: Not applicable.
- Limitations: None.
- Field Installable: Yes.
(#9919) 10,000 MSU-days
(No Longer Available as of June 30, 2015)
Pricing feature is used to facilitate the billing of On/Off Capacity on Demand (On/Off CoD) temporary CP resource tokens purchased through Resource Link.
- Minimum number of features: None.
- Maximum number of features: 250.
- Prerequisites: On-Line Capacity on Demand (#9900).
- Corequisites: 1 MSU-day (#9917), 100 MSU-days (#9918)
- Compatibility Conflicts: None known.
- Customer Setup: Not applicable.
- Limitations: None.
- Field Installable: Yes.
(#9920) IFL-day
(No Longer Available as of June 30, 2015)
Pricing feature is 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 number of features: None.
- Maximum number of features: 99.
- Prerequisites: On-Line Capacity on Demand (#9900).
- Corequisites: None.
- Compatibility Conflicts: None known.
- Customer Setup: Not applicable.
- Limitations: None.
- Field Installable: Yes.
(#9921) 100 IFL-days
(No Longer Available as of June 30, 2015)
Pricing feature is used to facilitate the billing of On/Off Capacity on Demand (On/Off CoD) temporary IFL resource tokens purchased through Resource Link.
- Minimum number of features: None.
- Maximum number of features: 250.
- Prerequisites: On-Line Capacity on Demand (#9900).
- Corequisites: 1 IFL-day (#9920)
- Compatibility Conflicts: None known.
- Customer Setup: NA.
- Limitations: None.
- Field Installable: Yes.
(#9922) 1 ICF-day
(No Longer Available as of June 30, 2015)
Pricing feature is used to facilitate the billing of On/Off Capacity on Demand (On/Off CoD) temporary Internal Coupling Facility (ICF) resource tokens purchased through Resource Link.
- Minimum number of features: None.
- Maximum number of features: 99.
- Prerequisites: On-Line Capacity on Demand (#9900).
- Corequisites: None.
- Compatibility Conflicts: None known.
- Customer Setup: Not applicable.
- Limitations: None.
- Field Installable: Yes.
(#9923) 100 ICF-days
(No Longer Available as of June 30, 2015)
Pricing feature is used to facilitate the billing of On/Off Capacity on Demand (On/Off CoD) temporary ICF resource tokens purchased through Resource Link.
- Minimum number of features: None.
- Maximum number of features: 250.
- Prerequisites: On-Line Capacity on Demand (#9900).
- Corequisites: 1 ICF-day (#9921)
- Compatibility Conflicts: None known.
- Customer Setup: NA.
- Limitations: None.
- Field Installable: Yes.
(#9924) 1 zIIP-day
(No Longer Available as of June 30, 2015)
Pricing feature is used to facilitate the billing of On/Off Capacity on Demand (On/Off CoD) temporary System z Integrated Information Processor (zIIP) resource tokens purchased through Resource Link.
- Minimum number of features: None.
- Maximum number of features: 99.
- Prerequisites: On-Line Capacity on Demand (#9900).
- Corequisites: None.
- Compatibility Conflicts: None known.
- Customer Setup: Not applicable.
- Limitations: None.
- Field Installable: Yes.
(#9925) 100 zIIP-days
(No Longer Available as of June 30, 2015)
Pricing feature is used to facilitate the billing of On/Off Capacity on Demand (On/Off CoD) temporary zIIP resource tokens purchased through Resource Link.
- Minimum number of features: None.
- Maximum number of features: 250.
- Prerequisites: On-Line Capacity on Demand (#9900).
- Corequisites: 1 zIIP-day (#9924)
- Compatibility Conflicts: None known.
- Customer Setup: NA.
- Limitations: None.
- Field Installable: Yes.
(#9926) 1 zAAP-day
(No Longer Available as of June 30, 2015)
Pricing feature is used to facilitate the billing of On/Off Capacity on Demand (On/Off CoD) temporary System z Application Assist Processor (zAAP) resource tokens purchased through Resource Link.
- Minimum number of features: None.
- Maximum number of features: 99.
- Prerequisites: On-Line Capacity on Demand (#9900).
- Corequisites: None.
- Compatibility Conflicts: None known.
- Customer Setup: Not applicable.
- Limitations: None.
- Field Installable: Yes.
(#9927) 100 zAAP-days
(No Longer Available as of June 30, 2015)
Pricing feature is used to facilitate the billing of On/Off Capacity on Demand (On/Off CoD) temporary zAAP resource tokens purchased through Resource Link.
- Minimum number of features: None.
- Maximum number of features: 250.
- Prerequisites: On-Line Capacity on Demand (#9900).
- Corequisites: 1 zAAP-day (#9926)
- Compatibility Conflicts: None known.
- Customer Setup: NA.
- Limitations: None.
- Field Installable: Yes.
(#9928) 1 SAP-day
(No Longer Available as of June 30, 2015)
Pricing feature is 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 number of features: None.
- Maximum number of features: 99.
- Prerequisites: On-Line Capacity on Demand (#9900).
- Corequisites: None.
- Compatibility Conflicts: None known.
- Customer Setup: Not applicable.
- Limitations: None.
- Field Installable: Yes.
(#9929) 100 SAP-days
(No Longer Available as of June 30, 2015)
Pricing feature is used to facilitate the billing of On/Off Capacity on Demand (On/Off CoD) temporary SAP resource tokens purchased through Resource Link.
- Minimum number of features: None.
- Maximum number of features: 250.
- Prerequisites: On-Line Capacity on Demand (#9900).
- Corequisites: 1 SAP-day (#9928)
- Compatibility Conflicts: None known.
- Customer Setup: NA.
- Limitations: None.
- Field Installable: Yes.
(#9975) Height reduction for shipping (z196)
(No Longer Available as of June 30, 2014)
This feature is required if it is necessary to reduce the shipping height of the z196. 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.
This optional feature should be ordered if you have doorways with openings less than 2032 mm (80.0 inches) high. This feature accommodates doorway openings as low as 1832 mm (72.1 inches). Top hat and side covers are shipped separately. If Internal Battery features (#3212) are a part of the order, they will be shipped separately. Instructions are included for the reassembly on site by IBM personnel.
- Minimum number of features: None.
- Maximum number of features: One.
- Prerequisites: None.
- Corequisites: None.
- Compatibility Conflicts: None known.
(#9976) Frame height reduction for return of 2094/2097 (z9 EC/z10 EC
(No Longer Available as of June 30, 2014)
This is for conversions from z9 EC(2094) or z10 EC (2097) to z196 (2817) only. The frame height reduction provides the tools and instructions to reduce the height of a 2094/2097 when returned to IBM on an upgrade from z9 EC to a z196 or a z10 EC to z196 (2817).
- Minimum number of features: None.
- Maximum number of features: One.
- Prerequisites: None.
- Corequisites: None
- Compatibility Conflicts: None known.
Back to top
|
|
| Accessories |
|
|
None.
Customer replacement parts
Not available.
Back to top
|
|
| Machine elements |
|
|
Not available.
Back to top
|
|
| Supplies |
|
|
None.
Supplemental media
Trademarks
(R), (TM), * Trademark or registered trademark of International Business Machines Corporation.
** Company, product, or service name may be a trademark or service mark of others.
UNIX is a registered trademark in the United States and other
countries licensed exclusively through X/Open Company Limited.
© IBM Corporation 2014.
Back to top