Been a while since I've been able to blog... z/OS V2.1 is strongly underway here, and that has been taking me away from my "treat" of blogging. For this entry, I wanted to pass along some information about planning for z/OS V2.1 that you may find helpful. (Remember, I've already mentioned to use the IBM Health Checker for z/OS right now.)
I've had the question on how much DASD storage installing z/OS and z/OSMF V2.1 will take. Here's some numbers that you might find interesting. Of course, these are sizes taken from our systems and the usual caveats apply:
- we use both JES's, we use all NLV's, we don't count non-z/OS program products,
- the z/OS V2.1 sizes are close estimates
- for the total z/OSMF sizes for R13, you need to add the "z/OSMF R13" and "WAS OEM" columns. For the total z/OSMF V2.1 sizes, you *only* need the z/OSMF V2.1 column (thank you Liberty profile!)
|z/OS R13||z/OS V2.1||z/OSMF R13||z/OSMF R13 WAS OEM||z/OSMF V2.1|
|Target PDS and PDSE||5,868||10,000||2||2||2|
|File System (zFS)||3,309||3,300||147||2,600||400|
|Font File System (zFS)||---||2,050||---||---||---|
z/OSMF V2.1 does NOT "imbed" Java SDK. Meaning that if you want to use z/OSMF V2.1 there will be an external dependency on Java SDK R7 64-bit + PTF. z/OSMF R13 did "imbed" Java SDK, so that was included in the table sizes above. How does possibly one less Java SDK to lug around sound to you??
Notice that there is a new file system for z/OS V2.1 - the font file system. More about that in a later blog. For now, know that you've got another 2,000 cylinders of file system space coming at you for z/OS V2.1.
We told you there was a lot coming in z/OS V2.1!