Hitachi

Job Management Partner 1 Version 10 Job Management Partner 1/Automatic Job Management System 3 Administration Guide


7.1.1 Starting JP1/AJS3 services manually

This subsection describes how to start JP1/AJS3 services manually.

If JP1/AJS3 services are defined to start when the system starts, they start automatically.

Organization of this subsection

(1) In Windows

To start a JP1/AJS3 service manually in Windows:

  1. In the Control Panel window, choose Services. Alternatively, choose Administrative Tools and then Services.

  2. Select the JP1/AJS3 service you want to start.

    Select the required service from the following list of service names:

    • JP1/AJS3 service

    • JP1/AJS3 Mail service#1

    • JP1/AJS3 Console Manager service#2

    • JP1/AJS3 Console Agent service#3

    • JP1/AJS3 Check Manager service#4

    • JP1/AJS3 Check Agent service#5

    • JP1/AJS3 Queueless Agent service#6

    • JP1/AJS3 Queueless File Transfer service#6

    #1

    Displayed only when mail system linkage has been set up.

    #2

    Displayed only when JP1/AJS3 Console Manager has been set up.

    #3

    Displayed only when JP1/AJS3 Console Agent has been set up.

    #4

    Displayed only when JP1/AJS3 Check Manager has been set up.

    #5

    Displayed only when JP1/AJS3 Check Agent has been set up.

    #6

    Displayed only when the queueless job execution environment has been set up.

  3. Click the Start button.

    The JP1/AJS3 service you selected starts.

    You can also start a service by executing the net start service-name command.

Supplementary notes
  • You do not need to perform any operations for the JP1/AJS3 Database service during operation because these services are controlled by JP1/AJS3. If the embedded database uses a method from a version earlier than 10-00, the JP1/AJS3 Database ClusterService service is also started. However, in ordinary operation, you do not need to use this service.

  • Use the jajs_spmd_status command to check whether all processes of JP1/AJS3 service have started.

(2) In UNIX

You can start the following services as described below:

To start the above services:

  1. Copy the /etc/opt/jp1ajs2/jajs_start script to any file.

    Execute the following command to copy the script without changing the file permissions:

    cp -p /etc/opt/jp1ajs2/jajs_start any-file-name
  2. Use an editor such as vi to open the copy of the script, and then delete the comment symbols on the comment lines.

    For details about how to delete comment symbols, see 15.7.1 Setting automatic startup and termination of the JP1/AJS3 service in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

  3. Execute the script to start the JP1/AJS3 service.

You can also use the ajsqlstart command to start the queueless agent service, and use the ajsqlftpstart command to start the queueless file transfer service. In addition, you can use the ajschkstart command to start the JP1/AJS3 Check Manager service or JP1/AJS3 Check Agent service.

For details about the ajsqlstart, ajsqlftpstart, and ajschkstart commands, see 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2 or 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1.

Supplementary notes
  • You can start the JP1/AJS3 Console services by using the following commands:

    - JP1/AJS3 Console Manager service

    /etc/opt/jp1ajs2cm/ajscminetd_startstop start

    - JP1/AJS3 Console Agent service

    /etc/opt/jp1ajs2/ajscainetd_startstop start

  • The current directory for the JP1/AJS3 services is determined based on how the services are started, as shown below. Do not delete the current directory during the operation of a JP1/AJS3 service.

    - Started by the jajs_start script:

    /opt/jp1ajs2/bin

    - Started by the jajs_spmd command:

    The directory in which the command was executed

  • Use the jajs_spmd_status command to check whether all processes of JP1/AJS3 service have started.