I just wanted to post the final results of my exercise.
To recap:
My 170 needed a scratch install. I did a scratch install of v5r2, then
applied the cume/hiper/groups I had from 2004. Upon installing the
current (April 2007) cume/hiper/group the machine croaked on the B side.
I had loaded in the order of hiper/group/cume, not cume/hiper/group.
I restored to the backup of v5r2 plus 2004. OPT01 became OPT02, and SSL
telnet didn't work. I removed AC3, DG1 and DCM. Reinstalled, reapplied
2004 PTFs. All was well.
I applied the 2007 cume and rebooted.
I applied the 2007 hipers and rebooted.
I applied the 2007 groups and rebooted.
All is well now.
So - it was either the volume of PTFs (hiper/group/cume) all at once on
a single reboot, or it was the order of application.
Thanks again for all your help.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Thursday, September 13, 2007 10:58 AM
To: Midrange Systems Technical Discussion
Subject: RE: Link Loader Failure and B600 0901 after v5r2 cume install
Hey, that does sound familiar!
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
This thread ...
RE: Link Loader Failure and B600 0901 after v5r2 cume install, (continued)
This mailing list archive is Copyright 1997-2025 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.