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

[Arne Vajhøj]

On 7/29/2017 8:22 PM, Kerry Main wrote:
>> -----Original Message-----
>> From: Info-vax [mailto:info-vax-bounces at rbnsn.com] On Behalf Of Arne
>> Vajhøj via Info-vax
>> On 7/29/2017 5:26 PM, Kerry Main wrote:
>>>> -----Original Message-----
>>>> From: Info-vax [mailto:info-vax-bounces at rbnsn.com] On Behalf Of IanD
>>>> via Info-vax
>>>> In the stone age we started with the VMS batch subsystem
>>>
>>> Its not a stone age concept. Batch files are an integral component of
>>> any modern OS offering.
>>
>> "in the stone age" = many years ago aka place in timeline
>> "stone age concept" = old fashioned concept aka obsolete
>>
>>>> Then evolved to scheduler tools, such as CA scheduler and DEC
>>> scheduler
>>>>
>>>
>>> No - schedulers are tools that automate the "scheduling" of batch jobs.
>>>
>>> Two different components.
>>
>> True. But one build on the other.
> 
> But they are not dependent on each other.

A schedule needs something to run the things that has been scheduled.

> A job scheduler is also used to schedule backups, AV, file transfer and
> app/db maint jobs. In most cases, these jobs are integrated with
> pre/post job processing code.
> 
> As an example, if a scheduled AV job finds a virus, do you really want
> to ignore this and allow a scheduled backup job to run with this virus
> included?
> 
> Or would you prefer that on detection of a virus, the post processing
> sends an alert to page someone and subsequently prevents the backup of
> that system from taking place?

The scheduler may have dependencies between jobs.

But that does not change that it need to have a way to run things.

Arne