Completed all this maintenance last night, all PTFs applied, firmware activated,
I did have one small unexpected issue.
We were doing some authority fixes, service jobs in QSYSWRK causing locks.
Signed on the console, ENDSBS *ALL *IMMED.
That got rid of all the locks, authority changes completed.
A BRMS system save was submitted to run in QCTL
STRBKUBRM CTLGRP(SAVSYS05) SBMJOB(*CTLSBS) APPEND(*YES) OMITS(*IGNORE)
Signed off the console, QCTL ended, SYSSAV did not start SRC A9003C60
Normally we SRC code during a SYSSAV is SRC A9003C70.
The SRC code was so similar, didn't realize it was different.
Once I realized the save was not running, my only recovering was to force down the LPAR from the HMC, and reboot.
Once completed the save SYSSAV did start.
Reviewing the logs this morning, forcing down the LPAR did result in some damaged objects on the IPL
However, objects were not identified in the message
Could I have recovered with less issues?
Message ID . . . . . . : CPF7001
Date sent . . . . . . : 12/17/13 Time sent . . . . . . : 01:07:54
Message . . . . : Damage was detected but has been ignored.
Cause . . . . . : Damage was detected during the requested operation.
However, the operation was completed.
Recovery . . . : Look at the job log (DSPJOBLOG command) for the messages
that identify the cause of the damage.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Friday, December 13, 2013 7:59 AM
To: Midrange Systems Technical Discussion
Subject: RE: IPL for delayed PTF, shutdown to activate firmware
I've done one rack with 3 lpars this way this week.
Then I've done another rack with 5 lpars this way also this week.
I've got another rack with 5 lpars to go. That's a weekend job. It's more of a "here, your turn, I'll be camping with the Scouts, call me if you need me." I've detailed out the process (about 25 pages per lpar) enough, and been doing it this way for years. Having others assist means the knowledge is not all lost if the unthinkable happens. Others assist in shifts and we change who works which shift to spread the knowledge. We do this once a quarter.
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: "Steinmetz, Paul" <PSteinmetz@xxxxxxxxxx>
To: "'midrange-l@xxxxxxxxxxxx'" <midrange-l@xxxxxxxxxxxx>
Date: 12/12/2013 04:55 PM
Subject: RE: IPL for delayed PTF, shutdown to activate firmware
Sent by: midrange-l-bounces@xxxxxxxxxxxx
So all I need is a PWRDWNSYS RESTART(*NO), all partitions.
Shutdown the service processor.
All firmware will now be activated.
Start the service processor.
Start all the partitions.
PTFs will apply on the way up.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [
mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of CRPence
Sent: Thursday, December 12, 2013 4:49 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: IPL for delayed PTF, shutdown to activate firmware
On 12-Dec-2013 12:37 -0800, Steinmetz, Paul wrote:
I need to an IPL for delayed PTF apply.
I also need to do a shutdown of all partitions for firmware
activation.
Am I correct that a shutdown will not apply PTFs?
Do I need to do a restart *yes for the PTF apply followed by a
shutdown to activate firmware.
It is the IPL, rather than the shutdown, in which PTF apply processing
runs. In a manual IPL the PTFs are applied only if chosen to do so
manually from a menu, and in an automatic IPL the previously identified as
delayed-apply PTFs will be applied automatically [at least if the IPL is
not deemed abnormal]. For LIC PTFs, the /side/ on which the system IPLs
is very relevant. Thus the option chosen for the RESTART parameter of the
Power Down System (PWRDWNSYS) should be [and as I recall, in my experience
is] immaterial for PTF activity; i.e. only the activation of the
already-applied firmware updates may depend on use of RESTART(*NO) having
effected a full powered-off PwrDwn. AFaIK the documentation will suggest
RESTART(*YES) as the *recommendation* only for your convenience; e.g. the
following doc:
<
http://pic.dhe.ibm.com/infocenter/iseries/v7r1m0/topic/cl/pwrdwnsys.htm>
_i Power Down System (PWRDWNSYS) i_
"...
_IPL source_ (IPLSRC)
Specifies whether an initial-program-load (IPL) is started from the
A-source, B-source or D-source of the system. This parameter allows you to
control which Licensed Internal Code (LIC) storage source of the system to
IPL. Also, the source of the system determines where LIC program temporary
fixes (PTFs) are applied. ...
...
It is recommended that you specify RESTART(*YES); otherwise, you cannot be
assured which source of the system is actually started. This precaution
can save you some time. ...
..."
FWiW I was under the impression from a prior [somewhat recent; months]
conversation on this forum, that there may be some IPL Attribute [per
CHGIPLA] that might enable the same effect without out the actual PwrOff.?
--
Regards, Chuck
--
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.
midrange.com
