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
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 mailing list archive is Copyright 1997-2013 by MIDRANGE dot 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 here. If you have questions about this, please contact