× 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.



Hi Thomas

Your first option is to save the guest system to tape (option 21), then
recreate the guest with the disk sizes you need, maybe using 6 or 8 disk
units/storage spaces as a minimum. This kind of depends on your tolerance
for downtime.

If you need a second option that is not doing a complete recovery then you
can mess with the disks and storage spaces to get there.

First of all you should match up which disk on the guest is which Network
Storage Space with some SST and Storage space exploration. I can't
remember the exact details of how and I don't have a hosted system to look
at, but basically use SST/WRKHWDRSC on the guest to get the disk unit
details and WRKNWSSTG to get the storage space details and match them up.

Once you know which disks are which, and in particular, which disk is the
Guest load source disk, if you have enough space you can move everything
off the disks by a combination of STRASPBAL and deallocating the unused
disks and then just doing a logical remove of the disks in SST on the
Guest. The logical remove will move data from the disks being removed onto
the ones that are being retained, but can take a while. STRASPBAL will
allow you to do the bulk of it in the background in advance while the
system is running and maybe save some down time.

once you have everything on the load source and the disks have been removed
from the system (ie.e the Guest LPAR has logically removed the disks) you
can delete the underlying storage spaces to reclaim the occupied storage.

Depending on how tight your storage is and what your performance
expectations are I would consider adding some new smaller storage spaces to
your system so it has some additional "arms" to work with. You can run
another STRASPBAL to spread disk evenly across the disk units again. Unless
you are desparate I would not mess with the load source which may have to
be 70GB or better anyway (though there is a PTF that might help with this)

Be sure to save those storage spaces before hand in QNWSSSTG because worst
case you can restore them if it all goes pear shaped or just go ahead save
the whole system to tape.




On Tue, Jul 7, 2020 at 8:03 AM Thomas Garvey <tgarvey@xxxxxxxxxx> wrote:

Hi,

I have a v7r3 partition hosting a v7r1 partition. We need it to be able
to move objects from v7r3 down THROUGH v7r1 to reach the destination of
a v5r4 server. No other licensed software (such as compilers) exist on
this partition.
However, the network storage spaces allocated to the network storage
device are much larger than we need for the v7r1 partition. We need to
SHRINK those storage spaces to give that space back to the v7r3 host.
The CHGNWSSTG command does not allow smaller sizes, only larger.
Nonetheless, we need to shrink these allocations.

So, exactly how do I do this? Do I have to wipe out the v7r1 partition
and the NWSD and spaces and build a new hosted partition with v7r1 (with
much smaller storage spaces allocated)?
I hope not, because IBM won't help with v7r1 anymore.
In my case, I have four network storage spaces defined. Maybe I can move
whatever is on three of them to the fourth, and then delete the three.
But how do I find out what is on those three and move it off? It's
probably mostly the OS which was distributed acress the spaces.

Anybody ever run into this issue? What did you do? Suggestions?

--

Best Regards,

Thomas Garvey


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.