Hitachi

Job Management Partner 1 Version 10 Job Management Partner 1/Automatic Job Management System 3 Messages 1


KAVS1989-E

The operation is not possible because the service (service-name) is not running.

The service indicated in service-name has not started, so command operation cannot be performed.

(S)

Cancels command execution.

For the queueless cluster process, the system cancels the processing to attach the logical host. Then, by default, the system continues startup processing without abnormally terminating the queueless cluster process.

If you want to abnormally terminate the queueless cluster process, specify error for the AJSQL_CLUSTERREQ environment setting parameter.

For details about AJSQL_CLUSTERREQ, see 2.7 Setting up the queueless job execution environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

If the processing to detach the logical host has been canceled, the system abnormally terminates the queueless cluster process.

(O)

Check that the service has started, and then execute the command.

If the service has started, wait a while and then retry the operation. If the retry does not correct the error, contact the system administrator and collect data (see 1.2.3 To the system administrators).

You can use either of the following methods to check whether the service has started:

In Windows:

In Control Panel or Administrative Tools, double-click Services, and check the status of the service.

In UNIX:

Use the ps command to make sure that the service for the process exists.

For details about the process that you should check, see B.3 Processes (for UNIX) in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.

If this message is output when the queueless cluster process is being started, wait until the service has started, and then take either of the following actions to attach the logical host:

  • Restart the JP1/AJS3 service.

  • Use the ajsqlattach command to attach the logical host.

If this message is output when the queueless cluster process is being stopped, no action is necessary because the service has already stopped.