Migrating to zOS R8 Part 1 - Messmer The Brain House

Migrating to z/OS R8 Part 1 of 3: Get Ready 

Session 2870 

Migrating to z/OS R8 

Part 1 of 3: Get Ready 

Marna WALLE 

z/OS Build and Install 

IBM Systems and Technology Group 

Poughkeepsie, New York 

mwalle@us.ibm.com 

Permission is granted to SHARE to publish this presentation paper in the SHARE proceedings; 

IBM retains the right to distribute copies of this presentation to whomever it chooses. 

August 15, 2006 | Baltimore, MD 

Abstract for Session 2870: Migrating to z/OS R8 Part 1 of 3 : Get Ready 

Thinking about migrating to the latest and greatest release - z/OS R8? The speaker will cover many of the installation 

requirements for preparing for your z/OS migration. Included will be: 

* Content of the z/OS R8 - what is new, changing, and removed. And what's being removed in the future! 

* Ordering and deliverables 

* Coexistence requirements - including the coexistence/migration/fallback/service policy 

* Driving and target system requirements - including both software and hardware 

* Some migrations actions you can perform now, on your current z/OS release 

Attend sessions 'Migrating to z/OS R8 Part 2 and Part 3' for specific migration tasks for z/OS R8. Preparing for your z/OS 

migration can be started today, with this session's important information! 

The general availability date for z/OS V1 R8 is planned for September 29, 2006. 

SHARE (c) Copyright IBM Corporation, 2006 August 15, 2006 

Session 2870 Page 1 of 70 Baltimore, MD

Content of z/OS R8 


Migrating to z/OS R8 Part 1 of 3: Get Ready Agenda 

Elements and Features Added, Changing, and Withdrawn 

z/OS Ordering and Deliverables 

Products Related to z/OS 

z/OS Policies 

z/OS Coexistence-Migration-Fallback 

Positioning for z/OS R8: 

Ensuring System Requirements are Satisfied 

Driving and Target System Requirements 

Migrating to z/Architecture 

Coexistence System Requirements 

Migration Actions You Can Do NOW 

Summary 

Migrating to z/OS R8: Part 1 of 3 - Get Ready! 

© 2003 IBM Corporation 


3 




Structure of Migrating to z/OS R7 Presentations 

Session 2870 - Part 1 of 3: Get Ready 

Content is what you just saw on the prior foil 

Session 2871 - Part 2 of 3: Get Set 

Migrations actions for z/OS R8 from selected elements: 

(General z/OS items) 

BCP 

XL C/C++ 

Communications Server 

HCD 

Session 2872 - Part 3 of 3: GO! 


DFSMS 

Distributed File Service - zFS 

Language Environment 

JES2 and JES3 

z/OS UNIX 

Also included are highlights of some enhancements you'll see in z/OS R8 for 

system programmers. 

Migrating to z/OS R8 Part 1 of 3 : Get Ready! 

You need to attend all 3 to 

get a complete migration 

picture! 


Scope 

Focus on Migrating to z/OS R8 from z/OS R5, R6, and R7 

If migrating to a new server level, see: 

for z890 and z990: migration action in z/OS Migration "Migrate to a z990 

or z890 server" 

for z9 EC and BC: attend "A z/OS System Programmer's Guide to 

Migrating to a New IBM System z9 EC or BC" session (and read 

migration action in z/OS Migration "Migrate to a System z9 server"). 

Other conference sessions on: 

What's New in z/OS 

A Systems Programmer Productivity Tool Bag 

JES2 z/OS 1.8 Product Overview & Review of Selected 1.7 Features 

What's New in LE for z/OS 

JES2 Exit Migration for z/OS 1.7 and also JES2 Exit Tutorial 

Hints for a Successful HFS to zFS Migration 

...and many others! 



Session 2870 Page 3 of 70 Baltimore, MD 

4 


5

Related Publications: 

w z/OS and z/OS.e Planning for Installation (GA22-7504) 

w z/OS Introduction and Release Guide (GA22-7502) 

w z/OS Program Directory (n/a) 

w zSeries Platform Test Report for z/OS and Linux Virtual Servers (formerly, the z/OS Parallel Sysplex Test Report) 

w z/OS License Program Specifications (GA22-7503) 

w z/OS Migration (GA22-7499) 

w z/OS Summary of Interface and Message Changes (SA22-7505) 

w z/OS MVS Planning: Operation (SA22-7601) 

w z/OS MVS Initialization and Tuning Reference (SA22-7592) 

w z/OS UNIX System Services Planning (GA22-7800) 

w ServerPac: Installing Your Order (no order number; custom-built to your order) 

w ServerPac: Using the Installation Dialog, (SA22-7815) 

Handy Internet Web Pages: 


URL 

http://www.ibm.com/servers/eserver/zseries/zos 

http://www.ibm.com/servers/eserver/zseries/zos/servicetst/ 

http://www.ibm.com/servers/eserver/zseries/zos/installation/ 

http://www.ibm.com/servers/eserver/zseries/zos/support/zos_eos_date 

s.html 

http://www.ibm.com/servers/eserver/zseries/zos/integtst/ 

http://www.ibm.com/servers/eserver/zseries/zos/bkserv/ 

http://www.redbooks.ibm.com/ 

http://www.ibm.com/support/techdocs/atsmastr.nsf/Web/Flashes 

http://www.ibm.com/servers/eserver/zseries/zos/support/ 

http://www.ibm.com/servers/eserver/zseries/zos/wizards/ 

http://www.ibmlink.ibm.com/ 

http://www.ibm.com/servers/eserver/zseries/software/swinfo/ 

http://service.boulder.ibm.com/390hdmvsinst.html 

http://service.boulder.ibm.com/390holddata.html 

http://www.ibm.com/servers/eserver/zseries/software/swinfo/pdo.htm 

http://www.can.ibm.com/custompac or 

http://www.ibm.com/ca/custompac 

http://www.ibm.com/software/shopzseries 

http://www.ibm.com/support/operations/us/order_delivery/ 

order_delivery.shtml 

http://www.ibm.com/servers/eserver/zseries/zos/software/isv17.html 

http://www.ibm.com/servers/eserver/zseries/library/refguides/ 

sw_pricing.html 

http://www.ibm.com/servers/eserver/zseries/swprice/ 

http://www.ibm.com/servers/eserver/zseries/zos/zos_sods.html 

http://www.ibm.com/servers/eserver/zseries/library/whitepapers 

http://www.ibm.com/servers/eserver/zseries/zos/installation/zos17_jes 

2_migration.html 

http://www.ibm.com/software/network/commserver/zos/ 

http://www.ibm.com/s390/java 

DESCRIPTION 

IBM z/OS home page 

Consolidated Service Test (CST) home page 

z/OS Installation 

End of Service dates for z/OS releases 

ZSeries Platform Test web page 

z/OS Library web page 

IBM Redbooks web page 

IBM Systems Center Flashes 

z/OS Technical Support 

z/OS Wizards 

IBMLink web page 

US Packaged Offerings web page 

ESO Overview 

Enhanced HOLDDATA web page 

CBPDO web page 

CustomPac (including SystemPac) web page 

ShopzSeries home page 

IBM Order Status homepage 

Software Dev. Supporting z/OS V1.7 web page 

zSeries Software Pricing Guide web page 

zSeries Software Pricing web page 

z/OS statements of direction web page 

z/OS Technical white papers 

JES2 Migration web page 

z/OS Communications Server web page 

z/OS Java web page 

IBM Education: 

IBM courses are available for z/OS. For schedules and enrollment on the world wide web, IBM Global Campus URL: 

http://www.ibm.com/services/learning/ . 



BCP 


z/OS R8 Base Elements and Optional Features Changing (from R5) 

z/OS R8 

Elements 

IBM HealthChecker for z/OS* (now 

integrated into BCP fmid) 

Common Information Model (CIM)* 

Communications Server - IP and 

SNA 

Communications Server Security 

Level 3 

Cryptographic Services 

ICSF (FMID HCR7731) 

PKI Services 

System SSL 

DFSMSdfp 

DFSMSdss 

DFSMShsm 

DFSMSrmm, 

DFSMStvs 

Distributed File Service 

HCD 

HCM 

HLASM (V1R5) 

HLASM Toolkit (V1R5) 

IBM Tivoli Directory Server for 

z/OS* (planned for 1H07) 

Infoprint Server 

Integrated Security Services 

Enterprise Identity Mapping 

LDAP Server 

Network Authentication Service 

ISPF 

JES2 

JES3 


Library Server 

Network File System 

RMF 

Run-Time Library Extensions 


SDSF 

Security Server - RACF 

SMP/E (V3R4) 

TSO/E 

C/C++ Without Debug Tool 

XL C/C++ 

z/OS Security Level 3 

IBM Tivoli Directory Server for 

z/OS Security Level 3* (includes 

LDAP Security Level 3) 

Network Authentication Service 

Level 3 

SSL Level 3 

z/OS UNIX 

Application Services 

Integrated Call Level Interface 

KEY: 

Black (in bold) are base elements 

Green (also in bold) are optional priced features 

Brown (also in italics) are optional unpriced features with export controls 

* indicates a new element since z/OS R5 

This element changed in z/OS R8 (from z/OS R5) 

This element changed in z/OS R8 (from z/OS R7) 

All other elements not listed have not changed since z/OS R5 



z/OS Elements and Features 

z/OS consists of base elements and optional features: 

� The base elements (or simply elements) deliver essential operating system functions. When you order z/OS, you 

receive all of the base elements. 

� The optional features (or simply features) are orderable with z/OS and provide additional operating system 

functions. Optional features are unpriced or priced: 

� Unpriced features are shipped to you only if you order them. If you plan to use any unpriced features, IBM 

recommends that you order them when you order your base elements. You must not wait until the next release 

becomes available. Once a release's base elements are no longer orderable, usually neither are its unpriced 

features. 

� Priced features are always shipped to you. When IBM packages your order, we enable the priced features that 

you ordered. These features are ready to use after you install z/OS (and customize them as needed). We disable 

the priced features that you did not order. Although they are installed on your system, you cannot use them. Later 

on, if you decide to use them, you notify IBM and you enable them dynamically (which is known as dynamic 

enablement). You dynamically enable by updating parmlib member IFAPRDxx and you notify IBM by contacting 

your IBM representative. 

Elements and features may be exclusive or nonexclusive: 

� An element or feature is called exclusive to z/OS if it exists only within z/OS (not also as a separately orderable, or 

stand-alone, product) and if future functional enhancements will occur only within z/OS. 

� An element or feature is called nonexclusive if it exists both (1) within z/OS and (2) as a stand-alone product. 

Listed in the foil above is the changing elements within z/OS V1.8 (that is, those that changed between z/OS V1.5 and 

z/OS V1.8). Also noted above are those elements changing between z/OS V1.7 and z/OS V1.8. For a complete list of all 

the z/OS V1.8 base elements and optional features, see Appendix A in this presentation. 



6

Some Element Information for z/OS R8 

See the table below for some notable changes that occurred in z/OS R8. For all previously announced statements of 

direction affecting z/OS R8 and future releases, visit http://www.ibm.com/servers/eserver/zseries/zos/zos_sods.html 

Name 

IBM Health Checker for z/OS 

IBM Tivoli Directory Server for z/OS 

msys for Operations 



Some Notable Element Information in z/OS R8 

IBM Health Checker for for z/OS 

Initially integrated into z/OS R7 as its own FMID, and that FMID was made 

available in a Web Deliverable back to z/OS R4. 

In z/OS R8 with enhancements, and merged with the BCP base FMID (HBB7730) 

IBM Tivoli Directory Server for z/OS 

New z/OS R8 base element, planned to be made available 1H07. 

The existing element, Integrated Security Services - LDAP Server, will continue to 

be available in addition to this new z/OS R8 Server. 

msys for Operations 

Removed in z/OS R8 

IBM plans to transition many of the msys for Operations functions to a new user 

interface and infrastructure in a future release of z/OS. 


IBM Tivoli Directory Server for z/OS Security Level 3 - new subelement in z/OS 

R8. Includes LDAP Server Security Level 3. 

Migrating to z/OS 1.7: Part 1 of 3 - Get Ready! 

Change 


© 20056IBM Corporation 

This function was included in z/OS R7 as a separate FMID under the BCP element. 

That z/OS R7 FMID was also made available in the Web deliverable IBM Health 

Checker for V1R4/R5/R6 of z/OS and z/OS.e. 

In z/OS R8, it’s a component of base element BCP FMID HBB7730. 

This new base element, IBM Tivoli Directory Server for z/OS, is planned to 

provide an optimized directory server, designed to allow greater 

consolidation of LDAP directories on z/OS. This function is planned to be 

made available by 1H2007. This is planned to enable you to collapse user 

registries typically used by distributed applications on z/OS, which can help 

simplify enterprise management and disaster recovery. The existing 

Integrated Security Services - LDAP Server will continue to be available in 

addition to the new z/OS R8 Server. 

This base element has been removed from the system. IBM plans to 

transition many of the msys for Operations functions to a new user interface 

and infrastructure in a future release of z/OS. 

This unpriced optional feature was new in z/OS R5 and contains several 

subelements. A new subelement in z/OS R8 is IBM Tivoli Directory Server 

for z/OS Security Level 3. This function includes and replaces the LDAP 

Security Level 3 subelement. 



7


Elements and Functions Withdrawn from z/OS R6 

C/C++ ISPF panels (from 

C/C++) 

Run-time Library Services 

(RTLS) (from Lang Env) 

Dynamic Link Library (DLL) 

Rename Utility (from Lang 

Env) 

SMIv1 version of the IBM MVS 

Enterprise-specific MIB 

module (from 

Communications Server) 

Priced Feature - invoke the C/C++ compiler 

via UNIX, JCL, or TSO/E. 

Base Element - no longer required due to 

stability and upward compatibliity 

Base Element - no longer needed due to 

C/C++ DLLs being licensed with the z/OS 

base 

Base Element - if you want to continue to use 

SMIv1, publicly available available tools can 

convert SMIv2 to SMIv1 

DCE Application Support Base Element - no replacement necessary. 

Evaluate WebSphere for similar function 

Encina Toolkit Executive Base Element - no replacement offered. 

Marketplace has moved to other technologies 

Text Search Base Element - available via web deliverable if 

still necessary for certain usage 


as of z/OS 

R6 

as of z/OS 

R6 

as of z/OS 

R6 

as of z/OS 

R6 

as of z/OS 

R6 

as of z/OS 

R6 

as of z/OS 

R6 



Withdrawn in z/OS V1.6 (last delivered in z/OS V1.5) 

This section lists items that were withdrawn in z/OS R6. You should take this into account as you plan your migration to 

z/OS R8. The removal of these functions may have migration actions which you can perform now, in preparation for z/OS 

R8. 

� The C/C++ ISPF panels, which include panels for C/C++ foreground compiles, C/C++ background compiles, and help 

panels for these compiles, are removed in z/OS V1.6. The z/OS C/C++ compiler can be invoked through z/OS UNIX, 

using JCL, and under TSO/E. 

� z/OS base element Language Environment's use of run-time library services (RTLS) is withdrawn in z/OS V1.6. This 

function is used primarily in run-time migration. Given the stability and the upward compatibility being provided by the 

Language Environment run-time library in recent releases of OS/390 and z/OS, this functionality is no longer required. 

� The Dynamic Link Library (DLL) Rename Utility, part of z/OS Language Environment, is removed in z/OS V1.6. This 

utility is used to package and redistribute IBM-supplied DLLs with applications. Since OS/390 V1R3, the C/C++ DLLs 

have been licensed with the OS/390 and z/OS base operating system. Therefore, the DLL Rename Utility is no longer 

required. 

� z/OS Communications Server support for the SMIv1 version of the SNMP IBM MVS TCP/IP Enterprise-specific MIB 

module is eliminated in z/OS V1.6. Support will continue for the SMIv2 version of this MIB module. For customers who 

want to continue using SMIv1, publically available tools can be used to convert an SMIv2 MIB module to an SMIv1 

MIB module. 

� Effective with z/OS V1.6, IBM has removed the base element, Distributed Computing Environment (DCE) Application 

Support, from z/OS. DCE Application Support facilitated the interaction between DCE clients and CICS or IMS 

regions. With the continued evolution of technology and accompanying changes in the marketplace, there is no need 

for this support. If similar function is required, IBM recommends that customers use IBM WebSphere. The DCE Base 

Services element, which provides services for developing and running client/server applications, is planned to 

continue to ship with z/OS and z/OS.e. 

� Effective with z/OS V1.6, IBM has removed the base element, Encina Toolkit Executive from z/OS. Encina Toolkit 

Executive provided a set of tools for developing client components of distributed transactional applications. Over time, 



8


the marketplace has moved to other technologies. This element, an enabler for DCE Application Support, is another 

obsolete element of z/OS V1.6 and is no longer be provided. There will be no replacement. 

� With z/OS V1.6, Text Search is no longer made available as a base element of z/OS. Instead, it will be made 

available for Web download as z/OS and z/OS.e Text Search under a restricted license. This is a change to the 

statement of direction made in Software Announcement 203-266 (RFA38767), dated October 7, 2003, which stated 

that with z/OS V1.6, the Text Search base element would be removed and no replacement would be provided. The 

Text Search element has been removed from the z/OS product. However, the Text Search function is still required 

and licensed for use only for DB2(R) UDB Text Extender feature of DB2 Universal Database for z/OS, Program 

Number 5625-DB2, as a Web deliverable named z/OS and z/OS.e Text Search. Before you use the DB2 UDB Text 

Extender feature, you must download and install the z/OS and z/OS.e Text Search Web deliverable on z/OS V1.6. 

Notable change: Starting with z/OS V1.7 and z/OS.e V1.7, the z/OS and z/OS.e Text Search Web deliverable is no 

longer available as a z/OS Web deliverable. Instead, the Text Search function is provided by Web download from the 

DB2 UDB Text Extender Web support site: 

http://www.ibm.com/software/data/db2/extenders/text/te390/ 




Elements and Functions Withdrawn from z/OS R7 

JES2 "compatibility" R4 mode 

(from JES2) 

JOBCAT and STEPCAT facilities 

(from DFSMSdfp) 

Support for ISAM data sets (from 

DFSMS) 

OS/390 R10 level of the C/C++ 

compilers (from C/C++) 

ECMB=NO circumvention in IEAOPTxx 

(from BCP) 

One-byte console IDs on macro 

interfaces and operator commands 

(and TRACK, ... commands) (from 

BCP) 

Base Element - to avoid a cold start, you must $ACTIVATE 

to convert the JES2 checkpoint to z2 mode before installing 

z/OS R7 

Base Element - any remaining JCL that use JOBCAT or 

STEPCAT must change 

Base Element - ISAM Compatibility Interface will still be 

provided (which allows you to run an ISAM program against 

a VSAM KSDS data set) 

Priced Feature - move to the ISO 1998 Standard level of the 

compilers (introduced in z/OS R2) 

Base Element - ECMB must be used, as the bypass will be 

removed. 

Base Element - Use console names, instead of one-byte 

IDs. Use Console ID Tracking Facility to identify one-byte ID 

usage, supplied as of z/OS R4 Consoles Enhancement 

feature. 


as of z/OS R7 

as of z/OS 

R7 

as of z/OS 

R7 

as of z/OS 

R7 

as of z/OS 

R7 

as of z/OS 

R7 

z/OS Optional Source media feature (not an element, an z/OS orderable feature) as of z/OS 

R7 

OROUTED (from Communications 

Server) 

Base Element - use OMPROUTE as the dynamic routing 

daemon 

= don't overlook! 

as of z/OS R7 

© 2003 IBM CorporationfInfInInfo 



This section lists items that were withdrawn in z/OS V1.7. You should take this into account as you plan your migration to 



� From base element JES2, IBM removes support for JES2 compatibility mode (R4). As of z/OS R7. JES2 will no 

longer support compatibility with pre-z/OS V1.2 systems. The $ACTIVATE command, which converts the JES2 

checkpoint from z2 mode to R4 mode (compatibility mode), will be removed. Before installing z/OS R7, you must do 

one of the following: 

� Use the $ACTIVATE command to convert the JES2 checkpoint to z2 mode 

� Offload the SPOOL, cold start JES2 z/OS R7, and reload the jobs on the new SPOOL 

� From base element DFSMSdfp, IBM removes the DFSMSdfp JOBCAT and STEPCAT facilities as of z/OS R7. The 

JOBCAT and STEPCAT facilities have been in existence for many years, predating the introduction of ICF (integrated 

catalog facility) catalogs. JOBCAT and STEPCAT were designed to address some of the functional shortcomings of 

VSAM catalogs, such as: 

� VSAM volume ownership, that is, all data sets on a volume having to be in the same VSAM catalog. Multiple 

catalogs could not point to data sets on the same volume. 

� Performance problems resulting from no multilevel alias support, as well as lack of ability to subset catalog data 

for recovery purposes. 

� Restrictions in the definition of the catalog SVC interface. 

The introduction of ICF catalogs in the mid-1980s and other catalog enhancements (such as the multilevel alias 

support) directly addressed those problems. In addition, processes were developed for system build to use system 

specific aliases instead of JOBCAT or STEPCAT. CBIPO introduced these processes and they are used today by 

offerings such as ServerPac to create data set entries in the new master catalog of the system being built. 

At the time ICF catalogs were introduced, the JOBCAT and STEPCAT facilities were functionally stabilized. Neither 

SMS-managed data sets nor UCBs above the 16 megabyte line may be used with JOBCAT or STEPCAT. ICF 



9


catalogs contain sufficient functional capabilities that all functions that previously could only be performed with 

JOBCAT or STEPCAT can now be done without them. 

Furthermore, the use of JOBCAT and STEPCAT can actually cause significant problems. Data sets are generally 

not cataloged according to the normal predictable search order when JOBCAT or STEPCAT is used. This impacts 

the ability to do comprehensive installation storage management and can increase staff requirements. For 

example, interval migration and recall using DFSMShsm is effectively unusable when the data sets cannot be 

found using the standard catalog search order. The use of JOBCAT and STEPCAT can also result in noticeable 

increases in the time required to perform catalog requests. 

� Due to ISAM's limited functionality and the capabilities of VSAM, particularly VSAM data sets in extended format, 

z/OS V1.6 was the last release in which DFSMS ISAM and the utility program, IEABISAM, was available. IBM has 

provided the ISAM Compatibility Interface (ISAM CI) which allows users to run an ISAM program against a VSAM 

KSDS data set. Details on using this interface and procedures for converting ISAM data sets to VSAM data sets can 

be found in Appendix E of Using Data Sets. This compatibility interface program continues to be provided as part of 

DFSMS and is not discontinued with the ISAM removal from DFSMS. 

� From optional feature C/C++ without Debug Tool, IBM has removed the OS/390 R10 level of the C/C++ compilers 

from z/OS R7. The OS/390 R10 C/C++ compilers were shipped as an aid to migration to the C/C++ compilers that 

were introduced in z/OS V1R2. The z/OS V1R2 level of the C++ compiler supports the ISO 1998 Standard level of 

C++. For information about migrating from the older to the newer level of the compilers, see z/OS C/C++ Compiler 

and Run-Time Migration Guide. 

� Previously, the CMB= parameter specified the I/O device classes for which measurement data was to be collected, in 

addition to the DASD and tape device classes. It also allowed you to specify the number of channel measurement 

block (CMB) slots to reserve for adding more devices with an ACTIVATE. As of the z990 Exploitation feature on z/OS 

R4, the system ignores the CMB and uses instead the measurement data in the extended channel measurement 

block (ECMB). As a migration action since then, you must convert user-written programs that make use of the CMB 

to make use of the ECMB, and contact ISVs to obtain updates to ISV programs that use the CMB. The type of 

programs especially likely to use the CMB are monitor programs. If ISV support is not available, you could have 

specified ECMB=NO in parmlib member IEAOPTxx as a circumvention until the ISV support is available. See APAR 

OA06164 for additional details. The ECMB=NO circumvention has been removed in z/OS R7, so have plans in place 

to discontinue this usage before migrating to z/OS R7. 

� One-byte console IDs are removed from macro interfaces and operator commands in z/OS R7. You are not allowed 

to specify one-byte console IDs on macros (such as WTO/WTOR), or on such operator commands as D C,CN= or D 

PFK,CN= . You should use console names instead. A service called the Console ID Tracking Facility is available to 

help you identify one-byte ID usage. The use of console names is already a best practice on OS/390 and z/OS. For 

information about Console ID Tracking facility, see z/OS MVS Planning: Operations. 

In addition, the TRACK command, as well as the commands STOPTR, CONTROL T, CONTROL D,U, CONTROL 

D,H, and MSGRT TR=A are removed in z/OS R7. 

� The z/OS Optional Source media feature is not offered as of z/OS R7. The last release offering these materials was 

z/OS R6. These features contain macros and source code for some programs in the z/OS BCP, BDT base, BDT SNA 

NJE, BDT File-to-File, DFSMS, MICR/OCR, BCP JPN, and Security Server RACF elements. 

� In z/OS R7, support for OROUTED has been removed from Communications Server. You should use OMPROUTE 

as your dynamic routing daemon. 




Element and Functions Withdrawn from z/OS R8 

zFS multi-file system aggregate 

shared across a sysplex (from 

Distributed File Service) 

Firewall Technologies (from 

Integrated Security Services) 

Some Communications Server 

functions 

Any remaining one-byte console ID 

support (from BCP) 

Certain plug-ins for msys for Setup: 

TCP/IP Services, z/OS UNIX System 

Services, Language Environment, 

Parallel Sysplex, ISPF, and RMF 

Base Element - zFS compatibility mode aggregates (which 

have a single file system per data set) will continue to be 

supported in all environments. 

Base Element - Many Firewall Technologies functions have 

been been long stabilized and can be replaced w/ Comm 

Server functions (IPSecurity). Some functions won't have 

replacements. 

Base Element - TCP/IP Configuration profile block 

definitions, PAGTSNMP subagent, EE TGs definition by 

specifying multiple SAP addrs, and AnyNet 

Base Element - Use console names instead of one-byte 

console IDs 

Base Element - TCP/IP plug-in available from web and won't 

require msys for Setup. Improvements for setup and 

configuration are planned in the future. 

msys for Operations Base Element - IBM plans to transition many of the current 

msys for Operations functions to a new user interface and 

infrastructure in a future release of z/OS. 



as of z/OS 

R8 

as of z/OS 


as of z/OS 


as of z/OS 


as of z/OS 


Planned for 

release after 

R7 




This section lists items that were withdrawn in z/OS V1.8. You should take this into account as you plan your migration to 



� z/OS V1.7 was the last release to allow mounting zFS file systems contained in multi-file system aggregates that are 

to be shared across systems in a sysplex. IBM has previously recommended that these multi-file system aggregates 

not be shared in a sysplex environment. Attempts to mount zFS file systems contained in multi-file system aggregates 

will fail in a z/OS UNIX shared file system environment. Mounting zFS compatibility mode aggregates, which have a 

single file system per data set, will continue to be supported in all environments. 

� z/OS V1.7 was the last release to include the Firewall Technologies component of the Integrated Security Services 

element. Many Firewall Technologies functions have been stabilized for some time and can be replaced using 

comparable or better functions provided by or planned for Communications Server, notably, IPSecurity. In addition, a 

functionally rich downloadable tool is planned to replace the IPSecurity and IP Filtering configuration GUI support. 

The following functions will be removed without replacement: 

� FTP Proxy services 

� Socks V4 services 

� Network Address Translation (NAT) 

� RealAudio (TM) support 

� z/OS V1.7 was the last release in which z/OS Communications Server will support the following functions, after which 

they will be removed from the product: 

� TCP/IP configuration profile block definition statements: 

� ASSORTEDPARMS 

� ENDASSORTEDPARMS 

� KEEPALIVEOPTIONS, 

� ENDKEEPALIVEOPTIONS 

Equivalent capability is provided for the ASSORTEDPARMS statements by the GLOBALCONFIG, 

IPCONFIG, TCPCONFIG, and UDPCONFIG statements. Equivalent capability is provided for the 

KEEPALIVEOPTIONS statements by INTERVAL and SENDGARBAGE on the TCPCONFIG statement. For 



10


information on TCP profile and configuration statements, refer to z/OS Communications Server IP 

Configuration Reference. 

� The SNMP Service Level Agreement (SLA) Version 1 MIB and the PAGTSNMP subagent. In z/OS V1.5, 

Communications Server provided a new SNMP SLA Version 2 MIB and NSLAPM2 subagent. IBM recommends 

that you migrate to the new Version 2 MIB and NSLAPM2. 

� The option of defining parallel Enterprise Extender TGs by specifying multiple SAP addresses. Beginning in z/OS 

V1.5, parallel EE TGs may be defined by using different EE VIPAs on one (or both) of the endpoints. 

� AnyNet. You may implement other IBM solutions such as Enterprise Extender (EE) as a replacement for AnyNet. 

� In z/OS V1.8, the remaining support for one-byte console IDs was removed from control blocks CIB, CSCB, ORE, 

WQE, XSA. This completes the removal of one-byte console IDs in z/OS. Instead of using one-byte console IDs, 

console names should be used. 

� Support for the following plug-ins for msys for Setup was withdrawn in z/OS V1.8: TCP/IP Services, z/OS UNIX 

System Services, Language Environment, Parallel Sysplex, ISPF, and RMF. You will not be able to use msys for 

Setup for function enablement, setup, or configuration of these areas of z/OS. The DB2 V8 msys for Setup plug-in is 

unaffected and remains available for setup and configuration of DB2. The TCP/IP plug-in will continue to be available 

for download via the Web and will no longer require msys for Setup. IBM intends to continue to deliver improvements 

to help with z/OS setup and configuration in the future. 

� z/OS V1.7 is the last release to support the z/OS msys for Operations element. msys for Operations has been 

removed from z/OS V1.8. IBM plans to transition many of the current msys for Operations functions to a new user 

interface and infrastructure in a future release of z/OS. 




Functions Planned to be Withdrawn 

in the release after R8... 

Host communication between HCM 

and HCD with APPC (from HCM) 

In-stack version of TN3270 Server 

(from Communications Server) 

APPC Application Suite in 


Run-time support for applications 

that use the C/C++ IBM Open Class 

(IOC) Dynamic Link Libraries (DLLs). 

Priced Feature - Only TCP/IP for host communication 

between HCM and HCD will be allowed. (Currently both 

TCP/IP and APPC are supported.) 

Base Element - use standalone TN3270 Server instead 

(introduced in z/OS R6) 

Base Element - more full-featured alternative applications 

exist in modern integrated SNA/IP networks. (APPC itself 

remains an integral part of SNA functions, and no plans to 

remove APPC from z/OS.) 

Priced Feature - Any application code that uses the IOC 

Library should migrate to use the Standard C++ Library 



Planned for 

release in 

2007 

Planned for 

relase in 

2007 

Planned for 

release in 

2007 

Planned for 

release in 

2007 



Planned for removal in the release following z/OS R8 

This section lists items that IBM has announced it intends to remove in release following z/OS R8. You are encouraged to 

consider these removals when making your plans for system upgrades. These statements represent IBM's current 

intentions. IBM development plans are subject to change or withdrawal without further notice. 

� z/OS R8 is planned to be the last release that supports host communication between Hardware Configuration 

Manager (HCM) and Hardware Configuration Dialog (HCD) elements via Advanced Program to Program 

Communication (APPC). Today for host communication either Transmission Control Protocol/Internet Protocol 

(TCP/IP) or APPC are supported. Starting with the z/OS release available in 2007, the host communication will be 

done exclusively via TCP/IP. 

� z/OS V1R6 Communications Server and subsequent releases include a standalone TN3270 Server. This standalone 

TN3270 server is expected to provide increased flexibility, improved reliability, and simplified problem diagnosis as 

compared to the in-stack version of the TN3270 Server. z/OS V1.8 is planned to be the last release of z/OS 

Communications Server which will support the in-stack version of the TN3270 Server. After z/OS V1.8 this capability 

will be removed from the product. In preparation for that change, customers should consider implementing the 

standalone TN3270 Server. For more information, refer to 


� The APPC Application Suite is a set of common applications originally designed to enhance the value of SNA 

networks for end users. Since more full-featured alternative applications exist in modern integrated SNA/IP networks, 

z/OS V1.8 is planned to be the last release of z/OS Communications Server which will include the APPC Application 

Suite. After z/OS V1.8 the APPC Application Suite will no longer be shipped with the product, and will not be 

supported. However, note that APPC itself remains an integral part of z/OS Communications Server's SNA functions, 

and there are no plans to remove APPC from z/OS. For more information please refer to 


� z/OS R8 is planned to be the last release to include the C/C++ IBM Open Class (IOC) Dynamic Link Libraries (DLLs). 

Application development support for the C/C++ IOC Library was withdrawn in z/OS V1.5. The run-time support (DLLs) 

for applications that use the IOC Library is planned to be removed in the z/OS release available in 2007. Applications 

that are dependent on the IOC Library will not run starting with the z/OS release available in 2007. IBM has previously 



11


recommended that customers with application code that uses the IOC Library migrate to the Standard C++ Library. 

The publication IBM Open Class Library Transition Guide was published with z/OS 2 V1.2 C/C++ as a reference for 

customers migrating their code from the IBM Open Class Library to the Standard C++ Library. You can get this guide 

by visiting http://www-1.ibm.com/support/docview.wss?rs=32&org=SW&doc=7001423&loc=en-us 




Functions Planned to be Withdrawn 

in the future... 

BIND DNS 4.9.3 (from 

Communications Server) 

English and Japanese panels 

from DFSORT 

Support for VSAM data sets 

with IMBED, REPLICATE, or 

KEYRANGE attributes (from 

DFSMS) 

zFS multi-file system 

aggregates (from Distributed 

File Service) 

RMF LDAP replacement (from 

RMF) 

Base Element - implement BIND 9.2.0 as a 

replacement (availabile since z/OS R4) 


Future 

Priced Feature - no replacement offered Future 

Base Element - plan to redefine any affected 

VSAM data sets. Use tool to assist in 

identifying affected VSAM data sets. 

Base Element - zFS compatibility mode 

aggregates will still be supported 

Priced Feature - RMF LDAP interface is 

planned to be replaced with a CIM Monitoring 

Interface that is part of z/OS R7 


Future 

Future 

Future 



Planned for removal in a future z/OS release 

This section lists items that IBM has announced it intends to remove in a future z/OS release. You are encouraged to 

consider these removals when making your plans for system upgrades. These statements represent IBM's current 

intentions. IBM development plans are subject to change or withdrawal without further notice. 

� In a future release the support for BIND DNS 4.9.3 will be removed from Communications Server. Customers should 

implement BIND DNS 9.2.0 as a replacement. BIND DNS 9.2.0 is included in the product beginning with z/OS V1.4. 

Customers exploiting the Connection Optimization (DNS/WLM) feature of BIND 4.9.3 should investigate alternative 

solutions, such as the Sysplex Distributor function. 

� The English and Japanese ISPF panels will be removed from DFSORT in a future release. This limited function 

interactive facility will no longer be provided, and there will be no replacement. 

� From DFSMS, support for the VSAM IMBED, REPLICATE, and KEYRANGE attributes will be withdrawn in a future 

release. No supported release of z/OS allows you to define new VSAM data sets with these attributes. Using them for 

existing data sets can waste DASD space and can often degrade performance. When this support is withdrawn, you 

will not be able to process data sets with these attributes. It is best to plan for this removal now, with the aid of a tool 

that will help you identified affected data sets. 

A tool is available for download to help identify VSAM data sets that contain the obsolete attributes IMBED, 

REPLICATE, or KEYRANGE. It is available from the software server (ftp.software.ibm.com) in the s390/mvs/tools 

directory as IMBDSHIP.JCL.TRSD. This will need to be downloaded in binary format and untersed using TRSMAIN. 

Note that this tool is provided as is. Instructions for use of the tool are included in the downloaded JCL. 

Note that while no announcement has been made of the specific date or release that data sets with these attributes 

will no longer be able to be opened, it would be prudent to use this tool to identify the data sets in your installation and 

begin converting them to versions that do NOT contain these attributes. IMBED and REPLICATE were intended as 

performance improvements which have been obsoleted by newer cached DASD devices. Striped data sets provide 

much better performance than KEYRANGE, and should be viewed as a candidate for any existing KEYRANGE data 

sets. 



12


� In a future release, IBM plans to withdraw support for zFS multi-file system aggregates. When this support is 

withdrawn, only zFS compatibility mode aggregates will be supported. (A zFS compatibility mode aggregate has a 

single file system per data set.) 

� IBM plans to replace the RMF LDAP backend in a future release of the operating system. The RMF LDAP interface 

currently allows access to RMF performance data from application programs. This functionality will be replaced with a 

Common Information Model (CIM) Monitoring interface which has been provided since z/OS V1.7. 





z/OS V1R6 

9/05 9/06 

z/OS V1R7 

(SystemPac) 

z/OS V1R8 

(SystemPac) 

Migrating to z/OS R8 Part 1 of 3: Get Ready © 2003 2006 IBM Corporation 

z/OS Ordering and Deliverable Key Dates 

Key Dates for z/OS R7 and z/OS R8 ordering: 

� September 16, 2005: General availability of Cryptographic Support for z/OS V1R6/R7 and z/OS.e V1R6/R7 Web 

deliverable (FMID HCR7730). This Web deliverable supports z/OS and z/OS.e V1.6 and V1.7. 

� September 30, 2005: General availability of IBM Health Checker for V1R4/R5/R6 of z/OS and z/OS.e Web 

deliverable. This Web deliverable supports z/OS and z/OS.e V1.4, V1.5, and V1.6. 

� May 26, 2006: General availability of the Enhancements to Cryptographic Support for z/OS V1R6/R7 and z/OS.e 

V1R6/R7 Web deliverable (FMID HCR7731). This Web deliverable supports z/OS and z/OS.e V1.6 and V1.7, and 

replaced the Cryptographic Support for z/OS V1R6/R7 Web deliverable (FMID HCR7730). 

� June 30, 2006: General availability of the IBM zIIP for z/OS and z/OS.e V1R6/R7 Web deliverable. 

� September 15, 2006: First date for ordering z/OS V1.8 ServerPac, SystemPac, CBPDO using CFSW configuration 

support, or ShopzSeries, the Internet ordering tool. Note that most z/OS media (executable code) is shipped only 

through Customized Offerings (ServerPac, SystemPac, and CBPDO). 

� September 29, 2006: z/OS V1.8 planned general availability via ServerPac, CBPDO and SystemPac. 

� October 10, 2006: Recommended last date for submitting z/OS V1.7 orders via the entitled Customized Offerings 

(ServerPac and CBPDO). This date will allow for adequate order processing time. 

� October 23, 2006: Last date for ordering z/OS V1.7 via ServerPac and CBPDO. 

� December 2006: Last date for ordering z/OS V1R4 z990 Exploitation Support feature and z/OS V1R4 Consoles 

Enhancements feature. 

Web deliverables 

Sometimes enhancements are provided as Web deliverables, and not integrated in your ServerPac, CBPDO, or 

SystemPac deliverable. For example, some of the ICSF enhancements are available this way. z/OS Web deliverables are 

available from http://www.ibm.com/eserver/zseries/zos/downloads/. They are packaged as two files that you download: 



9/07 

z/OS R.. planned 

z/OS V1R7 orderable started: 9/16/05 

ServerPac ordering ends: 10/23/06 

Enhancements to Cryptographic Support for z/OS V1R6/R7 

Web deliverable (FMID HCR7731), available starting 5/26/06. 

IBM zIIP for z/OS and z/OS.e V1R6/R7 Web deliverable, 

available starting 6/30/06. 

z/OS V1R6 orderable started: 9/10/04 

ServerPac ordering ended: 10/24/05 

SystemPac ordering ended: 7/24/06 

9/08 

z/OS R.. planned 

z/OS V1R8 orderable starting: 

9/15/06 

ServerPac planned ordering 

ends: 10/07 

13


w A readme file, which contains a sample job to uncompress the second file, transform it into a format that SMP/E 

can process, and invoke SMP/E to RECEIVE the file. This file must be downloaded as text. 

w A pax.z file, which contains an archive (compressed copy) of the FMIDs to be installed. This file needs to be 

downloaded to a workstation and then uploaded to a host as a binary file. 

For Web downloads, you must perform the following tasks: 

1. Allocate a R/W HFS directory on the z/OS driving system where the package will be staged (optional). 

2. Download both parts of the package from the download zone: http://www.ibm.com/eserver/zseries/zos/downloads/ 

3. Run the sample job provided in the README.TXT file. The job will invoke the GIMUNZIP service routine to extract 

the original data from the packages. 

4. Obtain and install service for the target system. Service is not included in Web deliverables. You can obtain service 

for Web deliverables through your regular preventive service deliverables that you use for z/OS. 

5. Install (SMP/E APPLY) the downloaded FMIDs. 




Crypto Support in z/OS Releases 

Release Level Integrated and Available 

z/OS R8 ICSF FMID HCR7731 is incorporated. 

z/OS R6 and 

z/OS R7 

Same level as the current latest Cryptographic web deliverable! 

in R6: z990 Cryptographic Support (FMID HCR770A) is incorporated. 

In R7: z990 Cryptographic Support (FMID HCR7720) is incorporated. 

Cryptographic Support (FMID HCR7730) was available for z/OS R6/R7 as a 

web deliverable on 9/16/05. However, Enhancements to Cryptographic 

Support (FMID HCR7731) is available as a web deliverable since 5/26/06, 

and replaced Cryptographic Support web deliverable. 

z/OS R5 z990 Cryptographic CP Assist Support (FMID HCR7708) is incorporated. 

z990 Cryptographic Support (FMID HCR770A) was a web deliverable for 

z/OS R5. However, z990 and z890 Enhancements to Cryptographic 

Support (FMID HCR770B) is available for z/OS R5 as a web deliverable, and 

replaces z990 Cryptographic Support. 


z/OS ICSF Release Levels 

The support for cryptography (z/OS base element ICSF) has been delivered via web deliverables and release 

incorporations for z/OS R5, R6, R7, and R8. The Web deliverables are available from 

http://www.ibm.com/eserver/zseries/zos/downloads/. You install them using SMP/E in a manner similar to installing with 

CBPDO. 

z/OS Releases and Crypto Web Deliverables 

Deliverable 

General availability 

z/OS V1R5, FMID HCR7708 

March 27, 2004 

incorporated 

z990 Cryptographic Support (for z/OS March 27, 2004 

V1R5) (FMID HCR770A) 

z990 and z890 Enhancements to May 28, 2004 

Cryptographic Support (for z/OS V1R5, 

z/OS V1R4, z/OS V1R3, z/OS V1R2, and 

OS/390 V2R10) (FMID HCR770B) 

z/OS V1R6, FMID HCR770A 

September 24, 2004 

incorporated 

z990 and z890 Enhancements to September 24, 2004 

Cryptographic Support (for z/OS V1R6) 

(FMID HCR770B) 

ICSF 64-bit Virtual Support (for z/OS December 17, 2004 

V1R6) 

(FMID HCR7720) 

Cryptographic Support for z/OS V1R6/R7 September 16, 2005 


Delivery method 

New release of products 

Web deliverable 








14

and z/OS.e V1R6/R7 (FMID HCR7730) 

Enhancements to Cryptographic Support 

for z/OS V1R6/R7 and z/OS.e V1R6/R7 


z/OS V1R7, FMID HCR7720 

incorporated 

Cryptographic Support for z/OS V1R6/R7 

and z/OS.e V1R6/R7 (FMID HCR7730) 

Enhancements to Cryptographic Support 

for z/OS V1R6/R7 and z/OS.e V1R6/R7 


z/OS V1R8, FMID HCR7731 

incorporated 


May 26, 2006 



May 26, 2006 










z/OS V1R8 Ordering 

Program Number: 5694-A01 

Ensure you order the optional priced and unpriced features that you were using 

before! 

Especially remember your export controlled features, if you desire. Here's the 

complete list: 


Communications Server Security Level 3 

No longer any ordering considerations for: 

ICSF: since latest ICSF is integrated into z/OS R8, there are *no* concerns for 

downleveling your ICSF level at this time. 

Tivoli Netview and System Automation: since msys for Operations is no longer in 

z/OS R8 

Order z/OS V1R7 electronically via ShopzSeries! 

When you do this, you can choose to have an electronic ServerPac! 

Notice there is: "z/OS V1 Base" and "z/OS V1 Alternate Base" - pick the right one! 




z/OS V1R8 Ordering 

The program number for z/OS Version 1 Release 8 is 5694-A01. When ordering this program number, remember to 

order all the optional features that you were licensed for in previous releases of z/OS. 

In z/OS V1R8 there are only two export controlled unpriced features: z/OS Security Level 3, and Communications 

Server Security Level 3. z/OS Security Level 3 contains the sub-elements: IBM Tivoli Directory Server for z/OS Security 

Level 3, Network Authentication Service Level 3, OCSF Security Level 3, and System Secure Sockets Layer (SSL) 

Security Level 3, 

Typically, when one new z/OS release becomes orderable in ServerPac and CBPDO, the previous release is orderable 

for only a month. Due to this short overlap, it is very important that you order the z/OS release you need for migration and 

coexistence while it’s still available for ordering. z/OS R4 users should plan to order z/OS R7 before the availability of 

z/OS R8! 

Ordering and Installing z/OS R8 Electronically! 

In many countries you may order z/OS electronically through ShopzSeries. ShopzSeries provides customers a 

self-service capability for planning and ordering S/390 software (and service) upgrades over the Web. It is the strategic 

worldwide self-service ordering system for zSeries software. You can order products through ShopzSeries and have them 

delivered electronically in some countries. 

In most countries, ShopzSeries provides electronic ordering and electronic delivery support for z/OS Service. You can 

access it directly off the ShopzSeries web site at: http://www.ibm.com/software/shopzseries 

When you order the z/OS product on ServerPac from ShopzSeries, you can choose to have it electronically delivered to 

you! This electronic ability was made generally available on January 10, 2005. 



15


Products Related to z/OS R8 

IBM SMP/E for z/OS and OS/390, V3.4 (5655-G44) 

SMP/E is non-exclusive! incorporated into R7, same level in R8 

Availability was September 30, 2005; no charge to z/OS licensed users 

IBM Debug Tool for z/OS V6 R1 (5655-P14) 

Debug Tool no longer incorporated, as of z/OS R5 

IBM Ported Tools for z/OS (5655-M23) - provides OpenSSH function! 

IBM Ported Tools for z/OS: Perl for z/OS Feature (5655-M23)- port of the Perl (version 5.8.7) 

When IBM Ported Tools for z/OS: Perl for z/OS Feature is ordered, it will be sent with IBM Ported Tools for z/OS 

(which contains the OpenSSH function). An order of IBM Ported Tools for z/OS will not include Perl for z/OS 

Feature. OpenSSH and Perl for z/OS functions can be run independently. 

XML Toolkit for z/OS V1 R9 (5655-J51) 

Contains XML V1R8 and V1R7 levels, as well 

IBM 64-bit SDK for z/OS, Java 2 Technology Edition V1 R4 (5655-M30) 

Can be ordered and can coexist with IBM SDK for z/OS, Java 2 Technology Edition V1 R4 

(5655-I56) 

IBM 64-bit SDK for z/OS, Java 2 Technology Edition, V5 (5655-N99) 

Can be ordered and can coexist with IBM 31-bit SDK for z/OS, Java 2 Technology Edition, V5 


(5655-N98) 



SMP/E for z/OS and OS/390 Version 3 Release 4 (5655-G44) 

Beginning with z/OS V1R2 (which was SMP/E V3 R1), SMP/E is nonexclusive because of the introduction of the SMP/E 

stand-alone product. SMP/E V3.4 is available under its own product number and also remains a base element of z/OS. 

This allows customers who are licensed for a currently supported release of z/OS to order and install the latest release of 

SMP/E without having to upgrade their entire operating system. The advantage is that products other than z/OS can 

exploit the packaging and installation enhancements in SMP/E without having to install the prerequisites for a new level of 

the operating system. 

In addition, since SMP/E plays a key role in Internet delivery of software, it allows IBM to exploit the Internet delivery and 

installation technologies in SMP/E sooner without having to wait for customers to migrate to new levels of the operating 

system. SMP/E V3.4 is available at no additional charge to customers. It is intended for customers who have a license for 

z/OS V1 (5694-A01). SMP/E V3.4 is incorporated into z/OS R7, and the same level is also in z/OS R8. 

SMP/E V3.4 provides the following enhancements for this release: 

� SMP/E Internet Service Retrieval: SMP/E Internet Service Retrieval is the latest enhancement in IBM's service 

delivery evolution for the z/OS platform. SMP/E V3.4 will address the common inhibitors to Internet delivery of service, 

and can simplify and automate the entire z/OS service acquisition process. SMP/E Internet Service Retrieval is 

designed to order and retrieve z/OS platform service from a dedicated IBM server via the Internet in one simple step 

right from z/OS. With SMP/E V3.4 you are now able to order and retrieve service on demand to obtain exactly what 

you need when you need it, or you can automate the service delivery process. By scheduling an SMP/E job to run 

once a week, or even every night, you can order and download the latest HOLDDATA and PTFs and have these 

service updates available exactly when you want them. You can request corrective service, three forms of preventive 

service, and even HOLDDATA. 

� Corrective: You can request one or more PTFs by name, or You can request PTFs to resolve specific APARs. 

When you specify one or more APARs, you receive PTFs that resolve the APARs, but only those PTFs that are 

applicable to your environment. 

� Preventive: There are three selection options for preventive service: 

� Critical service includes PTFs that resolve HIPER problems (high impact pervasive) and PTFs in error (PE). 



16


� Recommended service includes all PTFs with a Recommended Service Update SOURCEID (RSUyynn) and 

all PTFs that resolve HIPER problems or PTFs in error (critical service). 

� All service includes all currently available PTFs. 

� HOLDDATA: When you request HOLDDATA you get only the latest 2-years of Enhanced HOLDDATA for the 

entire z/OS platform (see http://service.software.ibm.com/holdata/390holddata.html for further information on 

Enhanced HOLDDATA). 

Your PTF service order is customized to your SMP/E environment using a software inventory file that identifies your 

installed FMIDs and the PTFs already present in your environment. This means you receive only the PTFs you 

request that are applicable to your environment plus any requisites you don't already have on hand. Furthermore, 

your order will not include any PTFs you already have, resulting in an order that is as complete and as small as 

possible that can be downloaded and installed quickly. 

The SMP/E RECEIVE command has been extended to support this Internet Service Retrieval capability. The 

RECEIVE command will use the HTTP 1.0 protocol with SSL to communicate over the Internet with the dedicated 

IBM server. The server accepts the PTF or HOLDDATA request from SMP/E and responds with the information 

necessary to download the files of PTFs and HOLDDATA. SMP/E then uses the FTP protocol to download the files 

from the IBM server to your local z/OS system. 

� ICSF Mitigation: The z/OS Integrated Cryptographic Services Facility (ICSF) is used by SMP/E to calculate SHA-1 

hash values. These hash values are calculated for files within a GIMZIP package to verify the integrity of the data 

within the package. 

SMP/E has been enhanced to use an alternate method to calculate SHA-1 hash values if ICSF is not available for 

use. Although ICSF is the preferred method, SMP/E will no longer require it for use by the GIMZIP and GIMUNZIP 

service routines, nor for the RECEIVE FROMNETWORK or RECEIVE FROMNTS commands. If SMP/E detects ICSF 

is not available, then SMP/E will automatically use an SMP/E Java application class to calculate SHA-1 hash values 

as an alternative. 

� Improved Load Module Build: The load module build phase of the APPLY, RESTORE and LINK LMODS 

commands is being enhanced to be more tolerant of allocation errors for the distribution libraries. This accommodates 

distribution libraries which may be off-line. In this case, SMP/E continues its search for a useable copy of the module 

instead of immediately failing because of the error allocating the distribution library. 

SMP/E V3.4 was available on September 30, 2005. ServerPac orders are built using either the default level of SMP/E 

(which is V3.4) or the lowest supported level of SMP/E that is required for the products in your order. The higher of these 

two SMP/E levels is used. For example, z/OS orders are built with the level of z/OS SMP/E provided in that release of 

z/OS. Subsystem orders are built with SMP/E V3.1, unless a product in your order has a dependency on a higher level of 

SMP/E. Your subsystem order would then be built with the minimum level of SMP/E that satisfies the requirement. The 

level of SMP/E used to build your order is documented in ServerPac Installing Your Order. 

If it may be a while until you migrate to z/OS R8, you may want to consider ordering this separate product early (in a 

CBPDO) in order to take advantage of the new functions in SMP/E right away! 

If you would like to start using SMP/E V3 R4 to process electronic deliverables, then you may order it using ShopzSeries 

(http://www.ibm.com/software/shopzseries) or download SMP/E V3 R3 from the download zone. The download zone can 

be found at: http://www.ibm.com/software/os/ then Downloads (with parallel paths for both OS/390 and z/OS). SMP/E V3 

R3 has been available via the download zone since October 1, 2004. 

IBM Debug Tool for z/OS Version 6 Release 1 (5655-P14) 

The latest available Debug Tool is the IBM Debug Tool for z/OS V6.1. IBM Debug Tool for z/OS is IBM's interactive 

source-level debugging tool for compiled applications. It is a program testing and analysis aid that helps you examine, 

monitor, and control the execution of application programs written in C, C++, COBOL, or PL/I on a z/OS or OS/390 

system. By using the disassembly view, Debug Tool also provides support for programs compiled with the NOTEST 

compiler option, or applications that include other languages. 

Debug Tool for z/OS V6.1 includes the following new features and enhancements (among many): 

� Breakpoints, monitors, and settings can now be saved and restored across debug sessions independent of the 

environment in which Debug Tool is running. 

� A set of prefix commands has been added so that you can interact with the Monitor window. The prefix commands 

that are available in the Monitor window will generate the corresponding Debug Tool command line command. These 

new prefix commands provide a better way to interact with the Monitor window. 

� You can now set an AT ENTRY breakpoint without Debug Tool knowing about the program ahead of time. This 

enhancement makes it easier to specify breakpoints. 




� The SET LONGCUNAME command has been updated to support the AT ENTRY breakpoint. 

� New suboptions have been added to the FIND command to enable you to navigate through searches more 

effectively. Changes have also been made to make the FIND command more like ISPF's FIND command. 

� Debug Tool can now debug C and C++ programs compiled with the new DEBUG compile option. The DEBUG 

compile option was available with C/C++ for z/OS V1.5. 

� The NAMES command has been added to allow you to have some control over the load modules and compile units 

that Debug Tool displays and debugs. The NAMES EXCLUDE function allows you to inform Debug Tool that certain 

load modules and/or compile units are not to be debugged (for example, data modules). The NAMES INCLUDE 

function allows you to inform Debug Tool that certain load modules and/or compile units that would normally be 

considered non-debuggable are to be debugged as user programs. 

� The AT CHANGE command has been enhanced to support level 88 data items. 

� Support has been added to debug PL/I applications where the programs in the application are compiled with a 

mixture of new and old IBM PL/I compilers such as IBM Enterprise PL/I for z/OS V3, IBM VisualAge PL/I for z/OS V2, 

IBM PL/I for MVS and VM V1, and IBM OS PL/I V2. 

There have been previous levels of the Debug Tool (IBM Debug Tool for z/OS Version 5 Release 1 (5655-M18), IBM 

Debug Tool for z/OS and OS/390 Version 4 Release 1 (5655-L24), Version 1 Release 3 (5688-I94) and IBM Debug Tool 

for z/OS and OS/390 Version 3 Release 1 (5655-H32). These levels are all higher than the level that was shipped in 

z/OS V1.4. z/OS R4 contained the CODE/370 V1R2 level of the debugger. As of z/OS V1R5, optional feature C/C++ with 

Debug Tool is no longer in z/OS. The functional replacement that you will need to order for that feature is the C/C++ 

without Debug Tool feature in z/OS and also the independent standalone program product - IBM Debug Tool for z/OS 

V6.1 (5655-P14). 

IBM Ported Tools for z/OS Version 1 Release 1 (5655-M23) 

IBM Ported Tools for z/OS is designed to provide the select features of secure shell known as OpenSSH enabling for: 

� Authentication for both the client and server 

� Privacy through encryption 

� Data integrity 

� Authorization 

� Forwarding or tunneling 

� An optional feature of compression 

� Communication using SSH1 and SSH2 protocols. 

Ordering information: It is an unpriced program product, that can be ordered with z/OS. It can run on z/OS R4 and 

higher. It has been generally available since May 28, 2004. The program numbers are IBM Ported Tools for z/OS 

(5655-M23) and IBM Ported Tools for z/OS Software and Subscription (5655-M29). 

IBM Ported Tools for z/OS: Perl for z/OS Feature (5655-M23) 

IBM Ported Tools for z/OS: Perl for z/OS Feature provides a port of the Perl (version 5.8.7) scripting language to the z/OS 

UNIX platform. Perl (Practical Extraction and Report Language) is a very popular general-purpose programming language 

that is widely used on UNIX and other computing platforms. 

Support for z/OS UNIX has been available for several years in the open-source version of Perl. Building this version of 

Perl is often difficult even for experienced users, and requires access to several GNU utilities. 

Perl for z/OS is preconfigured and precompiled, and is designed to eliminate the need for those complicated tasks. 

EBCDIC-related factors in the Perl application have been addressed; therefore, it is anticipated that Perl applications can 

run with data generated entirely in the z/OS UNIX environment. As with any z/OS related programming language, Perl 

programs that process data originating from non-EBCDIC (typically ASCII) systems must still convert this data from ASCII 

to EBCDIC, and vice versa. Tips for conversion can be found in IBM Ported Tools for z/OS: Perl for z/OS User's Guide 

(SA23-1347) at http://www.ibm.com/servers/eserver/zseries/zos/bkserv/ or 

http://www.ibm.com/servers/eserver/zseries/zos/unix/port_tools.html . 

Ordering information: Perl for z/OS is an unpriced feature of the IBM Ported Tools for z/OS, an unpriced licensed 

program. It has been generally available since June 16, 2006. The program numbers are IBM Ported Tools for z/OS 

(5655-M23) and IBM Ported Tools for z/OS Software and Subscription (5655-M29). 




XML Toolkit for z/OS Version 1 Release 9 (5655-J51) 

The C++ XML parser within this toolkit is a port of the IBM XML Parser for C++, XML4C V5.6, which is based on Apache's 

Xerces C++ V2.6 parser. 

� Specify that XML Schema annotations not be generated 

� Specify that XML Schema annotations not be regenerated when deserializing a grammar 

� Turn off default entity resolution 

� Perform schema-only validation when there is a Document Type Definition (DTD) 

The IBM XSLT Processor for C++, XSLT4C V1.10 within this toolkit, which is based on Apache's Xalan C++ V1.10 XSLT 

processor, has been updated with: 

� XML1.1 and Namespaces for XML1.1 support 

� Improved pluggable memory management 

� Improvements in Xalan XML serializers designed to provide improved performance. 

Support for the Java XML Parser and Processor is not packaged with the IBM XML Toolkit for z/OS. This support can 

now be obtained within the IBM SDK for z/OS, product offerings. 

The XML Toolkit for z/OS is based on open-source software developed by the Apache Software Foundation that does not 

provide for compatibility with prior releases. Care must be taken when installing IBM XML Toolkit for z/OS, V1.9, because 

the XML parsers and the XSLT processors in this toolkit are not compatible with previous releases. Please note, the IBM 

XML Toolkit for z/OS, V1.9 packages the latest XML parser and XSLT processor from Apache as well as those XML 

parsers and the XSLT processors from previous XML Toolkits so that applications that are using XML Toolkit for z/OS, 

V1.8 or XML Toolkit for z/OS, V1.7 will continue to run. This is intended to allow for continued use of these levels of the 

toolkit by applications that have written to their specific APIs. 

Ordering information: The availability date was June 16, 2006. The program numbers are XML Toolkit for z/OS 

(5655-J51), and XML Toolkit for z/OS S&S (5655-I30). 

IBM 64-bit SDK for z/OS, Java 2 Technology Edition Version 1 Release 4 (5655-M30) 

64-Bit SDK for z/OS, Java 2 Technology Edition, V1.4 is a Java SDK that contains a reengineered Java 2 virtual machine 

at the SDK 1.4 level and the IBM Just-in-Time (JIT) compiler. The program is a key building block for developing 

e-business applications. 64-Bit SDK for z/OS, Java 2 Technology Edition, V1.4 passes the Java SDK 1.4 compatibility test 

and provides the stability, service, and scalability you expect from a zSeries program. 64-Bit SDK for z/OS, Java 2 

Technology Edition, V1.4 provides: 

� Support for Java application programming in a 64-bit environment 

� Java 2 APIs at the SDK 1.4 level 

� Continuation of the "write once, run anywhere" Java paradigm 

� Java Record I/O (JRIO) 

� XML support 

� SAF and cryptography support 

� Support for the IBM zSeries Application Assist Processors available on the z9 EC, z9 BC, z990, and z890 servers 

� Additional reliability, availability, and serviceability (RAS) enhancements 

64-Bit SDK for z/OS, Java 2 Technology Edition, V1.4 requires z/OS V1 R6. IBM 64-Bit SDK for z/OS, Java 2 

Technology Edition, Version 1.4 (5655-M30) has the same functions as IBM SDK for z/OS, Java 2 Technology Edition 

(5655-I56), with the exception of: 

� Persistent reusable function 

� Sharing class objects between Java virtual machine (JVM) processes running in the same address space 

64-Bit SDK for z/OS, Java 2 Technology Edition, V1.4 (5655-M30) and SDK for z/OS, Java 2 Technology Edition, 

2 V1.4 (5655-I56) are independent products and can co-exist on the same z/OS system. 

Programs interacting with the 64-bit Java product, whether launching the JVM or being called from the JVM through the 

JNI interface, must be 64-bit programs. Programs dependent on JNI interfaces may require changes at the interface 

boundary to conform to 64-bit data types. Application JNI routines written in C will need to be recompiled for 64-bit, which 

may require some code changes. For details on incompatibilities, visit 

http://www.ibm.com/servers/eserver/zseries/software/java/ 




Ordering information: General availability occurred on December 17, 2004. The program numbers are IBM 64-Bit SDK 

for z/OS, Java 2 Technology Edition, V1.4 (5655-M30), and IBM 64-Bit SDK for z/OS, Software Subscription and Support 

(5655-I48). 

IBM SDK for z/OS, Java 2 Technology Edition, Version 1.4 (5655-I56) 

SDK for z/OS, Java 2 Technology Edition, V1.4 is a Java SDK that contains a reengineered Java 2 virtual machine at the 

SDK 1.4 level and the IBM Just-in-Time (JIT) compiler. The program is a key building block for developing e-business 

applications. SDK for z/OS, Java 2 Technology Edition, V1.4 passes the Java SDK 1.4 compatibility test and provides the 

stability, service, and scalability you expect from a zSeries program. 

SDK for z/OS, Java 2 Technology Edition, V1.4 provides: 

� Java 2 APIs at the SDK 1.4 level 


� New Java 2 function, including XML 

� Exploitation of enhanced z/OS linkage capabilities (XPLINK) 

� Enhanced IBM JIT compiler 

� JRIO 

� Security services 

� IBM enhanced memory management 

� Persistent reusable Java Virtual Machine (JVM) Support 


SDK for z/OS, Java 2 Technology Edition, V1.4 includes improved dump capability, tracing, and problem determination, 

as well as isolation to better diagnose and fix software defects. 

Ordering information: The program numbers are IBM SDK for z/OS, Java 2 Technology Edition, Version 1.4 (5655-I56), 

and IBM SDK for z/OS Service and Subscription (5655-I48) 


64-bit SDK for z/OS, Java 2 Technology Edition, V5 is a Java SDK that contains a reengineered Java 2 virtual machine at 

the SDK 5 level and the IBM Just-in-Time (JIT) compiler. The program is a key building block for developing on demand 

applications. 64-bit SDK for z/OS, Java 2 Technology Edition, V5 is designed to be compliant with the Java SDK 5 

compatibility test and is intended to provide the stability, service, and scalability you expect from a zSeries program. 

64-bit SDK for z/OS, Java 2 Technology Edition, V5 is designed to provide: 


� Java 2 APIs at the SDK 5 level 




� System Authorization Facility (SAF) and cryptography support 

� Use the System z9 and zSeries Application Assist Processors (zAAPs) available on z9 EC, z9 BC, z990 and z890 

servers 


64-bit SDK for z/OS, Java 2 Technology Edition, V5 includes similar dump capability, tracing, and problem determination 

as in SDK for z/OS, Java 2 Technology Edition, V1.4 (5655-I56). 

Ordering information: The program numbers are IBM 64-bit SDK for z/OS, Java 2 Technology Edition, V5 (5655-N99), 

and IBM SDK for z/OS Software Subscription and Support (5655-I48) 


31-bit SDK for z/OS, Java 2 Technology Edition, V5 is a Java SDK that contains a reengineered Java 2 virtual machine at 

the SDK 5 level and the IBM Just-in-Time (JIT) compiler. The program is a key building block for developing on demand 

applications. 31-bit SDK for z/OS, Java 2 Technology Edition, V5 is compliant with the Java SDK 5 compatibility test and 

is designed to provide the stability, service, and scalability you expect from a zSeries program. 

31-bit SDK for z/OS, Java 2 Technology Edition, V5 is designed to provide: 




� Java 2 APIs at the SDK 5 level 




� System Authorization Facility (SAF) and cryptography support 

� Use the System z9 and zSeries Application Assist Processors (zAAPs) available on z9 EC, z9 BC, z990 and z890 

servers 


31-bit SDK for z/OS, Java 2 Technology Edition, V5 includes similar dump capability, tracing, and problem determination 

as in SDK for z/OS, Java 2 Technology Edition, V1.4 (5655-I56). 

Ordering information: The program numbers are IBM 31-bit SDK for z/OS, Java 2 Technology Edition, V5 (5655-N98), 

and IBM SDK for z/OS Software Subscription and Support (5655-I48) 

Not mentioned in foil above... 


XML C++ Parser for the OS/390 2.10 C++ Compiler for z/OS (Web Deliverable) 

The XML C++ Parser for the OS/390 V2.10 C++ Compiler for z/OS (XML C++ Parser 1.4 for z/OS) provides continued 

support for the OS/390 V2.10 C++ Compiler shipped within z/OS. The XML C++ Parser 1.4 for z/OS is a repackaging of 

the C++ parser originally shipped within the IBM XML Toolkit for z/OS and OS/390 V1.4. This Web deliverable was 

available on September 24, 2004 at 

http://www.ibm.com/servers/eserver/zseries/software/xml/download/cparser_download.html . 

IBM Infoprint Transform products 

IBM is replacing the Infoprint Server Transforms for z/OS product with five separately orderable offerings. These products 

are available June 17, 2005 and offer: 

* Improved image quality in PostScript and PDF to AFP converted output 

* Improved font support and Latin2 language support in PCL to AFP 

* Support for later levels of the data streams converted to AFP 

* New function in the AFP to PDF transform 

* Support for additional AFP capabilities in all transforms from AFP 

* Separate availability of the Coaxial Printer Support function with additional support 

1) Infoprint Transforms to AFP V2.1 for z/OS (5655-N60) 

Transforms that are included in this offering are: 

* PCL to AFP (supports PCL6) 

* PostScript to AFP (supports PostScript Level 3 and earlier, and produces monochrome output) 

* PDF to AFP (supports PDF 1.4 and earlier, and produces monochrome output) 

* SAP/R3 to AFP 

2) Infoprint Transform for AFP to HP PCL V2.1 for z/OS (5655-P19) transforms AFP to PCL5, PCL5c, and PCL5e 

(result is PCL text and image). 

3) Infoprint Transform for AFP to Adobe PDF V2.1 for z/OS (5655-P20) transforms AFP to PDF 1.4 and has been 

significantly enhanced to include new capabilities that support richer PDF content, and the ability to encrypt the document 

while converting to prevent unauthorized use of the PDF document. AFP documents containing indexing, page grouping, 

and hyperlink commands will be converted into PDF documents with bookmarks for easier navigation using the Acrobat 

reader. 

Documents can also be enhanced to provide richer content and flexible access to related information. The AFP linking 

command (LLE) can also be used to refer to objects external to the AFP document. The AFP to PDF transform will now 

process these links to include the external reference in the resulting PDF document. This capability can be used, for 

example, to include an Internet address in the PDF document. 

4) Infoprint Transform for AFP to Adobe PostScript V2.1 for z/OS (5655-P21) transforms AFP to PostScript Level 3. 

In addition to enhanced PDF output, all of the transforms now support many AFP capabilities not supported by the 

existing Infoprint Server Transforms for z/OS product. New AFP functions now supported include: 




* Enhanced n-up formatting 

* Record formatting page definitions 

* XML page definitions 

* PDF and GIF in object containers 

* Additional bar code symbologies, including 2D bar codes 

The new transforms also provide a way for customers to configure paper sizes in the transforms. This function is provided 

as a USERMOD. 

5) Infoprint Coaxial Printer Support V2.1 for z/OS (5655-N62). The new Infoprint Coaxial Printer Support offering 

replaces the corresponding feature in the existing Infoprint Server Transforms for z/OS offering. It supports printing in IP 

PrintWay basic mode and IP PrintWay extended mode, which was introduced in Infoprint Server V1.5 for z/OS. In 

addition, multiple copies are now supported in IP PrintWay extended mode when printing on coaxial printers. 




z/OS Policy and Directions 

Release Frequency 

z/OS V1 R8 planned GA is Sept 29, 2006 

This is another delivery on our annual release cycle 

All subsequent releases are planned for GA in September 

Coexistence-Migration-Fallback 

Service Support 

Migrating to z/OS R8 Part 1 of 3: Get REady 



Release Frequency 

In response to customer feedback that the 6-month release cycle was too short and complicated customer migration 

plans, IBM announced in August 2002 that the release schedule for z/OS has changed to a 12-month cycle. The vast 

majority of z/OS customers migrate to new releases every 12 to 18 months. Less frequent releases in the future will allow 

IBM to provide even more integration testing for z/OS and related IBM middleware. It will also enable IBM to align the 

coexistence, migration, and fallback policy with the service policy, with the annual releases. 

Starting with z/OS R6, IBM intends to deliver releases annually, with general availability in September. This 

predictable release cycle will enable you to better plan your migration, freeing you to increase the value of your computing 

environment to your business and deliver better service to your end users. New z/OS functions will continue to be 

delivered between releases through the normal maintenance stream or as Web deliverables. In addition, significant new 

functions may be delivered between releases as features of the product (such as what we've seen for the z990 support). 

z/OS V1R8 is the third release to be delivered on this annual release cycle. 

These statements regarding the new release strategy represent current intentions of IBM. Any reliance on these 

statements is at the relying party's sole risk and will not create any liability or obligation for IBM. All statements regarding 

IBM's plans, directions, and intent are subject to change or withdrawal without notice. 



17

z/OS R8 Coexistence 

z/OS 

R4 

z/OS 

R5 


z/OS 

R6 

z/OS 

R7 

Starting with z/OS R6, IBM has aligned the coexistence, fallback, and 

migration policy with the service policy. 

z/OS R5, z/OS R6, z/OS R7, and z/OS R8 are supported for coexistence, migration, and 

fallback 

Prepare now! The lowest release planned for coexistence, migration, and fallback support on 

z/OS R8 is z/OS R5. If you are on z/OS R4 you should be planning for your migration to z/OS 

R7! 

Only JES2/JES3 that can coexist with the shipped JES can be "staged" on 

z/OS. This is enforced in z/OS V1 R8. That means: 

z/OS R5 JES2 thru z/OS R8 JES2 are supported for coexistence, migration, and fallback 

z/OS R5 JES3 thru z/OS R8 JES3 are supported for coexistence, migration, and fallback 




Understanding Coexistence 

Coexistence occurs when two or more systems at different software levels share resources. The resources could be 

shared at the same time by different systems in a multisystem configuration, or they could be shared over a period of time 

by the same system in a single-system configuration. Examples of coexistence are two different JES releases sharing a 

spool, two different service levels of DFSMSdfp sharing catalogs, multiple levels of SMP/E processing SYSMODs 

packaged to exploit the latest enhancements, or an older level of the system using the updated system control files of a 

newer level (even if new function has been exploited in the newer level). 

The sharing of resources is inherent in multisystem configurations that involve Parallel Sysplex implementations. But 

other types of configurations can have resource sharing too. Examples of configurations where resource sharing can 

occur are: 

� A single processor that is time-sliced to run different levels of the system, such as during different times of the day 

w A single processor running multiple images by means of logical partitions (LPARs) 

w Multiple images running on several different processors 

w Parallel Sysplex or non-Parallel Sysplex configurations 

Note: The term coexistence does not refer to z/OS residing on a single system along with VSE/ESA, VM/ESA, or z/VM in 

an LPAR or as a VM guest. 

z/OS systems can coexist with specific prior releases. This is important because it gives you flexibility to migrate systems 

in a multisystem configuration using rolling IPLs rather than requiring a systems-wide IPL. The way in which you make it 

possible for earlier-level systems to coexist with z/OS is to install coexistence service (PTFs) on the earlier-level systems. 

You should complete the migration of all earlier-level coexisting systems as soon as you can. Keep in mind that the 

objective of coexistence PTFs is to allow existing functions to continue to be used on the earlier-level systems when run 

in a mixed environment that contains later-level systems. Coexistence PTFs are not aimed at allowing new functions 

provided in later releases to work on earlier-level systems. 



z/OS 


z/OS 

R9 

z/OS 

R10 

18


Rolling z/OS across a multisystem configuration 

A rolling IPL is the IPL of one system at a time in a multisystem configuration. You might stage the IPLs over a few hours 

or a few weeks. The use of rolling IPLs allows you to migrate each z/OS system to a later release, one at a time, while 

allowing for continuous application availability. For example, data sharing applications offer continuous availability in a 

Parallel Sysplex configuration by treating each z/OS system as a resource for processing the workload. The use of rolling 

IPLs allows z/OS systems running these applications to be IPLed one at a time, to migrate to a new release of z/OS, while 

the applications continue to be processed by the other z/OS systems that support the workload. By using LPAR 

technology, you can use rolling IPLs to upgrade your systems without losing either availability or capacity. 

You can use rolling IPLs when both of the following are true: 

w The release to which you're migrating falls is supported for coexistence, fallback, and migration with the releases 

running on the other systems. 

w The appropriate coexistence PTFs have been installed on the other systems in the multisystem configuration. 

Even when you're using applications that do not support data sharing, rolling IPLs often make it easier to schedule z/OS 

software upgrades. It can be very difficult to schedule a time when all applications running on all the systems in a 

multisystem configuration can be taken down to allow for a complex-wide or Parallel Sysplex-wide IPL. The use of rolling 

IPLs not only enables continuous availability from an end-user application point of view, but it also eliminates the work 

associated with migrating all z/OS systems in a multisystem configuration at the same time. 

Understanding fallback 

Fallback (backout) is a return to the prior level of a system. Fallback can be appropriate if you migrate to z/OS R8 and, 

during testing, encounter severe problems that can be resolved by backing out the new release. By applying fallback 

PTFs to the "old" system before you migrate, the old system can tolerate changes that were made by the new system 

during testing. 

Fallback is relevant in all types of configurations, that is, single-system or multisystem, with or without resource sharing. 

As an example of fallback, consider a single system that shares data or data structures, such as user catalogs, as you 

shift the system image from production (on the "old" release) to test (on the new release) and back again (to the old 

release). The later-level test release might make changes that are incompatible with the earlier-level production release. 

Fallback PTFs on the earlier-level release can allow it to tolerate changes made by the later-level release. 

As a general reminder, always plan to have a backout path when installing new software by identifying and installing any 

service required to support backout. 

Fallback is at a system level, rather than an element or feature level, except for z/OS JES2 and z/OS JES3. That is, 

except for z/OS JES2 and z/OS JES3, you can't back out an element or feature; you can only back out the entire z/OS 

product. z/OS JES2 and z/OS JES3 fallback can be done separately as long as the level of JES is supported with the 

release of z/OS and any necessary fallback PTFs are installed. 

Fallback and coexistence are alike in that the PTFs that ensure coexistence are the same ones that ensure fallback. 

Note: Keep in mind that new functions can require that all systems be at z/OS V1R8 level before the new functions can 

be used. Therefore, be careful not to exploit new functions until you are fairly confident that you will not need to back out 

your z/OS V1R8 systems, as fallback maintenance is not available in these cases. You should consult the appropriate 

element or feature documentation to determine the requirements for using a particular new function. 

Which releases are supported for coexistence, fallback, and migration? 

Starting with z/OS R6, IBM has aligned the coexistence, fallback, and migration policy with the service policy. 

IBM intends to continue with the practice of providing service support for each release of z/OS for three years following 

its general availability (GA) date. IBM, at its sole discretion, may choose to leave a release supported for more than three 

years. This change to the coexistence, fallback, and migration policy is effective starting with z/OS R6 (that is, the first 

release of the new annual release cycle). As a general rule, this means that three releases will be supported for 

coexistence, fallback, and migration over a period of three years. This represents an increase of one year over the 

two-year period provided by the current coexistence, fallback, and migration policy of four releases under a six-month 

release cycle. The intention of this policy change is to simplify and provide greater predictability to aid in release 

migrations. 

Exceptions are: 

w In some cases, more than three releases may be coexistence, fallback, and migration supported if IBM at its sole 

discretion chooses to provide service support for greater than three years for a release. 




w Any z/OS release having three or fewer months of service remaining at general availability of a new release will not 

be coexistence, fallback, or migration supported with the new release. 

Thus, except for JES2 and JES3, z/OS V1R8 is coexistence, fallback, and migration supported with the following 

four z/OS releases: V1R7, V1R6, and V1R5. This means that: 

w Coexistence of a V1R8 system with a V1R7, V1R6, or V1R5 system is supported. 

w Fallback from V1R8 to V1R7, V1R6, or V1R5 is supported. 

w Migration to V1R8 from V1R7, V1R6, or V1R5 is supported. 

For JES2 and JES3, the way in which four consecutive releases is determined is different than for the rest of the 

operating system. If a JES2 or JES3 release is functionally equivalent to its predecessor (that is, its FMID is the same), 

then the release is considered to be the same JES release. Thus, z/OS V1R8 JES2 and JES3 are coexistence, 

fallback, and migration supported with the following JES releases: V1R8, V1R7, and V1R6-V1R5 (both are 

functionally equivalent). 

As of z/OS V1R2, compliance to the coexistence, fallback, and migration policy for JES2 and JES3 is enforced. A 

migration to a JES2 or JES3 release level that is not supported by the policy results in the following: 

w For JES2: If the JES2 release level for a system that is initializing is not compatible with the other active systems in 

the JES2 MAS, message HASP710 is issued and the JES2 address space for the initializing system is terminated. 

w For JES3: If the JES3 release level for a local is not compatible with the global in a JES3 multisystem complex, 

message IAT2640 is issued and the JES3 local is not allowed to connect to the global. 

The z/OS coexistence, fallback, and migration policy applies to the elements and features of z/OS, not to 

customer-developed applications, vendor-developed applications, or IBM products that run on z/OS. IBM performs 

integration testing and will provide service as necessary to support the z/OS coexistence, fallback, and migration policy. 

See the table below for a summary of current and planned coexistence, fallback, and migration support. 

These statements represent IBM's current intentions. IBM reserves the right to change or alter the coexistence, fallback, 

and migration policy in the future or to exclude certain releases beyond those stated. IBM development plans are subject 

to change or withdrawal without further notice. Any reliance on this statement of direction is at the relying party's sole risk 

and does not create any liability or obligation for IBM. 

Releases that are coexistence, fallback, and migration supported with z/OS V1R6 and beyond 

z/OS 

release 

(see 

note 1) 

R6 

R7 


Releases that 

are coexistence, 

fallback, and 

migration 

supported with 

the release in 

column one (see 

note 1) 

Explanation (see note 2) 

R6, R5, R4, R3 The new policy starts. General availability of R6 was September 2004. R2 would be the 

oldest service-supported release at that time and therefore the oldest release that is 

coexistence, fallback, and migration supported. However, its end-of-service date (October 

2004) is within three months of R6 general availability (September 2004), so R3 becomes the 

oldest release that is coexistence, fallback, and migration supported with R6. 

R7, R6, R5, R4 General availability of R7 was September 30, 2005. R4 is the oldest release that is service 

supported at that time and therefore the oldest release that is coexistence, fallback, and 

migration supported with R7. 

R8, R7, R6, R5 Planned general availability of R8 is September 29, 2006. R4 is planned to be the oldest 

release that is service supported at that time because its end-of-service date was extended 

by 18 months to 31 March 2007. However, R4 is not planned to be coexistence, fallback, 



R9 

R10 

R9, R8, R7 

R10, R9, R8 


and migration supported with R8. Therefore, R5 becomes the oldest release that is 

coexistence, fallback, and migration supported with R8. 

Planned general availability of R9 is September 2007. R7 is planned to be the oldest release 

that is service supported at that time and therefore the oldest release that is coexistence, 

fallback, and migration supported with R9. 

Planned general availability of R10 is September 2008. R8 is planned to be the oldest 

release that is service supported at that time and therefore the oldest release that is 

coexistence, fallback, and migration supported with R10. 

Notes: 

1. For readability, the version numbers have been omitted from the releases shown. Also, release numbering of 

future releases (later than R7) is for illustrative purposes and is not a guarantee of actual release numbers. 

2. Future general availability (GA) dates are projections based on the annual release cycle. Future end of service 

(EOS) dates are projections based on the 3-year service policy. 



z/OS Service Policy 


Release serviceable for three years following GA 

Service on last release of a version might be extended 

At least 12 months notice before withdrawing service 

Handy website: 

http://www.ibm.com/servers/eserver/zseries/zos/support/zos_eos_dates.html 

General Availability Service Expiration 

z/OS V1R4 27 September 2002 Announced to be 31 March 2007 

z/OS V1R5 26 March 2004 Announced to be 31 March 2007 

z/OS V1R6 24 September 2004 Announced to be 30 September 2007 

z/OS V1R7 30 September 2005 Planned to be September 2008 

z/OS V1R8 29 September 2006 Planned to be September 2009 


LOOK! 



Service Policy 

IBM's current policy is to provide maintenance (service) for each release of z/OS for three years following their general 

availability (GA) date. However, service on the last release of a version might be extended beyond the intended 

three-year period. Prior to withdrawing service for any version or release of z/OS, IBM intends to provide at least 12 

months notice. The service policy for z/OS also applies to any enhancements (including but not limited to web 

deliverables), such as the z/OS V1R4 enhancements that were provided to support the z990 server. 

See the table below for expiration dates for service support. Planned EOS dates are based on the 3-year service policy. 

Version and release General availability (GA) End of service (EOS) 

OS/390 V2R8 

24 September 1999 Occurred 30 September 2002 

OS/390 V2R9 

31 March 2000 

Occurred 31 March 2003 

OS/390 V2R10 

29 September 2000 Occurred 30 September 2004 

z/OS V1R1 

30 March 2001 


z/OS V1R2 

26 October 2001 Occurred 31 October 2004 

z/OS V1R3 

29 March 2002 


z/OS V1R4 

27 September 2002 31 March 2007 (announced) 

Note: This is 18 months longer than the normal 

three-year service period. 

z/OS V1R5 

26 March 2004 

31 March 2007 (announced) 

z/OS V1R6 

24 September 2004 Announced to be 30 September 2007 

z/OS V1R7 

30 September 2005 September 2008 (planned) 


29 September 2005 September 2009 (planned) 

Check out http://www.ibm.com/servers/eserver/zseries/zos/support/zos_eos_dates.html for a handy list of all end of 

service dates (back to MVS/ESA V4!). 



19


Positioning for z/OS R8 

Read Documentation and PSP buckets 

z/OS Migration and z/OS and z/OS.e Planning for Installation 

Software PSP buckets: ZOSV1Rx: ZOSGEN, SERVERPAC, ... 

Hardware PSP buckets: 2094DEVICE, 2096DEVICE, 2084DEVICE, 2086DEVICE, 2064DEVICE, 

2066DEVICE. Use the Technical Help Database for PSP buckets! 

PSP buckets no longer shipped in ServerPac or CBPDO! Use web site! 

DASD Storage Requirements 

z/OS R5 z/OS R6 z/OS R7 z/OS R8 

Target 5,160 5,277 5,375 5,456 

DLIB 7,212 7,338 7,455 7,362 

HFS 2,200 2,800 

(some growth!) 

Ensuring System Requirements Are Satisfied 

Driving System Requirements 

Target System Requirements 

Hardware and Software 

Coexistence System Requirements 

Migration Actions You Can Do NOW 


2,800 2,800 



z/OS Documentation: Where to Start 

To gain an overview of z/OS and plan for the installation, review: 

� z/OS V1 R8.0 Introduction and Release Guide (GA22-7502) 

� z/OS and z/OS.e V1R8 Planning for Installation (GA22-7504) 

� zSeries Platform Test Report for z/OS and Linux Virtual Servers (formerly, the z/OS Parallel Sysplex Test Report) 

To install z/OS, review Preventive Service Planning (PSP) Buckets: 

� ServerPac (if using ServerPac to install) 

� z/OS and individual elements 

� Hardware 

In addition, to install z/OS using ServerPac, review: 

� ServerPac: Using the Installation Dialog (SC28-1244) 

� The custom-built installation guide, ServerPac: Installing Your Order 

To install z/OS using CBPDO, review the z/OS Program Directory 

PSP Buckets 

z/OS, and most products that run on it, provide files containing information that became available after the product 

documents were printed. Kept on IBM's RETAIN system and also available using IBMLink, these files are called 

preventive service planning (PSP) "buckets", or just "PSPs". PSP buckets are identified by an upgrade identifier, and 

specific parts of them are called subsets. Each upgrade contains information about a product. Subsets contain 

information about specific parts of a product. For example, the z/OS PSP bucket has subsets for the BCP, JES2, 

ServerPac, and others. 

For software upgrades for ServerPac and CBPDO installations, refer to z/OS Program Directory. For software upgrades 

for SystemPac installations, the upgrade is CUSTOMPAC and the subsets are SYSPAC/FVD (for full volume dump 

format) and SYSPAC/DBD (for dump-by-data-set format). 

At the beginning of each PSP bucket is a change index. For each subset, the change index identifies the date of the latest 

entries in each section. You can quickly determine whether there are new entries you need to read by checking the 

change index. 



sizes in 3390 cylinders 

20


Since z/OS V1R7, the contents of PSP buckets are no longer shipped with CBPDO and ServerPac orders. Instead of the 

actual PSP information, you now receive the names of relevant upgrades and subsets, and you’re directed to the PSP 

Web site (https://techsupport.services.ibm.com/server/390.psp390) for the contents of the buckets. This ensures that you 

see the latest PSP information, as the PSP information that was provided with an order was current only on the day the 

order was created. 

The upgrade for the z/OS R8 PSP bucket is ZOSV1R8. Recognizing that there are many PSP buckets to review, z/OS 

uses descriptive element names, instead of FMIDs for the subsets. This reduces the number of PSP buckets that must be 

reviewed, since most elements are composed of multiple FMIDs. There are subsets in the ZOSV1R8 upgrade for general 

topics (ZOSGEN), and for the ServerPac deliverable (SERVERPAC) that should be reviewed also. DFSMS is 

consolidated into one subset. All PSP upgrades and subset IDs are listed in the z/OS Program Directory. However, the 

non-exclusive elements' stand-alone product upgrade and subsets are used. 

Hardware PSP upgrade identifiers 

Hardware PSP bucket upgrade IDs are in the form xxxxDEVICE and contain the latest software dependencies for the 

hardware, and recommended PTFs and APARs required for specific processor models. The PSP hardware upgrade 

identifiers are: 

w 2094DEVICE for the z9 EC server 

w 2096DEVICE for the z9 BC server 

w 2084DEVICE for the z990 server 




Tip: To simplify finding the appropriate PSP bucket and identifying which PTFs listed in the PSP bucket need to be 

installed on your system, you can use the Technical Help Database for Mainframe Preventive Service Planning Buckets 

(http://www14.software.ibm.com/webapp/set2/psp/srchBroker) and the Enhanced PSP Tool (EPSPT). The Web site 

provides a search capability as well as pull down lists for types of PSP buckets. The types supported include Processors, 

z/OS, and Functions. So you can simply select the processor you are preparing for and click Go. 

DASD Storage Requirements 

If you are migrating to z/OS R8 from z/OS R5 or you will have a different product set than your previous release, you will 

see increased need for DASD. How much more depends on what levels of products you are running. Keep in mind the 

DASD required for your z/OS system includes (per the z/OS Policy). That is, it includes ALL elements, ALL features that 

support dynamic enablement, regardless of your order, and ALL unpriced features that you ordered. This storage is in 

addition to the storage required by other products you might have installed. All sizes include 15% freespace to 

accommodate the installation of maintenance. 

The total storage required for z/OS data sets is listed in the space table in the z/OS Program Directory and z/OS and 

z/OS.e Planning for Installation. 

For z/OS R8: 

� The total storage required for all the target data sets is 5,456 cylinders on a 3390 device. 

� The total storage required for all the distribution data sets listed in the space table is 7,362 cylinders on a 3390 

device. 

� The total HFS storage is 2,800 cylinders on a 3390 device for the ROOT HFS and 50 cylinders for the /etc HFS. 

� The total storage required for the SMP/E SMPLTS is 0 3390 cylinders (there are no load modules in z/OS R8 that are 

both cross-zone and use CALLLIBs, thus the SMPLTS is not needed for permanent storage for the z/OS product 

itself). 




Driving System Requirements - ServerPac via Tape 

Minimum to Install z/OS R8 ServerPac via tape: 

1. Any one of the following: 

z/OS R5 with PTFs (several for LE since ServerPac uses LE runtime!) 

Read handout notes if your z/OS R5 system is running 31-bit (ESA/390), *not* 64-bit (z/Architecture) 

Customized Offerings Driver (subset of z/OS R5, with SMP/E V3.4) 

2. Activated OMVS address space with UNIX kernel services operating in full function mode for unloading the 

HFS via the pax utility 

3. Install from a user id that is permitted to the system resources defined in ServerPac job RACFDRV. You 

can install from a superuser (UID=0), or be a member of the facility class resource BPX.SUPERUSER 

4. Do not specify these LE run-time options as nonoverridable (NONOVR) in the CEEDOPT CSECT: 

ALL31, ANYHEAP, BELOWHEAP, DEPTHCONDLIMIT, ERRCOUNT, HEAP, HEAPCHK, INTERRUPT, 

LIBSTACK, PLITASKCOUNT, STACK, ... 

Minimum to Service the New Target System: 

See subsequent foil (includes shipped levels of program binder, SMP/E, and HLASM, and UNIX System 

Services requirements) 

If you order a product with your z/OS ServerPac that uses ++JAR, you'll need Java 2 Technology Edition 

(5655-D35). z/OS itself does NOT need Java as a driving system requirement! 



Driving System Requirements - Electronic ServerPac 


General availability for electronic delivery was January 10, 2005 

for those locations that can order z/OS product via ShopzSeries. 

Can choose between tape and electronic delivery 

Must be ordered from ShopzSeries to obtain electronic delivery 

Minimum to Install z/OS R8 ServerPac via electronic delivery: 

1. Must meet the tape requirements (on the previous foil) 

2. And to verify integrity of the data within the package SHA-1 hash values 

are used, must have either: 

SMP/E V3R3 and ICSF configured and active 

-or- SMP/E V3R4 -and- Java 2 Technology Edition V1R4 (ICSF is not 

necessary in this case!). 




21 



22


z/OS Driving System Requirements 

The driving system is the system image (hardware and software) that you use to install the target system. The target 

system is the system software libraries and other data sets that you are installing. You log on to the driving system and 

run jobs there to create or update the target system. Once the target system is built, it can be IPLed on the same 

hardware (same LPAR or same processor) or different hardware than that used for the driving system. 

If your driving system will share resources with your target system after the target system has been IPLed, be sure to 

install applicable coexistence service on the driving system before you IPL the target system. If you don't install the 

coexistence service, you will probably experience problems due to incompatible data structures (such as incompatible 

data sets, VTOCs, catalog records, GRS tokens, or APPC bind mappings). 

Customized Offerings Driver (5665-M12) 

The Customized Offerings Driver V2.1 (5665-M12) is an entitled driving system you can use if: 

1. you don't have an existing system to use as a driving system, or 

2. your existing system does not meet driving system requirements and you don't want to upgrade it to meet those 

requirements. 

At z/OS R8 GA, this driver is a subset of a z/OS R5 system except that the level of SMP/E in the driver is SMP/E V3R4. 

The Customized Offerings Driver is in DFSMSdss dump/restore format and supports 3380 and 3390 triple-density or 

higher DASD devices. The Customized Offerings Driver requires a locally attached non-SNA terminal and a system 

console from the IBM (or equivalent) family of supported terminal types: 317x, 327x, 319x, or 348x. An IBM (or equivalent) 

supported tape drive is also required to restore the driver. 

The Customized Offerings Driver is intended to run in single-system image and monoplex modes only. Its use in 

multisystem configurations is not supported. The Customized Offerings Driver is intended to be used only to install new 

levels of z/OS using ServerPac or CBPDO, and to install service on the new software until a copy (clone) of the new 

system can be made. The use of the Customized Offerings Driver for other purposes is not supported. 

The Customized Offerings Driver includes an HFS and the necessary function to use Communications Server (IP 

Services), Security Server, and the system-managed storage (SMS) facility of DFSMSdfp, but these items are not 

customized. However, existing environments can be connected to, and used from, the Customized Offerings Driver 

system. 

Identifying Driving System Software Requirements for ServerPac for z/OS R8 

Driving system requirements for installing z/OS R8 by way of ServerPac or dump-by-data-set SystemPac are: 

� An operating system: Use any of the following: 

� z/OS V1R5 with the PTFs in the table below. 

Note: If you do not IPL in z/Architecture mode, some installation jobs will fail. Therefore, if 

your driving system is to run in ESA/390 mode, you can avoid the problem by modifying 

ServerPac job IODFLOAD before you IPL your driving system in ESA/390 mode, as 

follows: 

� In step IODFINIT, comment out or remove the STEPLIB DD statement. 

� On the EXEC statement for program CBDMGHCP, change the SIZE parameter from 

SIZE=0 to SIZE=1024. 

� The Customized Offerings Driver (5665-M12). 

� A terminal: A locally-attached or network-attached terminal that can be used to establish a TSO/E session on the 

IPLed system is required. 

� Proper authority: Use the RACFDRV installation job as a sample of the security system definitions required so that 

you can perform the installation tasks. 

� Proper security: 

� In order for you to install into the zFS, the user ID you use must have read access to the 

SUPERUSER.FILESYS.PFSCTL resource in the RACF FACILITY class. 

� In order for you to install into the HFS, the following is required: 

� The user ID you use must be a superuser (UID=0) or have read access to the BPX.SUPERUSER resource in 

the RACF facility class. 

� The user ID you use must have read access to facility class resources BPX.FILEATTR.APF, 

BPX.FILEATTR.PROGCTL, and BPX.FILEATTR.SHARELIB (or BPX.FILEATTR.* if you choose to use a 



.

generic name for these resources). The commands to define these facility class resources are in 

SYS1.SAMPLIB member BPXISEC1 and in the z/OS UNIX Customization Wizard ( 

http://www.ibm.com/eserver/zseries/zos/wizards/). 

� Group IDs uucpg and TTY, and user ID uucp, must be defined in your security database. These IDs must 

contain OMVS segments with a GID value for each group and a UID value for the user ID. (For ease of use 

and manageability, define the names in uppercase.) 

� The group ID and user ID values assigned to these IDs cannot be used by any other IDs. They must be 

unique. 

� You must duplicate the required user ID and group names in each security database, including the same 

user ID and group ID values in the OMVS segment. This makes it easier to transport the HFS data sets 

from test systems to production systems. For example, the group name TTY on System 1 must have the 

same group ID value on System 2 and System 3. If it is not possible to synchronize your databases you 

will need to continue running the FOMISCHO job against each system after z/OS UNIX is installed. 

If names such as uucp, uucpg, and TTY are not allowed on your system, or if they conflict with existing 

names, you can create and activate a user ID alias table. For information about defining these group and user 

IDs to RACF and about creating a user ID alias table (USERIDALIASTABLE), see z/OS UNIX System 

Services Planning. Other sources of information are SYS1.SAMPLIB member BPXISEC1 and the z/OS UNIX 

Customization Wizard (http://www.ibm.com/eserver/zseries/zos/wizards/). (Note: You can use the RACFDRV 

installation job as a sample of the security system definitions required to perform the installation tasks.) 

� Language Environment run-time options: As of z/OS R7, ServerPac requires that the following Language 

Environment run-time options are not specified as nonoverrideable (NONOVR) in the CEEDOPT CSECT: ALL31, 

ANYHEAP, BELOWHEAP, DEPTHCONDLIMIT, ERRCOUNT, HEAP, HEAPCHK, HEAPPOOLS, INTERRUPT, 

LIBSTACK, PLITASKCOUNT, STACK, STORAGE, THREADHEAP, and THREADSTACK . 

� Language Environment: The CustomPac Installation Dialog uses the Language Environment run-time library 

SCEERUN. If SCEERUN is not in the link list on the driving system, you must edit the ServerPac installation jobs to 

add it to the JOBLIB or STEPLIB DD statements. 

� OMVS address space active: For ServerPac only (not SystemPac), an activated OMVS address space with z/OS 

UNIX kernel services operating in full function mode is required. 

� SMS active: The Storage Management Subsystem (SMS) must be active to allocate HFS and PDSE data sets, 

whether they are SMS-managed or non-SMS-managed. Also, the use of HFS data sets is supported only when SMS 

is active in at least a null configuration, even when the data sets are not SMS-managed. Do either of the following: 

� To allocate non-SMS-managed HFS and PDSE data sets, you must activate SMS on the driving system in at 

least a null configuration. You must also activate SMS on the target system. 

� To allocate SMS-managed HFS and PDSE data sets, you must activate SMS on the driving system in at least a 

minimal configuration. Then you must define a storage group, create SMS-managed volumes, and write, 

translate, and activate a storage class ACS routine that allows the allocation of PDSE and HFS data sets with the 

names in the ALLOCDS job. You must also activate SMS on the target system. 

� SMP/E ++JAR Support: If your ServerPac order contains any product that uses the ++JAR support introduced in 

SMP/E V3R2, then your driving system will require IBM Developer Kit for OS/390, Java 2 Technology Edition 

(5655-D35). z/OS V1R8 itself does not use the ++JAR support. 

� zFS configuration requirements (optional): If you will specify that you will use a zFS for ServerPac installation, then 

you must be sure that the zFS has been installed and configured, as described in z/OS Distributed File Service zSeries 

File System Administration. 

� Electronic delivery requirements (optional): If you intend to receive your ServerPac order by way of the Internet, you 

need either of the following: 

� SMP/E V3R3 and Cryptographic Services ICSF set up and activated 

� -or- SMP/E V3R4 and Java 2 Technology Edition V1R4 (in this case ICSF isn't necessary). 

� Proper level for service: In order for you to install service on the target system that you're building, your driving system 

must minimally meet the driving system requirements for CBPDO Wave 1 and must have the current (latest) levels of 

the program management binder, SMP/E, and HLASM. The service jobs generated by the CustomPac Installation 

Dialog use the target system's (and therefore current) level of the binder, SMP/E, and HLASM. If you choose to use 

your own jobs, model them after the jobs provided by ServerPac or dump-by-data-set SystemPac by adding STEPLIB 

DD statements to access MIGLIB (for the binder and SMP/E) and SASMMOD1 (for HLASM). Be sure that the 

SASMMOD1 and SYS1.MIGLIB data sets are APF authorized. Another way to install service is from a copy of your 

target system. 

Driving System PTFs for ServerPac for z/OS R8 

z/OS release PTFs 




z/OS V1R5 

z/OS V1R6 

z/OS V1R7 

w DFSMSdfp: UA05520, UA14837 

w z/OS UNIX: UQ79726, UQ85020 

For servicing: z/OS R8 level of the Program Management Binder, HLASM (V1R5). and z/OS R8 

SMP/E (SMP/E V3R4) 

� DFSMSdfp: UA14838 


For servicing: z/OS R8 level of the Program Management Binder, HLASM (V1R5), and z/OS R8 


For servicing: z/OS R8 level of the Program Management Binder, HLASM (V1R5), and z/OS R8 





Driving System Requirements to Service z/OS R8 (and for installing via CBPDO) 

Very Similar to Installing via ServerPac: 

z/OS R5 with PTFs, along with latest Program Binder, SMP/E, and HLASM, and PTFs 

May STEPLIB to Wave 0 target system's MIGLIB and SASMMOD1. 

Since z/OS R6, expect errors if you don't use the latest Program Binder like this one! 

IEW2322I 1220 5 INCLUDE SMPWRK3(CELQAWI) UQ88825 SEQ # 000025 

IEW2690E 3530 ONE OR MORE FIELD DESCRIPTORS IN GOFF RECORD 3 WITHIN MEMBER CELQAWI 

IDENTIFIED BY DDNAME SMPWRK3 ARE NOT VALID. ERRORID = 40. 

IEW2307E 1032 CURRENT INPUT MODULE NOT INCLUDED BECAUSE OF INVALID DATA. 

Activated OMVS address space, in full function mode 

SMP/E Link Edit UTILITY entry for the program binder 

Language Environment Run Time Library SCEERUN access. 

Install from a user id that is a superuser (UID=0), or be a member of the facility class resource 

BPX.SUPERUSER 

Install from a user id that is permitted read access to facility class resources 

BPX.FILEATTR.APF, BPX.FILEATTR.PROGCTL, and BPX.FILEATTR.SHARELIB (or 

BPX.FILEATTR.*) 

Group IDs uucpg and TTY, and user ID uucp, must be defined in your security database 

May also use the Customized Offerings Driver 

MMigrating to z/OS R8 Part 1 of 3: Get Ready 



Identifying Driving System Software Requirements for Servicing z/OS R8 and Installing CBPDO 

After installing via ServerPac, you will eventually want to install service on your z/OS R8 system. The driving system to 

install service on your z/OS R8 ServerPac system are the same as to install with the CBPDO method. For servicing your 

ServerPac system, you must meet the driving system requirements for "Wave 1" below. 

When you use the CBPDO method of installing z/OS you install in three stages called waves. (Wave 1, in order to be 

more manageable, is divided into several tasks called ripples.) This section describes the driving system requirements for 

each wave. 

z/OS R8 CBPDO: Driving System Wave 0 

In Wave 0 you install the program management binder (part of the BCP), the HLASM base element, and the SMP/E base 

element. These items must be installed on (available from) the driving system for subsequent wave installations. 

You can use either of the following as the driving system for installing z/OS R8 Wave 0: 

� z/OS R5 or later. 


z/OS R8 CBPDO: Driving System Wave 1 (and to service a ServerPac system) 

In Wave 1 you install most of the elements and features. The driving system requirements for installing Wave 1 are: 

An operating system: Use any of the following: 

� z/OS R5 or later with the PTFs listed in the ServerPac table previously, except that the program binder, HLASM, 

and SMP/E must be at the current (latest) levels. To satisfy the binder and SMP/E requirements, you can use a 

STEPLIB DD statement to access the z/OS V1R8 program binder and z/OS V1R8 SMP/E in the Wave 0 target 

system's SYS1.MIGLIB data set, and to access the z/OS V1R8 HLASM's ASM.SASMMOD1 data set. Ensure that the 

target system's SYS1.MIGLIB and ASM.SASMMOD1 data sets are APF authorized on the driving system. 

� Since z/OS R6, failure to use the latest program binder may result in errors during APPLY of z/OS service. 

You may see such errors as: 

IEW2322I 1220 5 INCLUDE SMPWRK3(CELQAWI) UQ88825 SEQ # 000025 

IEW2690E 3530 ONE OR MORE FIELD DESCRIPTORS IN GOFF RECORD 3 WITHIN MEMBER CELQAWI 

IDENTIFIED BY DDNAME SMPWRK3 ARE NOT VALID. ERRORID = 40. 



23


IEW2307E 1032 CURRENT INPUT MODULE NOT INCLUDED BECAUSE OF INVALID DATA. 


� Proper security: In order for you to install into the HFS, the security definitions described previously for ServerPac are 

required. 

� Binder entry in SMP/E UTILITY: The SMP/E UTILITY must have an entry for the binder. You can specify any of these 

program names in the UTILITY entry: IEWBLINK, HEWL, IEWL, LINKEDIT, or HEWLH096. (The linkage editor, which 

uses the names HEWLKED, HEWLF064, IEWLF440, IEWLF880, and IEWLF128, cannot be used.) 

� Language Environment: You must add SCEERUN (the run-time library provided by Language Environment) to your 

program search order because many elements and features require it. If you wish, add SCEERUN to your LNKLST 

concatenation. If you don't add SCEERUN to your LNKLST, you must access SCEERUN by using STEPLIB DD 

statements in the individual element and feature procedures that require them. The BCP's Program Management 

Binder is one function that requires access to SCEERUN; it has been required since OS/390 R10. This means that 

you must make available SCEERUN (via the LNKLST or STEPLIB, for instance) to any JCL and procedures (such as 

SMP/E procedures) that invoke the binder. This ensures that processing, such as conversion of long names to short 

names, is successful. 

� OMVS address space active: Before you install the elements and features in Wave 1, you must activate the OMVS 

address space in full function mode on the driving system. To activate OMVS, complete the required customization 

(for example, SMS and RACF setup) as described in z/OS UNIX System Services Planning. 

� Target system's HFS mounted: The target system's HFS must be mounted. 

z/OS R8 CBPDO: Driving System Wave 2 

In Wave 2 you install the z/OS V1R8 level of JES2 or JES3. Wave 2 is optional and can be combined with Wave 1. The 

driving system requirements for Wave 2 are the same as for Wave 1. 



Choosing IBM Products That You Want to Run with z/OS 

The functional and minimal requirements are found in the z/OS and z/OS.e Planning for Installation which is available on 

the Internet from http://www.ibm.com/servers/eserver/zseries/zos/bkserv/. 

For a list of products available for ordering with z/OS, you can do any of the following: 

� Use the self-service Internet application ShopzSeries: http://www.ibm.com/software/shopzseries 

� Use the product catalogs (order checklists). For z/OS 

http://www.ibm.com/eserver/zseries/software/swinfo/os390.htm 

w Access the software configurator used in your country, select the z/OS environment, and then select ServerPac, 

CBPDO, or SystemPac. 

w Refer to z/OS and z/OS.e Planning for Installation Appendix C, Minimum Releases of IBM Software Products 

That Run with z/OS and z/OS.e 

Many of these products can be ordered as part of your z/OS ServerPac order, z/OS SystemPac order, separate CBPDO 

order, or separate ProductPac order. 

If you're migrating to z/OS V1R8, you can find out which products have new levels by using ShopzSeries or by using the 

SMP/E base element's Planning and Migration Assistant. Both tools use data found on your system as well as the latest 

IBM software product catalog. 

Choosing ISV products that you want to run with z/OS 

For a list of independent software vendors (ISVs) that support z/OS, as well as announcements, testimonials, and other 

information, see http://www.ibm.com/servers/eserver/zseries/zos/zos_products.html 

For a directory of IBM and IBM Business partners that provide z/OS applications, tools, and services, see the Global 

Solutions Directory: http://www.ibm.com/software/solutions/isv 

Note that you can use SystemPac to get some ISV products on system delivery vehicles with IBM products. For a list of 

selectable ISVs with SystemPac, see: http://www.ibm.com/ca/custompac/ 

VM Guest Considerations 


Target System Requirements for z/OS R8 

Software Requirements 

Coexistence Software (on Other Target Systems) 

Correct Levels of IBM Non-z/OS and Non-IBM Products 

Functional Requirements 

z/OS R8 must run in z/Architecture mode (...since z/OS R6!) 

Some functions (like zAAP) require z990 or z890 at least. 

VM Guest considerations 

Only on z800 or z890 or BC: cannot IPL z/OS under an LPAR named 

ZOSExxxx (includes as a VM guest). 

(z/OS R6's Dynamic LPAR Rename function on z890 and BC can help here!) 

Hardware Requirements 

Processor Requirements: 

an IBM ^ zSeries z9 EC, z9 BC, z990, z890, z900, or z800 

Coupling Facility: see http://www.ibm.com/eserver/zseries/pso/cftable.html 


MMigrating to z/OS R8 Part 1 of 3: Get Ready 




24

z/OS can run as a VM guest. Requirements are: 

� Must be on a z9 EC, z9 BC, z990, z890, z900, or z800 server: VM must be z/VM (not VM/ESA). Furthermore, 

� if a z9 EC or z9 BC or z990 server, the z/VM PTF for APAR VM63124 must be installed. 

� If a z800, z890, or z9 BC server, then z/OS.e can run as a VM guest. The server must be a z800, z890, or z9 BC, 

VM must be z/VM, z/VM and z/OS.e must operate in z/Architecture (64-bit) mode, z/VM and z/OS.e must run in a 

logical partition (LPAR), and the LPAR must be named ZOSExxxx (where xxxx is any valid combination of zero to 

four characters). The LPAR name restriction ensures compliance with z/OS.e license terms, which prohibit z/OS 

from running in a z800, z890, or z9 BC LPAR named ZOSExxxx. (Linux for S/390 and Linux for IBM ^ 

zSeries are the only other operating systems that may run as a guest under z/VM in an LPAR named ZOSExxxx.) 

z/OS.e licensees are required to submit data to IBM that shows LPAR names. (The ZOSExxxx LPAR name 

restriction is only applicable to z800, z890, and z9 BC servers, not other servers. The Dynamic LPAR Rename 

function available on z890 and z9 BC can assist you with this requirement.) 

Target System Hardware Requirements 

The minimal hardware requirements for z/OS, as well as additional hardware needed by specific z/OS elements and 

features is documented in z/OS and z/OS.e Planning for Installation. Remember, z/OS V1R8 runs only in 

z/Architecture mode, and only on z9 EC , z9 BC, z990, z890, z900 or z800 servers. 

Identifying Processor Requirements 

z/OS V1R8 runs on the following IBM ^ zSeries servers (or their equivalents): 

� IBM zSeries z9 EC. 

� IBM zSeries z9 BC. 

� IBM zSeries 990 (z990). 




Identifying Coupling Facility Requirements 


There are hardware and software requirements related to coupling facility levels (CFLEVELs). See 

http://www.ibm.com/eserver/zseries/pso/cftable.html. 




Some IBM SW Target System Requirements for z/OS R8 

product name minimum supported level 

CICS TS V2 R2 

(V1 R3 was end of Service: 4/30/06) 

for zAAP exploitation, minimum level is V2 R3. 

DB2 V7 R1 with PTFs 

for determining zAAP execution potential and exploitation, 

minimum level is V7 R1 

for zIIP exploitation, minumum level is V8 plus PTFs 

IMS V8 R1 with PTFs 

(V7 R1 was end of Service: 11/8/05) 

for determining zAAP execution potential and exploitation, 

minimum level was V7 R1 

WebSphere 

Application 

Server 

V5 R1 

(V5 R0 was end of service 9/30/06) 

for determining zAAP execution potential, can use V5.02 

for zAAP exploitation, minimum level is V5 R1. 

zAAP exploitation requires at least z/OS R6 and the IBM Solution Developers Kit (SDK) for z/OS, Java 2 Technology 

Edition, V1.4 with PTF (or later) for APAR PQ86689 

zIIP requires the z/OS R6 or R7 zIIP Web deliverable, or z/OS R8. See zIIP functional PSP bucket. 




Selected IBM Subsystem Products that will run on z/OS R8 (and levels for zAAP and zIIP) 

For a complete list of the minimum release of IBM software products that run on z/OS R8, refer to Appendix C of z/OS 

and z/OS.e Planning for Installation. 

zAAP 

If you are interested in exploiting (or doing capacity planning for) zAAPs, then there are minimum software levels 

required. In order to exploit a zAAP, the operating system must be migrated to at least z/OS 1.6 (or z/OS.e 1.6), the IBM 

Solution Developers Kit (SDK) for z/OS, Java 2 Technology Edition, V1.4 with PTF (or later) for APAR PQ86689 must be 

used. 

Here is a table outlining the subsystems and minimum Java levels dependencies for determining zAAP Java execution 

and exploitation potential. The rows in blue identify some of the products levels that will exploit zAAPs. The rows in 

yellow, while not able to exploit the benefits of zAAPs, show where the zAAP Projection Tool for Java 2 Technology 

Edition, SDK1.3.1 can be used to assist in zAAP capacity planning. For instance, WebSphere V5.0.2 cannot exploit 

zAAP, however the zAAP Projection Tool can be used to determine zAAP Java execution potential if the WebSphere 

workloads were migrated to the required level for zAAP exploitation. 

zIIP 

For z/OS V1.6 or z/OS V1.7: If you will exploit the IBM System z9 Integrated Information Processor (zIIP), you will require 

the "IBM System z9 Integrated Information Processor Support for z/OS and z/OS.e V1R6/R7" Web deliverable plus PTFs 

(planned to be available June 30, 2006). This Web deliverable contains FMID JBB77S9 for z/OS V1.6, and FMID 

JBB772S for z/OS V1.7. Install the service identified in the program directory that comes with this Web deliverable and 

the service which is recommended in the appropriate zOSV1Rn BCPZIIP PSP bucket. IBM DB2 UDB for z/OS V8 with 

PTFs, is also required for exploitation for portions of eligible workloads. For z/OS V1.8, this Web deliverable is not 

needed, as zIIP support is incorporated. 



25

Coexistence Service Requirements for z/OS Release 8 

To understand the Coexistence-Fallback-Migration policy for z/OS, and which releases are supported with z/OS V1 R8, 

see the Coexistence section of this presentation. Listed below are the coexistence and fallback service, for installation on 

an z/OS V1R7 system for z/OS V1R8. For a list of the coexistence service on z/OS V1R6 and z/OS V1R5 for z/OS V1R8, 

see Appendix B of this presentation. 

Apply on z/OS V1R7, the coexistence and fallback service (PTFs) listed in the table below: 

Element or feature, and function provided by PTFs 


Coexistence System Requirements for z/OS R8 

Documented in z/OS Migration 

From z/OS R7 Coexistence PTFs for z/OS R8: 

BCP - WLM, Converter/Interpreter, Program Binder (new PM level - PM5!), Console, 

Logger, RRS 

DFSMS - dfp, hsm, rmm 


HCD - for HCM support 

JES2 - for MAS support down to z/OS R5 JES2 

JES3 - for multisystem complex support down to z/OS R5 JES3 

Language Environment - downward compatibility 

NFS - read support for new R8 NFS export file format 

RMF - sysplex-wide reporting toleration 

Security Server RACF - database template structure toleration 

From z/OS R6 or R5 Coexistence PTFs for z/OS © R8: 2003 IBM Corporation 

Found in the Appendix of your handout... 


BCP: Ensures that pre-z/OS V1R8 systems tolerate the new format of the z/OS 

V1R8 WLM service definition and service policy in the WLM couple data set. 

Moreover, the PTF ensures the toleration of changed WLM LPAR management and 

JES initiator management information that is exchanged in a mixed-release (z/OS 

V1R8 and pre-z/OS V1R8) sysplex. 

If the WLM service policy in the couple data set has been activated by a z/OS V1R8 

system, a pre-z/OS V1R8 system without the PTF will not be able to activate the 

policy and might fail during IPL with a wait state 064. If LPAR management is 

being used in a mixed-release sysplex and the PTF is not installed, you might 

experience abends and see message IWM054I FAILURE IN LPAR CPU 

MANAGEMENT, PROCESSING DISABLED. 

BCP: In z/OS V1R8, SYSIN DD * override statements are no longer required to 

reside in the job stream in the same order as the corresponding DD statements 

appear in the procedure. Because new text units are introduced for each SYSIN DD 

* statement, the PTF allows jobs to ignore the new text units when they run in a 


z/OS V1R7 PTFs 

UA90269 (if you do not 

have JBB772S installed) 

or UA90270 (if you have 

JBB772S installed) 

UA24560 



26


JES2 environment and convert on a z/OS V1R8 system but interpret on an earlier 

system. 

BCP: If an application developer compiles or assembles with the z/OS V1R8 

program management binder version 6 API invocation macros, or codes to the new 

STARTD API interface, and the resulting program is run on an earlier release of 

z/OS, the binder STARTD API will fail with return code 12, invalid parameter list, 

message IEW2132S 0064 INCORRECT NUMBER OF PARAMETERS PASSED 

FOR CALL. The PTF allows such a calling program to execute successfully. 

BCP: If an application developer uses the z/OS V1R8 program management binder 

to create a program object with the latest format in a PDSE, the PTF is needed so 

that an ISPF user can browse the PDSE on z/OS V1R7. 

BCP: In z/OS V1R8, the console restructure enhancement eliminates the master 

console and the console switch function. The PTF allows earlier systems to tolerate 

the enhancement. 

DFSMShsm 

DFSMShsm: In z/OS V1R8, dump volume (DVL) and dump class (DCL) control 

data set records were enlarged as part of the DFSMShsm dump encryption 

enhancement. The PTF allows a z/OS V1R7 system to tolerate the increase in record 

size. 

(TM) DFSMSdfp: An enhancement in the z/OS V1R8 object access method (OAM) 

component introduced a new ODLOBFL column in the object directory to exploit 

DB2 

DFSMSdfp: In z/OS V1R8, the D SMS,SMSVSAM,DIAG(CONTENTION) 

command is introduced to display internal VSAM RLS contention. The PTF allows 

a z/OS V1R7 system that receives the new DIAG CONTENTION command to 

tolerate the command by issuing a message analogous to IGW495I D 

SMS,SMSVSAM,DIAG COMMAND FUNCTION HAS FOUND THE DIAG 

TABLE HAS NO ENTRIES. If the PTF is not installed, the z/OS V1R7 system 

receiving the new command treats it as an irrelevant and confusing console 

message. 

DFSMSdfp: In z/OS V1R8, a performance improvement to VSAM RLS causes 

XES lock table cleanup to be skipped when the SMSVSAM address space is 

terminated, as documented in APAR OA11708. This PTF allows a z/OS V1R7 

system to tolerate the enhancement. 

: Allows a z/OS V1R7 system to tolerate the changes made by the 

fast replication tape support enhancement in z/OS V1R8. 

(R) BCP: Allows a z/OS V1R7 system to tolerate the z/OS V1R8 logger log stream 

GROUP designation and renamed log streams. 

BCP: Allows a z/OS V1R7 system to tolerate changes made to resource recovery 

services (RRS) display and ATRQUERY functions in z/OS V1R8. 

DFSMSdfp: Program object format 5 (PO5 format) is new in z/OS V1R8. The PTF 

allows PDSE program libraries that contain PO5 program objects to be processed by 

IEBCOPY on z/OS V1R7 systems. 

binary large object (BLOB) support. The PTF enables pre-z/OS V1R8 

OAMs to coexist in an OAMplex with OAMs at the z/OS V1R8 or later level. 

DFSMSrmm (TM) : Allows a pre-z/OS V1R8 system in a client/server environment to 

participate in an RMMplex in which a z/OS V1R8 system has been started. 

UA24437 

UA25784 

UA26398 and, if 

Japanese, UA26402 

UA24159, UA25588 

UA27072 

UA22351 

UA24413 

UA24374 

UA21542 

UA25405 

UA22716 

UA25145 if not using 

client/server 




Optionally, you can specify UTC(YES) with the EDGUTIL utility on z/OS V1R8 to 

enable DFSMSrmm common time support. 

DFSMSrmm: Allows a pre-z/OS V1R8 system to participate in an RMMplex in 

which a z/OS V1R8 system has been started. In particular, the PTF enables VRSEL 

processing to recognize the use of the special ABEND and OPEN vital record 

specifications and to correctly handle COUNT(0). It also prevents the continued use 

of the unsupported options STARTNUMBER and LOCATION(BOTH). 

Distributed File Service: Allows z/OS V1R7 systems to tolerate the change in the 

zFS XCF protocol that occurred in z/OS V1R8 (and was implemented in z/OS 

V1R7 by APAR OA13738). 

HCD: Allows z/OS V1R8 HCM to exploit z/OS V1R7 HCD functionality to enable 

new z/OS V1R8 HCM functions. 

JES2: Allows an earlier JES2 to run with z/OS V1R8 JES2 in a multi-access spool 

(MAS). Install the PTFs that are appropriate to the JES2 level that you are using. 

JES3: Allows a pre-z/OS V1R8 JES3 to tolerate the removal of various symbols 

from the IHAWQE macro, which was done as part of the console improvements 

made in z/OS V1R8. 

Language Environment (R) : Causes a meaningful message to be issued when a new 

z/OS V1R8 Language Environment run-time option is encountered by an earlier 

release. The message states that the option is ignored. If the PTF is not installed, the 

option is still ignored but a less meaningful message, or no message at all, is issued. 

RMF 

Security Server: In z/OS V1R8, the structure of the RACF database was changed 

to allow a template block to be continued into another block. The PTF allows a z/OS 

V1R7 system to process templates that extend into another block. If you share a 

RACF database between z/OS V1R8 and z/OS V1R7, you need to install the PTF on 

the z/OS V1R7 system. 

(TM) NFS: Allows a z/OS V1R7 system to read the new NFS export file format 

generated by a z/OS V1R8 system. 

: Ensures the toleration of new z/OS V1R8 functionality for sysplex-wide 

RMF reporting in earlier releases. 

DFSMSrmm, or both 

UA25145 and UA00015 

if using client/server 

DFSMSrmm 

UA22045 

UA24209 

PTF for APAR OA14334 

z/OS V1R7 JES2: 

UA24984; z/OS 

V1R5-V1R6 JES2: 

UA09501, UA18836, 

UA20902, UA90161, 

UA24983 

z/OS V1R7 JES3: 

UA24990; z/OS 

V1R5-V1R6 JES3: 

UA24989 

UK12452 

UA25099 

UA26170 

UA24980 




Some Migration Actions You Can Do NOW for z/OS R8 

1. Transition off of removed functions and elements: 

in R8: msys for Operations, zFS multifile system aggregates, Anynet, Firewall Technologies, ... 

in R7: JES2 R4 mode, JOBCAT/STEPCAT, OS/390 R10 C/C++ compilers, 1-byte console IDs, ... 

in R6: LE RTLS, DCE AS, Encina Toolkit Executive, ... 

in future: TN3270 in TCP/IP stack, run-time IOC DLLs, VSAM obsolete attributes, RMF LDAP, ... 

2. Prepare Driving and Target Systems: 

Driving systems - Doing electronic delivery? Review requirements. 

Target systems - 

z/Architecture on a z/Architecture-capable server! 

DASD storage for z/OS R8 - no big changes here 

ISV research for z/OS R8 

Coexisting systems - install required coexistence service 

3. Review PSP buckets: 

HW, z/OS, and Functional (ZIIP, ZAAP, HCHECK, GRSSTAR, ...) 




Prepare for your migration to z/OS R8! 

In this presentation you’ve seen many things can you can do right now, on your current z/OS release to help make your 

z/OS R8 migration smooth. Listed above are the things that were shown in this presentation, but make sure you attend 

Part 2 and Part 3 so that you know a more complete migration picture. 



27


Migrating to z/OS R8 Part 1 of 3: Get Ready Summary 

Content of z/OS R8 

Remember to order export contolled features: z/OS Sec Lvl 3 and CS Sec Lvl 3 


SMP/E V3R4 now! 

Ported Tools (and Perl feature), XML R9, 31-bit and 64-bit Java... 

z/OS Policies 

z/OS R8 Coexistence-Migration-Fallback from z/OS R5 

If you're on z/OS R4, you cannot coexist with z/OS R8! 

Ensuring System Requirements are Satisfied 

Driving System Requirements - z/OS R5 + PTFs, ... 

Target System Requirements - Must run z/OS R7 in z/Arch on a z/Arch server! 

Minimum Subsystem levels: CICS 2.2, DB2 7.1, IMS 8.1, WAS 5.1 

zAAP and zIIP exploitation requirements 

Coexistence Requirements 

Migration Actions You Can Do NOW: 

Replacements for removed functions and elements - and future removals. 

...and everything applicable in the next two presentations! 


Migrating to z/OS R8 Part 2 and Part 3 Presentations 

Same room - today! 

Session 2871 - Part 2 of 3: Get Set at 11am 


(General z/OS items) 

BCP 

C/C++ 


HCD 

Session 2872 - Part 3 of 3: GO! at 3:00pm 


DFSMS 



JES2 and JES3 

z/OS UNIX 

Also included are highlights of some enhancements you'll see in z/OS 

R8 for system programmers. 




28 




29

Appendix A: List of Base Elements and Optional Features for z/OS V1.8 

The following table lists the base elements and optional features in z/OS V1.8. The following table headings are used: 

Name 

What this document calls the element or feature. (To help you distinguish elements from features, element names in 

this column are highlighted.) Also, this column tells you which elements and features are only in z/OS (not also in 

z/OS.e). 

Function level 

The most recent release in which the element or feature changed. ("Change" means that one or more of the 

element's or feature's FMIDs [function modification identifiers] was changed, or that the element or feature was 

added to the system. New function added in program temporary fixes [PTFs] is not considered change.) Also, for 

nonexclusive elements and features, the equivalent level of the separate product is listed in parentheses. 

Note: 

The function level is expressed as a z/OS function level. The z/OS and z/OS.e function levels are identical. 

Do not confuse the function level with the product level. All elements and features are at the V1R8 product level but 

they are at various function levels. For example, the product level of z/OS BookManager READ is z/OS V1R8 but 

its function level is OS/390 V1R1 because OS/390 V1R1 was the last release in which it changed. 

Type and description 

z "Type" means the following: 

y Whether it's a base element or optional feature 

y Whether the base element or optional feature is exclusive (existing only within z/OS or z/OS.e) or 

nonexclusive (also available as a separate product) 

y If an optional feature, whether it's priced or unpriced 

y If an optional feature, whether it supports dynamic enablement (note that all the priced features support 

dynamic enablement) 

z "Description" is a brief description of the element or feature, and miscellaneous facts about it. 

Base elements and optional features in z/OS V1R8 and z/OS.e V1R8 

Name 

BCP 

BDT 

Function level (last time 

changed) 


OS/390 V1R2 


Type: base element, exclusive. 

The Base Control Program (BCP) provides essential operating system 

services. The BCP includes the I/O configuration program (IOCP), the 

workload manager (WLM), system management facilities (SMF), the z/OS 

UNIX System Services (z/OS UNIX) kernel, the program management 

binder, and support for the Unicode 


(TM) Type and description 

Standard. As of z/OS V1R8 and 

z/OS.e V1R8, the BCP also includes z/OS XML System Services (z/OS 

XML). 

IBM Health Checker for z/OS is also part of the BCP. This tool helps 

improve availability by reporting on active z/OS and sysplex settings that 

are different than IBM recommended best practices or customer-defined 

settings. It was initially available by PTF and download for z/OS V1R4 and 

z/OS.e V1R4, was integrated in base element msys for Operations in z/OS 

V1R5 and z/OS.e V1R5, was moved to the BCP in z/OS V1R7 and z/OS.e 

V1R7 (keeping its own FMID), and was merged into the BCP base FMID in 

z/OS V1R8 and z/OS.e V1R8 (losing its own FMID). 



BDT File-to-File 

(z/OS only) 

BDT SNA NJE 

BookManager BUILD 

(z/OS only) 

BookManager READ 

(z/OS only) 

C/C++ without Debug 

Tool 

CIM 


OS/390 V1R2 

OS/390 V1R2 

OS/390 V1R1 

(BookManager 

BUILD/MVS V1R3, 

5695-045) 

OS/390 V1R1 

(BookManager 

READ/MVS V1R3, 

5695-046) 





Bulk Data Transfer (BDT) provides the base services that the optional BDT 

features (BDT File-to-File and BDT SNA NJE) need to transfer data from 

one computer system to another. 

You cannot activate any BDT functions until one or both of the optional 

BDT features is enabled. 

Type: optional feature, exclusive, priced, can be dynamically enabled. This 

feature is supported with z/OS but not with z/OS.e. With z/OS.e, you install 

the code but it is not functional and you are not licensed to use it. 

BDT File-to-File allows users at one z/OS system in a SNA network to copy 

data sets to or from another z/OS system in the network. This feature is 

related to the element BDT. 

Type: optional feature, exclusive, priced, can be dynamically enabled. 

BDT SNA NJE allows JES3 users to transmit jobs, output, commands, and 

messages from one computer system to another within a SNA network. This 

feature is related to the element BDT and the feature JES3. 

Type: optional feature, nonexclusive, priced, can be dynamically enabled. 

This feature is supported with z/OS but not with z/OS.e. With z/OS.e, you 

install the code but it is not functional and you are not licensed to use it. 

BookManager BUILD creates softcopy documents that can be used by any 

of the BookManager products, such as BookManager READ or Library 

Server. 

Type: base element, nonexclusive. This element is supported with z/OS but 

not with z/OS.e. With z/OS.e, you install the code but it is not functional 

and you are not licensed to use it. 

BookManager READ is used to display, search, and manage online 

documents and bookshelves. A related optional feature is BookManager 

BUILD. 


C/C++ without Debug Tool consists of: 

w XL C/C++ compiler 

w C/C++ application development utilities. 

As of z/OS V1R5 and z/OS.e V1R5, optional feature C/C++ with Debug 

Tool is withdrawn. For debugging tools, see 

http://www.ibm.com/software/awdtools/debugtool/. 

As of z/OS V1R7 and z/OS.e V1R7, the OS/390 V2R10 level of the C/C++ 

compiler is withdrawn. The XL C/C++ compiler remains. For information 

about migrating from the former to the latter, see z/OS XL C/C++ Compiler 

and Run-Time Migration Guide for the Application Programmer. 


Common Information Model (CIM) is a standard data model for describing 

and accessing systems management data in heterogeneous environments. It 

allows system administrators to write applications that measure system 

resources in a network with different operating systems and hardware. To 

enable z/OS for cross platform management, a subset of resources and 

metrics of a z/OS system are mapped into the CIM standard data model. 

CIM was new in z/OS V1R7 and z/OS.e V1R7. 

Transport layer security (TLS) encryption is performed for CIM by base 

element Communications Server. CIM does not implement any of its own 

encryption algorithms. 

Type: base element, exclusive, can be dynamically enabled. 

Communications Server (also known as CS z/OS) supports secure TCP/IP, 

SNA, and UNIX networking throughout an enterprise. It gives you the 

ability to connect subsystems and applications to each other, and to connect 

network devices (such as terminals and printers) to the system. 




Security Level 3 

Cryptographic Services 

DCE Base Services 



OS/390 V2R9 


Communications Server consists of two components: IP Services and SNA 

Services. 

A related optional feature is Communications Server Security Level 3. 

For encryption, IP Services uses the firewall CDMF DES 40-bit, SNMPv3 

DES 56-bit, IP Sec DES 56-bit, and AES algorithms. IP Services also uses 

the System SSL component of Cryptographic Services for encryption 

services. SNA Services uses the limited DES algorithm for encryption. 

AnyNet (R) function was removed from Communications Server (SNA 

Services) in V1R8 of z/OS and z/OS.e. AnyNet has not been enhanced in 

many years and has been supplanted by Enterprise Extender, which has 

superior function and performance. 

Type: optional feature, exclusive, unpriced, cannot be dynamically enabled. 

This feature works in conjunction with the Communications Server base 

element to provide stronger encryption (greater than 64 bits) than that 

available without this feature. This feature uses the TDES algorithm for 

encryption. The actual level of encryption that takes place with this feature 

installed can be configured to be something less than the maximum level 

enabled by this feature. 

This feature is worldwide exportable subject to U.S. export regulations. 


Cryptography is the transformation of data to conceal its meaning. In z/OS 

and z/OS.e, the base element Cryptographic Services provides the following 

base cryptographic functions: data secrecy, data integrity, personal 

identification, digital signatures, and the management of cryptographic keys. 

Keys as long as 56 bits are supported by this base element. (Keys longer 

than 56 bits are supported by the optional feature z/OS Security Level 3.) 

Cryptographic Services consists of the following components: 

w Integrated Cryptographic Service Facility (ICSF). The level of V1R8 

ICSF is FMID HCR7731, which is the same level as in the Web 

deliverable Enhancements to Cryptographic Support for z/OS and 

z/OS.e V1R6/R7. 

w Open Cryptographic Services Facility (OCSF), which was last 

changed in OS/390 V2R10. 

w PKI Services, which was last changed in z/OS V1R8 and z/OS.e 

V1R8. Before V1R5, this component was in the optional feature 

Security Server, although it was licensed with the base operating 

system and could be used without ordering or enabling Security 

Server. 

w System Secure Sockets Layer (SSL), which was last changed in 

z/OS V1R8 and z/OS.e V1R8. 

For encryption: 

w OCSF uses the RC2/RC4/RC5 40-56 bit and DES 56-bit algorithms. 

w PKI Services uses the RACF (R) component of optional feature 

Security Server, and the ICSF, OCSF, and System SSL components 

of base element Cryptographic Services. For digital signatures, PKI 

Services uses the RSA, DSA, and DES 56-bit algorithms. 

w System SSL uses the RC2/RC4, DES through 56-bit, 

Diffie-Hellman, RSA, and DSA algorithms. 


DCE Base Services provides services for developing and running 

client/server applications, including remote procedure call, directory, 



DFSMSdfp (TM) 

DFSMSdss 

DFSMShsm (and 

DFSMSdss) 

DFSMSrmm 

DFSMStvs 

DFSORT (TM) 

Distributed File Service 






z/OS V1R5 



security, and distributed time services. This element is at the Open Group 

Open Software Foundation (OSF) DCE 1.1 level. 

DCE Base Services uses the limited DES algorithm for encryption. 


DFSMSdfp provides storage, data, program, and device management 

functions. Related optional features are DFSMSrmm (TM) , DFSMSdss (TM) , 

DFSMShsm (TM) , and DFSMStvs. 

As of z/OS V1R3 and z/OS.e V1R3, the program management binder is 

moved to the BCP base element. 


DFSMSdss copies and moves data for backup and recovery, and to reduce 

free-space fragmentation. 


DFSMShsm provides automated DASD storage management, including 

space management for low and inactive data, and availability management 

for accidental data loss caused by local and site disasters. DFSMShsm also 

lets you make effective use of tape media. 

DFSMShsm requires DFSMSdss. For this reason, DFSMShsm is not 

available by itself. If you want to use DFSMShsm, you must order the 

DFSMShsm/DFSMSdss combination. (DFSMSdss is also available by itself 

for those who do not want DFSMShsm.) 


DFSMSrmm helps you manage your removable media as one 

enterprise-wide library across systems that can share DASD. 


DFSMS Transactional VSAM Services (DFSMStvs) enables batch jobs and 

CICS online transactions to update shared VSAM data sets concurrently. 

DFSMStvs was introduced in June 2003 as an optional feature of z/OS 

V1R4 and z/OS.e V1R4. 


DFSORT provides fast and easy sorting, merging, copying, reporting, and 

analysis of your business information, as well as versatile data handling at 

the record, field, and bit level. DFSORT also includes the high-performance 

ICEGENER facility, the versatile ICETOOL utility, Symbols, and multiple 

output capability with the powerful OUTFIL feature. 

As of z/OS V1R2, DFSORT is exclusive to z/OS because the product 

DFSORT V1R14 (5740-SM1) is no longer marketed. 


Distributed File Service provides: 

w The DCE file serving (DFS (TM) ) component of the Open Group Open 

Software Foundation (OSF) DCE. The file serving support (the DFS 

client and server) is at the OSF 1.2.2 level. 

w The zSeries File System (zFS). The zFS is a UNIX file system that 

can be used in addition to the Hierarchical File System (HFS). zFS 

file systems contain files and directories that can be accessed with 

the z/OS and z/OS.e hierarchical file system file APIs. zFS file 

systems can be mounted into the z/OS UNIX hierarchy along with 

other local (or remote) file system types (such as HFS, TFS, 

AUTOMNT, and NFS). The zFS does not replace the HFS; it is 

complementary to the HFS. As of z/OS V1R7, you can use any 

combination of HFS and zFS file systems. zFS can be used for the 

root file system. Because zFS has higher performance characteristics 

than HFS and is the strategic file system, HFS might no longer be 



EREP 

ESCON (R) Director 

Support 

FFST (TM) 

GDDM (R) 

(z/OS only) 

GDDM-PGF 

(z/OS only) 

GDDM-REXX 

(z/OS only) 

OS/390 V1R1 

OS/390 V1R2 


OS/390 V1R1 

(EREP MVS (TM) V3R5, 

5658-260) 

OS/390 V1R2 

(GDDM/MVS V3R2, 

5695-167) 

OS/390 V1R2 

(GDDM/PGF V2R1.3, 

5668-812) 

OS/390 V1R2 

(GDDM-REXX/MVS 

V3R2, 5664-336) 

supported in future releases and you will have to migrate the 

remaining HFS file systems to zFS. 

The zFS provides significant performance gains in most 

environments requiring files 8 KB in size or greater that are 

frequently accessed and updated. The access performance of smaller 

files is equivalent to the HFS. For all files, the zFS provides a 

reduced exposure to loss of updates. The zFS is a logging file system 

with a write pattern to disk that reduces the points of failure after a 

system outage. For additional information about the zFS, including 

how to migrate data from the HFS to the zFS, see z/OS Distributed 

File Service zSeries File System Administration. 

The zFS component has its own FMID starting with z/OS V1R5 and 

z/OS.e V1R5. 

w Server message block (SMB) file/print serving support. The SMB 

support is based on the X/Open PC Interworking: SMB, Version 2. 

Included in the support is access to HFS, sequential, PDS, PDSE, 

and VSAM data sets from Windows XP Professional, Windows 

Terminal Server on Windows 2000, Windows Terminal Server on 

Windows 2003, SUSE Linux with Samba, and Redhat Linux with 

Samba. Windows workstation users can also exploit z/OS and 

z/OS.e printer capabilities using the SMB file/print server interface 

to the z/OS or z/OS.e Infoprint Server feature. 

For the software necessary to use the DFS or SMB file/print serving 

support, as well as the other Distributed File Service functions, see 

Appendix B, Software requirements for z/OS and z/OS.e elements 

and features in z/OS Planning for Installation. 

The DFS and SMB support use the DES 56-bit algorithm for encryption. 

Type: base element, nonexclusive. 

The Environmental Record Editing and Printing Program (EREP) edits and 

prints reports for the records placed in the error recording data set (ERDS), 

helping IBM service representatives fix problems. 


ESCON Director Support enables the reporting of ESCON director device 

errors to z/OS or z/OS.e. 


First Failure Support Technology (TM) (FFST) provides immediate 

notification and first failure data capture for software events. 

Type: base element, nonexclusive. This element is supported with z/OS but 

not with z/OS.e. With z/OS.e, you install the code but it is not functional 

and you are not licensed to use it. 

GDDM provides presentation services and device-driving capability. It 

includes PCLK and REXX code. Related optional features are 

GDDM-Presentation Graphics Feature and GDDM-REXX. Other 

GDDM-associated products (IVU, GKS, IMD) are not in z/OS, but are 

separately orderable with z/OS. 




GDDM-Presentation Graphics Feature (PGF) is a set of programs for 

creating presentation material in a variety of styles. 

This feature is related to the base element GDDM. 






HCD 

HCM 

HLASM 

HLASM Toolkit 

IBM HTTP Server 

IBM Tivoli (R) Directory 

Server for z/OS 

ICKDSF 

Infoprint Server 

z/OS V1R7 


z/OS V1R6 

(Toolkit feature of 

HLASM for MVS & VM 

& VSE V1R5, 5696-234) 

OS/390 V2R10 (but see 

description) 


z/OS V1R4 z990 

Compatibility Support 

feature 

(ICKDSF for z/OS, 

z/OS.e, and OS/390 R17, 

5655-257) 



z/OS V1R6 

(HLASM for MVS & VM 

& VSE V1R5, 5696-234) 

GDDM-REXX is a productivity tool that enables programmers to prototype 

GDDM applications and to create small routines and utility programs 

quickly and easily. 

This feature is related to the base element GDDM. 


Hardware Configuration Definition (HCD) defines both the operating 

system configuration and the processor hardware configuration for a system. 

A related optional feature is HCM. 


Hardware Configuration Manager (HCM) is a workstation-based 

client/server interface to the base element HCD. 


High Level Assembler (HLASM) integrates almost all functions of past 

assemblers and provides extensions and improvements. A related optional 

feature is the HLASM Toolkit. 


HLASM Toolkit provides tools to improve application development, 

debugging, and recovery. It is related to the base element HLASM. 


IBM HTTP Server is the Web server for z/OS and z/OS.e. It provides 

scalable, high performance Web serving for critical e-business applications. 

It supports Secure Sockets Layer (SSL) secure connections, dynamic 

caching using the Fast Response Cache Accelerator, multiple IP addresses, 

proxy authentication, and double-byte character set characters. 

IBM HTTP Server NA Secure is now a component of IBM HTTP Server. 

Before V1R6, it was an optional feature of z/OS and z/OS.e. This packaging 

change was the only change to IBM HTTP Server in V1R6; there was no 

functional change. 


IBM Tivoli Directory Server for z/OS provides client access to an LDAP 

server. It consists of a new, rewritten LDAP server (available later); an 

LDAP client; and LDAP client utilities. The LDAP client and LDAP client 

utilities can be used with the Integrated Security Services LDAP Server or, 

when available, the new IBM Tivoli Directory Server for z/OS LDAP 

server. 

For encryption, IBM Tivoli Directory Server for z/OS uses the AES, DES 

(56-bit, 112-bit, and 168-bit), SHA, MD5, and crypt algorithms. 

This base element is new in z/OS V1R8 and z/OS.e V1R8. 


The Device Support Facility (ICKDSF) enables you to perform functions 

needed for the installation and use of IBM DASD. 

ICKDSF was last changed in the z/OS V1R4 z990 Compatibility Support 

feature. This level was carried forward to the z/OS V1R4 z990 Exploitation 

Support feature and then to z/OS V1R5 and later, and is functionally 

equivalent to the R17 level of the ICKDSF product. 


Infoprint Server allows you to print files on z/OS and z/OS.e printers from 

any workstation that has TCP/IP access. This feature consists of the 

following components: 

w IP PrintWay (TM) . This component has its roots in the IP PrintWay 

feature of PSF/MVS V2R2 and the IP PrintWay/NetSpool feature of 

OS/390 V1R3. In z/OS V1R5, IP PrintWay extended mode was 

introduced. 



Integrated Security 

Services 


w NetSpool (TM) Migrating to z/OS R8 Part 1 of 3: Get Ready 

. This component has its roots in the NetSpool feature of 

PSF/MVS V2R2 and the IP PrintWay/NetSpool feature of OS/390 

V1R3. 

w Print Interface, new in OS/390 V2R5. 

w Printer Inventory Manager, new in OS/390 V2R8. 

w Transform Interface, new in OS/390 V2R8. 

w z/OS Infoprint Central, new in z/OS V1R5. 

IBM recommends that you use the Infoprint Server feature's IP PrintWay 

component rather than the Communications Server base element's Network 

Print Facility (NPF) to reroute print data to an IP network. IP PrintWay 

provides improved function, capacity, performance, and usability over NPF. 


Integrated Security Services provides base security functions for z/OS and 

z/OS.e. 

This base element was new in z/OS V1R5. It consists of components that 

used to be (before z/OS V1R5) in optional feature Security Server, plus a 

new (as of z/OS V1R5) component, Enterprise Identity Mapping. The 

components are: 

w DCE Security Server, which was last changed in OS/390 V2R9. 

This component is at the OSF DCE 1.2.2 level. This component 

uses the limited DES algorithm for encryption. 

w Enterprise Identity Mapping (EIM), introduced by a PTF in z/OS 

V1R4 and z/OS.e V1R4, and last changed in z/OS V1R8 and z/OS.e 

V1R8. This component allows you to map a user's identity on one 

system to the user's identity on another system. 

w LDAP Server, which was last changed in z/OS V1R8 and z/OS.e 

V1R8. LDAP Server uses the System SSL component of base 

element Cryptographic Services for encryption. 

The RDBM DB2 backend function of the LDAP Server is removed 

as of z/OS V1R4. You are encouraged to migrate to the enhanced 

TDBM DB2 backend because of its improved scalability and 

availability. For instructions, see z/OS Integrated Security Services 

LDAP Server Administration and Use. 

A new base element, IBM Tivoli Directory Server for z/OS, is 

provided with z/OS V1R8 and z/OS.e V1R8. It contains a new, 

rewritten LDAP server (available later); an LDAP client; and LDAP 

client utilities. The LDAP server in Integrated Security Services 

continues to exist in V1R8. However, the LDAP client and LDAP 

client utilities do not; in V1R8, they are only in IBM Tivoli 

Directory Server for z/OS. 

w Network Authentication Service, which was last changed in z/OS 

V1R6 and z/OS.e V1R6. Network Authentication Service uses the 

DES algorithm for encryption. Before z/OS V1R2, this component 

was named Network Authentication and Privacy Service. 

w Open Cryptographic Enhanced Plug-ins (OCEP), which was last 

changed in OS/390 V2R10. 

Before z/OS V1R5, the moved components (DCE Security Server, LDAP 

Server, Network Authentication Service, and OCEP), although packaged 

with the priced feature Security Server, were unpriced (that is, were licensed 

with the base operating system and could be used without ordering or 



ISPF 

JES2 

JES3 







enabling Security Server). Now that these five components are in base 

element Integrated Security Services, the packaging and pricing are 

consistent. 

The Firewall Technologies component has been removed from the system 

effective with z/OS V1R8 and z/OS.e V1R8. It was a Security Server 

component before V1R5, then an Integrated Security Services component in 

V1R6 and V1R7. 


ISPF provides facilities for all aspects of host-based software development. 

ISPF has four major components: 

w Dialog Manager (DM). The Dialog Manager provides services to 

dialogs and end users. These services include display, variable 

services, input and output, user and application profiles, table 

management, system interface services, and dialog testing and 

debugging aids. 

w Program Development Facility (PDF). PDF provides services to 

assist dialog or application developers. These include edit and 

browse functions, a wide range of foreground and batch compilers, 

data set and catalog utilities, TSO command interfaces, and data set 

search and compare functions. 

w Software Configuration and Library Manager (SCLM). SCLM is a 

tool that controls, maintains, and tracks all of the software 

components of the application throughout the development cycle. 

w Client/Server component. The Client/Server component provides 

users who have a workstation running Windows or UNIX with a 

graphical user interface to ISPF application panels. 


JES2 accepts the submission of work for the BCP. JES2 exercises 

independent control over its job processing functions, whereas JES3 

exercises centralized control. 

Prior levels of JES2 can be used with z/OS V1R8 but not with z/OS.e 

V1R8. 


JES3 accepts the submission of work for the BCP. JES3 exercises 

centralized control over its job processing functions, whereas JES2 

exercises independent control. 

Prior levels of JES3 can be used with z/OS V1R8 but not with z/OS.e 



Language Environment provides the run-time environment for programs 

generated with C, C++, COBOL, Fortran, and PL/I. 

z/OS.e Language Environment does not support (but z/OS Language 

Environment does support) the following: 

w COBOL, except for execution of precompiled COBOL DB2 stored 

procedures and other precompiled applications that use the Language 

Environment preinitialization interface (CEEPIPI). The applications 

could be compiled on a z/OS system, then run on a z/OS.e system. 

Stated another way, compiling COBOL programs on z/OS.e is not 

supported, and only precompiled COBOL DB2 stored procedures 

and other precompiled applications that use the Language 

Environment CEEPIPI (no other kinds of COBOL programs) can 

run on z/OS.e. 



Library Server 

MICR/OCR 

(z/OS only) 

msys for Setup 

NFS 

z/OS V1R7 

OS/390 V1R1 

z/OS V1R4 (but see 

description) 



w Fortran. 

w PL/I, except for execution of precompiled PL/I applications. As with 

COBOL, the applications could be compiled on a z/OS system, then 

run on a z/OS.e system. 

w Compatibility preinitialization for C and PL/I. 

w The library routine retention (LRR) function. (In z/OS, LRR can 

improve the performance of applications and subsystems.) 

Inclusion of Language Environment as a base element in z/OS and z/OS.e 

does not replace the need for separate compilers. 

As of z/OS V1R2, Language Environment supports the ISO 1998 C++ 

Standard Library. 

Language Environment uses the limited DES algorithm for encryption. 


Library Server converts BookManager documents to HTML for display 

through a web browser. Before z/OS V1R5, this element was named 

BookManager BookServer. 

Type: base element, exclusive. This element is supported with z/OS but not 

with z/OS.e. With z/OS.e, you install the code but you are not licensed to 

use it. 

This element provides the device support code for various magnetic and 

optical devices. 


Managed System Infrastructure for Setup (msys for Setup) was introduced 

in z/OS V1R1 to provide a graphical user interface for configuring z/OS, 

z/OS.e, and products that run on z/OS and z/OS.e. With z/OS V1R8, much 

of the function has been removed from msys for Setup. Of the seven 

plug-ins that supported the framework, six have been removed. The six 

plug-ins removed in z/OS V1R8 are: 

w IP Services 

w ISPF 

w Language Environment 

w Parallel Sysplex (R) 

w RMF (TM) 

w z/OS UNIX 

The only remaining plug-in, the DB2 V8 plug-in, is unaffected and remains 

available for enablement, setup, and configuration of DB2. Also remaining 

are the framework and DFSMS support. 

If you've been using any of the plug-ins that are no longer available, see 

z/OS Migration. 


Network File System (NFS) acts as a file server to workstations, personal 

computers, or other authorized systems in a TCP/IP network. It consists of a 

client and a server. It supports Berkeley sockets but not TCP/IP sockets. 

NFS uses the Network Authentication Service component of Integrated 

Security Services for encryption. 

NFS is always enabled, even when the alternate base configuration is 

ordered. 

In z/OS V1R8, the NFS server and client FMIDs were merged into one 

FMID. 



OSA/SF 

RMF 

Run-Time Library 

Extensions 

SDSF 

Security Server 

SMP/E 






z/OS V1R4 z990 

Compatibility Support 

feature 

z/OS V1R7 

(SMP/E for z/OS V3R4, 

5655-G44) 


Open Systems Adapter/Support Facility (OSA/SF) provides a user-friendly 

interface for monitoring and controlling the zSeries Open Systems Adapter 

feature, which provides network connectivity directly to local area networks 

(LANs) and wide area networks (WANs) that support IP and SNA 

protocols. OSA/SF supports Gigabit, Token Ring, Fast Ethernet, 

1000Base-T Ethernet, 10 Gigabit Ethernet, and ATM features depending on 

the server on which z/OS runs. For details, see System z9 and zSeries 

OSA-Express Customer's Guide and Reference, SA22-7935. 

OSA/SF was last changed in the z/OS V1R4 z990 Compatibility Support 

feature. This level was carried forward to the z/OS V1R4 z990 Exploitation 

Support feature and then to z/OS V1R5 and later. 

OSA/SF became exclusive with the introduction of the z/OS V1R4 z990 

Compatibility Support feature. 


Resource Measurement Facility (RMF) gathers data about z/OS and z/OS.e 

resource usage and provides reports at any system in a sysplex. 


Run-Time Library Extensions, introduced in z/OS V1R5 and z/OS.e V1R5, 

extends the run-time support provided by the Language Environment base 

element. It consists of : 

w Common Debug Architecture (CDA) libraries and utilities. 

w UNIX System Laboratories (USL) I/O Stream Library and USL 

Complex Mathematics Library, previously included in the base 

element C/C++ IBM Open Class (R) Library. 

w IBM Open Class dynamic link libraries (DLLs), previously included 

in the base element C/C++ IBM Open Class Library. 

Note: 

z/OS V1R8 and z/OS.e V1R8 are planned to be the last releases that 

include the IBM Open Class (IOC) dynamic link libraries (DLLs). 


System Display and Search Facility (SDSF) provides you with information 

to monitor, manage, and control your z/OS or z/OS.e system. 

Although prior levels of JES2 may be used with z/OS V1R8, prior levels of 

SDSF may not. 

In z/OS.e, BookManager help is not available for SDSF SYSLOG 

messages. This is because BookManager READ is not available in z/OS.e. 


Security Server lets you control access to protected resources. 

Security Server now consists of one component, RACF. In z/OS V1R5, its 

other components were moved to two base elements: Integrated Security 

Services (which was new in V1R5) and Cryptographic Services. The base 

element Integrated Security Services received the five components DCE 

Security Server, Firewall Technologies, LDAP Server, Network 

Authentication Service, and OCEP. The base element Cryptographic 

Services received the component PKI Services. 

Security Server uses the limited DES, CDMF, RC 40-bit, RSA, and DSA 

algorithms for encryption. 


SMP/E is a tool for installing and maintaining software, and for managing 

the inventory of software that has been installed. 

Before z/OS V1R2, SMP/E was an exclusive base element. Beginning with 

z/OS V1R2, SMP/E is nonexclusive because of the introduction of the 



TIOC 

TSO/E 


OS/390 V1R1 




SMP/E product. The SMP/E product allows customers who are currently 

licensed for an earlier level of z/OS or z/OS.e to order and install the latest 

level of SMP/E without having to upgrade their entire operating system. 

This allows products that run on z/OS or z/OS.e to exploit the packaging 

and installation enhancements of SMP/E without requiring a later level of 

the operating system. This also allows customers to exploit new electronic 

delivery and installation technologies in SMP/E sooner. The SMP/E product 

is available at no additional charge to customers. 

The Planning and Migration Assistant (PMA), a component of SMP/E, can 

help you maintain, plan for, and order new releases of z/OS, z/OS.e, and 

other products. It provides reports that use IBM-supplied data, your SMP/E 

consolidated software inventory (CSI) data set, and a CustomPac inventory 

file. The PMA Web site is 

http://www.ibm.com/eserver/zseries/zos/smpe/pma/. 


TIOC allows console services and TSO/E to communicate with the terminal 

hardware. 


Time Sharing Option/Extensions (TSO/E) provides an interactive terminal 

interface. As in prior releases of TSO/E, this element includes CLISTs and 

REXX, but does not include a REXX compiler. 

In z/OS.e, the number of concurrent TSO/E sessions is limited to eight. 

Type: optional feature, exclusive, unpriced, cannot be dynamically enabled. 

z/OS Security Level 3 provides strong encryption for z/OS and z/OS.e. 

The components in this feature are: 

w IBM Tivoli Directory Server for z/OS Security Level 3, which is 

new in z/OS V1R8 and z/OS.e V1R8. This component works in 

conjunction with the IBM Tivoli Directory Server for z/OS base 

element, and with the LDAP Server component of the Integrated 

Security Services base element, to provide stronger encryption 

(greater than 64 bits) than that available without the z/OS Security 

Level 3 feature. This component uses the RC4, TDES, and 

Advanced Encryption Standard (AES) algorithms for encryption. 

This component replaces LDAP Security Level 3, which was added 

in z/OS V1R6. 

w Network Authentication Service Level 3, which was last changed in 

z/OS V1R6 and z/OS.e V1R6. This component works in 

conjunction with the Network Authentication Service component of 

the Integrated Security Services base element to provide stronger 

encryption (greater than 64 bits) than that available without the z/OS 

Security Level 3 feature. This component uses the TDES algorithm 

for encryption. 

This component was new in z/OS V1R2. At that time it was named 

SecureWay (R) Security Server Network Authentication Service Level 

3. As of z/OS V1R3 and z/OS.e V1R3, the word "SecureWay" was 

dropped from the name. As of z/OS V1R5 and z/OS.e V1R5, the 

words "Security Server" are dropped from the name. 

w OCSF Security Level 3, which was last changed in OS/390 V2R10. 

This component works in conjunction with the OCSF component of 

the Cryptographic Services base element to provide stronger 

encryption (greater than 64 bits) than that available without the z/OS 

Security Level 3 feature. This component uses the TDES, DES, and 

RC2/RC4/RC5 algorithms for encryption. 



z/OS UNIX 

3270 PC File Transfer 

Program 



w System Secure Sockets Layer (SSL) Security Level 3, which was last 

changed in z/OS V1R8 and z/OS.e V1R8. This component works in 

conjunction with the System SSL component of the Cryptographic 

Services base element to provide stronger encryption (greater than 

64 bits) than that available without the z/OS Security Level 3 

feature. This component uses the RC2/RC4, TDES, and AES 

algorithms for encryption. 

Before z/OS V1R5, three of the components in z/OS Security Level 3 were 

separate features. In z/OS V1R5 they were repackaged, for the purpose of 

simplifying ordering, into the new feature z/OS Security Level 3. The three 

components are Network Authentication Service Level 3, OCSF Security 

Level 3, and System SSL Security Level 3. 

This feature is worldwide exportable subject to U.S. export regulations. 

OS/390 V1R2 

(3270 PC File Transfer 

Program V1R1.1, 

5665-311) 


z/OS UNIX System Services (z/OS UNIX) provides the standard command 

interface familiar to interactive UNIX users. This element is made up of four 

components: 

w Application Services, which was last changed in z/OS V1R8 and 

z/OS.e V1R8. This component includes the Shell, Utilities, 

Debugger, and Parallel Environment. 

w Connection Manager, which was last changed in OS/390 V2R7. 

w Integrated Call Level Interface (ICLI), which was last changed in 

z/OS V1R6 and z/OS.e V1R6. 

w Process Manager, which was last changed in OS/390 V2R7. 


3270 PC File Transfer Program transfers files from the host to the 

workstation for offline data manipulation, updating, or correction or for the 

transfer and storage of local data in the host system. 



Appendix B: Coexistence Service for z/OS V1.8 

Coexistence and fallback PTFs installed on back-level systems allow those systems to coexist with z/OS V1R8 systems 

during your migration, and allow backout from z/OS V1R8 to the back-level systems if necessary. Coexistence and 

fallback are important because they allow you to migrate systems in a multisystem configuration to z/OS V1R8 using 

rolling IPLs (one system at a time), allowing for continuous application availability. 

Depending on which back-level releases your z/OS V1R8 system is coexisting with, install the coexistence and fallback 

PTFs that are listed in the following tables. The first table is for coexistence and fallback service on z/OS V1R6 for z/OS 

V1R8. The second table is for coexistence and fallback service on z/OS V1R5 for z/OS V1R8. (For coexistence and 

fallback service on z/OS V1R7 for z/OS V1R8, see the body of this presentation.) 

z/OS V1R6 coexistence and fallback PTFs 

Install, on z/OS V1R6, the coexistence and fallback PTFs listed below. 



BCP: Ensures that pre-z/OS V1R8 systems tolerate the new format of the z/OS V1R8 WLM 

service definition and service policy in the WLM couple data set. Moreover, the PTF ensures 

the toleration of changed WLM LPAR management and JES initiator management 

information that is exchanged in a mixed-release (z/OS V1R8 and pre-z/OS V1R8) sysplex. 

If the WLM service policy in the couple data set has been activated by a z/OS V1R8 system, 

a pre-z/OS V1R8 system without the PTF will not be able to activate the policy and might 

fail during IPL with a wait state 064. If LPAR management is being used in a mixed-release 

sysplex and the PTF is not installed, you might experience abends and see message 

IWM054I FAILURE IN LPAR CPU MANAGEMENT, PROCESSING DISABLED. 

BCP: In z/OS V1R8, SYSIN DD * override statements are no longer required to reside in 

the job stream in the same order as the corresponding DD statements appear in the 

procedure. Because new text units are introduced for each SYSIN DD * statement, the PTF 

allows jobs to ignore the new text units when they run in a JES2 environment and convert on 

a z/OS V1R8 system but interpret on an earlier system. 

BCP: If an application developer compiles or assembles with the z/OS V1R8 program 

management binder version 6 API invocation macros, or codes to the new STARTD API 

interface, and the resulting program is run on an earlier release of z/OS, the binder STARTD 

API will fail with return code 12, invalid parameter list, message IEW2132S 0064 

INCORRECT NUMBER OF PARAMETERS PASSED FOR CALL. The PTF allows such a 

calling program to execute successfully. 

BCP: If an application developer uses the z/OS V1R8 program management binder to create 

a program object with the latest format in a PDSE, the PTF is needed so that an ISPF user 

can browse the PDSE on z/OS V1R6. 

BCP: In z/OS V1R8, the console restructure enhancement eliminates the master console 

and the console switch function. The PTF allows earlier systems to tolerate the enhancement. 

BCP: A z/OS V1R7 or later system cannot join a sysplex of earlier-level systems, and an 

earlier-level system cannot join a sysplex of z/OS V1R7 or later systems, without this PTF. 

BCP: Allows a z/OS V1R6 system to tolerate the z/OS V1R8 logger log stream GROUP 

designation and renamed log streams. 

BCP: z/OS V1R7 introduced the logger log stream DUPLEXMODE(DRXRC) 

specification. If DUPLEXMODE(DRXRC) is specified in a z/OS V1R7 or later system in a 

sysplex, and prior releases are running in the same sysplex, the PTF must be installed. If 

DUPLEXMODE(DRXRC) is not specified, installing the PTF is not required but is 

nevertheless recommended to avoid any complications if the configuration changes. 

BCP: Allows a pre-z/OS V1R7 system to use an IODF that was created using z/OS V1R7 or 

later HCD. 

BCP: Increased CPU utilization in the console address space might be reported on all 

systems in a sysplex after introducing a z/OS V1R4 system with the z/OS V1R4 Consoles 


UA90268 

UA24559 

UA24436 

UA25783 

UA26397 and, if Japanese, 

UA26399 

UA16036 

UA24158, UA25587 

UA17179 

UA17028 

UA16510 




Enhancements feature, or later-level system, into the sysplex. The coexistence PTF prevents 

heavy message traffic on the z/OS V1R7 or later system from impacting the other systems in 

the sysplex. 

BCP: Allows a z/OS V1R6 system to correctly handle blank WTOs issued to another 

system. 

BCP: Large format sequential data sets are only supported by z/OS V1R7 and later. The 

coexistence PTF causes z/OS to detect the accidental specification of such a data set for 

stand-alone dump output and to reject its use, as has been done for data set organizations 

such as PDS. 

BCP: Provides compatibility support for the corrected global resource serialization 

ISGLOCK structure rebuild processing in z/OS V1R7 APAR OA11147 (and rolled into 

z/OS V1R8). 

BCP: Allows a z/OS V1R6 system to tolerate changes made to resource recovery services 

(RRS) display and ATRQUERY functions in z/OS V1R8. 

DFSMSdfp: Program object format 5 (PO5 format) is new in z/OS V1R8. The PTF allows 

PDSE program libraries that contain PO5 program objects to be processed by IEBCOPY on 

z/OS V1R6 systems. 

DFSMSdfp: An enhancement in the z/OS V1R8 object access method (OAM) component 

introduced a new ODLOBFL column in the object directory to exploit DB2 binary large 

object (BLOB) support. The PTF enables pre-z/OS V1R8 OAMs to coexist in an OAMplex 

with OAMs at the z/OS V1R8 or later level. 

DFSMSdfp: An enhancement in the z/OS V1R7 object access method (OAM) component 

introduced a new valid value ("R") for the object location in the object directory to indicate 

that the object resides on DB2 disk in recalled status. This PTF enables pre-z/OS V1R7 

OAMs to coexist in an OAMplex with OAMs at the z/OS V1R7 or later level. 

DFSMSdfp: As part of VSAM extent constraint removal in z/OS V1R7, these PTFs 

prevent pre-z/OS V1R7 systems from opening data sets that have more than 255 extents. 

Also, if a data set is open and a z/OS V1R7 or later job extends it past 255 extents, the close 

on the pre-z/OS V1R7 system fails. Finally, these PTFs prevent conversion of a data set 

having more than 255 extents from being converted by DFSMSdss to a non-SMS managed 

data set on pre-z/OS V1R7 releases. 

DFSMSdfp: z/OS V1R7 introduced new QNAME and RNAME parameters for VSAM 

RLS. The coexistence PTFs prevent serialization problems from occurring when the new 

parameters are used in a global resource serialization complex that includes a pre-z/OS V1R7 

system. 

DFSMSdfp: In z/OS V1R8, the D SMS,SMSVSAM,DIAG(CONTENTION) command is 

introduced to display internal VSAM RLS contention. The PTF allows a z/OS V1R6 system 

that receives the new DIAG CONTENTION command to tolerate the command by issuing a 

message analogous to IGW495I D SMS,SMSVSAM,DIAG COMMAND FUNCTION HAS 

FOUND THE DIAG TABLE HAS NO ENTRIES. If the PTF is not installed, the z/OS 

V1R6 system receiving the new command treats it as an irrelevant and confusing console 

message. 

DFSMSdfp: In z/OS V1R8, a performance improvement to VSAM RLS causes XES lock 

table cleanup to be skipped when the SMSVSAM address space is terminated, as 

documented in APAR OA11708. This PTF allows a z/OS V1R6 system to tolerate the 

enhancement. 

DFSMSdfp: z/OS V1R7 and later support large format sequential data sets. These PTFs 

cause pre-z/OS V1R7 systems to issue ABEND 213-14 or 213-16 if a program attempts to 

open data sets that cannot work on those systems. 

DFSMSdss: z/OS V1R7 and later support large format sequential data sets. These PTFs 

cause pre-z/OS V1R7 systems to issue ABEND213-14 for any large format dump data sets 

that are provided as input to RESTORE or COPYDUMP, or output for DUMP and 

UA09962 

UA19042 

UA18542 

UA27071 

UA22350 

UA24412 

UA16996 

UA14884, UA16225, UA16798 

UA16635, UA16924, UA17236 

UA24373 

UA21541 

UA15871, UA16552, UA18496 

UA16798 




COPYDUMP. If DFSMSdss encounters any large format sequential data sets as input to 

logical data set COPY, logical and physical data set DUMP and RESTORE, data set print, or 

logical and physical data set RELEASE, the data set will fail with ADR878E rsn 17. 

DFSMShsm: Allows a z/OS V1R6 system to tolerate the changes made by the fast 

replication tape support enhancement in z/OS V1R8. 

DFSMShsm: In z/OS V1R8, dump volume (DVL) and dump class (DCL) control data set 

records were enlarged as part of the DFSMShsm dump encryption enhancement. The PTF 

allows a z/OS V1R6 system to tolerate the increase in record size. 

DFSMShsm: z/OS V1R7 and later support large format sequential data sets. The PTFs 

cause pre-z/OS V1R7 systems that might potentially recall, recover, or ARECOVER a data 

set to first verify that the data set is not a large format data set. If it is, an error message is 

issued describing the reason for the failure. 

DFSMShsm: z/OS V1R7 and later support large format sequential data sets. In an 

HSMplex with more than one DFSMShsm host, take care when migrating the journal to a 

large format sequential data set. All DFSMShsm hosts within an HSMplex must be at z/OS 

V1R7 or later before you can migrate the journal to a large format sequential data set. 

With the PTFs, when a pre-z/OS V1R7 DFSMShsm host attempts to open a journal, if the 

journal is a standard format data set, DFSMShsm initialization continues. If the journal is a 

large format data set, message MSGARC0509E with the "LARGE" text in the message is 

issued and DFSMShsm is stopped. If the journal is a striped data set, message 

MSGARC0509E with the "STRIPED" text in the message is issued and DFSMShsm is 

stopped. If the ARCBJRNL utility attempts to use a large format journal data set, it ends with 

return code RC40, which indicates an OPEN error. 

DFSMShsm: z/OS V1R7 and later support fast subsequent migration (FSM) of data sets. 

The PTFs cause DFSMShsm to set the appropriate flags during recall processing so that if 

the data set is later opened for output by either z/OS V1R7 systems or pre-z/OS V1R7 

systems, the flags used for reconnection determination are set appropriately. 

DFSMShsm: z/OS V1R7 increased the number of data set names supported in a tape table 

of contents (TTOC). If a system that has the coexistence PTF installed finds that the OCDS 

RECORDSIZE is 6144 bytes, which indicates that some instances of DFSMShsm in the 

HSMplex might be using the extended TTOC, then tape operations on that level of 

DFSMShsm are inhibited. 

DFSMSrmm: Allows a pre-z/OS V1R8 system in a client/server environment to participate 

in an RMMplex in which a z/OS V1R8 system has been started. Optionally, you can specify 

UTC(YES) with the EDGUTIL utility on z/OS V1R8 to enable DFSMSrmm common time 

support. 

DFSMSrmm: Allows a pre-z/OS V1R8 system to participate in an RMMplex in which a 

z/OS V1R8 system has been started. In particular, the PTF enables VRSEL processing to 

recognize the use of the special ABEND and OPEN vital record specifications and to 

correctly handle COUNT(0). It also prevents the continued use of the unsupported options 

STARTNUMBER and LOCATION(BOTH). 

Distributed File Service: Allows pre-z/OS V1R7 systems to tolerate new characters (@#$) 

allowed in z/OS V1R7 and later for zFS file systems and aggregates. 

Distributed File Service: Allows pre-z/OS V1R7 systems to tolerate the file system 

structure for z/OS V1R7 and later zFS file systems. 

HCD: Provides support for HCD users who share IODF data sets between pre-z/OS V1R7 

systems and z/OS V1R7 or later systems. 

ISPF: Allows pre-z/OS V1R7 systems to intelligently display the number of tracks in a large 

format sequential data set. If the number of tracks is greater than 64 KB, the string ">64K" 

and a larger explanatory message are written to the panel. 

ISPF: Provides an appropriate message when a user attempts to open a large format 

sequential data set from a pre-z/OS V1R7 release. 

UA25404 

UA22715 

UA16798, UA16953 

UA15871, UA16552, UA16956, 

UA18496 

UA16851, UA16859, UA16862, 

UA16946 

UA16949 

UA25144 if not using client/server 

DFSMSrmm, or both UA25144 and 

UA00009 if using client/server 

DFSMSrmm 

UA22044 

UA14530 

UA20483 

UA90174 (base and English), 

UA90175 (Japanese) 

UA19930, UA20545 

UA19933, UA19942 (Swiss 

German), UA19943 (Japanese), 



JES2: Allows an earlier JES2 to run with z/OS V1R8 JES2 in a multi-access spool (MAS). 

Install the PTFs that are appropriate to the JES2 level that you are using. 

JES2: Fixes a problem on a receiving pre-z/OS V1R7 node that can occur in a rare situation 

with a large scheduler work block text unit (SWBTU). Data sets have a large SWBTU when 

MAILTO, MAILCC, and MAILBCC keywords are used in addition to other keywords on 

OUTPUT JCL statements. The problem is caused by APAR OA09152 (PTF UA16214 on 

z/OS V1R5-V1R6 JES2 or PTF UA16213 on z/OS V1R4 JES). This is a network-specific 

problem, not a MAS-specific problem. 

JES3: Allows a pre-z/OS V1R8 JES3 to tolerate the removal of various symbols from the 

IHAWQE macro, which was done as part of the console improvements made in z/OS 


Language Environment: Causes a meaningful message to be issued when a new z/OS 

V1R8 Language Environment run-time option is encountered by an earlier release. The 

message states that the option is ignored. If the PTF is not installed, the option is still ignored 

but a less meaningful message, or no message at all, is issued. 

NFS: Allows a z/OS V1R7 system to read the new NFS export file format generated by a 

z/OS V1R8 system. 

NFS: Allows a pre-z/OS V1R7 NFS SMF report generator to process an SMF file that 

includes NFS V1R7 or later SMF records. Any records containing TCP/IP version 6 IP 

addresses will be ignored. 

NFS: Allows a pre-z/OS V1R7 NFS server to read a mount handle data set written by z/OS 

V1R7 or later NFS. 

RMF: Ensures the toleration of new z/OS V1R8 functionality for sysplex-wide RMF 

reporting in earlier releases. 

Security Server: In z/OS V1R8, the structure of the RACF database was changed to allow 

a template block to be continued into another block. The PTF allows a z/OS V1R6 system to 

process templates that extend into another block. If you share a RACF database between 

z/OS V1R8 and z/OS V1R6, you need to install the PTF on the z/OS V1R6 system. 

SMP/E: Provides support for SMP/E users who share SMPCSI data sets between pre-z/OS 

V1R7 systems and z/OS V1R7 or later systems. 

z/OS V1R5 coexistence and fallback PTFs 

Install, on z/OS V1R5, the coexistence and fallback PTFs listed below. 



UA19944 (German), UA19945 

(uppercase English) 

z/OS V1R5-V1R6 JES2: UA09501, 

UA18836, UA20902, UA90161, 

UA24983 

z/OS V1R5-V1R6 JES2: UA16217 

z/OS V1R5-V1R6 JES3: UA24989 

UK12451 

UA25098 

UA16683 

UA19507 

UA26131 

UA24979 

UO00116 

BCP: Ensures that pre-z/OS V1R8 systems tolerate the new format of the z/OS V1R8 WLM service 

definition and service policy in the WLM couple data set. Moreover, the PTF ensures the toleration of 

changed WLM LPAR management and JES initiator management information that is exchanged in a 

mixed-release (z/OS V1R8 and pre-z/OS V1R8) sysplex. 

If the WLM service policy in the couple data set has been activated by a z/OS V1R8 system, a pre-z/OS 

V1R8 system without the PTF will not be able to activate the policy and might fail during IPL with a 

wait state 064. If LPAR management is being used in a mixed-release sysplex and the PTF is not 

installed, you might experience abends and see message IWM054I FAILURE IN LPAR CPU 

MANAGEMENT, PROCESSING DISABLED. 

BCP: In z/OS V1R8, SYSIN DD * override statements are no longer required to reside in the job stream 

in the same order as the corresponding DD statements appear in the procedure. Because new text units 

are introduced for each SYSIN DD * statement, the PTF allows jobs to ignore the new text units when 

they run in a JES2 environment and convert on a z/OS V1R8 system but interpret on an earlier system. 


UA90267 

UA24558 




BCP: If an application developer compiles or assembles with the z/OS V1R8 program management 

binder version 6 API invocation macros, or codes to the new STARTD API interface, and the resulting 

program is run on an earlier release of z/OS, the binder STARTD API will fail with return code 12, 

invalid parameter list, message IEW2132S 0064 INCORRECT NUMBER OF PARAMETERS PASSED 

FOR CALL. The PTF allows such a calling program to execute successfully. 

BCP: If an application developer uses the z/OS V1R8 program management binder to create a program 

object with the latest format in a PDSE, the PTF is needed so that an ISPF user can browse the PDSE on 

z/OS V1R5. 

BCP: In z/OS V1R8, the console restructure enhancement eliminates the master console and the 

console switch function. The PTF allows earlier systems to tolerate the enhancement. 

BCP: In z/OS V1R5, a console enhancement minimizes the possibility of outages because of 

exhaustion of system resources used for messaging. The PTFs allow earlier systems to tolerate the 

enhancement. 

BCP: Prevents the depletion of private storage in the console address space on a receiving system when 

a large number of WTO/R messages are received on that system from other members of a sysplex. 

BCP: Increased CPU utilization in the console address space might be reported on all systems in a 

sysplex after introducing a z/OS V1R4 system with the z/OS V1R4 Consoles Enhancements feature, or 

later-level system, into the sysplex. The coexistence PTF prevents heavy message traffic on the z/OS 

V1R7 or later system from impacting the other systems in the sysplex. 

BCP: Allows a z/OS V1R5 system to correctly handle blank WTOs issued to another system. 

BCP: APARs OA05025 (PTF UA07361) and OA05391 together provide corrective service for XCF 

recovery from partial writes to couple data sets. APAR OA05391 introduces a new format for couple 

data set multi-subrecord check records (MSRCRs), which is required for recovery from partial writes to 

certain types of couple data set records. APAR OA05025 includes coexistence support that enables 

systems on which it is installed to interpret the new MSRCR format. 

Because both APARs have been incorporated into z/OS V1R6 and later, all other systems in the sysplex 

must be capable of interpreting the new MSRCR format before any V1R6 or later system can be IPLed 

into the sysplex. V1R5 systems include support for interpreting the new MSRCR format and do not 

require installation of additional maintenance to provide this capability. You must IPL all other systems 

in the sysplex with the appropriate PTF for APAR OA05025 (PTF UA07361 for V1R5) before IPLing 

any V1R6 or later system into the sysplex. Rolling IPLs are sufficient to install the PTFs for APARs 

OA05025 and OA05391. Note that the recovery provided by these two PTFs is not completely effective 

until all systems in the sysplex, including z/OS V1R5 systems, have been IPLed with both PTFs or with 

V1R6 or later. 

BCP: z/OS V1R6 has a new 64-bit global resource serialization ISGQUERY application programming 

interface (API). The PTF allows a z/OS V1R5 system to tolerate ISGQUERY requests from a z/OS 

V1R6 or later system. 

BCP: Provides compatibility support for the corrected global resource serialization ISGLOCK structure 

rebuild processing in z/OS V1R7 APAR OA11147 (and rolled into z/OS V1R8). 

BCP: Allows a z/OS V1R5 system to tolerate changes made to resource recovery services (RRS) 

display and ATRQUERY functions in z/OS V1R8. 

BCP: Allows a z/OS V1R5 system to tolerate new resource recovery services (RRS) restart function in 

z/OS V1R6 (and later). 

BCP: Starting in z/OS V1R6, the sysplex couple data set (CDS) can be expanded to allow up to 2047 

members in a cross-system coupling facility (XCF) group. This is an increase from the previous 

maximum of 1023 members per XCF group. Formatting a couple data set for more than 1023 members 

per group creates a Version 4 CDS. 

The PTF rolls back this function to z/OS V1R5. In terms of coexistence, it provides support for Version 

4 sysplex CDSs on z/OS V1R5. This is important because all systems in a sysplex must support Version 

4 sysplex CDSs to bring a Version 4 sysplex CDS into use, and once a sysplex is using a Version 4 

sysplex CDS, a system that does not support Version 4 sysplex CDSs cannot join the sysplex. 

BCP: A z/OS V1R7 or later system cannot join a sysplex of earlier-level systems, and an earlier-level 

system cannot join a sysplex of z/OS V1R7 or later systems, without this PTF. 

UA24435 

UA25782 

UA26404 and, if 

Japanese, UA26401 

UA05643, UA06655 

UA07960, UA07963 

UA16512 

UA09964 

UA07361 

UA09226 

UA18541 

UA27070 

UA09403, UA09425 

UA09967 

UA16038 




BCP: Allows a z/OS V1R5 system to tolerate the z/OS V1R8 logger log stream GROUP designation 

and renamed log streams. 

BCP: z/OS V1R7 introduced the logger log stream DUPLEXMODE(DRXRC) specification. If 

DUPLEXMODE(DRXRC) is specified in a z/OS V1R7 or later system in a sysplex, and prior releases 

are running in the same sysplex, the PTF must be installed. If DUPLEXMODE(DRXRC) is not 

specified, installing the PTF is not required but is nevertheless recommended to avoid any complications 

if the configuration changes. 

BCP: Allows a pre-z/OS V1R7 system to use an IODF that was created using z/OS V1R7 or later HCD. 

BCP: Large format sequential data sets are only supported by z/OS V1R7 and later. The coexistence 

PTF causes z/OS to detect the accidental specification of such a data set for stand-alone dump output and 

to reject its use, as has been done for data set organizations such as PDS. 

BCP, DFSMSdfp, DFSMSdss, DFSMShsm, DFSMSrmm: In z/OS V1R6, a new function introduced 

by PTF UA90124 enables DFSMS software support for IBM TotalStorage (R) Enterprise Tape System 

3592 and the media types MEDIA6, MEDIA7, and MEDIA8. Coexistence PTFs listed here allow a 

V1R5 system to coexist with a V1R6 or later system that uses this function. 

DFSMSdfp: Program object format 5 (PO5 format) is new in z/OS V1R8. The PTF allows PDSE 

program libraries that contain PO5 program objects to be processed by IEBCOPY on z/OS V1R5 

systems. 

DFSMSdfp: z/OS V1R6 has a new PDSE address space, SMSPDSE1, which is restartable. The 

coexistence PTF allows a z/OS V1R5 system to coexist with a z/OS V1R6 or later system that is 

exploiting the new address space. 

DFSMSdfp: An enhancement in the z/OS V1R8 object access method (OAM) component introduced a 

new ODLOBFL column in the object directory to exploit DB2 binary large object (BLOB) support. The 

PTF enables pre-z/OS V1R8 OAMs to coexist in an OAMplex with OAMs at the z/OS V1R8 or later 

level. 

DFSMSdfp: An enhancement in the z/OS V1R7 object access method (OAM) component introduced a 

new valid value ("R") for the object location in the object directory to indicate that the object resides on 

DB2 disk in recalled status. This PTF enables pre-z/OS V1R7 OAMs to coexist in an OAMplex with 

OAMs at the z/OS V1R7 or later level. 

DFSMSdfp: As part of VSAM extent constraint removal in z/OS V1R7, these PTFs prevent pre-z/OS 

V1R7 systems from opening data sets that have more than 255 extents. Also, if a data set is open and a 

z/OS V1R7 or later job extends it past 255 extents, the close on the pre-z/OS V1R7 system fails. Finally, 

these PTFs prevent conversion of a data set having more than 255 extents from being converted by 

DFSMSdss to a non-SMS managed data set on pre-z/OS V1R7 releases. 

DFSMSdfp: z/OS V1R7 introduced new QNAME and RNAME parameters for VSAM RLS. The 

coexistence PTFs prevent serialization problems from occurring when the new parameters are used in a 

global resource serialization complex that includes a pre-z/OS V1R7 system. 

DFSMSdfp: In z/OS V1R8, the D SMS,SMSVSAM,DIAG(CONTENTION) command is introduced to 

display internal VSAM RLS contention. The PTF allows a z/OS V1R5 system that receives the new 

DIAG CONTENTION command to tolerate the command by issuing a message analogous to IGW495I 

D SMS,SMSVSAM,DIAG COMMAND FUNCTION HAS FOUND THE DIAG TABLE HAS NO 

ENTRIES. If the PTF is not installed, the z/OS V1R5 system receiving the new command treats it as an 

irrelevant and confusing console message. 

DFSMSdfp: In z/OS V1R8, a performance improvement to VSAM RLS causes XES lock table cleanup 

to be skipped when the SMSVSAM address space is terminated, as documented in APAR OA11708. 

This PTF allows a z/OS V1R5 system to tolerate the enhancement. 

DFSMSdfp: z/OS V1R7 and later support large format sequential data sets. These PTFs cause 

pre-z/OS V1R7 systems to issue ABEND 213-14 or 213-16 if a program attempts to open data sets that 

cannot work on those systems. 

DFSMSdss: z/OS V1R7 and later support large format sequential data sets. These PTFs cause 

pre-z/OS V1R7 systems to issue ABEND213-14 for any large format dump data sets that are provided as 

input to RESTORE or COPYDUMP, or output for DUMP and COPYDUMP. If DFSMSdss encounters 

UA24157, UA25586 

UA17178 

UA17027 

UA19041 

UA90101, UA90113, 

UA90121, UA90127, 

UA90129 

UA22349 

UA09833 

UA24411 

UA16995 

UA14883, UA16224, 

UA16797 

UA16634, UA16923, 

UA17235 

UA24372 

UA21540 

UA15870, UA16551, 

UA18495 

UA16797 




any large format sequential data sets as input to logical data set COPY, logical and physical data set 

DUMP and RESTORE, data set print, or logical and physical data set RELEASE, the data set will fail 

with ADR878E rsn 17. 

DFSMShsm: Allows a z/OS V1R5 system to tolerate the changes made by the fast replication tape 

support enhancement in z/OS V1R8. 

DFSMShsm: In z/OS V1R8, dump volume (DVL) and dump class (DCL) control data set records were 

enlarged as part of the DFSMShsm dump encryption enhancement. The PTF allows a z/OS V1R5 system 

to tolerate the increase in record size. 

DFSMShsm: z/OS V1R7 and later support large format sequential data sets. The PTFs cause 

pre-z/OS V1R7 systems that might potentially recall, recover, or ARECOVER a data set to first verify 

that the data set is not a large format data set. If it is, an error message is issued describing the reason for 

the failure. 

DFSMShsm: z/OS V1R7 and later support large format sequential data sets. In an HSMplex with 

more than one DFSMShsm host, take care when migrating the journal to a large format sequential data 

set. All DFSMShsm hosts within an HSMplex must be at z/OS V1R7 or later before you can migrate the 

journal to a large format sequential data set. 

With the PTFs, when a pre-z/OS V1R7 DFSMShsm host attempts to open a journal, if the journal is a 

standard format data set, DFSMShsm initialization continues. If the journal is a large format data set, 

message MSGARC0509E with the "LARGE" text in the message is issued and DFSMShsm is stopped. 

If the journal is a striped data set, message MSGARC0509E with the "STRIPED" text in the message is 

issued and DFSMShsm is stopped. If the ARCBJRNL utility attempts to use a large format journal data 

set, it ends with return code RC40, which indicates an OPEN error. 

DFSMShsm: In z/OS V1R5, DFSMShsm is enhanced to use volume-level fast replication to create 

backup versions for sets of storage groups. A set of storage groups is defined through an SMS construct 

termed "copy pool". In support of fast replication, install the PTF on all z/OS V1R5 systems in a sysplex. 

DFSMShsm: z/OS V1R6 and later allow multiple secondary space management (SSM) tasks to run 

concurrently. The PTF allows a z/OS V1R5 system to tolerate this SSM multitasking. 

DFSMShsm: z/OS V1R7 supports fast subsequent migration (FSM) of data sets. The PTFs cause 

DFSMShsm to set the appropriate flags during recall processing so that if the data set is later opened for 

output by either z/OS V1R7 systems or pre-z/OS V1R7 systems, the flags used for reconnection 

determination are set appropriately. 

DFSMShsm: z/OS V1R7 increased the number of data set names supported in a tape table of contents 

(TTOC). If a system that has the coexistence PTF installed finds that the OCDS RECORDSIZE is 6144 

bytes, which indicates that some instances of DFSMShsm in the HSMplex might be using the extended 

TTOC, then tape operations on that level of DFSMShsm are inhibited. 

DFSMSrmm: Allows a pre-z/OS V1R8 system in a client/server environment to participate in an 

RMMplex in which a z/OS V1R8 system has been started. Optionally, you can specify UTC(YES) with 

the EDGUTIL utility on z/OS V1R8 to enable DFSMSrmm common time support. 

DFSMSrmm: Allows a pre-z/OS V1R8 system to participate in an RMMplex in which a z/OS V1R8 

system has been started. In particular, the PTF enables VRSEL processing to recognize the use of the 

special ABEND and OPEN vital record specifications and to correctly handle COUNT(0). It also 

prevents the continued use of the unsupported options STARTNUMBER and LOCATION(BOTH). 

Distributed File Service: Allows pre-z/OS V1R7 systems to tolerate new characters (@#$) allowed in 

z/OS V1R7 and later for zFS file systems and aggregates. 

Distributed File Service: Allows pre-z/OS V1R7 systems to tolerate the file system structure for z/OS 

V1R7 and later zFS file systems. 

HCD: Provides support for HCD users who share IODF data sets between pre-z/OS V1R7 systems and 

z/OS V1R7 or later systems. 

Infoprint Server: In z/OS V1R8, Infoprint Server adds new information to the FSSDATA parameter in 

the OUTPUT descriptor. The PTF allows IP PrintWay (TM) basic mode running on an earlier system in a 

UA25403 

UA22714 

UA16797, UA16952 

UA15870, UA16551, 

UA16955, UA18495 

UA07443 

UA09619 

UA16850, UA16858, 

UA16861, UA16945 

UA16948 

UA25143 

UA22043 

UA14529 

UA20482 

UA90174 (base and 

English), UA90175 

(Japanese) 

UA18196 




sysplex to recognize and ignore the new information in the FSSDATA parameter in the OUTPUT 

descriptor of jobs that are spooled on the z/OS V1R8 system but processed on the earlier system. 

ISPF: Allows pre-z/OS V1R7 systems to intelligently display the number of tracks in a large format 

sequential data set. If the number of tracks is greater than 64 KB, the string ">64K" and a larger 

explanatory message are written to the panel. 

ISPF: Provides an appropriate message when a user attempts to open a large format sequential data set 

from a pre-z/OS V1R7 release. 

JES2: Allows an earlier JES2 to run with z/OS V1R8 JES2 in a multi-access spool (MAS). Install the 

PTFs that are appropriate to the JES2 level that you are using. 

JES2: Fixes a problem on a receiving pre-z/OS V1R7 node that can occur in a rare situation with a large 

scheduler work block text unit (SWBTU). Data sets have a large SWBTU when MAILTO, MAILCC, 

and MAILBCC keywords are used in addition to other keywords on OUTPUT JCL statements. The 

problem is caused by APAR OA09152 (PTF UA16214 on z/OS V1R5-V1R6 JES2 or PTF UA16213 on 

z/OS V1R4 JES). This is a network-specific problem, not a MAS-specific problem. 

JES3: Allows a pre-z/OS V1R8 JES3 to tolerate the removal of various symbols from the IHAWQE 

macro, which was done as part of the console improvements made in z/OS V1R8. 

Language Environment: The /etc/utmpx file contains a user accounting database. In z/OS V1R6, 

the format of the records in the file was extended to support longer remote host names, 64-bit timestamp 

structures, and a version indicator. The coexistence PTF prevents the standard interfaces in pre-V1R6 

releases from accessing /etc/utmpx databases that use the new format, avoiding confusion and 

possible data corruption. Attempts to access a /etc/utmpx database in the new format from an earlier 

release return a null pointer. Applications can use perror() to print the error message. 

Language Environment: Causes a meaningful message to be issued when a new z/OS V1R8 

Language Environment run-time option is encountered by an earlier release. The message states that the 

option is ignored. If the PTF is not installed, the option is still ignored but a less meaningful message, or 

no message at all, is issued. 

NFS: Allows a z/OS V1R7 system to read the new NFS export file format generated by a z/OS V1R8 

system. 

NFS: Allows a pre-z/OS V1R7 NFS SMF report generator to process an SMF file that includes NFS 

V1R7 or later SMF records. Any records containing TCP/IP version 6 IP addresses will be ignored. 

NFS: Allows a pre-z/OS V1R7 NFS server to read a mount handle data set written by z/OS V1R7 or 

later NFS. 

RMF: Ensures the toleration of new z/OS V1R8 functionality for sysplex-wide RMF reporting in 

earlier releases. 

Security Server: In z/OS V1R8, the structure of the RACF database was changed to allow a template 

block to be continued into another block. The PTF allows a z/OS V1R5 system to process templates that 

extend into another block. If you share a RACF database between z/OS V1R8 and z/OS V1R5, you need 

to install the PTF on the z/OS V1R5 system. 

SMP/E: Allows an earlier SMP/E to tolerate enhancements introduced in z/OS V1R6 SMP/E (which is 

equivalent to SMP/E V3R3). 

SMP/E: Provides support for SMP/E users who share SMPCSI data sets between pre-z/OS V1R7 

systems and z/OS V1R7 or later systems. 

UA19929, UA20544 

UA19932, UA19938 

(Swiss German), 

UA19939 (Japanese), 

UA19940 (German), 

UA19941 (uppercase 

English) 

z/OS V1R5-V1R6 JES2: 

UA09501, UA18836, 

UA20902, UA90161, 

UA24983 


UA16217 


UA24989 

UQ85892 

UK12450 

UA25098 

UA16683 

UA19507 

UA26131 

UA24978 

UR54451, UR54454 (if 

Japanese) 

UO00115

Migrating to zOS R8 Part 1 - Messmer The Brain House

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?