Just to let everyone know what was happening with this project. I used Rob's and Chuck's advice along with IBM Redbook sg247164 to create a Virtual Tape to use to transfer the library. Everything setup nicely and the documentation made it easy. When I went to do the transfer the backup ran for approx. 1/2 hr. and then started to gobble up disk space going from about 40% to over 95% and started to shut down the production system. We had to stop the backup and delete the catalog to get the system operating again. Either this is not going to work for me or I may have missed something in the setup. I'll look into this later.
I also used the information I received from Jim O. and Paul S. along with IBM document #404791135 and set up an EE system. Using this system I ran a SAVRSTLIB. On approx. 95 GB library it ran for approx. 9 1/2 hrs. but everything I needed got transferred with no impact on production. It appears that this is the way I'll go for now. I adjusted the timing so that everything is ready to go before the start of the work day. I just lose about 6 hrs. worth of data from the previous night but that's taken care of on the next save and we can live with that. After all, this isn't DR it's just for testing and troubleshooting.
Not having done this kind of configuring on an AS400 in nearly 25 years and since things have changed so much it was nice to have all the suggestions and information from everyone. Thanks again to everyone on the list.
ISD - Programmer/Analyst
Simcoe Parts Service Inc.
Phone: 705-435-7814 Ex: 302
If I'd have done what I said I should have done,
then I'd be sitting here saying I should have done what I did do.
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of CRPence
Sent: Friday, September 06, 2013 5:03 PM
Subject: Re: Data Transfer
On 06 Sep 2013 13:11, CRPence wrote:
<<SNIP>> Because each WRITE operation to a save file is validated
IBM i 7.1 Information Center -> Systems management -> Backup and recovery -> Backing up your system -> Preparing your media to save your system -> Choosing your save media -> Save files _i I/O operations on a save file i_ "Review these considerations which apply to input and output operations on a save file.
* Records are always read and written sequentially. The records read from a save file contain sequence and parity information that is validated when the records are written into another save file. This information ensures that the records are processed in sequence and have not been changed.
You cannot write a record that has changed since it was retrieved from another save file. You cannot write a record that is not the next record in sequence. If you attempt either of these, an escape message is sent to report the error.
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 http://archive.midrange.com/midrange-l