Re: Cumulative PTF w/o Technology Refresh

Was that APYPTF *PERM followed by an IPL -before- you tried to load TR6?


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: Roberto José Etcheverry Romero <yggdrasil.raiker@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>,
Date: 05/16/2013 07:28 AM
Subject: Re: Cumulative PTF w/o Technology Refresh
Sent by: midrange-l-bounces@xxxxxxxxxxxx



Rob, first step before doing anything was doing an APYPTF *PERM on all
products. Still wasnt enough. In any case i blame the IBM i ftp server,
it's not the first time it drops a transfer and then mangles the image. I
should have restarted instead of appended those images.
In any case it's weird since i dont see a LIC ptf having an ClientAccess
ptf as pre or co-req. And they all got loaded after a few tries.
Come saturday i'll test all theories again.
Thanks!



On Thu, May 16, 2013 at 8:16 AM, <rob@xxxxxxxxx> wrote:

I believe that the cover letter for one the the TR's between 3 and 6
stated something to the effect of "make sure you have all ptfs

permanently

applied prior to loading this one". Once you get current on TR's they
tend to do this automatically for you.


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: Roberto José Etcheverry Romero <yggdrasil.raiker@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>,
Date: 05/15/2013 03:40 PM
Subject: Re: Cumulative PTF w/o Technology Refresh
Sent by: midrange-l-bounces@xxxxxxxxxxxx



Just yesterday i had that process fail:
7.1 @ TR3
Downloaded lastest cume and all groups. 7 images in total (2 for the

CUME

and 5 for the rest).
Got them onto the clients machine (a POWER5 520)
In the middle of the transfer ftp suffered a couple of disconnections (i
blame this for some of the trouble) but size was consistent.
After doing go ptf option 8, most ptfs got loaded BUT not applied, one
5770XH2 ptf failed with some signature problem (i ordered it just to be
safe).
I dont know if that ptf was the cause, but in the end, no auto ipl, no

lic

ptfs set for install.
I went around and did some apyptf with prereq *yes and got the marker

for

TR6 applied (mf99006 IIRC). After that and some other mucking around
setting some random ptfs to install i ran thru the catalog again and

this

time some more ptfs got loaded and applied.
The only missing ptf was that one for XH2.
Saturday i have to repeat that on the prod machine (a faster, i hope,
POWER7) and we'll see what caused those troubles.
Ah, selecting ALL groups for 7.1 ammounts to 26Gb total. Fixcentral

likes

to inflate values sometimes (i suppose it has totals for every ptf +
prereq
that get pruned when building the images).

Best Regards



On Wed, May 15, 2013 at 4:09 PM, Jim Oberholtzer <
midrangel@xxxxxxxxxxxxxxxxx> wrote:

Others have responded but the answer is absolutely in fact that's the
preferred method.

Load up the image catalog, verify it, and use option 8 from the PTF
menu. If your back on PTFs a bit, this is going to take "some
minutes" as Larry likes to say. You will also see several IPL
actions. Depending on the level you may even be prompted to do an IPL
manually, but I don't always see that.

One word of caution: Rob's right, it might be easier to order the

media

and load the image catalog from DVD. There is about 60GB of data in
them thar groups.........

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On 5/15/2013 1:52 PM, Steinmetz, Paul wrote:

I'm being asked to relay a couple questions.
Can the PTFs listed below by Jim all be applied via an Image

Catalog?

Can they be queued up (so to speak)?

-Kurt
-----Original Message-----
From:midrange-l-bounces@xxxxxxxxxxxx [mailto:

midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim Oberholtzer

Sent: Wednesday, May 15, 2013 10:04 AM
To: Midrange Systems Technical Discussion
Subject: Re: Cumulative PTF w/o Technology Refresh

Kurt,

I agree with your partners request, I would make the same one. That

said, if you have seen no improvement, I suspect a different problem

than

PTFs. Is this an LPAR box? Was the LPAR profile changed to use the

extra

processor? Is there a high limit on the processor that is less than

(I

think two based on your description) the number of processors you had
before adding one?

Yes, you can apply the cumulative and then go back and apply the

group

for the TR later; But I highly suggest that in addition to the

Cumulative

you apply the following list of groups as well:

PTF Group Text
SF99710 CUMULATIVE PTF PACKAGE C3037710
SF99709 GROUP HIPER
SF99708 GROUP SECURITY
SF99705 HARDWARE AND RELATED PTFS
SF99701 DB2 FOR IBM I
SF99627 7.1 ELECTRONIC SERVICES GROUP PTF
SF99572 JAVA
SF99368 IBM HTTP SERVER FOR I
SF99367 TCP/IP PTF
SF99366 PRINT PTFS
SF99362 BACKUP RECOVERY SOLUTIONS (even if you don't

use

BRMS this is where all the save/restore PTFs are)
SF99145 PERFORMANCE TOOLS (if you have them)

The TR is SF99707 TECHNOLOGY REFRESH

The HIPER, and Hardware ones are the ones I would find most

important

in

this case, however if your taking the time to apply any Group you

might

just as well get the entire batch. I'm not sure why you would not
want the TR group as well, unless there is something in the cover

letter

that leads you to believe there is going to be a problem.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects

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


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