Iseries migration of data

I need to migrate an iseries box for a customer.  The current machine is at V5R2.  The target machine is at V5R3.  We will not be replacing everything on the target box, just the profiles, libraries and data.  What is the best way to migrate this easily without wiping out the target box.
Kevin CaldwellOwner of RUseeingRed Tech SolutionsAsked:
Who is Participating?
Gary PattersonConnect With a Mentor VP Technology / Senior Consultant Commented:
Follow the instruction in the Backup and Recovery Guide for the target version (V5R3).  

If none of the standard cases fit your need, and you've never done a migration, you really need to consider bring in an experienced consultant.  Migrations can get tricky if you aren't following the IBM roadmap:

Make sure and read the following materials, too.  Links are in the IBM Support document above down in the V5R3 Migration Target grid.

PSP SF98086 - iSeries Memorandum to Users, V5R3
PSP SF98080 - Software Installation Information, V5R3

- Gary Patterson
expert02232010Connect With a Mentor Commented:
"We will not be replacing everything on the target box, just the profiles, libraries and data"

Haha. What are you keeping?

If you are going to V5R3, why not step up to V5R4?

When I did our last migration, I followed the book but really it comes down to moving it piecemeal to make sure everything is kosher.

You need a "quiet" time on the source machine so that not too many changes are happening. We spent about a month doing our migration and testing and so we did several rounds of each of the following:

Save the profiles and restore them on the new box.
Save the libraries, restore them on the new box.
We had some IFS directories we had bring over as well.
SAVSECDTA, RSTUSRPRF and RSTAUT to update the authority.

We set up some FTP jobs to do this automatically for changing libraries and user profiles while we were in test mode. We had everyone sign on the new system and test their access and found some problems that required the RSTAUT command. We also ended up doing a RCLSTG on the new box at some point. I think all the restore action (including some that didn't work), left a few fragments behind and the RCLSTG seemed to clean it up.

Beware of the order of restore if you have logical files not in the same library as the physical. Physical files first, then logicals. Make sure library list is correct for those special cases.

When we did the final data migration, we spent a weekend doing it and then waited for the problems to arise. After a month of testing, the final migration was very smooth. I think we had a few minor things come up but overall very smooth.

Good luck
Kevin CaldwellOwner of RUseeingRed Tech SolutionsAuthor Commented:
Sorry to reply so late on this.  
If you do a go save then #23  All user data and save this data then restore it on the other machine, would that also work?
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.