jpcspm stop
- Organization of this page
Format
jpcspm stop -key service-key [-lhost logical-host-name] [-inst instance-name] [-kill immediate]
Function
The jpcspm stop command stops services of Performance Management programs. It cannot stop 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 stop commands cannot be executed concurrently, nor can one be executed simultaneously with the jpcspm start command.
When the services to be stopped 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 stops 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 - 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 stopped. 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 stops at the same time.
-
jp1pc: All PFM - Manager 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 JP1/Performance Management Planning and Configuration Guide. For details about linkage with the start and stop of PFM - Web Console, in the JP1/Performance Management User's Guide, see the chapter describing start and stop for Performance Management.
-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 stopped, specifies the instance name. For instance-name, specify a string of 1 to 32 bytes, consisting of alphanumeric characters. This option is applicable only for a PFM - Agent or PFM - RM that has an instance environment. This option is ignored for any other service, if specified.
-kill immediate
Specify this option to forcibly stop processes that are running in a cluster system. If all is specified in service-key, the command stops all processes running on the same host. If a service key other than all is specified, the command stops all the processes for the specified service(s). Note that processes cannot be stopped for a particular instance by specifying -inst.
- Note
-
Use this option only for stopping processes forcibly during cluster operation.
Notes
-
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 stopping the service of a Performance Management program timed out. Wait a while, and then re-execute the jpcspm stop 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.
-
Once the jpcspm stop command is issued to stop PFM services, an attempt to stop the command (such as by pressing the Ctrl + C keys or with a signal) will not stop termination processing that has already been started by the command. If the jpcspm stop command is issued again to stop the service, the KAVE05034-E message might be displayed. Check the common message log for termination of the service and then re-execute the jpcspm stop command.
-
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.
-
In the case of a host that supports the status management function, the Status Server service is not stopped unless all or stat is specified in service-key.
-
If all is specified in service-key and the -lhost option is specified, the Status Server service will not be stopped.
-
If the status management function is enabled, and the jpcspm stop command with all or stat specified in service-key is executed at the physical host, and at least one service that depends on the Status Server service is running at the logical host (version that supports the status management function), the command will display the KAVE06022-I message and return the return value 108.
-
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. |
3 |
The specified service has already been stopped. |
5 |
The specified service has not been installed. |
10 |
The command is executing in another session. |
100 |
The Performance Management environment is invalid. |
102 |
The specified logical host name or instance has not been set up. |
103 |
Stop process monitoring timed out. |
107 |
Service start or stop processing is being executed by another process such as Windows Service Control Manager. |
108 |
Status Server cannot be stopped because a service that depends on the Status Server service is running. |
200 |
A memory shortage occurred. |
211 |
A file or directory cannot be accessed. |
255 |
An unexpected error occurred. |
Usage example 1
This example stops all services of the Performance Management programs:
jpcspm stop -key all
Usage example 2
This example stops only the service of an instance named oracleA in the PFM - Agent for Oracle:
jpcspm stop -key Oracle -inst oracleA