jpcspm start

Format

jpcspm start    -key service-key
               [-lhost logical-host-name]
               [-inst instance-name]

To Page Top

Function

The jpcspm start command starts services of Performance Management programs. It cannot start the services of Performance Management programs at a remote host.

You can use the jpctool service list command to check the status of the Performance Management program services. jpcspm start commands cannot be executed concurrently, nor can one be executed simultaneously with the jpcspm stop command.

When the services to be started include PFM - Manager and the health check function is enabled on the PFM - Manager host on which you execute the command, the health check agent also starts as part of the PFM - Manager service. Note that you cannot specify agt0 as the service key.

To Page Top

Hosts that can execute the command

• PFM - Manager

• PFM - Agent

• PFM - RM

To Page Top

Execution permission

In Windows:

User with Administrators permissions (executed from the administrator console when Windows UAC functionality is enabled)

In UNIX:

User with root user permissions

To Page Top

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

To Page Top

Arguments

To Page Top

Notes

• If PFM - Manager and PFM - Agent, or PFM - Manager and PFM - RM are installed on the same host, PFM - Manager must be started first in order to start the PFM - Agent, PFM - RM, or Action Handler service. If PFM - Manager and PFM - Agent, or PFM - Manager and PFM - RM are installed on separate hosts, the PFM - Agent, PFM - RM, or Action Handler service can be started in the stand-alone mode while PFM - Manager is not running. However, in the stand-alone mode, the available functions are limited. For details about these limitations, see the chapter describing start and stop for Performance Management in the JP1/Performance Management User's Guide. PFM - Agent version 06-70 does not support startup in the stand-alone mode. To start such a PFM - Agent, you must first start PFM - Manager, regardless of whether or not the PFM - Agent is installed on the same host as the PFM - Manager.

• You must specify the arguments in the order they appear in Format.

• If command execution returns the return value 103, monitoring of the process for starting the service of a Performance Management program timed out. Wait a while, and then re-execute the jpcspm start command. If this event occurs frequently, collect maintenance information and contact the system administrator. For details about how to collect maintenance information, see the chapter on troubleshooting in the JP1/Performance Management User's Guide.

• If command execution returns the return value 212, index creation for the Master Store, Agent Store, Remote Monitor Store service database failed. Check to see if there is enough free disk space. For guidelines for determining the required disk space, see the system estimates described in the appendix of the JP1/Performance Management Planning and Configuration Guide or the applicable PFM - Agent or PFM - RM manuals. If there is enough disk space and re-execution of the jpcspm start command results in an index creation error again, collect maintenance information and contact the system administrator. For details about how to collect maintenance information, see the chapter on troubleshooting in the JP1/Performance Management User's Guide.

• If command execution is interrupted by pressing the Ctrl + C keys or by a signal, a predefined return value is not returned. Therefore, you should ignore the return value when the command was interrupted by the Ctrl + C keys or by a signal.

• If the status management function is enabled, and the service with the specified service key supports the status management function, and the Status Server service is not running, the Status Server service is started first. Note that if the status management function is disabled, the Status Server service is not started.

• If the status management function is disabled, specifying stat in the service key displays the KAVE06023-E message and the command terminates.

• Do not execute this command concurrently with a start or stop command executed from cluster software or the service control manager. Because these commands contend with each other, the start or stop command might not be executed correctly.

• If you have enabled both automatic start and automatic stop of services in an environment powered by CentOS 7 or later versions, Linux 7 or later versions, Oracle Linux 7 or later versions, SUSE Linux 12 or later versions, start or stop the Performance Management program services by using the systemctl command. Starting or stopping the Performance Management program services by using the jpcspm start or jpcspm stop command renders automatic service stop impossible.

  The following example starts or stops services by using the systemctl command.

  Service start: systemctl start jp1_pc

  Service stop: systemctl stop jp1_pc

• When starting PFM - Agent or PFM - RM services, it is possible to start each service of PFM - Agent or PFM - RM, even though each service of PFM - Manager is not running. However, by starting PFM - Agent or PFM - RM in stand-alone mode, the functionality that can be used in Performance Management is limited.

  When stopping PFM - Manager services, it is possible to stop each service of PFM - Manager, even though each service of PFM - Agent or PFM - RM is running. However, when PFM - Manager is stopped, the functionality that can be used in Performance Management is limited. Additionally, even after re-starting PFM - Manager, the latest status of PFM - Agent or PFM - RM might not be displayed. In this case, the status can be confirmed by following the procedure described:

  • When PFM - Agent or PFM - RM has stopped

    Please confirm the status after starting PFM - Agent or PFM - RM.

  • When PFM - Agent or PFM - RM is running

    After re-starting PFM - Manager, wait for a while, and then confirm the status again.

  When starting PFM - Agent or PFM - RM services, it is recommended that each service of PFM - Agent or PFM - RM be started after each service of PFM - Manager is started, and when stopping services, it is recommended that each service of PFM - Manager be stopped after each service of PFM - Agent or PFM - RM is stopped. For details about the stand-alone mode see the chapter that describe when starting PFM - Agent or PFM - RM in a large-scale system in the manual JP1/Performance Management User's Guide.

• When the jpcspm start command is executed, if the hosts file does not have a localhost setting, the following message is output and the View Server service fails to start:

  KAVE05033-E A service could not start. (service=View Server, rc=-5)

  In this case, add the localhost setting to the hosts file, and execute the jpcspm start command.

• In AIX, when running a cluster system using HA Monitor, execute the following command to perform settings before executing the jpcspm start command for the script specified in the name operand of the servers definition:

  ulimit -s 32768

  For details about HA Monitor settings, see the manual High Reliability System Monitoring Functionality - HA Monitor.

To Page Top

Return values

To Page Top

Usage example 1

This example starts the services of all Performance Management programs:

jpcspm start -key all

To Page Top

Usage example 2

This example starts only the service of an instance named oracleA in the PFM - Agent for Oracle:

jpcspm start -key Oracle -inst oracleA

To Page Top