[Info-vax] OpenVMS Development Annoyances

[Arne Vajhøj]

On 4/21/2019 10:23 AM, seasoned_geek wrote:
> On Friday, February 8, 2019 at 3:58:07 PM UTC-6, Stephen Hoffman wrote:
>>
>>>> There's no job scheduler.  Yes, I'm aware of the add-ons.  No, batch
>>>> isn't a scheduler.  Batch was good enough and was useful for what we
>>>> were doing back in the early VAX era, but our needs have changed.
>>>
>>> What exactly do you need from a job scheduler ?
>>
>> I'd like to have a way to register an app for startup, and to register
>> callbacks when the app tips over, to automatically try a few restarts
>> but avoid a crash-loop, to collect failure-related data, and a way to
>> check if a certain app is running via API and via shell.  And I'd
>> prefer to not to poll process names.  Fairly standard stuff.  Is it
>> running?  Why not?  Can it restart?  Can I get a notification when some
>> part of production tips over?  Where do I send my run-time logs, and my
>> error-, failure-, and event-related logging?
>>
> 
> You've basically described what ACMS does. It will even give you
> throttle control, allowing you to set minimum and maximum numbers for
> task servers.

I would have considered a job scheduler and a transaction monitor
to be two different things.

Apparently someone at DEC agreed since they had both DECScheduler
and ACMS.

I will leave it to Steve to comment on whether he thinks ACMS
is a good fit for his requirements.

Arne