|
We had an interesting situation occur last evening. Durring month end close, we had a backup job hang in qbatch. My operator performed an end with *IMMED. The job would not terminate. Rather than seek assistance, the operator then ended Qbatch *immed. At that point Qbatch was hung for several hours. Being month end, time is somewhat of the essence, a controlled powerdown *immed restart *yes was then performed. Every thing but Qbatch and the job in question was ended prior to the poerdown. Out of all this I have two questions, 1 - what should have been done to terminate the job that was not ending? (No job log was being produced nor was there any run time. 2 - what would cause a job to hang like that? (We harrass the NT guy here for the instability from Microsoft on a PC touting the very stable 400 platform) Any assistance and or guidance would be greatly appreciated. We're running a 720 with 4.4. TIA, Bob +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.