JP2010072846A - Job operation management system and method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To restrain power consumption by stopping a job execution agent managed by a job management manager during a job execution idle period or by shifting the job execution agent to a power-saving mode. <P>SOLUTION: A job operation management system includes: the job execution agent for executing jobs; and the job management manager for managing the execution of jobs by the agent. The job management manager creates a job execution schedule in agent units of the job execution agent. The job management manager derives a period where no jobs are being executed from the job execution schedule in agent units. In a period where no jobs are being executed by the job execution agent, the job execution agent is stopped or set to be in a power-saving mode. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to a job operation management system and method, and in particular, in a computer system composed of a plurality of computers, during a period when a set of commands and applications specified by a user (hereinafter referred to as a job) is not executed. The present invention relates to a job operation management system and method in a computer system that can suppress power consumption in the computer by stopping the operation or by setting the power saving mode.

In recent years, the generation of CO ₂ in companies, general households, etc. has become a major problem, and the reduction thereof has been increasingly demanded. In particular, companies that a major source of emissions CO ₂ is reduced power consumption in order to reduce the CO ₂ has been determined as social responsibility.

  One method of reducing power consumption in a company is a method of reducing the power consumption of a computer system that is frequently used for business activities. This method uses a scheduling function of a job management system that manages jobs in a computer system or a task management function supported by the computer itself, and executes a command that supports stopping, starting, and changing to a power saving mode of the computer. By controlling the above, it is possible to manage computer stop / startup / change to the power saving mode in a time zone determined in operation, and to suppress power consumption in the computer system.

  In general, a job operation management system using computers includes a plurality of computers that actually execute jobs (hereinafter referred to as job execution agents) and a plurality of computers that manage execution of jobs by job execution agents (hereinafter referred to as job execution agents). The job management manager). The job management manager manages job execution by a plurality of job execution agents, and the job execution agent manages job execution from a plurality of job management managers.

  Therefore, the job operation management system uses its scheduling function to control the execution of commands that support stopping, starting, and changing to the power saving mode of job execution agents during times when jobs are not being executed. Next, create a job execution schedule for each job execution agent of the corresponding job execution agent (hereinafter referred to as a job execution schedule for each agent) in all job management managers that manage job execution of the job execution agent. It is necessary to confirm a time zone during which the agent is not executing a job (hereinafter referred to as a job execution idle period).

As a conventional technique related to the present invention, a technique related to a job scheduling analysis method is described, for example, in Patent Document 1 and the like. This conventional technique predicts a future job execution schedule based on past execution history information.
JP-A-8-286958

  In the above-described job operation management system according to the prior art using a computer, a job management manager manages a plurality of job execution agents, and a job execution agent is managed from a plurality of job management managers. For this reason, in order to stop the job execution agent during the job execution idle period or shift to the power saving mode, data defining the job execution schedule and job execution order of the job management manager (hereinafter referred to as job definition) It is necessary to identify the job execution idle period by checking the dependency relationship of the complex job consisting of

  The above-described job operation management system according to the prior art must manually define a job for specifying a job execution idle period, which causes a problem that it takes much time to specify the job execution idle period. In addition, when the job execution agent is manually stopped or shifted to the power saving mode, when the job is delayed on the job execution agent due to a failure or the like, it is difficult to change the plan. This causes a problem that it takes a lot of trouble.

  The object of the present invention is to solve the above-mentioned problems of the prior art, automatically calculate the job execution idle period of the job execution agent managed by the job management manager, and based on the calculated job execution idle period, It is an object of the present invention to provide a job management system and method capable of suppressing power consumption by stopping a computer that is a job execution agent or shifting to a power saving mode.

  According to the present invention, the object is a job operation management system in a computer system composed of a plurality of computers, and a job executed by a plurality of job execution agents, which are computers that execute jobs, and jobs by a plurality of job execution agents. A plurality of job management managers, which are computers for managing the execution of a job, and a job execution schedule database for each agent, the job management manager having a database storing job execution history data, and jobs of job execution agents A job execution management section that manages execution and updates job execution history data, an agent-based job execution schedule creation section that creates job execution schedules for each agent, and a job execution schedule for each agent A job execution schedule database update unit for each agent that updates juicy data, and an agent power management unit that manages the power of the job execution agent. The job execution schedule creation unit for each agent executes the job execution. Acquires historical data, creates job execution schedule data for each agent, stores it in the job execution schedule database for each agent, and the agent power manager manages the agent for each job execution agent from the job execution schedule database for each agent. The job execution schedule is acquired, the length of the period during which the job is not executed is calculated from the acquired schedule, and the job execution agent is executed during the time when the job is not executed. Was a stop or power saving mode Yuta, is accomplished by carrying out the return from the start or the power saving mode immediately before the next job execution.

  According to the present invention, without creating a job definition that explicitly stops the job execution agent or puts it into the power saving mode, the job execution agent is stopped or saved in the time period when the job execution agent is not being executed. Mode, and power consumption of the computer system can be suppressed.

  Embodiments of a job operation management system and method according to the present invention will be described below in detail with reference to the drawings.

  FIG. 1 is a block diagram showing a configuration of a computer system including a job operation management system according to an embodiment of the present invention.

  A computer system having a job operation management system according to an embodiment of the present invention shown in FIG. 1 includes a plurality of job management managers A 101 and B 102 which are computers for managing job execution by a plurality of job execution agents, and jobs. A plurality of job execution agents C103 and D104, which are computers to be executed, a job execution schedule database 106 for each agent holding a job execution schedule for each agent, and a plurality of terminals used by a user who manages job execution 201 is connected to the network 105 and configured to be able to communicate with each other.

  In the job execution schedule database 106 for each agent, job management managers A 101 and B 102 for creating a schedule (hereinafter referred to as an agent power schedule) for stopping the job execution agent C 103 or setting it to a power saving mode are provided. A schedule for executing a job of the job execution agent C103 to be created (hereinafter referred to as a job execution schedule) is stored. The job execution schedule database 106 for each agent also stores a job execution schedule for the job execution agent D104.

  Although FIG. 1 illustrates a computer system including two job execution agents and two job management managers, the number of job execution agents and job management managers may be arbitrary. Further, the computer system shown in FIG. 1 assumes that a large number of jobs are executed in a planned manner to some extent on a daily basis.

  FIG. 2 is a block diagram showing functional configurations of the job management manager A 101 and the job management manager B 102.

  The job management manager A 101 shown in FIG. 2A is a configuration example of a job management manager that performs power management of the job execution agents C103 and D104. The job management manager B 102 shown in FIG. This is a configuration example of a job management manager that does not perform power management of C103 and D104. The job management managers A101 and B102 are each a computer (information processing apparatus) including at least a storage device such as a CPU, a memory, and an HDD (not shown), and a database described later is stored in the storage device. In addition, a program for constructing various functions described later is loaded from the storage device into the memory. The program loaded in the memory constructs a predetermined function by being executed by the CPU.

  As shown in FIG. 2A, the job management manager A101 that performs power management of the job execution agents C103 and D104 has a job definition database 209, a job execution history database 210, and an agent power supply schedule database 211, and includes a terminal 201. A job definition database reference / updating unit 202 that updates the job definition database 209 according to an instruction from the user, a job execution management unit 203 that manages job execution of the job execution agents C103 and D104 and updates the job execution history database 210, and an agent A job execution schedule creation unit 204 for creating a job execution schedule for each unit, and an agent for updating the job execution schedule database 106 for each agent From the job execution schedule database update unit 205, the agent power schedule from the job execution schedule database 106 for each agent, the agent power management unit 206 that manages the power of the job execution agents C103 and D104, and all job management managers Each manager job execution management unit 207 that manages the job end upon receiving the job end notification of the job, and the job end notification unit 208 that notifies the job end to all the manager job execution management unit 207 are configured. Has been.

  The job management manager B102 that does not perform power management of the job execution agents C103 and D104 has almost the same configuration as the job management manager A101 as shown in FIG. The configuration of the job management manager A 101 is different in that the agent power management unit 206 and the all manager job execution management unit 207 do not exist.

  FIG. 3 is a diagram illustrating an example of job definition data in the job definition database 209 of the job management managers A 101 and B 102.

  Examples of the definition contents of the job definition database 209 of the job management managers A 101 and B 102 include, as shown in FIG. 3A and FIG. 3C, the job name 301, the job execution agent name 302, and the job execution as the fields. The contents 303 and schedule information 304 are included. The contents of these fields are as shown in FIGS. 3 (a) and 3 (c). The schedule information 304 indicates that the precondition for starting job execution depends on either time of day or end of job. Is set.

  For example, in the example of the job definition database of the job management manager A 101, the schedule information 304 of Job1 and Job2 is the start time 0:00, and the schedule information 304 of Job3 is the end of Job1 and Job2. Further, the schedule information 304 of Job4 is the start time 2:00. Further, in the example of the job definition database of the job management manager B102, the schedule information 304 of Job5 is 2:00 every day.

  Then, the job definition database reference update unit 202 displays the definition contents of the definition database 209 as described above so that the user can refer to and update the definition contents from the terminal 201. In this case, FIG. ) Is displayed as a GUI definition example 305 shown in FIG. 3B, and the example shown in FIG. 3C is displayed as a GUI definition example 305 shown in FIG.

  FIG. 4 is a diagram showing an example of job execution history data in the job execution history database 210 of the job management managers A 101 and B 102.

  As shown in FIGS. 4A and 4B, data examples of the job execution history database 210 of the job management managers A 101 and B 102 include, as their fields, an execution ID 401, a job name 402, a job execution agent name 403, A start time 404, an end time 405, and a job execution result 406 are included. The contents of these fields are as shown in FIGS. 4A and 4B, but the execution ID 401 is uniquely assigned in the job execution management system when the job is executed. It is.

  The job execution history database 210 is used by the job execution schedule creation unit 204 for each agent to obtain the estimated job execution time. In other words, the job execution schedule creation unit 204 collects job execution history records for each job using the job name 402 and the job execution agent name 403 as keys, and averages the difference between the end time 405 and the start time 404 of the collected records. Is calculated as the estimated job execution time. However, a job whose job execution result 406 is not normally completed or a record in which the difference between the end time 405 and the start time 404 is an exceptional value is excluded.

For example, when obtaining the estimated execution time of Job1 executed by the job execution agent C103, when the record having the job execution agent name of the job execution agent C103 and the job name of Job1 is extracted from the job execution history database 210, the execution ID 401 is “1”. ”,“ 11 ”,“ 21 ”, and“ 31 ”, but the job ID 401 is“ 21 ”in which the job has failed to start, and the difference between the end time 405 and the start time 404 is an exception. Since the job ID 401 that is a typical value is excluded from the record of “31”, the estimated execution time of Job1 is
((2008/1/1 0: 02-2008 / 1/1 0:00) + (2008/1/2 0: 04-2008 / 1/2 0:00)) / 2 = 3 minutes.

  As described above, the agent unit job execution schedule creation unit 204 creates an estimated job execution time for all jobs of the job execution agent C103 and creates an agent unit job execution schedule. Although not shown as an example, a job execution schedule can be similarly created for the job of the job execution agent D104.

  FIG. 5 is a diagram illustrating an example of data of a job execution schedule for each agent created by the job execution schedule creation unit 204 for each agent.

  As shown in FIGS. 5A and 5B created by the job management managers A 101 and B 102, the job execution schedule for each agent includes, as its fields, a date 501, an estimated job execution time 502, a job A name 503 and a premise job 504 are included. The contents of these fields are as shown in FIG. 5A and FIG. 5B. The prerequisite job 504 includes a job that is the schedule information 304 of the corresponding job in the job definition database 209. Is set.

  The agent unit job execution schedule database update unit 205 merges the agent unit job execution schedule with the agent unit job execution schedule created by another job management manager and stores the merged agent execution job database in the agent unit job execution schedule database 106. To do.

  FIG. 6 is a diagram illustrating an example of job execution schedule data for each agent in the job execution schedule database 106 for each agent.

  As shown in FIG. 6A, the agent-by-agent job execution schedule database 106 includes, as its fields, a date 601, an estimated job execution time 602, a job management manager name 603, a job name 604, and a prerequisite job 605. Has been.

  Then, the agent power management unit 206 of the job management manager A 101 searches for a time zone not corresponding to the estimated job execution time 602 in the job execution schedule database 106 for each agent, and creates a job power idle schedule in order to create an agent power schedule. Calculate the period.

  For example, as shown in FIG. 6B as the schedule image 606 of the job execution agent C103, the job execution estimated time end time of Job3 609 is 1:03, and the job execution idle period is calculated as Job4 611. If the start time of the job execution prediction time of Job5 612 is 2:00, the job execution idle period 1 610 is calculated as being from 1:03 to 2:00. In the above description, the idle period may be started by adding several minutes (arbitrary time) to the job end time, and the idle period may be ended several minutes (arbitrary time) before the start time of the next job.

  FIG. 7 is a diagram showing an example of agent power schedule data stored in the agent power schedule database 211.

  As shown in FIG. 7A, the agent power supply schedule data includes a definition 701, a precondition 702, an execution period 703, an execution destination agent 704, and an execution time 705 as fields. The definition 701 is a value that prescribes that the job execution agents C102 and D103 be "shifted to the stop / power saving mode" or "return from the start / power saving mode". The precondition 702 has a value only when the definition 701 is “transition to stop / power saving mode”, and ends all jobs scheduled to be executed from the previous start time or power saving mode return time. However, if the job is a precondition for another job and the other job is finished, the job that is always finished is excluded. For example, in the case of the third record example in which the implementation period 703 is “2008/2/1 1:55 to 24:00”, the image 706 of the agent power supply schedule of the job execution agent C shown in FIG. Confirming with the stop / power-saving mode period 2 708 is stopped or shifted to the power-saving mode, all jobs scheduled to be executed from the previous startup or power-saving mode return are Job4 611, and In the case of Job5 612, in the precondition 702, the end of Job4 611 and Job5 612 is set, and when the implementation period 703 is "2008/2/1 0: 0 to 1:50", stop / power saving Since it is a stop process in mode period 1 707 or a transition process to the power saving mode, it is scheduled to be executed from the previous start or the return to the power saving mode. All of the fixed jobs are Job1 607, Job2 608, and Job3 609. However, since Job1 607 and Job2 608 are the precondition jobs 605 of Job3 609, they are excluded. The end of Job3 609 is set.

  The implementation period 703 is a time limit for stopping the job execution agent or setting it to the power saving mode when the definition 701 is “transition to stop / power saving mode”. From the return time from the mode to the time excluding the time sufficient for the job execution agent C103 to stop and start (designated as 10 minutes in FIG. 7) from the end time of the job execution idle period. The execution period 703 is a time when the job execution agent is activated or returned from the power saving mode when the definition 701 is “return from the start / power saving mode”. A time is set by subtracting a sufficient time (5 minutes in the case of FIG. 7) for starting the job execution agent C103 from the end of the period. The execution time 705 is a field that is set after the job execution agents C103 and D104 are stopped, started, shifted to the power saving mode, or returned from the power saving mode. The job execution agent is actually stopped, started, and power saved. The time to shift to the mode or return from the power saving mode is set.

  FIG. 8 is a flowchart for explaining a processing operation in which the job management managers A 101 and B 102 create a schedule for the job execution agent C 103, which will be described next.

(1) First, the job execution schedule creation unit 204 for each agent of the job management managers A 101 and B 102 calculates the estimated job execution time from the job history information in the job execution history database 210, and based on the obtained estimated job execution time. Then, a job execution schedule for each agent of the job execution agent C103 is created (steps 801 and 802).

(2) Next, the agent-by-agent job execution schedule database update unit 205 acquires the agent-by-agent job execution schedule of the job execution agent C103 from the agent-by-agent job execution schedule database 106, and in addition to the agent of the job execution agent C103. It is determined whether or not a unit job execution schedule is registered (steps 803 and 804).

(3) If another job execution schedule for each job execution agent C103 is registered in step 804, the job execution schedule is merged with the registered data and executed in the job execution schedule database 106 for each agent. A job execution schedule for each agent of the agent C103 is registered (step 806).

(4) If no other job execution schedule for each agent of the job execution agent C103 is registered in step 804, the job execution for each agent of the job execution agent C103 is directly stored in the job execution schedule database 106 for each agent. A schedule is registered (step 805).

  FIG. 9 is a flowchart for explaining a processing operation in which the agent power management unit 206 of the job management manager A 101 creates an agent power schedule, which will be described next.

(1) First, the agent power management unit 206 of the job management manager A 101 acquires the job execution schedule for each agent of the job execution agent C 103 from the job execution schedule database 106 for each agent, and sets the job execution idle period from the acquired schedule. Calculate (steps 901 and 902).

(2) Next, it is determined whether or not there is a job execution idle period. If there is no job execution idle period, the processing here is terminated (step 903).

(3) If it is determined in step 903 that there is a job execution idle period, a job that is a precondition 702 for becoming the job execution idle period is obtained, an agent power schedule is created, and registered in the agent power schedule database 211. (Steps 904 to 906).

  FIG. 10 is a flowchart for controlling the processing operation of control in which the agent power management unit 206 of the job management manager A 101 stops the job execution agent C 103 or sets the power saving mode. This will be described next.

(1) When all manager job execution management units 207 of the job management manager A 101 receive a job end notification from the job execution agent C 103, the agent power management unit 206 of the job management manager A 101 determines that the job is stored in the agent power schedule database 210. It is determined whether or not the job is a precondition 702 (steps 1001 and 1002).

(2) If it is determined in step 1002 that the completed job does not correspond to the precondition 702, the job execution agent C103 is stopped or the control process for setting the power saving mode is not performed. Exit.

(3) If it is determined in step 1002 that the completed job is a job corresponding to the precondition 702, it is determined whether another job corresponding to the precondition 702 has not been completed. If the other job is not completed, the job execution agent C103 is stopped or the control process for setting the power saving mode is not performed, and the process is terminated (step 1003).

(4) If another job that is a precondition has been completed in the determination in step 1003, the current time is confirmed, and whether or not the current time corresponds to the execution period 703 of the agent power schedule. If it is determined that the job power supply schedule does not correspond to the execution period 703, the job execution agent C103 is stopped or the control process for setting the power saving mode is not performed, and the process is terminated (step 1004). .

(5) If it is determined in step 1004 that the current time corresponds to the execution period 703 of the agent power schedule, it is determined whether the job execution idle period is equal to or less than a predetermined time (step 1005). ).

(6) If it is determined in step 1005 that the job execution idle period is equal to or shorter than a predetermined time, the job execution agent C103 is suspended to enter the energy saving state, and the job execution idle period exceeds the predetermined time. If it has, the power of the job execution agent C103 is completely turned off, and the job execution agent C103 is stopped (steps 1007 and 1006).

(7) After the processing of Steps 1007 and 1006, the execution time 705 of the agent power schedule database 211 is updated and set, and the processing here ends (Step 1008).

  In the above-described processing, the length of the idle period for determining whether to stop the job execution agent C103 to enter the energy saving state or to completely turn off the power and stop the job execution agent C103 is determined by turning off the job execution agent. Taking into account the time required for startup from the start-up, the amount of extra power consumed at startup, etc., it is determined as appropriate depending on which can reduce more energy consumption compared to the case of energy saving. What is necessary is just to determine normally, for example about 1 hour.

  FIG. 11 is a flowchart for controlling the processing operation when notifying the user of how long the job execution idle period is in the job execution agent C103 or setting it to the power saving mode, which will be described next.

(1) In response to a user instruction from the terminal 201, the agent power management unit 206 extracts data having a value at the execution time 705 from the agent power schedule database 211 (step 1101).

(2) The execution time 705 of data whose definition 701 of the agent power supply schedule database 211 is “transition to stop / power saving mode” and the definition 701 paired with the data “return from stop / power saving mode” The length of the stop period of the job execution agent C103 or the period of the power saving mode is obtained from the difference from the data execution time 705, and the result is transmitted to the terminal 201 to notify the user (steps 1102, 1103). ).

  Through the above-described processing, the user can know the length of the stop period or the period of the power saving mode, and can know how much power consumption can be suppressed from the power consumption during the operation of the job execution agent C103. it can.

  Each process in the above-described embodiment of the present invention is configured by a program and can be executed by a CPU included in the present invention. These programs are stored in a recording medium such as an FD, CDROM, or DVD. It can be provided and can be provided by digital information via a network.

It is a block diagram which shows the structure of a computer system provided with the job operation management system by one Embodiment of this invention. FIG. 4 is a block diagram showing functional configurations of a job management manager A and a job management manager B. It is a figure which shows the example of the job definition data of the job definition database of the job management managers A and B. 6 is a diagram illustrating an example of job execution history data in a job execution history database 210 of job management managers A and B. FIG. It is a figure which shows the example of data of the job execution schedule for every agent which the job execution schedule preparation part for every agent produced. It is a figure which shows the example of the job execution schedule data per agent of the job execution schedule database per agent. It is a figure which shows the example of the agent power supply schedule data stored in an agent power supply schedule database. 6 is a flowchart for explaining a processing operation in which job management managers A and B create a schedule for a job execution agent C. 10 is a flowchart illustrating a processing operation in which an agent power management unit of job management manager A creates an agent power schedule. 6 is a flowchart for controlling a processing operation of a control in which an agent power management unit of a job management manager A stops a job execution agent C or sets a power saving mode. It is a flowchart for controlling the processing operation in the case of notifying the user of how long the job execution idle period is and whether the job execution agent C is stopped or in the power saving mode.

Explanation of symbols

101, 102 Job management manager A, B
103, 104 Job execution agents C, D
DESCRIPTION OF SYMBOLS 105 Network 106 Agent unit job execution schedule database 201 User terminal 202 Job definition database reference update part 203 Job execution management part 204 Agent unit job execution schedule creation part 205 Agent unit job execution schedule database update part 206 Agent power supply management part 207 All manager job execution management unit 208 Job end notification unit 209 Job definition database 210 Job execution history database 211 Agent power supply schedule database

Claims (6)

In a job operation management system in a computer system composed of a plurality of computers,
Equipped with multiple job execution agents that are computers that execute jobs, multiple job management managers that are computers that manage job execution on multiple job execution agents, and a job execution schedule database for each agent ,
The job management manager has a database storing job execution history data, creates a job execution management unit that manages job execution of job execution agents and updates job execution history data, and creates a job execution schedule for each agent. It consists of a job execution schedule creation unit for each agent, a job execution schedule database update unit for each agent that updates job execution schedule data for each agent, and an agent power management unit that manages the power of the job execution agent. ,
The job execution schedule creation unit for each agent acquires the job execution history data, creates job execution schedule data for each agent and stores it in a job execution schedule database for each agent,
The agent power management unit acquires the job execution schedule for each agent of the job execution agent from the agent execution schedule database, calculates the length of the period during which the job is not executed from the acquired schedule, and executes the job A job operation management system in which a computer as a job execution agent is stopped or put into a power saving mode during a non-working time period, and is started or restored from the power saving mode immediately before the next job execution.   The job operation management system according to claim 1, wherein the agent power management unit calculates a length of a period during which no job is executed in association with a job executed before or after a period during which no job is executed. .   3. The job operation management system according to claim 1, wherein whether to stop the computer or to enter a power saving mode is determined by a length of a period during which the job is not executed.   The job execution schedule creation unit for each agent creates individual job execution schedules for a plurality of job execution agents, and the job execution agent is not executed based on the plurality of job execution schedules. 4. The job operation management system according to claim 1, wherein the length is obtained.   5. The job management manager according to any one of claims 1 to 4, wherein the job management manager totals the time during which the computer is stopped or in the power saving mode during a period when the job is not executed, and reports the total to the manager terminal. The job operation management system according to 1. In a job operation management method in a computer system composed of a plurality of computers,
Equipped with multiple job execution agents that are computers that execute jobs, multiple job management managers that are computers that manage job execution on multiple job execution agents, and a job execution schedule database for each agent ,
The job management manager has a database storing job execution history data, creates a job execution management unit that manages job execution of job execution agents and updates job execution history data, and creates a job execution schedule for each agent. It consists of a job execution schedule creation unit for each agent, a job execution schedule database update unit for each agent that updates job execution schedule data for each agent, and an agent power management unit that manages the power of the job execution agent. ,
The job execution schedule creation unit for each agent acquires the job execution history data, creates job execution schedule data for each agent and stores it in a job execution schedule database for each agent,
The agent power management unit acquires the job execution schedule for each agent of the job execution agent from the agent execution schedule database, calculates the length of the period during which the job is not executed from the acquired schedule, and executes the job A job operation management method characterized in that a computer as a job execution agent is stopped or put into a power saving mode during a non-working time zone, and started or restored from the power saving mode immediately before the next job execution.

Images