Systemwalker Operation Manager Technical Guide

1.2.4 Operations for Daily Schedule Management

During normal operations, a single database is used to control both the definition information for jobs and job nets and the schedule information for each system (or subsystem). Schedule information is updated each time the process date changes.

When the Systemwalker Operation Manager Master Schedule Management function (hereafter referred to as the "Master Schedule Management function") is enabled, schedule information is combined with the definition information for jobs and job nets, and managed as a single "master data" set for each system (or subsystem). The schedule information is created by distributing it across process dates based on the master data. By using it, an operation with only a specific date that is not a routine task can be set in advance and the original settings can be automatically restored after the operation has been performed.

The Master Schedule Management function creates the schedule information for each process date by extracting only the data required for that process date from the master information. Accordingly, if, for example, there are a large number of job nets that are only executed once a month, the created schedule information will be smaller and have better execution performance.

Note also that in UNIX, the server load from schedule processes can be balanced by distributing it across schedule servers.

Normal operations

When the Master Schedule Management function is enabled

When the Systemwalker Operation Manager Master Schedule Management function is enabled, the following operations become possible.

• Daily schedule management

  Schedule information can be held for each process date. Past, present and future schedule information sets can be managed separately for different days.

• Daily schedule distribution [UNIX version]

  Schedule information can be distributed to up to five schedule servers and used for job scheduling. Definition information for jobs and job nets can be stored on the management server, and jobs can be executed on distributed servers based on the schedules stored on schedule servers.

• Operation changes

  If information for jobs and job nets changes significantly due to significant changes to the content of jobs, the modified definition information and schedule information can be registered in advance. When the release date arrives, the current master data can be swapped with the new master data automatically. Jobs and job nets can then be executed based on the new definition information and schedule information.

• Carried over job nets

  Job nets are managed for each process date. Job nets that span multiple process dates (referred to as "carried over job net") hold information such as which process date they started on, and their status when the process date changed. Users can specify how to handle job nets that span more than one process date, and can take actions if necessary. This makes it possible to control jobs taking process dates into account.

• Monitoring and operating schedule information

  The status of schedule information, which is managed separately for each process date, can be monitored via the GUI on the Operation Manager Client, and operations relating to schedules can also be performed. Job nets that span more than one process date can be monitored and operated from the GUI on the Operation Manager Client.

The following section explains operation configurations where the Master Schedule Management function is enabled, and is organized as follows.

• System operations controlled by a single server

• System operations controlled by multi-servers

System operations controlled by a single server

In this configuration, a single server is used to manage and schedule jobs (acting as both a management server and a schedule server).

System operations controlled by multi-servers [UNIX version]

In this configuration, definition information is stored on the management server, and schedule information is distributed to schedule servers. Schedule information can be distributed to up to five schedule servers.

Point

Guidelines for using the Master Schedule Management function

The Master Schedule Management function should be used if:

• There are job nets whose execution conditions may not be met on the same process date or whose execution takes a long time, so that they often do not complete within the same process date.

• There are job nets that do not complete within the same process date, and the execution schedule for the next day needs to be controlled.

• A large number of jobs or job net definitions exist, but only a limited number of job net operations are performed per day, because there are a large number of job nets that are only executed once a month.

Note that the Master Schedule Management function should be used to distribute the load across schedule servers in cases such as the following:

• A large number of jobs or job net definitions exist, inhibiting the execution of other jobs on that process date.

As a guideline, a single subsystem can process up to 20,000 jobs or 2,000 job nets, and a single server can process up to 100,000 jobs or 10,000 job nets. If there are more jobs or job nets, the performance of the entire system can be improved by distributing to multiple schedule servers using the Master Schedule Management function.

However, these process counts may vary depending on the system operating environment and operation requirements. When handling a large amount of jobs and job nets, perform thorough testing during the system operation design phase by referring to "Tuning of Performance" in the Systemwalker Operation Manager User's Guide.

Execute normal operations in cases such as the following:

• Jobs and job nets are completed before the end of the process date on which they are executed, and are rarely carried over until the next day to be executed.

Operation configurations with multiple zones

In this configuration, the Zone function supported by Solaris 10 or later is used to store definition information in the Global Zone and distribute schedule information to Non-global Zones.

Refer to the Systemwalker Operation Manager User's Guide - Master Schedule Management for information on how to operate the Master Schedule Management function.