|
Booth, In a message dated 97-08-30 19:22:37 EDT, you write: > It has just dawned upon me that there must be a reason that one of the > machines that I work on has a very slow response time for the WRKSPLF > command. Other response times on that machine are generally ok, but > WRKSPLF is just plain slow. Any ideas? Sounds like: A. You just have a DARN awful lot of spooled files/user on that machine. B. You haven't done a RCLSPLSTG on that machine in a while, and your average usage is less than it was on the days that generated the usage. C. You command defaults for WRKSPLF have been changed. Not too terribly long ago, our 320 was LOCKED DOWN when somebody accidentally typed WRKSPLF *ALL. The machine didn't move until the aforementioned job was terminated... HTH, Dean Asmussen Enterprise Systems Consulting, Inc. Fuquay-Varina, NC USA (Between Raleigh and Research Triangle Park) E-Mail: DAsmussen@AOL.COM "Hospitality is making your guests feel at home, even though you wish they were." -- Anonymous +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to "MIDRANGE-L@midrange.com". | To unsubscribe from this list send email to MAJORDOMO@midrange.com | and specify 'unsubscribe MIDRANGE-L' in the body of your message. | 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.