Re: WLM init without scheduling environment

One point of clarification: while Scheduling Environments primarily
determine where a job will run, they can also determine by extension
*whether* a job will run. That is, one use of SE is to hold up jobs that
need some resource that is (presumably) temporarily unavailable. In our
shop, we use SE to 'stop tape processing' during certain periods of
hardware or software maintenance. Since Scheduling Environments rest on
'abstract resources', you can use them to control job execution based on
any feature of your installation that you can define and relate to a
virtual on-off switch.

An SE that is totally unavailable might represent a mistake, but it might
also represent an additional level of control.

.