Re: is operating system always to blame, was: Ready to scrap

At 09:53 AM 07/24/2000, you wrote:
>      Had an operator change a jobpty to 1 once. System became
>      non-responsive, esentially locked until the job finished. Should
>      the OS be considered at fault for accepting a valid value that
>      produced undesired results? I think not.

Just playing play devil's advocate here ...

The operating system ALLOWED the job priority to be changed to a level that 
was not reasonable.

I would like to see a warning indicating the ramifications of making such a 
change.  Heck, even NT warns you when you try to change a processes 
priority in task manager.

david

--
| Internet: david@midrange.com
| WWW:      http://www.midrange.com/david
|
| This message was written and delivered using 100%
| post-consumer (recycled) data bits.

+---
| 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
+---