× 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.



Dear colleagues,
I am running on a model 9406-570, which was recently upgraded
from V5R3 to V5R4, with absolutely no trouble. However, after about 2
months of being at that O/S level, we were forced into the decision (for
various reasons) to try to take the machine back to V5R3. I have done
such 'scratch installs' in the past, simply by doing a Manual IPL from
the 'D' side, and reloading everything from a GO SAVE and/or original
IBM media (eg. V5R3 CDs). When I attempted to do so in this case, I got
the results below. Note that this system uses Ops Console (direct) for
the console connection, and has never used HMC to our knowledge.

1) V5R3 LIC was reloaded from original V5R3 install CDs, after
taking option '2' to scratch all disk units.
2) Upon taking the option to reload the Operating System, I
immediately was given the option to add non-configured disk units into
the ASP.
3) This ran for a while but finally halted with an error stating
that it failed to reset a system IOP.
4) I proceeded to bypass adding the drives, and continued with
re-loading user profiles, configuration objects, Lic Pgms, etc...
5) Upon further attempts to add disk units to the ASP, got hardware
errors on the units (see below).
6) We had to attach a PC to the HMC2 port on the back, in order to
get into the Service Processor interface.
7) Now we are unable to do a Manual IPL. Even though we have set
the value to 'Manual' in the Service Processor interface, and even
though the front LED panel reads '01 M V=F
HMC=0 P


the machine simply will not power up in
Manual mode. It always comes directly to the main LOGIN screen, and
therefore I am not able to get into DST. The errors indicate that there
is some kind of mismatch between the O/S level of the machine, and the
O/S level of the HyperVisor. Or that the HMC is not giving correct
information to the HyperVisor, that sort of thing. When IPLing (and as
of late, all through the day), I am getting numerous hardware errors in
WRKPRB and Service Tools on CMB07 and CMB06, but I still don't think it
is hardware. Below you will find some of the errors:

SRC B006 1302
SRC B006 1304
SRC B006 1308

SRC B600 512D
SRC B600 5120
SRC B600 5275

SRC 2844 B935 (message text: "Indicates that PHYP sent the FSP a bad
size, modifier, or HMC index."

Again, the primary question seems to be: is it possible to do a
'scratch install' from V5R4 back to V5R3 on a machine that has
HyperVisor on it? I cannot help but thinking that all of the problems
are related to moving the system O/S back to V5R3, but the HyperVisor
and Service processor are still at V5R4? And, why does the system think
that I have HMC installed, when I do not?

Any input would be appreciated!

Lane Requist


Lane Requist
Harris Corporation
9800 S. Meridian Blvd., Suite 300
Englewood, CO 80112
lrequist@xxxxxxxxxx
Desk (303)476-4666
Cell (303)588-9952



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.