jbs_stop.cluster (UNIX only)
- Organization of this page
Function
The jbs_stop.cluster command stops JP1/Base (the event service and process management including user management) in a cluster system. To execute this command, you must first register it in your cluster software.
The following commands are executed within this command:
-
jevstop logical-host-name
-
jbs_spmd_stop -h logical-host-name
Format
jbs_stop.cluster logical-host-name
Required execution permission
Superuser or JP1/Base administrator permission
Command directory
/etc/opt/jp1base/
Arguments
logical-host-name
When using JP1/Base in a cluster system, specify the logical host for which you want to execute this command.
Notes
-
The jbs_stop.cluster command does not stop the log-file trap management daemon, which is used on both the logical and physical hosts. You can stop the daemon by executing the jevlogdstop command after executing the jbs_stop.cluster command. However, if the log-file trap management daemon is active on the physical host, executing the jevlogdstop command will disable log file trapping on that physical host. Before executing the jevlogdstop command, make sure that the log file trapping is not being used on the physical host.
-
After issuing the stop request to the JP1/Base processes, this command ends with the return value 0. To check whether the processes have stopped correctly, after the jbs_stop.cluster command has finished, use the jbs_spmd_status command.
-
In a cluster system that requires monitoring resource operations while a resource is being stopped, the stop command might fail and not be able to stop the resource normally. Therefore, a stop command is provided that can stop JP1/Base normally through a retry. Modify the command settings as follows:
cd /etc/opt/jp1base cp -p jbs_stop.cluster.retry.model jbs_stop.cluster
Return values
|
0 |
Normal end |
|
1 |
More than one argument was specified. |