×
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.
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.?
As an Amazon Associate we earn from qualifying purchases.
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.