Get your DASD installation requirements in early!

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!)

 

DASD installation sizes (in 3390 cylinders)
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
DLIB 8,941 18,000 148 1,582 200
File System (zFS) 3,309 3,300 147 2,600 400
Font File System (zFS)  --- 2,050  --- --- ---
Grand Total 18,118

33,350

(15,115 more)

297 4,184

602

(3,879 less)

 

 

 

 

 

 

 

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!

-Marna

3 Comments
1 Like

z/OSMF

May 18, 2013 08:08 AM by Mary Anne Matyaz

Wow, look at those WASOEM numbers! Can't wait to see Liberty!

A Plethora of Fonts

May 18, 2013 01:46 PM by Edward Jaffe

The z/OS 2.1 DASD footprint is nearly double that of z/OS 1.13! (Based on your numbers it's actually only 83% higher...) We discovered this "problem" during z/OS 2.1 early testing and determined it was almost entirely attributable to the inclusion of fonts that almost nobody uses. Our solution was to simply not restore the fonts. Is there a similar option for customers installing via ServerPac? Does something "bad" happen if you remove these fonts as we have done?

A Plethora of Fonts...really there.

May 20, 2013 09:48 AM by Marna Walle

There is no option (like we have for removing the unused JES) for the fonts. That's part of the reason I wanted to get these sizes to you as early as possible!  In addition, if you use the z/OSMF Software Management appliction, then the *entire* zone gets deployed - that would include fonts.  I won't comment about removing a base element of z/OS -- it's against policy.  If you do break policy and you need the font, it will be up to you to fix the situation.

Recent Stories
The Tables Turn for Me. I'm a User.

Newer z/OS github additions

Do you have any thoughts on IBM Z resiliency?