Migrating to zOS R8 Part 1 - Messmer The Brain House

More documents

Recommendations

Info

JES2: Allows an earlier JES2 to run with z/OS V1R8 JES2 in a multi-access spool (MAS). Install the PTFs that are appropriate to the JES2 level that you are using. JES2: Fixes a problem on a receiving pre-z/OS V1R7 node that can occur in a rare situation with a large scheduler work block text unit (SWBTU). Data sets have a large SWBTU when MAILTO, MAILCC, and MAILBCC keywords are used in addition to other keywords on OUTPUT JCL statements. The problem is caused by APAR OA09152 (PTF UA16214 on z/OS V1R5-V1R6 JES2 or PTF UA16213 on z/OS V1R4 JES). This is a network-specific problem, not a MAS-specific problem. JES3: Allows a pre-z/OS V1R8 JES3 to tolerate the removal of various symbols from the IHAWQE macro, which was done as part of the console improvements made in z/OS V1R8. Language Environment: Causes a meaningful message to be issued when a new z/OS V1R8 Language Environment run-time option is encountered by an earlier release. The message states that the option is ignored. If the PTF is not installed, the option is still ignored but a less meaningful message, or no message at all, is issued. NFS: Allows a z/OS V1R7 system to read the new NFS export file format generated by a z/OS V1R8 system. NFS: Allows a pre-z/OS V1R7 NFS SMF report generator to process an SMF file that includes NFS V1R7 or later SMF records. Any records containing TCP/IP version 6 IP addresses will be ignored. NFS: Allows a pre-z/OS V1R7 NFS server to read a mount handle data set written by z/OS V1R7 or later NFS. RMF: Ensures the toleration of new z/OS V1R8 functionality for sysplex-wide RMF reporting in earlier releases. Security Server: In z/OS V1R8, the structure of the RACF database was changed to allow a template block to be continued into another block. The PTF allows a z/OS V1R6 system to process templates that extend into another block. If you share a RACF database between z/OS V1R8 and z/OS V1R6, you need to install the PTF on the z/OS V1R6 system. SMP/E: Provides support for SMP/E users who share SMPCSI data sets between pre-z/OS V1R7 systems and z/OS V1R7 or later systems. z/OS V1R5 coexistence and fallback PTFs Install, on z/OS V1R5, the coexistence and fallback PTFs listed below. Element or feature, and function provided by PTFs Migrating to z/OS R8 Part 1 of 3: Get Ready UA19944 (German), UA19945 (uppercase English) z/OS V1R5-V1R6 JES2: UA09501, UA18836, UA20902, UA90161, UA24983 z/OS V1R5-V1R6 JES2: UA16217 z/OS V1R5-V1R6 JES3: UA24989 UK12451 UA25098 UA16683 UA19507 UA26131 UA24979 UO00116 BCP: Ensures that pre-z/OS V1R8 systems tolerate the new format of the z/OS V1R8 WLM service definition and service policy in the WLM couple data set. Moreover, the PTF ensures the toleration of changed WLM LPAR management and JES initiator management information that is exchanged in a mixed-release (z/OS V1R8 and pre-z/OS V1R8) sysplex. If the WLM service policy in the couple data set has been activated by a z/OS V1R8 system, a pre-z/OS V1R8 system without the PTF will not be able to activate the policy and might fail during IPL with a wait state 064. If LPAR management is being used in a mixed-release sysplex and the PTF is not installed, you might experience abends and see message IWM054I FAILURE IN LPAR CPU MANAGEMENT, PROCESSING DISABLED. BCP: In z/OS V1R8, SYSIN DD * override statements are no longer required to reside in the job stream in the same order as the corresponding DD statements appear in the procedure. Because new text units are introduced for each SYSIN DD * statement, the PTF allows jobs to ignore the new text units when they run in a JES2 environment and convert on a z/OS V1R8 system but interpret on an earlier system. z/OS V1R5 PTFs UA90267 UA24558 SHARE (c) Copyright IBM Corporation, 2006 August 15, 2006 Session 2870 Page 66 of 70 Baltimore, MD
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
Page 1 and 2:
Migrating to z/OS R8 Part 1 of 3: G
Page 3 and 4:
Page 5 and 6:
BCP Migrating to z/OS R8 Part 1 of
Page 7 and 8:
Page 9 and 10:
Page 11 and 12:
Page 13 and 14:
Page 15 and 16: Migrating to z/OS R8 Part 1 of 3: G
Page 27 and 28: � Support for Java application pr
Page 33 and 34: R9 R10 R9, R8, R7 R10, R9, R8 Migra
Page 39 and 40: generic name for these resources).
Page 43 and 44: Choosing IBM Products That You Want
Page 51 and 52: Appendix A: List of Base Elements a
Page 53 and 54: Communications Server Security Leve
Page 55 and 56: EREP ESCON (R) Director Support FFS
Page 57 and 58: Integrated Security Services z/OS V
Page 59 and 60: Library Server MICR/OCR (z/OS only)
Page 61 and 62: TIOC TSO/E z/OS Security Level 3 OS
Page 63 and 64: Appendix B: Coexistence Service for
Page 65: Migrating to z/OS R8 Part 1 of 3: G
show all

Migrating to zOS R8 Part 1 - Messmer The Brain House

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?