Hitachi

JP1 Version 12 JP1/Integrated Management 2 - Manager Command, Definition File and API Reference


jcschstat

Organization of this page

Function

This command changes the status of monitoring nodes (monitoring objects or monitoring groups). It also clears the logs of status change events at the monitoring nodes. It cannot change the monitoring status of monitoring nodes.

You can include this command in batch processing in order to automatically initialize the status of monitoring nodes as the last processing step of error recovery, or you can use this command to automatically initialize the status of monitoring nodes after eliminating the cause of an error by linking with the help desk system.

You can use this command when the Central Scope functions are enabled.

If you execute this command while JP1/IM - Manager (Central Scope) is already processing 32 or more command requests, communication is lost at the server end, which causes this command to fail.

Format

jcschstat [-h logical-host-name]
          -n monitoring-node-ID-1, monitoring-node-ID-2, monitoring-node-ID-3...
          [-s status-value]
          [-i]
          [-t timeout-period]
          [-d]

Execution permission

In Windows: Administrator permissions (if the Windows UAC feature is enabled, the command is executed from the administrator console)

In UNIX: Superuser permissions

Storage directory

In Windows:

Scope-path\bin\

In UNIX:

/opt/jp1scope/bin/

Arguments

-h logical-host-name

When you are operating in a cluster system, this option specifies the logical host name. If this option is omitted, the logical host name specified in the JP1_HOSTNAME environment variable is assumed. If the JP1_HOSTNAME environment variable is not specified, the physical host name is assumed. If you are not using a cluster system, specification of this option is not needed.

-n monitoring-node-ID-1, monitoring-node-ID-2, monitoring-node-ID-3...

Specifies the IDs of the monitoring nodes (monitoring object IDs or monitoring group IDs) whose status is to be changed, expressed in hexadecimal notation.

You can specify a maximum of 10 monitoring node IDs. When you specify multiple IDs, separate them with the comma (,). The monitoring nodes are processed in the order in which they are specified.

-s status-value

Specifies the new status for the specified monitoring nodes. The status value is case sensitive. For monitoring objects, you can specify Emergency, Alert, Critical, Error, Warning, Normal, Debug, or Initial. For monitoring groups, you can specify only Initial.

When the status of a specified monitoring node changes, the status is propagated to the higher nodes and the lower nodes are initialized.

If this option is omitted, Initial is assumed.

-i

Specifies that a confirmation message is to be displayed when the status of a monitoring node is to be changed.

-t timeout-period

Specifies a timeout period for communication with the server. The permitted value is from 1 to 32,767 (seconds). The default is 1,800 seconds (30 minutes).

-d

Specifies that command processing is to be canceled and the command is to be terminated with an error if a monitoring node specified in the -n option does not exist or if a monitoring node status change fails.

If this option is omitted, the command skips processing on any monitoring node that does not exist or on which status change processing fails, and then processes the next monitoring node.

Return values

0

Normal termination

1

Logical host name was not found

2

Argument error

4

No permission to execute the command

12

Insufficient memory

32

Data access error

33

Specified monitoring tree ID or monitoring node ID was not found in the database

37

No response from the server (connection establishment request failed)

38

Communication with the server failed (the server was terminated during communication or the server's connection count exceeded the maximum value)

39

A timeout occurred (after a request was sent to the server, the timeout period was exceeded before a response was received)

40

An invalid response was sent from the server

42

Another command or request is being processed

43

A monitoring node for which not monitor is set is specified in -n

44

A monitoring group is specified in -n

99

Other error

Example

Change the status of monitoring node ID 8 to Error:

jcschstat -n 8 -s Error

Example output

jcschstat -n 5 -s Normal
KAVB7630-I The status of the monitoring node (5) has been set to Normal.