×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Any PTF that are not applied or groups, delete. Then try the new CUME.
I just won the battle on a V5R3 box that was 5 cume's behind.
Chris Bipes
Director of Information Services
CrossCheck, Inc.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Pete Helgren
Sent: Tuesday, February 09, 2010 3:51 PM
To: Midrange Systems Technical Discussion
Subject: Recovering from a hosed up CUME install
I have a customer that, for the life of me, managed to install a CUME
that just never seemed to fully apply (V5R4). Over a year ago I
invested 3 or 4 hours tracking which PTF(s) was(were) a co-req or a
pre-req and eventually was so confused by the circular logic (who's on
first, what's on second...) that I have decided to start with a new CUME
and apply it *clean*. The question is, can I *undo* the previous CUME?
I *think* the answer is yes, if I can slip the LIC and then load and
apply the latest CUME.
Is that the best approach? Or should I just I just plan to upgrade to
6.1 and leave it at that? I'd rather not do the 6.1 upgrade at the
moment so if there is a way to recover from a *bad* CUME install, I'd
like to take that approach first.
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.