|
Thanks to all who responded. Lots of good ideas. For those of you who care........... I called IBM hardware support. They verified that there was no indication in the error logs of an impending disk problem. After sorting through the system log for a while, I found a COBOL program that seemed to be active about the time we were having the problem. It turned out to be the result of a poor coding technique. I am no COBOL programmer, so I cannot explain the significance of this, but the offending program was issuing an INITIALIZE command before every READ file command. After removal, everything fell back into reasonable limits. Thanks again. Phil +--- | 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.