2.2.5 Necessary tasks when changing the date/time of a monitored host
The following describes the effects of changing the date/time of a monitored host, and the tasks that are required when you make these changes.
- Organization of this subsection
(1) Changing the date/time of a monitored host in an agent configuration
When changing the date/time of a monitored host in an agent configuration, perform the tasks required to change the system date/time described in the Job Management Partner 1/Base User's Guide.
(2) Returning the date/time of a monitored host in a remote monitoring configuration to a past date/time
If you reset the date/time of a monitored host in a remote monitoring configuration back to the original date/time after you have intentionally changed the date/time to a future date/time for testing or other purposes, you must delete the event log for the set future date/time on the host.
Use the following procedure to reset the date/time. Note that if the OS on a monitored host in remote monitoring configuration is UNIX, the following tasks are unnecessary.
-
If there is a remote monitoring event log trap that is running on the host, stop it.
-
Change the date/time of the host.
-
Confirm that the host does not have an event log whose date/time is later than the current date/time on the host. If there is such a log, delete the corresponding event log.
-
Restart the stopped remote monitoring event log trap.
Note that if the difference between the date/time of the host on which JP1/IM is running and the date/time of a monitored host is greater than the monitoring interval, you cannot monitor the host by using a remote monitoring event log trap. When changing the date/time of a monitored host, also check the date/time of the host on which JP1/IM is running.
(3) Setting the date/time of a monitored host in a remote monitoring configuration forward
No tasks are necessary for setting the date/time of a monitored host in a remote monitoring configuration for a reason such as a clock delay.