|
The Move Library to ASP (QHSMMOVL) API might fit the bill. The API can be found in the Object APIs chapter of the System API Reference. The API was introduced in V4R3 and basically does the save/restore for you. Bruce > >Recently our programming staff installed an upgrade to an application. Due >to disk space constraints in the system asp, installation and testing was >done in the user asp. This upgrade is now in production and I want to move >the libraries into the system asp (the user asp consists of old, slow, >unreliable and unprotected disk arrays). As I see it I may only have 1 >option - backup the libraries to tape and restore them to the system asp. I >noticed that cpylib restricts you to the same asp for source and destination >libraries. Is there any other way to accomplish moving these libraries from >one asp to another? If so, any pros/cons of either method? Thanks in >advance! > +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.