[Info-vax] Workload manager for VMS, Should it come with one? (or at least a Scheduler?)

[IanD]

In the stone age we started with the VMS batch subsystem

Then evolved to scheduler tools, such as CA scheduler and DEC scheduler

The rest of the world has moved on to workload management systems now, even enterprise and across systems ones too

Then in VMS land we went backwards, DEC scheduler stopped running on newer versions of VMS probably some 10 years ago

Having to roll your own scheduler on VMS one is painful and often requires lots of DCL wrapper code just to get simplistic management happening. Relying upon an external scheduler like JAMS on another platform has issues too if one wants to go off the platform and onto another reservation!

It seems to me a fairly important aspect of an OS to have a native reliable scheduler system (a workload management would of course be even better) but in VMS land we at still at the evolution stage of pre-warp technology, i.e. batch jobs

The batch job entries are individualistic in nature, they are not associated with other entries and/or cannot be rolled up into separate classes etc making their management even more painful.

Should an OS like VMS come with a workload management system or at least a scheduler system that supports inter job dependencies and other such goodies? 

Is the VMS vision to evolve to a system that will support workload management naively under some type of framework or are we distend to forever fight the job enemy with just the batch queue bow and arrow?