Hitachi

JP1 Version 12 JP1/Integrated Management 2 - Manager Command, Definition File and API Reference


jco_start.cluster (UNIX only)

Organization of this page

Function

When you are operating in a cluster system, this command starts JP1/IM - Manager on the logical host.

If you register this command into the cluster software, JP1/IM - Manager starts.

Before you execute this command, start JP1/Base on the same logical host. An error results if this command is executed while the event service of JP1/Base is not running.

The command terminates with a return value of 0 after issuing a startup request to the group of JP1/IM - Manager processes. To check whether the group of processes has started successfully, use the jco_spmd_status command after the jco_start.cluster command has terminated.

If this command is executed when the following condition is satisfied, the command starts the IM database service and then starts JP1/IM - Manager:

To execute this command, you must have executed jp1cc_setup_cluster and jp1cs_setup_cluster after installing and setting up JP1/IM - Manager. For the IM database service, you must set up the cluster system for the IM database service. For details about setting up a cluster system, see Chapter 8. Operation and Environment Configuration in a Cluster System (for UNIX) in the JP1/Integrated Management 2 - Manager Configuration Guide.

Format

jco_start.cluster [logical-host-name]

Execution permission

Superuser permissions

Storage directory

/etc/opt/jp1cons/

Arguments

logical-host-name

When you are operating in a cluster system, this option specifies the name of the logical host where this command is to be executed. The permitted length is from 1 to 63 bytes characters. If this option is omitted, the command assumes the logical host name specified in the JP1_HOSTNAME environment variable. If the JP1_HOSTNAME environment variable is not specified, the command assumes the physical host name.

Note

Return values

0

Normal termination

1

More than one argument is specified, the event service is not running, or the IM database service cannot be started

2

There is no log directory