Operating system support
This chapter contains operating system requirements and support considerations for the
IBM z13 and its features.
IBM z13 and its features.
This chapter describes the following topics:
Support of the IBM z13 functions depends on the operating system version and release. This information is subject to change. Therefore, for the most current information, see the Preventive Service Planning (PSP) bucket for 2964DEVICE.
4.1 Software support summary
The software portfolio for the IBM z13 includes various operating systems and middleware that support the most recent and significant technologies. Continuing the mainframe-rich tradition, five major operating systems are supported:
•z/OS
•z/VM
•z/VSE
•z/TPF
•Linux on z Systems
For software that is supported on the zBX Model 004, see 4.3, “Software support for zBX Model 004” on page 128.
Operating systems summary
Table 4-1 lists current and minimum operating system levels that are required to support IBM z13. Operating system levels that are no longer in service are not covered in this publication. These older levels can provide support for certain features.
Table 4-1 z13 operating system requirements
|
Operating system
|
ESA/390
(31-bit mode)
|
z/Architecture
(64-bit mode)
|
End of service
|
Notes
|
|
z/OS V2R1
|
No
|
Yes
|
September 20181
|
See the z/OS, z/VM, z/VSE, and z/TPF subsets of the 2964DEVICE Preventive Service Planning (PSP) buckets before installing z13.
|
|
z/OS V1R13
|
No
|
Yes
|
September 2016a
|
|
|
z/OS V1R12
|
No
|
Yes
|
September 20142
|
|
|
z/VM V6R33
|
No
|
Yes
|
April 2017a
|
|
|
z/VM V6R2c
|
No
|
Yes
|
December 2016a
|
|
|
z/VSE V5R2d
|
No
|
Yes
|
Not announced
|
|
|
z/VSE V5R14
|
No
|
Yes
|
June 2016a
|
|
|
z/TPF V1R1
|
Yes
|
Yes
|
Not announced
|
|
|
Linux on z Systems
|
No5
|
1 Planned date. All statements regarding IBM plans, directions, and intent are subject to change or withdrawal without notice. Any reliance on these Statements of Direction is at the relying party's sole risk and will not create liability or obligation for IBM.
2 z/OS V1R12 with required maintenance (compatibility support only) and extended support agreement
3 z/VM V6R2 and V6R3 require an architectural level set exclusive to z10 and successors.
4 z/VSE V5 requires an architectural level set exclusive to z9 and successors.
5 64-bit distributions include a 31-bit emulation layer to run 31-bit software products.
|
PTFs and PSP buckets: The use of several features depends on a particular operating system. In all cases, program temporary fixes (PTF) might be necessary with the operating system level indicated.
Preventive Service Planning (PSP) buckets are continuously updated and are reviewed regularly when planning for installation of a new system. They contain the latest information about installation, hardware and software service levels, service recommendations, and cross-product dependencies.
For Linux on z Systems distributions, consult the distributor’s support information.
|
Middleware
The following middleware offerings are for the IBM z13 environments:
•Transaction processing
– WebSphere Application Server and WebSphere Extended Deployment
– CICS Transaction Server
– CICS Transaction Gateway
– IMS DB and IMS DC
– IMS Connect
•Application integration and connectivity
– WebSphere Message Broker
– WebSphere MQ
– WebSphere ESB
•Process integration
– WebSphere Process Server
– WebSphere MQ Workflow
– WebSphere Business Integration Server
•Database
– IBM DB2 for z/OS
– IBM DB2 for Linux
– IBM DB2 Connect™
Service Management
The IBM Tivoli® brand has a large product set that includes the following offerings:
•IBM Tivoli Service Management Center
•IBM Tivoli Information Management for z/OS
•IBM Tivoli Workload Scheduler
•IBM Tivoli OMEGAMON® XE
•IBM Tivoli System Automation
Security
A highly secure z Systems environment can be implemented at various levels by using the following products:
•IBM Security zSecure™ suite
•The Security Server component of z/OS and z/VM; includes Resource Access Control Facility (IBM RACF®)
•IBM Tivoli Directory Server for z/OS
•z/OS Communications Server and Policy Agent; for policy-based network security
•The z/OS Cryptographic Services component of z/OS; includes the Integrated Cryptographic Service Facility (ICSF)
Application development and languages
Several programming languages are available for the IBM z13 environment. Because the Linux environment is similar to Linux on other servers, we focus on the z/OS environment.
In addition to the traditional COBOL, PL/I, Fortran, and Assembler languages, z Systems support C, C++, and Java (including Java Platform, Enterprise Edition and batch environments) programming languages also.
Development can be conducted by using the latest software engineering technologies and advanced integrated development environments (IDE). The extensive tool set uses a workstation environment for development and testing, with final testing and deployment performed on z/OS. Application development tools, many of which have components that are based on the Eclipse platform, are provided through the following offerings:
•IBM Rational® Application Developer for WebSphere
•IBM Rational Developer for z Systems
•IBM WebSphere Developer for z Systems
•IBM Rational Rose® product line
•IBM Rational Software Architect and Software Modeler
For more information about software for z Systems, see this web page:
We cannot emphasize enough the importance of using the most recent versions of the compilers. The compilers enable the use of the latest technologies that are implemented on the system and take advantage of the performance benefits that are introduced. Examples of benefits include new cache structures, new machine instructions, and instruction execution enhancements.
For example, the z13 processor introduces single-instruction, multiple-data (SIMD) instruction set, which uses the enhanced superscalar z13 core to process a large number of operands (vector) through a single instruction, allowing the development of smaller and optimized codes to improve efficiency of complex mathematical models and vector processing. This feature will be fully used by z/OS V2R1 operating system and several compilers have built-in functions for SMID.
|
Statement of Direction1 (SIMD Support - z/VM support SIMD): In a future deliverable, IBM intends to deliver support to enable z/VM guests to used the Vector Facility for z/Architecture (SIMD).
|
1 All statements regarding IBM plans, directions, and intent are subject to change or withdrawal without notice. Any reliance on these statements of general direction is at the relying party’s sole risk and will not create liability or obligation for IBM.
IBM compilers
Each new version of IBM z/OS compilers (Enterprise COBOL, Enterprise PL/I, XL C/C++) underscores the continuing IBM commitment to the COBOL, PL/I, and C/C++ programming languages on the z/OS platform.
Enterprise COBOL
The most recent version of Enterprise COBOL uses the most recent z/Architecture and performance optimization, enhanced XML parsing support, and capability of programming with Unicode, and supports Java 7 SDKs for Java interoperability.
Enterprise PL/I
The latest version of Enterprise PL/I provides web interoperability, which includes web services, XML parsers, and Java Platform, Enterprise Edition (Java EE). The compiler also includes the expanded support for UTF-16.
z/OS XL C/C++
The z/OS XL C/C++ uses the latest z/Architecture, including z13 servers. It enables developing high performance oriented applications, through the services provided by Language Environment and Runtime Library extension base elements, and works in concert with z/OS problem determination tools.
Application development tools
IBM Enterprise COBOL and Enterprise PL/I support are strategic components (separately orderable products) for IBM Rational Developer for IBM z Systems software. These features provide a robust, integrated development environment (IDE) for COBOL and PL/I and connecting web services, Java Platform, Enterprise Edition (Java EE) applications, and traditional business processes.
z/OS XL C/C++ programmers can also tap into Rational Developer for z Systems to boost their productivity by easily editing, compiling, and debugging z/OS XL C and XL C++ applications right from their workstation.
4.2 Support by operating system
In this section, we list the support by in-service operating systems of selected functions of the z13. For a detailed description of the z13 and its features, see the IBM z13 Technical Guide, SG24-8251. For an in-depth description of all I/O features, see the IBM z Systems Connectivity Handbook, SG24-5444.
4.2.1 z/OS
z/OS Version 1 Release 12 is the earliest in-service release that supports the z13, with required maintenance (compatibility support only) and extended support agreement.
Table 4-2 on page 116 summarizes the support requirements of selected z13 functions for the currently supported z/OS releases. In the table, Y (yes) means the function is supported, N (no) means the function is not supported.
Table 4-2 z/OS support summary
|
Function
|
V2R1
|
V1R13
|
V1R12
|
|
z13
|
Y
|
Y1
|
Ya
|
|
Support of 141 PUs by a single system image
|
Y
|
N2
|
Nb
|
|
Support of IBM zAware
|
Y
|
Y
|
N
|
|
IBM z Integrated Information Processor (zIIP)
|
Y3
|
Yc
|
Yc
|
|
4 TB memory per LPAR exploitation
|
Y4
|
N
|
N
|
|
Pageable 1 MB Large page support
|
Y
|
Y5
|
N
|
|
Decimal Floating point support for packed decimal conversions
|
Y
|
Y
|
N
|
|
2 GB Large Page Support
|
Y
|
Y
|
N
|
|
Support up to 85 LPARs
|
Y6
|
Yg
|
N
|
|
Support for six logical channel sub systems (CSS)
|
Y
|
Y
|
N
|
|
Support for 4 sub channel sets per CSS
|
Y
|
Y
|
N
|
|
Single-instruction, multiple-data (SIMD) support
|
Y
|
N
|
N
|
|
Two way simultaneous multi threading support (SMT-2)
|
Y7
|
N
|
N
|
|
HiperDispatch
|
Y
|
Y
|
Y
|
|
EP 11 cryptography support
|
Y
|
Y8
|
Yf
|
|
Common Cryptographic architecture >16 Domain Support
|
Y
|
Y9
|
N
|
|
CPACF
|
Y
|
Y
|
Y
|
|
CPACF AES-128, AES-192, and AES-256
|
Y
|
Y
|
Y
|
|
CPACF SHA-1, SHA-224, SHA-256, SHA-384, SHA-512
|
Y
|
Y
|
Y
|
|
CPACF protected key
|
Y
|
Y
|
Y
|
|
Crypto Express5S
|
Y10
|
Yh
|
Yh
|
|
Secure IBM Enterprise PKCS #11 (EP11) coprocessor mode
|
Y
|
Y
|
Y
|
|
Elliptic Curve Cryptography (ECC)
|
Y
|
Y
|
Y
|
|
Flash Express
|
Y
|
Y
|
N
|
|
zEDC Express
|
Y
|
N11
|
Nk
|
|
Shared (SR-IOV) 10GbE RoCE Express
|
Y
|
N
|
N
|
|
zHPF (High Performance FICON) Extended Distance II
|
Y
|
Y
|
N
|
|
FICON Dynamic Routing
|
Y
|
Y
|
N
|
|
Fabric Priority for an I/O request
|
Y
|
Y
|
N
|
|
FICON Express 16S
|
Y
|
Y
|
Y
|
|
FICON Express8S
|
Y
|
Y
|
Y
|
|
FICON Express812
|
Y
|
Y
|
Y
|
|
OSA-Express5S 10 Gigabit Ethernet LR and SR
CHPID type OSD
|
Y
|
Y
|
Y
|
|
OSA-Express5S 10 Gigabit Ethernet LR and SR
CHPID type OSX
|
Y
|
Y
|
Y
|
|
OSA-Express5S Gigabit Ethernet LX and SX
CHPID type OSD (using two ports per CHIPID)
|
Y
|
Y
|
Y
|
|
OSA-Express5S 1000BASE-T
CHPID type OSC (using two ports per CHPID)
|
Y
|
Y
|
Y
|
|
OSA-Express5S 1000BASE-T
CHPID type OSD (using two ports per CHPID)
|
Y
|
Y
|
Y
|
|
OSA-Express5S 1000BASE-T
CHPID type OSE(using one port per CHPID)
|
Y
|
Y
|
Y
|
|
OSA-Express5S 1000BASE-T
CHPID type OSM
|
Y
|
Y
|
Y
|
|
OSA-Express5S 1000BASE-T
CHPID type OSN (using one port per CHPID)
|
Y
|
Y
|
Y
|
|
OSA-Express4S 10 Gigabit Ethernet LR and SR
CHPID type OSD
|
Y
|
Y
|
Y
|
|
OSA-Express4S 10 Gigabit Ethernet LR and SR
CHPID type OSX
|
Y
|
Y
|
Y
|
|
OSA-Express4S Gigabit Ethernet LX and SX
CHPID type OSD (using two ports)
|
Y
|
Y
|
Y
|
|
OSA-Express4S 1000BASE-T
CHPID type OSC (using two ports per CHPID)
|
Y
|
Y
|
Y
|
|
OSA-Express4S 1000BASE-T
CHPID type OSD (using two ports per CHPID)
|
Y
|
Y
|
Y
|
|
OSA-Express4S 1000BASE-T
CHPID type OSE (using two ports per CHPID)
|
Y
|
Y
|
Y
|
|
OSA-Express4S 1000BASE-T
CHPID type OSM (using two ports per CHIPID)
|
Y
|
Y
|
Y
|
|
OSA-Express4S 1000BASE-T
CHPID type OSN (using two ports per CHPID)
|
Y
|
Y
|
Y
|
|
Coupling using InfiniBand
CHPID type CIB
|
Y
|
Y
|
Y
|
|
InfiniBand coupling links (12x IFB-SDR or 12x IFB-DDR) at a distance of 150 m
|
Y
|
Y
|
Y
|
|
InfiniBand coupling links (1x IFB-SDR or 1x IFB-DDR) at an unrepeated distance of 10 km
|
Y
|
Y
|
Y
|
|
IBM Integrated Coupling Adapter support (ICA)
|
Y
|
Y
|
Y
|
|
Server Time Protocol
|
Y
|
Y
|
Y
|
|
CFCC Level 20
|
Y
|
Y
|
Y
|
|
Assembler instruction mnemonics
|
Y
|
Y
|
Y
|
|
C/C++ exploitation of hardware instructions
|
Y13
|
N
|
N
|
|
CPU measurement facility
|
Y
|
Y
|
Y
|
1 Service is required for support of z13.
2 z/OS 1.13 and z/OS 1.12 support 100 cores per LPAR
3 On an upgrade from z196 or zEC12, installed zAAPs are converted to zIIPs by default. zAAPs are no more supported on z13.
4 4TB Support on z/oS LPAR with z/OS V2R1 is SoD
5 A web deliverable is required for Pageable 1M Large Page Support.
6 This supported only if the LPARs are running z/OS V2R1.IF z/OS V1R12 is running in any of the LPARs then only 60 LPARs are supported
7 Only for zIIP eligible workload
8 With Cryptographic support for z/OS V1R12-V1R13 web deliverable
9 With PTF and RSM enablement offering
10 Enhanced cryptographic support for z/OS V1R13-z/OS V2R1 web deliverable
11 Software decompression only.
12 Carry forward from zEC12/z196 only
13 z13 Exploitation Support for V2R1 XL C/C++ web deliverable
4.2.2 z/VM
At general availability, z/VM V6R3 and z/VM V6R2 provide compatibility support with use of some new z13 functions.
|
Statements of Direction1:
•Removal of support for Expanded Storage (XSTORE): z/VM 6.3 is the last z/VM release to support XSTORE for either host or guest usage. The IBM z13 will be the last high-end server to support XSTORE.
•Stabilization of z/VM V6.2 support: The IBM z13 server family is planned to be the last z Systems server supported by z/VM V6.2 and the last z Systems server that will be supported where z/VM V6.2 is running as a guest (second level). This is in conjunction with the statement of direction that the IBM z13 server family will be the last to support ESA/390 architecture mode, which z/VM V6.2 requires. z/VM V6.2 will continue to be supported until December 31, 2016, as announced in announcement letter # 914-012.
•Product Delivery of z/VM on DVD/Electronic only: z/VM 6.3 will be the last release of z/VM that will be available on tape. Subsequent releases will be available on DVD or electronically
•Enhanced RACF password encryption algorithm for z/VM: In a future deliverable an enhanced RACF/VM password encryption algorithm is planned. This support will be designed to provide improved cryptographic strength using AES-based encryption in RACF/VM password algorithm processing. This planned design is intended to provide better protection for encrypted RACF password data in the event that a copy of RACF database becomes inadvertently accessible
•z/VM support for single-instruction, multiple-data (SIMD): In a future deliverable IBM intends to deliver support to enable z/VM guests to exploit the Vector Facility for z/Architecture (SIMD)
|
1 All statements regarding IBM plans, directions, and intent are subject to change or withdrawal without notice. Any reliance on these statements of general direction is at the relying party’s sole risk and will not create liability or obligation for IBM.
Table 4-3 summarizes the support requirements of selected functions for the currently supported z/VM releases. In the table, Y (yes) means the function is supported, N (no) means the function is not supported.
|
Important: Any new functions listed as Y for z/VM 6.2 and 6.3 will require service (for both compatibility and exploitation).
|
Table 4-3 z/VM support summary
|
Function
|
V6R3
|
V6R2
|
|
z13
|
Y
|
Y
|
|
Support of up to 64 PUs for single thread
|
Y1
|
N2
|
|
zIIP3
|
Y
|
Y
|
|
1 TB real memory support
|
Y
|
N4
|
|
Large page support
|
N
|
N
|
|
Decimal floating point support for packed decimal numbers
|
Y
|
Y
|
|
Two way simultaneous multithreading (SMT) Support
|
Y
|
N
|
|
Single-instruction, multiple-data (SIMD) support
|
N
|
N
|
|
CPU measurement facility counter
|
Y
|
Y
|
|
HiperDispatch
|
Y
|
N
|
|
CPACF
|
Y
|
Y
|
|
CPACF AES-128, AES-192, and AES-256
|
Y
|
Y
|
|
CPACF SHA-1, SHA-224, SHA-256, SHA-384, SHA-512
|
Y
|
Y
|
|
CPACF protected key
|
Y
|
Y
|
|
Crypto Express5S
|
Y
|
Y
|
|
Secure IBM Enterprise PKCS #11 (EP11) coprocessor mode
|
Y
|
Ye
|
|
Elliptic Curve Cryptography (ECC)5
|
Y
|
Ye
|
|
Common Cryptographic Architecture (CCA) > 16 Domain Support
|
Y
|
Y
|
|
EP 11 Support
|
Y
|
Y
|
|
Flash Express
|
N
|
N
|
|
zEDC Express6
|
Y7
|
N
|
|
Shared 10GbE RoCE (SR-IOV) support8
|
Y
|
N
|
|
High Performance FICON (zHPF) Extended distance9
|
N
|
N
|
|
FICON Express8S
|
Y
|
Y
|
|
FICON Express8
|
Y
|
Y
|
|
FICON Express16S
|
Y
|
Y
|
|
OSA-Express QDIO data connection isolation for z/VM environments
|
Y
|
Y
|
|
OSA-Express5S 10 Gigabit Ethernet LR and SR
CHPID type OSD
|
Y
|
Y
|
|
OSA-Express5S 10 Gigabit Ethernet LR and SR
CHPID type OSX
|
N10
|
Nj
|
|
OSA-Express5S Gigabit Ethernet LX and SX
CHPID type OSD (using two ports)
|
Y
|
Y
|
|
OSA-Express5S 1000BASE-T
CHPID type OSC (using two ports per CHPID)
|
Y
|
Y
|
|
OSA-Express5S 1000BASE-T
CHPID type OSD (using two ports per CHPID)
|
Y
|
Y
|
|
OSA-Express5S 1000BASE-T
CHPID type OSE11 (using one or two ports per CHPID)
|
Y
|
Y
|
|
OSA-Express5S 1000BASE-T
CHPID type OSM
|
Nj
|
Nj
|
|
OSA-Express5S 1000BASE-T
CHPID type OSN (using two ports per CHPID)
|
Y
|
Y
|
|
OSA-Express4S 10 Gigabit Ethernet LR and SR
CHPID type OSD
|
Y
|
Y
|
|
OSA-Express4S 10 Gigabit Ethernet LR and SR
CHPID type OSX
|
Y
|
Y
|
|
OSA-Express4S Gigabit Ethernet LX and SX
CHPID type OSD (using two ports)
|
Y
|
Y
|
|
OSA-Express4S 1000BASE-T
CHPID type OSC (using two ports per CHPID)
|
Y
|
Y
|
|
OSA-Express4S 1000BASE-T
CHPID type OSD (using two ports per CHPID)
|
Y
|
Y
|
|
OSA-Express4S 1000BASE-T
CHPID type OSE (using two ports per CHPID)
|
Y
|
Y
|
|
OSA-Express4S 1000BASE-T
CHPID type OSM
|
Y
|
Y
|
|
OSA-Express4S 1000BASE-T
CHPID type OSN (using two ports per CHPID)
|
Y
|
Y
|
|
Multi-Vswitch Link Aggregation
|
Y
|
N
|
|
Dynamic I/O support for InfiniBand CHPIDs
|
Y
|
Y
|
|
InfiniBand coupling links (12x IFB-SDR or 12x IFB-DDR) at a distance of 150 m
|
Y
|
Y
|
|
InfiniBand coupling links (1x IFB-SDR or 1x IFB-DDR) at an unrepeated distance of 10 km
|
Y
|
Y
|
|
IBM Integrated Coupling Adapter support (ICA)
|
Y
|
Y
|
|
Dynamic I/O support for ICA CHPIDs
|
Y
|
Y
|
|
CFCC Level 20
|
Y
|
Y
|
1 64 cores support without multi-threading and 32 cores with multithreading-2
2 Supports only 32 PU in compatibility mode in z13
3 zAAPs not available on z13
4 Real memory limit is 256 GB
5 Service is required.
6 Minimum firmware bundle level 21
7 For z/OS guest support available through APAR
8 z/OS APAR required for exploiting SR-IOV for running z/OS as a guest in z/VM
9 zHPF(High Performance FICON) support available. But no support for extended distance. Greater than 64 KB writes over 100 KM distance that is used by HyperSwap functions.
10 Only dynamic I/O when z/VM is the controlling LPAR.
11 A CHPID Type OSE supports SNA (LLC2) and IP connectivity over Ethernet (802.3 or DIX V2).
|
z/VM logical partitions: IBM z13 CPs and IFLs have increased capacity over that of their predecessors. Therefore, we suggest that the capacity of z/VM logical partitions and of any guests, in terms of the number of IFLs and CPs (real or virtual), be reviewed and adjusted to achieve the required capacity. Virtual machine shares might also need adjustment.
|
4.2.3 z/VSE
Table 4-4 summarizes the support requirements of selected z13 functions for the currently supported z/VSE releases. In the table, Y (yes) means the function is supported, N (no) means the function is not supported.
Table 4-4 z/VSE support summary
|
Function
|
V5R21
|
V5R1a
|
|
z13
|
Y
|
Y
|
|
Support for up to ten CPs2
|
Y
|
Y
|
|
Large page support for data spaces (2 GB)
|
Y
|
Y
|
|
Simultaneous multithreading (SMT) 2 support
|
N
|
N
|
|
Single-instruction, multiple-data (SIMD) support
|
N
|
N
|
|
CPACF
|
Y
|
Y
|
|
CPACF AES-128, AES-192, and AES-256
|
Y
|
Y
|
|
CPACF SHA-1, SHA-224, SHA-256, SHA-384, SHA-512
|
Y
|
Y
|
|
CPACF protected key
|
N
|
N
|
|
Common Cryptographic Architecture (CCA) > 16 Domain Support3
|
Y4
|
Yd
|
|
Secure IBM Enterprise PKCS #11 (EP11) coprocessor mode
|
N
|
N
|
|
Crypto Express5S toleration
|
Yd
|
Yd
|
|
Elliptic Curve Cryptography (ECC)
|
N
|
N
|
|
FICON Express8S
|
Y
|
Y
|
|
FICON Express8
|
Y
|
Y
|
|
FICON Express16S
|
Y
|
Y
|
|
OSA-Express5S 10 Gigabit Ethernet LR and SR
CHPID type OSD
|
Y
|
Y
|
|
OSA-Express5S 10 Gigabit Ethernet LR and SR
CHPID type OSX
|
Y
|
Y
|
|
OSA-Express5S Gigabit Ethernet LX and SX
CHPID type OSD (using two ports)
|
Y
|
Y
|
|
OSA-Express5S 1000BASE-T
CHPID type OSC (using two ports per CHPID)
|
Y
|
Y
|
|
OSA-Express5S 1000BASE-T
CHPID type OSD (using two ports per CHPID)
|
Y
|
Y
|
|
OSA-Express5S 1000BASE-T
CHPID type OSE5 (using two ports per CHPID)
|
Y
|
Y
|
|
OSA-Express5S 1000BASE-T
CHPID type OSM
|
N
|
N
|
|
OSA-Express5S 1000BASE-T
CHPID type OSN6 (using two ports per CHPID)
|
Y
|
Y
|
|
OSA-Express4S 10 Gigabit Ethernet LR and SR
CHPID type OSD
|
Y
|
Y
|
|
OSA-Express4S 10 Gigabit Ethernet LR and SR
CHPID type OSX
|
Y
|
Y
|
|
OSA-Express4S Gigabit Ethernet LX and SX
CHPID type OSD (using two ports)
|
Y
|
Y
|
|
OSA-Express4S 1000BASE-T
CHPID type OSC (using two ports per CHPID)
|
Y
|
Y
|
|
OSA-Express4S 1000BASE-T
CHPID type OSD (using two ports per CHPID)
|
Y
|
Y
|
|
OSA-Express4S 1000BASE-T
CHPID type OSEe (using two ports per CHPID)
|
Y
|
Y
|
|
OSA-Express4S 1000BASE-T
CHPID type OSM
|
N
|
N
|
|
OSA-Express4S 1000BASE-T
CHPID type OSNf (using two ports per CHPID)
|
Y
|
Y
|
|
HiperSockets Completion Queue for Linux Fast Path function in LPAR
|
Y
|
Y
|
1 z/VSE V5 executes in z/Architecture mode and supports 64-bit real and 64-bit virtual memory addressing. PTF support required for exploitation and compatibility
2 z/VSE Turbo Dispatcher supports up to four CPs and tolerates up to 10-way LPARs
3 Coprocessor and Accelerator mode
4 Support available with PTF
5 A CHPID Type OSE supports both SNA (LLC2) and IP connectivity over Ethernet (802.3 or DIX V2).
6 One port is configured for OSN. The other port is unavailable.
4.2.4 z/TPF
Table 4-5 summarizes the support requirements of selected z13 functions for the currently supported z/TPF release. In the table, Y (yes) means the function is supported, N (no) means the function is not supported.
Table 4-5 TPF and z/TPF support summary
|
Function
|
z/TPF V1R11
|
|
z13
|
Y
|
|
Support for up to 141 PUs
|
Y
|
|
4 TB Real Storage Support
|
Y
|
|
CPACF
|
Y
|
|
CPACF AES-128, AES-192, and AES-256
|
Y2
|
|
CPACF SHA-1, SHA-224, SHA-256
|
Y3
|
|
CPACF protected key
|
N
|
|
Common Cryptographic Architecture (CCA) up to 85 Domain Support
|
Y
|
|
Secure IBM Enterprise PKCS #11 (EP11) coprocessor mode
|
N
|
|
Crypto Express5S
|
Y
|
|
Elliptic Curve Cryptography (ECC)
|
N
|
|
FICON Express16S
|
Y
|
|
FICON Express8S
|
Y
|
|
FICON Express8
|
Y
|
|
OSA-Express5S 10 Gigabit Ethernet LR and SR
CHPID type OSD
|
Y
|
|
OSA-Express5S 10 Gigabit Ethernet LR and SR
CHPID type OSX
|
N
|
|
OSA-Express5S Gigabit Ethernet LX and SX
CHPID type OSD (using two ports)
|
Y
|
|
OSA-Express5S 1000BASE-T
CHPID type OSC (using two ports per CHPID)
|
N
|
|
OSA-Express5S 1000BASE-T
CHPID type OSD (using two ports per CHPID)
|
Y
|
|
OSA-Express5S 1000BASE-T
CHPID type OSE(using two ports per CHPID)
|
N
|
|
OSA-Express5S 1000BASE-T
CHPID type OSM
|
N
|
|
OSA-Express5S 1000BASE-T
CHPID type OSN(using two ports per CHPID)
|
Y
|
|
OSA-Express4S 10 Gigabit Ethernet LR and SR
CHPID type OSD
|
Y
|
|
OSA-Express4S 10 Gigabit Ethernet LR and SR
CHPID type OSX
|
N
|
|
OSA-Express4S Gigabit Ethernet LX and SX
CHPID types OSD (using two ports)
|
Y
|
|
OSA-Express4S 1000BASE-T
CHPID type OSC (using one or two ports per CHPID)
|
N
|
|
OSA-Express4S 1000BASE-T
CHPID type OSD (using two ports per CHPID)
|
Y
|
|
OSA-Express4S 1000BASE-T
CHPID type OSE(using one or two ports per CHPID)
|
N
|
|
OSA-Express4S 1000BASE-T
CHPID type OSM
|
N
|
|
OSA-Express4S 1000BASE-T
CHPID type OSN (using one or two ports per CHPID)
|
Y
|
|
Coupling over InfiniBand
CHPID type CIB
|
Y4
|
|
IBM Integrated Coupling Adapter (ICA)
|
Y
|
|
CFCC Level 20
|
Y
|
1 PTF support required
2 Supports only AES-128 and AES-256.
3 Supports only SHA-1 and SHA-256.
4 Compatibility is supported.
4.2.5 Linux on z Systems
Linux on z Systems distributions are built separately for the 31-bit and 64-bit addressing modes of the z/Architecture. The newer distribution versions are built only for 64-bit. You can run 31-bit applications in the 31-bit emulation layer on a 64-bit Linux on z Systems distribution.
None of the current versions of Linux on z Systems distributions (SUSE: SLES 11,SLES 12; Red Hat: RHEL 5, RHEL 6, RHEL 7) require toleration support; therefore, any release of these distributions can run on the z13.
Table 4-6 lists the most recent service levels of the current SUSE and Red Hat supported to run on IBM z13.
Table 4-6 Current Linux on z Systems distributions, by z/Architecture mode
|
Linux distribution
|
z/Architecture (64-bit mode)
|
|
SLES 11
|
Yes
|
|
SLES 12
|
Yes
|
|
RHEL 7
|
Yes
|
|
RHEL 6
|
Yes
|
Table 4-7 lists selected z13 features, showing the minimum level of SUSE and Red Hat distributions that support each feature.
Table 4-7 Linux on z Systems support summary
|
Function
|
SUSE
|
Red Hat
|
|
z13
|
SLES 12
SLES 11
|
RHEL 7
RHEL 6
|
|
Maximum number of CPs or IFLs
|
64/2561
|
64/256a
|
|
Large page support
|
SLES 12
SLES 11
|
RHEL 7
RHEL 6
|
|
Decimal floating point for Packed decimal numbers
|
No
|
No
|
|
CPACF
|
SLES 12
SLES 11
|
RHEL 7
RHEL 6
|
|
CPACF AES-128, AES-192, and AES-256
|
SLES 12
SLES 11
|
RHEL 7
RHEL 6
|
|
CPACF SHA-1, SHA-224, SHA-256, SHA-384, SHA-512
|
SLES 12
SLES 11
|
RHEL 7
RHEL 6
|
|
CPACF protected key
|
Yes2
|
Yesb
|
|
Secure IBM Enterprise PKCS #11 (EP11) coprocessor mode
|
SLES 11,123
|
RHEL 6,7c
|
|
Crypto Express5S4
|
SLES 12
SLES 11 SP3
|
RHEL 7
RHEL 6.6
|
|
Elliptic Curve Cryptography (ECC)
|
Yesb
|
Yesb
|
|
Common Cryptographic Architecture (CCA) > 16 domain support
|
SLES 12
SLES 11 SP3
|
RHEL 7
RHEL 6.6
|
|
HiperSockets Completion Queue
|
SLES 12
SLES 11
|
RHEL 7
RHEL 6
|
|
HiperSockets Virtual Switch Bridge
|
SLES 12
SLES 11
|
RHEL 7
RHEL 6
|
|
HiperSockets Layer 2 support
|
SLES 12
SLES 11
|
RHEL 7
RHEL 6
|
|
Shared 10GbE RoCE (SR-IOV) Express
|
No
|
No
|
|
High Performance FICON (zHPF) extended distance
|
No
|
No
|
|
Simultaneous multithreading 2 Support (SMT-2) support
|
SLES 12
|
RHEL 7
|
|
Single-instruction, multiple-data (SIMD) support
|
SLES 12
|
RHEL 7
|
|
zFlash Express
|
SLES 12
SLES 11 SP3
|
RHEL 7
RHEL 6.4
|
|
zEDC Support
|
No
|
No
|
|
IBM zAware Support
|
SLES 12
SLES 11
|
RHEL 7
RHEL 6
|
|
FICON Express8S
CHPID type FC and FCP
|
SLES 12
SLES 11
|
RHEL 7
RHEL 6
|
|
FICON Express8,
CHPID types FC and FCP
|
SLES 12
SLES 11
|
RHEL 7
RHEL 6
|
|
FICON Express16S
CHPID type FC and FCP
|
SLES 12
SLES 11
|
RHEL 7
RHEL 6
|
|
OSA-Express5S 10 Gigabit Ethernet LR and SR
CHPID type OSD
|
SLES 12
SLES 11
|
RHEL 7
RHEL 6
|
|
OSA-Express5S 10 Gigabit Ethernet LR and SR
CHPID type OSX
|
SLES 12
SLES 11 SP15
|
RHEL 7
RHEL 6
|
|
OSA-Express5S Gigabit Ethernet LX and SX
CHPID type OSD (using two ports)
|
SLES 12
SLES 11
|
RHEL 7
RHEL 6
|
|
OSA-Express5S 1000BASE-T
CHPID type OSC (using one or two ports per CHPID)
|
No
|
No
|
|
OSA-Express5S 1000BASE-T
CHPID type OSD (using two ports per CHPID)
|
SLES 12
SLES 11
|
RHEL 7
RHEL 6
|
|
OSA-Express5S 1000BASE-T
CHPID type OSE6 (using one or two ports per CHPID)
|
No
|
No
|
|
OSA-Express5S 1000BASE-T
CHPID type OSM
|
SLES 12
SLES 11 SP2
|
RHEL 7
RHEL 6
|
|
OSA-Express5S 1000BASE-T
CHPID type OSN (using two ports per CHPID)
|
SLES 12
SLES 11
|
RHEL 7
RHEL 6
|
|
OSA-Express4S 10 Gigabit Ethernet LR and SR
CHPID type OSD
|
SLES 12
SLES 11
|
RHEL 7
RHEL 6
|
|
OSA-Express4S 10 Gigabit Ethernet LR and SR
CHPID type OSX
|
SLES 12
SLES 11 SP1c
|
RHEL 7
RHEL 6
|
|
OSA-Express4S Gigabit Ethernet LX and SX
CHPID type OSD (using two ports)
|
SLES 12
SLES 11
|
RHEL 7
RHEL 6
|
|
OSA-Express4S 1000BASE-T7
CHPID type OSD (using two ports per CHPID)
|
SLES 12
SLES 11
|
RHEL 7
RHEL 6
|
|
OSA-Express4S 1000BASE-Te
CHPID type OSM
|
SLES 12
SLES 11 SP3
|
RHEL 7
RHEL 6
|
|
OSA-Express4S 1000BASE-Te
CHPID type OSN (using two ports per CHPID)
|
SLES 12
SLES 11
|
RHEL 7
RHEL 6
|
1 SLES12 and RHEL7 supports 256 PUs and SLES11 and RHEL6 support 64 PUs. SLES and RHEL support 64 PUs when running as a guest under z/VM without multithreading and 32 PUs with multithreading.
2 Through CCA host library
3 Requires EP11 host library
4 CEX5S toleration mode support
5 Maintenance update required.
6 A CHPID Type OSE supports both SNA (LLC2) and IP connectivity over Ethernet (802.3 or DIX V2).
7 Not available on zBC12.
IBM is working with its Linux distribution partners so that use of further IBM z13 functions are provided in future Linux on z Systems distribution releases. We suggest the following updates:
•Use SLES 12 or RHEL 7 in any new projects for the z13.
•Update any Linux distributions to their latest service level before migration to z13.
•Adjust the capacity of any z/VM or Linux logical partitions, and of any z/VM guests, in terms of the number of IFLs and CPs, real or virtual, in face of the increased processor unit (PU) capacity of the z13.
4.2.6 References
Planning information for each operating system is available on the following support websites:
•z/OS:
•z/VM:
•z/TPF:
•z/VSE:
•Linux on z Systems:
4.3 Software support for zBX Model 004
IBM z BladeCenter Extension (zBX) Model 004 is available as an upgrade from an existing zBX Model 002 or Model 003. The following operating systems would be supported on zBX Model 004:
•AIX (on POWER7 blade located in IBM BladeCenter Extension Model 004):
AIX 5.3, AIX 6.1 and AIX 7.1 and subsequent releases and PowerVM Enterprise Edition
•Linux on System x (on IBM BladeCenter HX5 blade installed in zBX Model 004):
RHEL 5.5 and later, 6.0 and later, RHEL 7.0 and later, SLES 10 (SP4) and later, SLES 11 (SP1) and later, SLES 12 and later (64-bit only)
•Microsoft Windows (on IBM BladeCenter HX5 blades installed in zBX Model 004)
Microsoft Windows Server 2012, Microsoft Windows Server 2012 R2, Microsoft Windows Server 2008 R2 and Microsoft Windows Server 2008, SP2 (Datacenter Edition suggested) 64 bit only
4.4 z/OS considerations
IBM z13 base processor support is required in z/OS. With that exception, software changes do not require the new z13 functions and, equally, the new functions do not require functional software. The z/OS approach is to (where applicable) automatically decide to enable or disable a function that is based on the presence (enable) or absence (disable) of the required hardware and software.
General recommendations
The z13 introduces the latest z Systems technology; notable cases are Flash Express, zEDC Express,10GbE RoCE Express support, simultaneous multithreading (SMT), and single-instruction, multiple-data (SIMD) processing. Although support for z13 is provided by z/OS, starting with z/OS V1R12, the use of z13 functions depends on the z/OS release.
In general, we suggest the following approaches:
•Do not migrate software releases and hardware at the same time.
•Keep members of the sysplex at the same software level other than during brief migration periods.
•Migrate to a Server Time Protocol (STP)-only Coordinated Timing Network (CTN) before introducing a z13 into a Sysplex.
•Review z13 restrictions and considerations before creating an upgrade plan.
Flash Express
z13 supports the Flash Express feature, also available on the zEC12 and BC12, which can help improve resilience and performance of the z/OS system. Flash Express is designed to assist with the handling of workload spikes or increased workload demand that might occur at the opening of the business day, or in the event of a workload shift from one system to another.
z/OS is the first exploiter to use Flash Express storage as Storage Class Memory (SCM) for paging store and SAN Volume Controller dump. SAN Volume Controller dump-data capture time is expected to be substantially reduced. As a paging store, Flash Express storage is suitable for workloads that can tolerate paging and does not benefit workloads that cannot afford to page. The z/OS design for Flash Express storage does not completely remove the virtual storage constraints that are created by a paging spike in the system.
Flash Express storage is allocated to a logical partition, similar to main memory. The initial and maximum amount of Flash Express Storage that is available to a particular logical partition is specified at the SE or HMC through a new flash memory allocation panel.
The amount of Flash Express storage in the partition can be changed dynamically, between the initial and the maximum amount at the SE or HMC. For z/OS, this can also be done by an operator command. Each partition’s Flash Express storage is isolated similarly to main storage and each partition sees only its own space in the flash memory space.
Flash express feature is enhanced to support pageable large (1 MB) pages. Also, coupling facility (CF) support for Flash Express for certain list structures (IBM WebSphere MQ for z/OS Version 7) is enabled with PTF support.
zEnterprise Data Compression (zEDC) Express
zEDC Express, an optional feature available for zEC12,zBC12 and z13, addresses data growth requirements by providing hardware-based acceleration for data compression and decompression. zEDC provides data compression with lower CPU consumption than previously existing compression technology on z Systems.
The z/OS V2R1 zEnterprise Data Compression capability exploits zEDC Express and has the following minimum requirements:
•z/OS V2R1 with PTFs and the zEDC for z/OS feature
•z/OS V1R13 with PTFs (software decompression support only, no compression)
•z/OS V1R12 with PTFs (software decompression support only, no compression)
Initial exploiters included the following use cases.
•SMF archive data, compressed using zEDC, provided substantial benefit to increase the amount of data kept online.
•zSecure product output size of monitor and unload files reduced giving substantial media savings benefit.
•z/OS SAN Volume Controller and stand-alone memory dumps might be stored in up to 5X less space.
Support for DFSMS (BSAM/QSAM) is enabled, providing a new type of policy-based compression support for non-VSAM extended format data sets.
zIIP support
Starting with z13, no more IBM System z Application Assist processor (zAAP) is available. IBM z Integrated Information Processor (zIIP) will be able to drive zAAP eligibe workload too. A maximum of two zIIPs per one CP can be installed.
Because z/VM can dispatch virtual zIIPs on real CPs1, the z/VM partition does not require any real zIIPs defined to it. However, in general, real zIIPs should be used due to software licensing reasons.
Large page support
On z/OS, memory that is reserved for large page support needs to be defined in the IEASYSxx member of SYS1.PARMLIB. The definition cannot be dynamically changed.
HiperDispatch
HiperDispatch uses the new core-cache design, the new chip-cache design, and the new node and drawer-cache design of the z13 to increase the number of instructions per cycle.
On z/OS, a parameter of the IEAOPTxx member of SYS1.PARMLIB controls whether HiperDispatch is enabled or disabled for the z/OS image. It can be dynamically changed, without an initial program load (IPL) or any outage. The default is that HiperDispatch is enabled.
To use HiperDispatch effectively, adjustment of defined Workload Manager (WLM) goals and policies might be required. We suggest that WLM policies and goals are reviewed and updated as necessary, mainly after a migration to a new server or any important change on the system.
A health check is provided to verify whether HiperDispatch is enabled on z13
Capacity provisioning
Installation of the capacity provision function on z/OS requires completion of the the following prerequisite tasks:
1. Setting up and customizing z/OS RMF, including the Distributed Data Server (DDS)
2. Setting up the z/OS CIM Server (a z/OS base element with z/OS V1R9 and later)
3. Performing capacity provisioning customization as described in the z/OS MVS Capacity Provisioning User’s Guide , SC33-8299
Use of the capacity provisioning function requires the following elements:
•TCP/IP connectivity to observed systems
•TCP/IP connectivity from the observing system to the HMC of observed systems
•IBM Resource Measurement Facility (RMF) Distributed Data Server must be active
•Common Information Model (CIM) Server must be active
•Security and CIM customization
•Capacity Provisioning Manager customization
In addition, the Capacity Provisioning Control Center must be downloaded from the host and installed on a personal computer (PC) workstation. This application is only used to define policies. It is not required to manage operations.
Customization of the capacity provisioning function is required on the operating system that observes other z/OS systems in one or multiple sysplexes. See the following resources:
•For a description of the capacity provisioning domain, see z/OS MVS Capacity Provisioning User’s Guide , SC33-8299.
•For more details about capacity provisioning, see IBM System z10 Enterprise Class Capacity On Demand, SG24-7504.
Integrated Cryptographic Service Facility (ICSF)
Integrated Cryptographic Service Facility (ICSF) is a base component of z/OS. It is designed to transparently use the available cryptographic functions, whether CPACF or Crypto Express features, to balance the workload and help address the applications’ bandwidth requirements.
Despite being a z/OS base component, ICSF new functions are generally made available through a web deliverable support a couple of months after a new z/OS release is launched. Because of this fact, new functions must be related to an ICSF function modification identifier (FMID) instead of a z/OS version.
For a table that lists ICSF FMIDs and web-deliverable codes for z/OS V1R10 through V2R1, see IBM zEnterprise EC12 Technical Guide, SG24-8049. Later FMIDs include the functions of previous ones.
The Cryptographic Support for z/OS V1R13-z/OS-V2R1 web deliverable (ICSF FMID HCR77B0) is required to use the new functions that are available with the z13. Crypto Express5S toleration is available through maintenance at ICSF FMID HCR7780 or higher.
Coupling links
Each system can use, or not use, Internal coupling links, InfiniBand coupling links or Integrated Coupling Adapter (ICASR) coupling links independently of what other systems are doing. IBM z13 does not support participating in a Parallel Sysplex with System z10 and earlier systems.
Coupling connectivity is available only when other systems also support the same type of coupling. When you plan to use the InfiniBand coupling or ICA SR coupling links technology, we suggest that you consult the Coupling Facility Configuration Options white paper at the following web page:
z/OS XL C/C++ considerations
z/OS V2R1 with program temporary fixes (PTFs) or newer is required to be able to use the most recent level (11) of the following two C/C++ compiler options:
•ARCHITECTURE: This option selects the minimum level of machine architecture on which the program runs. Certain features that are provided by the compiler require a minimum architecture level. ARCH(11) uses instructions that are available on the z13.
•TUNE: This option allows optimization of the application for a specific machine architecture, within the constraints that are imposed by the ARCHITECTURE option. The TUNE level must not be lower than the setting in the ARCHITECTURE option.
For more information about the ARCHITECTURE and TUNE compiler options, see z/OS V2R1.0 XL C/C++ User’s Guide, SC14-7307.
|
C/C++: A C/C++ program that is compiled with the ARCH(11) or TUNE(11) options runs only on z13. Otherwise, an operation exception results. This is a consideration for programs that might need to run on servers of various levela during development, test, production, and fallback or disaster recovery.
|
IBM z Advanced Workload Analysis Reporter (IBM zAware)
With IBM zEnterprise EC12 and BC12, IBM introduced a new technology, IBM zAware, employing analytic algorithms based on machine learning developed by IBM Research.
The new version of IBM zAware introduces a new generation of technology with improved analytics to reduce false positives and provide better results. The previous version required messages with message ID (for example, z/OS and other IBM software). In the improved implementation, IBM zAware can process message streams that do not have message IDs (Linux operating system).
IBM zAware uses near real-time continuous learning algorithms, providing a diagnostics capability that is intended to help you quickly pinpoint problems, which in turn, can help you to more rapidly address service disruptions. IBM zAware uses analytics to intelligently examine z/OS console messages and Linux system log to find unusual patterns, inconsistencies, and variations.
Large z/OS operating system environments can sometimes generate more than 25 million messages per day. This can make manual analysis time-consuming and error-prone when exceptional problems occur. IBM zAware provides a simple graphical user interface (GUI) to help you find message anomalies quickly, which can help speed problem identification.
|
IBM zAware and z/VM: IBM intends to deliver IBM z Advanced Workload Analysis Reporter (IBM zAware) support for z/VM. This future release of IBM zAware is intended to help identify unusual behaviors of workloads running on z/VM in order to accelerate problem determination and improve service levels.
|
4.5 Coupling facility and CFCC considerations
Coupling facility connectivity to a z13 is supported on the zEC12, zBC12, z196, z114, or another z13. The logical partition running the Coupling Facility Control Code (CFCC) can be located on any of these supported systems.
Up to 141 ICF engines can be ordered on a single z13 server across multiple coupling facility LPARs. This helps environments that use server hosting multiple coupling facilities to support multiple Parallel Sysplexes. The limit is still 16 ICF engines for a single coupling facility LPAR. Because coupling link connectivity to System z10 and previous systems is not supported, this might affect the introduction of z13 into existing installations and require more planning. For more information, see the IBM z13 Technical Guide, SG24-8251.
z13 supports CFCC Level 20. To support migration from one CFCC level to the next, different levels of CFCC can be run concurrently if the Coupling Facility logical partitions are running on different central processor complexes (CPCs). CF logical partitions running on the same CPC share the CFCC level.
CFCC exploitation Flash Express for WebSphere MQ
CFCC Level 19 and later can use the full functionality of the Flash Express feature to help handle the overflow of WebSphere MQ shared queues. Overflow areas for certain Coupling Facility list structures can be provided by the Flash Express feature. This is designed to allow structure data to be migrated to Flash Express memory as needed and migrated back to real memory to be processed. This requires WebSphere MQ for z/OS V7, running on z/OS V2R1 or V1R13, with additional service.
CFCC Coupling Thin Interrupts
The Coupling Thin Interrupts enhancement, delivered with CFCC 19, improves the performance of a coupling facility partition. It also improves the dispatching of z/OS LPARS awaiting the arrival of a returned asynchronous CF requests, when used in a shared engine environment.
CFCC large memory support
CFCC Level 20 supports coupling facility use of large memory with improved availability for larger CF cache structures and data sharing performance with larger DB2 group buffer pools (GBP). This support removes inhibitors to using large CF structures, enabling use of large memory to appropriately scale to larger DB2 local buffer pools (LBP) and group buffer pools (GBP) in data sharing environments.
CFCC support 256 CHPIDs
|
•At the time of this writing IBM plans to support up to 256 coupling CHPIDs on z13, that is twice the 128 coupling CHPIDs supported on zEC12. This provides enhanced connectivity and scalability for a growing number of coupling channel types and facilitates consolidation of multiple sysplexes into the same set of physical servers.
•Each CF image will continue to support a maximum of 128 coupling CHPIDs.
|
1 All statements regarding IBM plans, directions, and intent are subject to change or withdrawal without notice. Any reliance on these statements of general direction is at the relying party’s sole risk and will not create liability or obligation for IBM.
For more information about CFCC code levels, see the Parallel Sysplex website:
For the recommended levels see the current exception letter published on Resource Link:
4.6 Input/output configuration program (IOCP) considerations
All z Systems require a description of their I/O configuration. This description is stored in input/output configuration data set (IOCDS) files. The input/output configuration program (IOCP) allows creation of the IOCDS file from a source file that is known as the input/output configuration source (IOCS).
The IOCS file contains detailed information for each channel and path assignment, each control unit, and each device in the configuration.
The required level of IOCP for z13 is V5 R1 L0 (IOCP 5.1.0) or later with PTF. For details, see z Systems Input/Output Configuration Program User's Guide for ICP IOCP, SB10-7136-00.
4.7 GDPS Virtual Appliance
Deploying IT environments based on IBM z Systems that are running only Linux on z Systems is typical. The GDPS Virtual Appliance is a building block of high availability and disaster recover solutions for those environments that do not have and do not require z/OS skills.
|
Statement of Direction1: In the first half of 2015, IBM intends to deliver a GDPS/Peer to Peer Remote Copy (GDPS/PPRC) multiplatform resiliency capability for customers who do not run the z/OS operating system in their environments. This solution is intended to provide IBM z Systems customers who run z/VM and their associated guests, for instance, Linux on z Systems, with similar high availability and disaster recovery benefits to those who run on z/OS. This solution will be applicable for any IBM z Systems announced after and including the zBC12 and zEC12.
|
1 All statements regarding IBM plans, directions, and intent are subject to change or withdrawal without notice. Any reliance on these statements of general direction is at the relying party’s sole risk and will not create liability or obligation for IBM.
GDPS Virtual Appliance is a fully integrated continuous availability and disaster recovery solution for Linux on z Systems customers and which consists of these items:
•An operating system image2
•The application components
•An appliance management layer which makes the image self-containing
•An API and UI for customization, administration, and operation tailored for the appliance function.
The GDPS Virtual Appliance is designed to improve both consumability and time-to-value for customers. It implements the GDPS/PPRC Multiplatform Resilience for z Systems, also known as xDR. xDR coordinates near-continuous availability and DR solution by these methods:
•Disk error detection
•Heartbeat for sanity checks
•Using IPL again in place
•Coordinated site takeover
•Coordinated HyperSwap
•Single point of control
Although the GDPS Virtual Appliance is supported with z/VM V5R4 or later, on IBM z13 z/VM, V6R2 or later is required.
For more information, see the IBM z13 Technical Guide, SG24-8251.
1 The z/VM system administrator can use the SET CPUAFFINITY command to influence the dispatching of virtual specialty engines on CPs or real specialty engines.
2 GDPS Virtual Appliance operating system image requires 1 LPAR with one logical CP to run.
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.