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


On Tue, Jan 16, 2024 at 10:13 AM Glenn Ericson <glenn-ericson@xxxxxxx>
wrote:

Go 3rd party maintenance or Your Business Partner if they provand that
service

Glenn Ericson <glenn-ericson@xxxxxxx>M:: 917 992 6270

RE: Hardware error coverage problem
Jan 16 at 11:05 AM
PrintRaw message

smith5646midrange@xxxxxxxxx <smith5646midrange@xxxxxxxxx>
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxxxxxxxx

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?

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription

related questions.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.