Migrating to zOS R8 Part 1 - Messmer The Brain House

Migrating to z/OS R8 Part 1 of 3: Get Ready
BCP: If an application developer compiles or assembles with the z/OS V1R8 program management
binder version 6 API invocation macros, or codes to the new STARTD API interface, and the resulting
program is run on an earlier release of z/OS, the binder STARTD API will fail with return code 12,
invalid parameter list, message IEW2132S 0064 INCORRECT NUMBER OF PARAMETERS PASSED
FOR CALL. The PTF allows such a calling program to execute successfully.
BCP: If an application developer uses the z/OS V1R8 program management binder to create a program
object with the latest format in a PDSE, the PTF is needed so that an ISPF user can browse the PDSE on
z/OS V1R5.
BCP: In z/OS V1R8, the console restructure enhancement eliminates the master console and the
console switch function. The PTF allows earlier systems to tolerate the enhancement.
BCP: In z/OS V1R5, a console enhancement minimizes the possibility of outages because of
exhaustion of system resources used for messaging. The PTFs allow earlier systems to tolerate the
enhancement.
BCP: Prevents the depletion of private storage in the console address space on a receiving system when
a large number of WTO/R messages are received on that system from other members of a sysplex.
BCP: Increased CPU utilization in the console address space might be reported on all systems in a
sysplex after introducing a z/OS V1R4 system with the z/OS V1R4 Consoles Enhancements feature, or
later-level system, into the sysplex. The coexistence PTF prevents heavy message traffic on the z/OS
V1R7 or later system from impacting the other systems in the sysplex.
BCP: Allows a z/OS V1R5 system to correctly handle blank WTOs issued to another system.
BCP: APARs OA05025 (PTF UA07361) and OA05391 together provide corrective service for XCF
recovery from partial writes to couple data sets. APAR OA05391 introduces a new format for couple
data set multi-subrecord check records (MSRCRs), which is required for recovery from partial writes to
certain types of couple data set records. APAR OA05025 includes coexistence support that enables
systems on which it is installed to interpret the new MSRCR format.
Because both APARs have been incorporated into z/OS V1R6 and later, all other systems in the sysplex
must be capable of interpreting the new MSRCR format before any V1R6 or later system can be IPLed
into the sysplex. V1R5 systems include support for interpreting the new MSRCR format and do not
require installation of additional maintenance to provide this capability. You must IPL all other systems
in the sysplex with the appropriate PTF for APAR OA05025 (PTF UA07361 for V1R5) before IPLing
any V1R6 or later system into the sysplex. Rolling IPLs are sufficient to install the PTFs for APARs
OA05025 and OA05391. Note that the recovery provided by these two PTFs is not completely effective
until all systems in the sysplex, including z/OS V1R5 systems, have been IPLed with both PTFs or with
V1R6 or later.
BCP: z/OS V1R6 has a new 64-bit global resource serialization ISGQUERY application programming
interface (API). The PTF allows a z/OS V1R5 system to tolerate ISGQUERY requests from a z/OS
V1R6 or later system.
BCP: Provides compatibility support for the corrected global resource serialization ISGLOCK structure
rebuild processing in z/OS V1R7 APAR OA11147 (and rolled into z/OS V1R8).
BCP: Allows a z/OS V1R5 system to tolerate changes made to resource recovery services (RRS)
display and ATRQUERY functions in z/OS V1R8.
BCP: Allows a z/OS V1R5 system to tolerate new resource recovery services (RRS) restart function in
z/OS V1R6 (and later).
BCP: Starting in z/OS V1R6, the sysplex couple data set (CDS) can be expanded to allow up to 2047
members in a cross-system coupling facility (XCF) group. This is an increase from the previous
maximum of 1023 members per XCF group. Formatting a couple data set for more than 1023 members
per group creates a Version 4 CDS.
The PTF rolls back this function to z/OS V1R5. In terms of coexistence, it provides support for Version
4 sysplex CDSs on z/OS V1R5. This is important because all systems in a sysplex must support Version
4 sysplex CDSs to bring a Version 4 sysplex CDS into use, and once a sysplex is using a Version 4
sysplex CDS, a system that does not support Version 4 sysplex CDSs cannot join the sysplex.
BCP: A z/OS V1R7 or later system cannot join a sysplex of earlier-level systems, and an earlier-level
system cannot join a sysplex of z/OS V1R7 or later systems, without this PTF.
UA24435
UA25782
UA26404 and, if
Japanese, UA26401
UA05643, UA06655
UA07960, UA07963
UA16512
UA09964
UA07361
UA09226
UA18541
UA27070
UA09403, UA09425
UA09967
UA16038
SHARE (c) Copyright IBM Corporation, 2006 August 15, 2006
Session 2870 Page 67 of 70 Baltimore, MD