1
Let’s Get z/OS Up and Running on the
IBM z16!
Marna WALLE
IBM z/OS Development
mwalle@us.ibm.com
March 8, 2022

© 2023 IBM Corporation
Trademarks
2
Notes:
Performance is in Internal Throughput Rate (ITR) ratio based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput that any user will experience will vary depending upon
considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve
throughput improvements equivalent to the performance ratios stated here.
IBM hardware products are manufactured from new parts, or new and serviceable used parts. Regardless, our warranty terms apply.
All customer examples cited or described in this presentation are presented as illustrations of the manner in which some customers have used IBM products and the results they may have achieved. Actual environmental costs and
performance characteristics will vary depending on individual customer configurations and conditions.
This publication was produced in the United States. IBM may not offer the products, services or features discussed in this document in other countries, and the information may be subject to change without notice. Consult your local IBM
business contact for information on the product or services available in your area.
All statements regarding IBM's future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only.
Information about non-IBM products is obtained from the manufacturers of those products or their published announcements. IBM has not tested those products and cannot confirm the performance, compatibility, or any other claims related to
non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.
Prices subject to change without notice. Contact your IBM representative or Business Partner for the most current pricing in your geography.
This information provides only general descriptions of the types and portions of workloads that are eligible for execution on Specialty Engines (e.g, zIIPs, zAAPs, and IFLs) ("SEs"). IBM authorizes customers to use IBM SE only to execute
the processing of Eligible Workloads of specific Programs expressly authorized by IBM as specified in the “Authorized Use Table for IBM Machines” provided at www.ibm.com/systems/support/machine_warranties/machine_code/aut.html
(“AUT”). No other workload processing is authorized for execution on an SE. IBM offers SE at a lower price than General Processors/Central Processors because customers are authorized to use SEs only to process certain types and/or
amounts of workloads as specified by IBM in the AUT.
* Registered trademarks of IBM Corporation
Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries.
Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in the United States, other countries, or both and is used under license therefrom.
IT Infrastructure Library is a Registered Trademark of AXELOS Limited.
ITIL is a Registered Trademark of AXELOS Limited.
Linear Tape-Open, LTO, the LTO Logo, Ultrium, and the Ultrium logo are trademarks of HP, IBM Corp. and Quantum in the U.S. and other countries.
Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States
and other countries.
The registered trademark Linux® is used pursuant to a sublicense from the Linux Foundation, the exclusive licensee of Linus Torvalds, owner of the mark on a worldwide basis.
Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.
OpenStack is a trademark of OpenStack LLC. The OpenStack trademark policy is available on the OpenStack website.
Red Hat®, JBoss®, OpenShift®, Fedora®, Hibernate®, Ansible®, CloudForms®, RHCA®, RHCE®, RHCSA®, Ceph®, and Gluster® are trademarks or registered trademarks of Red Hat, Inc. or its subsidiaries in the United States and other
countries.
RStudio®, the RStudio logo and Shiny® are registered trademarks of RStudio, Inc.
UNIX is a registered trademark of The Open Group in the United States and other countries.
VMware, the VMware logo, VMware Cloud Foundation, VMware Cloud Foundation Service, VMware vCenter Server, and VMware vSphere are registered trademarks or trademarks of VMware, Inc. or its subsidiaries in the United States
and/or other jurisdictions.
Zowe™, the Zowe™ logo and the Open Mainframe Project™ are trademarks of The Linux Foundation.
Other product and service names might be trademarks of IBM or other companies.
Parallel Sysplex*
z14
Z15
z16
FICON*
GDPS*
HyperLink
IBM*
IBM Cloud Paks
ibm.com*
IBM logo*
IBM Z*
z/OS*
z/VM*
z/VSE*

Agenda ▪IBM z16 functions & features
▪z/OS support by release
▪Installing z/OS PTFs for IBM z16
▪Upgrade considerations
• General
• IBM z16 upgrade considerations
• Sysplex and Multisystem considerations
▪Exploitation considerations for select
functions
▪Summary

© 2022 IBM Corporation
4
IBM z16 (3931) Model A01 Functions & Features
(z/OS support in blue)
One hardware model, Five Features, 1-4 19” Frame
System
Up to 85 user partitions, 32 TB per partition, 200
CPUs/zIIPs/IFLs per partition, up to 224 PUs
• Up to 16 TB per z/OS LPAR with z/OS V2.5
•2 CP chips on a Dual Chip Module (DCM), 5.4 GHz
•L1 Private 128K i & 128K d
•-L2 n/a
•L3 Shared 32 MB / core, 192 MB effective shared
•L4 n/a
256 GB HSA, 40 TB maximum, 10 TB per drawer
Channel Subsystem scalability
•Up to six (6) Channel Sub Systems (CSSs)
• 4 Subchannel Sets per CSS
HiperDispatch Enhancements
IBM Z Integrated Accelerator for AI
Hardware Instrumentation Services (CPUMF)
New machine instructions
Crypto Express8S
OSA Express7S 1.2
IBM System Recovery Boost
Coupling Express2 LR 10Gb (CX6-DX) PCIe
adapter
CF Level 25
•Retry buffers for cache and lock commands
•Cache residency time metrics
•Scalability improvements
•Request latency/performance improvements
ICA-SR 1.1
Max ICA SR per CEC 48 adapters/96ports (same
as z15)
Max ICP CHPIDs per CEC – 64
10 GbE and 25 GbE RoCE Express 3 SR and LR
(CX6-DX)
FICON Express 32S
zHyperLink® Express1.1
• Maximum 16 Adapters /32 ports
IBM Flexible Capacity for Cyber Resilience

z/OS support summary
Release
z10 EC
z10 BC
WdfM
z196
z114
WdfM
zEC12
zBC12
WdfM
z13
Z13s
WdfM
z14
z14 ZR1
WdfM
z15 T01
z15 T02 z16
End of
Service
Extended
Defect
Support (1)
z/OS V2.11 X X X X X X 9/18 9/21
z/OS V2.21 X X X X X X X 9/20 9/23 (*)
z/OS V2.3 X X X X X 9/22 (*) 9/25 (*)
z/OS V2.4 X X X X X 9/24 (*) 9/27 (*)
z/OS V2.5 X X X X 9/26 (*) 9/29 (*)
z/OS 3.1 X X X 9/28 (*) 9/31 (*)
Notes:
(1) The IBM Software Support Services offering provides the ability for customers to purchase extended defect support service for those z/OS releases
which are end of service.
(*) Planned. All statements regarding IBM's plans, directions, and intent are subject to change or withdrawal without notice.
WdfM – Server has been withdrawn from Marketing
IBM Software Support Services required for
z/OS support
Supported
Not supported
Legend

Supported z/OS releases on IBM z16
• IBM z16 capabilities differ depending on z/OS release
• Toleration support
• z/OS V2.2 + PTFs (Must have IBM Software Support Services offering purchased)
• z/OS V2.2 September 2020 was End of Service.
• Exploitation support on z/OS:
• z/OS V2.3 + PTFs
• Exploitation support of select functions
• z/OS V2.4 + PTFs
• Exploitation support of more select functions
• z/OS V2.5 + PTFs, and z/OS 3.1
• Even more exploitation

PSP Buckets and Fix Categories (FIXCATs)
▪z/OS general information in the HW PSP bucket:
• Documented in PSP Bucket: Upgrade = 3931DEVICE, Subset = 3931/ZOS
• Base support is provided by PTFs identified by:
• IBM.Device.Server.z16-3931.RequiredService
• Exploitation of many functions is provided by PTFs identified by:
• IBM.Device.Server.z16-3931.Exploitation
• Recommended service is identified by:
• IBM.Device.Server.z16-3931.RecommendedService
Fixes that are required to run z/OS
on the IBM z16 servers.
You must have these PTFs installed.
Fixes that are required to exploit
the capabilities of the IBM z16
server.. Only necessary to install
if you are exploiting the function.
Fixes that are recommended to run z/OS on the IBM z16
server. These fixes are also listed in the Recommended
Service section of the hardware PSP bucket. They
represent fixes that have been recommended by IBM
Service. It is recommended that you review and install
these PTFs.
To easily find the PSP buckets on the internet, search on “3931DEVICE z/OS”.

Common questions
Answers: Not all the PTFs are documented in the z16
PSP bucket. Only the Recommended PTFs can be
found in the PSP bucket, as the IBM Service process can
only include them automatically.
The PSP bucket does not include the Required or
Exploitation PTFs, and only references the SMP/E
FIXCATs.
In fact, it is strongly recommended that you use only
SMP/E FIXCATs to verify that you have all categories of
PTFs installed on your system.
SMP/E FIXCAT process is far easier and more accurate
than the manual verification you’d need to do for PTF
verification from the PSP bucket.
Should I use the
z16 PSP bucket to
find the PTFs that I
need for z/OS?
Why aren’t all the
z/OS PTFs
documented in the
PSP bucket?

Using SMP/E REPORT MISSINGFIX
REPORT MISSINGFIX command identifies fixes associated with particular fix categories that have not yet been
installed and identifies whether any SYSMODs are available to satisfy those missing fixes
1. Get the latest Enhanced HOLDDATA
• Included when you use RECEIVE ORDER
• You can also download it from the Enhanced HOLDDATA site
• This site uses ftp, which is not commonly supported in several browsers
• http://service.software.ibm.com/holdata/390holddata.html#download
2. Sample Command to identify missing fixes for Required, Exploitation and Recommended service.
SET BDY(GLOBAL) .
REPORT MISSINGFIX ZONES(target_zone)
FIXCAT(IBM.Device.Server.z16*).

General upgrade reminders
▪z/OS does not require an IBM z16
▪Install all z/OS z16 service prior to upgrading your hardware
▪ IBM z16 only requires software identified as Required
▪ Note sysplex consideration: Install all Required PTFs before introducing z16, either as z/OS or CF image.
▪ IBM z16 does not require any Exploitation software
▪ Note sysplex consideration: Before exploiting a z16 sysplex function, Install all Exploitation PTFs on all z/OS images.
▪ z/OS z16 Recommended service should be reviewed to see if you need it.
▪New ! ICSF support for z16 is provided with PTFs, not Web deliverables.
▪ PTFs will be appropriately categorized into Required, Exploitation, and Recommended.
▪ Much easier now, for installing and identifying ICSF support
▪Recommendations:
• Avoid upgrading to new software releases and servers at the same time
• Keep quantity of change smaller
• Less-complex back out, if you do need to back out
• Review restrictions and upgrade considerations when creating your upgrade plan

IBM z16 z/OS upgrade material
To find the complete z/OS z16 upgrade information, use one of the following:
1. z/OS z16 Upgrade Workflow for z/OSMF, provided with APAR OA62703 on V2.2 and higher
• Only contains the z/OS steps for upgrading to z16
• Installs into the /usr/lpp/bcp/upgrade directory, file z16_zOS_Upgrade_Workflow.xml
• Recommended format as z/OSMF offers interactive assistance, and will run associated health
checks.
• Updates will be marked with FIXCAT IBM.Device.Server.z16-3931.RequiredService
2. z/OS z16 Upgrade Workflow Exported format
• Single flat file, HTML format, to be found on IBM Documentation website
• For those that don’t wish to use z/OSMF, but no interactive assistance
• Identical content to the z/OS z16 Upgrade Workflow for z/OSMF
3. z/OS V2.5 Upgrade Workflow for z/OSMF, step “Upgrade to an IBM z16 server”
• Identical to the z/OSMF workflow, but has been imbedded into the whole z/OS V2.5 release
upgrade workflow

Unsupported features on IBM
z16 servers
▪ Following hardware features cannot be ordered or
carried forward to IBM z16 servers:
• Prepaid On/Off Capacity on Demand (On/Off CoD)
temporary CP resource tokens do not carry
forward.
• Internal Battery Feature (IBF), which is an internal
short term uninterruptible power supply (UPS).
• Use of the Transport Layer Security protocol
versions 1.0 (TLS 1.0) and version 1.1 (TLS 1.1)
for establishing secure connections to the Support
Element (SE), Hardware Management Console
(HMC), and Open Systems Adapter (OSA)
Integrated Console Controller (channel path type
OSC).
• RoCE Express (CX3). SMC-R connections needs
to be upgraded to use function type ROCE-2.
• FICON Express 16S, FICON Express 8S, FICON
Express32
• Coupling Express LR (CX3), needs to be upgraded
to Coupling Express2 LR (CX6-DX)
• Crypto Express 5S
• OSA Express 5S, OSA Express 7S 25 Gigabit
Ethernet SR
• Container Hosting Foundation, feature code 0104

IOCP (I/O Configuration
Program) for IBM z16
IOCP provides support for:
• IBM z16 base machine definition: Machine type 3931,
model A01.
• Including support for:
• Requiring all PCHIDs on the same FICON adapter be
the same CHPID type.
• Prevents the mixing of FICON (FC) and FICON
Channel Protocol (FCP) channels on the same
FICON adapter .
• Removal of OSA-Express CHPID type OSM, FID type
ROCE.
▪PTFs for APAR OA60286 provided on all z/OS releases:
▪ z/OS V2.4 and older releases use the same IOCP FMID
HIO1104
▪ z/OS V2.5 uses IOCP FMID HIO1105
▪For IBM z16, it is required to have a new IBM z16 IOCDS
written when migrating from a prior generation (z15 or z14).
▪Updated publication:
▪ IOCP User’s Guide – SB10-7172

HCD support for IBM z16
• IBM z16 base machine definition and activation support
• Machine type 3931. model A01
• No support for PCIe function type ROCE. Any SMC-R connections
needs to be upgraded to use function type ROCE-2.
• You can now define up to 24 RoCE Express (from 16)
adapters (48 ports) using function type ROCE-2
• No support for OSA-Express CHPID type OSM.
• Remove before migrating a configuration to IBM z16.
• Any CHPID mix of FICON (FC) and Fiber Channel Protocol (FCP)
channel on the same adapter will now result in a production IODF
build error.
• Separate such channels on to different adapters, using HCD
or the CHPID mapping tool. APAR OA59076 is required to
write an IOCDS on a IBM z16.
• Support is provided on z/OS V2.2 and later.
• IBM z16 hardware can be defined on any supported z/OS version
and server
• Dynamic activation is supported on the IBM z16 server and for an
IBM z16 stand-alone coupling facility.
• Note: HCD PTF needs to be installed on all systems used for
HCD definition and activation.
Be aware: On the z16, you see only 10 partitions in the highest
Channel Subsystem (CSS 5). There are no FW partitions any more
that you need to take care of. When copying a CSS into CSS 5 of a
z16 or when changing the processor type of an existing
processor, HCD will allow this, if partitions 0xB - 0xF are either
reserved or FW partition. In this case, HCD deletes these partitions.

New z/Architecture and IBM z16 machine
instructions
• By default (unless locally customized), the assembler uses the OPTABLE(UNI) universal operation
code table.
• This defines the mnemonics for instructions up to the latest supported z/Architecture level.
• APAR PH39324 provides exploitation support for HLASM 1.6 (all z/OS releases), adding the new
mnemonics for IBM z16.
• These mnemonics may collide with the names of Assembler macro instructions you have
• It is safer to assemble using an OPTABLE option which matches the current highest target hardware
level.
• If you code Assembly Language macros, you should compare the list of new instructions to the
names of your Assembler macros.
• Tool available here: https://www.ibm.com/support/pages/tool-compare-ibm-z16-instruction-
mnemonics-user-macro-libraries
• If a conflict is identified, then either:
• Rename your affected macros
• Specify a separate assembler OPCODE table – PARM=,ASMAOPT, or ‘*PROCESS OPTABLE’
in the source
• See HLASM Programmer’s Guide
• Use a coding technique that permits both use of a new instruction and a macro with the same
name in an assembly such as HLASM’s mnemonic tag (:MAC :ASM)
• See HLASM Language Reference
• See the APAR documentation for a link to the new mnemonics and what to do in the case of
clashes.
OPTABLE MACHINE
Z16 Z16, ARCH-14
ZSA zSeries-10, ZS-10

Server participation in a Parallel Sysplex
▪IBM z16 servers support active participation in the same Parallel Sysplex, and connection with, these servers.
▪ IBM z15 T01, IBM z15 Model T02
• IBM z14 , IBM z14 Model ZR1
• This is both a direct CEC-CEC connectivity requirement, as well as anywhere in the sysplex regardless of
direct or indirect connectivity.
▪Which means:
• Configurations with z/OS on one of these servers can add an IBM z16 server to their Sysplex for either a z/OS
or a Coupling Facility image
• Configurations with a Coupling Facility on one of these servers can add an IBM z16 server to their Sysplex for
either a z/OS or a Coupling Facility image.
• Use of Integrated Coupling Adapter (ICA SR) or Coupling Express LR (CE LR) coupling links required.
• z14 servers were the last generation servers to support HCA3-O and HCA3-O LR (Infiniband coupling links).
These HCA3-O and HCA3-O LR links are not supported on z15 or IBM z16.
• Ensure all Required PTFs are installed on all z/OS images in the sysplex before introducing an IBM z16 server
into the sysplex, either as a z/OS or CF image.
• Ensure all necessary sysplex z/OS z16 Exploitation PTFs are installed on all z/OS images in the sysplex
before using an exploitation function in the sysplex, which affects either a z/OS or CF image.

Server connection and participation in a
Parallel Sysplex …
z/OS CF
z/OS z/OS
z/OS CF
z/OS z/OS
IBM
z16
z13
or
prior
o For connectivity and STP CTN: z13, z13s, zEC12, zBC12, z196,
z114, z10 EC/BC, z9 EC/BC, z990, z890 cannot connect to IBM
z16.
o For sysplex participation: z13, z13s, zEC12, zBC12, z196, z114,
z10 EC/BC, z9 EC/BC, z990, z890 is not supported with IBM z16.
IBM
z16
z/OS CF
z/OS z/OS
z/OS CF
z/OS z/OS
IBM
z16,
z14,
or
z15
Coupling Express LR (CE LR)
10 Gbps, 10/100 km
Integrated Coupling Adapter (ICA SR)
8 GBps, up to 150M
✓ For connectivity and STP CTN: z14, z15, and IBM z16 can connect to
IBM z16.
✓ For sysplex participation: z14, z15, and IBM z16 is supported with
IBM z16.
✓ Can use Infiniband in this picture only for z14 > z14 connection, not
IBM z16 (not z14 ZR1 models)

Firmware levels for coexisting Parallel Sysplex CEC connectivity
• Coupling facility code level on IBM z16 is CF Level 25.
• PE always recommends the highest available MCL level for best performance and availability, in a
sysplex.
• Find current CF Level information: https://www.ibm.com/downloads/cas/EEGKM5OM
January
19,
2023
information
Coupling Facility Code Level

Exploitation
considerations
for select IBM
z16 functions
CPU Measurement Facility new extended counters
z/OS Data Gatherer core topology location information
CFLEVEL 25 enhancements
z/OS Container Extensions (zCX) support and
zCX Foundation for Red Hat OpenShift support
System Recovery Boost enhancements
IBM z/OS Change Tracker
Up to 16 TB of real memory for z/OS image
zDNN library enablement for IBM Z Integrated Accelerator for AI
Compilers and Automatic Binary Optimizer for z/OS exploitation
Integrated Cryptographic Support Facility

CPU Measurement Facility new extended counters
▪For every server generation, the hardware adds, removes, and moves extended counters in the CPU Measurement
Facility (CPU/MF)
▪ For IBM z16 extended counters will begin with HISCTR_KEXT7_ * in the HISYCTRS mapping (z/OS MVS
Data Areas Volume 1)
▪z/OS Hardware Instrumentation Services (HIS) will collect IBM z16 extended counters for performance problem
diagnosis.
▪ HIS must be setup and started to collect this information, on each LPAR. See “Collecting CPU MF (Counters)
on z/OS – Detailed Instructions” here .
▪ HIS writes the extended counters in SMF 113. Refer to z/OS MVS SMF book.
▪ If changed extended counter sets are being used, then any programs relying upon those counters are
impacted, and must be updated accordingly.
▪ If unchanged extended counter sets are using, no changes are necessary.
▪ V2.3 and higher
▪ z/OS does not collect CPU MF data when running as a guest of z/VM.
Reminder! Gathering CPU MF Counters is an industry “best practice”. Review the methodology for successful
IBM Z Systems Processor Capacity Planning found here .
1. Capture on pre-IBM z16 (“before”) server to determine your LSPR workload
2. Capture on IBM z16 (“after”) server
3. Having the “before” and “after” can allow you to:
• Validate your achieved IBM z16 processor performance, and
• Provide insights for new features and functions.

z/OS Data Gatherer core topology information
▪zArchitecture is enhanced for IBM z16 and is providing CPU/core topology location related metrics for logical
and physical core homes, for a topology change.
▪The z/OS Data Gatherer retrieves the new CPU/core topology location related metrics and stores the metrics
in :
▪ SMF record type 70 subtype 1, PR/SM Logical Processor data section, which will show the entire
Processor Topology (logical and physicals) for all LPARs (z/OS or not).
▪ CPC logical processor section of Monitor III CPC data control block (ERBCPCDB)
▪If the CPU/core topology location related metrics are changing during the SMF interval or Monitor III
meantime, an indicator is set.
▪Metrics will be used for diagnostic and performance management purposes
▪ Recommendation is to still collect SMF 99.14 for processor topology, as this consolidated SMF 70.1 is
complementary.
▪ V2.3 and higher
▪ zPCR (Processor Capacity Reference) plans to support LPAR Topology Information
▪ CPU topology location related metrics will not be available when running as a guest under z/VM.

CFLEVEL 25 enhancements
▪Structure and Coupling Facility Storage Sizing with CF Level 25
• As expected, may increase storage requirements.
• CFLEVEL 25 structure size increases might be more noticeable than in prior
CFLEVELs, specifically for structures that are smaller (perhaps, 100MB or less).
• As always, use the CFSizer tool https://www.ibm.com/support/pages/cfsizer or the
batch SIZER utility (https://www.ibm.com/support/pages/cfsizer-alternate-sizing-
techniques).
• Make corresponding changes your CFRM policy INITSIZE and/or SIZE values.
▪Coupling Facility 25 Enhancements:
▪ Sysplex resiliency enhancements
▪ Additional cache structure metrics

CFLEVEL 25 – Resiliency enhancements
▪ Improved recovery for non-retriable CF commands
▪ Provides retry buffer support for cache and lock commands that are
non-retriable today.
▪ Intended to greatly improve recoverability following link problems such
as Interface Control Checks.
▪ No exploitation support is required.
▪ V2.2 and higher
▪ Improved capability for Structure Full recovery processing to be reserved for
use after a structure full condition occurs
▪ Exploiters can reserve a percentage of record data entries for recovery
use, and access those reserved entries (when needed for recovery
purposes) by using a new keyword on lock requests that create record
data entries.
▪ V2.3 and higher. VSAM RLS support in OA62059 on V2.3 and higher.

CFLEVEL 25 – Additional cache structure metrics
• Intended to help improve structure sizing and
apportionment between cache structures.
• New metrics for how long cache structure entries
(“directory entry residency time”) and data (“data entry
residency time”) are residing before they are reclaimed.
• CF calculates the elapsed time a data area or
directory entry resides in storage, before reclaimed.
• Metrics are returned when requested, by exploiter.
• Db2 13 has Group Buffer Pool residency time
reporting.
▪ V2.3 and higher.

z15 System Recovery Boost Recap - Startup/Shutdown Boosts…
Unleash additional processing capacity
using your already-entitled Central
Processors and zIIPs during a fixed-
duration performance increase known
as, “the boost period.”
✓ Faster shutdown (planned events only).
✓ Faster startup (IPL)
✓ Faster middleware and workload restart
✓ Faster system recovery and workload
execution
✓ Faster and parallelized GDPS
reconfiguration and orchestration actions.
The boost period can be used twice per IPL:
• 30-minute boost for shutdown
• 60-minute boost for startup
Speed Boost
Enables general-purpose
processors on sub-capacity machine
models to run at full-capacity speed
in the boosting image(s).
zIIP Boost
Provides additional capacity and
parallelism by enabling general-
purpose workloads to run on zIIP
processors that are available to the
boosting image(s).
GDPS enhancements
Increases the speed at which GDPS
drives hardware actions, along with the
speed of the underlying hardware
services.
1
2
3
Supported by z/OS
Supported by z/OS. Requires defined zIIPs
Supported by z/OS®, z/TPF, z/VM® & SADMP
All with zero increase in IBM software licensing costs

z15 System Recovery Boost Recap – Sysplex Recovery Enhancements
Provides recovery boosts for smaller-scope, occasional sysplex recovery activities, that introduce small-
scale disruptions when they occur
• Boosts automatically initiated when these events occur
• In effect on the relevant set of systems in the sysplex where the recovery is taking place
• Short-term boost periods, limited in total amount (30 minutes per LPAR per day)
Sysplex recovery activities that are boosted include:
• Sysplex Partitioning – planned or unplanned removal of a system from the sysplex
• CF Structure Recovery – recovery from CF or CF structure problems that require structure-level
rebuild or duplexing recovery
• CF Datasharing Member Recovery – recovery from disconnect or failure of a CF locking datasharing
member with locking resources held
• HyperSwap – planned or unplanned HyperSwaps from primary to secondary disk sets
No increase in IBM software licensing costs!
For more information see the Systems Recovery Boost Content solution (https://www.ibm.com/support/z-
content-solutions/system-recovery-boost/).
30

z16 System Recovery Boost enhancements highlights
❖ New additional enhancements, exclusive to IBM z16, for short-duration Recovery Process
boosts*.
1. SVC Dump boost (program-requested & oper-initiated, including from SLIP
trap)
• Boost system on which SVC dump is taken, to reduce system impact and expedite
diagnostic capture.
• Disabled by default
• Use CHNGDUMP to enable boost by specifying a minimum dump size threshold in GB
• DISPLAY DUMP,OPTIONS provides details about current size value set
• DISPLAY DUMP,INFO provides new dump size information to aid in choosing a dump
size threshold value
2. Customer-identified middleware start/restart boost
• Boost system on which middleware instance is being started/restarted to expedite
resource recovery processing, release retained locks, etc.
• Uses Classification Rules in WLM Service Definition (STCs only) via new Boost attribute
• Applicable to planned starts/restarts, or restarts after failure, manual, automated, or
ARM-driven restarts.

z16 System Recovery Boost enhancements highlights
3. Hyperswap Configuration Load boost
• Provides a Recovery Process boost* during a Hyperswap configuration
change/load/reload
• Intended to accelerate the process and minimize the disruption of the policy reload
• Enabled by default
• Works for GDPS, CSM or any other HyperSwap Manager that makes a Hyperswap
configuration change
❖ *Recovery Process boosts remain limited to 30 min per LPAR per day in
aggregate
❖ V2.4 and higher. Also use FIXCAT IBM.Function.SystemRecoveryBoost.
❖ For more details, see Dave Surman’s comprehensive SHARE presentation entitled: System
Recovery Boost Enhancements on the IBM z16

z16 System Recovery Boost enhancements highlights …contd
❖ Support for dynamic enabling and disabling all Recovery Process boosts, for better control
perhaps to “economize” boost times for when you prefer.
• Overriding control is in IEASYSxx BOOST=.
• New IEASRB PROC:
• S IEASRB,[CLASS=RP,]REQ=DISABLE|D
• S IEASRB,[CLASS=RP,]REQ=ENABLE|E
❖ Support for monitoring and display Recovery Process boost information.
❖ z/OS display command for current usage of time: total, details about LPAR 24-hour time window, etc.
(Used and remaining time is IBM z16 specific)
• D IPLINFO,BOOST,STATE command with additional information.
❖ IBM z16 specific: SE/HMC display command for current usage of time, similar to z/OS
• …and provide HW REST APIs to access same information
❖ SMF Type 90, subtype 40 logging of summary information, end of every 24-hour period.
❖ z/OS support to account for Recovery Process boosts that did not occur:
• Because the Recovery Process boosts were disabled, or
• Because of insufficient time in the 30-min pool.
• z/OS display command and SMF records will contain new information about these “potential” boosts
which did not occur, as well as those that did occur.
▪ V2.4 and higher. Also use FIXCAT IBM.Function.SystemRecoveryBoost.

Summary: z/OS System Recovery Boost March 1, 2023
Boosts are:
1. Speed:
subcap can
run fullcap
2. zIIP:
allowing
workload
onto zIIPs
On by default in
IEASYSxx
BOOST=SYSTEM
SMP/E FIXCAT IBM.Function.SystemRecoveryBoost
z16
z15 z16
System Recovery Boost
Recovery Process Boost*
at MCL P46602.005 for IBM z15 Driver 41C (Bundle S29)
Recovery Process Boost*
IPL
Startup
Standalone
Dump
(no
zIIP
boost)
Shutdown
Sysplex
Partitioning
–
planned
or
unplanned
removal
CF
Structure
Recovery
–
rebuild
or
duplex
CF
Datasharing
Member
Recovery-
disconnect
or
failure
from
locking
resources
Planned/Unplan
ned
HyperSwap
SVC
Dump
STC
start/restart
HyperSwap
configuration
load
Intended
Duration
60 min 60 min 30 min 2 min 1 min 1 min 2 min 2 min 5 min 2 min
Basis of use Auto Auto S IEASDBS Auto Auto Auto Auto CHNGDUMP
SET,SDUMP,
RPBMINSZ
threshold
WLM service
definition BOOST
attribute
Auto
z/OS 2.3 PTF PTF PTF PTF PTF PTF PTF
z/OS 2.4 PTF PTF PTF PTF PTF PTF PTF PTF PTF PTF
z/OS 2.5 PTF PTF PTF PTF PTF PTF PTF PTF PTF PTF
z/OS 3.1 YES YES YES YES YES YES YES YES YES YES
*Recovery Process Boost limited to 30 min per day per LPAR in aggregate. In V2.4 and V2,5, can be enabled or disabled
with S IEASRB,CLASS=RP,REQ=DISABLE|ENABLE
GDPS provides configuration and orchestration parallelization in V4R2, V4R3, and V4R4.

z/OS Container Extensions (zCX) support (aka zCX for Containers)
• On z/OS V2.4, zCX running on z14 or z15 requires one of the following:
• Container Hosting Foundation HW feature code 0104
• Monthly License Charge (MLC) product IBM Container Hosting
Foundation for z/OS (5655-HZ1)
• On IBM z16, there is no HW feature code 0104
• zCX on z16 has a dependency on the IBM Container Hosting
Foundation for z/OS product
• For the zCX Content Solution, visit https://www.ibm.com/support/z-
content-solutions/container-extensions/
• V2.4 and higher. Also use FIXCAT IBM.Function.zCX

• When running zCX for Red Hat OpenShift, it requires:
• zCX Foundation for Red Hat OpenShift (5655-ZCX)
• zCX Foundation for Red Hat OpenShift S&S (5666-ZCY)
• Note: HW feature code 0104 cannot be used for this offering, regardless of
hardware level (z14 and higher)
• zCX for Red Hat OpenShift requires standard RedHat Infrastructure
services to handle load balancing, DNS and others
• Can typically deploy these in a Bastion node
• A Bastion node may be deployed in zCX for Containers
• Same requirements as on previous slide
• Bastion node deployed on z16 LPAR will require z/OS Container Hosting
Foundation for z/OS
• For the zCX Foundation for Red Hat OpenShift Content Solution, visit
https://www.ibm.com/support/z-content-solutions/zcx-openshift/
• z/OS V2.4 and higher
IBM zCX Foundation for Red Hat OpenShift support

Integrated Cryptographic Support Facility Enhancements
• New ICSF support is required to administer a CEX8 coprocessor (which is new to IBM z16) if using a TKE
workstation, due to exploitation of quantum algorithms.
• Otherwise, existing workloads will run on IBM z16 without requiring ICSF support.
• Required support is provided on:
• z/OS V2.2 with z/OS V2.1-V2.2 (Web deliverable HCR77C0) or higher + PTF
• z/OS V2.3 or higher + PTF
• Common Cryptographic Architecture (CCA) Content:
▪ New CEX8 Coprocessor support
▪ New Quantum Safe Algorithms (Kyber & Dilithium 8,7)
• Enterprise PKCS #11 (EP11 ) Content:
• New CEX8 Coprocessor support
• EP11 New Quantum Safe Algorithms (Kyber & Dilithium 8,7)
• Exploitation of new function is supplied in ICSF PTFs on:
• z/OS V2.2-V2.4 (Web deliverable HCR77D1) or V2.5 (base, which is HCR77D2) or higher
• When exploiting new Quantum Safe Algorithms and sharing a KDS in a sysplex, ensure all ICSF PTFs
are installed on all systems.

zDNN library enablement for IBM Z Integrated Accelerator for AI
• IBM Z Integrated Accelerator for AI (AIU) is an on-chip inference accelerator in IBM z16.
• Refer to IBM Telum announcement.
• New zDNN library provides APIs and toolkit to drive AIU via new NNPA instruction.
• Neural Network Processor Assist (NNPA) is the new instruction that drives the AIU.
• zDNN provides support for an exploiter to:
• Transform tensor memory layout from standard layout to non-standard layout, which is required
by NNPA.
• Convert tensor element data type from standard types to the NNPA required DLFloat16 format.
• Call deep learning primitives, supported on NNPA.
• zDNN available on both z/OS and Linux and Z distributions.
• Linux on Z facilitates zCX exploitation of AIU when using supported Linux AI frameworks.
• Exploiters on servers without IBM Z Integrated Accelerator for AI are expected to provide an
alternate implementation of primitives:
• ONNX model compiler feature that is part of WMLz 2.4:
• When using this, the compiler knows to either generate a call to zDNN (if IBM z16 present) or
generate optimized program (using vector instructions) for the model
• Db2 SQL Data Insights feature (on Db2 13) uses the AIU when available (via zDNN):
• When not available uses a linear algebra library (openBLAS) to create an optimized software
implementation.
• V2.4 and higher.

Compilers and Automatic Binary Optimization for z/OS exploitation
The compiler releases with the new IBM z16 support are:
• Enterprise COBOL Compiler 6.4
• Enterprise PL/I Compiler 6.1
• IBM Open XL C/C++ for z/OS 1.1
• Availability as a Web deliverable, for z/OS V2.4 and V2.5
• Automatic Binary Optimizer for z/OS 2.2
• IBM SDK Java Technology Edition 8, and IBM Semeru Runtime Certified Edition 11.
• COBOL, ABO and PL/I will use new IBM z16 facilities to:
• Accelerate both directions of fixed/floating point conversions often found in financial
applications.
• Accelerate handling of numeric editing types used for formatted numeric output.
• Enable new optimizations for the common computational type of zoned decimal in COBOL
and PL/I.
• Open XL C/C++ will have exploitation of the IBM z16’s AIU instructions via new set of Built In
Functions (BIFs).

Up to 16 TB of real memory for z/OS image
• Allows new workloads which require more storage than is currently available.
• Allows 2 GB LFAREA to exceed the prior 4 TB limit, up to 16 TB.
• Real memory is available only for 2 GB pages.
• Adjust applications that make use of 2 GB frames to use more frames if applicable, such
as Java, Db2, etc.
• All online real storage defined to the LPAR, more than 4 TB is part of the 2 GB LFAREA, in
addition to what was specified in LFAREA.
• For instance: 8 TB defined to the LPAR and IEASYSxx: LFAREA=(1M=1024,2G=512)
➔ 5 TB of 2 GB pages.
• 1 GB of 1 MB pages, and 5 TB of 2 GB pages
• 5 TB = (512 x 2 GB = 1 TB) + (8 TB - 4 TB = 4 TB)
• On z/OS V2.5, no PTFs required. Not IBM z16 specific.
• Note:
• Any machine having a single LPAR consuming more than the amount of memory plugged
within a drawer will inherently reduce the performance of the LPAR due to the cross-drawer
communication. (This would be 10TB for z15/z16, and 8TB for z14)

IBM z/OS Change Tracker - Complementary resiliency feature available
• z/OS suite of system programmer tools to comprehensively manage
change configuration management.
• Real-time, system-wide software configuration change tracking and
control for system libraries, across all LPARs in a sysplex
• Automatic versioning of identified system control data sets, including
customization of the number of backups
• Member-level recovery and reporting of real-time change
• Capabilities to roll back and undo unplanned or unsuccessful updates
of the changed library members
• Comparisons between snapshots of system control data sets, or even
entire volumes, with differences identified, which may help to ensure
that software deployments have been successful
• Priced feature on z/OS V2.5 and higher. Not IBM z16 specific.
• Content solution available here: https://www.ibm.com/support/z-content-
solutions/serverpac-install-zosmf/

Summary: z/OS Support for IBM z16 March 1, 2023
Release
IBM.Device.Server.z16-
3931.RequiredService
IBM.Device.Server.z16-3931.Exploitation Max
Mem/
LPAR
Base
Support
ICSF
Crypto
Express
8S
Requirements
CF
Level
25
–
Cache
and
Lock
Retry
Enh
Integrated
Accelerator
for
AI
Enablement
CPU
Measurement
Facility
(HIS)
IBM
z16
Assembler
Support
z/OS
Data
Gatherer
core
topology
loc
info
SRB
–
Additional
Recovery
Process
Boosts
ICSF
Crypto
Express8S
zCX
support
RoCE
Express3
IBM
Open
XL
C/C++
CF
Level
25
–
Addl
Cache
Struct
Metrics
CF
Level
25
–
Struct
Full
Recov
TB
z/OS V2.2S P P, WDC P P P, WD1 4
z/OS 2.3 P P P P P P P,WD1 P P P 4
z/OS 2.4 P P P P P P P P P,WD1 P,SP P W P P 4
z/OS 2.5 P P P Y Y P P P P SP Y W P P 16
z/OS 3.1 Y Y Y Y Y Y Y Y Y SP Y W Y Y 16
DC Requires the ICSF web deliverable for FMID HCR77C0 minimally.
D1 Requires the ICSF web deliverable for FMID HCR77D1 minimally.
W A web deliverable is required, available at http://www-
03.ibm.com/systems/z/os/zos/downloads/
SP Required a separate program product, IBM Container Hosting Foundation for
z/OS (5655-HZ1)
Note:
S IBM Software Support Services required for extended
support.
P PTF is required, use SMP/E FIXCAT for identification
Y Support is in the base

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

More from Marna Walle

More from Marna Walle (9)

Recently uploaded

Recently uploaded (20)