7.9.3 Changing the date and time of the system

(a) Advancing the system time

To advance the system time to the current time:

1. End the JP1/AJS3 services.

2. Advance the system time.

3. Start the JP1/AJS3 services.

(b) Moving the system time backward and waiting until the repeated period passes

To return the system time to the current time:

1. End the JP1/AJS3 services.

2. Return the time of the system.

3. When the time of the system reaches the actual time, start the JP1/AJS3 services.

   For example, assume that 02:00 is returned to 01:00 in step 2. After the system time becomes 02:00, start the JP1/AJS3 services.

(c) Moving the system time backward and starting JP1/AJS3 immediately

The following procedure describes how to move the system time back to the current time and then start JP1/AJS3 immediately. In this case, the next start time of JP1/AJS3 is earlier than the time at which JP1/AJS3 was stopped. Therefore, you must reorganize the database environment of JP1/AJS3 - Manager.

1. End the JP1/AJS3 services.

2. If the performance report output function is enabled, delete the performance log files.

   For details, see 5.3.1 Overview of the performance report output function.

3. Return the time of the system.

4. Re-create the database environment.

   For details, see 23.4.1(6) Setting up an embedded database again in the JP1/Automatic Job Management System 3 Configuration Guide.

5. Start the JP1/AJS3 services in cold-start mode.

Cautionary notes

• If you move the system time backward on a JP1/AJS3 - Agent host, you cannot search for JP1 events that were received before the monitoring of event reception was started.

• In the job definition, if Normal if file was updated is specified as a condition for the end judgment of a job and, after the system date and time is changed, if the file is updated before the actual date and time when the file was created, the file update cannot be detected, and the job might end abnormally.

  During the end judgment, the file-update date and time obtained when the job started and the file-update date and time obtained when the job ended are compared.

  For example, suppose a job starts at 11:00 every day and, after a file is updated at 12:00, the job ends at 13:00 and then end judgment is performed. At 14:00 on October 10, the JP1/AJS3 service is stopped, and then the system date and time is changed to 10:00 on October 9.

  The file-update date and time obtained at 11:00 on October 9 when the job started is 12:00 on October 10, which is the date and time when the file was updated by the job prior to when the system date and time was changed. The file-update date and time obtained at 13:00 on October 9 when the job ended is 12:00 on October 9, which is the date and time when the file was updated by the job after the system date and time was changed. During the end judgment, no file update is detected, so the job is not recognized as having ended normally.

  For this reason, after you change the system date and time while the JP1/AJS3 service is stopped, before executing a job, you will need to adjust the file-update date and time to match the current system date and time, for example, by manually updating the file.