3.5.7 Defining a different calendar for each application

Sometimes a certain application or a particular department will have different open days. In such a case, you can define different calendars for different applications.

As an example, consider a case in which the Tokyo head office, the Osaka branch office, and the Nagoya branch office all execute a certain application, but run the application on different days. The respective application calendars are as follows.

Tokyo head office: Execute daily
Osaka branch office: Execute Monday through Saturday
Nagoya branch office: Execute Monday through Friday

There are two ways of structuring the application.

Group all jobnets with the same application calendar in job groups.
Create the application within one job group, and refer to calendars of other job groups.

These methods are explained in detail below.

Organization of this subsection

(1) Grouping jobnets with the same application calendar in job groups
(2) Creating the application within one job group, and referencing calendars defined for other job groups
(3) Examples of calendar work tasks

(1) Grouping jobnets with the same application calendar in job groups

This method is best used for applications that meet the following conditions:

There are multiple application groups, but no dependent relationships between the application groups.
There is a system administrator responsible for each application group.
Multiple application groups are managed by one manager.

The following figure shows an example of the application configuration.

Figure 3‒13: Grouping jobnets with the same application calendar in job groups

An overview of the method used to set the schedule is given below.

Create job groups for Tokyo, Osaka, and Nagoya under the scheduler service.
Define jobnets under each job group.
Define a calendar for each job group.
Register the jobnets for execution.

To Page Top

(2) Creating the application within one job group, and referencing calendars defined for other job groups

This method is best used for applications that meet the following conditions:

There are multiple application groups, and dependent relationships between the application groups.
One system administrator manages all applications.

The following figure shows an example of the application configuration.

Figure 3‒14: Referring to a calendar of another job group

An overview of the method used to define the schedule is given below.

Create a single jobnet (jobnet 1) under the scheduler service.
Define the applications to be executed at Tokyo, Osaka, and Nagoya as nested jobnets within the root jobnet.
Specify the calendar of the Tokyo head office in the scheduler service.
Create job groups for Osaka and Nagoya.
Define calendars for the Osaka and Nagoya job groups.

Define only calendars for these job groups; do not create jobnets for them.
Set the nested jobnets you want to execute at each branch to refer to the calendar defined for the respective job group.

In the Schedule Settings dialog box, select Refer to a calendar of another job group. Set Osaka application 1 and Osaka application 2 to refer to the calendar of the Osaka branch job group. Set Nagoya application 1 and Nagoya application 2 to refer to the calendar of the Nagoya branch job group.
Register the root jobnet for execution.

With this method, you can monitor all of the jobnets in a single monitor window.

To Page Top

(3) Examples of calendar work tasks

This subsection presents some examples that show how calendars are applied.

Example 1

In the first example we will explain how to set a calendar premised on the following conditions:

There are multiple work task groups, but there is no interdependency among the information in the individual calendars.
Each work task group is controlled by its own system administrator.
The multiple work task groups are managed by a single work task manager host.

Based on these premises, we will create a hierarchy for the work task group and define calendars, as shown in the following figure.

Figure 3‒15: Calendar work task example 1

When working from the monitor screen with an example like this, you can only check the execution schedule and results of work tasks under a single work task group (for example the Tokyo group) at one time. In a situation where multiple system administrators are managing individual work task groups, this arrangement makes it easy for the responsible system administrators to check the schedules and results for the work tasks they are concerned with.

Example 2

We will explain the setting of a calendar premised on the following conditions.

There are multiple work task groups and the information in their calendars is interdependent.
All of the work tasks are managed by a single system administrator.

Taking these conditions as the premises, we will create a hierarchy for the work task group and define a calendar, as shown in the following figure.

Figure 3‒16: Calendar work task example 2

When you make the settings in the figure above, the individual work tasks are executed as follows.

Tokyo work tasks: The work tasks reference a calendar for daily execution so they are executed every day.
Hiroshima work tasks: The work tasks reference a calendar in which only Sunday is a closed day, so they are executed from Monday through Saturday.
Nagoya work tasks: These work tasks reference a calendar in which Saturdays and Sundays are closed days, so they are executed from Monday through Friday.

In this example, if you check the group AJSROOT1 on the monitor screen, you can check the schedules and results of all the work tasks under this group. This makes it easy for a single system administrator to manage all the work tasks.

To Page Top