You can set an example time (or virtual time) in the subsystem to be operated in the test mode and check the expected schedule execution.
In the Standard Edition version, however, you can set the virtual time but you cannot operate the subsystem in the test mode.
The following describes how to operate the subsystem in the test mode.
Procedure
Extracting and distributing the schedule information
Distribute the policy of schedule information you have extracted from the actually operating subsystem to the subsystem to be operated in the test mode. For the policy distribution, see the Systemwalker Operation Manager Installation Guide.
Setting the virtual time
Set the virtual time (an example time) in the subsystem to be operated in the test mode. The virtual time can be set by defining on the Test mode sheet of Define Jobscheduler Startup Parameters window.
Figure 4.37 Define Jobscheduler Startup Parameters window - Test mode sheet
Displays a shift from the system time if the virtual time is set.
Use this option to change the virtual time setup.
Specifies the date and time of virtual time. You cannot set a past time.
Releases the date and time of virtual time.
Disabling the job
Disable the jobs you must not execute in the subsystem in the test mode. For details on how to disable, see "Chapter 7 Operating Jobs".
Restarting the service/daemon
Restart the Jobscheduler service/daemon and operate it in the test mode.
Note
Setting the virtual time beyond the year end
If you set a virtual time beyond the year end, the calendar showing three years from the year set for the virtual time is temporarily displayed during the test mode operation. The calendars before the year set for the virtual time are erased.
If you release the test mode in the virtual time and return to the current clock time, the Startup days calendar showing three years including the current year will be created. When this three-year startup day calendar is created, new startup days will be created for years where startup days had not been created. For years where startup days had already been created, the existing startup day information will be retained. At this time, the calendars already erased during virtual time setup may not be different from the previous ones even when recreated.
The following gives examples when the calendars are recreated and when not recreated.
If you set the startup day on the calendar automatically generated (such as schedule patterns and the Startup days sheet of the Job Net Properties window), the same calendar as before will be automatically created when you release the test mode operation.
For the startup day individually set in the Startup Days window, its calendar will not be automatically created when you release the test mode operation. You must individually set the startup day again.
Note
Registering new job nets when a virtual time has been set up
If the date is moved forward by setting a virtual time and then a job net is registered, past dates cannot be specified as startup days. This means that it may be necessary to specify startup days again if a job net has been registered in this kind of situation and then virtual time has been cleared.
