Migrating to zOS R8 Part 1 - Messmer The Brain House

Migrating to z/OS R8 Part 1 of 3: Get Ready
catalogs contain sufficient functional capabilities that all functions that previously could only be performed with
JOBCAT or STEPCAT can now be done without them.
Furthermore, the use of JOBCAT and STEPCAT can actually cause significant problems. Data sets are generally
not cataloged according to the normal predictable search order when JOBCAT or STEPCAT is used. This impacts
the ability to do comprehensive installation storage management and can increase staff requirements. For
example, interval migration and recall using DFSMShsm is effectively unusable when the data sets cannot be
found using the standard catalog search order. The use of JOBCAT and STEPCAT can also result in noticeable
increases 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 has
provided the ISAM Compatibility Interface (ISAM CI) which allows users to run an ISAM program against a VSAM
KSDS data set. Details on using this interface and procedures for converting ISAM data sets to VSAM data sets can
be found in Appendix E of Using Data Sets. This compatibility interface program continues to be provided as part of
DFSMS 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++ compilers
from z/OS R7. The OS/390 R10 C/C++ compilers were shipped as an aid to migration to the C/C++ compilers that
were introduced in z/OS V1R2. The z/OS V1R2 level of the C++ compiler supports the ISO 1998 Standard level of
C++. For information about migrating from the older to the newer level of the compilers, see z/OS C/C++ Compiler
and Run-Time Migration Guide.
� Previously, the CMB= parameter specified the I/O device classes for which measurement data was to be collected, in
addition to the DASD and tape device classes. It also allowed you to specify the number of channel measurement
block (CMB) slots to reserve for adding more devices with an ACTIVATE. As of the z990 Exploitation feature on z/OS
R4, the system ignores the CMB and uses instead the measurement data in the extended channel measurement
block (ECMB). As a migration action since then, you must convert user-written programs that make use of the CMB
to make use of the ECMB, and contact ISVs to obtain updates to ISV programs that use the CMB. The type of
programs especially likely to use the CMB are monitor programs. If ISV support is not available, you could have
specified ECMB=NO in parmlib member IEAOPTxx as a circumvention until the ISV support is available. See APAR
OA06164 for additional details. The ECMB=NO circumvention has been removed in z/OS R7, so have plans in place
to 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 allowed
to specify one-byte console IDs on macros (such as WTO/WTOR), or on such operator commands as D C,CN= or D
PFK,CN= . You should use console names instead. A service called the Console ID Tracking Facility is available to
help you identify one-byte ID usage. The use of console names is already a best practice on OS/390 and z/OS. For
information 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, CONTROL
D,H, and MSGRT TR=A are removed in z/OS R7.
� The z/OS Optional Source media feature is not offered as of z/OS R7. The last release offering these materials was
z/OS R6. These features contain macros and source code for some programs in the z/OS BCP, BDT base, BDT SNA
NJE, 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 OMPROUTE
as your dynamic routing daemon.
SHARE (c) Copyright IBM Corporation, 2006 August 15, 2006
Session 2870 Page 10 of 70 Baltimore, MD