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
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
<strong>Migrating</strong> <strong>to</strong> z/OS <strong>R8</strong> <strong>Part</strong> 1 of 3: Get Ready<br />
Since z/OS V1R7, the contents of PSP buckets are no longer shipped with CBPDO and ServerPac orders. Instead of the<br />
actual PSP information, you now receive the names of relevant upgrades and subsets, and you’re directed <strong>to</strong> the PSP<br />
Web site (https://techsupport.services.ibm.com/server/390.psp390) for the contents of the buckets. This ensures that you<br />
see the latest PSP information, as the PSP information that was provided with an order was current only on the day the<br />
order was created.<br />
<strong>The</strong> upgrade for the z/OS <strong>R8</strong> PSP bucket is ZOSV1<strong>R8</strong>. Recognizing that there are many PSP buckets <strong>to</strong> review, z/OS<br />
uses descriptive element names, instead of FMIDs for the subsets. This reduces the number of PSP buckets that must be<br />
reviewed, since most elements are composed of multiple FMIDs. <strong>The</strong>re are subsets in the ZOSV1<strong>R8</strong> upgrade for general<br />
<strong>to</strong>pics (ZOSGEN), and for the ServerPac deliverable (SERVERPAC) that should be reviewed also. DFSMS is<br />
consolidated in<strong>to</strong> one subset. All PSP upgrades and subset IDs are listed in the z/OS Program Direc<strong>to</strong>ry. However, the<br />
non-exclusive elements' stand-alone product upgrade and subsets are used.<br />
Hardware PSP upgrade identifiers<br />
Hardware PSP bucket upgrade IDs are in the form xxxxDEVICE and contain the latest software dependencies for the<br />
hardware, and recommended PTFs and APARs required for specific processor models. <strong>The</strong> PSP hardware upgrade<br />
identifiers are:<br />
w 2094DEVICE for the z9 EC server<br />
w 2096DEVICE for the z9 BC server<br />
w 2084DEVICE for the z990 server<br />
w 2086DEVICE for the z890 server<br />
w 2064DEVICE for the z900 server<br />
w 2066DEVICE for the z800 server<br />
Tip: To simplify finding the appropriate PSP bucket and identifying which PTFs listed in the PSP bucket need <strong>to</strong> be<br />
installed on your system, you can use the Technical Help Database for Mainframe Preventive Service Planning Buckets<br />
(http://www14.software.ibm.com/webapp/set2/psp/srchBroker) and the Enhanced PSP Tool (EPSPT). <strong>The</strong> Web site<br />
provides a search capability as well as pull down lists for types of PSP buckets. <strong>The</strong> types supported include Processors,<br />
z/OS, and Functions. So you can simply select the processor you are preparing for and click Go.<br />
DASD S<strong>to</strong>rage Requirements<br />
If you are migrating <strong>to</strong> z/OS <strong>R8</strong> from z/OS R5 or you will have a different product set than your previous release, you will<br />
see increased need for DASD. How much more depends on what levels of products you are running. Keep in mind the<br />
DASD required for your z/OS system includes (per the z/OS Policy). That is, it includes ALL elements, ALL features that<br />
support dynamic enablement, regardless of your order, and ALL unpriced features that you ordered. This s<strong>to</strong>rage is in<br />
addition <strong>to</strong> the s<strong>to</strong>rage required by other products you might have installed. All sizes include 15% freespace <strong>to</strong><br />
accommodate the installation of maintenance.<br />
<strong>The</strong> <strong>to</strong>tal s<strong>to</strong>rage required for z/OS data sets is listed in the space table in the z/OS Program Direc<strong>to</strong>ry and z/OS and<br />
z/OS.e Planning for Installation.<br />
For z/OS <strong>R8</strong>:<br />
� <strong>The</strong> <strong>to</strong>tal s<strong>to</strong>rage required for all the target data sets is 5,456 cylinders on a 3390 device.<br />
� <strong>The</strong> <strong>to</strong>tal s<strong>to</strong>rage required for all the distribution data sets listed in the space table is 7,362 cylinders on a 3390<br />
device.<br />
� <strong>The</strong> <strong>to</strong>tal HFS s<strong>to</strong>rage is 2,800 cylinders on a 3390 device for the ROOT HFS and 50 cylinders for the /etc HFS.<br />
� <strong>The</strong> <strong>to</strong>tal s<strong>to</strong>rage required for the SMP/E SMPLTS is 0 3390 cylinders (there are no load modules in z/OS <strong>R8</strong> that are<br />
both cross-zone and use CALLLIBs, thus the SMPLTS is not needed for permanent s<strong>to</strong>rage for the z/OS product<br />
itself).<br />
SHARE (c) Copyright IBM Corporation, 2006 August 15, 2006<br />
Session 2870 Page 36 of 70 Baltimore, MD