Job Management Partner 1/Automatic Job Management System 3 Command Reference 1

[Contents][Glossary][Index][Back][Next]


jajs_spmd_status

Format

For JP1/AJS3 - Manager
jajs_spmd_status
     [-h logical-host-name]
     [-s|-a]
     [-t time]

For JP1/AJS3 - Agent
jajs_spmd_status
     [-h logical-host-name]
     [-t time]

Description

Checks the state of the jajs_spmd sub-processes against the jajs_spmd process or services.

For details about the jajs_spmd sub-processes or services, see B. List of Processes in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.

Execution privileges

In Windows: Administrators privileges

In UNIX: Superuser privileges

Storage directory

In Windows:
JP1/AJS3 - Manager-installation-folder\bin\
JP1/AJS3 - Agent-installation-folder\bin\

In UNIX:
/opt/jp1ajs2/bin/

Arguments

-h logical-host-name

Specify the name of the logical host that you want to check for its status on a cluster system.

You can specify a character string of 1 to 255 bytes.

By default, the system assumes the logical host name specified by the JP1_HOSTNAME environment variable. If environment variable JP1_HOSTNAME is not specified, the physical host name (which can be determined by the hostname command) is assumed.

-s|-a

Specify the objects whose status you want to display for JP1/AJS3 - Manager.

-t time

Specify the timeout value for JP1/AJS3 status confirmation. The specified value applies to each process, and is not the timeout value for the entire command execution.

You can specify a value between 0 and 32,767 (seconds).

The default value is 60 seconds. Even if you specify 0, the system assumes that a value of 60 seconds is specified.

If confirmation by the jajs_spmd_status command is not terminated within a specified period of time, it is considered that execution of the jajs_spmd_status command has failed.

Notes

Return values

0 Any of the following:
  • All processes are being started.
  • Some processes have been stopped by the jajs_spmd_stop command with the -n option specified or by the ajsstop command.
  • The command is being stopped. (There are no abnormally terminated processes.)
1 Any of the following:
  • An error occurred in, for example, communication with process management.
  • The shared folder (shared directory) has not been mounted in a cluster system.
  • Execution permission is not granted.
4 Any of the following:
  • Some of the processes are being started (There are abnormally terminated processes.).
  • The command is being started.
  • The command is being stopped. (There are abnormally terminated processes.)
8 All processes are being terminated.
12 Any of the following (an error that might not occur if the command is executed again):
  • A temporary error prevented the status of JP1/AJS3 from being determined.
  • A request to obtain the status of JP1/AJS3 timed out.

Example

The following command outputs the status of each JP1/AJS3 component service and the status of processes that belong to each JP1/AJS3 component service on logical host lhost.

 
jajs_spmd_status -h lhost -a
 

Output example 1

The following shows an output example when the -a option is specified for JP1/AJS3 - Manager.

[Figure]

Output example 2

The following shows an output example when the -s option is specified for JP1/AJS3 - Manager.

[Figure]

Output example 3

The following shows an output example for JP1/AJS3 - Agent.

[Figure]

The following shows the meaning of the output.

process name
Indicates the process name.
Note that database indicates the embedded database service, and ajsembdb indicates the embedded database process. Therefore, database is displayed in Windows only. Both database and ajsembdb are managed by the embedded database service and commands. For this reason, if database or ajsembdb is displayed as process name, a hyphen (-) is displayed for process ID.

process ID
Indicates the process ID.

attribute
Indicates the setup identifier that identifies the embedded database or the scheduler service name.

[Contents][Back][Next]


[Trademarks]

Copyright (C) 2009, 2010, Hitachi, Ltd.
Copyright (C) 2009, 2010, Hitachi Solutions, Ltd.