Tom, I think this is completely out of scope for your proposed
changes, but what I would
really like to see is an automated
scheduler that understands
dependencies. So you could say
things like, "Run this job once those other two jobs completed
successfully and returned status code 'foo'."
I'm not thinking about just reports here, but rather, also scheduled
data collection, manipulation and maintenance of batch data feeds,
that sort of thing - in short, automation of all sorts. Here are some
made up examples: "Get the current bid and ask prices of IBM every 10
minutes."; "Every month, roll over futures to the new contracts, then
remind the humans."
Likely the Workflow package would be a very useful there, but I
haven't used it yet so I can't really say.
Also, there are various other unix systems out there that have a model
of dependencies (various replacements for System V style init boot
scripts, etc.), but I don't know how any of those approach the
problem, or if they're relevent.