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

[Kerry Main]

> -----Original Message-----
> From: Info-vax [mailto:info-vax-bounces at rbnsn.com] On Behalf Of Arne
> Vajhøj via Info-vax
> Sent: July 29, 2017 6:03 PM
> To: info-vax at rbnsn.com
> Cc: Arne Vajhøj <arne at vajhoej.dk>
> Subject: Re: [Info-vax] Workload manager for VMS, Should it come with
> one? (or at least a Scheduler?)
> 
> 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 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?

[snip...]

Regards,

Kerry Main
Data Center Migration Architect,
Shared Services IT Advisor
Back to the Future IT Inc.
Mobile: 613-797-4937
Office: 613-271-1943
FAX:    613-599-6261
Kerry.Main at BacktotheFutureIT.com 
http://ca.linkedin.com/in/kerrymain 

Learning from the past to plan for the future