MigratingTo_zOSR7_Part1

Migrating to z/OS 1.7: Part 1 of 3 - Get Ready!Thinking about migrating to z/OS 1.7 - our latest release? This session will cover many of the installation requirements for preparing foryour z/OS migration. Included will be:

Content of the z/OS R7 - what new, changing, and removed (and what's being removed in the future)Ordering and deliverablesCoexistence requirements - including the coexistence/migration/fallback/service policyDriving and target system requirements - including both software and hardwareMigrating to z/Architecture - recommended paths

Review “Migrating to z/OS 1.7: Part 2 of 3 - Get Set!” and “Migrating to z/OS 1.7: Part 3 of 3 - GO!” for migration tasks for z/OS R7.Preparing for your z/OS R7 migration can be started today, with this session's important information!

The general availability date for z/OS V1 R7 was September 30, 2005.

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

(c) Copyright IBM Corporation, 2006 March 7, 2006Page 1 of 80

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

Marna WALLEz/OS Build and Install

IBM Systems and Technology Group Poughkeepsie, New York

[email protected]

March 7, 2006 | Seattle, WA


(c) Copyright IBM Corporation, 2006 March 7, 2006 Page 2 of 80

Content of z/OS V1.7Elements and Features Added, Changing, and Withdrawn

z/OS Ordering and DeliverablesProducts Related to z/OS

z/OS Policiesz/OS Coexistence-Migration-Fallback

Positioning for z/OS V1.7:Ensuring System Requirements are Satisfied

Driving and Target System Requirements

Migrating to z/Architecture Hardware First Path and Software First Path

Coexistence System RequirementsMigration Actions You Can Do NOW

Summary

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

© 2003 IBM Corporation

3© 2006 IBM CorporationMigrating to z/OS 1.7: Part 1 of 3 - Get Ready!



4© 2006 IBM Corporation

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

Content is what you just saw on the prior foil Part 2 of 3: Get Set!

Migrations actions for z/OS R7 (with a focus on migrating from R4) from selected elements:

(General z/OS items)BCPC/C++Communications Server

HCD

Part 3 of 3: GO!Migrations actions for z/OS R7 (with a focus on migrating from R4) from selected elements:

DFSMSLanguage EnvironmentJES2 and JES3SMP/E

z/OS UNIX

Also included are highlights of some enhancements you'll see in z/OS R7 for system programmers.


You

need

to a

ttend

all

3 to

ge

t a c

ompl

ete

mig

ratio

n pi

ctur

e!


ScopeFocus Mostly on Migrating to z/OS R7 from z/OS R4

Little, but not much z890 and z990 support covered.


Related Publicationsw 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)

Internet Web Pages

IBM Systems Center Flasheshttp://www.ibm.com/support/techdocs/atsmastr.nsf/Web/FlashesIBM Redbooks web pagehttp://www.redbooks.ibm.com/

z/OS Library web pagehttp://www.ibm.com/servers/eserver/zseries/zos/bkserv/ZSeries Platform Test web pagehttp://www.ibm.com/servers/eserver/zseries/zos/integtst/

End of Service dates for z/OS releaseshttp://www.ibm.com/servers/eserver/zseries/zos/support/zos_eos_dates.html

z/OS Installationhttp://www.ibm.com/servers/eserver/zseries/zos/installation/Consolidated Service Test (CST) home pagehttp://www.ibm.com/servers/eserver/zseries/zos/servicetst/

IBM z/OS home pagehttp://www.ibm.com/servers/eserver/zseries/zosDESCRIPTIONURL



5a© 2006 IBM Corporation

First, an important z/OS web page to know!


A migration webcast will be available here after 3/15, along with a detailed PDF for the webcast!

z/OS Java web pagehttp://www.ibm.com/s390/java

RMF Tools web pagehttp://www.ibm.com/servers/eserver/zseries/zos/rmf/rmfhtmls/rmftools.html

z/OS Technical white papershttp://www.ibm.com/servers/eserver/zseries/library/whitepaperszSeries Software Pricing web pagehttp://www.ibm.com/servers/eserver/zseries/swprice/

zSeries Software Pricing Guide web pagehttp://www.ibm.com/servers/eserver/zseries/library/refguides/sw_pricing.html

Software Dev. Supporting z/OS V1.7 web pagehttp://www.ibm.com/servers/eserver/zseries/zos/software/isv17.html

IBM Order Status homepagehttp://www.ibm.com/support/operations/us/order_delivery/order_delivery.shtml

ShopzSeries home pagehttp://www.ibm.com/software/shopzseries

CustomPac (including SystemPac) web pagehttp://www.can.ibm.com/custompac orhttp://www.ibm.com/ca/custompac

CBPDO web pagehttp://www.ibm.com/servers/eserver/zseries/software/swinfo/pdo.htmEnhanced HOLDDATA web pagehttp://service.boulder.ibm.com/390holddata.html

ESO Overviewhttp://service.boulder.ibm.com/390hdmvsinst.htmlUS Packaged Offerings web pagehttp://www.ibm.com/servers/eserver/zseries/software/swinfo/

IBMLink web pagehttp://www.ibmlink.ibm.com/z/OS Wizardshttp://www.ibm.com/servers/eserver/zseries/zos/wizards/

z/OS Technical Supporthttp://www.ibm.com/servers/eserver/zseries/zos/support/

IBM EducationIBM 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/ .



z/OS Elements and Featuresz/OS consists of base elements and optional features:

The base elements (or simply elements) deliver essential operating system functions. When you order z/OS, youreceive all of the base elements.The optional features (or simply features) are orderable with z/OS and provide additional operating systemfunctions. 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, IBMrecommends that you order them when you order your base elements. You must not wait until the next releasebecomes available. Once a release's base elements are no longer orderable, usually neither are its unpricedfeatures.Priced features are always shipped to you. When IBM packages your order, we enable the priced features thatyou ordered. These features are ready to use after you install z/OS (and customize them as needed). We disablethe priced features that you did not order. Although they are installed on your system, you cannot use them. Lateron, if you decide to use them, you notify IBM and you enable them dynamically (which is known as dynamicenablement). You dynamically enable by updating parmlib member IFAPRDxx and you notify IBM by contactingyour 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, orstand-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.7 (that is, those that changed between z/OS V1.4 withoutany features and z/OS V1.7). Also noted above are those elements changing between z/OS V1.6 and z/OS V1.7. For acomplete list of all the z/OS V1.7 base elements and optional features, see Appendix A in this presentation.





z/OS R7 ElementsBCP

IBM HealthChecker for z/OS*Common Information Model (CIM)*Communications Server

IP and SNACommunications Server Security Level 3Cryptographic Services

ICSF (FMID HCR770A)PKI ServicesSSL

DFSMSdfpDFSMSdssDFSMShsmDFSMSrmm,DFSMStvsDFSORTDistributed File ServiceHCDHCMHLASM (V1R5)HLASM Toolkit (V1R5)

RMFRun-Time Library Extensions*SDSFSecurity Server

RACFSMP/E (V3R4)TSO/EC/C++ Without Debug Tool

XL C/C++z/OS Security Level 3

LDAP Security Level 3 *Network Authentication Service Level 3SSL Level 3

z/OS UNIXApplication ServicesIntegrated Call Level Interface

z/OS V1 R7 Base Elements and Optional Features Changing (from V1R4)

KEY:Black (in bold) are base elementsGreen (also in bold) are optional priced featuresBrown (also in italics) are optional unpriced features with export controls* indicates a new element since z/OS R4This element changed in z/OS R7 (from z/OS R4 w/o features)This element changed in z/OS R7 (from z/OS R6)

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

ICKDSF (R17)Infoprint ServerIntegrated Security Services*

Enterprise Identity MappingLDAP ServerNetwork Authentication Service

ISPFJES2JES3Language EnvironmentLibrary Servermsys for Operations

System Automation (part of V2R3)Network File SystemOSA/SF

Stuff has moved around since z/OS R4!"Why can't I find that old base element in my new release?" you might ask. "Or, I never heard of that feature; where did itcome from?" Well, for reasons such as ordering simplification and technology improvements, elements and features comeand go, components within them move around, and names change. See the table below what's happened since z/OSV1R4.

Summary of element, feature, and component name changes, additiions, deletions, and moves since z/OS V1R4

This base element is new. It is comprised of the new component EnterpriseIdentity Mapping (EIM) and five former components of optional feature

Integrated Security Services

This base element was removed from the system. For migration assistance,see z/OS Migration.

IBM License Manager (ILM)

The is a new component in the new base element Integrated SecurityServices. (The other components in Integrated Security Services previouslyexisted in optional feature Security Server.)

Enterprise Identity Mapping (EIM)

This base element now includes the component PKI Services, which used tobe in optional feature Security Server. The complete list of CryptographicServices components is now ICSF, OCSF, PKI Services, and System SSL.

Cryptographic Services

This optional feature was removed from the system. For migrationassistance, see z/OS Migration.

C/C++ with Debug Tool

This base element was removed from the system. Some remaining functionshave moved to the new base element Run-Time Library Extensions. Formigration assistance, see z/OS Migration.

C/C++ IBM Open Class Library The name of this base element changed to Library Server. BookManager BookServer Change Name (new ones are highlighted)




7© 20056IBM CorporationMigrating to z/OS 1.7: Part 1 of 3 - Get Ready!

Where are they now since z/OS V1.4?

Cryptographic Services:PKI Services (formerly from Security Server and was licensed with the base)ICSFOCSFSystem SSL

Integrated Security ServicesEnterprise Identity Mapping (introduced as a PTF on z/OS R4)DCE Security Server (formerly from Security Server and was licensed with the base)Firewall Technologies (formerly from Security Server and was licensed with the base)LDAP Server (formerly from Security Server and was licensed with the base)Network Authentication Service (formerly from Security Server and was licensed with the base)OCEP (formerly from Security Server and was licensed with the base)

Run-Time Library ExtensionsCommon Debug ArchitectureUNIX System Lab I/O Stream Library and Complex Math Library (formerly part of C/C++ IBM Open Class Library)IBM Open Class DLLs (formerly part of C/C++ IBM Open Class Library)

Security Server:RACF

z/OS Security Level 3LDAP Server Security Level 3Network Authentication Service Level 3 (formerly its own feature Security Server Network Authentication Service Level 3)OCSF Security Level 3 (formerly its own feature)System SSL Security Level 3 (formerly its own feature)

This unpriced optional feature is new. It is a repackaging comprised of theformerly separate optional features Security Server Network AuthenticationService Level 3 (but now without "Security Server" in its name), OCSFSecurity Level 3, and System SSL Security Level 3, and the new componentin z/OS R6 LDAP Security Level 3.

z/OS Security Level 3

This former optional feature is now a component of new optional featurez/OS Security Level 3.

System SSL Security Level 3

This former optional feature is now a component of new optional featurez/OS Security Level 3. Also, it has a new name: Network AuthenticationService Level 3 ("Security Server" was removed from the name).

Security Server Network AuthenticationService Level 3

This optional feature had seven components but now has only one, RACF.The PKI Services component moved to the Cryptographic Services baseelement. The other five components moved to new base element IntegratedSecurity Services. They are DCE Security Server, Firewall Technologies,LDAP Server, Network Authentication Service, and OCEP.

Security Server

This base element is new. Some functions are picked up from the removedbase element C/C++ IBM Open Class Library, and other functions are new.

Run-Time Library Extensions

This former optional feature is now a component of new optional featurez/OS Security Level 3.

OCSF Security Level 3

This former optional feature is now a component of new optional featurez/OS Security Level 3. In addition, its name has been trimmed; "SecurityServer" is removed from the beginning of the name.

Network Authentication Service Level 3

This is the new name of base element BookManager BookServer. Library Server

Security Server: DCE Security Server, Firewall Technologies, LDAP Server,Network Authentication Service, and OCEP.



Withdrawn in z/OS V1.5 (last delivered in z/OS V1.4)This section lists items that were withdrawn in z/OS V1.5. You should take this into account as you plan your migration toz/OS R7. The removal of these functions may have migration actions which you can perform now, in preparation for z/OSR7.

Development with the C/C++ IBM Open Class Library is not supported. This includes removal of the ApplicationSupport Class and Collection Class libraries. Run-time support is provided for existing applications in z/OS R7, butthis support will be removed in a future release. For new application development that needs C++ library support, usethe C++ Standard Library, shipped with z/OS base element Language Environment, instead of the C/C++ IBM OpenClass Library. From base element DFSMSdfp, IBM has removed Object Access Method (OAM) support for Filenet 9246 opticallibraries, 9247 optical drives, and 12-inch optical media If you need to store objects on optical devices, you canreplace these Filenet devices and media with IBM 3995 optical devices and media. If you do not require opticaldevices, you can transition the data to any z/OS-supported tape media or to DB2 tables on DASD. Base element IBM License Manager is not delivered since z/OS V1.5. On November 26, 2002, IBM announced that ithas decided not to deliver the IBM License Manager tool for zSeries, as previously described. IBM's long-termobjectives remain the same:

to deliver a heterogeneous software license management tool to support open standards, where applicable, such as X-Open Software License Management (XSLM) standard to offer a mechanism to help customers, Independent Software Vendors and IBM understand software use, as itrelates to Ts & Cs

This announcement does not alter the Ts & Cs of zSeries Workload License Charges (WLC). IBM will continue todeliver sub-capacity software pricing benefits using the Sub-Capacity Reporting Tool (SCRT), until a strategic solutionis available. IBM will continue to enhance SCRT over time. If you have questions about a specific vendors' support ofSCRT or other sub-capacity pricing implementations, please contact that vendor directly. Tivoli software, IBM'scenter of competency for managing technology, will take a leadership role in defining and delivering thecross-platform roadmap for future license management technologies. The first of these license managementtechnologies is IBM Tivoli License Manager. Tivoli is currently developing follow-on plans for the zSeries platform. Ifyou had performed any customization for ILM, that customization can be removed.





Elements and Functions Withdrawn from z/OS R5

Application Development support in the C/C++ IBM Open Class Library

Base Element - use the C++ Standard Library (shipped with Language Environment) instead

as of z/OS R5

C/C++ with Debug Tool

Optional Feature - use z/OS R5 C/C++ without Debug Tool feature and also the independent standalone program product - IBM Debug Tool for z/OS V6.1 (5655-P14).

as of z/OS R5

OAM support for Filenet 9246, optical libraries, 9247 optical drives, and 12" optical media (from DFSMSdfp)

Base Element - if optical is required, replace Filenet devices and media with IBM 3995 optical devices and media. If optical is not required, use tape media or DB2 tables on disk.

as of z/OS R5

IBM License Manager

Base Element - use the Sub-Capacity Reporting Tool (SCRT) for subcapacity software pricing

as of z/OS R5

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 toz/OS R7. The removal of these functions may have migration actions which you can perform now, in preparation for z/OSR7.

The C/C++ ISPF panels, which include panels for C/C++ foreground compiles, C/C++ background compiles, and helppanels 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. Thisfunction is used primarily in run-time migration. Given the stability and the upward compatibility being provided by theLanguage 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. Thisutility is used to package and redistribute IBM-supplied DLLs with applications. Since OS/390 V1R3, the C/C++ DLLshave been licensed with the OS/390 and z/OS base operating system. Therefore, the DLL Rename Utility is no longerrequired. z/OS Communications Server support for the SMIv1 version of the SNMP IBM MVS TCP/IP Enterprise-specific MIBmodule is eliminated in z/OS V1.6. Support will continue for the SMIv2 version of this MIB module. For customers whowant to continue using SMIv1, publically available tools can be used to convert an SMIv2 MIB module to an SMIv1MIB module.Effective with z/OS V1.6, IBM has removed the base element, Distributed Computing Environment (DCE) ApplicationSupport, from z/OS. DCE Application Support facilitated the interaction between DCE clients and CICS or IMSregions. With the continued evolution of technology and accompanying changes in the marketplace, there is no needfor this support. If similar function is required, IBM recommends that customers use IBM WebSphere. The DCE BaseServices element, which provides services for developing and running client/server applications, is planned tocontinue 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 ToolkitExecutive provided a set of tools for developing client components of distributed transactional applications. Over time,






C/C++ ISPF panels (from C/C++)

Priced Feature - invoke the C/C++ compiler via UNIX, JCL, or TSO/E.

as of z/OS R6

Run-time Library Services (RTLS) (from Lang Env)

Base Element - no longer required due to stability and upward compatibliity

as of z/OS R6

Dynamic Link Library (DLL) Rename Utility (from Lang Env)

Base Element - no longer needed due to C/C++ DLLs being licensed with the z/OS base

as of z/OS R6

SMIv1 version of the IBM MVS Enterprise-specific MIB module (fromCommunications Server)

Base Element - if you want to continue to use SMIv1, publicly available available tools can convert SMIv2 to SMIv1

as of z/OS R6

DCE Application Support Base Element - no replacement necessary. Evaluate WebSphere for similar function

as of z/OS R6

Encina Toolkit Executive Base Element - no replacement offered. Marketplace has moved to other technologies

as of z/OS R6

Text Search Base Element - available via web deliverable if still necessary for certain usage

as of z/OS R6

the marketplace has moved to other technologies. This element, an enabler for DCE Application Support, is anotherobsolete 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 madeavailable for Web download as z/OS and z/OS.e Text Search under a restricted license. This is a change to thestatement of direction made in Software Announcement 203-266 (RFA38767), dated October 7, 2003, which statedthat with z/OS V1.6, the Text Search base element would be removed and no replacement would be provided. TheText Search element has been removed from the z/OS product. However, the Text Search function is still requiredand licensed for use only for DB2(R) UDB Text Extender feature of DB2 Universal Database for z/OS, ProgramNumber 5625-DB2, as a Web deliverable named z/OS and z/OS.e Text Search. Before you use the DB2 UDB TextExtender 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 nolonger available as a z/OS Web deliverable. Instead, the Text Search function is provided by Web download from theDB2 UDB Text Extender Web support site: http://www.ibm.com/software/data/db2/extenders/text/te390/



Withdrawn in z/OS V1.7 (last delivered in z/OS V1.6)This section lists items that were withdrawn in z/OS V1.7. You should take this into account as you plan your migration toz/OS R7. The removal of these functions may have migration actions which you can perform now, in preparation for z/OSR7.

From base element JES2, IBM removes support for JES2 compatibility mode (R4). As of z/OS R7. JES2 will nolonger support compatibility with pre-z/OS V1.2 systems. The $ACTIVATE command, which converts the JES2checkpoint from z2 mode to R4 mode (compatibility mode), will be removed. Before installing z/OS R7, you must doone of the following:

Use the $ACTIVATE command to convert the JES2 checkpoint to z2 modeOffload 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. TheJOBCAT and STEPCAT facilities have been in existence for many years, predating the introduction of ICF (integratedcatalog facility) catalogs. JOBCAT and STEPCAT were designed to address some of the functional shortcomings ofVSAM catalogs, such as:

VSAM volume ownership, that is, all data sets on a volume having to be in the same VSAM catalog. Multiplecatalogs 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 datafor 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 aliassupport) directly addressed those problems. In addition, processes were developed for system build to use systemspecific aliases instead of JOBCAT or STEPCAT. CBIPO introduced these processes and they are used today byofferings 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. NeitherSMS-managed data sets nor UCBs above the 16 megabyte line may be used with JOBCAT or STEPCAT. ICF



© 2003 IBM CorporationfInfInInfo




JES2 "compatibility" R4 mode (from JES2)

Base Element - to avoid a cold start, you must $ACTIVATE to convert the JES2 checkpoint to z2 mode before installing z/OS R7

as of z/OS R7

JOBCAT and STEPCAT facilities (from DFSMSdfp)

Base Element - any remaining JCL that use JOBCAT or STEPCAT must change

as of z/OS R7

Support for ISAM data sets (from DFSMS)

Base Element - ISAM Compatibility Interface will still be provided (which allows you to run an ISAM program against a VSAM KSDS data set)

as of z/OS R7

OS/390 R10 level of the C/C++ compilers (from C/C++)

Priced Feature - move to the ISO 1998 Standard level of the compilers (introduced in z/OS R2)

as of z/OS R7

ECMB=NO circumvention in IEAOPTxx (from BCP)

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

as of z/OS R7

One-byte console IDs on macro interfaces and operator commands (and TRACK, ... commands) (from BCP)

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

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

as of z/OS R7

catalogs contain sufficient functional capabilities that all functions that previously could only be performed withJOBCAT or STEPCAT can now be done without them. Furthermore, the use of JOBCAT and STEPCAT can actually cause significant problems. Data sets are generallynot cataloged according to the normal predictable search order when JOBCAT or STEPCAT is used. This impactsthe ability to do comprehensive installation storage management and can increase staff requirements. Forexample, interval migration and recall using DFSMShsm is effectively unusable when the data sets cannot befound using the standard catalog search order. The use of JOBCAT and STEPCAT can also result in noticeableincreases 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 hasprovided the ISAM Compatibility Interface (ISAM CI) which allows users to run an ISAM program against a VSAMKSDS data set. Details on using this interface and procedures for converting ISAM data sets to VSAM data sets canbe found in Appendix E of Using Data Sets. This compatibility interface program continues to be provided as part ofDFSMS 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++ compilersfrom z/OS R7. The OS/390 R10 C/C++ compilers were shipped as an aid to migration to the C/C++ compilers thatwere introduced in z/OS V1R2. The z/OS V1R2 level of the C++ compiler supports the ISO 1998 Standard level ofC++. For information about migrating from the older to the newer level of the compilers, see z/OS C/C++ Compilerand Run-Time Migration Guide.Previously, the CMB= parameter specified the I/O device classes for which measurement data was to be collected, inaddition to the DASD and tape device classes. It also allowed you to specify the number of channel measurementblock (CMB) slots to reserve for adding more devices with an ACTIVATE. As of the z990 Exploitation feature on z/OSR4, the system ignores the CMB and uses instead the measurement data in the extended channel measurementblock (ECMB). As a migration action since then, you must convert user-written programs that make use of the CMBto make use of the ECMB, and contact ISVs to obtain updates to ISV programs that use the CMB. The type ofprograms especially likely to use the CMB are monitor programs. If ISV support is not available, you could havespecified ECMB=NO in parmlib member IEAOPTxx as a circumvention until the ISV support is available. See APAROA06164 for additional details. The ECMB=NO circumvention has been removed in z/OS R7, so have plans in placeto 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 allowedto specify one-byte console IDs on macros (such as WTO/WTOR), or on such operator commands as D C,CN= or DPFK,CN= . You should use console names instead. A service called the Console ID Tracking Facility is available tohelp you identify one-byte ID usage. The use of console names is already a best practice on OS/390 and z/OS. Forinformation 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, CONTROLD,H, and MSGRT TR=A are removed in z/OS R7. The z/OS Optional Source media feature is not offered in z/OS R7. The last release offering these materials wasz/OS R6. These features contain macros and source code for some programs in the z/OS BCP, BDT base, BDT SNANJE, 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 OMPROUTEas your dynamic routing daemon.



Planned for removal in the release after z/OS R7This section lists items that IBM has announced it intends to remove after z/OS R7. You are encouraged to considerthese removals when making your plans for system upgrades. These statements represent IBM's current intentions. IBMdevelopment plans are subject to change or withdrawal without further notice.

z/OS V1.7 is planned to be the last release to allow mounting zFS file systems contained in multi-file systemaggregates that are to be shared across systems in a sysplex. IBM has previously recommended that these multi-filesystem aggregates not be shared in a sysplex environment. Once this support has been removed, attempts to mountzFS 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 besupported in all environments.z/OS V1.7 is planned to be the last release to include the Firewall Technologies component of the Integrated SecurityServices element. Many Firewall Technologies functions have been stabilized for some time and can be replacedusing comparable or better functions provided by or planned for Communications Server, notably, IPSecurity. Inaddition, a functionally rich downloadable tool is planned to replace the IPSecurity and IP Filtering configuration GUIsupport. The following functions will be removed without replacement:

FTP Proxy servicesSocks V4 servicesNetwork Address Translation (NAT)RealAudio (TM) support

z/OS V1.7 is planned to be 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:ASSORTEDPARMSENDASSORTEDPARMSKEEPALIVEOPTIONS,ENDKEEPALIVEOPTIONS




11

© 2006 IBM CorporationMigrating to z/OS 1.7: Part 1 of 3 - Get Ready!

Functions Planned to be Withdrawn after R7...zFS multi-file system aggregate shared across a sysplex (from Distributed File Service)

Base Element - zFS compatibility mode aggregates (which have a single file system per data set) will continue to be supported in all environments.

Planned for release after R7

Firewall Technologies (from Integrated Security Services)

Base Element - Many Firewall Technologies functions have been been stabilized and can be replaced w/ Comm Server functions. Some functions won't have replacements.


Some Communications Server functions

Base Element - TCP/IP Configuration profile block definitions, PAGTSNMP subagent, EE TGs definition by specifying multiple SAP addrs, and AnyNet


Any remaining one-byte console ID support (from BCP)

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


Certain plug-ins for msys for Setup: TCP/IP Services, z/OS UNIX System Services, Language Environment, Parallel Sysplex, ISPF, and RMF

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.


Equivalent capability is provided for the ASSORTEDPARMS statements by the GLOBALCONFIG,IPCONFIG, TCPCONFIG, and UDPCONFIG statements. Equivalent capability is provided for theKEEPALIVEOPTIONS statements by INTERVAL and SENDGARBAGE on the TCPCONFIG statement. Forinformation on TCP profile and configuration statements, refer to z/OS Communications Server IPConfiguration 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 recommendsthat 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/OSV1.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 the release following z/OS V1.7, the remaining support for one-byte console IDs will be removed from controlblocks CIB, CSCB, ORE, WQE, XSA. This completes the removal of one-byte console IDs in z/OS. Instead of usingone-byte console IDs, console names should be used.Support for the following plug-ins for msys for setup will be withdrawn in the release following z/OS V1.7: TCP/IPServices, z/OS UNIX System Services, Language Environment, Parallel Sysplex, ISPF, and RMF. When this supportis withdrawn, you will not be able to use msys for Setup for function enablement, setup, or configuration of theseareas of z/OS. The DB2 V8 msys for Setup plug-in is unaffected and remains available for setup and configuration ofDB2. The TCP/IP plug-in will continue to be available for download via the Web and will no longer require msys forSetup. IBM intends to continue to deliver improvements to help with z/OS setup and configuration in the future.z/OS V1.7 is planned to be the last release to support the z/OS msys for Operations element. It is IBM's intent toremove the z/OS msys for Operations element from the release following z/OS V1.7. IBM plans to transition many ofthe current msys for Operations functions to a new user interface and infrastructure in a future release of z/OS.



Planned for removal in the release following z/OS R8This section lists items that IBM has announced it intends to remove in release following z/OS R8. You are encouraged toconsider these removals when making your plans for system upgrades. These statements represent IBM's currentintentions. 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 ConfigurationManager (HCM) and Hardware Configuration Dialog (HCD) elements via Advanced Program to ProgramCommunication (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 bedone exclusively via TCP/IP.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. Applicationsthat are dependent on the IOC Library will not run starting with the z/OS release available in 2007. IBM has previouslyrecommended that customers with application code that uses the IOC Library migrate to 2 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 forcustomers migrating their code from the IBM Open Class Library to the Standard C++ Library. You can get this guideby visiting http://www-1.ibm.com/support/docview.wss?rs=32&org=SW&doc=7001423&loc=en-us

For more information, and for all previously announced statements of direction affecting z/OS V1.7 and futurereleases, visit http://www.ibm.com/servers/eserver/zseries/zos/zos_sods.html




11b

© 2006 IBM CorporationMigrating to z/OS 1.7: Part 1 of 3 - Get Ready!

Functions Planned to be Withdrawn in the release after R8...

Host communication between HCM and HCD with APPC (from HCM)

Priced Feature - Only TCP/IP for host communication between HCM and HCD will be allowed. (Currently both TCP/IP and APPC are supported.)

Planned for release in 2007

Run-time support for C/C++ IBM Open Class (IOC) Dynamic Link Libraries (DLLs) (from C/C++ without Debug)

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 removal in a future z/OS releaseThis section lists items that IBM has announced it intends to remove in a future z/OS release. You are encouraged toconsider these removals when making your plans for system upgrades. These statements represent IBM's currentintentions. 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 shouldimplement 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 alternativesolutions, such as the Sysplex Distributor function.The English and Japanese ISPF panels will be removed from DFSORT in a future release. This limited functioninteractive 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 futurerelease. No supported release of z/OS allows you to define new VSAM data sets with these attributes. Using them forexisting data sets can waste DASD space and can often degrade performance. When this support is withdrawn, youwill not be able to process data sets with these attributes. It is best to plan for this removal now, with the aid of a toolthat 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/toolsdirectory 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 attributeswill no longer be able to be opened, it would be prudent to use this tool to identify the data sets in your installation andbegin converting them to versions that do NOT contain these attributes. IMBED and REPLICATE were intended asperformance improvements which have been obsoleted by newer cached DASD devices. Striped data sets provide






Functions Planned to be Withdrawn in the future...

BIND DNS 4.9.3 (from Communications Server)

Base Element - implement BIND 9.2.0 as a replacement (availabile since z/OS R4)

Future

English and Japanese panels from DFSORT

Priced Feature - no replacement offered Future

Support for VSAM data sets with IMBED, REPLICATE, or KEYRANGE attributes (from DFSMS)

Base Element - plan to redefine any affected VSAM data sets. Use tool to assist in identifying affected VSAM data sets.

Future

zFS multi-file system aggregates (from Distributed File Service)

Base Element - zFS compatibility mode aggregates will still be supported

Future

In-stack version of TN3270 Server (from Communications Server)

Base Element - use standalone TN3270 Server instead (introduced in z/OS R6)

Future

RMF LDAP replacement (from RMF)

Priced Feature - RMF LDAP interface is planned to be replaced with a CIM Monitoring Interface that is part of z/OS R7

Future

much better performance than KEYRANGE, and should be viewed as a candidate for any existing KEYRANGE datasets. In a future release, IBM plans to withdraw support for zFS multi-file system aggregates. When this support iswithdrawn, only zFS compatibility mode aggregates will be supported. (A zFS compatibility mode aggregate has asingle file system per data set.)z/OS V1R6 Communications Server and subsequent releases include a standalone TN3270 Server. This standaloneTN3270 server is expected to provide increased flexibility, improved reliability, and simplified problem diagnosis ascompared to the in-stack version of the TN3270 Server. In a future release of z/OS Communications Server, supportfor the in-stack version of the TN3270 Server is planned to be discontinued. In preparation for that change, customersshould consider implementing the standalone TN3270 Server. For more information, refer to http://www.ibm.com/software/network/commserver/zos/IBM plans to replace the RMF LDAP backend in a future release of the operating system. The RMF LDAP interfacecurrently allows access to RMF performance data from application programs. This functionality will be replaced with aCommon Information Model (CIM) Monitoring interface that is now part of z/OS V1.7.

For more information, and for all previously announced statements of direction affecting z/OS V1.7 and futurereleases, visit http://www.ibm.com/servers/eserver/zseries/zos/zos_sods.html



z/OS Ordering and Deliverable Key DatesKey Dates for z/OS R7:

July 26, 2005: z/OS V1.7 CFSW configurator support for stand-alone path (5694-A01) and price proposal support.September 16, 2005: General availability of Cryptographic Support for z/OS V1R6/R7 and z/OS.e V1R6/R7 Webdeliverable. This Web deliverable supports z/OS and z/OS.e V1.6 and V1.7.September 16, 2005: First date for ordering z/OS V1.7 ServerPac, SystemPac, CBPDO using CFSW configurationsupport, or ShopzSeries, the Internet ordering tool. Note that most z/OS media (executable code) is shipped onlythrough Customized Offerings (ServerPac, SystemPac, and CBPDO). September 16, 2005: Withdrawal of the 4mm media feature code support and the z/OS V1.6 Optional Source Codefeatures.September 30, 2005: z/OS V1.7 general availability via ServerPac, CBPDO and SystemPac. September 30, 2005: General availability of IBM Health Checker for V1R4/R5/R6 of z/OS and z/OS.e Webdeliverable. This Web deliverable supports z/OS and z/OS.e V1.4, V1.5, and V1.6. September 30, 2005: Removal of z/OS and z/OS.e Text Search Web deliverable. For more information, refer to theDB2 UDB Text Extender Web support site: http://www.ibm.com/software/data/db2/extenders/text/te390/support.htmlDecember 2006: Last date for ordering z/OS V1R4 z990 Exploitation Support feature and z/OS V1R4 ConsolesEnhancements feature.

Web deliverablesSometimes enhancements are provided as Web deliverables. For example, some of the z/OS enhancements in supportof the z990 server 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:

w A readme file, which contains a sample job to uncompress the second file, transform it into a format that SMP/Ecan process, and invoke SMP/E to RECEIVE the file. This file must be downloaded as text.



13© 2003 IBM CorporationMigrating to z/OS 1.7: Part 1 of 3 - Get Ready! © 2006 IBM Corporation

z/OS Ordering and Deliverables 9/069/04 9/05

z/OS V1R6

z/OS R8 planned

Cryptographic Support for z/OS V1R6/R7 Web deliverable (FMID HCR7730), available starting 9/16/05.

z/OS 1.4 Consoles Enhancements Feature

ordering mandatory with z/OS V1R4 starting 2 /24/04,ordering mandatory with z/OS V1R4 starting 2 /24/04,available via CBPDO until December 2006available via CBPDO until December 2006z990 Exploitation

available via CBPDO until December 2006available via CBPDO until December 2006

z/OS V1R7 z/OS V1R7 orderable starting 9/16/05 GA is 9/30/05.

9/07

IBM Health Checker for V1R4/R5/R6 of z/OS and z/OS.e Web deliverable available starting 9/30/05

z/OS V1R6 orderable starting 9/10/04, ending 10/24/05

ICSF

HC

z/OS R.. planned

w A pax.z file, which contains an archive (compressed copy) of the FMIDs to be installed. This file needs to bedownloaded 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. In order to use GIMUNZIP, the driving system needs to have SMP/E V3R1(also shipped in z/OS V1R2) or later, or OS/390 V2R7 through V2R10 and z/OS V1R1 SMP/E with PTF UR52471(APAR IR43312).

4. Obtain and install service for the target system. Service is not included in Web deliverables. You can obtain servicefor Web deliverables through your regular preventive service deliverables that you use for z/OS.

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



z/OS R4, R5, R6, and R7 Support for z890/z990 Servers and CryptographyThe z890 and z990 servers represent the second generation of zSeries servers. The support for the z890/z990 andCyrptography has been delivered via features, web deliverables, and release incorporations for z/OS R4, R5, R6, and R7.The features can be installed along with z/OS V1R4 or later, using ServerPac, SystemPac, or CBPDO. The Webdeliverables are available from http://www.ibm.com/eserver/zseries/zos/downloads/. You install them using SMP/E in amanner similar to installing with CBPDO.

New release of products March 27, 2004 z/OS V1R5

Unpriced feature of z/OS V1R4

Ordering of unpriced feature withz/OS V1R4 mandatory

October 31, 2003

February 24, 2004

z/OS V1R4 z990 Exploitation Support

Web deliverableSeptember 19, 2003 for z/OS V1R4, and z/OS V1R2; October 17, 2003 for z/OS V1R3; andNovember 21, 2003 for OS/390 V2R10

z990 Cryptographic Support (for z/OSV1R4, z/OS V1R3, z/OS V1R2, andOS/390 V2R10) (FMID HCR770A)

Web delverableJune 13, 2003 z990 Cryptographic CP Assist Support forz/OS V1R3 (FMID HCR7708)

Web deliverableJune 13, 2003 z990 Compatibility for Selected Releases(for z/OS V1R3, z/OS V1R2, and OS/390V2R10)

Unpriced feature of z/OS V1R4 June 13, 2003 z/OS V1R4 z990 Compatibility Support New release of products September 27, 2002 z/OS V1R4 Delivery method General availability Deliverable

z/OS Releases and z890/z990 and Crypto Support Deliveries




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

z990 and Crypto Support for z/OS R4, R5, R6, and R7

z/OS R6 and z/OS R7

z990 Exploitation Support is incorporated

in R6: z990 Cryptographic Support (FMID HCR770A) is incorporated. In R7: z990 Cryptographic Support (FMID HCR7720) is incorporated.However, Cryptographic Support (FMID HCR7730) is available for z/OS R6/R7 as a web deliverable on 9/16/05.

z/OS R5 z990 Exploitation Support is incorporated.

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 R4 z990 Exploitation Support is incorporated into z/OS R4 after Feb 24, 2004.z990 Exploitation Support remains available separately in CBPDO until December 2006.

z990 Cryptographic CP Assist Support (FMID HCR7708) is incorporated via z990 Exploitation Support. z990 Cryptographic Support (FMID HCR770A) was a web deliverable for z/OS R4. However,z990 and z890 Enhancements to Cryptographic Support (FMID HCR770B) is available for z/OS R4 as a web deliverable, and replaces z990 Cryptographic Support.

Release Support Provided

Web deliverableSeptember 16, 2005Cryptographic Support for z/OS V1R6/R7and z/OS.e V1R6/R7 (FMID HCR7730)

New release of productsSeptember 30, 2005z/OS V1R7(z990 Exploitation Supportincoporated)

Web deliverableSeptember 16, 2005Cryptographic Support for z/OS V1R6/R7and z/OS.e V1R6/R7 (FMID HCR7730)

Web deliverableDecember 17, 2004ICSF 64-bit Virtual Support (for z/OSV1R6) (FMID HCR7720)

Web deliverableSeptember 24, 2004z990 and z890 Enhancements toCryptographic Support (for z/OS V1R6)(FMID HCR770B)

New release of productsSeptember 24, 2004z/OS V1R6(z990 Exploitation Supportincoporated)

Web deliverableMay 28, 2004z990 and z890 Enhancements toCryptographic Support (for z/OS V1R5,z/OS V1R4, z/OS V1R3, z/OS V1R2, andOS/390 V2R10) (FMID HCR770B)

Web deliverableMarch 27, 2004 z990 Cryptographic Support (for z/OSV1R5) (FMID HCR770A)

(z990 Exploitation Supportincorporated)

Support for z9-109 Servers The IBM System z9 109 (z9-109) server is the follow-on to the zSeries servers. The z9-109 server provides moreprocessing power, memory, and I/O capacity than the zSeries servers (z990, z890, z900, and z800). Migrating to z/OSV1R7 on a z9-109 server will allow you to take advantage of these improvements. To read about the software actionsnecessary to migrate your z/OS system from your current server to a z9-109 server, see z/OS Migration to the IBM Systemz9. You can find this document by going to the Migration and Installation section of the z/OS Web site: http://www.ibm.com/servers/eserver/zseries/zos/installation/.



z/OS V1R7 OrderingThe program number for z/OS Version 1 Release 7 is 5694-A01. When ordering this program number, remember toorder all the optional features that you were licensed for in previous releases of z/OS.

In z/OS V1R7 there are only two export controlled unpriced features: z/OS Security Level 3, and CommunicationsServer Security Level 3. z/OS Security Level 3 contains the sub-elements: LDAP Security Level 3, NetworkAuthentication 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, SystemPac, and CBPDO, the previous releaseis orderable for only a month. Due to this short overlap, it is very important that you order the z/OS release you need formigration and coexistence while it’s still available for ordering. z/OS R4 users should plan to order z/OS R7 before theavailability of z/OS R8! Ordering and Installing z/OS R7 Electronically!In many countries you may order z/OS electronically through ShopzSeries. ShopzSeries provides customers aself-service capability for planning and ordering S/390 software (and service!) upgrades over the Web. It is the strategicworldwide self-service ordering system for zSeries software. You can order products through ShopzSeries and have themdelivered electronically in some countries.

In most countries, ShopzSeries provides electronic ordering and electronic delivery support for z/OS Service. You canaccess 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 toyou! This electronic ability was made generally available on January 10, 2005.





z/OS V1R7 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:

z/OS Security Level 3Communications Server Security Level 3

Recommended to place your z/OS R7 order before z/OS R8's availability!September 2006 is the planned GA for z/OS R8. Ordering availability typically starts 2 weeks prior to GA.

There is planned to be only a one-month overlap between R7 and R8 ordering.

Web deliverable Cryptographic Support for z/OS V1R6/R7 (HCR7730) NOT in R7HCR7720 (ICSF z990 Cryptographic Support) incorporated into R7.

Tivoli Netview and System Automation users take note!z/OS msys for Operations contain parts of these products, ...see next foil

Order z/OS V1R7 electronically via ShopzSeries!When you do this, you can choose to have an electronic ServerPac!

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/Estand-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 ofSMP/E without having to upgrade their entire operating system. The advantage is that products other than z/OS canexploit the packaging and installation enhancements in SMP/E without having to install the prerequisites for a new level ofthe operating system.

In addition, since SMP/E plays a key role in Internet delivery of software, it allows IBM to exploit the Internetdelivery and installation technologies in SMP/E sooner without having to wait for customers to migrate to newlevels of the operating system. SMP/E V3.4 is available at no additional charge to customers. It is intended forcustomers who have a license for z/OS V1 (5694-A01). SMP/E V3.4 is incorporated into z/OS R7.

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 servicedelivery 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 isdesigned to order and retrieve z/OS platform service from a dedicated IBM server via the Internet in one simple stepright from z/OS. With SMP/E V3.4 you are now able to order and retrieve service on demand to obtain exactly whatyou need when you need it, or you can automate the service delivery process. By scheduling an SMP/E job to runonce a week, or even every night, you can order and download the latest HOLDDATA and PTFs and have theseservice updates available exactly when you want them. You can request corrective service, three forms of preventiveservice, 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 areapplicable 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).





Products Related to z/OS R7IBM SMP/E for z/OS and OS/390, V3.4 (5655-G44)

SMP/E is non-exclusive! incorporated into R7Availability was September 30, 2005; no charge to z/OS licensed users

IBM Debug Tool for z/OS V6 R1 (5655-P14) and V5 R1 (5655-M18) Debug Tool no longer incorporated, as of z/OS R5

z/OS R7 msys for Operations contains parts of:Tivoli Netview for OS/390 V1 R4 (5697-B82) Tivoli System Automation for OS/390 V2 R3 (5698-A14)(Remember, msys for Ops intended to be removed after z/OS R7)

Tivoli NetView for OS/390 V5 R1 (5697-ENV) Can be ordered with, and is compatible with z/OS R7 msys for Ops

Tivoli System Automation for OS/390 V2 R3 (5698-A14) Can be ordered with, and is compatible with z/OS R7 msys for Ops(When ordering SA V3 R1, will have a requisite on Netview V1 R4 or V5 R1)

IBM Ported Tools for z/OS (5655-M23) - provides OpenSSH function!XML Toolkit for z/OS V1 R8 (5655-J51) - GA was June 17, 2005

Contains XML V1R7 and V1R6 levels, as wellIBM 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)

Recommended service includes all PTFs with a Recommended Service Update SOURCEID (RSUyynn) andall 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 theentire z/OS platform (see http://service.software.ibm.com/holdata/390holddata.html for further information onEnhanced HOLDDATA).

Your PTF service order is customized to your SMP/E environment using a software inventory file that identifies yourinstalled FMIDs and the PTFs already present in your environment. This means you receive only the PTFs yourequest 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 aspossible that can be downloaded and installed quickly. The SMP/E RECEIVE command has been extended to support this Internet Service Retrieval capability. TheRECEIVE command will use the HTTP 1.0 protocol with SSL to communicate over the Internet with the dedicatedIBM server. The server accepts the PTF or HOLDDATA request from SMP/E and responds with the informationnecessary to download the files of PTFs and HOLDDATA. SMP/E then uses the FTP protocol to download the filesfrom 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-1hash values. These hash values are calculated for files within a GIMZIP package to verify the integrity of the datawithin the package.SMP/E has been enhanced to use an alternate method to calculate SHA-1 hash values if ICSF is not available foruse. Although ICSF is the preferred method, SMP/E will no longer require it for use by the GIMZIP and GIMUNZIPservice routines, nor for the RECEIVE FROMNETWORK or RECEIVE FROMNTS commands. If SMP/E detects ICSFis not available, then SMP/E will automatically use an SMP/E Java application class to calculate SHA-1 hash valuesas an alternative.Improved Load Module Build: The load module build phase of the APPLY, RESTORE and LINK LMODScommands is being enhanced to be more tolerant of allocation errors for the distribution libraries. This accommodatesdistribution libraries which may be off-line. In this case, SMP/E continues its search for a useable copy of the moduleinstead of immediately failing because of the error allocating the distribution library.

SMP/E V3.4 was available on September 30, 2005. The default level shipped with z/OS R7 is SMP/E V3.4. ServerPacorders are built using either the default level of SMP/E or the lowest supported level of SMP/E that is required for theproducts in your order. The higher of these two SMP/E levels is used. For example, z/OS orders are built with the level ofz/OS SMP/E provided in that release of z/OS. Subsystem orders are built with SMP/E V3.1, unless a product in your orderhas a dependency on a higher level of SMP/E. Your subsystem order would then be built with the minimum level ofSMP/E that satisfies the requirement. The level of SMP/E used to build your order is documented in ServerPac InstallingYour Order. If it may be a while until you migrate to z/OS R7, you may want to consider ordering this separate product early (in aCBPDO) 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 canbe found at: http://www.ibm.com/software/os/ then Downloads (with parallel paths for both OS/390 and z/OS). SMP/E V3R3 has been available via the download zone since October 1, 2004.

IBM Debug Tool for z/OS Version 6 Release 1 (5655-P14) and V5 Release 1 (5655-M18) The latest available Debug Tool is the IBM Debug Tool for z/OS V6.1, also available is the V5.1 level. IBM Debug Tool forz/OS is IBM's interactive source-level debugging tool for compiled applications. It is a program testing and analysis aidthat helps you examine, monitor, and control the execution of application programs written in C, C++, COBOL, or PL/I ona z/OS or OS/390 system. By using the disassembly view, Debug Tool also provides support for programs compiled withthe 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 theenvironment 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 commandsthat are available in the Monitor window will generate the corresponding Debug Tool command line command. Thesenew 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. Thisenhancement 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 moreeffectively. 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 DEBUGcompile 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 unitsthat Debug Tool displays and debugs. The NAMES EXCLUDE function allows you to inform Debug Tool that certainload modules and/or compile units are not to be debugged (for example, data modules). The NAMES INCLUDEfunction allows you to inform Debug Tool that certain load modules and/or compile units that would normally beconsidered 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 amixture 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.

The Debug Tool V5.1 provides the following functional and usability improvements which make Debug Tool an even moreproductive tool to use:

Dynamic debugging support for PL/I and C/C++Improved handling for long compile unit (CU) names for C/C++ and Enterprise PL/I programs%WHERE built-in functionRemote debug conditional watch breakpoint supportRemote debug COBOL local variable pane performance enhancementRemote debug additional command supportRemote debug step/breakpoint log message support

Debug Tool Utilities and Advanced Functions V5.1 (5655-M19) is a separate, optional product that builds on the functionin Debug Tool V5.1, providing even more debugging capability for z/OS and OS/390 applications. Debug Tool V5.1 is nowincluded in Debug Tool Utilities and Advanced Functions V5.1.

There have been previous levels of the Debug Tool (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 ofthe debugger. As of V1R5, optional feature C/C++ with Debug Tool is no longer in z/OS. The functional replacement thatyou will need to order for that feature is the C/C++ without Debug Tool feature in z/OS and also the independentstandalone program product - IBM Debug Tool for z/OS V6.1 (5655-P14) or V5.1 (5655-M18).

Tivoli Netview and Tivoli System Automation Ordering ConsiderationParts of two stand-alone products are included in msys for Operations in z/OS R7: Tivoli NetView for OS/390 V1R4(5697-B82) and Tivoli System Automation for OS/390 V2R3 (5698-A14). If you already have these stand-alone productsinstalled (at the V1R4 and V2R3 levels, respectively), you can install z/OS V1R7 (including msys for Operations) in thesame SMP/E zone as the stand-alone products. In this case, it is recommended that you order these stand-aloneproducts in your z/OS ServerPac. They will be installed in the same zones as z/OS, and will not require separatemaintenance and duplication of service work (which they would if they were in separate zones).

However, if you have an earlier level of either stand-alone product installed, you have to put the stand-alone product intoa separate zone before installing z/OS R7, and maintain its data sets with different names than the z/OS msys forOperations data sets. (Use BUILDMCS to move the stand-alone products or else you will have to reinstall them.) Olderlevels of Tivoli NetView and Tivoli System Automation than what is included in z/OS R7 cannot be ordered with a z/OSServerPac.

If you plan on moving from z/OS msys for Operations NetView to a full-function NetView V1R4, there is a sample job toassist you. This sample job will enlarge the msys for Operations data sets to accommodate the extra space needed for aNetView V1R4 installation. For details, see Tivoli OS/390 Installation: Migration Guide Version 1 Release 4, SC31-8768.



You may order Tivoli NetView V5R1 (5697-ENV) or V1R4 (5697-B82) with z/OS; it is compatible with msys for Operationsand will be installed in the z/OS SMP/E zones. You may order Tivoli System Automation V2R3 (5698-A14) with z/OS; it iscompatible with msys for Operations and will be installed in the z/OS SMP/E zones.

Tivoli NetView for z/OS Version 5 Release 1 (5697-ENV)IBM Tivoli NetView, V5R1 provides enhancements in the following areas and more:

TCP/IP Management Management of complex environments with support for DVIPA Monitor connections to any application on an OS/390 or z/OS

NetView Web Application Easier to use Web interface SNMP services available from a Web console

Time to Value NetView style sheet can help achieve simpler customization

Increased platform flexibility through Linux support for: IP resource discovery and management (Linux on zSeries) NMC Topology Server (Linux on zSeries) NMC Topology Console (Linux on Intel)

Remember, Tivoli NetView V5R1 (5697-ENV) can be ordered with, and is compatible with msys for Operations. If youwould like to use the full function Tivoli NetView (any release level), you must order it.

Tivoli System Automation for OS/390 Version 2 Release 3 (5698-A14)Tivoli System Automation for OS/390 (SA OS/390) plays an important role in building the end-to-end automation ofProject eLiza. The unique functions of SA OS/390 V2R3 can help with single z/OS or OS/390 systems and ParallelSysplex clusters to ease management, help reduce costs, and increase application availability. SA OS/390 is designed to automate I/O, processor, and system operations and includes "canned" automation for IMS, CICS, IBM Tivoli WorkloadScheduler, and DB2. SA V2 R3 became generally available on September 24, 2004.

Remember, Tivoli System Automation for OS/390 Version 2 Release 3 can be ordered with, and is compatible with z/OSmsys for Operations. For background information:

z/OS R4 msys for Operations contained portions of System Automation for z/OS Version 2 Release 1z/OS R5 and the z/OS V1.4 z990 Exploitation feature contained portions of System Automation for z/OS Version 2Release 2.z/OS R6 and z/OS R7 contains portions of Tivoli System Automation for OS/390 Version 2 Release 3.

If you would like to use the full function Tivoli System Automation V2R3, you must order it.

IBM Tivoli System Automation for z/OS (SA z/OS) Version 3 Release 1 (5698-SA3)IBM Tivoli System Automation for z/OS V3.1 integrates with Tivoli OMEGAMON and IBM Tivoli System Automation forMultiplatforms V2.1 to help you:

Proactively manage availability and performance through performance driven automationIntegrate z/OS into end-to-end automation of heterogeneous on demand applications

V3.1 self-configuration advances help reduce automation implementation time and cost with:Twelve add-on policies including WebSphere high availability automationPolicy import and mass updateSelf-configuration of IMS and CICS messages 1.2GDPS Integration

V3.1 is easier to use with:New command for moving a sysplex applicationDisplay of captured system messages and more IMS, CICS and VTAM information

SA V3.1 has a functional requirement (for all functions) on IBM Tivoli NetView for OS/390 (5697-B82) V1.4 or IBM TivoliNetView for z/OS (5697-ENV) V5.1, or later.

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 serverPrivacy through encryptionData integrityAuthorizationForwarding or tunnelingAn optional feature of compressionCommunication using SSH1 and SSH2 protocols.

It is an unpriced program product, that can be ordered with z/OS. It can run on z/OS R4 and higher. It has beengenerally available since May 28, 2004.

XML Toolkit for z/OS Version 1 Release 8 (5655-J51)The C++ XML Parser within this toolkit is a port of the IBM XML4C V5.5 Parser, which is based on Apache's Xerces C++V2.6 parser. Enhancements to the parser in this release include: * Extra Performance Linkage (XPLINK) support * Reduced dynamic link library (DLL) footprint * Updated World Wide Web Consortium (W3C) specifications support * Schema support improvements * Grammar caching The XSLT4C V1.9 C++ XSLT Processor within this toolkit, based on Apache's Xalan C++ V1.9 XSLT processor, has beenupdated with: * XPLINK support * Pluggable memory management * Improved stability on execution of large stylesheets and XML files * A global option to pool all text node strings

Support for the Java XML Parser and Processor is no longer packaged with the IBM XML Toolkit for z/OS. This supportcan now be obtained within the IBM SDK for z/OS, Java 2 Technology Edition, V1.4 (5655-I56) and the IBM 64-bit SDKfor z/OS, Java 2 Technology Edition V1.4 (5655-M30).

Due to general limitation of compatibility in the Apache Software Foundation open-source code upon which the program isbased, IBM XML Toolkit for z/OS, V1.8 will not necessarily provide compatibility with prior releases. Therefore,applications based on prior releases of the XML Toolkit, in general, may need to continue to require those prior releases.In support of these releases, both the V1.7 and the V1.6 products are included in the IBM XML Toolkit for z/OS, V1.8distribution package and will be installed, by default, along with V1.8, if not already present.The availability date was June 17, 2005.

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 continuedsupport for the OS/390 V2.10 C++ Compiler shipped within z/OS. The XML C++ Parser 1.4 for z/OS is a repackaging ofthe C++ parser originally shipped within the IBM XML Toolkit for z/OS and OS/390 V1.4. This Web deliverable wasavailable on September 24, 2004 at http://www.ibm.com/servers/eserver/zseries/software/xml/download/cparser_download.html .

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 machineat the SDK 1.4 level and the IBM Just-in-Time (JIT) compiler. The program is a key building block for developinge-business applications. 64-Bit SDK for z/OS, Java 2 Technology Edition, V1.4 passes the Java SDK 1.4 compatibility testand provides the stability, service, and scalability you expect from a zSeries program. 64-Bit SDK for z/OS, Java 2Technology Edition, V1.4 provides:

Support for Java application programming in a 64-bit environmentJava 2 APIs at the SDK 1.4 levelContinuation of the "write once, run anywhere" Java paradigmJava Record I/O (JRIO)XML supportSAF and cryptography support



Support for the IBM zSeries Application Assist Processors available on the z9-109, z990, and z890 serversAdditional 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 2Technology 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 functionSharing 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 theJNI interface, must be 64-bit programs. Programs dependent on JNI interfaces may require changes at the interfaceboundary to conform to 64-bit data types. Application JNI routines written in C will need to be recompiled for 64-bit, whichmay require some code changes.

For details on incompatibilities, visit http://www.ibm.com/servers/eserver/zseries/software/java/General availability occurred on December 17, 2004.

IBM Infoprint Transform products (not mentioned in foil above...)IBM is replacing the Infoprint Server Transforms for z/OS product with five separately orderable offerings. These productsare 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 beensignificantly enhanced to include new capabilities that support richer PDF content, and the ability to encrypt the documentwhile 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 Acrobatreader.Documents can also be enhanced to provide richer content and flexible access to related information. The AFP linkingcommand (LLE) can also be used to refer to objects external to the AFP document. The AFP to PDF transform will nowprocess these links to include the external reference in the resulting PDF document. This capability can be used, forexample, 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 theexisting 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 providedas a USERMOD.

5) Infoprint Coaxial Printer Support V2.1 for z/OS (5655-N62). The new Infoprint Coaxial Printer Support offeringreplaces the corresponding feature in the existing Infoprint Server Transforms for z/OS offering. It supports printing in IPPrintWay™ basic mode and IP PrintWay™ extended mode, which was introduced in Infoprint Server V1.5 for z/OS. Inaddition, multiple copies are now supported in IP PrintWay extended mode when printing on coaxial printers.



Release FrequencyIn response to customer feedback that the 6-month release cycle was too short and complicated customer migrationplans, IBM announced in August 2002 that the release schedule for z/OS has changed to a 12-month cycle. The vastmajority of z/OS customers migrate to new releases every 12 to 18 months. Less frequent releases in the future will allowIBM to provide even more integration testing for z/OS and related IBM middleware. It will also enable IBM to align thecoexistence, migration, and fallback policy with the service policy, once the annual releases begin.

Starting with z/OS R6, IBM intends to deliver releases annually, with general availability in September. Thispredictable release cycle will enable you to better plan your migration, freeing you to increase the value of your computingenvironment to your business and deliver better service to your end users. New z/OS functions will continue to bedelivered between releases through the normal maintenance stream or as Web deliverables. In addition, significant newfunctions may be delivered between releases as features of the product (such as what we've seen for the z990 support). z/OS V1R7 is the second release to be delivered on this annual release cycle.

These statements regarding the new release strategy represent current intentions of IBM. Any reliance on thesestatements is at the relying party's sole risk and will not create any liability or obligation for IBM. All statements regardingIBM's plans, directions, and intent are subject to change or withdrawal without notice.





z/OS Policy and Directions

Release Frequencyz/OS V1 R7 was GA on Sept 30, 2005

This is another delivery on our annual release cycle

All subsequent releases are planned for GA in September

Coexistence-Migration-FallbackService Support

Understanding CoexistenceCoexistence occurs when two or more systems at different software levels share resources. The resources could beshared at the same time by different systems in a multisystem configuration, or they could be shared over a period of timeby the same system in a single-system configuration. Examples of coexistence are two different JES releases sharing aspool, two different service levels of DFSMSdfp sharing catalogs, multiple levels of SMP/E processing SYSMODspackaged to exploit the latest enhancements, or an older level of the system using the updated system control files of anewer 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. Butother types of configurations can have resource sharing too. Examples of configurations where resource sharing canoccur 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 inan 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 systemsin a multisystem configuration using rolling IPLs rather than requiring a systems-wide IPL. The way in which you make itpossible 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 theobjective of coexistence PTFs is to allow existing functions to continue to be used on the earlier-level systems when runin a mixed environment that contains later-level systems. Coexistence PTFs are not aimed at allowing new functionsprovided in later releases to work on earlier-level systems.





z/OS R7 Coexistence

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

z/OS R4, z/OS R5, z/OS R6, and z/OS R7 are supported for coexistence, migration, and fallbackPrepare 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 R7. That means:

z/OS R4 JES2 thru z/OS R7 JES2 are supported for coexistence, migration, and fallbackz/OS R4 JES3 thru z/OS R7 JES3 are supported for coexistence, migration, and fallback

z/OSR4

z/OS R5

z/OS R6

z/OS R7

z/OS R8

z/OSR3

z/OS R9

Rolling z/OS across a multisystem configurationA rolling IPL is the IPL of one system at a time in a multisystem configuration. You might stage the IPLs over a few hoursor a few weeks. The use of rolling IPLs allows you to migrate each z/OS system to a later release, one at a time, whileallowing for continuous application availability. For example, data sharing applications offer continuous availability in aParallel Sysplex configuration by treating each z/OS system as a resource for processing the workload. The use of rollingIPLs allows z/OS systems running these applications to be IPLed one at a time, to migrate to a new release of z/OS, whilethe applications continue to be processed by the other z/OS systems that support the workload. By using LPARtechnology, 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/OSsoftware upgrades. It can be very difficult to schedule a time when all applications running on all the systems in amultisystem configuration can be taken down to allow for a complex-wide or Parallel Sysplex-wide IPL. The use of rollingIPLs not only enables continuous availability from an end-user application point of view, but it also eliminates the workassociated with migrating all z/OS systems in a multisystem configuration at the same time.

Understanding fallbackFallback (backout) is a return to the prior level of a system. Fallback can be appropriate if you migrate to z/OS R7 and,during testing, encounter severe problems that can be resolved by backing out the new release. By applying fallbackPTFs to the "old" system before you migrate, the old system can tolerate changes that were made by the new systemduring 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 youshift the system image from production (on the "old" release) to test (on the new release) and back again (to the oldrelease). 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 anyservice 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/OSproduct. z/OS JES2 and z/OS JES3 fallback can be done separately as long as the level of JES is supported with therelease 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 V1R7 level before the new functions canbe used. Therefore, be careful not to exploit new functions until you are fairly confident that you will not need to back outyour z/OS V1R7 systems, as fallback maintenance is not available in these cases. You should consult the appropriateelement 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 followingits general availability (GA) date. IBM, at its sole discretion, may choose to leave a release supported for more than threeyears. This change to the coexistence, fallback, and migration policy is effective starting with z/OS R6 (that is, the firstrelease of the new annual release cycle). As a general rule, this means that three releases will be supported forcoexistence, fallback, and migration over a period of three years. This represents an increase of one year over thetwo-year period provided by the current coexistence, fallback, and migration policy of four releases under a six-monthrelease cycle. The intention of this policy change is to simplify and provide greater predictability to aid in releasemigrations. Exceptions are:

w In some cases, more than three releases may be coexistence, fallback, and migration supported if IBM at its solediscretion 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 notbe coexistence, fallback, or migration supported with the new release.

Thus, except for JES2 and JES3, z/OS V1R7 is coexistence, fallback, and migration supported with the following four z/OS releases: V1R6, V1R5, and V1R4. This means that:

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

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

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

For JES2 and JES3, the way in which four consecutive releases is determined is different than for the rest of theoperating 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 V1R7 JES2 and JES3 are coexistence,fallback, and migration supported with the following JES releases: V1R6-V1R5 (both are functionally equivalent),and V1R4.

As of z/OS V1R2, compliance to the coexistence, fallback, and migration policy for JES2 and JES3 is enforced. Amigration 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 inthe 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 tocustomer-developed applications, vendor-developed applications, or IBM products that run on z/OS. IBM performsintegration 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 subjectto change or withdrawal without further notice. Any reliance on this statement of direction is at the relying party's sole riskand does not create any liability or obligation for IBM.

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

General availability of R7 is September 30, 2005. R4 is the oldest release that is servicesupported at that time and therefore the oldest release that is coexistence, fallback, andmigration supported with R7.

R7, R6, R5, R4 R7

The new policy starts. General availability of R6 was September 2004. R2 would be theoldest service-supported release at that time and therefore the oldest release that iscoexistence, fallback, and migration supported. However, its end-of-service date (October2004) is within three months of R6 general availability (September 2004), so R3 becomes theoldest release that is coexistence, fallback, and migration supported with R6.

R6, R5, R4, R3 R6

According to the old policy, four consecutive releases are supported for coexistence, fallback,and migration.

R5, R4, R3, R2 R5

According to the old policy, four consecutive releases are supported for coexistence, fallback,and migration. Also, OS/390 R10 and z/OS R1 count as one release.

R4, R3, R2, R1,and OS/390 R10R4

Explanation (see note 2)

Releases thatare coexistence,fallback, andmigrationsupported withthe release incolumn one (seenote 1)

z/OSrelease(seenote 1)



Notes:

1. For readability, the version numbers have been omitted from the releases shown. Also, release numbering offuture 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.

Planned general availability of R9 is September 2007. R7 is planned to be the oldest releasethat is service supported at that time and therefore the oldest release that is coexistence,fallback, and migration supported with R9.

R9, R8, R7 R9

Planned general availability of R8 is September 2006. R4 is planned to be the oldest releasethat is service supported at that time because its end-of-service date was extended by 18months to 31 March 2007. However, R4 is not planned to be coexistence, fallback, andmigration supported with R8. Therefore, R5 becomes the oldest release that iscoexistence, fallback, and migration supported with R8.

R8, R7, R6, R5 R8



Service PolicyIBM's current policy is to provide maintenance (service) for each release of z/OS for three years following their generalavailability (GA) date. However, service on the last release of a version might be extended beyond the intendedthree-year period. Prior to withdrawing service for any version or release of z/OS, IBM intends to provide at least 12months notice. The service policy for z/OS also applies to any enhancements, such as the z/OS V1R4 enhancements thatwere 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.

September 2008 (planned) 30 September 2005z/OS V1R7September 2007 (planned) 24 September 2004z/OS V1R6 31 March 2007 (announced) 26 March 2004 z/OS V1R5

31 March 2007 (announced)

Note: This is 18 months longer than the normalthree-year service period.

27 September 2002 z/OS V1R4 Occurred 31 March 2005 29 March 2002 z/OS V1R3 Occurred 31 October 2004 26 October 2001 z/OS V1R2 Occurred 31 March 2004 30 March 2001 z/OS V1R1 Occurred 30 September 2004 29 September 2000 OS/390 V2R10 Occurred 31 March 200331 March 2000 OS/390 V2R9 Occurred 30 September 200224 September 1999OS/390 V2R8End of service (EOS) General availability (GA) Version and release

Check out http://www.ibm.com/servers/eserver/zseries/zos/support/zos_eos_dates.html for a handy list of all end ofservice dates (back to MVS/ESA V4!).





z/OS Service PolicyRelease serviceable for three years following GAService on last release of a version might be extendedAt least 12 months notice before withdrawing serviceHandy website: http://www.ibm.com/servers/eserver/zseries/zos/support/zos_eos_dates.html

General Availability Service Expiration

OS/390 V2 R10 29 September 2000 30 September 2004

z/OS V1 R1 30 March 2001 31 March 2004

z/OS V1 R2 26 October 2001 31 October 2004z/OS V1 R3 29 March 2002 31 March 2005

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 Planned to be September 2007

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

LOOK!

z/OS Documentation: Where to StartTo gain an overview of z/OS and plan for the installation, review:

z/OS V1 R7.0 Introduction and Release Guide (GA22-7502) z/OS and z/OS.e V1R7 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 Bucketsz/OS, and most products that run on it, provide files containing information that became available after the productdocuments were printed. Kept on IBM's RETAIN system and also available using IBMLink, these files are calledpreventive service planning (PSP) "buckets", or just "PSPs". PSP buckets are identified by an upgrade identifier, andspecific parts of them are called subsets. Each upgrade contains information about a product. Subsets containinformation 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 upgradesfor SystemPac installations, the upgrade is CUSTOMPAC and the subsets are SYSPAC/FVD (for full volume dumpformat) and SYSPAC/DBD (for dump-by-data-set format).





Positioning for z/OS R7Read Documentation and PSP buckets

z/OS Migration and z/OS and z/OS.e Planning for InstallationSoftware PSP buckets: ZOSV1Rx: ZOSGEN, SERVERPAC, ...Hardware PSP buckets: 2094DEVICE, 2084DEVICE, 2086DEVICE, 2064DEVICE, 2066DEVICE

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

DASD Storage RequirementsUse SMP/E V3R2 or higher to reduce SMPLTS size!

Ensuring System Requirements Are SatisfiedDriving System RequirementsTarget System Requirements

HardwareSoftware

Coexistence System RequirementsMigration Actions You Can Do NOW

z/OS R4 z/OS R5 z/OS R6 z/OS R7Target 4,646 5,160 5,277 5,375

DLIB 6,295 7,212 7,338 7,455

HFS 2,200 2,200 2,800(some growth!)

2,800

sizes i n 3390 cyl ind ers

At the beginning of each PSP bucket is a change index. For each subset, the change index identifies the date of the latestentries in each section. You can quickly determine whether there are new entries you need to read by checking thechange index.Since z/OS V1R7, the contents of PSP buckets are no longer shipped with CBPDO and ServerPac orders. Instead of theactual PSP information, you now receive the names of relevant upgrades and subsets, and you’re directed to the PSPWeb site (https://techsupport.services.ibm.com/server/390.psp390) for the contents of the buckets. This ensures that yousee the latest PSP information, as the PSP information that was provided with an order was current only on the day theorder was created.

The upgrade for the z/OS R7 PSP bucket is ZOSV1R7. Recognizing that there are many PSP buckets to review, z/OSuses descriptive element names, instead of FMIDs for the subsets. This reduces the number of PSP buckets that must bereviewed, since most elements are composed of multiple FMIDs. There are subsets in the ZOSV1R7 upgrade for generaltopics (ZOSGEN), and for the ServerPac deliverable (SERVERPAC) that should be reviewed also. DFSMS isconsolidated into one subset. All PSP upgrades and subset IDs are listed in the z/OS Program Directory. However, thenon-exclusive elements' stand-alone product upgrade and subsets are used.

Hardware PSP upgrade identifiersHardware PSP bucket upgrade IDs are in the form xxxxDEVICE and contain the latest software dependencies for thehardware, and recommended PTFs and APARs required for specific processor models. The PSP hardware upgradeidentifiers are:

w 2094DEVICE for the z9-109 serverw 2084DEVICE for the z990 serverw 2086DEVICE for the z890 serverw 2064DEVICE for the z900 server w 2066DEVICE for the z800 server

DASD Storage Requirements If you are migrating to z/OS R7 from z/OS R4 or you will have a different product set than your previous release, you willsee increased need for DASD. How much more depends on what levels of products you are running. Keep in mind theDASD required for your z/OS system includes (per the z/OS Policy). That is, it includes ALL elements, ALL features thatsupport dynamic enablement, regardless of your order, and ALL unpriced features that you ordered. This storage is inaddition to the storage required by other products you might have installed. All sizes include 15% freespace toaccommodate 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 andz/OS.e Planning for Installation.

For z/OS R7: The total storage required for all the target data sets is 5,375 cylinders on a 3390 device. The total storagerequired for all the distribution data sets listed in the space table is 7,455 cylinders on a 3390 device. The total HFSstorage is 2,800 cylinders on a 3390 device for the ROOT HFS and 50 cylinders for the /etc HFS. The total storagerequired for the SMP/E SMPLTS is 0 3390 cylinders (there are no load modules in z/OS R7 that are both cross-zone anduse 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 R7 ServerPac via tape: 1. Any one of the following:

z/OS R4 with PTFs (several for LE since ServerPac uses LE runtime!)Customized Offerings Driver (subset of z/OS R4, 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 R7 ServerPac via electronic delivery:

1. Must meet the tape requirements (on the previous foil)

2. And 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!).

z/OS Driving System Requirements The driving system is the system image (hardware and software) that you use to install the target system. The targetsystem is the system software libraries and other data sets that you are installing. You log on to the driving system andrun jobs there to create or update the target system. Once the target system is built, it can be IPLed on the samehardware (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 toinstall applicable coexistence service on the driving system before you IPL the target system. If you don't install thecoexistence service, you will probably experience problems due to incompatible data structures (such as incompatibledata 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 R7 GA, this driver is a subset of a z/OS R4 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 orhigher DASD devices. The Customized Offerings Driver requires a locally attached non-SNA terminal and a systemconsole 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 inmultisystem configurations is not supported. The Customized Offerings Driver is intended to be used only to install newlevels of z/OS using ServerPac or CBPDO, and to install service on the new software until a copy (clone) of the newsystem 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 (IPServices), Security Server, and the system-managed storage (SMS) facility of DFSMSdfp, but these items are notcustomized. However, existing environments can be connected to, and used from, the Customized Offerings Driversystem.

Identifying Driving System Software Requirements for ServerPac for z/OS R7Driving system requirements for installing z/OS R7 by way of ServerPac or dump-by-data-set SystemPac are:

An operating system: Use any of the following: z/OS V1R4 with the PTFs in the table belowThe 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 theIPLed system is required. Proper authority: Use the RACFDRV installation job as a sample of the security system definitions required so thatyou 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 theSUPERUSER.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 inthe 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 ageneric name for these resources). The commands to define these facility class resources are inSYS1.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 mustcontain OMVS segments with a GID value for each group and a UID value for the user ID. (For ease of useand 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 beunique.



You must duplicate the required user ID and group names in each security database, including the sameuser ID and group ID values in the OMVS segment. This makes it easier to transport the HFS data setsfrom test systems to production systems. For example, the group name TTY on System 1 must have thesame group ID value on System 2 and System 3. If it is not possible to synchronize your databases youwill 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 existingnames, you can create and activate a user ID alias table. For information about defining these group and userIDs to RACF and about creating a user ID alias table (USERIDALIASTABLE), see z/OS UNIX SystemServices Planning. Other sources of information are SYS1.SAMPLIB member BPXISEC1 and the z/OS UNIXCustomization Wizard (http://www.ibm.com/eserver/zseries/zos/wizards/). (Note: You can use the RACFDRVinstallation job as a sample of the security system definitions required to perform the installation tasks.)

Language Environment run-time options: z/OS R7 ServerPac requires that the following Language Environmentrun-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 librarySCEERUN. If SCEERUN is not in the link list on the driving system, you must edit the ServerPac installation jobs toadd it to the JOBLIB or STEPLIB DD statements.OMVS address space active: For ServerPac only (not SystemPac), an activated OMVS address space with z/OSUNIX 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 SMSis 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 atleast 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 aminimal 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 thenames in the ALLOCDS job. You must also activate SMS on the target system.

DFSORT: msys for Setup job XMLGNR8 requires DFSORT or an equivalent sort program on the system on which theXMLGNR8 job is run. 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 V1R7 itself does not use the ++JAR support.zFS configuration requirements (optional): If you will specify that you will use a zFS for ServerPac installation, thenyou must be sure that the zFS has been installed and configured, as described in z/OS Distributed File Service zSeriesFile System Administration. Electronic delivery requirements (optional): If you intend to receive your ServerPac order by way of the Internet, youneed 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 systemmust minimally meet the driving system requirements for CBPDO Wave 1 and must have the current (latest) levels ofthe program management binder, SMP/E, and HLASM. The service jobs generated by the CustomPac InstallationDialog use the target system's (and therefore current) level of the binder, SMP/E, and HLASM. If you choose to useyour own jobs, model them after the jobs provided by ServerPac or dump-by-data-set SystemPac by adding STEPLIBDD statements to access MIGLIB (for the binder and SMP/E) and SASMMOD1 (for HLASM). Be sure that theSASMMOD1 and SYS1.MIGLIB data sets are APF authorized. Another way to install service is from a copy of yourtarget system.

Driving System PTFs for ServerPac for z/OS R7

w BCP: UW85908, UW86153

w DFSMSdfp: UA03183, UA04412, UA05519, UA14836, UW85002, UW86070, UW89483

w Language Environment: UQ70118, UQ70160, UQ70272, UQ70333, UQ70416, UQ70498, UQ70557,UQ70590, UQ70592, UQ70593, UQ70596, UQ70606, UQ70647, UQ70650, UQ70687, UQ70697,UQ70704, UQ70706, UQ70779, UQ70868, UQ71039, UQ71063, UQ71068, UQ71238, UQ71263,

z/OS V1R4PTFs z/OS release



DFSMSdfp: UA14838

For servicing: z/OS R7 level of the Program Management Binder, HLASM (V1R5), and z/OS R7SMP/E (SMP/E V3R4)

z/OS V1R6

w DFSMSdfp: UA05520, UA14837

w z/OS UNIX: UQ79726, UQ85020For servicing: z/OS R7 level of the Program Management Binder, HLASM (V1R5). and z/OS R7SMP/E (SMP/E V3R4)

z/OS V1R5

UQ71321, UQ71361, UQ71496, UQ71530, UQ71710, UQ71760, UQ71782, UQ71968, UQ72004,UQ72574, UQ72696, UQ73749, UQ74531, UQ75076, UQ75401, UQ75491, UQ76026, UQ76036,UQ76266, UQ76456, UQ76852, UQ77438, UQ77457, UQ77642, UQ77836, UQ77996, UQ78072,UQ78140, UQ78148, UQ78196, UQ78708, UQ78925, UQ78939, UQ79725, UQ80924, UQ85017

w z/OS UNIX:UA06764, UW93643

For servicing: z/OS R7 level of the Program Management Binder, HLASM (V1R5), and z/OS R7SMP/E (SMP/E V3R4)



Identifying Driving System Software Requirements for Servicing z/OS R7 and Installing CBPDOAfter installing via ServerPac, you will eventually want to install service on your z/OS R7 system. The driving system toinstall service on your z/OS R7 ServerPac system are the same as to install with the CBPDO method. For servicing yourServerPac 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 bemore manageable, is divided into several tasks called ripples.) This section describes the driving system requirements foreach wave.

z/OS R7 CBPDO: Driving System Wave 0In Wave 0 you install the program management binder (part of the BCP), the HLASM base element, and the SMP/E baseelement. 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 R7 Wave 0:

z/OS R4 or later. Also, if you install from 3590 tape, you should have APAR OW51956 installed on your drivingsystem. On z/OS V1R4 the PTF is UW85187. The Customized Offerings Driver (5665-M12).

z/OS R7 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 V1R4 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 aSTEPLIB DD statement to access the z/OS V1R7 binder and z/OS V1R7 SMP/E in the Wave 0 target system'sSYS1.MIGLIB data set, and to access the z/OS V1R7 HLASM's ASM.SASMMOD1 data set. Ensure that the targetsystem'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




23© 2006 IBM CorporationMMigrating to z/OS 1.7: Part 1 of 3 - Get Ready!

Driving System Requirements to Service z/OS R7 (and for installing via CBPDO)

Very Similar to Installing via ServerPac: z/OS R4 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

IEW2690E 3530 ONE OR MORE FIELD DESCRIPTORS IN GOFF RECORD 3 WITHIN MEMBER CELQAWIIDENTIFIED BY DDNAME SMPWRK3 ARE NOT VALID. ERRORID = 40. IEW2307E 1032 CURRENT INPUT MODULE NOT INCLUDED BECAUSE OF INVALID DATA.

The Customized Offerings Driver (5665-M12).Proper security: In order for you to install into the HFS, the security definitions described previously for ServerPac arerequired. Binder entry in SMP/E UTILITY: The SMP/E UTILITY must have an entry for the binder. You can specify any of theseprogram names in the UTILITY entry: IEWBLINK, HEWL, IEWL, LINKEDIT, or HEWLH096. (The linkage editor, whichuses 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 yourprogram search order because many elements and features require it. If you wish, add SCEERUN to your LNKLSTconcatenation. If you don't add SCEERUN to your LNKLST, you must access SCEERUN by using STEPLIB DDstatements in the individual element and feature procedures that require them. The BCP's Program ManagementBinder is one function that requires access to SCEERUN; it has been required since OS/390 R10. This means thatyou must make available SCEERUN (via the LNKLST or STEPLIB, for instance) to any JCL and procedures (such asSMP/E procedures) that invoke the binder. This ensures that processing, such as conversion of long names to shortnames, is successful.OMVS address space active: Before you install the elements and features in Wave 1, you must activate the OMVSaddress 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 R7 CBPDO: Driving System Wave 2In Wave 2 you install the z/OS V1R7 level of JES2 or JES3. Wave 2 is optional and can be combined with Wave 1. Thedriving system requirements for Wave 2 are the same as for Wave 1.



Choosing IBM Products That You Want to Run with z/OSThe functional and minimal requirements are found in the z/OS and z/OS.e Planning for Installation which is available onthe 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/shopzseriesUse the product catalogs (order checklists). For z/OShttp://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 ProductsThat 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 CBPDOorder, or separate ProductPac order.

If you're migrating to z/OS V1R7, you can find out which products have new levels by using ShopzSeries or by using theSMP/E base element's Planning and Migration Assistant. Both tools use data found on your system as well as the latestIBM software product catalog.

Choosing ISV products that you want to run with z/OSFor a list of independent software vendors (ISVs) that support z/OS, as well as announcements, testimonials, and otherinformation, see http://www.ibm.com/eserver/zseries/solutions/s390da/

For a directory of IBM and IBM Business partners that provide z/OS applications, tools, and services, see the GlobalSolutions Directory: http://www.ibm.com/software/solutions/isvNote that you can use SystemPac to get some ISV products on system delivery vehicles with IBM products. For a list ofselectable ISVs with SystemPac, see: http://www.ibm.com/ca/custompac/

VM Guest Considerations




24© 2006 IBM CorporationMMigrating to z/OS 1.7: Part 1 of 3 - Get Ready!

Target System Requirements for z/OS R7

Software Requirements Coexistence Software (on Other Target Systems)Correct Levels of IBM Non-z/OS and Non-IBM Products

Functional Requirementsz/OS R7 must run in z/Architecture mode (...since z/OS R6!)Some functions (like zAAP) require z990 or z890 at least

VM Guest considerationsOnly on z800 or z890: cannot IPL z/OS under an LPAR named ZOSExxxx (includes as a VM guest).

(z/OS R6's Dynamic LPAR Rename function on z890 can help here!)

Hardware RequirementsProcessor Requirements:

an IBM ^ zSeries z9-109, z990, z890, z900, or z800

Coupling Facility: see http://www.ibm.com/eserver/zseries/pso/cftable.html

z/OS can run as a VM guest. Requirements are:Must be on a z9-109, z990, z890, z900, or z800 server: VM must be z/VM (not VM/ESA). Furthermore,

if a z9-109 or z990 server, the z/VM PTF for APAR VM63124 must be installed.If a z800 or z890 server, then z/OS.e can run as a VM guest. The server must be a z800 or z890, VM must bez/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 logicalpartition (LPAR), and the LPAR must be named ZOSExxxx (where xxxx is any valid combination of zero to fourcharacters). The LPAR name restriction ensures compliance with z/OS.e license terms, which prohibit z/OS andOS/390 from running in a z800 or z890 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 namerestriction is only applicable to z800 and z890 servers, not other servers. The Dynamic LPAR Rename functionavailable on z890 can assist you with this requirement.)

Target System Hardware RequirementsThe minimal hardware requirements for z/OS, as well as additional hardware needed by specific z/OS elements andfeatures is documented in z/OS and z/OS.e Planning for Installation. Remember, z/OS V1R7 runs only inz/Architecture mode, and only on z9-109, z990, z890, z900 or z800 servers.Identifying Processor Requirementsz/OS V1R7 runs on the following IBM ^ zSeries servers (or their equivalents):

IBM ^ zSeries 9109 (z9-109)IBM ^ zSeries 990 (z990). IBM ^ zSeries 890 (z890).IBM ^ zSeries 900 (z900). IBM ^ zSeries 800 (z800).

Identifying Coupling Facility RequirementsThere are hardware and software requirements related to coupling facility levels (CFLEVELs). See http://www.ibm.com/eserver/zseries/pso/cftable.html.



Selected IBM Software Products that will run on z/OS R7 (and zAAP levels)For a complete list of the minimum release of IBM software products that run on z/OS R7, refer to Appendix C of z/OSand z/OS.e Planning for Installation.

A note for WebSphere Application Server users: Because WebSphere Application Server for z/OS and OS/390, V4.0.1will not be supported on z/OS R6 or z/OS R7 and its service has been discontinued on April 30, 2005 (as announced inSoftware Announcement 904-021, dated February 3, 2004), customers currently running WebSphere V4.0.1 are stronglyencouraged to migrate to WebSphere V5 in order to avoid the need to simultaneously upgrade the WebSphere and z/OSlevels. Websphere V5.0 is planned to be end of service on September 30, 2006.

If you are interested in exploiting (or doing capacity planning for) zAAPs, then there are minimum software levelsrequired. 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 IBMSolution Developers Kit (SDK) for z/OS, Java 2 Technology Edition, V1.4 with PTF (or later) for APAR PQ86689 must beused and for WebSphere-based Java workloads, WebSphere Version 5.1 or above is required.

Here is a table outlining the subsystems and minimum Java levels dependencies for determining zAAP Java executionand exploitation potential. The rows in blue identify some of the products levels that will exploit zAAPs. The rows inyellow, while not able to exploit the benefits of zAAPs, show where the zAAP Projection Tool for Java 2 TechnologyEdition, SDK1.3.1 can be used to assist in zAAP capacity planning. For instance, WebSphere V5.0.2 cannot exploitzAAP, however the zAAP Projection Tool can be used to determine zAAP Java execution potential if the WebSphereworkloads were migrated to the required level for zAAP exploitation.





Some IBM SW Target System Requirements for z/OS R7product name minimum supported level

CICS TS V1 R3 (End of Service: 4/30/06)

for determining zAAP execution potential, can use V2 R2.for zAAP exploitation, minimum level is V2 R3.

DB2 V7 with PTFs

for determining zAAP execution potential and exploitation, minimum level is V7

IMS V7 with PTFs (End of Service: 11/8/05)

for determining zAAP execution potential and exploitation, minimum level is V7

WebSphere Application Server

V5.0 (Note: WAS V4.0.1 is not supported on z/OS R6!)

for determining zAAP execution potential, can use V5.02for zAAP exploitation, minimum level is V5.1end of service for V5.0 is 9/30/06

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

The zAAP Projection Tool for Java 2 Technology Edition, SDK1.3.1 can be used to assist in zAAP capacity planning.



Processors Supported for z/OS R7: z/Architecture provides performance and reliability improvements over ESA/390 architecture. Since z/OS R6, z/OS nolonger supports ESA/390 architecture. z/OS R6 required z/Architecture servers, and established a new architectural levelset, and must be IPLed in z/Architecture mode. Thus, z/OS R6 and z/OS R7 support only the z9-109, z990, z890, z900,and z800 servers (and their equivalents). z/OS R6 and z/OS R7 will not IPL on the G5, G6, and Multiprise 3000servers.





z/OS 1.4z/OS 1.5

z900

z/OS 1.6z/OS 1.7

z890G5/G6

z/OS HW support and z/OS Architectural Level Set

z800

z/OS.e 1.4z/OS.e 1.5z/OS.e 1.6z/OS.e 1.7

z990

z/OS.e 1.4z/OS.e 1.5z/OS.e 1.6z/OS.e 1.7

z9-109

Architecture Modes Supported by Release and ServerThis table shows you the architecture mode supported on each release and server.

z/Architecturenot supportedz/OS V1R7z/Architecturenot supportedz/OS V1R6z/ArchitectureESA/390z/OS V1R5

z/Architecture ESA/390 z/OS V1R2, R3, or R4 without the z/OSV1R2/3/4 Bimodal MigrationAccommodation installed or after thesix-month term has expired

ESA/390 and z/Architecture ESA/390 z/OS V1R2, R3, or R4 with the z/OSV1R2/3/4 Bimodal MigrationAccommodation installed and within thesix-month term

z/Architecture ESA/390 z/OS V1R1 ESA/390 and z/ArchitectureESA/390OS/390 V2R10

Architecture mode supported byz990, z900, z890, and z800 servers

(and z9-109 on z/OS R4 and higher)

Architecture mode supported byG5, G6, and Multiprise 3000 servers

Release





A Brief History of Supported Architecture Modes

G5/G6 MP3000 z800, z900, z890, z990

* using z/OS Bimodal Migration Accommodation within terms of offering

OS/390 R10 ESA/390 ESA/390 or z/Architecture not supportedz/OS R1 ESA/390 z/Architecture not supportedz/OS R2 - R4 ESA/390 z/Architecture R4: z/Architecture

z/OS R2 - R4 * ESA/390 ESA/390 or z/Architecture R4: ESA/390 or z/Architecture

z/OS R5 ESA/390 z/Architecture z/Architecturez/OS R6 not supported z/Architecture z/Architecturez/OS R7 not supported z/Architecture z/Architecture

ESA/390 is 31-bit, z/Architecture is 64-bit

z9-109

Deciding Which to Migrate First - SW (from z/OS R4 to R7) or HW (to z9-109, z990, z890, z900, or z800)The IBM ^ z9-109, z990, z890, z900, and z800 servers support the 64-bit architecture, z/Architecture. When yourun z/OS on a z9-109, z990, z890, z900, or z800 server in z/Architecture mode you can take advantage of all that thissoftware/hardware combination has to offer, such as:

w Intelligent Resource Director (IRD), which dynamically manages processor and channel resource utilization acrossLPARs based on workload priorities. IRD combines the strengths of LPARs, Parallel Sysplex, and workloadmanager (WLM).

w HiperSockets, which allows high-speed connectivity between LPARs without any physical cabling (providing a"TCP/IP network in the system").

w 64-bit real and virtual storage support, which provides relief from the constraint of the 2 GB real and virtual storagelimit of ESA/390 architecture and eliminates the overhead of page movement from central storage to expandedstorage.

Depending on your current environment, a migration can involve a software upgrade to z/OS R7, a hardware upgrade to az9-109, z990, z890, z900, or z800 server, and a change in architecture from ESA/390 to z/Architecture. In addition, youmight choose to change your terms and conditions -- from Parallel Sysplex License Charges (PSLC) pricing to WorkloadLicense Charges (WLC) pricing. Factors to consider when deciding whether to upgrade your software or hardware firstare:

w Existing plans and commitments. w Architectural level set requirement since z/OS R6, to run on z9-109, z990, z890, z900, or z800 in z/Architecture

mode.w Timing of capacity requirements and new functions (hardware and software). w Once a z9-109, z990, z890, z900, or z800 server is installed, how soon you want to exploit the new architecture

and how prepared you are for WLC pricing. (Refer to z/OS Planning for Workload License Charges.) w The level of existing software. w The level of existing hardware. w Your test environment. w Your disaster recovery environment.

Also consider how much change (and risk) you want to make (or accept) at any given upgrade. Some factors are:





Migrating to z/Architecture

This will allow you to exploit:64-bit architecture (z/Architecture), Intelligent Resource Director,HiperSockets, ...

Bimodal Migration accommodation allows you to use a "safety net" to z/Architecture, when coming from z/OS R4

Recommended scenarios follow, based on:need to exploit new architecturelevel of existing hardware and level of existing softwaremigration flexibility

minimizing change (hardware, software, and architecture) is recommendedTypical Migration Paths to z/OS R7 from z/OS R4:

Hardware First (recommended!)Software First from G5/G6/MP3000 (disallowed!)

Sincez/OS R6 in

z/Architecture!

w The ability to schedule multiple upgrade windows. If scheduling upgrades is not a problem for your applications,you might want to minimize the amount of change (risk) and make several small hardware or software changes.However, if because of testing, application availability, or other factors you get only two upgrade opportunities ayear, you might want to limit those to one hardware and one software change.

w The ability to back out from a given change. While it is normal to plan for backout from a processor change,architecture change, or a new operating system level, you might not want to do more than one at a time.

w How important it is to you to have similar test and production environments, and a similar disaster recoveryenvironment (for example, in terms of hardware, software, and architecture levels). Disaster recovery environmentsshould mirror as closely as possible their associated production environments. Therefore, plans for your disasterrecovery systems should include upgrading the hardware to support z/Architecture once your productionenvironment supports it.

As you will see, you have some flexibility when migrating to z/OS R7 on a z9-109, z990, z890, z900, or z800 server. Theoptimal migration path will not be the same for every customer. The topics that follow will help you determine the bestmigration path for you.



Recommended Migration Paths to z/OS R7: Hardware FirstUse the following general outline for migrating from z/OS V1R4 on a G5, G6, or Multiprise 3000 server to z/OS V1R7 on az9-109, z990, z890, z900, or z800 server: 1. Download and install the z/OS V1R2/3/4 Bimodal Migration Accommodation on your old system. Your old system will

still run in ESA/390 (31-bit) mode. 2. Install (if necessary) the appropriate software support for your server. Refer to the corresponding PSP bucket for any

newly identified required service.3. Upgrade to a z9-109, z990, z890, z900, or z800 server. When you IPL your old system (z/OS V1R4) on the new

server, your system will still run in ESA/390 mode if you specify ARCHLVL 1 in parmlib member LOADxx. 4. Migrate to z/Architecture mode within the terms and conditions of the Bimodal Migration Accommodation (that is,

within 6 months of licensing z/OS to that new server), first by specifying ARCHLVL 2, then by removing ARCHLVLand allowing it to default.

5. Install z/OS V1R7 using ServerPac, CBPDO, or SystemPac. When you IPL z/OS V1R7, your system will come up inz/Architecture (64-bit) mode.



Typical Migration Paths to z/OS R7: Hardware First


G5/G6MP3000

z/OS R431-bit

6 month fallback capabilitywith the Bimodal Migration Accommodation

zSeries

z/OSR4

31-bit

zSeries

z/OSR4

64-bit

zSeries

z/OS 1.7

64-bit

Recommended! Single changes in hardware, architecture, and software

Disallowed Migration Path to z/OS R7: Software First from G5/G6/MP3000You cannot use this path for migrating from z/OS V1R4 on a G5, G6, or Multiprise 3000 server to z/OS V1R7 on az9-109, z990, z890, z900, or z800 server. The reason is that z/OS V1R7 will not IPL on a G5, G6, or MP3000 server.Thus, the Hardware First Migration Path is recommended when migrating from a G5, G6, or MP3000 server.



Disallowed Migration Path to z/OS R7: Software First from G5/G6/MP3000


G5/G6MP3000

z/OS R431-bit

z/OS R7 will not IPL on G5/G6/MP3000

zSeries

z/OS 1.7

64-bit

G5/G6MP3000

z/OS R731-bit

Coexistence Service Requirements for z/OS Release 7To understand the Coexistence-Fallback-Migration policy for z/OS, and which releases are supported with z/OS V1 R7,see the Coexistence section of this presentation. Listed below are the coexistence and fallback service, for installation onan z/OS V1R4 system for z/OS V1R7. For a list of the coexistence service on z/OS V1R5 and z/OS V1R6 for z/OS V1R7,see Appendix B of this presentation.

Apply on z/OS V1R4, the coexistence and fallback service (PTFs) listed in the table below:

UA09332, UA09334 (if theConsoles Enhancementsfeature is installed)

BCP: A lower-level system in a sysplex can receive messages from a z/OS V1R6 or latersystem with a console ID of 0 and an area ID specified. The coexistence PTFs allow thelower-level receiving system to handle the messages correctly.


BCP: Increased CPU utilization in the console address space might be reported on allsystems in a sysplex after introducing a z/OS V1R4 system with the z/OS V1R4 ConsolesEnhancements feature, or later-level system, into the sysplex. The coexistence PTFsprevent heavy message traffic on the z/OS V1R7 system from impacting the other systemsin the sysplex.


BCP: Prevents the depletion of private storage in the console address space on areceiving system when a large number of WTO/R messages are received on that systemfrom other members of a sysplex.

BCP PTFs UA05642 andUA06654, SDSF PTFUQ79592

BCP, SDSF: In z/OS V1R5, a console enhancement minimizes the possibility of outagesdue to exhaustion of system resources used for messaging. The PTFs allow back-levelsystems to tolerate the enhancement.

UA01785, UA02025,UA02173, UA02178,UA90002 (if Japanese),UA90003, UQ74992

BCP, Communications Server, RMF: Allows a z/OS V1R4 system to coexist with a z/OSV1R5 or later system that runs on a z9-109, z990, or z890 server.

z/OS V1R4 PTFs Element or feature, and reason PTFs are needed





Coexistence System Requirements for z/OS R7 from z/OS R4Documented in z/OS Migration (December 2005 is the latest level - contains coexistence updates!)

From z/OS R4 Coexistence PTFs for z/OS R7:BCP - GRS, RRS, Console, Program Binder, XCF, z990, System Logger, AllocationCommunications Server - z990DFSMS - dfp, hsm, and rmm, and ICKDSF supportDistributed File Service - zFS HCD - V5 IODF sharing support,ISPF - large format seq ds display and messagesJES2 - for MAS support down to z/OS R4 JES2JES3 - for multisystem complex support down to z/OS R4 JES3Language Environment - downward compatibilityNFS - SMF records, mount handle data set coexistenceRMF - z990SDSF - Console

SMP/E - toleration of z/OS R7 (SMP/E V3R4) enhancements

From z/OS R5 or R6 Coexistence PTFs for z/OS R7:Found in the Appendix of your handout...

UA18497

BCP: DSNTYPE=LARGE data sets are only supported by z/OS V1R7. The coexistencePTF causes z/OS to detect the accidental specification of such a data set for stand-alonedump output and to reject its use, as has been previously done for such data setorganizations as a PDS.

UA17026 BCP: Allows a pre-z/OS V1R7 system to use an IODF that was created using z/OS V1R7HCD.

UA17177

BCP: z/OS V1R7 introduces the logger log stream DUPLEXMODE(DRXRC) specification.If DUPLEXMODE(DRXRC) is specified in a z/OS V1R7 system in a sysplex, and priorreleases are running in the same sysplex, the PTF must be installed. IfDUPLEXMODE(DRXRC) is not specified, installing the PTF is not required but isnevertheless recommended to avoid any complications if the configuration changes.


BCP: A z/OS V1R7 system cannot join a sysplex of lower-level systems, and a lower-levelsystem cannot join a sysplex of z/OS V1R7 systems, without this PTF.

UA09966

BCP: Starting in z/OS V1R6, the sysplex couple data set (CDS) can be expanded to allowup to 2047 members in a cross-system coupling facility (XCF) group. This is an increasefrom the previous maximum of 1023 members per XCF group. Formatting a couple dataset for more than 1023 members per group creates a Version 4 CDS. The PTF rolls back this function to z/OS V1R4. In terms of coexistence, it provides supportfor Version 4 sysplex CDSs on z/OS V1R4. This is important because all systems in asysplex 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 supportVersion 4 sysplex CDSs cannot join the sysplex.

UA09402, UA09424 BCP: Allows a z/OS V1R4 system to tolerate new resource recovery services (RRS)restart function in z/OS V1R6 (and later).

UA18540

BCP: GRS APAR OA11383 provides compatibility support for the corrected GRSISGLOCK structure rebuild processing in APAR OA11147 which is contained in z/OSV1R7. OA11383 MUST be installed and IPLed on EVERY system in the sysplex beforeinstalling and IPLing z/OS V1R7 on ANY system in the SYSPLEX.

UA09225 BCP: z/OS V1R6 has a new 64-bit global resource serialization (GRS) ISGQUERYapplication programming interface (API). The PTF allows a z/OS V1R4 system to tolerateISGQUERY requests from a z/OS V1R6 or later system.

UA07360 and, if Japanese,UW95504

BCP: APARs OA05025 (PTF UA07360) and OA05391 together provide corrective servicefor XCF recovery from partial writes to couple data sets. APAR OA05391 introduces a newformat for couple data set multi-subrecord check records (MSRCRs), which is required forrecovery from partial writes to certain types of couple data set records. APAR OA05025includes coexistence support that enables systems on which it is installed to interpret thenew MSRCR format. Because both APARs have been incorporated into z/OS V1R6 and later, all other systemsin the sysplex must be capable of interpreting the new MSRCR format before any V1R6 orlater system can be IPLed into the sysplex. V1R5 systems include support for interpretingthe new MSRCR format and do not require installation of additional maintenance toprovide this capability. You must IPL all other systems in the sysplex with the appropriatePTF for APAR OA05025 (PTF UA07360 for V1R4) before IPLing any V1R6 or later systeminto the sysplex. Rolling IPLs are sufficient to install the PTFs for APARs OA05025 andOA05391. Note that the recovery provided by these two PTFs is not completely effectiveuntil all systems in the sysplex, including z/OS V1R5 systems, have been IPLed with bothPTFs or with V1R6 or later.

UA02566

BCP: Produces an informative message when the z/OS V1R4 or earlier version of theprogram management binder is used to try to rebind incompatible program objects createdin z/OS V1R5 or later. The PTF detects when the program object level of the V1R5 objectis incompatible with back-level capabilities and produces an error message. Without thePTF, there might be a misleading error message or abend.

UA09963 BCP: Allows a z/OS V1R4 system with the Consoles Enhancement feature installed tocorrectly handle blank WTOs issued to another system.



UA07442, UW95453 DFSMSdfp, DFSMShsm: In z/OS V1R5, DFSMShsm was enhanced to use volume-levelfast replication to create backup versions for sets of storage groups. A set of storage

UW88886

DFSMSdfp, DFSMShsm, DFSMSrmm: In z/OS V1R5, the maximum value of the filesequence number for a data set on a tape volume increased from 9999 to 65 535 for IBMstandard label (SL) tapes, unlabeled (NL) tapes, and bypass label processing (BLP). ThisPTF causes a message and abend if a tape data set with file sequence number greaterthan 9999 is attempted to be opened on a back-level system.

UA16633, UA16922,UA17234

DFSMSdfp: z/OS V1R7 supports new QNAME and RNAME parameters for VSAM RLS.The coexistence PTFs prevent serialization problems from occurring when the newparameters are used in a GRS complex that includes a pre-z/OS V1R7 system.

UA14882, UA16223,UA16796

DFSMSdfp: As part of VSAM extent constraint removal in z/OS V1R7, these PTFs preventpre-z/OS V1R7 systems from opening data sets that have more than 255 extents. Also, ifa data set is open and a z/OS V1R7 job extends it past 255 extents, the close on thepre-z/OS V1R7 system fails. Finally, these PTFs prevent conversion of a data set havingmore than 255 extents from being converted by DFSMSdss to a non-SMS managed dataset on pre-z/OS V1R7 releases.

UA16993

DFSMSdfp: An enhancement in the z/OS V1R7 Object Access Method (OAM) componentintroduces a new valid value ("R") for the object location in the object directory to indicatethat the object resides on DB2 disk in recalled status. This PTF enables pre-z/OS V1R7OAMs to coexist in an OAMplex with OAMs at the z/OS V1R7 level.

UW85576 DFSMSdfp: Allows a z/OS V1R4 system to tolerate the 64-bit POSIX time support in z/OSV1R6 and later by converting values to the 32-bit format.

UA01753, UA03391,UW95817

DFSMSdfp: ICKDSF R17 (equivalent to the level in the z/OS V1R4 z990 CompatibilitySupport feature) removed the requirement to have volumes varied offline to all otherOS/390 or z/OS systems sharing the volumes when building indexes or refreshing,extending, or building new VTOCs. However, before implementing this function, you mustapply these coexistence PTFs to all sharing z/OS V1R4 systems.

UA09832, UA10775 DFSMSdfp: z/OS V1R6 has a new PDSE address space, SMSPDSE1, which isrestartable. The coexistence PTFs allow a z/OS V1R4 system to coexist with a z/OS V1R6or later system that is exploiting the new address space.

UA03391 DFSMSdfp: Allows DFSMSdfp to tolerate the support in ICKDSF R17 and DFSMS forreindexing online volumes.

UW94336

DFSMSdfp: Object Access Method (OAM) now expires object tape volumes and expirestape and optical volumes that belong to object backup storage groups. This functionsignificantly reduces the amount of private storage that the OAM address space uses atlarger installations. This PTF enables back-level OAMs to coexist in an OAMplex withOAMs at the z/OS V1R5 level.

UA09049

DFSMSdfp: Allows users on z/OS V1R4 systems to read and write non-VSAM extendedformat data sets with more than 16 stripes. Although such data sets can only be allocatedwith more than 16 stripes on z/OS V1R5 or later, they can be accessed for read and writeon back-level systems.

UW87192

DFSMSdfp: Before z/OS V1R5, a striped, extended-format sequential data set could beallocated with a maximum of 16 stripes, which limited the maximum data set size to 16volumes. Beginning with z/OS V1R5, an extended-format sequential data set can have amaximum of 59 stripes and, thus, a maximum of 59 volumes. This PTF allows a back-levelsystem to read or write to an extended-format sequential data set with more than 16stripes. However, the back-level system cannot allocate a data set with more than 16stripes.

UA90083, UA90089,UA90093, UA90098,UA90099

BCP, DFSMSdfp, DFSMSdss, DFSMShsm, DFSMSrmm: In z/OS V1R6, a new functionintroduced by PTF UA90124 enables DFSMS software support for IBM TotalStorageEnterprise Tape System 3592 and the media types MEDIA6, MEDIA7, and MEDIA8.Coexistence PTFs listed here allow a V1R4 system to coexist with a V1R6 or later systemthat uses this function.

UA11849 Communications Server: Allows a z/OS V1R4 system to coexist with a V1R7 system.



UA19928ISPF: Allows pre-z/OS V1R7 systems to intelligently display the number of tracks in a large format

UA90174 and UA90175 HCD: Provides support for HCD users who share IODF data sets between pre-z/OS V1R7systems and z/OS V1R7 systems.

UA20485Distributed File Service: Allows releases to correctly access the new structure in z/OSV1R7 (version 1.4) for zFS aggregates. If you do not install toleration APAR OA11573 onprior releases, prior releases will not be able to correctly access the new structure.

UA14531 Distributed File Service: Allows pre-z/OS V1R7 systems to tolerate new characters (@#$)allowed in z/OS V1R7 for zFS file systems and aggegates.

UA03299, UA90010,UA90011, UA90012 (ifJapanese), UW92622,UW92623 (if Japanese),UW94636, UW95741

DFSMSrmm: Backup at anytime is an enhancement in z/OS V1R5. Coexistence serviceprevents the failure of inventory management when a backup that uses this enhancementstarts on a lower-level system.

UA16947

DFSMShsm: z/OS V1R7 increases the number of data set names supported in a tapetable of contents (TTOC). If a system that has the coexistence PTF installed finds that theOCDS RECORDSIZE is 6144 bytes, which indicates that some instances of DFSMShsmin the HSMplex might be using the extended TTOC, then tape operations on that level ofDFSMShsm are inhibited.

UA16849, UA16857,UA16860, UA16944

DFSMShsm: z/OS V1R7 supports fast subsequent migration (FSM) of data sets. ThePTFs cause DFSMShsm to set the appropriate flags during recall processing so that if thedata set is later opened for output by either z/OS V1R7 systems or pre-z/OS V1R7systems, the flags used for reconnection determination are set appropriately.

UA09618 DFSMShsm: z/OS V1R6 and later allow multiple secondary space management (SSM)tasks to run concurrently. The PTF allows a z/OS V1R4 system to tolerate this SSMmultitasking.

UA15869, UA16550,UA16954

DFSMShsm: z/OS V1R7 supports large format sequential data sets. In an HSMplex withmore than one DFSMShsm host, take care when migrating the journal to a large formatsequential data set. All DFSMShsm hosts within an HSMplex must be at z/OS V1R7before 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 thejournal is a standard format data set, DFSMShsm initialization continues. If the journal is alarge format data set, message MSGARC0509E with the "LARGE" text in the message isissued and DFSMShsm is stopped. If the journal is a striped data set, messageMSGARC0509E with the "STRIPED" text in the message is issued and DFSMShsm isstopped. If the ARCBJRNL utility attempts to use a large format journal data set, it isended with return code RC40, which indicates an OPEN error.

UA16796, UA16951

DFSMShsm: z/OS V1R7 supports large format sequential data sets. The PTFs causepre-z/OS V1R7 systems that might potentially recall, recover, or ARECOVER a data set tofirst verify that the data set is not a large format data set. If it is, an error message is issueddescribing the reason for the failure.

UA16796

DFSMSdss: z/OS V1R7 supports large format sequential data sets. These PTFs causepre-z/OS V1R7 systems to issue ABEND213-14 for any large format dump data sets thatare provided as input to RESTORE or COPYDUMP, or output for DUMP andCOPYDUMP. If DFSMSdss encounters any large format sequential data sets as input tological 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.

UA15869, UA16550 DFSMSdfp: z/OS V1R7 supports large format sequential data sets. These PTFs causepre-z/OS V1R7 systems to issue ABEND 213-14 or 213-16 if a program attempts to opendata sets that cannot work on those systems.

groups is defined through an SMS construct termed "copy pool". The coexistence PTFsprevent back-level versions of DFSMShsm from processing target volumes in the copypool backup storage group. The DFSMShsm recovery of fast replication backups is not available on systems beforeV1R5. If you must back out of V1R5 to an earlier release, you can use the DFSMSdssCOPY command to recover individual volumes.



UO00114 SMP/E: Provides support for SMP/E users who share SMPCSI data sets betweenpre-z/OS V1R7 systems and z/OS V1R7 systems.

UR53977, UR54450,UR54453 (if Japanese)

SMP/E: Allows back-level SMP/E to tolerate enhancements introduced in z/OS V1R5SMP/E (which is equivalent to SMP/E V3R2).

UA19506 NFS: Allows a pre-z/OS V1R7 NFS server to read a mount handle data set written by NFSV1R7.

UA16682 NFS: Allows a pre-z/OS V1R7 NFS SMF report generator to process an SMF file thatincludes NFS V1R7 SMF records. Any records containing TCP/IP version 6 IP addresseswill be ignored.

UQ85891

Language Environment: The /etc/utmpx file contains a user accounting database. In z/OSV1R6, the format of the records in the file was extended to support longer remote hostnames, 64-bit timestamp structures, and a version indicator. The coexistence PTFprevents the standard interfaces in pre-V1R6 releases from accessing /etc/utmpxdatabases 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 returna null pointer. Applications can use perror() to print the error message.

UQ78072 Language Environment: Detects attempts to use a new suboption on back-level releasesthat do not support it. This coexistence service is necessary to support downwardcompatibility for Language Environment.

UA04010, UA07715 JES3: Allows z/OS V1R4 JES3 to run with z/OS V1R7 JES3 in a multisystem complex.

UA16216

JES2: Fixes a problem on a receiving z/OS V1R4 node that can occur in a rare situationwith a large scheduler work block text unit (SWBTU). Data sets have a large SWBTUwhen MAILTO, MAILCC, and MAILBCC keywords are used in addition to other keywordson OUTPUT JCL statements. The problem is caused by APAR OA09152 (PTF UA16213on z/OS V1R4 JES). This is a network-specific problem, not a MAS-specific problem.

UA03828, UA09500,UA90160, UA20901

JES2: Allows z/OS V1R4 JES2 to run with z/OS V1R7 JES2 in a multi-access spool(MAS).

UA19931, UA19934 (SwissGerman), UA19935(Japanese), UA19936(German), UA19937(uppercase English)

ISPF: Provides an appropriate message when a user attempts to open a large format sequential dataset from a pre-z/OS V1R7 release.

sequential data set. If the number of tracks is greater than 64 KB, the string “>64K” and a largerexplanatory message are written to the panel.





Content of z/OS R7Remember the only export contolled features are now z/OS Sec Lvl 3 and CS Sec Lvl 3

z/OS Ordering and DeliverablesRemember msys for Operations considerationSMP/E V3R4, Ported Tools, 64-bit Java, XML, ...

z/OS Policiesz/OS R7 Coexistence-Migration-Fallback from z/OS R4If you're on z/OS R4, the max migration stretch is to z/OS R7, prepare now!Plan for R8 Coexistence-Migration-Fallback...support back to z/OS R5.

Ensuring System Requirements are Satisfied Driving System Requirements - z/OS R4 + PTFs, ...Target System Requirements - Must run z/OS R7 in z/Arch!

Migrating to z/Architecture Migrating to z/OS R7 from R4: Hardware First Path is the way to go!

Coexistence Requirements

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




Migrating to z/OS 1.7 Part 2 and Part 3 Presentations Part 2 of 3: Get Set!

Migrations actions for z/OS R7 (with a focus on migrating from R4) from selected elements:

(General z/OS items)BCPC/C++Communications Server

HCD

Part 3 of 3: GO! Migrations actions for z/OS R7 (with a focus on migrating from R4) from selected elements:

DFSMSLanguage EnvironmentJES2 and JES3SMP/E

z/OS UNIX

Also included are highlights of some enhancements you'll see in z/OS R7 for system programmers.


Appendix A: List of Base Elements and Optional Features for z/OS V1.7The following table lists the base elements and optional features in z/OS V1.7. The following table headings are used:

Name What this document calls the element or feature. (To help you distinguish elements from features, element names inthis column are highlighted.) Also, this column tells you which elements and features are only in z/OS (not also inz/OS.e).

Function level The most recent release in which the element or feature changed. ("Change" means that one or more of theelement's or feature's FMIDs [function modification identifiers] was changed, or that the element or feature wasadded to the system. New function added in program temporary fixes [PTFs] is not considered change.) Also, fornonexclusive 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 V1R7 product level butthey are at various function levels. For example, the product level of z/OS BookManager READ is z/OS V1R7 butits 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) ornonexclusive (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 supportdynamic enablement)

z "Description" is a brief description of the element or feature, and miscellaneous facts about it.

Table 1. Base elements and optional features in z/OS V1R7 and z/OS.e V1R7

Type: base element, exclusive. OS/390 V1R2 BDT

Type: base element, exclusive. The Base Control Program (BCP) provides essential operatingsystem 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, andsupport for the Unicode(TM) Standard. As of z/OS V1R3 and z/OS.eV1R3, the BCP also includes the program management binder,which was formerly in the DFSMSdfp base element. IBM Health Checker for z/OS is now part of the BCP. This tool helpsimprove availability by reporting on active z/OS and sysplex settingsthat are different than IBM recommended best practices or customerdefined settings. It was initially available by PTF and download forz/OS V1R4 and z/OS.e V1R4, was integrated in base element msysfor Operations in z/OS V1R5 and z/OS.e V1R5, and was moved tothe BCP in z/OS V1R7 and z/OS.e V1R7.

z/OS V1R7 BCP Type and description

Function level (lasttime changed) Name



Type: base element, exclusive. Common Information Model (CIM) is a standard data model fordescribing and accessing systems management data inheterogeneous environments. It allows system administrators to writeapplications that measure system resources in a network withdifferent operating systems and hardware. To enable z/OS for crossplatform management from a common point of control, a subset ofresources and metrics of a z/OS system are mapped into the CIMstandard data model. CIM is new in z/OS V1R7 and z/OS.e V1R7.

z/OS V1R7 CIM

Type: optional feature, exclusive, priced, can be dynamicallyenabled. C/C++ without Debug Tool consists of:

w The XL C/C++ compiler

w C/C++ application development utilities. As of z/OS V1R5 and z/OS.e V1R5, optional feature C/C++ withDebug 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 theC/C++ compiler is withdrawn. The XL C/C++ compiler remains. Forinformation about migrating from the former to the latter, see z/OS XLC/C++ Compiler and Run-Time Migration Guide for the ApplicationProgrammer.

z/OS V1R7 C/C++ without DebugTool

Type: base element, nonexclusive. This element is supported withz/OS but not with z/OS.e. With z/OS.e, you install the code but it isnot functional and you are not licensed to use it. BookManager READ is used to display, search, and manage onlinedocuments and bookshelves. A related optional feature isBookManager BUILD.

OS/390 V1R1 (BookManagerREAD/MVS V1R3,5695-046)

BookManager READ (z/OS only)

Type: optional feature, nonexclusive, priced, can be dynamicallyenabled. 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 arenot licensed to use it. BookManager BUILD creates softcopy documents that can be usedby any of the BookManager products, such as BookManager READor Library Server.

OS/390 V1R1 (BookManagerBUILD/MVS V1R3,5695-045)

BookManager BUILD (z/OS only)

Type: optional feature, exclusive, priced, can be dynamicallyenabled. BDT SNA NJE allows JES3 users to transmit jobs, output,commands, and messages from one computer system to anotherwithin a SNA network. This feature is related to the element BDT andthe feature JES3.

OS/390 V1R2 BDT SNA NJE

Type: optional feature, exclusive, priced, can be dynamicallyenabled. 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 arenot licensed to use it. BDT File-to-File allows users at one z/OS system in a SNA networkto copy data sets to or from another z/OS system in the network. Thisfeature is related to the element BDT.

OS/390 V1R2 BDT File-to-File (z/OS only)

Bulk Data Transfer (BDT) provides the base services that theoptional BDT features (BDT File-to-File and BDT SNA NJE) need totransfer data from one computer system to another. You cannot activate any BDT functions until one or both of theoptional BDT features is enabled.



Type: base element, exclusive. Cryptography is the transformation of data to conceal its meaning. Inz/OS and z/OS.e, the base element Cryptographic Services providesthe following base cryptographic functions: data secrecy, dataintegrity, personal identification, digital signatures, and themanagement of cryptographic keys. Keys as long as 56 bits aresupported by this base element. (Keys longer than 56 bits aresupported by the optional feature z/OS Security Level 3.) Cryptographic Services consists of the following components:

w Integrated Cryptographic Service Facility (ICSF). The level ofV1R7 ICSF is FMID HCR7720, which is the same level as inthe Web deliverable ICSF 64-bit Virtual Support for z/OSV1R6 and z/OS.e V1R6. Note that a later level of ICSF (FMIDHCR7730) is available in the Cryptographic Support for z/OSV1R6/R7 and z/OS.e V1R6/R7 Web deliverable.

w Open Cryptographic Services Facility (OCSF), last changed inOS/390 V2R10.

w PKI Services, last changed in z/OS V1R7 and z/OS.e V1R7.Prior to V1R5, this component was in the optional featureSecurity Server, although it was licensed with the baseoperating system and could be used without ordering orenabling Security Server.

w System Secure Sockets Layer (SSL), last changed in z/OSV1R6.

z/OS V1R7 CryptographicServices

Type: optional feature, exclusive, unpriced, cannot be dynamicallyenabled. This feature works in conjunction with the Communications Serverbase element to provide stronger encryption (greater than 64 bits)than that available without this feature. This feature uses the TDESalgorithm for encryption. The actual level of encryption that takesplace with this feature installed can be configured to be somethingless than the maximum level enabled by this feature. This feature is related to the base element Communications Serverand to the Firewall Technologies component of the IntegratedSecurity Services base element. This feature is worldwide exportable subject to U.S. exportregulations.

z/OS V1R7 Communications ServerSecurity Level 3

Type: base element, exclusive, can be dynamically enabled. Communications Server (also known as CS z/OS) supports secureTCP/IP, SNA, and UNIX networking throughout an enterprise. It givesyou the ability to connect subsystems and applications to each other,and to connect network devices (such as terminals and printers) tothe system. Communications Server consists of two components: IP Servicesand SNA Services. SNA Services includes AnyNet function. A related optional feature is Communications Server Security Level3. For encryption, IP Services uses the firewall CDMF DES 40-bit,SNMPv3 DES 56-bit, IP Sec DES 56-bit, and AES algorithms. IPServices also uses the System SSL component of CryptographicServices for encryption services. SNA Services uses the limited DESalgorithm for encryption.

z/OS V1R7 CommunicationsServer

For encryption, CIM uses the DES 56-bit algorithm and, if z/OSSecurity Level 3 is installed, the TDES 168-bit algorithm.



Type: optional feature, exclusive, priced, can be dynamicallyenabled. DFSORT provides fast and easy sorting, merging, copying, reporting,and analysis of your business information, as well as versatile datahandling at the record, field, and bit level. DFSORT also includes thehigh-performance ICEGENER facility, the versatile ICETOOL utility,

z/OS V1R5 DFSORT

Type: optional feature, exclusive, priced, can be dynamicallyenabled. DFSMS Transactional VSAM Services (DFSMStvs) enables batchjobs and CICS online transactions to update shared VSAM data setsconcurrently. DFSMStvs was introduced in June 2003 as an optional feature ofz/OS V1R4 and z/OS.e V1R4.

z/OS V1R7 DFSMStvs

Type: optional feature, exclusive, priced, can be dynamicallyenabled. DFSMSrmm helps you manage your removable media as oneenterprise-wide library across systems that can share DASD.

z/OS V1R7 DFSMSrmm

Type: optional feature, exclusive, priced, can be dynamicallyenabled. DFSMShsm provides automated DASD storage management,including space management for low and inactive data, andavailability management for accidental data loss caused by local andsite disasters. DFSMShsm also lets you make effective use of tapemedia. DFSMShsm requires DFSMSdss. For this reason, DFSMShsm is notavailable by itself. If you want to use DFSMShsm, you must order theDFSMShsm/DFSMSdss combination. (DFSMSdss is also availableby itself for those who don't want DFSMShsm.)

z/OS V1R7 DFSMShsm (andDFSMSdss)

Type: optional feature, exclusive, priced, can be dynamicallyenabled. DFSMSdss copies and moves data for backup and recovery, and toreduce free-space fragmentation.

z/OS V1R7 DFSMSdss

Type: base element, exclusive. DFSMSdfp provides storage, data, program, and devicemanagement functions. Related optional features are DFSMSrmm,DFSMSdss, DFSMShsm, and DFSMStvs. As of z/OS V1R3 and z/OS.e V1R3, the program management binderis moved to the BCP base element.

z/OS V1R7 DFSMSdfp

Type: base element, exclusive. DCE Base Services provides services for developing and runningclient/server applications, including remote procedure call, directory,security, and distributed time services. This element is at the OpenGroup Open Software Foundation (OSF) DCE 1.1 level. DCE Base Services uses the limited DES algorithm for encryption.

OS/390 V2R9 DCE Base Services

For encryption:

w OCSF uses the RC2/RC4/RC5 40-56 bit and DES 56-bitalgorithms.

w PKI Services uses the RACF component of optional featureSecurity Server, and the ICSF, OCSF, and System SSLcomponents of base element Cryptographic Services. Fordigital signatures, PKI Services uses the RSA and DSAalgorithms.

w System SSL uses the RC2/RC4, DES through 56-bit, andDiffie-Hellman algorithms.



Type: base element, exclusive. OS/390 V1R1 ESCON Director

Type: base element, nonexclusive. The Environmental Record Editing and Printing Program (EREP)edits and prints reports for the records placed in the error recordingdata set (ERDS), helping IBM service representatives fix problems.

OS/390 V1R1 (EREP MVS V3R5,5658-260)

EREP

Type: base element, exclusive. Distributed File Service provides:

w The DCE file serving (DFS) component of the Open GroupOpen Software Foundation (OSF) DCE. The file servingsupport (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 systemthat can be used in addition to the Hierarchical File System(HFS). zFS file systems contain files and directories that canbe accessed with the z/OS and z/OS.e hierarchical file systemfile APIs. zFS file systems can be mounted into the z/OS UNIXhierarchy along with other local (or remote) file system types(such as HFS, TFS, AUTOMNT, and NFS). The zFS does notreplace the HFS; it is complementary to the HFS. As of z/OSV1R7, you can use any combination of HFS and zFS filesystems. zFS can be used for the root file system. BecausezFS has higher performance characteristics than HFS and isthe strategic file system, HFS mighty no longer be supportedin future releases and you will have to migrate the remainingHFS file systems to zFS. The zFS provides significant performance gains in mostenvironments requiring files 8 KB in size or greater that arefrequently accessed and updated. The access performance ofsmaller files is equivalent to the HFS. For all files, the zFSprovides a reduced exposure to loss of updates. The zFS is alogging file system with a write pattern to disk that reduces thepoints of failure after a system outage. For additionalinformation about the zFS, including how to migrate data fromthe HFS to the zFS, see z/OS Distributed File Service zSeriesFile System Administration. The zFS component has its own FMID starting with z/OSV1R5 and z/OS.e V1R5.

w Server message block (SMB) file/print serving support. TheSMB 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 WindowsXP Professional and Windows 2000 Professionalworkstations. Windows workstation users can also exploitz/OS and z/OS.e printer capabilities using the SMB file/printserver interface to the z/OS or z/OS.e Infoprint Server feature. For the software necessary to use the DFS or SMB file/printserving support, as well as the other Distributed File Servicefunctions, see Appendix B, Software requirements for z/OSand z/OS.e elements and features in z/OS Planning forInstallation..

The DFS and SMB support use the DES 56-bit algorithm forencryption.

z/OS V1R7 Distributed FileService

Symbols, and multiple output capability with the powerful OUTFILfeature. As of z/OS V1R2, DFSORT is exclusive to z/OS; the productDFSORT V1R14 (5740-SM1) is no longer marketed.



Type: optional feature, nonexclusive, priced, can be dynamicallyenabled. HLASM Toolkit provides tools to improve application development,debugging, and recovery. It is related to the base element HLASM.

z/OS V1R6 (Toolkit feature ofHLASM for MVS & VM& VSE V1R5,5696-234)

HLASM Toolkit

Type: base element, nonexclusive. High Level Assembler (HLASM) integrates almost all functions ofpast assemblers and provides extensions and improvements. Arelated optional feature is the HLASM Toolkit.

z/OS V1R6 (HLASM for MVS & VM& VSE V1R5,5696-234)

HLASM

Type: optional feature, exclusive, priced, can be dynamicallyenabled. Hardware Configuration Manager (HCM) is a PWS-basedclient/server interface to the base element HCD.

z/OS V1R7 HCM

Type: base element, exclusive. Hardware Configuration Definition (HCD) defines both the operatingsystem configuration and the processor hardware configuration for asystem. A related optional feature is HCM.

z/OS V1R7 HCD

Type: optional feature, nonexclusive, priced, can be dynamicallyenabled. 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 arenot licensed to use it. GDDM-REXX is a productivity tool that enables programmers toprototype GDDM applications and to create small routines and utilityprograms quickly and easily. This feature is related to the base element GDDM.

OS/390 V1R2 (GDDM-REXX/MVSV3R2, 5664-336)

GDDM-REXX (z/OS only)

Type: optional feature, nonexclusive, priced, can be dynamicallyenabled. 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 arenot licensed to use it. GDDM-Presentation Graphics Feature (PGF) is a set of programs forcreating presentation material in a variety of styles. This feature is related to the base element GDDM.

OS/390 V1R2 (GDDM/PGF V2R1.3,5668-812)

GDDM-PGF (z/OS only)

Type: base element, nonexclusive. This element is supported withz/OS but not with z/OS.e. With z/OS.e, you install the code but it isnot 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 areGDDM-Presentation Graphics Feature and GDDM-REXX. OtherGDDM-associated products (IVU, GKS, IMD) are not in z/OS, but areseparately orderable with z/OS.

OS/390 V1R2 (GDDM/MVS V3R2,5695-167)

GDDM (z/OS only)

Type: base element, exclusive. First Failure Support Technology (FFST) provides immediatenotification and first failure data capture for software events.

OS/390 V1R2 FFST

ESCON Director Support enables the reporting of ESCON directordevice errors to z/OS or z/OS.e.

Support



Type: base element, exclusive. Integrated Security Services provides base security functions forz/OS and z/OS.e. This base element was new in z/OS V1R5. It consists of fivecomponents that used to be in optional feature Security Server plusone new component, Enterprise Identity Mapping. The componentsare:

w DCE Security Server, last changed in OS/390 V2R9. Thiscomponent is at the OSF DCE 1.2.2 level. This componentuses the limited DES algorithm for encryption.

z/OS V1R7 Integrated SecurityServices

Type: optional feature, exclusive, priced, can be dynamicallyenabled. Infoprint Server allows you to print files on z/OS and z/OS.e printersfrom any workstation that has TCP/IP access. This feature consistsof the following components:

w IP PrintWay. This component has its roots in the IP PrintWayfeature of PSF/MVS V2R2 and the IP PrintWay/NetSpoolfeature of OS/390 V1R3. In z/OS V1R5, IP PrintWay extendedmode was introduced.

w NetSpool. This component has its roots in the NetSpoolfeature of PSF/MVS V2R2 and the IP PrintWay/NetSpoolfeature of OS/390 V1R3.

w Print Interface, new in OS/390 V2R5.

w Printer Inventory Manager, new in OS/390 V2R8.

w Transform Manager, 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 IPPrintWay component rather than the Communications Server baseelement's Network Print Facility (NPF) to reroute print data to an IPnetwork. IP PrintWay provides improved function, capacity,performance, and usability over NPF.

z/OS V1R5 Infoprint Server

Type: base element, nonexclusive. The Device Support Facility (ICKDSF) enables you to performfunctions needed for the installation and use of IBM DASD. ICKDSF was last changed in the z/OS V1R4 z990 CompatibilitySupport feature. This level was carried forward to the z/OS V1R4z990 Exploitation Support feature and then to z/OS V1R5, z/OSV1R6, and z/OS V1R7, and is functionally equivalent to the R17 levelof the ICKDSF product.

z/OS V1R4 z990Compatibility Supportfeature (ICKDSF for z/OS,z/OS.e, and OS/390R17, 5655-257)

ICKDSF

Type: base element, exclusive. IBM HTTP Server is the Web server for z/OS and z/OS.e. It providesscalable, high performance Web serving for critical e-businessapplications. It supports Secure Sockets Layer (SSL) secureconnections, dynamic caching using the Fast Response CacheAccelerator, multiple IP addresses, proxy authentication, anddouble-byte character set characters. IBM HTTP Server NA Secure is now a component of IBM HTTPServer. Prior to V1R6, it was an optional feature of z/OS and z/OS.e.This packaging change was the only change to IBM HTTP Server inV1R6; there was no functional change.

OS/390 V2R10 (but seedescription)

IBM HTTP Server



Type: base element, exclusive. ISPF provides facilities for all aspects of host-based softwaredevelopment. ISPF has four major components:

w Dialog Manager (DM). The Dialog Manager provides servicesto dialogs and end users. These services include display,variable services, input and output, user and applicationprofiles, table management, system interface services, anddialog testing and debugging aids.

w Program Development Facility (PDF). PDF provides servicesto assist dialog or application developers. These include editand browse functions, a wide range of foreground and batchcompilers, data set and catalog utilities, TSO commandinterfaces, and data set search and compare functions.

z/OS V1R7 ISPF

w Enterprise Identity Mapping (EIM), introduced by a PTF inz/OS V1R4 and z/OS.e V1R4, and last changed in z/OS V1R7and z/OS.e V1R7. This component allows you to map a user'sidentity on one system to the user's identity on anothersystem.

w Firewall Technologies, last changed in z/OS V1R4 and z/OS.eV1R4. The Internet Security Association and Key ManagementProtocol (ISAKMP) server of Firewall Technologiesimplements the required elements of Internet Key Exchange(IKE) as defined by Request for Comments (RFC) 2409. Theconfiguration server of Firewall Technologies communicateswith the firewall configuration graphical user interface (GUI)that is shipped within Firewall Technologies. FirewallTechnologies uses the DES algorithm for encryption.

w LDAP Server, last changed in z/OS V1R6 and z/OS.e V1R6.LDAP Server uses the System SSL component of baseelement Cryptographic Services for encryption. The RDBM DB2 backend function of the LDAP Server isremoved as of z/OS V1R4. You are encouraged to migrate tothe enhanced TDBM DB2 backend because of its improvedscalability and availability. For instructions, see z/OSIntegrated Security Services LDAP Server Administration andUse.

w Network Authentication Service, last changed in z/OS V1R6and z/OS.e V1R6. Network Authentication Service uses theDES algorithm for encryption. Prior to z/OS V1R2, thiscomponent was named Network Authentication and PrivacyService.

w Open Cryptographic Enhanced Plug-ins (OCEP), last changedin OS/390 V2R10.

Prior to z/OS V1R5, the five moved components (DCE SecurityServer, Firewall Technologies, LDAP Server, Network AuthenticationService, and OCEP), although packaged with the priced featureSecurity Server, were unpriced (that is, were licensed with the baseoperating system and could be used without ordering or enablingSecurity Server). Now that these five components are in baseelement Integrated Security Services, the packaging and pricing areconsistent.



Type: base element, exclusive. z/OS V1R7 Library Server

Type: base element, exclusive. Language Environment provides the run-time environment forprograms generated with C, C++, COBOL, Fortran, and PL/I. z/OS.e Language Environment does not support (but z/OS LanguageEnvironment does support) the following:

w COBOL, except for execution of precompiled COBOL DB2stored procedures and other precompiled applications that usethe Language Environment preinitialization interface(CEEPIPI). The applications could be compiled on a z/OSsystem, then run on a z/OS.e system. Stated another way,compiling COBOL programs on z/OS.e is not supported, andonly precompiled COBOL DB2 stored procedures and otherprecompiled applications that use the Language EnvironmentCEEPIPI (no other kinds of COBOL programs) can run onz/OS.e.

w Fortran.

w PL/I, except for execution of precompiled PL/I applications. Aswith COBOL, the applications could be compiled on a z/OSsystem, 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 canimprove the performance of applications and subsystems.)

Inclusion of Language Environment as a base element in z/OS andz/OS.e does not replace the need for separate compilers. As of z/OS V1R2, Language Environment supports the ISO '98 C++Standard Library. Language Environment uses the limited DES algorithm forencryption.

z/OS V1R7 LanguageEnvironment

Type: optional feature, exclusive, priced, can be dynamicallyenabled. JES3 accepts the submission of work for the BCP. JES3 exercisescentralized control over its job processing functions, whereas JES2exercises independent control. Prior levels of JES3 can be used with z/OS V1R7 but not with z/OS.eV1R7.

z/OS V1R7 JES3

Type: base element, exclusive. JES2 accepts the submission of work for the BCP. JES2 exercisesindependent control over its job processing functions, whereas JES3exercises centralized control. Prior levels of JES2 can be used with z/OS V1R7 but not with z/OS.eV1R7.

z/OS V1R7 JES2

w Software Configuration and Library Manager (SCLM). SCLM isa tool that automatically controls, maintains, and tracks all ofthe software components of the application throughout thedevelopment cycle.

w Client/Server component. The Client/Server componentprovides users who have a workstation running Windows orUNIX with a graphical user interface to ISPF applicationpanels.

As of z/OS V1R2, the Library Management Facility (LMF) of ISPFwas removed.



Type: base element, exclusive. Managed System Infrastructure for Setup (msys for Setup),introduced in z/OS V1R1, offers a new approach for configuringz/OS, z/OS.e, and products that run on z/OS and z/OS.e. Theconfiguration process is driven by a graphical user interface thatgreatly facilitates the definition of customization parameters. Updatesare under the control of the msys for Setup user and are madedirectly to the system.

z/OS V1R4 msys for Setup

Type: base element, exclusive (but see note below). Managed System Infrastructure for Operations (msys for Operations)simplifies the day-to-day operation of z/OS and z/OS.e ParallelSysplex configurations by automating typical operator tasks andevents. msys for Operations was new in z/OS V1R2. As of z/OS V1R7, IBM Health Checker for z/OS is no longer part ofmsys for Operations. It is now part of the BCP base element.

Note:Parts of two products are included in msys for Operations:Tivoli NetView for OS/390 V1R4 (5697-B82) and SystemAutomation for z/OS V2R3 (5645-006 or 5698-A14). If youalready have the NetView and System Automation productsinstalled (at the V1R4 and V2R3 levels, respectively), you caninstall z/OS V1R7 or z/OS.e V1R7 (including msys forOperations) in the same SMP/E zone as the NetView andSystem Automation products. In this case, it is recommendedthat you order the NetView and System Automation products inyour z/OS V1R7 ServerPac. They will be installed in the samezones as z/OS V1R7, and will not require separatemaintenance and duplication of service work (which they wouldif they were in separate zones). However, if you have an earlier level of either the NetView orSystem Automation product installed, you have to put theproduct into a separate zone before installing z/OS V1R7, andmaintain its data sets with different names than the z/OSV1R7 msys for Operations data sets. (Use BUILDMCS tomove the NetView or System Automation product or else youwill have to reinstall it.) Older levels of NetView and SystemAutomation than what is included in z/OS V1R7 cannot beordered with a z/OS V1R7 ServerPac. If you plan on moving from z/OS V1R7 msys for OperationsNetView to a full-function NetView V1R4, there is a sample jobto assist you. This sample job will enlarge the msys forOperations data sets to accommodate the extra space neededfor a NetView V1R4 installation. For details, see Tivoli OS/390Installation: Migration Guide Version 1 Release 4, SC31-8768.

You may order the follow-on NetView product, Tivoli NetViewV5R1 (5697-ENV), with z/OS V1R7. It is compatible with msysfor Operations and will be installed in the z/OS SMP/E zones.

z/OS V1R6 msys for Operations

Type: base element, exclusive. This element is supported with z/OSbut not with z/OS.e. With z/OS.e, you install the code but you are notlicensed to use it. This element provides the device support code for various magneticand optical devices.

OS/390 V1R1 MICR/OCR (z/OS only)

Library Server converts BookManager documents to HTML fordisplay through a web browser. Prior to z/OS V1R5, this element wasnamed BookManager BookServer.



Type: base element, exclusive. Network File System acts as a file server to workstations, personalcomputers, or other authorized systems in a TCP/IP network. Itconsists of a client (Network File System Client) and a server(Network File System Server). It supports Berkeley sockets but notTCP/IP sockets.

z/OS V1R7 Network File System

With each release of z/OS and z/OS.e, additional tasks aresupported by msys for Setup:

w Starting in z/OS V1R1 you could use msys for Setup to set upa Parallel Sysplex resource sharing environment. (For moreinformation, see z/OS MVS Setting Up a Sysplex.)

w In z/OS V1R2, usage of msys for Setup was extended to letyou:

z Create the basic IP configuration files

z Create the ISPF configuration table keyword file andload module

z Perform additional tasks for Parallel Sysplexconfiguration, such as setting up the system logger

z Set up a base sysplex

w As of z/OS V1R3 and z/OS.e V1R3:

z You can use msys for Setup to set limits on your UNIXsystem resources, such as the maximum number ofuser IDs that can be concurrent at one time and themaximum number of processes that the system will runat one time. These settings are stored in the z/OS UNIXparmlib member BPXPRMxx. The system will doself-discovery and prime with the values that yoursystem already has, and you can use msys for Setupproperty sheets to do any ongoing customization ofBPXPRMxx.

z You can use msys for Setup to configure the defaultsystem-wide run-time options for LanguageEnvironment. msys for Setup builds the necessaryconfiguration files, through an easy-to-use dialog andaccompanying help text, which you then put intoproduction. In addition, you can use msys for Setup tocreate the region-wide run-time options for both CICSand IMS regions.

w As of z/OS V1R4 and z/OS.e V1R4, Communications Server(IP Services) extends its usage of msys for Setup to portreservation and definition of TN3270 servers.

w As of z/OS V1R5 and z/OS.e V1R5:

z msys for Setup allows you to configure RMF.

z If PTFs UA90013 and UA90015 are installed on z/OSV1R4 or later, IBM Directory Server V5R1 (with FixPack1) is supported on the workstation as an alternative tothe LDAP server on the host.



Type: optional feature, exclusive, priced, can be dynamicallyenabled. Security Server lets you control access to protected resources.

z/OS V1R7 Security Server

Type: optional feature, exclusive, priced, can be dynamicallyenabled. System Display and Search Facility (SDSF) provides you withinformation to monitor, manage, and control your z/OS or z/OS.esystem. Although prior levels of JES2 may be used with z/OS V1R7, priorlevels of SDSF may not. In z/OS.e, BookManager help is not available for SDSF SYSLOGmessages. This is because BookManager READ is not available inz/OS.e.

z/OS V1R7 SDSF

Type: base element, exclusive. Run-Time Library Extensions, introduced in z/OS V1R5 and z/OS.eV1R5, extends the run-time support provided by the LanguageEnvironment base element. It consists of :

w Common Debug Architecture (CDA) libraries and utilities.

w UNIX System Laboratories (USL) I/O Stream Library and USLComplex Mathematics Library, previously included in the baseelement C/C++ IBM Open Class Library.

w IBM Open Class dynamic link libraries (DLLs), previouslyincluded in the base element C/C++ IBM Open Class Library.

z/OS V1R7 Run-Time LibraryExtensions

Type: optional feature, exclusive, priced, can be dynamicallyenabled. Resource Measurement Facility (RMF) gathers data about z/OS andz/OS.e resource usage and provides reports at any system in asysplex. As of z/OS V1R5 and z/OS.e V1R5, an RMF msys plug-in isavailable that allows you to configure RMF from msys for Setup. Theplug-in guides you through customization and migration tasks andensures correct and consistent RMF parmlib members. You cancustomize a new z/OS or z/OS.e RMF installation, modify an existingone, or migrate from previous releases of RMF.

z/OS V1R7 RMF

Type: base element, exclusive. Open Systems Adapter/Support Facility (OSA/SF) provides auser-friendly interface for monitoring and controlling the zSeriesOpen Systems Adapter feature, which provides zSeries networkconnectivity directly to local area networks (LANs) and wide areanetworks (WANs) that support IP and SNA protocols. OSA/SFsupports Gigabit, Token Ring, Fast Ethernet, 1000Base-T Ethernet,10 Gigabit Ethernet, and ATM features depending on the processoron which z/OS runs. For details, see zSeries OSA-ExpressCustomer's Guide and Reference, SA22-7935. OSA/SF was last changed in the z/OS V1R4 z990 CompatibilitySupport feature. This level was carried forward to the z/OS V1R4z990 Exploitation Support feature and then to z/OS V1R5, z/OSV1R6, and z/OS V1R7. OSA/SF became exclusive with the introduction of the z/OS V1R4z990 Compatibility Support feature.

z/OS V1R4 z990Compatibility Supportfeature

OSA/SF

Network File System uses the Network Authentication Servicecomponent of Integrated Security Services for encryption. Network File System is always enabled, even when the alternatebase configuration is ordered.



Type: optional feature, exclusive, unpriced, cannot be dynamicallyenabled. z/OS Security Level 3 provides strong encryption for z/OS andz/OS.e. The components in this feature are:

w LDAP Security Level 3, new in z/OS V1R6 and z/OS.e V1R6. This component works in conjunction with the LDAP Servercomponent of the Integrated Security Services base elementto provide stronger encryption (greater than 64 bits) than thatavailable without the z/OS Security Level 3 feature. Thiscomponent uses the TDES and RC4 algorithms for encryption.

w Network Authentication Service Level 3, last changed in z/OSV1R6 and z/OS.e V1R6. This component works in

z/OS V1R6 z/OS Security Level 3

Type: base element, exclusive. Time Sharing Option/Extensions (TSO/E) provides an interactiveterminal interface. As in prior releases of TSO/E, this elementincludes CLISTs and REXX, but does not include a REXX compiler. In z/OS.e, the number of concurrent TSO/E sessions is limited toeight.

z/OS V1R6 TSO/E

Type: base element, exclusive. TIOC allows console services and TSO/E to communicate with theterminal hardware.

OS/390 V1R1 TIOC

Type: base element, nonexclusive. SMP/E is a tool for installing and maintaining software, and formanaging the inventory of software that has been installed. Prior to z/OS V1R2, SMP/E was an exclusive base element.Beginning with z/OS V1R2, SMP/E is nonexclusive because of theintroduction of the SMP/E product. The SMP/E product allowscustomers who are currently licensed for an earlier level of z/OS orz/OS.e to order and install the latest level of SMP/E without having toupgrade their entire operating system. This allows products that runon z/OS or z/OS.e to exploit the packaging and installationenhancements of SMP/E without requiring a later level of theoperating system. This also allows customers to exploit newelectronic 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 ofSMP/E, can help you maintain, plan for, and order new releases ofz/OS, z/OS.e, and other products. It provides reports that useIBM-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/.

z/OS V1R7 (SMP/E for z/OS V3R4,5655-G44)

SMP/E

Security Server now consists of one component, RACF. In z/OSV1R5, its other components were moved to two base elements,Integrated Security Services (which was new in V1R5) andCryptographic Services. The base element Integrated SecurityServices received the five components DCE Security Server, FirewallTechnologies, LDAP Server, Network Authentication Service, andOCEP. The base element Cryptographic Services received thecomponent PKI Services. Security Server uses the limited DES, CDM, and RC 40-bitalgorithms for encryption.



Type: base element, nonexclusive. 3270 PC File Transfer Program transfers files from the host to theworkstation for offline data manipulation, updating, or correction or forthe transfer and storage of local data in the host system.

OS/390 V1R2 (3270 PC File TransferProgram V1R1.1,5665-311)

3270 PC File TransferProgram

Type: base element, exclusive. z/OS UNIX System Services (z/OS UNIX) provides the standardcommand interface familiar to interactive UNIX users. This element ismade up of four components:

w Application Services, last changed in z/OS V1R7 and z/OS.eV1R7. This component includes the Shell, Utilities, Debugger,and Parallel Environment.

w Connection Manager, last changed in OS/390 V2R7.

w Integrated Call Level Interface (ICLI), last changed in z/OSV1R6 and z/OS.e V1R6.

w Process Manager, last changed in OS/390 V2R7.

z/OS V1R7 z/OS UNIX

conjunction with the Network Authentication Servicecomponent of the Integrated Security Services base elementto provide stronger encryption (greater than 64 bits) than thatavailable without the z/OS Security Level 3 feature. Thiscomponent uses the TDES algorithm for encryption. This component was new in z/OS V1R2. At that time it wasnamed SecureWay Security Server Network AuthenticationService Level 3. As of z/OS V1R3 and z/OS.e V1R3, the word"SecureWay" was dropped from the name. As of z/OS V1R5and z/OS.e V1R5, the words "Security Server" are droppedfrom the name.

w OCSF Security Level 3, last changed in OS/390 V2R10. Thiscomponent works in conjunction with the OCSF component ofthe Cryptographic Services base element to provide strongerencryption (greater than 64 bits) than that available without thez/OS Security Level 3 feature. This component uses theTDES, DES, and RC2/RC4/RC5 algorithms for encryption.

w System Secure Sockets Layer (SSL) Security Level 3, lastchanged in z/OS V1R6 and z/OS.e V1R6. This componentworks in conjunction with the System SSL component of theCryptographic Services base element to provide strongerencryption (greater than 64 bits) than that available without thez/OS Security Level 3 feature. This component uses theRC2/RC4, TDES, and Advanced Encryption Standard (AES)algorithms for encryption.

Prior to z/OS V1R5, three of the components in z/OS Security Level3 were separate features. In z/OS V1R5 they were repackaged, forthe purpose of simplifying ordering, into the new feature z/OSSecurity Level 3. The three components are Network AuthenticationService Level 3, OCSF Security Level 3, and System SSL SecurityLevel 3. This feature is worldwide exportable subject to U.S. exportregulations.



Appendix B: Coexistence Service for z/OS V1.7Coexistence and fallback PTFs installed on back-level systems allow those systems to coexist with z/OS V1R7 systemsduring your migration, and allow backout from z/OS V1R7 to the back-level systems if necessary. Coexistence andfallback are important because they allow you to migrate systems in a multisystem configuration to z/OS V1R7 usingrolling IPLs (one system at a time), allowing for continuous application availability.

Depending on which back-level releases your z/OS V1R7 system is coexisting with, install the coexistence and fallbackPTFs that are listed in the following tables. The first table is for coexistence and fallback service on z/OS V1R5 for z/OSV1R7. The second table is for coexistence and fallback service on z/OS V1R6 for z/OS V1R7. (For coexistence andfallback service on z/OS V1R4 for z/OS V1R7, see the body of this presentation.)

Table 2. Coexistence and fallback PTFs needed on z/OS V1R5Apply on z/OS V1R5, the coexistence and fallback service (PTFs) listed in this table:

UA09967 BCP: Starting in z/OS V1R6, the sysplex couple data set (CDS) can be expanded to allowup to 2047 members in a cross-system coupling facility (XCF) group. This is an increase

UA09403, UA09425 BCP: Allows a z/OS V1R5 system to tolerate new resource recovery services (RRS)restart function in z/OS V1R6 (and later).

UA18541


UA09226 BCP: z/OS V1R6 has a new 64-bit global resource serialization (GRS) ISGQUERYapplication programming interface (API). The PTF allows a z/OS V1R5 system to tolerateISGQUERY requests from a z/OS V1R6 or later system.

UA07361

BCP: APARs OA05025 (PTF UA07361) and OA05391 together provide corrective servicefor XCF recovery from partial writes to couple data sets. APAR OA05391 introduces a newformat for couple data set multi-subrecord check records (MSRCRs), which is required forrecovery from partial writes to certain types of couple data set records. APAR OA05025includes coexistence support that enables systems on which it is installed to interpret thenew MSRCR format. Because both APARs have been incorporated into z/OS V1R6 and later, all other systemsin the sysplex must be capable of interpreting the new MSRCR format before any V1R6 orlater system can be IPLed into the sysplex. V1R5 systems include support for interpretingthe new MSRCR format and do not require installation of additional maintenance toprovide this capability. You must IPL all other systems in the sysplex with the appropriatePTF for APAR OA05025 (PTF UA07361 for V1R5) before IPLing any V1R6 or later systeminto the sysplex. Rolling IPLs are sufficient to install the PTFs for APARs OA05025 andOA05391. Note that the recovery provided by these two PTFs is not completely effectiveuntil all systems in the sysplex, including z/OS V1R5 systems, have been IPLed with bothPTFs or with V1R6 or later.

UA09964 BCP: Allows a z/OS V1R5 system to correctly handle blank WTOs issued to anothersystem.

UA16512

BCP: Increased CPU utilization in the console address space might be reported on allsystems in a sysplex after introducing a z/OS V1R4 system with the z/OS V1R4 ConsolesEnhancements feature, or later-level system, into the sysplex. The coexistence PTFprevents heavy message traffic on the z/OS V1R7 system from impacting the othersystems in the sysplex.

UA07960, UA07963 BCP: Prevents the depletion of private storage in the console address space on areceiving system when a large number of WTO/R messages are received on that systemfrom other members of a sysplex.

UA05643, UA06655 BCP: In z/OS V1R5, a console enhancement minimizes the possibility of outages due toexhaustion of system resources used for messaging. The PTFs allow back-level systemsto tolerate the enhancement.




UA16797, UA16952


UA16797

DFSMSdss: z/OS V1R7 supports large format sequential data sets. These PTFs causepre-z/OS V1R7 systems to issue ABEND213-14 for any large format dump data sets thatare provided as input to RESTORE or COPYDUMP, or output for DUMP andCOPYDUMP. If DFSMSdss encounters any large format sequential data sets as input tological 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.


UA16634, UA16923,UA17235

DFSMSdfp: z/OS V1R7 supports new QNAME and RNAME parameters for VSAM RLS.The coexistence PTFs prevent serialization problems from occurring when the newparameters are used in a GRS complex that includes a pre-z/OS V1R7 system.

UA14883, UA16224,UA16797

DFSMSdfp: As part of VSAM extent constraint removal in z/OS V1R7, these PTFs preventpre-z/OS V1R7 systems from opening data sets that have more than 255 extents. Also, ifa data set is open and a z/OS V1R7 job extends it past 255 extents, the close on thepre-z/OS V1R7 system fails. Finally, these PTFs prevent conversion of a data set havingmore than 255 extents from being converted by DFSMSdss to a non-SMS managed dataset on pre-z/OS V1R7 releases.

UA16995


UA09833 DFSMSdfp: z/OS V1R6 has a new PDSE address space, SMSPDSE1, which isrestartable. The coexistence PTF allows a z/OS V1R5 system to coexist with a z/OS V1R6or later system that is exploiting the new address space.

UA90101, UA90113,UA90121, UA90127,UA90129

BCP, DFSMSdfp, DFSMSdss, DFSMShsm, DFSMSrmm: In z/OS V1R6, a new functionintroduced by PTF UA90124 enables DFSMS software support for IBM TotalStorageEnterprise 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 systemthat uses this function.

UA18498


UA17027 BCP: Allows a pre-z/OS V1R7 system to use an IODF that was created using z/OS V1R7HCD.

UA17178


UA16038 BCP: A z/OS V1R7 system cannot join a sysplex of lower-level systems, and a lower-levelsystem cannot join a sysplex of z/OS V1R7 systems, without this PTF.

from the previous maximum of 1023 members per XCF group. Formatting a couple dataset 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 supportfor Version 4 sysplex CDSs on z/OS V1R5. This is important because all systems in asysplex 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 supportVersion 4 sysplex CDSs cannot join the sysplex.



UQ85892 Language Environment: The /etc/utmpx file contains a user accounting database. In z/OS

z/OS V1R4 JES3:UA04010, UA07715

JES3: Allows a back-level JES3 to run with z/OS V1R7 JES3 in a multisystem complex.Apply the PTFs that are appropriate to the JES3 level that you are using.

z/OS V1R5-V1R6 JES2:UA16217, UA20902

z/OS V1R4 JES2:UA16216, UA20901

JES2: Fixes a problem on a receiving pre-z/OS V1R7 node that can occur in a raresituation with a large scheduler work block text unit (SWBTU). Data sets have a largeSWBTU when MAILTO, MAILCC, and MAILBCC keywords are used in addition to otherkeywords on OUTPUT JCL statements. The problem is caused by APAR OA09152 (PTFUA16214 on z/OS V1R5-V1R6 JES2 or PTF UA16213 on z/OS V1R4 JES). This is anetwork-specific problem, not a MAS-specific problem.

z/OS V1R5-V1R6 JES2:UA09501, UA90161; z/OSV1R4 JES2: UA03828,UA09500, UA90160

JES2: Allows a back-level JES2 to run with z/OS V1R7 JES2 in a multi-access spool(MAS). Apply the PTFs that are appropriate to the JES2 level that you are using.



UA19929ISPF: Allows pre-z/OS V1R7 systems to intelligently display the number of tracks in a large formatsequential data set. If the number of tracks is greater than 64 KB, the string “>64K” and a largerexplanatory message are written to the panel.

UA90174 and UA90175 HCD: Provides support for HCD users who share IODF data sets between pre-z/OS V1R7systems and z/OS V1R7 systems.



UA16948

DFSMShsm: z/OS V1R7 increases the number of data set names supported in a tapetable of contents (TTOC). If a system that has the coexistence PTF installed finds that theOCDS RECORDSIZE is 6144 bytes, which indicates that some instances of DFSMShsmin the HSMplex might be using the extended TTOC, then tape operations on that level ofDFSMShsm are inhibited.

UA16850, UA16858,UA16861, UA16945

DFSMShsm: z/OS V1R7 supports fast subsequent migration (FSM) of data sets. ThePTFs cause DFSMShsm to set the appropriate flags during recall processing so that if thedata set is later opened for output by either z/OS V1R7 systems or pre-z/OS V1R7systems, the flags used for reconnection determination are set appropriately.

UA09619 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 SSMmultitasking.

UA07443

DFSMShsm: In z/OS V1R5, DFSMShsm is enhanced to use volume-level fast replicationto create backup versions for sets of storage groups. A set of storage groups is definedthrough an SMS construct termed "copy pool". In support of fast replication, install the PTFon all z/OS V1R5 systems in a sysplex.

UA15870, UA16551,UA16955

DFSMShsm: z/OS V1R7 supports large format sequential data sets. In an HSMplex withmore than one DFSMShsm host, take care when migrating the journal to a large formatsequential data set. All DFSMShsm hosts within an HSMplex must be at z/OS V1R7before 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 thejournal is a standard format data set, DFSMShsm initialization continues. If the journal is alarge format data set, message MSGARC0509E with the "LARGE" text in the message isissued and DFSMShsm is stopped. If the journal is a striped data set, messageMSGARC0509E with the "STRIPED" text in the message is issued and DFSMShsm isstopped. If the ARCBJRNL utility attempts to use a large format journal data set, it isended with return code RC40, which indicates an OPEN error.




UR54451, UR54454 (ifJapanese)

SMP/E: Allows back-level SMP/E to tolerate enhancements introduced in z/OS V1R6SMP/E (which is equivalent to SMP/E V3R3).

UA19507 NFS: Allows a pre-z/OS V1R7 NFS server to read a mount handle data set written by NFSV1R7.


V1R6, the format of the records in the file was extended to support longer remote hostnames, 64-bit timestamp structures, and a version indicator. The coexistence PTFprevents the standard interfaces in pre-V1R6 releases from accessing /etc/utmpxdatabases 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 returna null pointer. Applications can use perror() to print the error message.

Table 3. Coexistence and fallback PTFs needed on z/OS V1R6Apply, on z/OS V1R6, the coexistence and fallback service (PTFs) listed in this table:.

UA16635, UA16924,UA17236

DFSMSdfp: z/OS V1R7 supports new QNAME and RNAME parameters for VSAM RLS.

UA14884, UA16225,UA16798

DFSMSdfp: As part of VSAM extent constraint removal in z/OS V1R7, these PTFs preventpre-z/OS V1R7 systems from opening data sets that have more than 255 extents. Also, if adata set is open and a z/OS V1R7 job extends it past 255 extents, the close on thepre-z/OS V1R7 system fails. Finally, these PTFs prevent conversion of a data set havingmore than 255 extents from being converted by DFSMSdss to a non-SMS managed dataset on pre-z/OS V1R7 releases.

UA16996


UA18499


UA09962 BCP: Allows a z/OS R6 system to correctly handle blank WTOs issued to another system.

UA16510

BCP: Increased CPU utilization in the console address space might be reported on allsystems in a sysplex after introducing a z/OS V1R4 system with the z/OS V1R4 ConsolesEnhancements feature, or later-level system, into the sysplex. The coexistence PTFprevents heavy message traffic on the z/OS V1R7 system from impacting the othersystems in the sysplex.

UA18542


UA17028 BCP: Allows a pre-z/OS R7 system to use an IODF that was created using z/OS R7 HCD.

UA17179


UA16036 BCP: A z/OS V1R7 system cannot join a sysplex of lower-level systems, and a lower-levelsystem cannot join a sysplex of z/OS V1R7 systems, without this PTF.




z/OS V1R5-V1R6 JES2:JES2: Fixes a problem on a receiving pre-z/OS V1R7 node that can occur in a rare

z/OS V1R5-V1R6 JES2:UA09501, UA90161; z/OSV1R4 JES2: UA03828,UA09500, UA90160

JES2: Allows a back-level JES2 to run with z/OS V1R7 JES2 in a multi-access spool(MAS). Apply the PTFs that are appropriate to the JES2 level that you are using.



UA19930ISPF: Allows pre-z/OS V1R7 systems to intelligently display the number of tracks in a large formatsequential data set. If the number of tracks is greater than 64 KB, the string “>64K” and a largerexplanatory message are written to the panel.

UA90174 and UA90175HCD: Provides support for HCD users who share IODF data sets between pre-z/OS V1R7systems and z/OS V1R7 systems.



UA16949

DFSMShsm: z/OS V1R7 increases the number of data set names supported in a tapetable of contents (TTOC). If a system that has the coexistence PTF installed finds that theOCDS RECORDSIZE is 6144 bytes, which indicates that some instances of DFSMShsm inthe HSMplex might be using the extended TTOC, then tape operations on that level ofDFSMShsm are inhibited.

UA16851, UA16859,UA16862, UA16946

DFSMShsm: z/OS V1R7 supports fast subsequent migration (FSM) of data sets. The PTFscause DFSMShsm to set the appropriate flags during recall processing so that if the dataset is later opened for output by either z/OS V1R7 systems or pre-z/OS V1R7 systems, theflags used for reconnection determination are set appropriately.

UA15871, UA16552,UA16956

DFSMShsm: z/OS V1R7 supports large format sequential data sets. In an HSMplex withmore than one DFSMShsm host, take care when migrating the journal to a large formatsequential data set. All DFSMShsm hosts within an HSMplex must be at z/OS V1R7before 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 thejournal is a standard format data set, DFSMShsm initialization continues. If the journal is alarge format data set, message MSGARC0509E with the "LARGE" text in the message isissued and DFSMShsm is stopped. If the journal is a striped data set, messageMSGARC0509E with the "STRIPED" text in the message is issued and DFSMShsm isstopped. If the ARCBJRNL utility attempts to use a large format journal data set, it is endedwith return code RC40, which indicates an OPEN error.

UA16798, UA16953


UA16798

DFSMSdss: z/OS V1R7 supports large format sequential data sets. These PTFs causepre-z/OS V1R7 systems to issue ABEND213-14 for any large format dump data sets thatare provided as input to RESTORE or COPYDUMP, or output for DUMP and COPYDUMP.If DFSMSdss encounters any large format sequential data sets as input to logical data setCOPY, logical and physical data set DUMP and RESTORE, data set print, or logical andphysical data set RELEASE, the data set will fail with ADR878E rsn 17.


The coexistence PTFs prevent serialization problems from occurring when the newparameters are used in a GRS complex that includes a pre-z/OS V1R7 system.




UA19507 NFS: Allows a pre-z/OS R7 NFS server to read a mount handle ds written by NFS R7.


z/OS V1R4 JES3:UA04010, UA07715

JES3: Allows a back-level JES3 to run with z/OS V1R7 JES3 in a multisystem complex.Apply the PTFs that are appropriate to the JES3 level that you are using.

UA16217; z/OS V1R4JES2: UA16216

situation with a large scheduler work block text unit (SWBTU). Data sets have a largeSWBTU when MAILTO, MAILCC, and MAILBCC keywords are used in addition to otherkeywords on OUTPUT JCL statements. The problem is caused by APAR OA09152 (PTFUA16214 on z/OS V1R5-V1R6 JES2 or PTF UA16213 on z/OS V1R4 JES). This is anetwork-specific problem, not a MAS-specific problem.



Date post:	25-Oct-2015
Category:	Documents
Upload:	pradeepgowda89
View:	33 times
Download:	2 times