jcfallogstat
- Organization of this page
Function
Displays the operating status of a remote monitoring log file trap.
Executing this command returns the operating status of a remote monitoring log file trap that has the monitoring name specified as the argument or that monitors the monitored host specified as the argument.
Note that a maximum of five commands can be executed concurrently.
The following conditions must be satisfied to execute this command:
-
The IM Configuration Management service is running
-
There is a remotely monitored host in the remote monitoring configuration.
-
A remotely monitored host has already collected host information.
Format
jcfallogstat {-o monitored-host-name [-a monitoring-name] | ALL} [-h logical-host-name]
Execution permission
In Windows: Administrator permissions
In UNIX: Superuser permissions
Storage directory
- In Windows:
-
Manager-path\bin\imcf\
- In UNIX:
-
/opt/jp1imm/bin/imcf/
Display format
Executing the jcfallogstat command displays the output result in the format described below. Note that when ALL is specified and there are no hosts in the remote monitoring configuration, or when the specified host does not exist in the remote monitoring configuration, a message to that effect is displayed.
- Note:
-
In this example, a line number is added at the beginning of each line for descriptive purposes:
1 message-IDmessage
2 message-IDmessage
3 [host-name]
4 monitoring-namestatus
5 monitoring-namestatus
6 monitoring-namestatus
7 [host-name]
8 [host-name]
9 status
10 :
-
Line 1
A message indicating that command execution has started is displayed.
-
Line 2
A message indicating the following display scope is displayed:
-
All
-
Specified host
-
Specified log file traps on the specified host
-
-
Lines 3 to 6
The statuses of the log file traps on the remotely monitored host for the specified scope are displayed. The following statuses are displayed:
-
START: The log file trap is running.
-
STOP: The log file trap has stopped.
-
EDIT: The action definition file for the log file trap is being edited, but the changes have not been applied.
-
FAIL: The log file trap status could not be obtained for one of the following reasons:
- The host is invalid (host information was not collected, or collection failed).
- An error occurred in SSH or WMI/NetBIOS (NetBIOS over TCP/IP) communication.
- An authentication error occurred.
- An input/output error occurred.
- An error occurred during an attempt to obtain exclusive rights.
- An internal error occurred.
-
-
Line 7
If no log file traps are defined, only the host name is displayed.
-
Lines 8 and 9
If an error has occurred on a host but the status could not be obtained, only FAIL is displayed.
-
Line 10
The statuses of log file traps on all remotely monitored hosts for the specified scope are displayed.
Arguments
- -o monitored-host-name
-
Specifies the name of the monitored host for a remote monitoring log file trap whose operating status you want to check.
- -a monitoring-name
-
Specifies the monitoring name of a remote monitoring log file trap whose operating status you want to check.
Specify a character string with a maximum of 30 bytes for the monitoring name. Alphanumeric characters, hyphens (-), and underlines can be used. The first character must be an alphanumeric character. The monitoring name is not case sensitive.
- ALL
-
Specifies the monitoring names of all log file traps.
- -h logical-host-name
-
Specifies the name of the logical host on which you want to execute the command. If this option is omitted, the logical host name is set. If this option is omitted, the logical host name specified for the JP1_HOSTNAME environment variable is set. If no logical host name is set for JP1_HOSTNAME, the physical host name is set.
Return values
0 |
All remote monitoring log file traps are running |
1 |
Some remote monitoring log file traps are running (When the ALL option is specified, or only the -o option is specified) |
2 |
Partial or total failure |
4 |
Invalid argument |
6 |
Unable to connect to the server |
7 |
Invalid host information |
14 |
Invalid DB |
17 |
Invalid permission |
18 |
Input/output error |
19 |
All remote monitoring log file traps have stopped |
21 |
Upper limit for number of concurrent executions reached |
255 |
Internal error |
Other values |
Other error |
Example
Display the operating status of the remote monitoring log file trap name1 on host1:
jcfallogstat -o host1 -a name1