Software requirements for running z/OS V2R2

You must plan for the appropriate software to run with z/OS® V2R2 on your target system. This topic lists software requirements to consider.

Begin by determining which PTFs are required for minimum support on z/OS V2R2 and which PTFs are required to use specific functions. You can identify these PTFs (for both minimum and functional support) with a FIXCAT called IBM.TargetSystem-RequiredService.z/OS.V2R2, in enhanced HOLDDATA. A HOLDDATA type FIXCAT (fix category) is used to associate an APAR to a particular category of fix for target system PTFs identified as levels.

Then, use the SMP/E command REPORT MISSINGFIX to help identify those PTFs on your current system which would be needed for your upgrade to z/OS V2R2.

For example, you might 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.V2R2).

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.

Next, you must determine the minimum product release levels and release levels for functional requirements. IBM® middleware and application products require a specific level (version, release, or PTF) so that the products will run on z/OS V2R2. You cannot use the FIXCAT support to determine these release levels. Instead, you can refer to Table 1 for the functions of z/OS that require specific z/OS optional features, IBM middleware products, or IBM application products. The PTFs that are documented in Table 1 are required for support on z/OS V2R2.

If you are upgrading from z/OS V1R13 or z/OS V2R1, you may use the product levels on z/OS V2R2 that you used on your prior z/OS release, as long as the product levels are still service-supported. Note, however, that if you are using any of the functions in Table 1, 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 related to systems in a sysplex using the coupling facility. For that information, see the Parallel Sysplex® Web site: http://www.ibm.com/systems/z/pso/.
Requirements 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 operating systems whose service is withdrawn by the operating system manufacturer.
z/OS V2R2 has an overall dependency on IBM 64-bit SDK for z/OS, Java™ Technology Edition, V7.1 (5655-W44) and IBM 31-bit SDK for z/OS, Java Technology Edition, V7.1 (5655-W43). Some z/OS elements might run with an earlier level of Java; see Table 1 for the specific Java dependencies for each element.

Table 1. Functions of z/OS V2R2 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 z13™, z13s^TM, zEC12, zBC12, z196, z114, and System z10™ servers, see z/OS Migration. DB2® Data Server Driver for JDBC and SQLJ that supports Java Batch Container requirements 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 migrating to FICON, use the z/OS HCM feature. To report on the measurement data generated for FICON CHPIDs, use the z/OS RMF™ feature. To exploit 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 IEAVFTED REXX exec is a compiled REXX program which requires the full REXX compiler run-time libraries (at least [5695-014] REXX LIBR BASE V1.4 (FMID HWJ9140) installed before attempting to use IEAVFTED. Note that IEAVFTED will not work with the z/OS base element, REXX Alternate Runtime Library z/OS Base (FMID HWJ9143). Java requirements: The SMF product registration Java support requires that the following Java level or later be installed: IBM SDK for z/OS, Java 2 Technology Edition, V1 (5655-I56) at SDK 1.5 or later. Capacity Provisioning requires IBM 31-Bit SDK for z/OS, Java 2 Technology Edition V6 (5655-R31) or later. Job support for started tasks requirements: The z/OS Security Server feature is required if you plan to use dynamic security control for started tasks (using the STARTED class to assign RACF identities to started procedures and jobs dynamically with the RDEFINE and RALTER commands). Messages 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. Predictive Failure Analysis (PFA) requirements: The PFA component requires that the following Java level be installed: IBM 31-bit SDK for z/OS, Java 2 Technology Edition, V7.1 or higher. PFA will not run unless you modify it to point to the correct version of Java. RSM enhancements including Flash Express® support (that also includes dynamic reconfiguration support and optional PLPA/COMMON page data set support), pageable 1 MB Large Page support, and 2 GB Large Page support, requires a separate web deliverable (the z/OS V1R13 RSM Enablement Offering web deliverable). Runtime Library services (RTLS) requirement in z/OS: The z/OS Security Server feature is required if you want to check a user's access to libraries that are defined to RTLS and protected by security profiles. 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 has supported user-managed duplexing rebuild for its group buffer pools starting from DB2 V5 to the current release. 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's 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 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.
BCP (continued)	The IBM zEnterprise® Application Assist Processor (zAAP) is a specialized processing unit that provides an economical Java execution environment. Use of a zAAP requires one of the following or later products: IBM SDK for z/OS, Java 2 Technology Edition, V1 (5655-I56) at SDK 1.5 or later IBM 31-bit SDK for z/OS, Java 2 Technology Edition, V5 (5655-N98) IBM 64-bit SDK for z/OS, Java 2 Technology Edition, V5 (5655-N99) 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. DB2 Data Sever Driver for JDBC and SQLJ supports Java Batch Container function with PTF UK69734 and UK69742 (FMID JDB9912)
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 have the following products installed: 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 V5 (5697-ENV) R3 or later. For file access protection for FTP: z/OS Security Server feature For FTP DB2 query: DB2 V10 (5605-DB2) or later. 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 V5.3 (5697-B82) or later. For HPR, automatic network routing in composite network node: NCP V7R3 (5648-063). To use Spare SDLC lines: NCP V7 (5648-063) and NTuneMON V2 (5648-141). 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	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. 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® run time libraries for batch applications that will use VSAM RLS data access. 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 may browse, edit, copy, delete, and restore PDSE member generations both online and in batch.
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's 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 7, 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. With z10 and later servers, 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 IBM Resource Link® website: http://www.ibm.com/servers/resourcelink. It updates the IOCP input file with the PCHID values and can generate reports to help with cabling.
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 Java level be installed: IBM 64-bit SDK for z/OS, Java Technology Edition, V7.1 (5655-W44)
IBM TDS	If IBM TDS will use DB2 to store data for a general LDAP directory server, DB2 V10 (5605-DB2) or later 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 using the Kerberos or GSS-API programming interface, you require the z/OS XL C/C++ feature . To use the ldapdiff utility, you require 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 that the following Java level be installed: IBM 64-bit SDK for z/OS, Java Technology Edition, V7.1 (SR3) (5655-W44)
ICKDSF	None.
Infoprint Server	The z/OS Security Server feature is required. To print output from Infoprint Server using 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 or later: IBM 31-bit SDK for z/OS, Java Technology Edition, V7.1 (5655-W43) 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 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 the following: IBM 31-bit SDK for z/OS, Java Technology Edition, V7.1 (5655-W43) IBM 64-bit SDK for z/OS, Java Technology Edition, V7.1 (5655-W43) Accessing Infoprint Central requires one of the following web browsers on the user's workstation: Microsoft Internet Explorer 9.0 or later Mozilla Firefox 24 Extended Support Release (ESR) or later. 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 1 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 V1R13 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. To print on printers controlled by z/OS Communications Server SNA Services, Infoprint Coaxial Printer Support V2 for z/OS (5655-N62) is required. The workstation operating system required to use the Infoprint Port Monitor is Windows Server 2008 or Windows 7.
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, 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). 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). Note that in order 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 V5 (5697-ENV) R3 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 run time 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 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 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, WebSphere MQ for z/OS V7.0.1 (5655-F10) or later is required on the panels CK, ENC, PS and RM for z/OS V2R1 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, you must use DB2 V10 (5605-DB2) or later.
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 using 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 using the C or C++ language application programming interface, you require the z/OS 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.