9.4.2 Important notes on checking a job status
This section describes provides important notes on checking a job status.
- Organization of this subsection
(1) Holding reports from relay systems
When a job is executed from the managing server, the managed computers automatically report the results to a higher level system. If the job is executed via a relay system, the relay system reports the results on the managed computers and the relay system to an upper system.
However, if the job execution results are reported from a relay system when the network is busy, the network may be overloaded. In this case, you can temporarily suspend reporting from the relay systems. To suspend reporting, execute a Hold report job whose destination is set to the relay system. Similarly, to resume the reporting, execute a Hold-report release job.
You can check if the reporting is suspended or not for a relay system by selecting the relay system in the System Configuration window or Destination window and opening the Attribute page.
Note that if the suspended relay system is a relay managing the ID, the results of the jobs that are set to that ID group are also processed by the relay system.
(2) When the status of a job via a relay system does not change
In the cases of the following jobs, the execution status on Remote Installation Manager will not change until the file transfer finishes between the relay system and a lower level system.
-
A job on which split distribution of the package is specified#
-
A job on which a lower system failed to start up in an in-between relay system
#: If the Notify JP1/IT Desktop Management 2 - Manager of the status of the split distribution executed on the lower JP1/IT Desktop Management 2 - Agent check box has been selected in the Settings to send notifications to JP1/IT Desktop Management 2 - Manager page opened from the Relay system settings in the agent settings, the execute status will change.