MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » August 2013

Re: PTF install questions



fixed

Apologies for my getting lazy. Didn't quite feel excited about getting to
computer room.

Just looked at LAN console graphic of panel. Shows only 01 B. Actual
physical front panel does indeed show 01 B N V=F P

So, full IPL it is.

When I do things like PWRDWNSYS or >merely< some device configuration
change remotely, I do indeed proceed carefully. No fun at all having
things go awry. urned out that despite there was no issue with the IPL
this morning, the "nice people" higher up got an alert when system went
down. Monitoring software.


On Wed, Aug 28, 2013 at 2:42 PM, Roberto José Etcheverry Romero <
yggdrasil.raiker@xxxxxxxxx> wrote:

Kinda. If you can i would read up on ASMI, configure an IP address and get
access to it. It's a poor man's HMC in that you can turn on/off, modify
front panel settings, read historic SRCs and the like and it's a godsend
when you are remotely ipl'ing a machine. When you somehow fail to include
the RESTART *YES and the machine goes down and you dont have anyone to push
the white button, ASMI is good indeed.
If not, it shouldn't be problematic, just change the panel now and send the
PWRDWNSYS when you can. I dont feel confortable IPL'ing a machine when i
dont have front panel access.

Best Regards,



On Wed, Aug 28, 2013 at 4:34 PM, John McKee <jmmckee@xxxxxxxxxxxxxx>
wrote:

I wondered about that this morning. Debated on whether to do it or not.
From previous messages exchanged with Rob, I was not sure if that would
have made a difference.

I started the IPL from my apartment (long boring story). Got to desk and
terminal session was down. My DEVD had ONLINE (*NO). I have since
changed
it to *YES. In theory, now, I could then perform a full IPL remotely and
fix this minor irritant. Am I right?

John


On Wed, Aug 28, 2013 at 2:22 PM, Roberto José Etcheverry Romero <
yggdrasil.raiker@xxxxxxxxx> wrote:

Ah! i know what your problem is...
Front panel, does it perchance read: 01 B N V=F P? it should read 01 B
N
V=F T. In the same way you have A side and B side for LIC you have P
and
T
(permanent and temporal) sides for the FSP's firmware. You are IPL'ing
from
P which is the same as IPLing from A and expecting ptfs to be loaded.
Next time, do a PWRDWNSYS but take care that it's a *FULL and not a
*SYS
one. It'll restart the FSP and load the correct fw.

Best Regards!



On Wed, Aug 28, 2013 at 4:15 PM, John McKee <jmmckee@xxxxxxxxxxxxxx>
wrote:

Finally did.

DSPPTF SELECT(*ACTRQD)
shows eight MH PTFs - 1076, 1073, 1070, 1053, 1007, 1004, 1001, 0997.
All
permantly applied. All show "Permanently applied - IPL". IPL source
is
##MACH#B ##SERV#P.

Displaying general information for 5722999 MH01076 shows Server IPL
required ##SERV#T

Sticking my neck way out - does this imply that a second IPL from "B"
side
will fix?

We had PTFs temp applied on "B" for years. We are IPLed, now, on
"B".
Did
IPL this morning only end up syncing B and A sides, and another IPL
will
fix it?

DSPPTF LICPGM(5722SS1) shows most recent (?) cum as TC10292.

I have applied PTFs suggested in (I have three documents don't
remember
which one) manuals for v5r4 to v61 maybe v71 (mind is going). Will
look
through the docs a lot more to be sure nothing was missed. Since
things
are working, predictably, is there any point in loading a more recent
CUME? I know you guys with LOADS more experience say link loader is
no
longer an issue. But, is there any point to loading a CUME to get to
next
level if upgrade PTFs are permanently applied?

John McKee
--
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.


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


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


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







Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact