×

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.




Most of the time when reviewing batch jobs which seem to take an
inordinate amount of time the goal is to reduce I/O's.
My best example was a developer who coded this

Clear summary file;
Read detail file
Try to update row in summary file, if update fails try write
next

Extreme numbers of I/O to summary file. Changed to

Read detail file in order of desired summary rows;
sum total in memory
at control break time write out the total to summary file

Shaved off an hour.

In your case you could look at a number of things.
TRCJOB for one.

Another thing to look at is
select system_table_schema, system_table, system_table_member,
open_operations, close_operations, insert_operations, update_operations,
delete_operations,
...
from qsys2.syspartitionstat
where system_table in ('FROMFILE', 'TOFILE')
https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_73/db2/rbafzcatsyspstat.htm
Run that before and after the batch job.


Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2026 by midrange.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 on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.