Migrating to zOS R8 Part 1 - Messmer The Brain House

More documents

Recommendations

Info

Migrating to z/OS R8 Part 1 of 3: Get Ready Enhancements feature, or later-level system, into the sysplex. The coexistence PTF prevents heavy message traffic on the z/OS V1R7 or later system from impacting the other systems in the sysplex. BCP: Allows a z/OS V1R6 system to correctly handle blank WTOs issued to another system. BCP: Large format sequential data sets are only supported by z/OS V1R7 and later. The coexistence PTF causes z/OS to detect the accidental specification of such a data set for stand-alone dump output and to reject its use, as has been done for data set organizations such as PDS. BCP: Provides compatibility support for the corrected global resource serialization ISGLOCK structure rebuild processing in z/OS V1R7 APAR OA11147 (and rolled into z/OS V1R8). BCP: Allows a z/OS V1R6 system to tolerate changes made to resource recovery services (RRS) display and ATRQUERY functions in z/OS V1R8. DFSMSdfp: Program object format 5 (PO5 format) is new in z/OS V1R8. The PTF allows PDSE program libraries that contain PO5 program objects to be processed by IEBCOPY on z/OS V1R6 systems. DFSMSdfp: An enhancement in the z/OS V1R8 object access method (OAM) component introduced a new ODLOBFL column in the object directory to exploit DB2 binary large object (BLOB) support. The PTF enables pre-z/OS V1R8 OAMs to coexist in an OAMplex with OAMs at the z/OS V1R8 or later level. DFSMSdfp: An enhancement in the z/OS V1R7 object access method (OAM) component introduced a new valid value ("R") for the object location in the object directory to indicate that the object resides on DB2 disk in recalled status. This PTF enables pre-z/OS V1R7 OAMs to coexist in an OAMplex with OAMs at the z/OS V1R7 or later level. DFSMSdfp: As part of VSAM extent constraint removal in z/OS V1R7, these PTFs prevent pre-z/OS V1R7 systems from opening data sets that have more than 255 extents. Also, if a data set is open and a z/OS V1R7 or later job extends it past 255 extents, the close on the pre-z/OS V1R7 system fails. Finally, these PTFs prevent conversion of a data set having more than 255 extents from being converted by DFSMSdss to a non-SMS managed data set on pre-z/OS V1R7 releases. DFSMSdfp: z/OS V1R7 introduced new QNAME and RNAME parameters for VSAM RLS. The coexistence PTFs prevent serialization problems from occurring when the new parameters are used in a global resource serialization complex that includes a pre-z/OS V1R7 system. DFSMSdfp: In z/OS V1R8, the D SMS,SMSVSAM,DIAG(CONTENTION) command is introduced to display internal VSAM RLS contention. The PTF allows a z/OS V1R6 system that receives the new DIAG CONTENTION command to tolerate the command by issuing a message analogous to IGW495I D SMS,SMSVSAM,DIAG COMMAND FUNCTION HAS FOUND THE DIAG TABLE HAS NO ENTRIES. If the PTF is not installed, the z/OS V1R6 system receiving the new command treats it as an irrelevant and confusing console message. DFSMSdfp: In z/OS V1R8, a performance improvement to VSAM RLS causes XES lock table cleanup to be skipped when the SMSVSAM address space is terminated, as documented in APAR OA11708. This PTF allows a z/OS V1R6 system to tolerate the enhancement. DFSMSdfp: z/OS V1R7 and later support large format sequential data sets. These PTFs cause pre-z/OS V1R7 systems to issue ABEND 213-14 or 213-16 if a program attempts to open data sets that cannot work on those systems. DFSMSdss: z/OS V1R7 and later support large format sequential data sets. These PTFs cause pre-z/OS V1R7 systems to issue ABEND213-14 for any large format dump data sets that are provided as input to RESTORE or COPYDUMP, or output for DUMP and UA09962 UA19042 UA18542 UA27071 UA22350 UA24412 UA16996 UA14884, UA16225, UA16798 UA16635, UA16924, UA17236 UA24373 UA21541 UA15871, UA16552, UA18496 UA16798 SHARE (c) Copyright IBM Corporation, 2006 August 15, 2006 Session 2870 Page 64 of 70 Baltimore, MD
Migrating to z/OS R8 Part 1 of 3: Get Ready COPYDUMP. If DFSMSdss encounters any large format sequential data sets as input to logical data set COPY, logical and physical data set DUMP and RESTORE, data set print, or logical and physical data set RELEASE, the data set will fail with ADR878E rsn 17. DFSMShsm: Allows a z/OS V1R6 system to tolerate the changes made by the fast replication tape support enhancement in z/OS V1R8. DFSMShsm: In z/OS V1R8, dump volume (DVL) and dump class (DCL) control data set records were enlarged as part of the DFSMShsm dump encryption enhancement. The PTF allows a z/OS V1R6 system to tolerate the increase in record size. DFSMShsm: z/OS V1R7 and later support large format sequential data sets. The PTFs cause pre-z/OS V1R7 systems that might potentially recall, recover, or ARECOVER a data set to first verify that the data set is not a large format data set. If it is, an error message is issued describing the reason for the failure. DFSMShsm: z/OS V1R7 and later support large format sequential data sets. In an HSMplex with more than one DFSMShsm host, take care when migrating the journal to a large format sequential data set. All DFSMShsm hosts within an HSMplex must be at z/OS V1R7 or later before you can migrate the journal to a large format sequential data set. With the PTFs, when a pre-z/OS V1R7 DFSMShsm host attempts to open a journal, if the journal is a standard format data set, DFSMShsm initialization continues. If the journal is a large format data set, message MSGARC0509E with the "LARGE" text in the message is issued and DFSMShsm is stopped. If the journal is a striped data set, message MSGARC0509E with the "STRIPED" text in the message is issued and DFSMShsm is stopped. If the ARCBJRNL utility attempts to use a large format journal data set, it ends with return code RC40, which indicates an OPEN error. DFSMShsm: z/OS V1R7 and later support fast subsequent migration (FSM) of data sets. The PTFs cause DFSMShsm to set the appropriate flags during recall processing so that if the data set is later opened for output by either z/OS V1R7 systems or pre-z/OS V1R7 systems, the flags used for reconnection determination are set appropriately. DFSMShsm: z/OS V1R7 increased the number of data set names supported in a tape table of contents (TTOC). If a system that has the coexistence PTF installed finds that the OCDS RECORDSIZE is 6144 bytes, which indicates that some instances of DFSMShsm in the HSMplex might be using the extended TTOC, then tape operations on that level of DFSMShsm are inhibited. DFSMSrmm: Allows a pre-z/OS V1R8 system in a client/server environment to participate in an RMMplex in which a z/OS V1R8 system has been started. Optionally, you can specify UTC(YES) with the EDGUTIL utility on z/OS V1R8 to enable DFSMSrmm common time support. DFSMSrmm: Allows a pre-z/OS V1R8 system to participate in an RMMplex in which a z/OS V1R8 system has been started. In particular, the PTF enables VRSEL processing to recognize the use of the special ABEND and OPEN vital record specifications and to correctly handle COUNT(0). It also prevents the continued use of the unsupported options STARTNUMBER and LOCATION(BOTH). Distributed File Service: Allows pre-z/OS V1R7 systems to tolerate new characters (@#$) allowed in z/OS V1R7 and later for zFS file systems and aggregates. Distributed File Service: Allows pre-z/OS V1R7 systems to tolerate the file system structure for z/OS V1R7 and later zFS file systems. HCD: Provides support for HCD users who share IODF data sets between pre-z/OS V1R7 systems and z/OS V1R7 or later systems. ISPF: Allows pre-z/OS V1R7 systems to intelligently display the number of tracks in a large format sequential data set. If the number of tracks is greater than 64 KB, the string ">64K" and a larger explanatory message are written to the panel. ISPF: Provides an appropriate message when a user attempts to open a large format sequential data set from a pre-z/OS V1R7 release. UA25404 UA22715 UA16798, UA16953 UA15871, UA16552, UA16956, UA18496 UA16851, UA16859, UA16862, UA16946 UA16949 UA25144 if not using client/server DFSMSrmm, or both UA25144 and UA00009 if using client/server DFSMSrmm UA22044 UA14530 UA20483 UA90174 (base and English), UA90175 (Japanese) UA19930, UA20545 UA19933, UA19942 (Swiss German), UA19943 (Japanese), SHARE (c) Copyright IBM Corporation, 2006 August 15, 2006 Session 2870 Page 65 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: 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: Appendix B: Coexistence Service for
show all

Migrating to zOS R8 Part 1 - Messmer The Brain House

Create successful ePaper yourself

Delete template?

Save as template?