Job Management Partner 1/Base User's Guide

jevstat

Function

The jevstat command enables you to check the operating status of event service processes (jevservice). For details on event service processes, see B. List of Processes.

Format

jevstat [event-server-name]
         [-t timeout-in-seconds]

Required execution permission

In Windows: Administrators (If User Account Control (UAC) for Windows is enabled, you must execute the command from the administrator console.)

In UNIX: Superuser

Command directory

In Windows:

installation-folder\bin\

In UNIX:

/opt/jp1base/bin/

Arguments

event-server-name

Specify the event server name at which to check whether event service processes have started or stopped in, for example, the cluster system. Event server names are case sensitive. If you omit this option, the host name set in the environment variable JP1_HOSTNAME is assumed. If the environment variable JP1_HOSTNAME is not set, the physical host name is assumed. Specify the event server name as a character string of no more than 255 bytes.

-t timeout (in-seconds)

Specify how long the system should wait for the jevstat command to complete execution. The specifiable range is 1 to 32,767. If the jevstat command does not complete execution within the specified time, execution is assumed to have failed. The default is 60 seconds.

Notes

• If a jevstat command is executed immediately after an event service starts, the following error message might be output: KAJP1706-E A connection to the event server cannot be established. In such a case, execute the jevstat command a few seconds after the event service starts.
• If the jevstat command is executed and the following message is output to an integrated trace log, the command might have timed out: KAJP1775-E An attempt to send or receive communication data has failed. (maintenance information). Re-execute the jevstat command, specifying how long to wait for the command to complete execution in the -t option.

Return values

0	All processes are active.
1	Abnormal termination (command processing error)
4	Some processes are active.
8	All of the child processes have stopped.
12	Abnormal termination (error returned by the event server)

Further explanation

When using JP1/Base in a cluster system on UNIX, you can use the jevstat command in the abnormality detection script of the logical host. In this case, you should be aware that the names of the event server to be run on the logical host are case sensitive and must be specified accordingly. Refer to the event server index file (index) in which the event server names for the logical host are defined as you specify them.

The following shows a definition example of the event server index file (index), and the execution result of the jevstat command run using the index file.

Definition example of the event server index file (index)

server * default
server HOSTZZ /jp1/share/

Examples of jevstat commands and their results:

jevstat command execution examples	Execution results
jevstat	Outputs the status of the event server on the physical host.
jevstat hostzz	Outputs an error message indicating that the specified event server name was not found.
jevstat HOSTZZ	Outputs the status of the event server on the logical host.

Example

Examples of the jevstat command for Windows and UNIX are shown below.

In Windows:

E:\>jevstat
KAJP1771-I Processing to report the status of the event service HOST1 will now start.
Display the running processes
process name        process ID
jevservice        1234
KAJP1772-I All the processes are running.

In UNIX:

$ /opt/jp1base/bin/jevstat
KAJP1771-I Processing to report the status of the event service HOST1 will now start.
Display the running processes
process name        process ID
jevservice        2098
KAJP1772-I All the processes are running.

KAJP1772-I is a message shown when all the necessary processes for the event server have been started.

[Contents][Back][Next]

All Rights Reserved. Copyright (C) 2009, Hitachi, Ltd.