Notes on commands
- Organization of this page
Notes common to all commands
Before executing a command in UNIX, the current directory must be changed to the command's installation directory. For details about a command's installation directory, see the explanation for each command.
Notes about specifying the host and lhost options in a jpctool db command or jpctool service command
The following shows the specifications for the -host and -lhost options, and the corresponding target range when this command is executed:
-
jpctool db backup
-
jpctool db clear
-
jpctool db dump
-
jpctool service
-
When executing the command at a PFM - Manager host
If you execute the jpctool db command or jpctool service command at a PFM - Manager host and the PFM - Manager is in a logical host environment, you must specify that logical host in the -lhost option. For example, in the case of the system configuration shown in the figure below, the jpctool db command or jpctool service command is executed at logical host C, so -lhost C is specified. Note that if you omit the -lhost option, the command will be executed at physical host A.
To execute the jpctool db command or jpctool service command that targets a service on a specific host, specify the -host option. In this example, to execute the command on host D, you would specify -host D -lhost C.
![[Figure]](GRAPHICS/ZU202002.GIF)
-
When executing the command at a PFM - Agent or PFM - RM host
If you execute the jpctool db command or jpctool service command on a PFM - Agent or PFM - RM host, and the PFM - Agent or PFM - RM host is in a logical host environment, you must specify that logical host in the -lhost option. For example, for the system configuration shown in the figure below, the jpctool db command or jpctool service command is executed at logical host C, so -lhost C is specified.
![[Figure]](GRAPHICS/ZU202003.GIF)
Notes on execution of jpctool alarm commands
-
Event
The jpctool alarm inactive and jpctool alarm unbind commands that the manager executes to stop the monitoring that uses alarms are not synchronized with the completion of monitoring stoppage on the monitoring target agent.
Therefore, if you stop the monitoring that uses alarms and then stop the monitoring target system, Performance Management might detect the stoppage of the monitoring target system before detecting the completion of monitoring stoppage, and issue an unintended alarm.
-
How to avoid this event
If you want to stop the monitoring that uses alarms and then stop the monitoring target system, wait about 60 seconds# before stopping the monitoring target system, or ignore the alarm that might be issued when the monitoring target system is stopped.
Example:
-
Execute the jpctool alarm inactive or jpctool alarm unbind command to stop the monitoring that uses alarms.
-
Make the process pause for 60 seconds.
-
Stop the system being monitored by Performance Management.
- #
-
This is a standard pause duration, so it may have to be varied depending on the system environment. If an unintended alarm is issued even with a pause, extend the length of the pause.
-
You must be careful about also the following jpctool alarm commands, because processing is not synchronized with the completion of the processing on the target agent.
-
jpctool alarm active
-
jpctool alarm bind
-
jpctool alarm copy
-
jpctool alarm delete
-
jpctool alarm import
Commands that cannot be executed with alarm commands
You cannot execute any alarm commands (commands beginning with jpctool alarm) on a machine on which the following commands are running:
-
List of commands that cannot be executed with alarm commands
-
jpcconf acc setup
-
jpcconf acc unsetup
-
jpcconf agent setup
-
jpcconf ha
-
jpcconf hc
-
jpcconf inst setup
-
jpcconf inst unsetup
-
jpcconf mgrhost
-
jpcconf stat
-
jpcspm start
-
jpcspm stop
-
jpctool alarm
-
jpctool db
-
jpctool monitor resume
-
jpctool monitor suspend
-
jpc_start (executed when the OS starts)
-
jpc_stop (executed when the OS starts)
-
If you execute an alarm command in such a situation, the return value 4 is returned and the subsequent processing is not performed. Even if these commands target different hosts (a physical host and a logical host), if you execute the commands concurrently, the same result occurs.
For PFM - Manager 10-10-10 or later, if you execute an alarm command when the setting to suspend execution of the alarm command (Alarm Command Wait Mode) is enabled in the startup information file (jpccomm.ini), the alarm command is executed after other executing commands finish.
For details on the jpccomm.ini file and Alarm Command Wait Mode, see Startup information file (jpccomm.ini). Note that, when you set Alarm Command Wait Mode in a logical host environment, you must enable Alarm Command Wait Mode in the startup information file (jpccomm.ini) on both the active and standby physical hosts, instead of enabling Alarm Command Wait Mode in the startup information file under the environment directory.
Notes on executing commands concurrently
Some commands have restrictions on concurrent execution with other commands, and on concurrent execution of multiple instances of the same command.
The following table displays whether a command can be executed concurrently with other commands, and whether multiple instances of the same command can be executed concurrently.
|
Command name |
Type |
Concurrent execution for each type |
Concurrent execution with other instances of the same command |
|||
|---|---|---|---|---|---|---|
|
Start/ stop |
Setup |
Synchronization |
Other |
|||
|
jpcabformcheck |
Other |
Y |
Y |
Y |
Y |
Y |
|
jpccfgbackup |
Other |
Y |
Y |
Y |
Y |
N |
|
jpcconf acc display |
Other |
Y |
Y |
Y |
Y |
Y |
|
jpcconf acc setup |
Setup |
N |
N |
Y |
Y |
N |
|
jpcconf acc unsetup |
Setup |
N |
N |
Y |
Y |
N |
|
jpcconf agent list |
Other |
Y |
Y |
Y |
Y |
N |
|
jpcconf agent setup |
Setup |
N |
N |
Y |
Y |
Y |
|
jpcconf agttree export |
Other |
Y |
Y |
Y |
Y |
Y |
|
jpcconf agttree import |
Other |
Y |
Y |
Y |
Y |
Y |
|
jpcconf bgdef check |
Setup |
N |
N |
Y |
Y |
N |
|
jpcconf bgdef delete |
Setup |
N |
N |
Y |
Y |
N |
|
jpcconf bgdef display |
Setup |
N |
N |
Y |
Y |
N |
|
jpcconf bgdef export |
Setup |
N |
N |
Y |
Y |
N |
|
jpcconf bgdef import |
Setup |
N |
N |
Y |
Y |
N |
|
jpcconf bgdef list |
Setup |
N |
N |
Y |
Y |
N |
|
jpcconf db define |
Setup |
N |
N |
Y |
Y |
N |
|
jpcconf db display |
Setup |
N |
N |
Y |
Y |
N |
|
jpcconf db vrset |
Setup |
N |
N |
Y |
Y |
N |
|
jpcconf ha export |
Setup |
N |
N |
Y |
Y |
N |
|
jpcconf ha import |
Setup |
N |
N |
Y |
Y |
N |
|
jpcconf ha list |
Setup |
N |
N |
Y |
Y |
N |
|
jpcconf ha setup |
Setup |
N |
N |
Y |
Y |
N |
|
jpcconf ha unsetup |
Setup |
N |
N |
Y |
Y |
N |
|
jpcconf hc disable |
Setup |
N |
N |
Y |
Y |
N |
|
jpcconf hc display |
Setup |
N |
N |
Y |
Y |
N |
|
jpcconf hc enable |
Setup |
N |
N |
Y |
Y |
N |
|
jpcconf host hostmode |
Setup |
N |
N |
Y |
Y |
N |
|
jpcconf host hostname |
Setup |
N |
N |
Y |
Y |
N |
|
jpcconf im disable |
Other |
Y |
Y |
Y |
Y |
Y |
|
jpcconf im enable |
Other |
Y |
Y |
Y |
Y |
Y |
|
jpcconf inst list |
Setup |
Y |
N |
Y |
Y |
N |
|
jpcconf inst setup |
Setup |
N |
N |
Y |
Y |
N |
|
jpcconf inst unsetup |
Setup |
N |
N |
Y |
Y |
N |
|
jpcconf ipv6 disable |
Setup |
N |
N |
Y |
Y |
N |
|
jpcconf ipv6 display |
Setup |
N |
N |
Y |
Y |
N |
|
jpcconf ipv6 enable |
Setup |
N |
N |
Y |
Y |
N |
|
jpcconf mgrhost define |
Setup |
N |
N |
Y |
Y |
N |
|
jpcconf mgrhost display |
Setup |
N |
N |
Y |
Y |
N |
|
jpcconf ov disable |
Other |
Y |
Y |
Y |
Y |
Y |
|
jpcconf port define |
Setup |
N |
N |
Y |
Y |
N |
|
jpcconf port list |
Setup |
N |
N |
Y |
Y |
N |
|
jpcconf prodname disable |
Setup |
N |
N |
Y |
Y |
N |
|
jpcconf prodname display |
Setup |
N |
N |
Y |
Y |
N |
|
jpcconf prodname enable |
Setup |
N |
N |
Y |
Y |
N |
|
jpcconf stat disable |
Setup |
N |
N |
Y |
Y |
N |
|
jpcconf stat display |
Setup |
N |
N |
Y |
Y |
N |
|
jpcconf stat enable |
Setup |
N |
N |
Y |
Y |
N |
|
jpcconf target display |
Setup |
N |
N |
Y |
Y |
N |
|
jpcconf target list |
Setup |
N |
N |
Y |
Y |
N |
|
jpcconf target setup |
Setup |
N |
N |
Y |
Y |
N |
|
jpcconf target unsetup |
Setup |
N |
N |
Y |
Y |
N |
|
jpcconf primmgr notify |
Other |
Y |
Y |
Y |
N |
N |
|
jpcimevt |
Other |
Y |
Y |
Y |
Y |
Y |
|
jpciniupdate |
Setup |
N |
N |
Y |
Y |
Y |
|
jpcnodecount |
Other |
Y |
Y |
Y |
Y |
Y |
|
jpcparamdump |
Setup |
N |
N |
Y |
Y |
N |
|
jpcras |
Other |
Y |
Y |
Y |
Y |
Y |
|
jpcspm start |
Start/stop |
N |
Y |
Y |
Y |
N |
|
jpcspm stop |
Start/stop |
N |
Y |
Y |
Y |
N |
|
jpctool alarm active#1 |
Setup |
N |
N |
Y |
Y |
N |
|
jpctool alarm bind#1 |
Setup |
N |
N |
Y |
Y |
N |
|
jpctool alarm check#1 |
Setup |
N |
N |
Y |
Y |
N |
|
jpctool alarm copy#1 |
Setup |
N |
N |
Y |
Y |
N |
|
jpctool alarm delete#1 |
Setup |
N |
N |
Y |
Y |
N |
|
jpctool alarm export#1 |
Setup |
N |
N |
Y |
Y |
N |
|
jpctool alarm import#1 |
Setup |
N |
N |
Y |
Y |
N |
|
jpctool alarm inactive#1 |
Setup |
N |
N |
Y |
Y |
N |
|
jpctool alarm list#1 |
Setup |
N |
N |
Y |
Y |
N |
|
jpctool alarm unbind#1 |
Setup |
N |
N |
Y |
Y |
N |
|
jpctool alarm unapplied#1 |
Setup |
N |
N |
Y |
Y |
N |
|
jpctool config alarmsync |
Synchronization |
Y |
Y |
N |
Y |
N |
|
jpctool config mgrexport |
Setup |
N |
N |
Y |
Y |
N |
|
jpctool config mgrimport |
Setup |
N |
N |
Y |
Y |
N |
|
jpctool config sync |
Synchronization |
Y |
Y |
N |
Y |
N |
|
jpctool db backup |
Other |
Y |
Y |
Y |
Y |
N |
|
jpctool db clear |
Other |
Y |
Y |
Y |
Y |
Y |
|
jpctool db dmconvert |
Setup |
N |
N |
Y |
Y |
N |
|
jpctool db dump |
Other |
Y |
Y |
Y |
Y |
Y |
|
jpctool db import |
Setup |
N |
N |
Y |
Y |
N |
|
jpctool db restore |
Other |
Y |
Y |
Y |
Y |
Y |
|
jpctool service delete |
Other |
Y |
Y |
Y |
Y |
Y |
|
jpctool service list |
Other |
Y |
Y |
Y |
Y |
Y |
|
jpctool service sync |
Setup |
N |
N |
Y |
Y |
N |
|
jpctool monitor list |
Other |
Y |
Y |
Y |
Y |
Y |
|
jpctool monitor resume#2 |
Setup |
N |
N |
Y |
Y |
Y |
|
jpctool monitor status |
Other |
Y |
Y |
Y |
Y |
Y |
|
jpctool monitor suspend#2 |
Setup |
N |
N |
Y |
Y |
Y |
- Legend:
-
Y: The command can be executed concurrently with the other command, or multiple instances of the same command can be executed concurrently.
N: The command cannot be executed concurrently with the other command, or multiple instances of the same command cannot be executed concurrently.
- #1
-
If you specify the -wait option, command execution is suspended until the currently running command terminates.
- #2
-
If another command is running, processing is suspended until that command terminates, and then the processing continues.