1) Do you need to only refresh libraries for an application, or the entire LPAR, the entire LPAR would be almost like a system restore.

We've automated the refresh of an entire application using AJS, (Advanced Job Scheduler) BRMS, and a 4drive Tape library.
Two jobs in AJS on Test LPAR
1) First job deletes all the libraries on the test LPAR, any time after 5 pm. (takes about 1 hour for delete)
2) Normal Full production SWA runs every night at 22:00 ; completed by 00:30
3) Second job starts around 00:30, has a built in delay and waits for the Production Save to be done. (takes about 2 1/2 hours for the application libraries).
Issues a separate RSTLIBBRM command for each library to be restored.
Within AJS, we parameters so we can easily change the restore if the latest version is not requested, but an older version.

Cause . . . . . : Command to execute is: RSTLIBBRM SAVLIB(CABLEFILES)


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Richard Reeve
Sent: Monday, December 14, 2015 2:11 PM
To: Midrange Systems Technical Discussion
Subject: Lpar refresh strategy


I am not an LPAR expert and was hoping for a little advice. I have a box with 3 LPARS. One production, one test and one development.

I am looking for advice on the most straight forward way of refreshing the test LPAR from production. Is there a way that I could automate? If so, how? FWIW - the library names are the same in both test and production.

Thanks in advance for any advice.

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,
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at

This thread ...


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

This mailing list archive is Copyright 1997-2020 by 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].