I had a similar issue with an old 8203-E4A Power 6 box running V7R1
and 1 partition a few years back.
No maintenance in place. Every 3 years or the batteries throw an error.
The usual batteries expired stuff. I'm able to force the batteries to an error
condition, gently remove the C1/C2 or C4/C5 battery, reinsert them and
restart the battery cache. Yeah, it's risky but the firm didn't want to spend
any $$ on it since it was a dev playground. Their take was if it goes it goes.
So that said, a network guy decided to upgrade the UPS. What he didn't say
is he was going to pull the power strip the old UPS was on, etc. Ends up
under the floor, he didn't know that Power 6 8203-E4A was also plugged in.
WHOOPS!
I get a call that the machine stopped running. Log on to the HMC and what do
you know, the expansion unit where the load source was located failed. Flat out
died.
I reached out here and a guy from Abacus Solutions called me saying he had
the exact same box in their shop and he thought there was a way to unplug
that unit and plug it into the drive card if it had 2 slots. Sure enough it did.
Once that was done I had to do a bit of HMC config so the load source was found.
I think I explained that right (it's kind of a blur from a few years ago) but sure
enough the box came up and it's still (knock wood) running today.
Moral of story .... Jim could be right. it may be something that could be fixed
without any help. Just a bit of research. Side note: For me, Abacus has
disk drives for that model at about $50 each. I kept a few of them on hand
as a safety net back then.
MM
Respectfully,
Michael Mayer
IBM i on Power System Admin
ERMCO-ECI
2225 Industrial Rd
Dyersburg, Tennessee 38024
Office and OnCall: 731.676.4318
Cell: 518.641.8906
Email: michael.mayer@xxxxxxxxxxxxx
https://www.ermco-eci.com
IBM i Personal Blog:
https://ibmireference.blogspot.com
"Success is not final. Failure is not fatal. It is the courage to continue that counts".
2. RE: Hardware error coverage problem (smith5646midrange@xxxxxxxxx)
4. Re: Hardware error coverage problem (Jim Oberholtzer)
----------------------------------------------------------------------
message: 2
date: Tue, 16 Jan 2024 11:05:10 -0500
from: smith5646midrange@xxxxxxxxx
subject: RE: Hardware error coverage problem
So, is the reverse true? If I do not have coverage and something breaks, I can add coverage at that point, open a ticket and it will be covered?
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Jim Oberholtzer
Sent: Monday, January 15, 2024 8:40 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Hardware error coverage problem
Gotta report it while the contract is in force.
Jim Oberholtzer
Agile Technology Architects
On Jan 15, 2024, at 6:55?PM, smith5646midrange@xxxxxxxxx wrote:
?I had a hardware maintenance contract on my 8208-E4D that expired on
12/31/23. On 01/12/24, I noticed that a hardware error was logged on
12/24/23 (before the contract expired). I opened a ticket but IBM is
telling me that since the ticket was opened on 01/12/24 and my
contract expired on 12/31/23, the error is not covered.
It seems like the error should be covered based on the date it was
logged, not the date that the ticket was opened, Is the support
person looking at the issue incorrectly and it should be covered based on the logged date?
Anybody have an knowledge on this issue?
------------------------------
message: 4
date: Tue, 16 Jan 2024 11:16:12 -0600
from: Jim Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx>
subject: Re: Hardware error coverage problem
Agreed, I don't think IBM will cover that model any longer.
What's the problem? It might be a whole lot easier to fix than you think,
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects
----------------------------------
midrange.com
