Sorry to hear about the rain at the meeting. I couldn't make it this
year. :-)
As mentioned killing Management Central is not a bad idea. You could
use WRKSYSACT and sort by IO to help confirm but it definitely looks
like a couple of things in Management Central are running amok. Chris
might not agree but I would think killing that process would not cause
any big concerns....
Michael Crump
Manager, Computing Services
Saint-Gobain Containers, Inc.
1509 S. Macedonia Ave.
Muncie, IN 47302
765.741.7696
765.741.7012 f
Consulting
If you are not part of the solution, there's good money to be made in
prolonging the problem.
This email and its attachments may be confidential and are intended
solely for the use of the individual to whom it is addressed. Any views
or opinions expressed are solely those of the author and do not
necessarily represent those of Saint-Gobain. If it did, it would be
folded, mutilated, watered down, politically corrected, and would show
up a week later if at all. If you are not the intended recipient of
this email and its attachments, you must take no action based upon them,
nor must you copy or show them to anyone.
Please contact the sender if you believe you have received this email in
error.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Friday, September 07, 2007 8:54 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Performance issue
Backup on one little 270 has been running for an extremely inordinate
amount of time. This is a test 270, one I could IPL during the middle
of
the day and not one person would notice. It's taking longer to backup
than our biggest lpar on our 570. Using the same tape drive and
connection technology. (LTO3 TS3310)
So my initial hypothesis is that some performance issue is bogging it
down.
Performance is not my bailiwick. Performance is normally handled by
throwing a big chunk of money at it until it runs right. My boss
(Chris)
is at a meeting from 8 to 3 with our BP, who is probably hoping to help
him handle performance issues on our other equipment. Don't know how
the
meeting is going, it is raining ;-)
Some information that may, or may not, be significant:
WRKSBSJOB SBS(QBATCH)
Job User Type -----Status----- Function
BACKDTALIB MASTER BATCH ACTIVE PGM-BACKDTALIB
GDIQBATCHM MASTER AUTO ACTIVE DLY-900
OPIFSGET ROB BATCH ACTIVE CMD-RTVDIRINF
QFFFFFFD4 CHRIS BATCH ACTIVE PGM-QYPSSTRT
QFFFFFFD4 CHRIS BATCH ACTIVE PGM-QYPSSTRT
QFFFFFFD4 CHRIS BATCH ACTIVE PGM-QYPSSTRT
QFFFFFFD4 CHRIS BATCH ACTIVE PGM-QYPSSTRT
What is QFFFFFFD4?
WRKSYSACT
Overall DB CPU util . . . : .0
Overall CPU util . . . . : 5.8
Total Total DB
Job or CPU Sync Async
CPU
Task User Number Thread Pty Util I/O I/O
Util
QYPSJSVR QYPSJSVR 515260 0006096E 16 .8 140 4
.0
QYPSJSVR QYPSJSVR 515260 0000000B 0 .3 125 0
.0
RMTMSAFETA 0 .3 0 0
.0
QZRCSRVS QUSER 543212 000001B8 20 .3 3 7
.0
QFFFFFFD4 CHRIS 541585 0000041B 0 .2 22 0
.0
QZRCSRVS QUSER 543256 00000018 20 .2 45 39
.0
QFFFFFFD4 CHRIS 542533 00000213 56 .2 100 0
.0
...
With frequent spikes
Total Total DB
Job or CPU Sync Async
CPU
Task User Number Thread Pty Util I/O I/O
Util
QYPSJSVR QYPSJSVR 515260 0005BC02 16 85.2 3 0
.0
...
WRKDSKSTS
Size % I/O Request Read Write Read Write %
This mailing list archive is Copyright 1997-2024 by midrange.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 on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
