Re: Migration Refresh

[pnelson@xxxxxxxxxx]

What kind of stuff will be in QGPL & QUSRSYS? How are they fixed for DASD? 
If they've got enough, why not create a library on the 720 to contain a 
save file for each appropriate library. Save those libraries into the save 
files each day, and FTP the data from the 720 to the 810. At the end of 
the FTP script, issue a command to restore the libraries from the save 
files. That way, the users performing the testing will be using data that 
is current as of the close of business the previous day.

Contact me off line for an example of how some of my clients are doing 
this.


Paul Nelson
Arbor Solutions, Inc.
708-670-6978  Cell
pnelson@xxxxxxxxxx

"Always do right. This will gratify some people and astonish the rest." 
Samuel L. Clemens  (Mark Twain)




"Doug Hart" <doughart@xxxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
10/17/2003 10:24 PM
Please respond to Midrange Systems Technical Discussion

 
        To:     "Midrange Systems Technical Discussion" 
<midrange-l@xxxxxxxxxxxx>
        cc: 
        Subject:        Migration Refresh



 I just installed a new 810 for a customer and next week will be loading 
it from their existing 720.  This migration of their apps and data will 
build a working system which they will test on v5r2.  In about a month we 
plan to refresh the 810 and cut it over to production.  Since this test 
duration is so long the standard save changed object refresh isn't very 
doable. 

 On another system (small like this one) I deleted all the user libraries 
and user objects from QGPL and QUSRSYS before doing a full refresh.  Is 
this the best method or simply a waste of time as the restore will refresh 
the objects normally?

---
Doug Hart



_______________________________________________
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,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.