jpcspm start
- Organization of this page
Format
jpcspm start -key service-key [-lhost logical-host-name] [-inst instance-name]
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.
Hosts that can execute the command
-
PFM - Manager
-
PFM - Agent
-
PFM - Base
-
PFM - RM
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
Installation directory
- In Windows:
installation-folder\tools\
- In UNIX:
/opt/jp1pc/tools/
Arguments
-key service-key
Specifies the service key of the service that is to be started. A product name can also be specified when the product name display functionality is enabled. You can also specify the following in service-key:
-
all: The services of all Performance Management programs. If linkage is set with the start and stop of PFM - Web Console, the PFM - Web Console service also starts at the same time.
-
jp1pc: All Performance Management services (excluding the PFM - Web Console service).
-
Manager or mgr: The PFM - Manager services (excluding the Action Handler service).
-
AH or act: The Action Handler service.
-
StatSvr or stat: The Status Server service.
-
WebConsole or wc: The PFM - Web Console service. This can be specified when linkage is set with the start and stop of PFM - Web Console.
For details about the service key of the PFM - Agent or PFM - RM service, see the naming rules described in the appendix of the Job Management Partner 1/Performance Management Planning and Configuration Guide. For details about linkage with the start and stop of PFM - Web Console, see the chapter describing start and stop for Performance Management in the Job Management Partner 1/Performance Management User's Guide.
-lhost logical-host-name
Specifies the host environment in which this command is executed. You use this argument if a logical host has been configured on the machine that is used to execute this command. For logical-host-name, specify a string of 1 to 32 bytes, consisting of alphanumeric characters with no space characters.
If this argument is omitted, the physical host is assumed. Wildcard characters cannot be used.
-inst instance-name
If a specific instance of the service is to be started, specifies the instance name. For instance-name, specify a string of 1 to 32 bytes, consisting of alphanumeric characters. This option is applicable only to a PFM - Agent or PFM - RM that has an instance environment. This option is ignored for any other service, if specified.
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 Job Management Partner 1/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 Job Management Partner 1/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 Job Management Partner 1/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 Job Management Partner 1/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.
Return values
0 |
The command terminated normally. |
1 |
An argument specification is invalid. |
2 |
The user does not have execution permission for the command. |
4 |
The specified service is already running, or the command was executed while the Store database was being accessed by the Master Store, Agent Store, or Remote Monitor Store service, or a command. |
5 |
The specified service has not been installed. |
10 |
The command is executing in another session. |
100 |
The Performance Management environment is invalid. |
101 |
The PFM - Manager service is not running. |
102 |
The specified logical host name or instance has not been set up. |
103 |
Start process monitoring timed out. |
107 |
Service start or stop processing is being executed by another process, such as Windows Service Control Manager. |
200 |
A memory shortage occurred. |
211 |
A file or directory cannot be accessed. |
212 |
Index creation failed. |
255 |
An unexpected error occurred. |
Usage example 1
This example starts the services of all Performance Management programs:
jpcspm start -key all
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