This section explains how to determine the startup days for job nets.
You can define startup day information in the Startup days tab of the Job Net Properties window.
Determine the following three items in relation to the startup days:
Determine the basic settings for the startup days.
Determine the detailed settings for the startup days, such as the operation period and shift settings for the startup days.
To set up individual startup days that do not fall into patterns (for example, starting job nets on a particular date, such as "December 20"), determine the settings for unscheduled days after determining the basic settings.
Note that job nets will not run on a day that has been set up as a startup day if the power to the server is not turned on. Ensure that the days specified as the startup days for job nets are days when the power will be turned on.
There are three methods of setting up the basic startup days, as described below. Determine which method to use to set up the basic startup days.
This method involves setting up the basic startup days by selecting a schedule pattern (a startup day pattern for one year).
Registering a schedule pattern beforehand makes it easy to register the startup days for job nets, and so, this method is suitable for situations where there are multiple job nets with similar startup day patterns.
For this method, a schedule pattern must be created beforehand. Refer to "Registering the Schedule Pattern" in the Systemwalker Operation Manager User Guide for details on schedule patterns.
This method uses the schedule of another job net for which the startup days have already been set up.
Use this method to start a job net on the same days as schedule of another job net.
In additions, to use schedule of another job net, it must be registered as a base job net.
This method involves specifying the startup days directly.
Use this method to specify the basic startup days when it is necessary to set up specific startup days for individual job nets.
For example, the following specifications are possible:
Particular date for every year
For example, "April 4, every year", the particular pattern for every year can be specified.
Particular date or day of the week for every month
For example, "the 20th of every month", or "the Monday of the week", the particular pattern for every month can be specified. It is also possible to specify "the last day of the month."
Business days
It is possible to specify which day is the first day of the business, and then specify a certain number of business days, either counting forwards from the first day of the business month or counting backwards from the last day of the business month (the day before the day specified as the first day of the business month).
If necessary, determine the following detailed settings:
To shift the startup days relative to the startup days specified using the Schedule pattern, Another job net, or Other radio buttons, determine the shift direction, the number of days to shift, and how to handle holidays.
Determine how to handle a startup day that coincides with a holiday in the calendar. The following items can be specified:
Whether to start the job net
Whether to shift the startup day
Shift direction
Number of days to shift
To use calendar holiday settings, specify which calendar to use. To use multiple calendars, determine the conditions(AND or OR conditions) for combining the calendars as well.
Note that the holidays that have been specified in the SYSTEM_CALENDAR are used as the schedule for turning the power on and off. This means that if Power Control is performed, neither servers nor job nets will start on days that have been specified as holidays in the SYSTEM_CALENDAR even if the SYSTEM_CALENDAR is not selected as the job net holiday calendar.
To restrict the operation period of a job net, determine the operation period.
To set up individual startup days that do not fall into patterns (for example, starting job nets on a particular date, such as "December 20"), design and adjust the settings for unscheduled days at the end after the basic startup days settings are complete.
You can fine tune startup days in the Startup Days window, Startup Days (Preview) window, or Application Plan window. However, note that the startup days specified in these windows are known as exception days and may be cleared when the calendar or the startup days are changed.
Refer to "Startup Day Information" in the Systemwalker Operation Manager User Guide for details on exception day.
Essentially, child job nets in a layered job net start when their parent job net starts. However, you can start child job nets using a different schedule from the parent job net by setting a different startup day for each child job net.
Specifying startup days for the child job nets enables you to, for example, change the job net flow configuration by day.
Refer to "I Want to Change the Flow Configuration per Day" in the Systemwalker Operation Manager How-To Guide for details.
If you specify startup days for a child job net or master linked job net, you must validate the specified startup days by specifying Validate only on startup days in the Add/Change - Job window for the child job net or master linked job net.
