Software requirements for running z/OS V2R3

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

If you are upgrading from z/OS V2R1 or z/OS V2R2, you can use the product levels on z/OS V2R3 that you used on your prior z/OS release, as long as the product levels are 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:
  1. This topic does not describe program requirements that are related to systems in a sysplex using the coupling facility. For that information, see Parallel Sysplex.
  2. Requirements that are listed in this topic reflect the minimum levels.
  3. Some IBM products and z/OS elements and features have comparable non-IBM equivalents. This topic reflects only IBM software.
  4. z/OS does not support service for client operating systems whose service is withdrawn by the operating system manufacturer.
  5. z/OS V2R3 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.

Determine which PTFs are needed for z/OS V2R3

You must determine which PTFs are required for minimum support on z/OS V2R3, and which PTFs are required to use specific functions in z/OS V2R3.

To do so, follow these steps:
  1. Identify the PTFs for both minimum support and functional support with a FIXCAT called IBM.TargetSystem-RequiredService.z/OS.V2R3, 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.
  2. To identify the PTFs on your current system that would be needed for your upgrade to z/OS V2R3, 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.V2R3).
  3. 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 V2R3

IBM middleware and application products require a specific release to run on z/OS V2R3. 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 V2R3.

Table 1. IBM middleware and application products that require a specific version to run on z/OS V2R3
If you use this IBM product... You need this product level (in most cases achieved with PTFs)
IBM Application Performance Analyzer for z/OS IBM Application Performance Analyzer for z/OS requires the 14.1 level at a minimum. Earlier levels of this product are not supported for use with z/OS V2R3.
IBM Security zSecure products:
  • zSecure Admin (5655-N16)
  • zSecure Visual (5655-N20)
  • zSecure Audit (5655-N17). A subset of the zSecure Audit functions is contained in Adapters for QRadar® SIEM (5655-AD8).
  • zSecure Alert (5655-N21)
  • zSecure Command Verifier (5655-N19)
  • zSecure CICS Toolkit (5655-N18), which is installed on CICS.
IBM Security zSecure products require the 2.3.0 level at a minimum. Earlier levels of this product are not supported for use with z/OS V2R3.

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

Table 2. Functions of z/OS V2R3 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.
BCP For requirements related to software support for the IBM z14™ (z14),IBM z13®, z13sTM, zEC12, and zBC12 servers, see z/OS Migration.

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.
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.
BCP (continued)
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 requires IBM 31-Bit SDK for z/OS, Java 2 Technology Edition V8 (5655-DGG) or later. CP does not support the 64-bit version of this SDK.
  • Predictive Failure Analysis (PFA) requires IBM 31-Bit SDK for z/OS, Java 2 Technology Edition V8 (5655-DGG) or later. PFA 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 2 Technology Edition, V7.0 or later.
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.
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.
Restricted use common service area (RUCSA):
  • For installations that cannot eliminate user key (8-15) common storage usage, the restricted use common service area (RUCSA) provides a means of isolating user key common storage to specific users and thus, controlling or eliminating the security risk that is associated with common user key storage. On z/OS releases V2R3 and V2R2, RUCSA is available as part of the BCP when you apply the PTF for APAR OA56180.
BCP (continued)
System-managed duplexing rebuild requires any APARs included in the CFDUPLEXING PSP bucket. This function can be exploited 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.
  • MQSeries® enables system-managed duplexing rebuild for shared queues in WebSphere® MQ for z/OS.
  • 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.
BookManager® READ To use the print function to print BookManager documents on AFP printers, you need to set your BookManager READ print options to GML Starter Set and install the following products:
  • DCF V1R4 (5748-XX9)
  • PSF for z/OS V4 (5655-M32)
CIM None.
Communications Server IP Services has the following software requirements:
  • For SNMP NetView® client support: Tivoli NetView for z/OS V5R4 (5697-ENV) or later , as long as 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 IMS sockets on z/OS: IMS V12 (5635-A03) or later
  • 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.
  • For TCP/IP functions written in C (C sample programs, Network Database System client and server, Network Computing System, Remote Procedure Call, non-z/OS UNIX X Window System) or z/OS UNIX features (ONC/RPC, X Window System), you require the z/OS XL C/C++ feature.
SNA Services has the following software requirements:
  • For High Performance Routing (HPR) Border Node and HPR network management:
    • Tivoli NetView for z/OS z/OS V5R4 (5697-ENV) or later.
  • If running z/OS as a guest under z/VM®, the PTF for VM APAR VM64789 is required.
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 will not be 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 after initiating SMF halt processing. Note that 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.

For more information about the z/OS data set encryption enhancements, see z/OS DFSMS Using the New Functions.

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 exploiting 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 z/OS Security Server feature (RACF component); CICS TS for z/OS V3.1 (5655-M15) or later; and 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

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

The IP Services component of the z/OS Communications Server base element must be operational.

SMB print serving support requires the z/OS Infoprint Server feature to be operational.

SMB password encryption requires the OCSF component of the z/OS Cryptographic Services base element to be operational to use hardware encryption capabilities.

Supported SMB clients include Microsoft Windows 8, Microsoft Windows 7, Microsoft Windows Server 2012, Microsoft Windows Server 2008, SUSE Linux with Samba, and Redhat Linux with Samba.

EREP None.
ESCON Director Support None.
FFST None.
GDDM None.
GDDM-PGF None.
GDDM-REXX None.
HCD To migrate from the active switch configuration or to activate a switch configuration, Tivoli System Automation for z/OS (5698-SA3) is required.

To perform the verification/priming function of the active I/O configuration, Tivoli System Automation for z/OS (5698-SA3) is required.

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), if Tivoli System Automation (TSA) I/O operations is not installed or not running. This action is possible for a server after the z196 and z114 generations supporting zDAC and for a system in the local sysplex, which is capable for dynamic activates. The verification is limited to FICON attached storage devices.
HCM Operating system (workstation):
  • Windows 7
Host communication:
  • TCP/IP: TCP/IP networking protocol must be installed (delivered with Windows 7).
  • HCM installation: A method to download the code from the host to the workstation is required (for example, FTP or PCOMM).
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
  • The Knowledge Center element requires that the following minimum level of Java level is installed:
    • IBM 64-bit SDK for z/OS, Java Technology Edition, V8 (5655-DGH)
IBM TDS 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 TDS is used only to provide LDAP access to user, group, connect, and resource profiles stored in RACF.
  • If IBM TDS is used only to provide LDAP access to configuration data stored in an IODF by way of HCD
  • If IBM TDS uses a file system to store data for a general LDAP directory server.

If IBM TDS uses a file-based backend (LDBM, file-based GDBM, or CDBM), a z/OS UNIX file system is required for storing this data. IBM TDS for z/OS 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 31-bit SDK for z/OS, Java 2 Technology Edition, V7.1 (5655-W43).
IBM z/OS Management Facility (z/OSMF) The z/OSMF element 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.

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:
  • IBM 31-bit SDK for z/OS, Java Technology Edition, V7.1 (5655-W43)
  • IBM 31-bit SDK for z/OS, Java Technology Edition, V8 (5655-DGG)
The IPP Server can use only the 31-bit SDK. However, you can install the 64-bit SDK on your z/OS system. See the Java versions that follow.
To use the print management functions that are provided by Infoprint Central, you require:
  • A running IBM HTTP Server base element of z/OS
  • XML Toolkit for z/OS V1R10 (5655-J51).
  • One of these:
    • IBM 31-bit SDK for z/OS, Java Technology Edition, V7.1 (5655-W43) or V8 (5655-DGG)
    • IBM 64-bit SDK for z/OS, Java Technology Edition, V7.1 (5655-W44) or V8 (5655-DGH)
Infoprint Server (continued)
Accessing Infoprint Central requires one of the following web browsers on workstations with these tested operating systems:
Windows 7 Professional, Windows 8.1, and Windows Server 2012
  • Microsoft Internet Explorer 10.0 or 11.0
  • Mozilla Firefox 42 Extended Support Release (ESR) or later
Windows 10
  • Microsoft Edge 25 or later
  • Microsoft Internet Explorer 10.0 or 11.0
  • Mozilla Firefox 42 Extended Support Release (ESR) or later
Note: Other browsers might work with Infoprint Central V2R3, but have not been tested. Using untested browsers might result in some Infoprint Central functions that are unavailable.
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
The following transform products are no longer supported as of z/OS V2R1:
  • Infoprint Transform for AFP to HP PCL V2 for z/OS (5655-P19)
  • Infoprint Transform for AFP to Adobe PDF V2 for z/OS (5655-P20)
  • Infoprint Transform for AFP to Adobe PostScript V2 for z/OS (5655-P21)
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:
  • IBM Print Transform from AFP to PCL for Infoprint Server for z/OS (5655-TF2)
  • IBM Print Transform from AFP to PDF for Infoprint Server for z/OS (5655-TF1)
  • IBM Print Transform from AFP to PostScript for Infoprint Server for z/OS (5655-TF3)

The transforms can convert (1) 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, and (2) AFP, line data, and XML data streams to PCL, PostScript, or PDF format for printing, e-mailing, or presenting on the web.

The Infoprint Coaxial Printer Support for z/OS (5655-N62) for printing to SNA-controlled printers is no longer supported as of z/OS V2R3.

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 one of the following operating systems on the workstation, by using the TCP/IP included in the workstation operating system:
  • Windows 7 or Windows 8
  • IBM AIX® V6.1 with X11R6 Motif V1R2

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).

Use of JES2 internal readers by CICS Transaction Server (CICS/TS) V3R1 (5655-M15) requires PTF UK25148 (for APAR PK42184).

Use of Tivoli Workload Scheduler for z/OS (5698-A17) requires the JES2 PTF for APAR PK85334.

Use of JES2 internal readers by CICS Transaction Server (CICS/TS) V3R2 (5655-M15) requires PTF UK27691 (for APAR PK48550).

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 None.
Library Server The IBM HTTP Server base element must be operational.

Use of extended shelf support requires XML Toolkit for z/OS V1R10 (5655-J51).

Indexing or reindexing of any type of shelf requires XML Toolkit for z/OS V1R10 (5655-J51).

Use of InfoCenter support requires XML Toolkit for z/OS V1R10 (5655-J51), plus IBM 31-bit SDK for z/OS, Java Technology Edition, V7.1 (5655-W43) or V8 (5655-DGG).

Use of the Java applet-based administrative interface requires XML Toolkit for z/OS V1R10 (5655-J51), plus IBM 31-bit SDK for z/OS, Java Technology Edition, V7.1 (5655-W43) or V8 (5655-DGG).

To use the Java applet-based administrative interface, the client workstation must be running a level of Java that equals or exceeds the level of Java running on the z/OS server. Use of the original HTML-based administrative interface does not require Java to be running on the client workstation, nor does it require Java to be running on the z/OS server except when documentation stored as InfoCenters is being administered.

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
OSA/SF To meet the SAF of the host operating system on which OSA/SF is running, the z/OS Security Server feature is required.

To handle alerts that OSA reports when the SNA mode is active on an OSA and issue OSA/SF for MVS commands from NetView, Tivoli NetView for z/OS V5R4 (5697-ENV) or later is required.

The z/OS RMF feature is required to obtain resource utilization data about OSA channels.

To access OSA/SF at a workstation, use a workstation that supports Java 1.6 runtime libraries. Interoperability testing with Windows 7 and Linux has been done. The OSA/SF GUI for Windows is shipped in a single JAR file.

RMF The RMF Spreadsheet Reporter requires:
  • Operating system: Windows 7.
  • Spreadsheet program: To use the spreadsheet macros that are shipped with the Spreadsheet Reporter, you can use one of the following Microsoft Excel products: Excel 2007, Excel 2010, or Excel 2013.
RMF Performance Monitoring (RMF PM) requires:
  • Operating system: Windows 7.
The RMF Client/Server requires:
  • Host software: a z/OS Communications Server network connection from the workstation to the host.
  • Workstation software: An operating system that supports the z/OS ISPF Client/Server.
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:
  • Use the RMF support that is provided by the DA panel
  • View sysplex-wide data on the DA panel
  • View both the MVS and LPAR view of CPU use on the DA panel
  • Use the Y action character to issue an MVS STOP command on the DA panel
  • View IBM zIIP information on the DA panel

For sysplex-wide data in a JES2 environment, a service-supported level of WebSphere MQ for z/OS is required on the panels CK, ENC, PS, and RM for JES2 systems.

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 The SMP/E RECEIVE ORDER command requires the IBM 31-bit SDK for z/OS Java Technology Edition V6.0 (5655-R31), or IBM 64-bit SDK for z/OS Java Technology Edition V6.0 (5655-R32) or higher.

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 previously mentioned levels of Java.

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.
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 Font Collection

None.

z/OS OpenSSH 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 terminal emulation software, such as IBM Personal Communications/3270 and IBM Communications Manager/2, is required.