Re: PTF problem

Call IBM, you've worked on this enough. You pay for service - use it.

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From:
Mark Allen <scprideandms@xxxxxxxxx>
To:
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date:
02/09/2009 01:25 PM
Subject:
Re: PTF problem
Sent by:
midrange-l-bounces@xxxxxxxxxxxx



I've got the most recent cume etal, It was after the last apply I saw it
but
it may be left over from one someone else did before, I am going to try
and
load the CUME to optical sometime today/tomorrow and try and reinstall it,
gonna do the db2/Hiper and HTTP one also as they are all in not installed
status on the work ptf group display.

This was (supposed to be for me ) a normal apply the latest because we
have
our sw vendor doing some WAS stuff. (I haven't even tried to apply the
WAS
6.0 pTF's yet, just got it installed last week)

Anyways I'll give it a shot later this week

On Mon, Feb 9, 2009 at 12:56 PM, Ingvaldson, Scott <
scott.ingvaldson@xxxxxxxxxx> wrote:

Hi Mark -

This is an iSeries, being "hosed" doesn't imply that it can't be fixed.

The most likely problem is that trying to load and apply individual
PTF's created a dependancy issue that may de difficult to resolve. Did
you try installing a whole package? The current cumulative package
would probably help a lot. Using GO PTF, Option 8 with option
3=Multiple volume sets and *SERVICE should get everything back into sync
for you.

Watch for messages about "damaged" PTFs. Damaged PTFs will have to be
removed completely and then reinstalled.

Another question, are these PTFs required to fix a specific problem that
you were having? Or did someone just decide to download them?

Regards,

Scott Ingvaldson
Senior IBM Support Specialist
Fiserv Midwest



-----Original Message-----
From: Mark Allen [mailto:scprideandms@xxxxxxxxx]
Sent: Monday, February 09, 2009 11:18 AM
To: Midrange Systems Technical Discussion
Subject: Re: PTF problem

Product ID/PTF ID . . . . . . . . . . : 5722SS1 SI33896
Release . . . . . . . . . . . . . . . : V5R4M0

On order . . . . . . . . . . . . . . . : No
PTF save file . . . . . . . . . . . . : No
PTF status . . . . . . . . . . . . . . : Not applied
Latest superseding PTF . . . . . . . . : None
Status date/time . . . . . . . . . . . : 01/21/09 12:28:30
Type . . . . . . . . . . . . . . . . . : Immediate
Unattended IPL action . . . . . . . . : None
Optional part . . . . . . . . . . . . : 0003
PTF library . . . . . . . . . . . . . : QSYSDIR
Cover letter . . . . . . . . . . . . . : Yes
Mandatory instructions . . . . . . . . : No
Test Fix . . . . . . . . . . . . . . . : No
Action pending . . . . . . . . . . . . : No

and it won't apply because it needs 33895 which won't because of 31059
and 31060, like Scott said it's "Hosed"

On Mon, Feb 9, 2009 at 10:59 AM, Pete Massiello
<pmassiello-ml@xxxxxxxxxxxx>wrote:

Mark,

What is the status of SI33896 as this is superseding SI31059?

Pete

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mark Allen
Sent: Monday, February 09, 2009 10:37 AM
To: Midrange Systems Technical Discussion
Subject: Re: PTF problem

Pretty sure the last few IPLS have all been from the B side,

and all I've got is SI33895 in a save file only it won't load , it
will not load SI31060 due to SI31059 being in the incorrect state

Product ID/PTF ID . . . . . . . . . . : 5722SS1 SI31060
Release . . . . . . . . . . . . . . . : V5R4M0

On order . . . . . . . . . . . . . . . : Yes
PTF save file . . . . . . . . . . . . : No
PTF status . . . . . . . . . . . . . . : Temporarily applied
Latest superseding PTF . . . . . . . . : SI33895
Status date/time . . . . . . . . . . . : 05/23/08 01:04:01
Type . . . . . . . . . . . . . . . . . : Immediate
Unattended IPL action . . . . . . . . : None
Optional part . . . . . . . . . . . . : 0003
PTF library . . . . . . . . . . . . . : QSYSDIR
Cover letter . . . . . . . . . . . . . : No
Mandatory instructions . . . . . . . . : No
Test Fix . . . . . . . . . . . . . . . : No
Action pending . . . . . . . . . . . . : No



Product ID/PTF ID . . . . . . . . . . : 5722SS1 SI31059
Release . . . . . . . . . . . . . . . : V5R4M0

On order . . . . . . . . . . . . . . . : No
PTF save file . . . . . . . . . . . . : No
PTF status . . . . . . . . . . . . . . : Superseded
Latest superseding PTF . . . . . . . . : SI33896
Superseded by . . . . . . . . . . . . : SI33896
Status date/time . . . . . . . . . . . : 01/21/09 12:28:31
Type . . . . . . . . . . . . . . . . . : Immediate
Unattended IPL action . . . . . . . . : None
Optional part . . . . . . . . . . . . : 0003
PTF library . . . . . . . . . . . . . : QSYSDIR
Cover letter . . . . . . . . . . . . . : No
Mandatory instructions . . . . . . . . : No
Test Fix . . . . . . . . . . . . . . . : No
Action pending . . . . . . . . . . . . : No

I'll do another PWRDWNSYS with IPL from side B tonight and see what
that does, if nothing I'll get on the horn with IBM,

Thanks All, this list is wonderful...

On Fri, Feb 6, 2009 at 1:22 PM, <rob@xxxxxxxxx> wrote:

Since you're tired, did you notice I was asking about 5 and not 6?

SI33895

not SI33896?
But the IPL should address any pending actions needed.
Just make sure you specify IPLSRC(B) on your PWRDWNSYS.

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From:
Mark Allen <scprideandms@xxxxxxxxx>
To:
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date:
02/06/2009 01:11 PM
Subject:
Re: PTF problem
Sent by:
midrange-l-bounces@xxxxxxxxxxxx



Action pending . . . . . . . . . . . . : No
Action required . . . . . . . . . . . : No

it's still only in the Save file, the LODPTF won;t work, and dang I
searched on special instructions but didn't see anything thanks for
the link, I'll take a look

On Fri, Feb 6, 2009 at 11:52 AM, <rob@xxxxxxxxx> wrote:

DSPPTF LICPGM(5722SS1) SELECT(SI33895) What do you have for Action

pending . . . . . . . . . . . . :
Action required . . . . . . . . . . . :

See also "Special Instructions" at:

http://www-912.ibm.com/a_dir/as4ptf.nsf/a18db68aae4a7d81862566ba005d14
5c/d38
d2a9f5b2fe7728625753800633611?OpenDocument&Highlight=2,si33895<http://
www-912.ibm.com/a_dir/as4ptf.nsf/a18db68aae4a7d81862566ba005d145c/d38%
0Ad2a9f5b2fe7728625753800633611?OpenDocument&Highlight=2,si33895>

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From:
Mark Allen <scprideandms@xxxxxxxxx>
To:
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date:
02/06/2009 11:26 AM
Subject:
Re: PTF problem
Sent by:
midrange-l-bounces@xxxxxxxxxxxx



APYPTF LICPGM(5722SS1) RLS(V5R4M0) DELAYED(*YES)

PTF 5722SS1-SI33896 V5R4M0 not applied. PTF 5722SS1-SI33895
V5R4M0 required.

On Fri, Feb 6, 2009 at 10:11 AM, Pete Massiello
<pmassiello-ml@xxxxxxxxxxxx>wrote:

Mark,

Read the message carefully is it asking for SI31060 to be

Perm applied first? I have seen that before. The message will
tell you

that.

Also, have you tried doing a APYPTF *ALL *TEMP
DELAY(*YES) and

doing

an IPL and seeing if it will apply during an IPL?

Pete

Pete Massiello
iTech Solutions
http://www.itechsol.com

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mark Allen
Sent: Friday, February 06, 2009 8:53 AM
To: Midrange Systems Technical Discussion
Subject: PTF problem

I "inherited" this problem and for the life of me don't know how

it

got

in

this state or how to fix it.


SI33896
Product ID/PTF ID . . . . . . . . . . : 5722SS1 SI33896
Release . . . . . . . . . . . . . . . : V5R4M0

On order . . . . . . . . . . . . . . . : No
PTF save file . . . . . . . . . . . . : No
PTF status . . . . . . . . . . . . . . : Not applied
Latest superseding PTF . . . . . . . . : None
Status date/time . . . . . . . . . . . : 01/21/09 12:28:30
Type . . . . . . . . . . . . . . . . . : Immediate

Try and apply it and it says it needs SI33895 It is in a save
file and when I try to apply SI33895 I get the msg

that

it

needs SI31060 yet it's applied????

SI31060
Product ID/PTF ID . . . . . . . . . . : 5722SS1 SI31060
Release . . . . . . . . . . . . . . . : V5R4M0

On order . . . . . . . . . . . . . . . : Yes
PTF save file . . . . . . . . . . . . : No
PTF status . . . . . . . . . . . . . . : Temporarily applied
Latest superseding PTF . . . . . . . . : SI33895
Status date/time . . . . . . . . . . . : 05/23/08 01:04:01
Type . . . . . . . . . . . . . . . . . : Immediate



What am I missing? I've looked/searched and not finding

anything.

Thought

I'd ask here BEFORE I called IBM......
--
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.



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



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