7.6.12 Suspending and restarting a running job
When you want to complete package distribution during a time frame of light network load, distribution processing might not finish within the time frame. In such a case, you can temporarily suspend a running job to control the time frame during which the job is executed. Later, the suspended job can be restarted from the point where it was suspended.
Use the following methods to suspend and restart jobs:
-
Issuing a suspension or restart instruction from the managing server to the relay system or management relay server
Execute Suspend file transfer and Resume file transfer jobs on the managing server to instruct the relay system or management relay server to suspend and restart the job. If you specify a schedule to execute these jobs beforehand, you can perform operations, such as suspending package distribution just before business hours and restarting package distribution just after business hours.
-
Issuing a suspension or restart instruction to the managing server itself
You can issue a suspension or restart instruction to the managing server itself to which the Remote Install Manager is connected. To do this, from the Execute menu of the Remote Install Manager, select Suspend/Resume File Transfer and then Suspend or Resume.
-
Executing the dcmsusp command on the managing server
You can use the dcmsusp command to automatically suspend and restart package distribution. You can specify both the relay system (or management relay server) and the local system as the target of a suspension instruction.
You can use these methods all together. For example, you can execute the Suspend file transfer job on the relay system to suspend file transfer, and then execute the dcmsusp command to restart the file transfer.
For details about the scope of job suspension and restarting, see 3.1.6(6)(c) Scope of suspension and resumption of job distribution.
- Organization of this subsection
(1) Relationships between job suspension/restarting and other operations
The relationships between job suspension/restarting and other operations are described below.
- Relationship with multicast distribution
-
You cannot suspend jobs specifying multicast distribution. Even if you execute job suspension on the relay system, the job continues running. However, a job specifying multicast distribution is suspended if you execute job suspension on a computer that contains at least one Install package job that is already being suspended.
- Relationship with split distribution
-
You can suspend jobs specifying split distribution in the same way as normal jobs. If you suspend such a job while split packages are being transferred, package transfer restarts from the point where it was suspended. When package transfer is suspended, the packages are further split, and the transfer is not restarted until the specified distribution interval has passed.
- Relationship with the Client Control facility
-
You can suspend jobs specifying Client Control in the same way as normal jobs. When you suspend or restart such jobs, the system behaves as below. If the target computer is an agent for UNIX, Shut down the client after the job execution is disabled.
- If you specify Start the target computer if it is not running and Shut down the client after the job execution:
-
-
The computer turns on.
-
<An instruction to suspend the job is issued.>
-
The computer turns off.
-
<An instruction to restart the job is issued.>
-
The computer turns on.
-
The job finishes.
-
The computer turns off.
-
- If you specify Start the target computer if it is not running:
-
-
The computer turns on.
-
<An instruction to suspend the job is issued.>
-
The computer remains on.
-
<An instruction to restart the job is issued.>
-
The job finishes.
-
The computer remains on.
-
- If you specify Shut down the client after the job execution:
-
-
The job is running.
-
<An instruction to suspend the job is issued.>
-
The computer turns off.
-
<An instruction to restart the job is issued.>
-
The computer remains off, and the job does not restart.
-
(2) System behavior when you change the route to a computer during job suspension
If you change the route to a computer during job suspension, the system behaves as follows:
-
If you change the route to the relay system or management relay server where a job is being suspended, the suspension status is not released, and the job remains suspended. The job processing results are posted to the host system through the previous (pre-change) route.
-
If you change the route to a suspended job on a computer, any files that have been transferred to the computer are deleted (the suspended job is deleted).