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

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


11.3.1 Monitoring JP1/AJS3 processes

In JP1/AJS3, you can start or terminate the scheduler service only. Therefore, if only the processes of the scheduler service are terminated, the entire JP1/AJS3 is active.

You can use the jajs_spmd_status command to monitor the major processes of the JP1/AJS3 service.

You can use the jajs_status command to monitor the processes of the scheduler service.

Cautionary notes
  • You can use the jajs_spmd command to start the processes of only the scheduler service. Also, you can use the jajs_spmd_stop command to stop the processes of only the scheduler service. Therefore, when you start or stop only the scheduler service, make sure that the process monitoring does not assume the start or stop of the scheduler service to be an error.
  • If an error occurs in a scheduler service process and the scheduler service stops, the process is automatically restarted. In this case, no process exists after the scheduler service stops until it is restarted. After the scheduler service is restarted, the process ID changes. Therefore, in consideration of the case whereby the automatic restart of the scheduler service allows the operation to continue, we recommend that you do not monitor the processes of the scheduler service.
    If the following behavior is repeated three or more times, the automatic restart of the scheduler service is disabled: After a scheduler service process is started, the scheduler service stops within 6 hours.
  • If an error occurs in a scheduler service process and the scheduler service stops, the JP1/AJS3 service continues to wait to accept the jajs_spmd command. Therefore, if only the scheduler service has terminated abnormally, the jajs_spmd_status command cannot detect an error. Use the jajs_status command to check the status of the process.

[Contents][Back][Next]


[Trademarks]

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