Applicable versions and levels
Windows versions: V5.0L10 or later
Solaris versions: 5.0 or later
Linux versions: 5.2, V10.0L10 or later
Linux for Itanium versions: V12.0L10 or later
HP-UX versions: 5.1 or later
AIX versions: 5.1 or later
DS versions: V20L10
Action 1
Points to check
Was the start operation performed?
Was the restart operation performed?
Was the continue operation performed?
Cause
If the start or restart operation was performed, the job net will start instantly.
The job net will also start if the execution condition was met at the point when the continue operation was performed.
Action 2
Points to check
Has the system time been changed?
Cause
If the system time is changed while Jobscheduler is running, it may run at an unintended time.
Action method
Change the system time according to "To change the system time" below.
To restore the system time, delete the following files:
The jobdb1.log, jobdb2.log, and jobdb3.log files in the Jobscheduler database directory
All files under the net.spool subdirectory of the Jobscheduler database directory
Event log [Windows versions]
Start the Systemwalker Operation Manager service/daemon.
When a cluster system has not been installed
Execute the poperationmgr command to stop the Systemwalker Operation Manager service/daemon, and then change the system time.
When a cluster system has been installed
Use the cluster software to stop the Systemwalker Operation Manager cluster application, and then change the system time.
Do not change the system time while Jobscheduler is running.
Action 3
Points to check
Has the holiday calendar or schedule pattern been changed?
Cause
In V5.0L20 or earlier or V5.1 or earlier, the startup days are re-created if the holiday calendar or schedule pattern is changed.
In V5.0L30 or later or V5.2 or later, if the Halt recreation of startup days for holiday calendars and jobnets using a schedule pattern check box has not been selected on the Use function2 tab in the Define Jobscheduler Startup Parameters window, the startup day will be created again when the holiday calendar or schedule pattern is changed.
If the startup day is created again, the startup day may be changed according to the definition on the Startup Days tab and the Calendar tab (V13.3.1 or earlier) in the Job Net Properties window.
Action method
Review the startup day definition.
Action 4 [Windows versions]
Points to check
Is the schedule server Windows Server 2003?
Was system (operating system) time correction performed automatically by NTP?
Is the BIOS clock (time) slow or fast?
Was the job net that was started at the unintended time the first one to be executed after Jobscheduler starts?
Cause
In environments in which time compensation is performed automatically, if the BIOS clock (time) is slow or fast, time compensation for the system (operating system) clock is performed according to the NTP server clock when the system is started by the W32Time service.
In Jobscheduler, set the execution time of the job net to be executed first when the Jobscheduler service starts.
If the Jobscheduler service is started before the W32Time service, the first job net is started using the clock before time compensation is performed by the W32Time service.
For this reason, if the BIOS clock is slow or fast, the job net started first may be started at an unintended time.
Action method
If the difference in time between the BIOS clock and the NTP server clock is great (slow or fast), set the BIOS clock to the NTP server clock.
Information
Normally, the BIOS clock is also compensated when the W32Time service ends, for example, so there is no great deviation between the NTP server and the BIOS clock.
However, in Windows Server 2003, the BIOS clock is not compensated when the W32Time service ends, so there are cases where the difference between the NTP server and the BIOS clock becomes gradually greater during operations that continue for a long time.
