sashton
Reputable Poster
Hi List,
Okay, here is my strange situation. Built a full PY package over the weekend. Everything finished successfully. Yesterday, Monday, morning though when I came in to work, there were 20+ jobs running in QBATCH at a status MTXW, mutex wait. I have seen that before when deploying packages while jobs are running. But I had already deployed my full PY successfully. When I looked closer, it turns out the deployment time to the AS/400 server took 3.5 hours! Way more than the usual 10 min. So I figured something must have gotten hosed in the deploy. So, I killed all the jobs running, put the job queues on hold and redeployed the full package. This time was fine, it only took 7 min instead of 3.5 hours. Now, I started to submit some jobs and they still were going to either SEMW, semaphore wait, or MTXW. This confused me. So anyhow, we ended up just IPLing the machine and bringing it back up. Once this was complete, I ran a R0006P and this time it just went to a TIMW, time wait. After about 7-8 min, it came out of time wait and finished. I thought that perhaps the package was bad, so last night, I rebuilt another full PY pacakge. Everything built fine and deployed fine with normal times. Again, all UBEs that are submitted immediately go in to TIMW and then "wake up" after several minutes and complete normally. But why? What is now causing them to all go to TIMW for such a long time. Any help would be greatly appreciated. I have attached a pdf with the screenshots of the call stack of one of the UBEs in time wait. Any idea what some of the process names are such as "jdesleepmilliseconds"?
Okay, here is my strange situation. Built a full PY package over the weekend. Everything finished successfully. Yesterday, Monday, morning though when I came in to work, there were 20+ jobs running in QBATCH at a status MTXW, mutex wait. I have seen that before when deploying packages while jobs are running. But I had already deployed my full PY successfully. When I looked closer, it turns out the deployment time to the AS/400 server took 3.5 hours! Way more than the usual 10 min. So I figured something must have gotten hosed in the deploy. So, I killed all the jobs running, put the job queues on hold and redeployed the full package. This time was fine, it only took 7 min instead of 3.5 hours. Now, I started to submit some jobs and they still were going to either SEMW, semaphore wait, or MTXW. This confused me. So anyhow, we ended up just IPLing the machine and bringing it back up. Once this was complete, I ran a R0006P and this time it just went to a TIMW, time wait. After about 7-8 min, it came out of time wait and finished. I thought that perhaps the package was bad, so last night, I rebuilt another full PY pacakge. Everything built fine and deployed fine with normal times. Again, all UBEs that are submitted immediately go in to TIMW and then "wake up" after several minutes and complete normally. But why? What is now causing them to all go to TIMW for such a long time. Any help would be greatly appreciated. I have attached a pdf with the screenshots of the call stack of one of the UBEs in time wait. Any idea what some of the process names are such as "jdesleepmilliseconds"?