I am thinking you'd be better off with save/restore for a number of
Number 1: Do you really want to rename your new system (or your old
Number 2: If you really are a small shop with a single box do you really
want to learn all this stuff about SNADS communication just to do a data
migration? Keeping in mind that SNADS has no future and it's all in TCP
nowadays. Basically all that SAVRSTLIB does is
a-Save the library to a save file
b-transmit the library
c-Restore the library
Number 3: Do you have the space on the old system to contain the space
for the save file too?
And my biggest reason: If it is possible, and it may not be if your
system is really old and doesn't support newer OS, I think it is best to
migrate your system to the newest OS and then restore that using steps
If your system is too old then a compromise might be finding out the
highest level your old system will support and the lowest level your new
system will support. For example I upgraded a 270 to v5r4M5, restored
that on a power 6, upgraded it to 6.1 (and when 7.1 came out, 7.1).
If your old system truly cannot upgrade to a level that is supported even
as a temporary intermediate between the two then what you are doing is a
data migration as outlined in:
If you are running such an old system, and you only have a single system,
then I'll hazard a guess that it's been awhile since you've done your last
upgrade and you may be a bit rusty at it. This is where it may behoove
you to contract it out to people who do this all the time. People like
Pete Massiello or Larry Bolhuis. I wouldn't mind a little weekend work
doing this kind of stuff myself. I have 11 lpars of IBM i 7.1 running on
three racks. Granted, I jump on the latest OS ASAP so with 7.1 having
come out over two years ago it's been awhile since my last upgrade (but
not my last install).
Too many people think they can restore a few libraries and stuff and that
will work. What little time they save doing this is often spent by weeks
of cleaning up problems.