Re: How to identify a runaway job

[Martin Rowe <dbg400.net@xxxxxxxxx>]

Hi Denis

We used to get this a lot with rogue SQL session from PC clients. I wrote a
background utility to watch for disk use increase and send a message to
QSYSOPR if it passed a set threshold. It also checks temporary storage per
job, and CPU per job. You can tweak it to fit your circumstances - code is
at http://www.dbg400.net/foswiki/bin/view/DBG400/DasdMon

Regards, Martin


On 5 July 2013 15:17, Denis Robitaille <denis_robitaille@xxxxxxxxxxxx>wrote:

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