7.9.3 Changing the date and time of the system
- Organization of this subsection
(1) For JP1/AJS3 - Manager and JP1/AJS3 - Agent
This subsection explains the procedure for changing the system's date and time of the system during JP1/AJS3 - Manager and JP1/AJS3 - Agent operation.
After the JP1/AJS3 service starts, if you change the system date and time to a large degree, for example, the change will affect the execution schedules of jobnets. If you need to significantly change the system date and time, do so when the JP1/AJS3 service is not running. Note that, if you move the system time backward, a repeated period arises in the system time flow. In this case, wait until the repeated period passes, and then start the service. If you need to start the service without waiting for the current time to match the old system time, reorganize the database environment and then cold-start the JP1/AJS3 service.
If you use the Network Time Protocol (NTP) or similar to adjust the server time in small increments, you will not need to stop and then cold-start the services as described below. When you use NTP or similar, we recommend that you make millisecond adjustments, adjusting the time continuously so that the clock does not show the same time twice.
If you change the system time on the host where JP1/AJS3 - Agent Minimal Edition is running, the change can affect the number of jobs executed per day. For cautionary notes on changing the system, see G.4(2) Change of the system time in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.
(a) Advancing the system time
To advance the system time to the current time:
-
End the JP1/AJS3 services.
-
Advance the system time.
-
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:
-
End the JP1/AJS3 services.
-
Return the time of the system.
-
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
If the system time is ahead of the current time and you move it back to the current time and immediately restart JP1/AJS3, the time at which JP1/AJS3 stopped becomes later than the time at which JP1/AJS3 restarted. In this case, you must perform the following tasks in JP1/AJS3 - Manager:
-
Rebuild the database environment
-
Delete the performance log file
-
Delete the execution agent performance log file
-
Delete the aggregation results of the number of job executions
-
Delete the aggregation results of the execution agent performance data
After moving the system time back to the current time, if you want to restart JP1/AJS3 immediately, perform the following procedure:
-
End the JP1/AJS3 services.
-
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.
-
If the execution agent performance report output function is enabled, delete the execution agent performance log files.
For details, see 5.3.2 Overview of the execution agent performance report output function.
-
(If the management portal execution environment has been set up and aggregation of the number of job executions or aggregation of the execution agent performance data is enabled) Terminate the JP1/AJS3 System Control Manager service.
-
(If the management portal execution environment has been set up and aggregation of the number of job executions is enabled) Delete the following folders or directories:
In Windows:
-
Physical host:
Mgr_Data_Path#\sys\jobagg
-
Logical host:
shared-folder\jp1ajs2\sys\jobagg
In UNIX:
-
Physical host:
/var/opt/jp1ajs2/sys/jobagg
-
Logical host:
shared-directory/jp1ajs2/sys/jobagg
For details about the management portal execution environment, see 6.7.3 Settings for the Web GUI (Management Portal) in the JP1/Automatic Job Management System 3 Configuration Guide.
-
-
(If the management portal execution environment has been set up and aggregation of the execution agent performance data is enabled) Delete the following folders or directories:
In Windows:
-
Physical host:
Mgr_Data_Path#\sys\agtagg
-
Logical host:
shared-folder\jp1ajs2\sys\agtagg
In UNIX:
-
Physical host:
/var/opt/jp1ajs2/sys/agtagg
-
Logical host:
shared-directory/jp1ajs2/sys/agtagg
For details about the management portal execution environment, see 6.7.3 Settings for the Web GUI (Management Portal) in the JP1/Automatic Job Management System 3 Configuration Guide.
-
-
Return the time of the system.
-
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.
-
Start the JP1/AJS3 services in cold-start mode.
-
(If the management portal execution environment has been set up and aggregation of the number of job executions is enabled) Restart the JP1/AJS3 System Control Manager service.
- #
-
The path indicated by Mgr_Data_Path differs depending on the installation folder.
- If the installation folder is the default installation folder or is in a folder protected by the system:
-
%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2
A folder protected by the system is the path to a folder in any of the following:
-
system-drive\Windows
-
system-drive\Program Files
-
system-drive\Program Files (x86)
The default value for %ALLUSERSPROFILE% is system-drive\ProgramData.
-
- If the installation folder is other than the above:
-
JP1/AJS3 - Manager-installation-folder
- 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.
-
(2) For JP1/AJS3 - Web Console
The following shows how to change the system date/time of JP1/AJS3 - Web Console. Note that a change to the system date/time is also applied to the system time zone settings.
-
Terminate the JP1/AJS3 - Web Console services.
Terminate the following two services:
-
JP1/AJS3 HTTP Server service
-
JP1/AJS3 Web Application Server service
-
-
Change the system date/time.
If you change the system date/time to a past date/time, you must also delete the directory that contains work files.
The directory that contains work files is as follows:
- In Windows:
-
System-folder-for-Web-Console-server\rcmd
- In UNIX:
-
System-directory-for-Web-Console-server/rcmd
-
Start the JP1/AJS3 - Web Console services.
Start the following two services:
-
JP1/AJS3 Web Application Server service
-
JP1/AJS3 HTTP Server service
-