Re: How to identify a runaway job

Don't know how much time you have right now, but a disk collection utility
that reports on temporary storage like Vision Director would do the trick
for you. Right now, however, I would wrkactjob, F10 to reset stats, then
refresh over a couple minutes, then look at the jobs using high cpu and
look at them first, putting on hold and see if DASD stops climbing.

Larry Ketzes
Lead Enterprise Infrastructure Engineer
lketzes@xxxxxxxxxxx
302-594-2146



From:
"Denis Robitaille" <denis_robitaille@xxxxxxxxxxxx>
To:
"MIDRANGE-L@xxxxxxxxxxxx" <midrange-l@xxxxxxxxxxxx>
Date:
07/05/2013 10:17 AM
Subject:
How to identify a runaway job
Sent by:
midrange-l-bounces@xxxxxxxxxxxx



Hello all,

We are currently facing a major problem. There is, on one of our systems,
1 or more job that is consuming disk at an alarming rate (the % used goes
up 1 percent every 5 minutes or so). We have thousands of jobs running and
we can not easily pin point the guilty one.

In the past, we got lucky some times (a badly defined SQL that we were
able to spot), and unlucky some others (IPL when the % got to high).

Does anyone can give me hints on how to spot, on the fly, the disk
consumption of a job, be that for Database IO or temporary memory space.

Thanks in advance


Denis Robitaille
Chef de service TI
Cascades Centre des technologies,
une division de Cascades Canada ULC

412 Marie Victorin
Kingsey falls(Québec) Canada J0A 1B0
T : 819 363 6130


Pour toute information sur les événements techniques, veuillez consulter
notre calendrier Groupwise CAS_CALENDRIER_TI