Hi Pete
Last time I ran into this (actually years ago) I got the machine into a
restricted state and then wrote out a list of what PTF's came up as having
problems in the IPL Log. I tried to work out the order but ran into the same
issues you did.
Eventually I settled for a brute force approach and just attempted to load
and apply on each one until one worked then started working my way through
the list again. Eventually they all go applied OK. I recall that I had to
apply some of the "good" PTF's permanently so that the problem PTF's could
apply Temporarily and I suspect this was the real cause of the problem.
I guess the worth of this approach depends on how many there are, I think I
had about a dozen.
Regards
Evan Harris
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Pete Helgren
Sent: Thursday, 11 February 2010 8:37 a.m.
To: Midrange Systems Technical Discussion
Subject: Re: Recovering from a hosed up CUME install
OK. I can look at that. I wish there was an easy way to see the PTF
"chain". That is, which unapplied PTF's have CO or PRE reqs that
haven't been applied or met. That would tell me if I had one PTF that
was missing that was a pre- or co req for other PTF's that weren't
applied. I have a feeling that is what the issue is because a year or
so ago when I ran into this, I tried to individually apply the PTF's and
eventually got down to a bunch that just wouldn't apply. They all
seemed to be contingent on same few PTF's that weren't applying, but as
I investigated the "core" group of them, they all seems to be contingent
on the same group of PTF's and they seemed to have a "circular" logic.
That is PTF A needed PTF B which needed PTF C which needed PTF A again.
I took copious notes which I eventually couldn't decipher...
Maybe I'll build a spreadsheet and see if I can figure out which PTF is
the culprit. I wish I could get the list of required co and pre reqs
with the DSPPTF *OUTFILE. That way I could use query or SQL to find the
missing link.
Pete
Pete Massiello wrote:
Pete,
I had this problem once before, and I wrote a quick CL that applied
each PTF individually. I then IPLed, and then ran the program again, and
that actually fixed everything. When you do a APYPTF *ALL *TEMP *IMMDLY
(or
even delayed), it stops when it can't apply one. That is why I wrote a
CLP
that would try to apply each and every PTF individually that wasn't Perm
or
Temp Applied. You can do this now and see how many get applied.
Pete
Pete Massiello
iTech Solutions
http://www.itechsol.com
Add iTech Solutions on Facebook:
http://www.facebook.com/group.php?gid=126431824120
Add iTech Solutionw on LinkedIn:
http://www.linkedin.com/groups?gid=2206093
midrange.com
