× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Sue,

I see your recommendation of 79565.

Yet, this IBM link http://www-01.ibm.com/support/docview.wss?uid=nas8N1013717 says The smallest load source capacity allowed is 17 GB (document is discussing 6.1 & 7.1). In order to have a virtual disk of size 17 GB, it must be created as a 19.2 GB drive. Technically the system will allow a smaller disk size when using virtual disks; however, this will cause problems later--for example, when you go to upgrade to the next release and try to expand the LIC space.

Since a 17GB drive is referring to the 17.5 GB drives, which is 1/4 that of a 70GB drive, why wouldn't you multiple 19.2GB by 4 and get 76,800 when using the CRTNWSSTG command?

Thanks

Pete

--
Pete Massiello
iTech Solutions
http://www.itechsol.com
http://www.iInTheCloud.com





-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Sue Baker
Sent: Wednesday, October 16, 2013 7:30 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: 7.2 Was: IBM i 7.1 Technology Refresh 7 available Nov. 15-CLARIFICATION on POWER5

Jim Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx> wrote on Wed, 16 Oct 2013 23:01:23 GMT:

The LPARs are anywhere between 15 and 30 virtual drives all at 35GB
right now. I'm going to set up at least two or more vSCSI controllers
on each, so we can vitrualize tape/dvd on one then have the others for
storage.


With that quantity of virtual devices, doubling all the VSCSI units to 70G would be lots of storage. I think in this specific case, 70G load source and then specifying *ENDALC after you get LIC, QSYS, QUSRSYS, QGPL loaded and balanced would be an appropriate plan.

When you create the load source unit via CRTNWSSTG, make sure you don't specify 70000 "megabytes" as your size (NWSSIZE) because you won't really end up with 70 GB. You need to specify as 71680 to really get to 70 GB. However, don't forget the 512- byte translation makes the i client LPAR see this unit as 11% smaller, so it would end up at approximately 62 GB.

To have the client see a 70 GB (or slightly larger) unit, you want to define at 79565 megabytes in the CRTNWSSTG command.

--
Sue
IBM Americas Advanced Technical Skills (ATS) Power Systems Rochester, MN
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.