Notes on commands

Notes common to all commands

Before executing a command, 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.

To Page Top

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.

  

• 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.

  

To Page Top

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, JP1/PFM 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:

  1. Execute the jpctool alarm inactive or jpctool alarm unbind command to stop the monitoring that uses alarms.

  2. Make the process pause for 60 seconds.

  3. Stop the system being monitored by JP1/PFM.

  #

  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

To Page Top

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

  • 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 F. 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.

To Page Top