×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
%busy
Are the IO counts for ACTIVE_JOB_INFO cumulative?
Thanks
-----Original Message-----
From: Rob Berendt [mailto:rob@xxxxxxxxx]
Sent: Thursday, April 18, 2019 10:30 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: Job behind disk utilization?
I'm trying to determine if you mean %busy or %full.
If you want to find jobs with lots of I/O, that's pretty easy.
Look at ACTIVE_JOB_INFO and sort by these columns:
ELAPSED_TOTAL_DISK_IO_COUNT
ELAPSED_ASYNC_DISK_IO_COUNT
ELAPSED_SYNC_DISK_IO_COUNT
Temporary storage (from ACTIVE_JOB_INFO still) PEAK_TEMPORARY_STORAGE
For really looking into temporary storage look at:
QSYS2.SYSTMPSTG
http://ibm.biz/DB2foriServices
Now, if you want to find out who has been writing a lot of rows to your tables, over an extended time period, and you don't care if the job is active or not, then you'll have to journal your tables and use stuff like QSYS2.DISPLAY_JOURNAL
midrange.com
