|
Nice to get to 7.3. Congrats.
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: Jeff Crosby <jlcrosby@xxxxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 12/20/2017 08:15 AM
Subject: Re: IBM 9406-270 as400 error code C100 101A
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
"There are a number of reasons for resaves. Currently the two biggest
reasons are: New TR's, and new hardware support."
Just ran into that. We are (finally) going to move our IBM into the
cloud. We're at 7.1 on a System i 520 going to Power 8 at 7.3.
They could not restore our Save 21 directly to the Power 8 hardware
because
our version is not LIC spin S. So, to not disrupt us out here, they
restored to Power 5 hardware in the data center, slipped the LIC there,
applied all PTFs and did a new Save 21. That save will now be restored to
Power 8 for the upgrade to 7.3 and away we go.
On Wed, Dec 20, 2017 at 7:45 AM, Rob Berendt <rob@xxxxxxxxx> wrote:
RSA was the very first version of V4R2.of
RSC would be the third time they respun V4R5
7.1 is already on resave S.
There are a number of reasons for resaves. Currently the two biggest
reasons are: New TR's, and new hardware support. IBM swore on a stack
bibles that they were done with new TR's for 7.1. However they didissue
a new resave of 7.1 for some new hardware. Resave R was for TR11, thethe
last one. Resave S was for some new hardware.
Let's say V4R2 came out before the 270. Now let's say it didn't support
the 270 until resave E. Can you see why resave C might be an issue?
Disclaimer: I do not know at what levels certain hardware were added to
support on certain levels of OS based on resaves. My comments about the
270 were solely for example uses.
People burn themselves all the time. They quickly order the newest
version of the OS and leave it on the shelf for 3 years as the project
gets delayed. Then they don't order a new resave, thinking the new cume
will save them. Well if you can't boot this latest hardware on the old
DVD it gets really hard to put a ptf on.
Even though I'm on the latest OS I order the final resave and cume at
end of life for an old version and shelve it. For possible mergers andthat
acquisitions.
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: Alexandre Bencz <alebencz@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 12/19/2017 08:22 PM
Subject: Re: IBM 9406-270 as400 error code C100 101A
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
I have the disks of v4r2 and v4r5.... in v4r2 there are this text:
* Licensed Internal Code - RSA
In v4r5 there are this text:
* Licensed Internal Code - RSC
On Tue, Dec 19, 2017 at 1:32 PM, Rob Berendt <rob@xxxxxxxxx> wrote:
And, your LIC CD, what version is it? And do you see a resave/respinthe
marker on it? For example:
Licensed Machine Code RS611-A
or some such thing? Basically the higher the ending letter the newer
resave.off
What is a resave?
http://www-01.ibm.com/support/docview.wss?uid=nas8N1022015
Alas, none of these versions of OS will run on a 270.
What versions of OS are supported on a 270?
http://www-01.ibm.com/support/docview.wss?uid=ssm1platformibmi
I did manage to upgrade a 270 to V5R4M5 to allow me to migrate it to a
Power 6 MMA.
However, if you do not have license keys needed for V5 you'd be better
at V4R5.
To me, this is so far behind that I would be so frustrated with it
listI'd shoot the box full of holes and get time on a service instead.list
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
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxx--
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
--
Jeff Crosby
VP Information Systems
UniPro FoodService/Dilgard
P.O. Box 13369
Ft. Wayne, IN 46868-3369
260-422-7531
www.dilgardfoods.com
The opinions expressed are my own and not necessarily the opinion of my
company. Unless I say so.
--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
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.