Re: AW: Monitoring runaway jobs (was Re: Oh where has my disk space g one?)

[Martin Rowe <martin@xxxxxxxxxx>]

On Monday 19 November 2001 9:09 am, oliver.wenzel@cibavision.novartis.com
wrote:
> Martin,
>
> I'm also looking for some automatic means to find these runaway jobs.
> I've had 2 or the 3 of these excessive queries
> with up to 20GB of temp storage.
>
> I guess I'll first set the maxstg parm in the user profile to something
> else than *nomax.
>
> Does anybody know where to set limits for files created by queries?
>
> OLiver

Hi Oliver

The problem as I see it is that temp storage doesn't seem to be limited
by the max storage parm :( Our query users have specific profiles for
running queries, and these already have maxstg set (5Gb from memory) -
and temp exceeds that. The routine I wrote can pull out the interim temp
storage objects (access paths etc) that query builds dynamically, but not
'real' QTEMP objects generated by programs & the like.

I'll stick what I've got so far on my site, and if I ever find out how to
get the QTEMP info, I'll update it.

Regards, Martin
--
martin@dbg400.net  jamaro@firstlinux.net  http://www.dbg400.net        /"\
DBG/400 - DataBase Generation utilities - AS/400 / iSeries Open        \ /
Source free test environment tools and others (file/spool/misc)         X
[this space for hire]  ASCII Ribbon Campaign against HTML mail & news  / \