JP5539829B2 - Job scheduling apparatus and job scheduling program - Google Patents

Description

  The present invention relates to a job scheduling technique for performing a job execution schedule in a job operation management system operating on a computer.

  2. Description of the Related Art Conventionally, in a job operation management system that runs on a computer, a proposal has been made regarding a job scheduling apparatus that performs a schedule for executing each of a large number of jobs that are performed in business.

  For example, Patent Document 1 below discloses a technique for performing job scheduling automatically and efficiently by setting a job schedule by using an input device.

  Patent Document 2 discloses a technique that can easily confirm whether or not a job is scheduled on an intended date by specifying job information and calendar information with parameters from a screen and simulating them. Yes.

JP 2001-312412 A JP-A-6-83646

  However, in the conventional job operation management system as described above, the schedule specification for determining whether to execute the job, the calendar information for determining the operation day or the closed day, and the schedule rule such as the execution date and time, the transfer method, etc. It is configured with settings. Therefore, there is no particular problem when creating a schedule with a certain rule at the date and time to be executed, but when a schedule with a certain rule at the date and time when it is not executed, the rule must be reversed and set. There was a problem. For example, in order to create a schedule such as “execute every day except the first day of every month”, it is necessary to set “execute on the second, third,... Therefore, the operation becomes complicated.

  Furthermore, when the rule of the date and time not to be executed fluctuates in relation to the calendar, there is a problem that the rule cannot be set. For example, in the case of “execute every day except weekends”, the normal weekend is Friday, but if it happens to be a holiday, the weekend will be Thursday and it will be difficult to convert to the day of execution.

  Further, in the job operation management system in which the execution schedule is determined only by the calendar information as in Patent Document 1, even if the closed days as the entire business are the same, the day when many jobs do not want to be executed for a specific job If there is, there is a problem that it is necessary to create a different calendar for the job, and if the schedule is changed, the calendar must be changed one by one.

  An object of the present invention is to provide an intuitive and easy-to-understand mechanism for registering a schedule that is difficult to implement only by a combination of execution dates and times.

  According to one aspect of the present invention, a calendar information acquisition unit that acquires calendar information including closed days for the entire business consisting of a plurality of jobs, particularly a plurality of jobs ranging from 10 to tens of thousands, and the calendar information A schedule information acquisition unit for acquiring schedule information including an execution scheduled date based on an execution schedule rule applicable to each job created without depending on the schedule and an execution exclusion scheduled date based on an execution exclusion schedule rule from the schedule database; After reflecting the non-working day information, the non-working day information reflecting unit reflecting the non-working day information based on the calendar information acquired by the calendar information acquiring unit respectively on the scheduled execution date and the non-execution scheduled date Execution schedule information that reflects the execution exclusion scheduled date on the scheduled execution date-execution exclusion schedule Job scheduling apparatus is provided, characterized in that it comprises a distribution reflecting portion. In addition to the scheduled execution rule, the job is executed in consideration of the scheduled execution exclusion rule that has the processing cycle as an item, so the days that will not be executed are registered without considering the days that are not executed based on the reversed rules. It is possible to execute the schedule calculation automatically by directly registering.

    In addition, the present invention provides a calendar information acquisition unit that acquires calendar information including closed days for the entire business including a large number of jobs ranging from a plurality of jobs, particularly 10 to tens of thousands, from the calendar database, and the calendar information acquisition unit. A non-working day list creation unit that creates a list of non-working days based on the acquired calendar information, and a scheduled execution date and execution exclusion based on an execution schedule rule that can be applied to each job created without depending on the calendar information A schedule information acquisition unit that acquires schedule information including an execution exclusion scheduled date based on a schedule rule from a schedule database; and a schedule execution date based on the execution schedule rule based on the schedule information acquired by the schedule information acquisition unit Execution schedule list creation section for creating a list of execution schedules , An execution exclusion schedule list creating unit that creates an execution exclusion schedule list in which execution exclusion scheduled dates are listed based on the execution exclusion schedule rule, and the closed days list in the execution schedule list and the execution exclusion schedule list, respectively. A non-working day list reflecting unit to reflect, and a non-execution schedule list reflecting unit for reflecting the non-execution schedule list in the execution schedule list after reflecting the non-working day list respectively. This is a featured job scheduling apparatus.

  The schedule information includes a closed day transfer rule for each of the execution schedule list and the execution excluded schedule list, and the closed day list reflection unit is configured to execute the closed execution day list and the execution schedule list based on the closed day transfer rule. It is recommended to re-edit the execution exclusion list. The execution schedule list and the execution exclusion schedule list are re-edited in consideration of the transfer rule for closed days, which is suitable for computer calculations.

  It is preferable that the execution schedule rule and the execution exclusion schedule rule are input from the input unit as schedule rules applicable to each job. Thereby, a suitable schedule rule can be set finely for each job.

  The present invention may be a job scheduling method in the job scheduling apparatus, a job scheduling program for causing a computer to execute the method, and a computer-readable recording medium for recording the program.

  According to the present invention, since calendar information and schedule information are separated and managed in the DB, it is not necessary to create another calendar to suppress job execution on days other than closed days, When changing the calendar information, the minimum necessary change is required.

  In addition, not only the execution schedule but also the execution exclusion schedule that has the same processing cycle as the execution schedule can be registered as a schedule in the schedule information. Instead of registering one by one, it is possible to automatically calculate the schedule by directly registering the days that are not executed.

It is a functional block diagram which shows the example of 1 structure of the job operation management system by one embodiment of this invention. It is a functional block diagram which shows the example of 1 structure of the job scheduling program (apparatus) by this Embodiment. It is a figure (c) which shows an example of a record of a schedule rule registration screen (a, b) by this embodiment, and a schedule database (DB) corresponding to it. It is a figure (b) which shows an example of a calendar registration screen (a) by this embodiment, and a record of a calendar database (DB) corresponding to it. It is a flowchart figure which shows the flow of a job scheduling process by this Embodiment. It is a figure which shows the process which reflects holiday information in the execution schedule list in the process of the job scheduling by this Embodiment. It is a figure which shows the process which reflects holiday information in the execution exclusion schedule list in the process of the job scheduling by this Embodiment. It is a figure which shows the process which reflects execution exclusion information in the execution schedule list in the process of the job scheduling by this Embodiment. It is a figure which shows the screen which displayed the execution schedule of 1 month (June is made into an example) of a job net.

  The present invention separates calendar information for determining the operating days and closed days for the entire business and schedule information for determining the execution schedule for each job, and further, in the schedule information, every day, every weekend, and on the second Wednesday of every month, similar to the execution schedule This is characterized in that an execution exclusion schedule having such a processing cycle as an item can be set. That is, the schedule information is separated information that does not depend on the calendar information.

  Hereinafter, a job scheduling apparatus and a job operation management system using the same according to an embodiment of the present invention will be described with reference to the drawings.

  FIG. 1 is a functional block diagram showing an outline of a job operation management system including a job scheduling apparatus according to the present embodiment.

  The job operation management system 100 according to the present embodiment includes a data storage device (program) 101, a job scheduling device (program) 102, a job execution device (program) 103, and a screen display device (program) 104. Is mounted in the ROM as a program that cooperates with the CPU of the computer, for example. Any one of these apparatuses 101 to 104 may be executed by a dedicated circuit.

  The job operation management system 100 is connected to, for example, each database of the schedule DB 111, the calendar DB 112, and the job definition DB 113, a display device (LCD display, etc.) 120, and an input device (mouse, keyboard, touch panel, etc.) 130 via a network. ing. These configurations can be basically realized by a personal computer (PC).

  Next, an outline of processing of the entire system will be briefly described. First, on the parameter input screen (GUI) displayed on the display device 120, the input device 130 is used to input job definition parameters relating to the job schedule, calendar, and job contents, and data is input to the DB via the GUI. The data storage programs 101 to be stored in the schedule DB 111, the calendar DB 112, and the job definition DB 113, respectively. Note that the data in the job definition DB 113 is general data relating to what kind of job is to be performed, and thus the description thereof is omitted here.

  The job scheduling program 102 acquires information from the schedule DB 111 and the calendar DB 112, and calculates the day on which the job is executed. The job scheduling program (apparatus) will be described later with reference to FIG.

  The job execution program 103 is a general known program that executes a job based on the schedule calculated by the job scheduling program 102.

  The screen display program 104 is a general known program that displays the schedule calculated by the job scheduling program 102 on the display device 120.

  FIG. 3 is a diagram showing an example of the schedule rule registration screen 200 and a schedule 210 record 210 corresponding to the schedule rule registration screen 200. The schedule rule registration screen 200 shown in FIGS. 3A and 3B includes a rule ID 201, a schedule type 202, a start date 203, a start date 204, a start time 205, a repeat designation 206, a repeat cycle 207, and a closed day transfer designation. The configuration includes 208 input items.

  The rule ID 201 is an ID that is uniquely set to specify the content of the schedule rule.

  The schedule type 202, which is a feature of the present embodiment, indicates the schedule type of the schedule rule. As the schedule type, “execution” and “execution exclusion” can be selected. When “execution” is selected as the schedule type, a screen for inputting a rule to be executed is displayed. When “execution exclusion” newly provided is selected, a screen for inputting a rule to be excluded from execution is displayed (FIG. 3B). If “Exclude Execution” is selected here, the start time 205, which is unnecessary information for the execution exclusion schedule, is grayed out and cannot be selected or edited, thereby eliminating unnecessary input.

  The start date 203 indicates the start date of application of the schedule rule. The schedule rule is applied with the date entered here as the start month.

  The start date 204 indicates the application rule start date. “Specify date” is displayed here, but “Specify month end” and “Specify day of the week” can also be selected from the pull-down menu, etc. If “Specify date” is selected, specify the date, If "" is selected, it is possible to specify the number of days before the last day. If "Select day of week" is selected, it is possible to specify the week, the last week, or the day of the week.

  The start time 205 indicates the time when the job is executed. If “Exclude Execution” is selected in the schedule type 202 and the rule is an execution exclusion schedule, the job is not executed and the start time information is unnecessary, so it is grayed out and cannot be selected or edited.

  The repeat designation 206 indicates whether to repeat the schedule rule in a specific processing cycle. By checking this check box, the repetition cycle 207 can be set. A repetition cycle 207 indicates a repetition condition of the schedule rule. The cycle can be specified in units of days, weeks, months, or years.

  The non-business day transfer designation 208 designates an operation method when the scheduled date is set as a non-business day in the calendar. In the non-business day transfer designation 208, the job is not executed without the non-business day transfer, “no execution”, the business day is transferred to the previous operation day, and the job is executed “transfer to the previous operation day”. The user can select “Transfer on a later operation day” to transfer the job to a later operation day and “Execute without transfer” to execute the job without transfer regardless of a closed day.

  FIG. 3C is a diagram illustrating an example of a schedule rule record 210 stored in the schedule DB 111. For example, in the record of schedule rule ID 201 = 1, the schedule type 202 is “execution”, the start date 203 is June 2010, the start date 204 is 5th, the start time 205 is 10:00, and repetitions 206 and 207 are repeated. However, the change 208 of the closed days is “not executed” every day. In the record with the schedule rule ID 201 = 2, the schedule type 202 is “Exclusion Excluded”, the start date 203 is June 2010, the start date 204 is 10 days, the start time 205 is blank, and the repetitions 206 and 207 are January. Every holiday 208 is “not executed”.

  These schedule rules are associated with the job net, and a plurality of rules to be executed and rules to be excluded can be registered.

  Such schedule rules are stored in the schedule DB 111 (FIG. 1) with the above input.

  FIG. 4 is a diagram showing an example of the calendar registration screen 300 (FIG. 4A) and the corresponding record 310 (FIG. 4B) of the calendar DB 112 (FIG. 1). On the calendar registration screen 300, operation days and closed days can be registered with designation 301 for each day of the week throughout the year and designation 302 for each individual date.

  If neither the designation 301 for each day of the week (Sunday in this case) nor the designation 302 for each individual date (in this case, June 5th or 19th) is specified, it is treated as a job operation day, and only one of them is not specified. In the case of specification, the other specification content is followed. If the specified contents differ between the two, detailed specification can be made by giving priority to the specification for each individual date.

  In the record 310 shown in FIG. 4B, the left side of the figure is day information, and the right side is date information. The information shown in FIG. 4B is stored in the calendar DB 112 shown in FIG. For example, on Saturday, June 5, 2010, the day of the week information is used, and the date information is closed. Also, as in ID = 2, if the day of the week information is closed on Saturday and Sunday, and the date information on June 5 and June 19 is not specified, June 5 and June 19 Will be closed respectively. Furthermore, as in the case of ID = 3, when all days of the week are operated in the day information and the date information on June 5 and June 19 is not specified, June 5 and June 19 are , Each will be operational. The calendar information is associated with the job net.

  Returning to FIG. 2, the job scheduling apparatus according to this embodiment will be described. The job scheduling apparatus 102 is generally realized by a job scheduling program. As shown in FIG. 1 and FIG. 2, the job scheduling program (device) 102 includes a calendar information acquisition unit 121 that acquires calendar information in the calendar DB 112, and a closed day from the calendar information acquired by the calendar information acquisition unit 121. And a closed day list creation unit 122 for creating a list.

  Furthermore, it has the schedule information acquisition part 123 which acquires the schedule rule in schedule DB111, and the schedule list preparation part 124 which produces a schedule list. The schedule list creation unit 124 includes an execution schedule list creation unit 125 and an execution exclusion schedule list creation unit 126.

  Furthermore, the execution schedule list creation unit 125 and the execution exclusion schedule list creation unit 126 are compared with the closed day list reflection unit 127 that reflects the closed day list created by the closed day list creation unit 122, and the execution schedule list. Includes an execution schedule list-execution exclusion schedule list reflection unit 128 that reflects the execution exclusion schedule list.

  FIG. 5 is a flowchart showing a flow of processing for determining a job net execution schedule. The description will be made with reference to other drawings.

  First, the calendar information acquisition unit 121 acquires calendar information associated with a job net from the calendar DB 112 (step S1). If the calendar information can be acquired (YES in step S2), the closed day list creation unit 122 creates and adds a closed day list from the acquired calendar information (step S3). When all the calendars associated with the job net have been acquired (NO in step S2), the schedule information acquisition unit 123 acquires the schedule rule associated with the job net from the schedule DB 111 (step S4). If the schedule rule can be acquired (YES in step S5, there is a record), the scheduled type of the acquired schedule rule is confirmed (step S6). Here, if the schedule type is “execution”, the execution schedule list creation unit 125 creates and adds an execution schedule list (step S7). If the schedule type is “execution exclusion”, the execution exclusion schedule list is created. The unit 126 creates / adds an execution exclusion schedule list (step S8). When all the schedule rules associated with the job net have been acquired (NO in step S5), the closed day list reflection unit 127 reflects the information on the closed day list in the execution schedule list (step S9). If there is an execution schedule on a closed day, the execution schedule is deleted from the list or the date is changed in accordance with the specified holiday transfer setting set in the execution schedule list. In other words, the execution schedule list is re-edited based on the designation of change of closed days. When the holiday schedule is reflected on the execution schedule list, the holiday day list reflection unit 127 reflects the information on the holiday list to the execution exclusion schedule list (step S10). If there is an execution exclusion schedule on a closed day, the execution exclusion schedule is deleted from the list or the date is changed in accordance with the closed day transfer designation set in the execution exclusion schedule list. In other words, the execution exclusion schedule list is re-edited based on the designation of change of closed days. When reflection of the closed days is finished, the execution schedule list-execution exclusion schedule list reflection unit 128 reflects the information of the execution exclusion schedule list to the execution schedule list (step S11). At this time, unlike the closed days, the execution schedule on the date included in the execution exclusion schedule is always deleted.

  Note that the closed day list creation process and the execution schedule list / execution schedule list creation process may be started for the first time. Processing may be performed in parallel.

  FIG. 6 is a diagram showing how the closed days list 610 is reflected in the execution schedule list 600. The closed days list 610 is created from the calendar information 310 shown in FIG. 4, and closed days 611 to 616 are listed. On the other hand, the execution schedule list 600 is created from the schedule rule information 210 shown in FIG. 3, and each day is assigned to “execute”, “do not execute”, “transfer to the previous operation day”, “Transfer to a later operation date” is specified. In FIG. 6, some dates are omitted.

  Of the holiday days 611 to 616 listed in the holiday day list 610, the reflection of the holiday day 611 to the execution schedule of 2010/06/05 is “not executed” because the transfer of the holiday days is “not executed”. Remove from the list. Reflecting a closed day 612 in the execution schedule of 2010/06/06, the change of the closed day is “transfer to the previous open day”, so the previous open day is searched. In this case, 2010/06/05 is a closed day, and 2010/06/04 is the nearest operation day before 2010/06/06. Therefore, the transfer date is 2010/06/04 10:00, and since there is no execution schedule at this date, it is added to the execution schedule as the transfer schedule. Reflecting the closed days in the scheduled execution date of 2010/06/13, since the transfer of closed days is "execute" in 613, the execution schedule is not changed as it is. Reflecting the closed days 614 in the scheduled execution date of 2010/06/19 is that the change of closed days is “transfer to a later operation day”, so the later operation day is searched. In this case, since 2010/06/20 is a closed day, 2010/06/21 is the nearest operation date after 2010/06/19. Therefore, the transfer date is 2010/06/21 10:00, but since there is an execution schedule for this date, the execution schedule for the transfer is deleted. In the reflection 615 of 2010/06/20, the execution schedule is not changed as it is because the transfer of the holiday is “execute”. The reflected holiday 616 to the execution schedule of 2010/06/27 is deleted from the execution schedule list because the change of the closed day is “not executed”. In this way, the list is re-edited according to the transfer rule.

  FIG. 7 is a diagram illustrating a state in which a closed day list 710 (same as the closed day list 610) is reflected in the execution exclusion schedule list 700. The execution exclusion schedule list 700 is based on an execution exclusion schedule rule that excludes execution on the 10th, 20th, and 30th of each month (see FIG. 3B). Since there is no corresponding execution exclusion schedule on 2010/06/05, 06, 13, 19, and 27 (711, 712, 713, 714, 716) among the closed days, the execution exclusion schedule list is not changed. Since the holiday 715 of 2010/06/20 is scheduled to be excluded from execution, the change of the holiday is “not executed” and is deleted from the execution exclusion list. If the holiday 715 on 2010/06/20 is scheduled to be excluded from execution, and the transfer of the holiday is “execute”, 2010/06/20 is also included in the execution exclusion schedule. In addition, if the holiday 715 on 2010/06/20 is scheduled to be excluded, and the transfer of the holiday is “Transfer before”, it will be excluded because 2010/06/19 is a holiday. The day is 2010/06/18. If the holiday 715 of 2010/06/20 is scheduled to be excluded from execution, and the transfer of the holiday is “transfer later”, the execution exclusion scheduled date is 2010/06/21.

  FIG. 8 is a diagram showing a state in which an execution exclusion schedule list 810 (which reflects 710 in 700 of FIG. 7) is reflected in the execution schedule list 800. In FIG. 8, some dates are omitted. Since the execution exclusion schedules 811 and 812 of 2010/06/10 and 2010/06/30 are scheduled to be executed, they are deleted from the execution schedule list. In addition, in FIG. 7, when the holiday 715 of 2010/06/20 is scheduled to be excluded from execution and the transfer of the holiday is “execute”, 2010/06/20 is also included in the execution exclusion schedule. Therefore, this day will be deleted from the execution schedule. In this way, the execution exclusion schedule list 810 is created and reflected in the execution schedule list. Generally, since there are few scheduled execution exclusion dates, it is converted and reflected as in the past. There are many cases where the processing becomes easier than in the case.

  FIG. 9 shows a job net execution schedule display screen 900 for one month. Here, job nets 1 to 3 are illustrated, but actually, a large number of job nets are scheduled.

  “Jobnet 1” has no closed days (the calendar is ID = 3 in FIG. 4B), the execution schedule is “execute daily from 06/06/2010” (execution schedule list 600), and there is no execution exclusion schedule. This is an example where a case is applied, which will be executed every day from 2010/06/05.

  “Jobnet 2” has a holiday of “every Sunday and 2010/06/05, 2010/06/19” (calendar is ID = 1 in FIG. 4B), and the execution schedule is “2010/06/05 This is an example in which there is no execution exclusion schedule in the “execute every day” (execution schedule list 600), and only 2010/06/05, 6, 19, and 27 are closed days.

  “Jobnet 3” has a holiday of “every Sunday and 2010/06/05, 2010/06/19” (calendar is ID = 1 in FIG. 4B), and the execution schedule is “from June 05, 2010” This is an example in which the execution exclusion schedule is “execution schedule list 600” and the execution exclusion schedule is “10th, 20th, 30th of every month” (execution exclusion schedule list 700). By applying the execution exclusion schedule, Compared with “Jobnet 2”, 2010/06/10, 30 is the execution exclusion date.

  As described above, by performing the processing shown in FIG. 5, it is possible to perform scheduling of job nets that take execution exclusion into consideration with a simple operation.

  As described above, according to the present embodiment, since the calendar information and the schedule information are separated, it is not necessary to create another calendar in order to suppress the execution of the job on a day other than a closed day. And the calendar information can be changed with minimal changes.

  In addition, not only the execution schedule but also the execution exclusion schedule that has the same processing cycle as the item can be registered as a schedule in the schedule information, so if the schedule has a day that does not execute according to a certain rule, it will be reversed one by one There is an advantage that the schedule calculation can be automatically executed by directly registering the day that is not executed without registering it in consideration of the rule. In particular, this is an extremely effective means when a large number of jobs are executed at the same time.

  The present invention can be used as a job scheduling apparatus.

DESCRIPTION OF SYMBOLS 100 Job operation management system 101 Data storage program 102 Job scheduling program 103 Job execution program 104 Screen display program 111 Schedule DB
112 Calendar DB
113 Job definition DB
DESCRIPTION OF SYMBOLS 120 Display apparatus 121 Calendar information acquisition part 122 Holiday day list creation part 123 Schedule information acquisition part 124 Schedule list creation part 125 Execution schedule list creation part 126 Execution exclusion schedule list creation part 127 Holiday day list reflection part 128 Execution schedule list-execution exclusion Schedule list reflection unit 130 Input device 200 Schedule rule registration screen 201 Rule ID
202 Schedule type 203 Start date 204 Start date 205 Start time 206 Repetition specification 207 Repetition cycle 208 Closed day transfer specification 210 Schedule DB record 300 Calendar registration screen 301 Open days / close days for each day of the week 302 Open days / Non-working day designation 310 Calendar DB record 600 Execution schedule list 610 Closed day list 700 Execution exclusion schedule list 710 Closed day list 800 Execution schedule list 810 Execution exclusion schedule list 900 Job net execution schedule display screen for one month

Claims (5)

A calendar information acquisition unit that acquires calendar information including closed days for the entire business composed of multiple jobs from a calendar database;
A closed day list creating unit for creating a closed day list in which only closed days are listed based on the calendar information acquired by the calendar information acquiring unit;
A schedule information acquisition unit that acquires schedule information including an execution scheduled date based on an execution schedule rule applicable to each job created without depending on the calendar information and an execution exclusion scheduled date based on an execution exclusion schedule rule from a schedule database When,
Based on the schedule information acquired by the schedule information acquisition unit , “execute”, “do not execute”, “transfer to previous operation day”, and “transfer to subsequent operation day” are designated for each day. scheduled execution list creation unit that creates the scheduled execution list that lists the scheduled execution date has been and, the execution excluded plans "do not run" a closed transfer for each day on the basis of the rule execution excluded scheduled date that is specified An execution exclusion schedule list creation section for creating an execution exclusion schedule list in which is listed,
A non-working day list reflecting unit for reflecting non-working days listed in the non-working day list in the non-execution schedule list and the non-execution schedule list,
An execution schedule list that reflects the execution exclusion scheduled date listed in the execution exclusion schedule list in the execution schedule list after reflecting the closed days list;
The schedule information includes a closed day transfer rule for each of the execution schedule list and the execution exclusion schedule list,
The job schedule list reflection unit re-edits the execution schedule list and the execution exclusion schedule list based on the closed day transfer rule. The re-editing is
If there is an execution schedule on a closed day, the execution schedule list is transferred to a closed day by deleting the execution schedule from the list or changing the date in accordance with the closed day transfer specification set in the execution schedule list. Re-edit as specified,
If there is an execution exclusion schedule on a closed day, the execution exclusion schedule is deleted from the execution exclusion schedule list or the date is changed in accordance with the closed day transfer specification set in the execution exclusion schedule list. Re-edit the to-be-excluded list based on the transfer specification for holidays,
2. The job scheduling apparatus according to claim 1, wherein when the closed days are reflected, the execution schedule list-execution exclusion schedule list reflection unit reflects the information of the execution exclusion schedule list in the execution schedule list.   The job scheduling apparatus according to claim 2, wherein an execution schedule on a date included in the execution exclusion schedule list is always deleted.   The job scheduling apparatus according to claim 1, wherein the execution schedule rule and the execution exclusion schedule rule are input from an input unit as schedule rules applicable to each job. A calendar information acquisition procedure for acquiring calendar information including a non-working day for the entire business composed of multiple jobs from the calendar database;
A closed day list creating procedure for creating a closed day list in which only closed days are listed based on the calendar information acquired by the calendar information acquiring procedure;
Schedule information acquisition procedure for acquiring schedule information including a scheduled execution date based on an execution schedule rule applicable to each job created without depending on the calendar information and an execution exclusion scheduled date based on an execution exclusion schedule rule from the schedule database When,
Based on the schedule information acquired in the schedule information acquisition procedure , “execute”, “do not execute”, “transfer to previous operation day”, and “transfer to subsequent operation day” are designated for each day. Execution schedule list creation procedure that creates an execution schedule list that lists the scheduled execution dates that have been executed, and scheduled execution exclusion dates that are specified as “do not execute” for each day based on the execution exclusion schedule rule To create an execution exclusion list that creates an execution exclusion list that is listed,
A reflected holiday list reflecting procedure for reflecting the closed days listed in the closed days list in the scheduled execution list and the scheduled exclusion list;
Execution schedule list for reflecting the execution exclusion scheduled date listed in the execution exclusion schedule list in the execution schedule list after reflecting the closed days list-execution exclusion schedule list reflection procedure;
A job scheduling program for causing a computer to execute
The schedule information includes a closed day transfer rule for each of the execution schedule list and the execution exclusion schedule list, and the closed day list reflection procedure is based on the closed day transfer rule. A job scheduling program characterized by re-editing an execution exclusion schedule list.

Images