|
I had a similar problem, which was initially hard to research.. In the end, I had to: - Check the access log for the website itself... (Looking for any kind of failure return code) - Check the Sys Op message queue for job failures... - Changed the CL program to send me a message when run with parms from the web page, and to dump the job when completed - Changed the user profile I was signing on with to have a job description that logged CL commands and generated log files Our response time was truly bad, until I increased the pre-start jobs and pre-compiled the JSP pages... We still have plenty of occasions where the job just seems to hang. You can see the QQF* job in QINTER, but it has no program running and you cannot display the job stack. If you kill that browser session, and start another, that will frequently get things going. The original hung job will stay there for quite a long time... Mike Tuckman Systems Engineer TNT Logistics North America Office: (904) 928-1516 Pager: (877) 291-0016 Text Page: 8772910016@xxxxxxxxxxxxxxxx
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.