Software requirements for running z/OS V2R5

Careful planning is needed to ensure that you run the appropriate software with z/OS V2R5 on your target system. This topic lists software requirements to consider.

If you are upgrading from an earlier release of z/OS®, you can use the product levels on z/OS V2R5 that you used on your prior z/OS release. The product levels must be still service-supported, with the following exceptions:

If you are using any of the products in Table 1, you must use the product levels shown.
If you are using any of the functions in Table 2, and those functions have dependencies on IBM® middleware or application products, you must use the product levels shown (or later).

Notes:

This topic does not describe program requirements that are related to systems in a sysplex that use the coupling facility. For more information, see Parallel Sysplex.
Requirements that are listed in this topic reflect the minimum levels.
Some IBM products and z/OS elements and features have comparable non-IBM equivalents. This topic reflects only IBM software.
z/OS does not support service for client systems for which service has been withdrawn by the operating system manufacturer.

Java dependencies for z/OS elements and components

z/OS V2R5 has an overall dependency on IBM 64-bit SDK for z/OS, Java™ Technology Edition, V8 (5655-DGH), and IBM 31-bit SDK for z/OS, Java Technology Edition, V8 (5655-DGG). Generally, this dependency exists for new or enhanced functions in z/OS. For the specific Java dependencies for each element, see Table 2.

As indicated in IBM United States Software Announcement 220-008, dated April 7, 2020, IBM intends to deliver an IBM SDK for z/OS, Java Technology Edition version 11. The SDK is planned to support the complete Java 11 language specification, enabling Java 11 compliant applications to be ported to z/OS. The SDK is planned to include the JZOS library for Java batch deployments and exploitation of z/OS system services (launcher and toolkit). Other z/OS specific extensions, such as integration with z/OS access control of cryptographic services and resources (keys/certificates), and support for Z hardware security modules, are planned to be introduced over time through service refreshes.

For the specific Java dependencies for each z/OS element, see Table 2. The z/OS dependencies in the table must be followed for proper functioning of z/OS.

The following z/OS components and elements use Java:

Base Control Program (BCP):
- Predictive Failure Analysis (PFA)
- System Management Facilities (SMF)
- Subcapacity Reporting Tool (SCRT)
- Workload Management (WLM)
- XML System Services
Capacity Provisioning Manager (CPM)
Common Information Model (CIM)
DFSMS:
- DFSMShsm
HCD
HCM
IBM Knowledge Center for z/OS
IBM Tivoli® Directory Server (TDS)
IBM z/OS Liberty Embedded
IBM z/OS Management Facility (z/OSMF)
Infoprint Server
PKI services
SDSF
Security Server RACF®
SMP/E

Determine which PTFs are needed for z/OS V2R5

Determine which PTFs are required for minimum support on z/OS V2R5, and which PTFs are required to use specific functions in z/OS V2R5.

To do so, follow these steps:

Identify the PTFs for both minimum support and functional support with a FIXCAT called IBM.TargetSystem-RequiredService.z/OS.V2R5, in enhanced HOLDDATA. The HOLDDATA type FIXCAT (fix category) is used to associate an APAR to a particular category of fix for target system PTFs identified as levels.
To identify the PTFs on your current system that would be needed for your upgrade to z/OS V2R5, run the SMP/E command REPORT MISSINGFIX.
You might, for example, use a command such as the following to identify PTFs for the CICS® CSI:
```
SET BDY(GLOBAL). 
REPORT MISSINGFIX ZONES(CICS51T) 
FIXCAT(IBM.TargetSystem-RequiredService.z/OS.V2R5).
```
To determine what PTFs are needed and not yet installed, run the command REPORT MISSINGFIX against the global zones that you use to support your middleware and application products.

Determine the minimum product or functional release levels for z/OS V2R5

IBM middleware and application products require a specific release to run on z/OS V2R5. You cannot use the FIXCAT support to determine these release levels. Instead, you can refer to the tables in this section.

Table 1 lists the IBM middleware and application products that require a specific version of the product to run on z/OS V2R5.

Table 1. IBM middleware and application products that require a specific version to run on z/OS V2R5
If you use this IBM product...	You need this product level (usually achieved with PTFs)
IBM Application Performance Analyzer for z/OS (5655-Q49)	IBM Application Performance Analyzer for z/OS requires Version 14.1 at a minimum. Earlier levels of this product are not supported for use with z/OS V2R5.
IBM Tivoli zSecure Suite: IBM Security zSecure Adapters for QRadar® SIEM (5655-AD8) IBM Security zSecure Admin (5655-N16) IBM Security zSecure Audit (5655-N17) IBM Security zSecure Command Verifier (5655-N19) IBM Security zSecure Visual (5655-N20) IBM Security zSecure Alert (5655-N21)	IBM Security zSecure products require zSecure Suite 2.5 at a minimum. Earlier levels of this product are not supported for use with z/OS V2R5.
IBM Tivoli Event Pump for z/OS (5698-B34)	IBM Tivoli Event Pump for z/OS, Version 4.2.2 requires PTF UA92963 for APAR OA51799. Prior releases (V4R2.0 and V4R2.1) of IBM Tivoli Event Pump for z/OS do not have a corresponding fix and therefore do not run on z/OS V2R5.

Table 2 lists the functions of z/OS V2R5 that require specific optional features, IBM middleware products, or IBM application products.

Table 2. Functions of z/OS V2R5 that require specific z/OS optional features or IBM products
z/OS element or feature	Required z/OS optional features or IBM products (by function)
Alternate Library for REXX	None.
Base Control Program (BCP)	For requirements related to software support for the IBM z16™, IBM z15™™, IBM z14®, z14 ZR1, z13®, and z13s®™ servers, see the z/OS Upgrade Workflow. Db2® Data Server Driver for JDBC and SQLJ supports Java Batch Container function with PTF UK69734 and UK69742 (FMID JDB9912) Dynamic APF requirements: The z/OS Security Server feature is required if you want to use the RACF data security monitor program (DSMON) to produce reports for APF-authorized programs.
BCP (continued)	FICON® requirements: To simplify configuration definition tasks when you are migrating to FICON, use the z/OS HCM feature. To report on the measurement data that is generated for FICON CHPIDs, use the z/OS RMF feature. To use the architecture enhancements, use the following: z/OS JES3 feature PSF for z/OS V4 (5655-M32) Tivoli System Automation for z/OS V3 (5698-SA3) or later IMS V12 (5635-A03) or later. IEAVFTED REXX exec requirements: The IBM supplied IEAVFTED REXX exec is used to produce a Timed Event Data Report in either a TSO or IPCS environment. The exec is a compiled REXX program that requires the full REXX compiler runtime libraries (at least [5695-014] REXX LIBR BASE V1.4 (FMID HWJ9140) installed. IEAVFTED does not work with the z/OS base element, REXX Alternate Runtime Library z/OS Base (FMID HWJ9143). Java requirements: Capacity Provisioning Manager (CPM) requires IBM 31-Bit SDK for z/OS, Java Technology Edition V8 (5655-DGG). CPM does not support the 64-bit version of this SDK. XML System Services requires IBM 31-Bit SDK for z/OS, Java Technology Edition V8 (5655-DGG). XML System Services does not support the 64-bit version of this SDK. Sub-Capacity Reporting Tool (SCRT) requires IBM 31-bit or 64-bit SDK for z/OS, Java Technology Edition, V7.0 or later. Other BCP components require the following minimum level of Java: IBM 64-bit SDK for z/OS, Java Technology Edition, V8 (5655-DGH) Job support for started tasks requirements: z/OS Security Server feature is required if you plan to use dynamic security control for started tasks. You can do this by using the STARTED class to assign RACF identities to started procedures and jobs dynamically with the RDEFINE and RALTER commands. Messages that are displayed in non-English languages: The z/OS Security Server feature is required if you use this function because RACF is used to obtain language information for users.
BCP (continued)	Operations log (OPERLOG) requirements: The z/OS Security Server feature is required if you want to protect the OPERLOG log stream. The z/OS SDSF feature is required if you want to use the log browser facility for the OPERLOG log stream. System-managed duplexing rebuild requires any APARs included in the CFDUPLEXING PSP bucket. This function can be used by the following products and components: System logger, the JES2 checkpoint, WLM for multisystem enclaves and IRD, VTAM® GR and multinode persistent sessions (MNPS), and BatchPipes® for OS/390® V2 (5655-D45) enable system-managed duplexing rebuild through APAR PQ49953. IRLM V2R1 and higher enables system-managed duplexing rebuild for the IRLM lock structure for IMS and Db2 data sharing. Db2 supports system-managed duplexing rebuild for its system communication area. Db2 supports user-managed duplexing rebuild for its group buffer pools, as of Db2 V5. IBM MQ enables system-managed duplexing rebuild for shared queues. CICS shared temporary storage queues, coupling facility data tables, and named counters are protected by system-managed duplexing rebuild in CICS Transaction Server (TS) for z/OS V3.1 (5655-M15) and later. IMS supports system-managed duplexing rebuild function for IMS shared message queue structures and IMS fast path expedited message handler (EMH) structures. IMS also supports z/OS system-managed duplexing rebuild function for IMS fast path virtual storage option (VSO) structures. This support also enables the system-managed rebuild and automatic altering of the VSO structure size. TSO/E consoles used as extended MCS consoles: The z/OS Security Server feature is required if you want to use this function because RACF is used to obtain console security attributes. z/OS UNIX kernel requirements: The z/OS Security Server feature is required if any address space must call a z/OS UNIX kernel service.
BDT	One or both of the BDT features (BDT File-to-File or BDT SNA NJE).
BDT File-to-File	None.
BDT SNA NJE	Any supported JES3 level.
Common Information Model (CIM)	Common Information Model (CIM) requires the following minimum level of Java: IBM 64-bit SDK for z/OS, Java Technology Edition, V8 (5655-DGH)
Communications Server	IP Services has the following software requirements: For SNMP NetView® client support: Tivoli NetView for z/OS V5R4 (5697-ENV) or later, if it is service-supported. For file access protection for FTP: z/OS Security Server feature For FTP Db2 query: A supported Db2 level is required. For user-written programs in Pascal that interface to a TCP, UDP, or IP boundary: IBM VS Pascal Compiler and Library (5668-767) For user-written programs in C that interface to an X Window System client, Remote Procedure Call, TCP or UDP protocol boundary, DPI, IP, or z/OS UNIX feature (Rcommands, RPC, or X Window System), you require the z/OS XL C/C++ feature. z/OS XL C/C++ feature is required for TCP/IP functions that are written in C, such as the following: C sample programs Network Database System client and server Network Computing System Remote Procedure Call Non-z/OS UNIX X Window System z/OS UNIX features (ONC/RPC, X Window System). SNA Services has the following software requirements: For High Performance Routing (HPR) Border Node and HPR network management: Tivoli NetView for z/OS V5R4 (5697-ENV) or later. If you are running z/OS as a guest under z/VM®, you require the PTF for VM APAR VM64789.
Communications Server Security Level 3	None.
Cryptographic Services	None.
DFSMSdfp	Data set encryption Ensure that ICSF is started early in the IPL process so that encryption services are available to the system initialization functions that use encryption. This consideration is especially important if you plan to encrypt zFS file systems, SMF data sets, or other data sets that are used during z/OS initialization. To ensure that ICSF is started early, place the command S CSF,SUB=MSTR (or the appropriate PROC name) early in the COMMNDxx member. This action can help to minimize delay in mounting zFS file systems and initializing OMVS, and prevent delays in z/OS initialization. On the command, the specification SUB=MSTR is used to start ICSF before JES. Otherwise, if you use automation to start ICSF, it is not started early enough for encryption to be available to initialization functions. Similarly, during z/OS system shutdown, ensure that ICSF is one of the last features to be terminated so that dependent functions are not impacted. ICSF can be terminated after the OMVS and JES address spaces are terminated and SMF halt processing is started. When ICSF is brought down after SMF is halted, an SMF record is not created for ICSF termination. Tip: If your ICSF startup procedure specifies a CSFLIST data set, you can remove this specification. ICSF no longer uses a CSFLIST data set, and ignores it if specified. Note: With ICSF APAR OA55378 for z/OS V2R3, ICSF can be started automatically during IPL. This option allows callers of ICSF to take advantage of ICSF functions during IPL. To start ICSF automatically during IPL, the ICSFPROC and ICSF system parameters must both be specified. For more information about the z/OS data set encryption enhancements, see z/OS DFSMS Using the New Functions. DFSMS EzNoSQL As of z/OS V2R4 and later with APAR OA64018, EzNoSQL adds Java support to the existing C and native APIs. For more information, see the EzNoSQL content solution webpage: EzNoSQL for z/OS. Distributed FileManager (DFM/MVS™) DataAgent and the DFM target server: To check the authorization of remote systems to connect to z/OS and to access specific data sets, the z/OS Security Server feature (RACF component) is required. PDSE member generations with ISPF For full support in using PDSE member generations with ISPF, IBM Data Set Commander V8.1 (5635-ISP) is beneficial. This product can display a member list with all member generations, from which users can browse, edit, copy, delete, and restore PDSE member generations both online and in batch. VSAM record level sharing (RLS): To use this function, you need the following: z/OS Security Server feature (RACF component) CICS TS for z/OS V3.1 (5655-M15) or later Appropriate levels of COBOL, PL/I, FORTRAN, and Language Environment® runtime libraries for batch applications that use VSAM RLS data access.
DFSMSdss	IMS backup-while-open support: To use this function, the Database Manager feature of IMS V12 (5635-A03) or later is required.
DFSMShsm	To use control data set (CDS) record level sharing (RLS), you require global resource serialization or an equivalent function. The DFSMShsm component requires the following minimum level of Java: IBM 64-bit SDK for z/OS, Java Technology Edition, V8 (5655-DGH)
DFSMSrmm	None.
DFSMStvs	To apply forward recovery logs to a restored copy of a data set, you need CICS VSAM Recovery for z/OS V4 (5655-P30). To back up data sets while they are open, you need the z/OS features DFSMShsm and DFSMSdss.
DFSORT	DFSORT Performance Booster for The SAS System requires enabling support from SAS Institute Inc.
EREP	None.
FFST	None.
GDDM	None.
GDDM-PGF	None.
GDDM-REXX	None.
HCD	Use of the CHPID Mapping Tool is recommended for mapping logical CHPIDs to physical channels (PCHIDs) and creating input to HCD/IOCP. The tool is a workstation-based Java application available from the Resource Link home page. It updates the IOCP input file with the PCHID values and can generate reports to help with cabling. HCD requires the following minimum level of Java: IBM 64-bit SDK for z/OS, Java Technology Edition, V8 (5655-DGH) Note: Beginning with z/OS V2R1 (HCD version 2), you can verify the active or target configuration by using z/OS discovery and I/O Autoconfiguration (zDAC). This action is possible for a server that supports zDAC, and for a system in the local sysplex that is enabled for dynamic activations. The verification is limited to FICON attached storage devices.
HCM	Operating system (workstation): A supported level of Windows Host communication: TCP/IP: TCP/IP networking protocol must be installed (delivered with Windows). HCM installation: A method to download the code from the host to the workstation is required, such as FTP or IBM Personal Communications (PCOMM). HCM requires the following minimum level of Java: IBM 64-bit SDK for z/OS, Java Technology Edition, V8 (5655-DGH)
HLASM	None.
HLASM Toolkit	None.
IBM HTTP Server	A web browser must be installed on a networked workstation. Communications Server IP connectivity must be established.
IBM Knowledge Center for z/OS	IBM Knowledge Center for z/OS requires that the following minimum level of Java level is installed on the system: IBM 64-bit SDK for z/OS, Java Technology Edition, V8 (5655-DGH)
IBM Tivoli Directory Server	If IBM TDS uses Db2 to store data for a general LDAP directory server, a supported Db2 level is required. Db2 is not required in the following situations: If IBM Tivoli Directory Server is used only to provide LDAP access to user, group, connect, and resource profiles stored in RACF. If IBM Tivoli Directory Server uses a file system to store data for a general LDAP directory server. If IBM Tivoli Directory Server uses a file-based backend (LDBM, file-based GDBM, or CDBM), a z/OS UNIX file system is required for storing this data. IBM Tivoli Directory Server requires a z/OS UNIX System file system for storing the schema backend. To write application programs that use the Kerberos or GSS-API programming interface, you require the z/OS XL C/C++ feature. IBM TDS requires the following minimum level of Java: IBM 64-bit SDK for z/OS, Java Technology Edition, V8 (5655-DGH) To use the ldapdiff utility, you require the following minimum level of Java: IBM 31-bit SDK for z/OS, Java 2 Technology Edition, V7.1 (5655-W43).
IBM z/OS Liberty Embedded	IBM z/OS Liberty Embedded requires the following minimum level of Java: IBM 64-bit SDK for z/OS, Java Technology Edition, V8 SR4 FP10 (5655-DGH)
IBM z/OS Change Tracker	None.
IBM z/OS Management Facility (z/OSMF)	z/OSMF requires the following minimum level of Java: IBM 64-bit SDK for z/OS, Java Technology Edition, V8 SR4 FP10 (5655-DGH) By default, the SDK resides in the directory /usr/lpp/java/J8.0_64 on your system. If you installed it in another location, be sure to include the JAVA_HOME statement in your IZUPRMxx parmlib member, as described in IBM z/OS Management Facility Configuration Guide. To use the IBM z/OS Encryption Readiness Technology (zERT) Network Analyzer plug-in, you require Db2 11 for z/OS or later.
IBM z/OS Workload Interaction Correlator	None.
ICKDSF	None.
Infoprint Server	The z/OS Security Server feature is required. To print output from Infoprint Server with AFP printers, you require PSF for z/OS V4 (5655-M32). If you want to use the IPP server function of Infoprint Server, you require the following level of Java: IBM 31-bit SDK for z/OS, Java Technology Edition, V8 (5655-DGG) The IPP Server can use only the 31-bit SDK. To use the print management functions that are provided by Infoprint Central, you require: A running IBM HTTP Server base element of z/OS IBM XML Toolkit for z/OS V1R11 (5655-J51) Accessing Infoprint Central requires one of the following web browsers on workstations with the following tested operating systems: Windows 10 Google Chrome Version 81.0.4044.122 (Official Build) or later (64-bit) Microsoft Edge Version 80.0.0361.54 or later Mozilla Firefox 71.0 or later (64-bit) Note: Other browsers might work with Infoprint Central, but are not tested. Using untested browsers might result in some Infoprint Central functions that are disabled. Infoprint Server can use the following transform products to convert data streams from one format to another: Infoprint Transforms to AFP V2 for z/OS (5655-N60) Infoprint XT for z/OS (5655-O15) InfoPrint Transform Manager for Linux® Version 1 Release 2 of the following transform products can be used to convert data streams from one format to another on z/OS V2R1 and later releases: IBM Print Transform from AFP to PCL for Infoprint Server for z/OS (5655-TF2) IBM Print Transform from AFP to PostScript for Infoprint Server for z/OS (5655-TF3)
Infoprint Server (continued)	Version 1 Release 2 Mod 2 (V1R2M2) of the following transform product can be used to convert data streams from one format to another on z/OS V2R1 and later releases: IBM Print Transform from AFP to PDF for Infoprint Server for z/OS (5655-TF1) The transforms can convert: PCL, PostScript, PDF, SAP R/3, and Xerox print data to AFP format for printing by PSF for z/OS V4 (5655-M32) on AFP printers AFP, line data, and XML data streams to PCL, PostScript, or PDF format for printing, e-mailing, or presenting on the web. The workstation operating system that is required to use the Infoprint Port Monitor is Windows 8.1, Windows 10, Windows Server 2012, or Windows Server 2016.
Integrated Security Services	None.
ISPF	To use ISPF Software Configuration and Library Manager (SCLM), the z/OS Security Server feature is recommended, but not required, to ensure data integrity. Use of VSAM support (Edit/View/Browse) requires the File Manager for z/OS product.
JES2	To monitor and control jobs, output, devices, and system resources from TSO/E, you require the z/OS SDSF feature. To use Advanced Function Presentation, you need PSF for z/OS V4 (5655-M32).
JES3	To monitor JES3 activity, z/OS RMF is required. To use Advanced Function Presentation, you need PSF for z/OS V4 (5655-M32).
Language Environment	With the following PTFs, the system auto-installs the Language Environment related resource definitions: PTF UI43662 for CICS TS 5.1 PTF UI43663 for CICS TS 5.2 PTF UI42574 for CICS TS 5.3 With CICS TS 5.4 and later, the autoinstall feature is included in the base code.
Metal C Runtime Library	None.
MICR/OCR	None.
NFS	NFS Client and NFS Server both require: z/OS Communications Server - IP Services z/OS Security Server feature
PKI Services	PKI Services requires the following minimum level of Java: IBM 64-bit SDK for z/OS, Java Technology Edition, V8 (5655-DGH)
RMF	The RMF Spreadsheet Reporter requires: Operating system: Windows 10. Spreadsheet program: To use the spreadsheet macros that are included with the Spreadsheet Reporter, you can use one of the following Microsoft Excel products: Excel 2013 or later. RMF Performance Monitoring (RMF PM) requires: Operating system: Windows 10.
Restricted Use Common Service Area (RUCSA)	None.
Runtime Library Extensions	None.
SDSF	To use the SAF security feature of SDSF, you require the z/OS Security Server feature. SDSF requires the following minimum level of Java: IBM 64-bit SDK for z/OS, Java Technology Edition, V8 (5655-DGH)
Security Server	To run the RACF remove ID utility (IRRRID00) or the RACF report writer, you require the z/OS DFSORT feature. If you use Db2 to manage multilevel data, you require a supported Db2 level. Security Server requires the following minimum level of Java: IBM 64-bit SDK for z/OS, Java Technology Edition, V8 (5655-DGH)
SMP/E	SMP/E V3.7 requires one of the following Java levels or later: IBM 31-bit SDK for z/OS, Java Technology Edition, V8 (5655-DGG) IBM 64-bit SDK for z/OS, Java Technology Edition, V8 (5655-DGH) The RECEIVE FROMNETWORK command and the GIMZIP and GIMGTPKG service routines require either the ICSF component of base element Cryptographic Services to be operational, or the level of Java mentioned here.
Terminal Input Output Controller (TIOC)	None.
TSO/E	For language support service or for TSO/E to save the user's console command profile, the z/OS Security Server feature is required.
XL C/C++	None.
XML Toolkit	None.
z/OS Authorized Code Scanner	None.
z/OS Container Extensions (zCX)	zCX is an element of z/OS (FMID HZDC7C0) that includes the Linux kernel and Docker Engine as well as the associated z/OSMF workflow. The software has the 3-character prefix AZD. All systems in the sysplex on which you deploy zCX must be at the z/OS V2R4 level or higher. The recommended enablement solution for zCX is to purchase and install IBM Container Hosting Foundation for z/OS, which delivers Monthly License Charge (MLC) pricing. If you have an IBM z14® or IBM z15™ processor, as an alternative to IBM Container Hosting Foundation for z/OS, you can purchase and install feature code 0104 through the eConfig Fulfillment Center. Both options include service and support for the underlying Linux kernel and zCX appliance, as well as unlimited zCX usage in the central processor complex (CPC) across all LPARs. If you have a z14 or higher processor, you can enable the zCX trial and experiment with zCX for 90 days. After that, IBM Container Hosting Foundation for z/OS is the recommended enablement solution for zCX Docker.
z/OS File System (zFS)	In z/OS V2R4, z/OS File System (zFS) replaced Distributed File Service, which became obsolete. The IP Services component of the z/OS Communications Server base element must be operational.
z/OS Font Collection	None.
z/OS OpenSSH	Starting with Version 6.4p1, z/OS OpenSSH no longer supports the use of ssh-rand-helper. It requires that a working /dev/random device is available to all OpenSSH client and server jobs. This change requires that ICSF is configured to support /dev/random and that users have SAF authority to the CSFRNG service. Otherwise, if /dev/random is not available, the ssh or sshd command fails with the following message: `FOTS1949 PRNG is not seeded. Please activate the Integrated Cryptographic Service Facility (ICSF)`
z/OS Security Level 3	None.
z/OS UNIX	To write application programs that use the C or C++ language application programming interface, you require the z/OS XL C/C++ feature.
3270 PC File Transfer Program	Compatible 3270 emulation software, such as IBM Personal Communications/3270 and IBM Communications Manager/2, is required.