|
SP2 is certainly more stable than SP1. If you used the classic interface
the sizes of the windows constantly changing will drive you to distraction.
Rob is correct there are some things that simply do not exist in the
Enhanced+ environment. IBM i hosting IBM i being the major one. While
dynamic LPAR is there, it's a real PITA and if you just want to make a
temporary change (add a tape device for a special backup, then remove it)
it
does not handle those things well.
While I understand Rob's reluctance to move to the command line, like Larry
I've been convinced it's the proper way to go if you manage more than a
couple of partitions or multiple machines on the HMC. Simpler environments
were the change is minimal, stay with the GUI.
There are some parts of the Enhanced+ interface that are really excellent
(SEA management for VIOS folks for instance) but that does not make up for
the poor design of the rest.
Memory on the HMC is critical. Consider a memory upgrade to the box (cheap
too) to get as much memory as possible on the HMC.
--
Jim Oberholtzer
Agile Technology Architects
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rob
Berendt
Sent: Friday, December 29, 2017 6:30 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: Status unmatch HMC and Power 8 server.
I am running 8.8.6 SP2
I try to use the Enhanced View as much as possible. The main reason is
that
IBM considers that the wave of the future and pretty soon the Classic view
will no longer be available. Therefore the more I use it the more I can
report to IBM what doesn't work so they get it fixed before it's all I can
use. That, and it will develop familiarity.
Some of the function isn't there in the enhanced view. Even more than the
enhanced graphics of the enhanced view IBM is grasping something else as
even more "wave of the future": Command line. Apparently they are under
the belief that "real men don't use graphics" and when it comes to stuff
people prefer the command line. I tend to disagree with much of that.
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: Jack Kingsley <iseriesflorida@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 12/23/2017 04:56 PM
Subject: Re: Status unmatch HMC and Power 8 server.
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
How solid is 8.8.6 SP2
On Fri, Dec 22, 2017 at 9:18 AM, Jim Oberholtzer <
midrangel@xxxxxxxxxxxxxxxxx> wrote:
HMC 8.7 and the latest code of 8.8.6 have so many bugs I can't begin toservers.
keep
them cataloged. I just installed a new 41A with an 8.7 HMC and it did
not
show those problems but I'm no surprised.
I just closed a PMR where the RMC connection was lost to two VIOS
Took them five days to get to a resolution. Meanwhile I had torebuild
100% of the SEAs and all communications to the partitions. That was atRob
8.8.6.
--
Jim Oberholtzer
Agile Technology Architects
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Berendtthat's
Sent: Friday, December 22, 2017 6:24 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: Status unmatch HMC and Power 8 server.
But does the HMC and FSP every communicate? Like, can you start 5250
sessions? Can you look at the hardware? etc?
Basically if there is NO communication anymore that's one issue. But if
there is just no communication about the SRC changing during startup
a whole other issue.<https://maps.google.com/?q=ator+-+IBM+i+6.1+Group+Dekko+Dept+1&entry=gmail&source=g>
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1
600
to: 2505 Dekko Drivei
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: Tsutomu Fukuda <tufukuda@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 12/21/2017 08:53 PM
Subject: Re: Status unmatch HMC and Power 8 server.
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
Hi Rob.
->YES.- never catch up to matching during startup and shutdown?
->NO.- eventually match but there seems to be a lag time before they do?
-Before update -
S814---SV860_109 (FW860.31)
HMC---MH01723 (V8R8.7.0 M0 Fix)
-> This is OK.
IBM CE told us that the FSP and HMC does not communicate from packet
capture.
The link you show me is very useful.
https://www-304.ibm.com/support/customercare/flrt/
matrix?domain=mtm=8286-41A
&pkey=pwr
Many thanks.
Tsutomu. Japan.
On Fri, Dec 22, 2017 at 1:28 AM, Rob Berendt <rob@xxxxxxxxx> wrote:
Very good.
Should be a good combination
https://www-304.ibm.com/support/customercare/flrt/
matrix?domain=mtm=8286-42A&pkey=pwr
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: Tsutomu Fukuda <tufukuda@xxxxxxxxx>
To: midrange-l@xxxxxxxxxxxx
Date: 12/21/2017 11:18 AM
Subject: Re: Status unmatch HMC and Power 8 server.
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
The HMC version is as follows.
MH01725 (V8R8.7.0 M1)
Kind Regards.
Tsutomu.
On Thu, Dec 21, 2017 at 4:04 PM, Tsutomu Fukuda <tufukuda@xxxxxxxxx>
wrote:
Hi.
We have been using the Power 8 machine(S814). (which are installed
C70040917.3 )
There are problem as follows.
1)when start up (by HMC)
S814 server have already started with status STAND BY, but
listislist
displayed on HMC yet.--
2)when shutdown (by HMC)
S814 server had been shutdown but C19020 (or C19020FF) is still
displayed on HMC.
We push PF5 to refresh the screen of HMC every time.
Does anyone have those problems.
--------DSPFMWSTS---------------------
*ACTIVE SV860_127 MH01732
FW860.41
------ HMC Version ----------------------
We appreciate any advise.
Kind Regards.
Tsutomu.
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
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@xxxxxxxxxxxxlist
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
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
--
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.