So, I've got this CREATE TABLE query with a select that has three joins,
and simple selections in the primary table as well as in one of the joined
tables. The query is in a RUNQRY command, which is in a CLLE program. The
program was submitted 40 minutes ago. It took about two minutes for the
indexes to be built, before I saw (via WRKJOB) records being added into the
created table. It took about 5 - 7 minutes to get to just over 5 million
records in the new table, and then the I/O counts on WRKJOB's Display Open
Files screen came to a complete stop. Meanwhile, the CPU time used
continues to climb at a nice pace. The system seems to be giving all of
its resources to my job, which is showing my job taking 547% of the CPU,
while the system as a whole is at 594%. DASD's at 41% used.
Interestingly, the DB Faults and Pages on WRKSYSSTS are zero for all pools,
and this is after about 2 minutes of data collection. I would have
expected the DB Pages to be maxxed out, given how much CPU my job is taking.
Not sure where else to look. Any ideas would be appreciated.
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.