[Info-vax] OpenVMS Development Annoyances

[Arne Vajhøj]

On 4/22/2019 12:37 PM, Kerry Main wrote:
>> From: Info-vax <info-vax-bounces at rbnsn.com> On Behalf Of 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:
>>>> 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.
> 
> Agree - they are two separate products which address two separate and
> different sets of requirements.
> 
>> Apparently someone at DEC agreed since they had both DECScheduler and
>> ACMS.
> 
> Yes.  Same for other OS platforms - they have separate products for Job
> Schedulers and TP Monitors. Neither of which are typically native to the OS.
> They are usually both addressed with commercial LP offerings from vendors.

I don't even see them target the same people.

To me a scheduler is an OPS thingy while a transaction monitor
is DEV thingy.

Arne