[Info-vax] Restrict the use of SUBMIT/USER= to one particular user.

David Froble davef at tsoft-inc.com
Thu Nov 10 14:35:18 EST 2016


Stephen Hoffman wrote:

> and we all end up writing our own 
> requeuing and resubmission tools, duplicate job prevention and 
> detection, and other such, and then there's the lack of provision in 
> OpenVMS for scheduling jobs across clusters, and then there's that the 
> queue manager system service API is... baroque... at best, and very 
> limited in what it provides.

This is the part that I'd like to address.  Just what's wrong with people 
designing and implementing their own solutions?  I'm not going to believe that 
only the OS developers can do well with this task, nor that they understand 
everyone's requirements.

Yes, things can be improved, and they should be improved.

But I don't expect any OS to include for example, Accounts Payable, Accounts 
Receivable, Inventory control, General Ledger, Order processing, Orbital 
mechanics, FTL navigation, Web Server, Email, Browser, ....  (Add your apps)

And if it did, most likely the apps would not fit everyone's needs.

So, where do you draw the line?  Regardless of where, one size will not fit all.

What an OS can attempt to do is provide some generic capabilities, and tools for 
users to develop their own requirements.  But even then, such isn't really part 
of the OS.



More information about the Info-vax mailing list