|
Peter, What if there is that outside chance that a job in normal operation could write xxxxx number of records or utilize more than 70% of the CPU. If the OS stopped it, it would be considered a bug in the OS. I know that a program that would suck that many machine cycles would be extremely bad design, but I'm sure that somewhere they exist. (Albeit, not in my shop. HA,HA,HA). I think we'll have to agree to disagree on this one. Mark -----Original Message----- From: Peter Dow [SMTP:pcdow@yahoo.com] Sent: Wednesday, July 26, 2000 5:08 PM To: MIDRANGE-L@midrange.com Subject: Re: is operating system always to blame, was: Ready to scrap an AS/400 Hi Mark, Sorry, but I disagree. The operating system is in control. Or should be. Why do you say "it can only warn someone"? If it can warn someone, why can't it put the offending job on hold? Do you think the OS doesn't know which job is filling up the disk? Is it impossible to put a job on hold? I'm not even sure you need the OS to handle that situation -- someone else on the list was asking for monitoring software that would detect when a job was at 70% CPU utilization and several solutions were mentioned. I see no reason why those same packages couldn't monitor disk usage and hold the offending job until some human intervenes. If monitoring software could do it, so could the OS. Peter Dow Dow Software Services, Inc. 909 425-0194 voice 909 425-0196 fax From: Mark Walter <mwalter@netrax.net> > Say the program loops and writes records into a data file of some sort, > the procedure fills up the disk. This can happen by the way. An AS/400 > query with improper joins specified will also fill up disk. The cannot know > what is filling up the disk, it can only warn someone that the disk is > reached its threshold. Eventually, the machine will fail. I'd say that this > is not the fault of the OS. > +--- > | 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 > +--- __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com +--- | 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 +--- +--- | 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.