RE: Loading TR9 on V7R1 - Performance Issues!

What TR level were you at prior?
What CUM level were you at prior?
MF9900* status?

MF99009 Permanently applied
MF99008 Permanently applied
MF99007 Permanently applied
MF99006 Permanently applied
MF99005 Permanently applied
MF99004 Permanently applied
MF99003 Permanently applied
MF99002 Permanently applied

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.