jajs_start.cluster (UNIX only)

Format

jajs_start.cluster
     [logical-host-name]
     [jajs_spmd-command-options]

To Page Top

Description

Starts JP1/AJS3 in the logical host environment.

This command is used to control the startup of JP1/AJS3 in a cluster system. Before using this command, you must register it in the cluster system.

The following explains the command's flow of processing.

1. Starts the queueless agent service if it has not started.

2. Starts the queueless file transfer service if it is not started.

3. Attaches a logical host to the queueless agent service if no logical host is attached to the service.

4. Executes the jajs_spmd command to start a JP1/AJS3 process.

5. Starts the JP1/AJS3 Check Manager service if it has not started.

6. Starts the JP1/AJS3 Check Agent service if it has not started.

7. Starts the JP1/AJS3 Autonomous Agent service and the JP1/AJS3 Autonomous Agent Messenger service if they are not running.

8. Executes the jajs_spmd_status command, and then waits for a maximum of 60 seconds until JP1/AJS3 starts. If JP1/AJS3 is unable to start, the logical host of the queueless agent service is detached.

9. Executes the jajs_spmd_status command to display the status of JP1/AJS3 processes.

In the initial status when JP1/AJS3 is installed, the definitions for starting services except the JP1/AJS3 processes are commented out. If necessary, customize the definitions so that startup processing is enabled. For details about customization, see 17.2.11 Specifying the settings that control startup and termination of JP1/AJS3 in a logical host environment in the JP1/Automatic Job Management System 3 Configuration Guide.

To Page Top

Execution privileges

Superuser privilege

To Page Top

Storage directory

/etc/opt/jp1ajs2/

To Page Top

Arguments

To Page Top

Notes

• This command cannot be executed in Windows.

• If you specify options for this command, be sure to specify a logical host name for the first option of the argument.

• You must specify the logical host name if you specify the jajs_spmd command options.

• JP1/AJS3 might not start correctly if you execute this command together with any of the following commands on the same logical host:

  ajsprofalter command

  ajsembdbstart command

  ajsembdbstop command

  ajsstart command

  ajsstop command

  jajs_hstd command

  jajs_hstd_stop command

  jajs_spmd command

  jajs_spmd_status command

  jajs_spmd_stop command

  jajs_start.cluster command (UNIX only)

  jajs_stop.cluster command (UNIX only)

• If you want to execute this command by using a remote shell command, beforehand, make sure that the standard input, the standard output, and the standard error output are disconnected (that is, assign /dev/null to these). If you execute the command without disconnecting these, the remote shell command might not terminate when startup of the JP1/AJS3 service is completed.

• In Linux, the maximum size for core file output might be set to 0 in the standard setting. In this case, core dumps are not output.

  However, in the default script of the jajs_start.cluster command, the maximum size for core file output is set when a JP1/AJS3 process starts, so that core dumps can be output.

  if [ 'uname' = Linux ]; then
    ulimit -c unlimited
  fi

  You can change the above settings to comment lines by adding a hash mark (#) to the beginning of each line as follows:

  #if [ 'uname' = Linux ]; then
  #  ulimit -c unlimited
  #fi

  Change the lines to comment lines in the following cases:

  • The core file output setting violates the security policies of the host you are using.

  • The maximum size for core file output has been changed from the standard setting, and an OS user who is an AJS administrator in the JP1 administrator group executes the jajs_start.cluster command.

    In this case, if the setting lines have not yet been changed to comment lines when the jajs_start.cluster command is executed, an error message is output to the standard error output.

  After the setting lines are changed to comment lines, the maximum size for core file output does not change within the JP1/AJS3 process started by the jajs_start.cluster command. Note that depending on the occurrence time of a segmentation error, bus error, or another error in a JP1/AJS3 process, an incomplete core dump might be output. Therefore, you might not be able to identify the cause of the error.

To Page Top

Return values

0	Normal end
Values other than 0	Abnormal end

To Page Top