Job Management Partner 1/Automatic Job Management System 3 Administration Guide
After a jobnet with start conditions has been registered for execution, you can use either of the two methods below to change an event job definition in the start conditions. The time the changes take effect are determined by the method.
- Cancel the execution registration of the jobnet with start conditions
Cancel the execution registration of the jobnet, and then re-register the jobnet for execution. The new definition takes effect when the jobnet is registered. If you do not cancel the execution registration, the new definition does not take effect until the next scheduled execution.
- Stop the scheduler service
Stop the scheduler service, and then restart it. When the scheduler service is stopped, the monitoring generations are set to the Interrupted monitoring status. The new definition takes effect when the scheduler service is restarted.
To stop the scheduler service, use one of the following methods.
- (a) Execute the ajsstop command.
- Execute the command as follows:
- ajsstop -F scheduler-service-name [-s|-n|-j|-k]
- For the command syntax, see ajsstop in 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1.
- (b) Execute the jajs_spmd_stop command.
- Execute the command as follows:
- jajs_spmd_stop -n jajs_schd -F scheduler-service-name -job
- For the command syntax, see jajs_spmd_stop in 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1.
- (c) In JP1/Power Monitor, set the program to wait for termination of a JP1/AJS3 jobnet, and then shut down the host using any of the following methods:
- - Execute a local power control job, specifying Planned termination as its Termination request type.
- - Execute a remote power control job, specifying Power off: Planned termination as its Request type.
- - Shut down the host from JP1/Power Monitor, specifying Planned termination.
Copyright (C) 2009, 2010, Hitachi, Ltd.
Copyright (C) 2009, 2010, Hitachi Solutions, Ltd.