Migrating to zOS R8 Part 1 - Messmer The Brain House

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