Service Control

VSI OpenVMS Service Control (OSC)

OSC is a management framework that makes non-cluster aware services (applications) highly available to their clients.

Non-cluster aware applications do not synchronize access to shared resources within an OpenVMS cluster. Thus, such applications can only run on one cluster member at any time. Without using OSC, or another application management software with the same functionality, a non-cluster aware application has to be restarted manually on the same or another cluster member node if it fails due to a hardware or software fault.

OpenVMS ServiceControl can monitor applications running on an OpenVMS cluster and all their required resources. If the cluster member on which an application is running fails, or if a particular required resource fails, OpenVMS ServiceControl relocates or restarts the application depending on the type of failure and the failover policy applied. OSC guarantees that if an application has to failover to another cluster member the application will only be started on a node which has the required resources and where these required resources can be activated.

Any hardware or software entity can be defined a resource, such as a disk, file system, network card (NIC), IP address, a database and/or any kind of application.

All resources of a particular type are controlled by one OSC agent. Controlling a resource means monitoring the status of a resource, bringing it online (starting) and taking it offline (stopping). OpenVMS ServiceControl provides several agents for controlling a wide range of resources (disks, shadow-sets, processes, NIC, failSAFE IP, Oracle DB …).

Due to the design of OpenVMS ServiceControl it is very simple to create a new OSC agent for a particular resource type, by providing monitor, start and stop command scripts or C functions that are compiled and linked against the OSC agent framework library.

Latest Version

3.5

Licensing

Support licenses available

Documentation