HP Operations Manager for Windows

ovc


NAME

ovc

- perform actions on local components.

SYNOPSIS 

ovc  -h|-help 

ovc  -start [<target> ... ] [-boot]{[-async]|[-verbose]} 

ovc  -stop [<target> ... ][-nostart]{[-async]| [-verbose]} 

ovc  -restart [<target> ... ] 

ovc  -kill [-verbose] 

ovc  -status [<target> ... ] [-level <level>] 

ovc  -notify <event> [<target> ...] [-value <value>] 

ovc  -version

DESCRIPTION

The ovc command controls the starting and stopping, event notification, and status reporting of all components registered with the HP Operations control service.

A component can be a server process belonging to any of the products, such as HP Operations Manager for Windows (HPOM for Windows), HP Operations agents (for example, the Performance Agent or the Discovery Agent), an event interceptor, or an application delivered by an integrator. Each component must have an associated registration file providing HPOM with configuration and process information about the component. For more information about registration, refer to ovcreg(1).

A target can be either a component or a group of components, defined as a category. The ovc command first tries to initiate action on the category specified in target. If the category called target is not found, ovc then tries the individual component called target. Note that a category name may not match any component name.

The HP Operations control daemon or service automatically restarts any component that terminates unexpectedly if the AutoRestart option in the registration file of the component is set to true. If you stop the HP Operations control daemon or service using the -kill option, all registered components are stopped as well.

Parameters

The ovc command recognizes the following options:

-h|-help
Displays all available options for the ovc command.

-start [<target> ... ] [-boot]{[-async]|[verbose]}
Starts the selected components. The <target> option specifies a component or category. If you do not use <target> , all components are started. If you do not use -boot, only components that start at boot time are started.

The -async option starts the components asynchronously. If you use the -verbose option, the ovc command displays the progress of the command execution. You can use the -async or the -verbose option, but you may not include these options together in a command.

-stop [<target> ... ] [-nostart]{[-async]|[verbose]}
Stops the selected components. The <target> option specifies a component or category. If you do not use <target> , all components are stopped except those components that belong to the CORE component group. If you specify the -nostart option, and if the control daemon is not running, the command does not perform any action. If you do not specify the -nostart option, the ovc -stop command starts the control daemon, and ovbbccb components if these components are not running. The -async option starts the components asynchronously. If you use the -verbose option, the ovc command displays the progress of the command execution. You can use the -async or the -verbose option, but you may not include these options together in a command.

-restart [<target> ... ]
Stops components before they are restarted. The <target> option specifies a component or category. If you do not use <target> , all components are stopped and restarted.

-kill [-verbose]
Stops all components registered with the HP Operations control service. If you use the -verbose option, the ovc command displays the progress of the command execution.

-notify <event> [<target> ... ] [-value <value>]
Sends notification of an event with the value of <value> to the component or category specified by the following:

<target> ...

You can specify the <value> to the component that generates the event (event generator) and that sends the event-related information to all components that request the event information (event subscribers). If you do not use <target>, the event notification is sent to all components. If you do not use <value>, only the event notification is sent.

-status [<target> ... ] [-level <level>]
Reports the status of a component or category specified by <target>. The status report contains the component's label, description, category, process ID, and STATE. Components can be in one of the following states: Stopped (0 in numeric format), Starting (1), Initializing (2), Running (3), Stopping (4), N/A (5), or Aborted (6). If you do not specify <target>, the status of all components is returned.

The <level> option specifies the type and quantity of information to display, as follows:

Level 0
Status of registered components monitored by HPOM.

Level 1
Status of registered components, whether they are monitored by HPOM or not.

Level 2
Status of registered components and a dump of their registration information.

Level 3
ID of core processes. Zero (0) indicates root. Non-zero indicates non-root ownership.

Level 4
Similar to level 0, but the STATE is reported in numeric format.

Level 5
Similar to level 1, but the STATE is reported in numeric format.

Level 6
Similar to level 0, but the output is not formatted.

Level 7
Similar to level 1, but the output is not formatted.
-version
Prints the version of ovc.

AUTHOR

ovc was developed by Hewlett-Packard Company.

EXIT STATUS

The following exit values are returned:

0
Success.

1
Not defined.

2
Ignored.

62
UNIX daemon or Windows service is not running.

63
Control daemon is being initialized.

64
Generic error.

65
Invalid target.

67
Operation aborted.

69
Missing prerequisite.

70
Authorization error.

71
Operation on prerequisite failed.

73
Invalid event.

EXAMPLES

The following examples show how to use the ovc command and some of its options to control and display important information about registered components:

SEE ALSO

ovcreg(1)