Not sure what you mean. Talking about the QTEMP library usually means that you are concerned about disk consumption by temporary objects. CPU time is not attributable at an object level. CPU is consumed by programs. They do perform I/O that affects data in files including the QTEMP library. If you are purely looking to see what jobs are consuming the most DASD in QTEMP at any moment in time, use option "14. Temporary Storage" from the "EZRAD WORKPERF" menu. This feature shows you all active jobs on the system - similar to the WRKACTJOB command. It shows the current temporary storage and size of QTEMP for each active job. You can sort by either of these to find the jobs you are looking for.

If you are referring more to wanting to know how much CPU was consumed performing I/O on specific files, you will need to use our Query Optimizer (for SQL jobs) and our Application Optimizer (for RPG, CL, COBOL, C, JAVA, etc..)