Not necessarily. QAI02 may execute other programs that could have caused the problem or the job stream may be designed in such a way that QAI02 is executed after the offending program. I would start with the program after QCMD and determine what programs are called to determine how QAI02 is executed and what is executed from QAI02. Eventually, you may find your answer. Hope that helps. Donald R. Fisher, III Project Manager The Roomstore Furniture Company (804) 784-7600 ext. 2124 DFisher@roomstoreeast.com <clip> The program was in DSPW state - this was a result of running wrkactjob in batch selecting all interactive users with cpupct > 1.0. So I assume QAI02 was really the offending program? <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.