|
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
bounces@xxxxxxxxxxxx] On Behalf Of Wayne McAlpine
Sent: Wednesday, January 09, 2008 10:59 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Anybody else had trouble getting a new system password from
IBMafter a CPU upgrade?
Charles, does this bump up the software tier? That may be their
rationale.
Wilt, Charles wrote:
This past November, we replaced the original 2465/0868 CPU in our model810 with a used 2467/0867
purchased from our standard IBM BP.allow the CPU to continue to
However, it turns out IBM is refusing to supply a new system password to
work in our box after the 70-day grace period expires.that IBM is refusing to
I'm not directly involved in the discussions, but what I'm being told is
supply a password for two main reasons:extended support contract in place
--we are on an unsupported release (v5r2) but I'm told we have an
to tide use over till we can upgrade to v5r4processor tier. Had we replaced
--we just put in a faster single processor while staying in the same
the original single with a dual processor, they'd be willing to supply apassword.
us we have to swap our old box
So far, we're hitting a brick wall with IBM. IBM is basically telling
for the one the faster processor came out of.wall?
Has anybody else had this problem?
More importantly, did you find a the hammer needed to get through this
appreciated.
Any other comments/suggestions/people to contact would be much
confidential and privileged. If you receive this e-mail and you are not a
Thanks in advance!
Charles Wilt
Software Engineer
CINTAS Corporation - IT 92B
513.701.1307
wiltc@xxxxxxxxxx <mailto:wiltc@xxxxxxxxxx>
This e-mail transmission contains information that is intended to be
named addressee you are hereby notified that you are not authorized to
read, print, retain, copy or disseminate this communication without the
consent of the sender and that doing so is prohibited and may be unlawful.
Please reply to the message immediately by informing the sender that the
message was misdirected. After replying, please delete and otherwise
erase it and any attachments from your computer system. Your assistance
in correcting this error is appreciated.
--
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.