Don't worry about what those do. If the job is not in a "wait" status like DEQW, DSPW, or ICFW, execute the command STRSRVJOB <job name using the CPU>. Then start debug on the last program in the stack you recognize (QAI02 it would appear) with UPDPROD(*YES). Then just ADDTRC *ALL. Chances are the program is in an endless loop and DSPTRCDTA will tell you where the loop is. Hope that helps. Donald R. Fisher, III Project Manager The Roomstore Furniture Company (804) 784-7600 ext. 2124 DFisher@roomstoreeast.com <clip> We have some users who are occasionally using a lot of CPU (relatively) for an interactive job. What is this call stack telling me? Specifcally, what is .DRVRX01, and what do modules QWSGET and QT3REQIO do? <clip>
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.