RE: Loading TR9 on V7R1 - Performance Issues!

Kenneth,

I have some addition info, but not a performance issue.
I applied TR9 and latest CUM to 2 LPARs last night.
The 1st LPAR, MF99009 was already applied, all went as expected.

The 2nd LPAR, MF99009 was included to be applied with the other PTFs
The below messages occurred, several of the CPF36BD, during option 8, load from service.
Before I did my PWRDWNSYS, I had many PTFs that were still in *SAVF status, not loaded, nor set to be applied.
During the PWRDWNSYS, watching the IPL process, these PTFs that were not loaded did get loaded and applied.
I expected another PWRDWNSYS would be need to load and apply these missed PTFs, but that was not the case.

CPF3611 Diagnostic 40 11/19/14 22:04:53.966714 QPZINSFX QSYS 16AE QPZPTFIN QSYS 0602
Message . . . . : PTF 5770999-MF99009 V7R1M0 requires IPL.
Cause . . . . . : PTF 5770999-MF99009 V7R1M0 must be permanently applied
before the remaining PTFs can be loaded and applied. PTF 5770999-MF99009
V7R1M0 is a technology refresh requisite PTF required by one or more of the
PTFs being loaded. Recovery . . . : Perform a normal mode IPL to the B
IPL source and then try the request again.

CPF362E Diagnostic 40 11/19/14 22:04:53.969464 QPZINSFX QSYS 1729 QUICMENU QSYS 00C1
Message . . . . : IPL required to complete PTF install processing.
Cause . . . . . : At least one PTF requires an initial program load (IPL) to
complete the PTF install processing. This includes one or both of the
following: -- A technology refresh PTF or its requisite PTFs requires an
IPL. A technology refresh PTF must be permanently applied before the
remaining PTFs can be loaded and applied. -- One or more special handling
PTFs or its requisite PTF requires an IPL. There are special handling PTFs
defined in a PTF group being installed that must be applied before the
remaining PTFs in the PTF group can be applied. Recovery . . . : Perform
a normal mode IPL from the B IPL source to complete the PTF install. During
the next unattended IPL, the remaining PTFs will be installed. If an IPL is
required for a technology refresh PTF, device *SERVICE and image catalog
*NONE will be used to load the additional PTFs during the next IPL. See the
previously listed messages for PTFs that require an IPL.

CPF36BD Diagnostic 30 11/19/14 22:48:03.295954 QPZLPC QSYS 110F QPZINSFX QSYS 0845
Message . . . . : PTF MF99009 prevented load of PTF MF58863.
Cause . . . . . : The program temporary fix (PTF) 5770999-MF58863 being
loaded has a technology refresh requisite PTF 5770999-MF99009. The
technology refresh PTF 5770999-MF99009 or its superseding PTF is not
permanently applied. Recovery . . . : Do one of the following, and then
try the Load PTF (LODPTF) command again: -- Specify *APYPERM for the
superseded PTFs (SPRPTF) parameter. For Licensed Internal Code PTFs, the
system must be operating on the B IPL source. -- Permanently apply (APYPTF
command) PTF 5770999-MF99009 or its superseding PTF.

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Graap, Kenneth
Sent: Wednesday, November 19, 2014 10:11 PM
To: Midrange Systems Technical Discussion
Subject: RE: Loading TR9 on V7R1 - Performance Issues!

That's why what happened is so strange. Setting the PTF as *DLYALL shouldn't have changed anything at all on the system. But having what happened so soon after applying these PTF's delayed seems more than just chance.


Message ID . . . . . . : CPI362F Severity . . . . . . . : 00
Message type . . . . . : Information
Date sent . . . . . . : 11/18/14 Time sent . . . . . . : 13:10:48

Message . . . . : PTF installation process started.
Cause . . . . . : This message is sent to the QHST log when a PTF
installation process is started. The following installing options were used:
-- PTF menu option 2
1=Select products option 7
2=All products option 8
3=Install PTF (INSPTF) command
-- Install type *DLYALL
-- Device name *SERVICE




Message ID . . . . . . : CPC3D87 Severity . . . . . . . : 00
Message type . . . . . : Completion
Date sent . . . . . . : 11/18/14 Time sent . . . . . . : 13:19:40

Message . . . . : Loading of PTFs completed successfully.
Cause . . . . . : Processing to store PTFs on the system in preparation for
applying them has completed successfully.



I'm telling you, this was a dramatic and immediate performance meltdown.

From Performance Tools, immediately BEFORE the meltdown (13:25 to 13:50):

CPU Job Tns Average Disk
Date Time Util Count Count Response I/O
11/18/14 13:25:00 47.40 2458 2523 .08 504842
11/18/14 13:30:00 45.56 2311 2986 .07 464335
11/18/14 13:35:00 64.93 2153 3011 .11 791395
11/18/14 13:40:00 61.55 2173 3091 .10 735801
11/18/14 13:45:00 53.89 2499 2878 .36 808631
11/18/14 13:50:00 48.93 2628 2718 .47 603441


Immediately AFTER the meltdown (13:55 to 14:20):


CPU Job Tns Average Disk
Date Time Util Count Count Response I/O
11/18/14 13:55:00 39.22 2676 1675 6.83 653187
11/18/14 14:00:00 59.95 2515 2098 1.79 1359376
11/18/14 14:05:00 29.23 1902 1740 6.94 502435
11/18/14 14:10:00 28.06 2184 1810 2.32 273721
11/18/14 14:15:00 37.60 2387 1445 7.82 1008579
11/18/14 14:20:00 35.02 2192 1467 6.30 578398




Reply or Forwarded mail from: Kenneth E Graap


-----Original Message-----

I didn't use the "Immediate" option. I set all to delay until the next IPL.

Reply or Forwarded mail from: Kenneth E Graap

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