Migrating to zOS R8 Part 1 - Messmer The Brain House
Migrating to zOS R8 Part 1 - Messmer The Brain House
Migrating to zOS R8 Part 1 - Messmer The Brain House
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Coexistence Service Requirements for z/OS Release 8<br />
To understand the Coexistence-Fallback-Migration policy for z/OS, and which releases are supported with z/OS V1 <strong>R8</strong>,<br />
see the Coexistence section of this presentation. Listed below are the coexistence and fallback service, for installation on<br />
an z/OS V1R7 system for z/OS V1<strong>R8</strong>. For a list of the coexistence service on z/OS V1R6 and z/OS V1R5 for z/OS V1<strong>R8</strong>,<br />
see Appendix B of this presentation.<br />
Apply on z/OS V1R7, the coexistence and fallback service (PTFs) listed in the table below:<br />
Element or feature, and function provided by PTFs<br />
<strong>Migrating</strong> <strong>to</strong> z/OS <strong>R8</strong> <strong>Part</strong> 1 of 3: Get Ready<br />
Coexistence System Requirements for z/OS <strong>R8</strong><br />
Documented in z/OS Migration<br />
From z/OS R7 Coexistence PTFs for z/OS <strong>R8</strong>:<br />
BCP - WLM, Converter/Interpreter, Program Binder (new PM level - PM5!), Console,<br />
Logger, RRS<br />
DFSMS - dfp, hsm, rmm<br />
Distributed File Service - zFS<br />
HCD - for HCM support<br />
JES2 - for MAS support down <strong>to</strong> z/OS R5 JES2<br />
JES3 - for multisystem complex support down <strong>to</strong> z/OS R5 JES3<br />
Language Environment - downward compatibility<br />
NFS - read support for new <strong>R8</strong> NFS export file format<br />
RMF - sysplex-wide reporting <strong>to</strong>leration<br />
Security Server RACF - database template structure <strong>to</strong>leration<br />
From z/OS R6 or R5 Coexistence PTFs for z/OS © <strong>R8</strong>: 2003 IBM Corporation<br />
Found in the Appendix of your handout...<br />
<strong>Migrating</strong> <strong>to</strong> z/OS <strong>R8</strong> <strong>Part</strong> 1 of 3: Get Ready<br />
BCP: Ensures that pre-z/OS V1<strong>R8</strong> systems <strong>to</strong>lerate the new format of the z/OS<br />
V1<strong>R8</strong> WLM service definition and service policy in the WLM couple data set.<br />
Moreover, the PTF ensures the <strong>to</strong>leration of changed WLM LPAR management and<br />
JES initia<strong>to</strong>r management information that is exchanged in a mixed-release (z/OS<br />
V1<strong>R8</strong> and pre-z/OS V1<strong>R8</strong>) sysplex.<br />
If the WLM service policy in the couple data set has been activated by a z/OS V1<strong>R8</strong><br />
system, a pre-z/OS V1<strong>R8</strong> system without the PTF will not be able <strong>to</strong> activate the<br />
policy and might fail during IPL with a wait state 064. If LPAR management is<br />
being used in a mixed-release sysplex and the PTF is not installed, you might<br />
experience abends and see message IWM054I FAILURE IN LPAR CPU<br />
MANAGEMENT, PROCESSING DISABLED.<br />
BCP: In z/OS V1<strong>R8</strong>, SYSIN DD * override statements are no longer required <strong>to</strong><br />
reside in the job stream in the same order as the corresponding DD statements<br />
appear in the procedure. Because new text units are introduced for each SYSIN DD<br />
* statement, the PTF allows jobs <strong>to</strong> ignore the new text units when they run in a<br />
© 2006 IBM Corporation<br />
z/OS V1R7 PTFs<br />
UA90269 (if you do not<br />
have JBB772S installed)<br />
or UA90270 (if you have<br />
JBB772S installed)<br />
UA24560<br />
SHARE (c) Copyright IBM Corporation, 2006 August 15, 2006<br />
Session 2870 Page 46 of 70 Baltimore, MD<br />
26
Change language