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 execution condition changed for a job net not yet started for which the scheduled start time was exceeded?
Cause
When the job net execution condition is changed (this includes changes to calendars), the schedule will be created again. At this time, for a job net not yet started for which the execution time was exceeded, the next (future) schedule will be used.
Action method
Change the execution condition for the job net at a time that will not affect the job net operation.
Action 2
Points to check
Has the policy been distributed?
Cause
When Systemwalker Operation Manager is restarted following distribution of the Calendar policy, the startup days for job nets that are using the changed calendar are re-created. For this reason, the startup days set in the Startup Days window or the Application Plan window will be cleared individually.
If the only policy distributed is Schedule DB/schedule pattern, the startup days will not be re-created, and the information at the time the policy is extracted will be used for the startup days.
Action method
Firstly, in the Startup Days window, check if the applicable day is the startup day. Afterwards, perform the following procedure as necessary.
After distributing the Calendar policy, reset the startup days in the Startup Days window or the Application Plan window individually.
In V5.0L30/5.2 or later, to suppress again the creation of the job net startup day by the Calendar policy distribution, select Halt recreation of startup days on the Use function2 tab in the Define Jobscheduler Startup Parameters window (this window is displayed by clicking Startup parameter in the Systemwalker Operation Manager Environment Setup window) (*1). It is necessary to restart Jobscheduler afterwards.
If the only policy distributed is Schedule DB/schedule pattern, use one of the following methods to correct the startup days setting.
Set the startup days individually in the Startup Days window or Application Plan window.
Change the startup days in the Job Net Properties window.
Change the schedule pattern and calendar used by the job net (*2)
*1: The startup days will not be re-created if the Halt recreation of startup days check box is selected under the Use function2 tab in the Define Jobscheduler Startup Parameters window.
*2: This affects all job nets that use a schedule pattern and calendar.
