Software requirements for running z/OS V2R4
Careful planning is needed to ensure that you run the appropriate software with 
z/OS® V2R4
on your target system. This topic lists software requirements to
consider.
z/OS V2R4 that you used on your prior z/OS release. The product levels must be still service-supported,
with the following exceptions:
- 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 is withdrawn by the operating system manufacturer.
-
z/OS V2R4 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. Older functions that are
unchanged from previous releases, and have lower Java
requirements, are expected to work with earlier supported releases of Java. 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.
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)
- Capacity Provisioning Manager (CPM)
- Common Information Model (CIM)
- HCD
- HCM
- IBM Documentation for z/OS
- IBM Tivoli Directory Server (TDS)
- IBM z/OS Management Facility (z/OSMF)
- Infoprint Server
- PKI services
- SDSF
- Security Server RACF
- SMP/E
- WebSphere Liberty
- XML System Services
- Base Control Program (BCP):
Determine which PTFs are needed for z/OS V2R4
You must determine which PTFs are required for minimum support on z/OS V2R4,
and which PTFs are required to use specific functions in z/OS V2R4.
- Identify the PTFs for both minimum support and functional support with a FIXCAT called
- To identify the PTFs on your current system that would be needed for your upgrade to z/OS V2R4, 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.V2R4). - 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 V2R4
IBM middleware and application products require a specific
release to run on z/OS V2R4. 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 V2R4.
| 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 V2R4. |
|
IBM Tivoli® zSecure Suite:
|
IBM Security zSecure products require
Version 2.4.0 at a minimum. Earlier levels of this product are not supported for use with z/OS V2R4. |
| 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 V2R4. |
Table 2 lists the functions of z/OS V2R4 that require
specific optional features, IBM middleware products, or IBM application 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 z15™, IBM z14®, z14 ZR1, z13®, z13s™,
zEC12, and zBC12 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:
FICON® requirements:
|
| BCP (continued) | IEAVFTED REXX exec requirements:
Java requirements:
Job support for started tasks requirements:
Messages that are displayed in non-English languages:
Operations log (OPERLOG) requirements:
Restricted use common service area (RUCSA):
|
| BCP (continued) |
System-managed duplexing rebuild requires any APARs included in the CFDUPLEXING PSP bucket. This
function can be used by the following products and components:
TSO/E consoles used as extended MCS consoles:
z/OS
UNIX kernel requirements:
|
| 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. |
| CIM | None. |
| Communications Server | IP Services has the following software requirements:
SNA Services has the following software requirements:
|
| Communications Server Security Level 3 | None. |
| Cryptographic Services | None. |
| DFSMSdfp |
|
| DFSMSdss |
IMS backup-while-open support: To use this function, the Database Manager feature of IMS V12 (5635-A03) or later is required. |
| DFSMShsm |
Control data set (CDS) record level sharing (RLS) serialization: To use this function, global resource serialization or an equivalent function is required. |
| 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. |
| Distributed File Service |
As of z/OS V2R4, Distributed File Service (DFS) is obsolete. Use z/OS Network File System (NFS) instead. The IP Services component of the z/OS Communications Server base element must be operational. |
| 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. 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):
Host communication:
|
| 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 Documentation for z/OS |
|
| 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 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. To use the ldapdiff utility, you require the following minimum level of Java:
|
| IBM z/OS Management Facility (z/OSMF) | The z/OSMF element requires the following minimum level of Java:
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.
|
| 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 one of the following minimum levels of
Java:
To use the print management functions that are provided by Infoprint
Central, you require:
|
| Infoprint Server (continued) |
Accessing Infoprint Central requires one of the following web browsers on workstations with the
following tested operating systems:
Note: Other browsers might work with Infoprint Central, but have not been tested. Using an
untested browser might result in some Infoprint Central functions being disabled.
Infoprint Server can use the following transform products to convert data streams from one format
to another:
Version 1 Release 2 of the following transform products are now
available and can also be used to convert data streams from one format to another on z/OS
V2R1 and later releases:
Version 1 Release 2 Mod 2 (V1R2M2) of the following transform product is now available
and can also be used to convert data streams from one format to another on z/OS V2R1 and later releases:
The transforms can convert:
The workstation operating system that is required to use the Infoprint Port Monitor is Windows 7, 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. For TCP/IP communication, ISPF Client/Server requires the IP Services component of
Communications Server on the host and the TCP/IP included in one of the following operating systems
on the workstation:
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 need 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:
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:
|
| RMF | The RMF Spreadsheet
Reporter requires:
RMF Performance Monitoring (RMF PM) requires:
The RMF Client/Server requires:
|
| Runtime Library Extensions | None. |
| SDSF | To use the SAF security feature of SDSF, the z/OS
Security Server feature is required. The z/OS
RMF feature is required for users to do the following:
|
| Security Server | To run the RACF remove ID utility (IRRRID00) or the
RACF report writer, the z/OS
DFSORT feature is required.
If you use Db2 to manage multilevel data, a supported Db2 level is required. |
| SMP/E |
SMP/E V3.7 requires one of the following Java levels or later:
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. |
| 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. |
| z/OS Security Level 3 | To write application programs that use the DCE programming interface, you require the z/OS XL C/C++ feature. |
| z/OS Container Extensions (zCX) |
zCX is shipped as an element of z/OS. This 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 will deploy zCX must be at the z/OS V2R4 or later level. IBM Container Hosting Foundation for z/OS delivers Monthly
License Charge (MLC) pricing to satisfy the requirement for the Z hardware feature code
0104. |
| z/OS File System (zFS) |
In z/OS V2R4, z/OS File System (zFS) replaces Distributed File Service, which is now obsolete. The IP Services component of the z/OS Communications Server base element must be operational. |
| z/OS Font Collection | None. |
| z/OS OpenSSH |
As of z/OS V2R2, OpenSSH is a base element of z/OS. With Version 6.4p1, OpenSSH no longer supports the use of ssh-rand-helper and 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:
|
| 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. |