|
I agree with Jim here.
First of all, running RSTCFG without SRM(*NONE) to a different machine may
turn it into a vegetable. Kind of covered in the system migration guide.
Second, Jim's right on the differences. Let me give you an example.
Migrating that 10MB token ring lan line to a 1GB Ethernet will require
changing a lot of parameters. Heck, migrating a 10/100 ethernet to a 1GB
ethernet requires a lot of changes.
Here's a compromise. Do the following:
RTVCFGSRC *ALL to a source file.
Pour through that source. Edit/change as needed.
Restore to different machine. Try compiling it and running it.
See also
WRKHDWRSC *CMN and it's other possible values.
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: "Jim Oberholtzer" <midrangel@xxxxxxxxxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxx>
Date: 02/02/2015 07:11 AM
Subject: RE: Converting 150 to 520 RSTCFG?
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
I would not unless there are specific devices you will need. I'd recreate
everything. There is just too much difference between the hardware models
to have all the unsupported and odd stuff on the target box. The cleanup
will take longer than just recreating everything.
--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Gary
Kuznitz
Sent: Sunday, February 01, 2015 8:27 PM
To: Midrange Systems Technical Discussion
Subject: Converting 150 to 520 RSTCFG?
I have an AS/400 9401 model 150 running V4r4.
I need to convert everything to a 9405-520 running V5R3.
Should I run RSTCFG on the 520?
Of course the configurations are not identical.
It would be nice if I didn't have to reconfigure all the displays.
Thanks,
Gary Kuznitz
--
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.
--
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.
--
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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.