jajs_start (UNIX only)

Format

jajs_start

To Page Top

Description

The jajs_start command starts JP1/AJS3 on the physical host.

This command is executed when the system starts.

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 has not started.

3. Starts JP1/AJS3.

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

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

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

7. Executes the jajs_spmd_status command, and then waits for a maximum of 60 seconds until JP1/AJS3 starts.

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

In the initial status when JP1/AJS3 is installed, the definition for startup processing is commented out. That is, startup processing is disabled. If necessary, customize the definition so that startup processing is enabled. For details about customization, see 15.9.1 Setting automatic startup and termination of the JP1/AJS3 service 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

Notes

• This command cannot be executed in Windows.

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

  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 command (UNIX only)

  jajs_stop command (UNIX only)

• Execute this command in an environment in which the JP1_HOSTNAME environment variable has not been set. If you execute this command in an environment in which the JP1_HOSTNAME environment variable has been set, the command attempts to start JP1/AJS3 on the logical host set in the variable, not JP1/AJS3 on the physical host. If you want to start JP1/AJS3 on the physical host, delete the JP1_HOSTNAME environment variable. This command does not support a logical host.

• 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 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 command.

    In this case, if the setting lines have not yet been changed to comment lines when the jajs_start 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 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