Re: Improve R&D LPAR poor disk performance (10K spiiny); Move Library to a different ASP

To me the biggest problem in that list was journaling and that one in particular IS handled correctly by utilizing save/restore for the move. Save/Restore is my go to method for this and IMHO is the best way to make it happen.

Note also that I am usually doing this for PowerHA and one of the strong recommendations for PowerHA is that all your data be journaled.


- Larry "DrFranken" Bolhuis

www.Frankeni.com
www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.

On 6/24/2016 11:45 AM, CRPence wrote:

On 24-Jun-2016 10:28 -0500, Steinmetz, Paul wrote:

Move Library to ASP (QHSMMOVL) API

Thanks for the link.

Too many restrictions though, no can do.

Restrictions

Data queue entries are not moved and will be lost.
The QSYSWRK subsystem must be active.
A library cannot be moved in the following cases:
<<SNIP list of restrictions preventing move>>

NB that those <snipped> restrictions are mostly not just annoyances
easily overcome by avoiding that API, but are instead, issues that are
functionally incapable of being overcome; i.e. a save\restore will not
function for the expressed purpose, for most of those same reasons. For
example, the database dependencies spanning an ASP will fail the
restore, so using the API with the Check Dependencies capability can be
helpful to avoid having to cleanup an incomplete\improper restore.

As to the Data Queue data restriction, by that release [IBM i 7.2 aka
v7r2], I would expect IBM might be amenable to adding the Queue Data
(QDTA) parameter to their SAVLIB [so as not to have to intercept\replace
that specification as QDTA(*DTAQ) to overcome that restriction]... or
perhaps ensuring not to explicitly specify QDTA(*NONE) to enable the
command default to be enabled.?