|
That is true. Also note that 7.2 will require a load source that is 70GB
or higher, and right now the min is 17GB so that is a big jump and people
should start planning for this now.
Pete
--
Pete Massiello
iTech Solutions
http://www.itechsol.com
http://www.iInTheCloud.com
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:
midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Wednesday, October 16, 2013 10:39 AM
To: Midrange Systems Technical Discussion
Subject: 7.2 Was: IBM i 7.1 Technology Refresh 7 available Nov.
15-CLARIFICATION on POWER5
<snip>
[IBM i 7.1 partitions>->(BECOMES)->: Partitions with the release
after IBM i 7.1 cannot own any HSL/RIO or IOP hardware, but they can be
virtual clients. (This support statement was already true for POWER7 and
later. This planning statement specifically applies to POWER6
technology-based systems running (ADDED)->[the release after] IBM i 7.1.)
</snip>
Would guesting 7.2, either
- on a host 7.1 partition
- or on VIOS
insulate you from the above statement? Granted all affected I/O (disk,
tape controllers, etc) would have to either be on supported hardware or be
virtualized also.
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: DrFranken <midrange@xxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>,
Date: 10/08/2013 12:49 PM
Subject: Re: IBM i 7.1 Technology Refresh 7 available Nov.
15-CLARIFICATION on POWER5
Sent by: midrange-l-bounces@xxxxxxxxxxxx
Steve Will responded with these corrections:
===================================================
The next generation of servers following POWER7® / POWER7+™ is not
planned to support IBM i 6.1 and will require IBM i 7.1, or later.
[IBM i 7.1 partitions]->(BECOMES)->: The release after IBM i 7.1
will run on POWER6® and newer hardware. No POWER5 technology-based
systems are supported.
[IBM i 7.1 partitions>->(BECOMES)->: Partitions with the release
after IBM i 7.1 cannot own any HSL/RIO or IOP hardware, but they can be
virtual clients. (This support statement was already true for POWER7 and
later. This planning statement specifically applies to POWER6
technology-based systems running (ADDED)->[the release after] IBM i 7.1.)
Language Translation Support: Starting with (ADDED)->[the release
after] 7.1, the 5770-SS1 IBM i operating system and subsequent products
will no longer be translated into Croatian and Romanian. The national
language version feature codes for Croatian (#2912) and Romanian (#2992)
will remain, but the text will now be delivered in English. The system
multicultural support for these languages will not be affected.
======================================================
So effectively there was some 'oops' where IBM i 7.1 was used where 'The
release after 7.1' was intended.
Also if you missed it, Colin Paris indicated that 'The release after IBM
i 7.1' would be known as 'IBM i 7.2' and is expected in 2Q14.
- Larry "DrFranken" Bolhuis
www.frankeni.com
www.iDevCloud.com
www.iInTheCloud.com
On 10/8/2013 11:01 AM, Gqcy wrote:
*This message was transferred with a trial version of CommuniGate(r)Pro*
POWER5+, as well?a
On 10/8/2013 8:59 AM, DrFranken wrote:
I have asked people 'who will know' for clarification but it has to be
--typo. It would be quite a shock to attempt loading a TR to a POWER5
system and find out that suddenly it no longer works. For IBM i 7.2,
POWER5 will not be supported.
- Larry "DrFranken" Bolhuis
www.frankeni.com
www.iDevCloud.com
www.iInTheCloud.com
On 10/7/2013 6:06 PM, Roberto José Etcheverry Romero wrote:
On that subject, i noticed something weird:
"IBM i 7.1 partitions run on POWER6® and newer hardware. No POWER5
technology-based systems are supported."
AFAIK IBM i 7.1 ran just fine on my test 520. Does this mean that
starting on TR7 the LIC wont load on such systems? or is it an attempt
to move people off the old hardware?
Just a thought...
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.
midrange.com
