Rob,
I rebooted the HMC this morning, see if this helps.
I did find that I'm now behind on SP for 8820, but also 883 and 884 are available.
Any thoughts on HMC code update?
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Wednesday, December 09, 2015 9:15 PM
To: Midrange Systems Technical Discussion
Subject: Re: HMC called home E332FFFF ; E35A0011 ; E355004C
Used to be that a reboot of the HMC on occasion was necessary. I traditionally do it the week before some planned outage. This helped to clear up memory.
But you may wish to check on 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: "Steinmetz, Paul" <PSteinmetz@xxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxx>
Date: 12/09/2015 08:59 PM
Subject: HMC called home E332FFFF ; E35A0011 ; E355004C
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
HMC called home several times the last few day, possibly while I was
DLPARing adapters and memory.
Anyone else experiencing these?
Do I need an HMC code update, not finding the link for code updates 8 or
greater.
7042 CR6 8820 SP0
E332FFFF -
Explanation
This error occurs when the HMC receives notification that a particular
Java code string is corrupted.
Problem determination
If you have the call home feature enabled, the failure information
(including the JavaCore) will be transmitted to service and support. The
support organization will examine the JavaCore file. Otherwise, you can
retry the task.
E35A0011
Explanation
Licensed Internal Code failure on the Hardware Management Console (HMC).
Problem determination
Call your next level of support.
E355004C
Explanation
Licensed Internal Code failure on the Hardware Management Console (HMC).
Response
A memory threshold has been exceeded for the Java Virtual Machine(JVM). It
is possible that memory for the JVM is becoming exhausted and will soon
run out. It is also possible that this is a spike in the memory usage of
the JVM and things could return to a normal operational state. In addition
to the log being taken, a dump of the JVM has been forced for this
condition as well.
Problem determination
Call your next level of support.
Thank You
_____
Paul Steinmetz
IBM i Systems Administrator
Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071
610-826-9117 work
610-826-9188 fax
610-349-0913 cell
610-377-6012 home
psteinmetz@xxxxxxxxxx
http://www.pencor.com/
midrange.com
