Software requirements for running z/OS 3.1
Careful planning is needed to ensure that you run the appropriate software with z/OS 3.1 on your target system. This topic lists software requirements to consider.
- This topic does not describe the software requirements that are related to systems in a sysplex that use the coupling facility. For more information, see IBM z/OS Parallel Sysplex.
- With the exception of Java, the software requirements that are listed in this topic reflect the minimum levels. For Java, the indicated level is the level that is specifically required by the element or component.
- 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 the service has been withdrawn by the operating system manufacturer.
Java dependencies for z/OS elements and components
![Start of change](./delta.gif)
![Start of change](./delta.gif)
![End of change](./deltaend.gif)
- IBM Semeru Runtime Certified Edition for z/OS, Version 17 (5655-UA1).
![End of change](./deltaend.gif)
The Semeru 17 software development kit (SDK) supports the Java Standard Edition 17
language specification, which enables Java 17-compliant applications to be ported to and deployed on
IBM z/OS.
For more information, see z/OS Java home page.
For z/OS 3.1 orders, Semeru 17 is available as a bypassable requisite when you order
z/OS 3.1 through Shopz (as product 5655-UA1).
![Start of change](./delta.gif)
- IBM Semeru Runtime Certified Edition for z/OS, Version 11 (5655-DGJ)
- IBM 64-bit SDK for z/OS, Java Technology Edition, V8 (5655-DGH)
- IBM 31-bit SDK for z/OS, Java Technology Edition, V8 (5655-DGG)
![End of change](./deltaend.gif)
To use Semeru 17, you must update the JAVA_HOME environment variable to the proper
location. By default, the SDK resides in the following directory on your system:
/usr/lpp/java/J17.0_64
If you installed the SDK in another location, be sure to update the JAVA_HOME
location for the z/OS functions that use Java. See the z/OS product publications for the functions
used and the location for specifying the JAVA_HOME environment variable.
z/OS provides support for Java in the form of program temporary fixes (PTFs). To
find the PTFs for Semeru 17, use the following SMP/E fix category:
IBM.TargetSystem-RequiredService.Semeru.17
- Base Control Program (BCP):
- Predictive Failure Analysis (PFA)
- System Management Facilities (SMF)
- Subcapacity Reporting Tool (SCRT)
- Workload Management (WLM)
- z/OS XML System Services (z/OS XML)
- Capacity Provisioning Manager (CPM)
- Common Information Model (CIM)
- DFSMS:
- DFSMShsm
- 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
For the specific Java dependencies for each z/OS element, see Table 2. The Java dependencies must be followed for proper functioning of z/OS.
![Start of change](./delta.gif)
- Capacity Provisioning Manager (CPM)
- Predictive Failure Analysis (PFA)
- XML System Services.
![End of change](./deltaend.gif)
Infoprint Server requires IBM Semeru Runtime
Certified Edition for z/OS, Version 11 (5655-DGJ). For more
details, see the Infoprint Server entry in Table 2.
Determine which PTFs are needed for z/OS 3.1
Determine which PTFs are required for minimum support on z/OS 3.1, and which PTFs are required to use specific functions in z/OS 3.1.
- Identify the PTFs for both minimum support and functional support with the following fix
category (FIXCAT) in enhanced HOLDDATA:
- IBM.TargetSystem-RequiredService.z/OS.3.1
The HOLDDATA type FIXCAT 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 3.1, 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.3.1).
- 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 required product or functional release levels for z/OS 3.1
IBM middleware and application products require a specific release to run on z/OS 3.1. 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 3.1.
If you use this IBM product... | You need this product level (usually achieved with PTFs) |
---|---|
IBM
Security zSecure
Suite:
|
IBM Security zSecure products require ![]() ![]() ![]() ![]() |
IBM Tivoli Event Pump for z/OS (5698-B34) |
IBM
Tivoli Event Pump for z/OS, Version 4.2.2 (with PTF UA92963 for APAR OA51799) ![]() ![]() |
Table 2 lists the functions of z/OS 3.1 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 ![]() ![]() Db2® Data Server Driver for JDBC and SQLJ supports Java Batch Container function with PTF UK69734 and UK69742 (FMID JDB9912) Dynamic APF requirements:
|
BCP (continued) |
FICON® requirements:
IEAVFTED REXX exec requirements:
Java requirements:
Job support for started tasks requirements:
Messages that are displayed in non-English languages:
Operations log (OPERLOG) requirements:
TSO/E consoles used as extended MCS consoles:
z/OS
UNIX kernel requirements:
|
Common Information Model (CIM) |
Common Information Model (CIM) requires the following level of Java:
|
Communications Server | IP Services has the following software requirements:
SNA Services has the following software requirements:
|
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 |
To use control data set (CDS) or record level sharing (RLS), you require global resource serialization or an equivalent function. The DFSMShsm component requires the following level of Java:
|
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 require 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. Note: 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 | ![]() ![]() 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 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. IBM TDS requires the following level of Java:
|
IBM z/OS Liberty Embedded | IBM
z/OS Liberty Embedded requires the following level of Java:
|
IBM z/OS Change Tracker | None. |
IBM z/OS Management Facility (z/OSMF) | z/OSMF requires the following level of Java:
|
IBM z/OS Workload Interaction Correlator | None. |
ICKDSF | None. |
Infoprint Server | The z/OS Security Server feature is
required. Infoprint Central requires the
following levels of Java:
If you want to use the Internet Printing Protocol (IPP) function of Infoprint Server
(AOPIPPD), you require the following level of Java:
IPP for Infoprint Server can use only the 31-bit SDK. Java 11 can be used for Infoprint Central if your installation does not start AOPIPPD, or both Java 8 and Java 11 are installed on the system. To use the print
management functions that are provided by Infoprint Central, you require:
To
print output from Infoprint Server with AFP printers, you require PSF for z/OS V4 (5655-M32) Infoprint Server can
use the following transform products to convert data streams from one format to another:
The
following transform products can be used to convert data streams from one format to another on z/OS:
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 are not tested. Using untested
browsers might result in some Infoprint Central functions that are disabled.
|
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:
The transforms can convert:
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). |
Language Environment |
None. |
Metal C Runtime Library |
None. |
MICR/OCR | None. |
NFS | NFS Client and NFS Server both require:
|
PKI Services |
PKI Services requires the following level of Java:
|
RMF | The RMF Spreadsheet Reporter requires:
RMF Performance Monitoring (RMF PM) requires:
|
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 level of Java:
|
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
level of Java:
|
SMP/E | SMP/E V3.7 requires the following level of Java:
|
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 later. 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 later 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. |
![]() ![]() |
![]() IBM SMF Explorer must be installed in a z/OS UNIX environment or in a non-z/OS environment that includes a supported Python interpreter. To obtain the z/OS UNIX support for IBM SMF
Explorer, apply one of the following PTFs:
For more information about IBM SMF Explorer installation requirements, see IBM SMF Explorer. ![]() |
z/OS File System (zFS) |
The IP Services component of the z/OS Communications Server base element must be operational. |
z/OS Font Collection | None. |
z/OS OpenSSH |
None. |
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 is required, such as IBM Personal Communications/3270 and IBM Communications Manager/2. |