MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » December 2012

RE: Having trouble with PTFs



fixed

We hadn't updated the system since we installed it and the cume available at
the time of install (maybe 2 years ago).
Frankly, this all started with a support request to IBM for a failure on
multiple systems of a certain IBM command. Turns out our SWMA had expired
(no notice from IBM to renew). So we had to renew that and then they asked
for a WRKPTFGRP printout. They refused to look at our issue unless our
development system was brought up to date on PTFs. Regardless that the same
issue is appearing on our v5r4 box and v5r3 partition.
Anyway, I downloaded the cume, HIPER, DB, and TR5 PTF direct to my system
(which appear as save files in QGPL). There was no ISO nor any image
catalogs.


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jack Kingsley
Sent: Tuesday, December 11, 2012 8:25 AM
To: Midrange Systems Technical Discussion
Subject: Re: Having trouble with PTFs

How old were the ptfs that you had on this machine prior to starting, not
sure if that would matter. You mentioned you downloaded the ptf's, how many
ISO's did you end up with. Did you do a verify *PTF on your image catalog,
curious if that would show anything worth while.

On Tue, Dec 11, 2012 at 9:17 AM, Thomas Garvey <tgarvey@xxxxxxxxxx> wrote:

This is an E4B which started out with v7r1. And we DID do the
Allocate Additional Space during the install. I think there was a PTF
that was needed to do a similar process before this cume was applied,
and that PTF was superseded. The superseded PTF was also checked.
Also, the superseded PTF was included in the cume, I think. Confusing.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim Oberholtzer
Sent: Tuesday, December 11, 2012 8:06 AM
To: Midrange Systems Technical Discussion
Subject: Re: Having trouble with PTFs

Pure speculation on my part at this point but: Was this machine
upgraded from earlier releases? If so was the step "Allocate
Additional Space for LIC" actually performed from the Prepare for
Install menu? It does require some additional downtime on the next
IPL, and it's not always needed, so many times it's overlooked.

I also wonder if it might work in this instance. Run it for V7R1M0?

The save file approach vs. the image catalog should not make a
difference in the process. It's merely a different way to approach
the PTF installation.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On 12/11/2012 7:55 AM, Thomas Garvey wrote:
I had read here that several folks had applied the cume and TR5
without trouble, but maybe there's a difference between doing it
from an optical image, rather than save files downloaded from the
Fix Central site (which is what I did).


-----Original Message-----
From:midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim
Oberholtzer
Sent: Tuesday, December 11, 2012 6:43 AM
To: Midrange Systems Technical Discussion
Subject: Re: Having trouble with PTFs

I have seen this too. MF99005 is a pre-requisite and co-requisite
to quite a few PTFs. It can be loaded individually as Rob points
out, and most definitely needs an IPL.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On 12/11/2012 6:32 AM,rob@xxxxxxxxx wrote:
I had my own trouble with PTF's this last week. On several
lpars I had ran APYPTF LICPGM(5770999) APY(*PERM) DELAYED(*YES)
and then loaded and set MF99005, TR5, cume and a bunch of groups
to apply at the next IPL. Failed. Had to do this in two steps
APYPTF
LICPGM(5770999) APY(*PERM) DELAYED(*YES) and then loaded and set
MF99005 IPL do the rest IPL again.

Many were pretty insistent that MF99005 be applied before
continuing.


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 46755http://www.dekko.com
--
--
--
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