JP2000112887A - Method for scheduling batch job - Google Patents

Abstract

PROBLEM TO BE SOLVED: To prevent the start of succeeding system service from being delayed by ending a batch processing service even when the batch processing service is delayed and does not end within a scheduled time and carrying over uncompleted batch jobs to succeeding batch processing service. SOLUTION: The management of batch jobs and that of data information to be used for the scheduling of batch jobs can be executed for every group unit and batch job scheduling using each different date can be executed for every group unit by batch job scheduling processing 204. Consequently, uncompleted batch jobs made to remain in preceding system service can be carried over to succeeding system service.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[0001] 1. Field of the Invention [0002] The present invention relates to a method of scheduling a batch job in a computer system which requires processing of a large number of batch jobs as a method of using a computer.

[0002]

2. Description of the Related Art A schedule based on a scheduled processing date of a batch job has been provided in a computer system based on common date information, and only one computer system provides services on the same date.

[0003]

According to the conventional scheduling method based on the scheduled processing date of a batch job, a batch job registered centrally is scheduled based on the same date information in one computer system. .
For this reason, in the batch job processing service, even if a scheduled batch job cannot be completed within the scheduled processing time due to a processing delay, a failure, or the like, the batch job processing service time is extended. However, if all scheduled batch jobs are not completed normally, the next service batch job cannot be scheduled, which may affect the start of the next system service.

[0004] In view of the above, it is an object of the present invention to stop a system at a predetermined system service end time even if a batch job processing service is delayed, and to execute a batch job that cannot be executed in time. By providing a batch job scheduling method that enables execution on the business day that should be executed at the time of the next system service, it is possible to avoid the occurrence of total delay of system service start due to batch job processing service delay, An object of the present invention is to provide a batch job scheduling method that suppresses the influence of a specific business process at the block level.

[0005]

According to the present invention, a batch job that cannot be executed at the end of a system service is carried over at the next system service, and is carried out in the next system service in parallel with the batch job processing service to be provided. By enabling the execution of a batch job carried over from the previous system service, a batch job processing service delay avoids a front-end delay in starting the next system service.

In the method of the present invention, when executing a batch job carried over from the previous system service, a batch job processing service on a date that should be executed is enabled, and all batch jobs that have not been executed previously are completed. At that point, the batch job processing service on the date of the day is enabled again. In order to localize the effects of carried over batch jobs, batch jobs should be
Provided is a batch job scheduling method for enabling division in a group unit according to an application and enabling carryover of a batch job in the group unit.

[0007] In order to enable group-based schedules, all registered batch jobs and batch job groups are managed as record information storing information necessary for the schedule, using the respective names as keys. In the schedule of the present invention, a batch job is scheduled based on a predetermined scheduled processing date, and date information used for the schedule can be registered as a calendar information table unique to the system.

In the batch job scheduling method of the present invention, batch jobs are processed on different dates for each group within the same business day within the same system. For this reason, the present invention provides a method for preventing unauthorized reference and update of a database, and a logical assignment method of a batch job and a database used in processing by the batch job. Further, in the system using the batch job scheduling method of the present invention, since the used date uses uniquely defined calendar information, a method of handing over the processing date to the batch processing program is provided.

[0009]

Embodiments of the present invention will be described below in detail with reference to the drawings.

FIG. 1 shows a system configuration diagram of a system to which the present invention is applied. As shown in FIG. 1, the present invention provides a large amount of batch processing services by a host computer 102 installed in a computer center 101. A batch schedule function 103 to which the batch schedule method of the present invention is applied includes an operating system. System 104, database management system 105
It is mounted on the top and realizes input / output to / from the schedule information 107 and a request to start the batch job 103 using each basic function.

In the scheduling method of the present invention, it is assumed that schedule information necessary for a batch job schedule is defined in advance by a user and registered as schedule information 107. The schedule information 107 includes batch job information and a batch job information table for managing the status, batch job group information and a group information table for managing the status, a schedule information table for managing the status of the entire batch job schedule, It is also assumed that a calendar information table for managing date information used in the batch job schedule of the present invention is registered. Also,
For the job control statement for starting a batch job for starting a batch job, the user creates one job control statement for each batch job with respect to the batch job registered in the schedule information 107 in advance, and stores it in the startup JCL information 109. You need to register. Regarding the registration of the job control statement, it is necessary to register the corresponding batch job name in the startup JCL information 109 as the member name of the job control statement.

FIG. 2 is a block diagram showing a system service of a batch processing system to which the present invention is applied in units of processing. In the present invention, from the start of the system service start process 201 to the system service end process 206
Is managed as one day. For this reason, even when a day shift occurs after 24:00 during the system service, the batch processing system to which the present invention is applied does not change on a daily basis because of the system service. The date is updated when the system service start processing 201 is started. In the present invention, in the batch processing service, when a situation occurs in which all batch jobs scheduled for the batch service 205 for the current day are not completed within the scheduled time, the system service from the previous business day system service is performed at the next business day system service. As a carryover, it is possible to provide a service on the previous business day as the batch service 203 for the previous day.

According to the present invention, batch job scheduling processes 202 and 204 for providing the batch service 203 of the previous day and the batch service 205 of the current day in parallel are provided. All of these schedules are performed based on information managed in the schedule information file 107.

Next, details of schedule information required for realizing the scheduling method of the present invention will be described. In the present invention, the date on which the system service is provided is updated at the start of the scheduling function 104 adapted to the scheduling method of the present invention, separately from the system date, so that calendar information unique to the system is required.
FIG. 3 shows a calendar unique to the system for providing a batch processing service for implementing the present invention. Regarding the date used in the system service, the date when the user provides the system service (business day) and the day when the system service is suspended (non-business day) are designated as the calendar information state 303 in advance, and the first time after the calendar is created. It is assumed that a calendar start date can be specified when the system service is provided, and thereafter the system service is provided based on the calendar information table, and the date 301 used at the time of starting the system service is updated. This schedule function has means for acquiring a date from the calendar information table.

FIG. 4 shows a batch job information table for managing batch job definition information and status information necessary for realizing the present invention. FIG.
As shown in (1), a batch job scheduled by the scheduling method of the present invention needs to be registered in this table in advance. This table stores the job name 40
It is assumed that one record information is stored for one batch job using 1 as key information. The management items of each batch job include a group name 402 as a unit for executing the schedule for the batch job, a state 403 for managing whether the batch job is to be activated at the time of the system service that executed the schedule, and a status 403 of the batch job. A start date 404 that specifies a scheduled execution date, a start condition 405 that specifies a trigger for starting the batch job, a start condition satisfied state 406 that manages a state of satisfaction of the start condition, and a suppressed state that manages a suppressed state of starting the batch job. 40
7. Execution result 40 for managing the execution status of the batch job
8 and a program name 409 that defines a business processing program used when the batch job is executed.

In these management items, a job name 401,
Group name 402, start date 404, and start condition 4
05 needs to be registered in advance by the user. In the state 403, the initial value is excluded from the schedule, and if the business day is a scheduled start date according to the batch job schedule, it is updated as a schedule target. When a request to satisfy the condition is issued for the condition specified as the activation condition, the condition is updated to the satisfied condition,
In the inhibited state 407, the batch job is started with the initial value set to the uninhibited state, and the processing result is updated to the inhibited state when the processing result is abnormally terminated and the inhibition is specified.
The initial value is set to the unexecuted state, and depending on the execution state of the batch job, it changes to the unexecuted state, carryover not executed state, execution wait state, carryover execution wait state, execution requesting state, executing state, normal end state, abnormal end state Shall be updated.

When assigning the job name 401, the business database 108 used for each batch job is used.
Is logically divided into groups, a business database logical group name of one digit alphanumeric is given to the divided logical group, and this business database logical group name is assigned to the second digit from the top of the job name 401 of the batch job. Let it correspond to one character.

FIG. 5 shows a group information table for managing batch job group information which is a batch job schedule unit. Regarding group information, this table uses the group name 501 as key information.
It is assumed that information of one record is stored for one group. The management items of each group include a group name 501 indicating a schedule unit of a batch job, a state 502 for managing whether or not the state of the group is a carryover schedule when performing the schedule of the group, and a state 502 for managing a carryover schedule. In the case of, the number of carry-over days 503 for managing how many business days before the batch job to be started is to be started, and a number for specifying the maximum number of batch jobs that can be started in the same group There are severe 504.

Among the management items, group name 501,
The user needs to register the multiplicity 504 in advance. In the state 502, it is assumed that the initial value is a non-carryover state, and the batch state is updated to a carryover state when a batch job to be carried over exists in the group according to the batch job schedule.

FIG. 6 shows a schedule information table for managing the state of the schedule function employing the scheduling method of the present invention. In the schedule information table, as a necessary item for scheduling a batch job, a schedule state 601 for managing whether or not a carryover schedule is performed, and whether a group requiring a carryover schedule exists among registered groups Whether to carry over or not 602, if a carryover group exists, the number of carryover days for that group is 5
Carryover days 603 to manage the maximum value of 03, current business day date 6 to manage the date information to provide the system service
04 and last business day date 605 that manages the previous business day date information used for the carryover schedule.
For the previous business day date 605, it is assumed that date information up to the number of days before the number set in the carry over days 603 is set.

The above-described calendar information table, batch job information table, group information table, and schedule information table can be used by the batch job scheduling function having the batch scheduling method of the present invention based on the information registered by the user. It is assumed that the apparatus has a method of converting the information into a format, and means for enabling reference and updating of the table information.

FIG. 7 is a functional block diagram showing the batch scheduling method of the present invention. As shown in FIG. 7, the present invention provides a batch job scheduler function 701 for managing a batch job schedule and the execution of a batch job, and a batch schedule method of the present invention.
This is realized by a batch schedule function providing API function 711 provided for a batch processing program to be scheduled.

The batch job scheduler function 701 includes:
A batch schedule control function 702 for controlling the functions constituting the batch scheduler function 701, a batch schedule start function 703 for checking the status of the schedule information when the batch scheduler function 701 starts, and a batch job for scheduling the batch job registered in the schedule information The schedule function 704, the schedule function 704 is the state 502 of the group to be scheduled.
, A batch job is scheduled using the business day date of the day, and a carryover schedule function 706 that schedules the batch job as carryover processing before the previous day, and the execution status of the scheduled batch job Job execution status management function 707 that manages a batch job, and batch job activation control function 7 that requests a scheduled batch job to be activated
08, a batch job end control function 709 that reflects the end result of the batch job started by the batch job start control function 708 in the schedule information, and the batch job start condition 40 registered in the schedule information
The batch schedule control function 702 comprises a trajectory condition setting control function 710 for setting the start condition satisfaction state 406 of FIG. 5, and requests processing of each function and processing control such as termination of each function. The batch schedule control function 702 and each function have a function of communicating a processing request between the functions.

An API for providing a batch schedule function
The function 711 is provided directly to a business processing program of a batch job scheduled by the batch scheduler function 701, and the user uses the batch schedule function providing API function 711 in accordance with the usage standard when creating the business processing program. Need to use.

API function 7 for providing a batch schedule function
11, a batch process start AP that notifies the batch scheduler function 701 of the start of the batch job requested to be started by the batch scheduler function 701.
I function 712, an API function 714 for acquiring a start JCL / SYSIN information for the business processing program to acquire input information from the start job control language of the batch job;
The DB information check API function 714 that returns the information of the business database scheduled to be updated by the batch job scheduled as the carryover processing to the business processing program, and the processing of the batch job started by the batch job scheduler function 701 ends. A function of a batch processing end API function 715 for notifying the batch job scheduler function of the completion is provided.

The batch job scheduler function 701 having the batch job scheduling method of the present invention is started when a system service is started, and the batch job scheduler control function 702 requests the batch schedule start function 703 to perform processing. A start process 201 is performed.

In the batch schedule start function 703,
Based on the schedule information at the start of the batch job scheduler function 701, it is determined whether the state 502 of the group is required to be carried over based on the state of the batch job belonging to each group. 8, a batch schedule start process 70 will be described.
3 is shown in detail. The group information table is obtained from the schedule information, and the first record information is read into the group information record (step 801). Next, the first record of the job information record is read from the job information table (step 802). Name 501 and group name 4 of job information record
02 is compared (step 803), and a batch job existing in the target group is searched.

If the batch job of the record is a batch job in the target group, the execution status of the batch job is checked. If the batch job of the record is not a batch job in the target group, the next job information record is read (step 807).

To check the execution status of the batch job, it is checked whether the status 403 of the batch job is a schedule target status (step 804). Since the batch job was scheduled to be executed at the time, the execution result 408 is checked.

In other cases, since the batch job was not scheduled to be executed at the time of the system service on the previous business day, the batch job is excluded from processing and the next job information record is read (step 807). It is checked whether the execution result 408 is in a normal end state (step 804).
If the batch job is in the normal end state, it is determined that the batch job has been completed normally at the end of the previous business day system service, and the next job information record is read (step 807). If the batch job is not in the normal end state, the batch job is determined to be a carryover target batch job, and the state 502 of the group to which the batch job belongs is updated to the carryover state (step 806).

When a batch job to be carried over is detected, the job information table is closed (step 80).
9) Then, the next group information record is read (step 810), the job information record is obtained again from the top of the job information table (step 802), and the above processing is repeated to obtain all the group information registered in the group information table. Do it for records. At the point in time when the processing has been completed for all the groups registered in the group information table, if the state 502 of the group information record has been updated to the carryover state, the schedule state 602 in the schedule information table is changed to the carryover processing state. 603 is updated to the state in which carryover is present. As described above, the batch schedule start function 703 ends, and the scheduling method is determined for all the groups registered in the schedule information.

After the end of the batch schedule start function 703, the batch job schedule control function 702 starts the batch job schedule function 704, and the batch job schedule processing 202 starts. The batch job schedule function 704 schedules whether a batch job registered based on the schedule information is to be executed during the current business day business service.

The details of the batch job schedule function 704 will be described with reference to FIG. The schedule information table is read from the schedule information (step 901), and the schedule state 601 is checked (step 90).
2). If the schedule state 601 indicates that the carryover is present, the center operator is inquired as to whether or not to activate the carryover batch job (step 903). In response to this inquiry, the center operator responds as to whether or not to start the carryover batch job in the previous business day system service in the system service of the day.

Next, the first record of the group information record is read from the group information table (step 90).
4) Check the state 502 of the group (step 905). If the state 502 is other than the carryover state, the schedule for the group is the normal schedule processing (step 908). If the state is the carryover state, the response result of the center operator inquiry is determined (step 9).
06) If the response result indicates that the carry-over batch job needs to be started, the schedule of the group is set to carry-over schedule processing (step 907); otherwise, the normal schedule processing (step 908) is performed.

When the processing for one group is completed, the next group information record is read (step 90).
9) The above processing is performed again, and processing is performed for all registered groups until EOF is detected (step 910). Next, details of the normal schedule processing (step 908) are shown in FIG.

In the normal schedule processing, the first record of the job information record is read from the job information table (step 1001), and the group name 402 of the job information record is compared with the group name of the group performing the schedule processing (step 1002). Then, the process is performed on the batch jobs existing in the group. If the batch job of the read job information record is a batch job in the group, the state 403, the activation condition satisfied state 406, the suppression state 407, and the execution result 408 are updated to the initial state.

Next, the current business day date 604 is obtained from the schedule information table (step 1003), and is compared with the start date 404 of the job information record (step 1004). Only when they match, the state 403 is updated to the start target state. (Step 1005). At this point, if all the start condition satisfied states 406 of the batch job are satisfied, the execution result 408 is updated to an execution waiting state. Next, the next job information record is read (step 1006), the above-mentioned schedule processing is performed again, and this is repeated until the EOF is detected by reading the job information record (step 1007), thereby executing the batch job schedule.

Next, carryover schedule processing (step 9)
07) is shown in FIG. The carryover schedule process reads the first record of the job information record from the job information table 1101, compares the group name 402 of the job information record with the group name of the group that is executing the schedule process (step 1102), and This is done for batch jobs that do.
Determine the status 403 of the batch job (step 1103)
Then, in the case of the activation target state, the execution result 408 is determined (step 1104). If the state 403 is a start target state and the execution result 408 is other than a normal end state, the execution result 408 is updated to a carryover non-start state as a batch job to be carried over from the previous business day system service (step 1106).

At this point, if all the start condition satisfied states 406 of the batch job are satisfied, the state is updated to the carryover execution wait state. The next job information record is read (step 1106), and the above-described schedule processing is performed again.
The carryover schedule is executed by repeatedly performing the OF until the detection (step 1107).

As described above, when the schedule processing is performed on all the batch job groups registered as the schedule information, the batch job scheduling function 7
04 ends.

At this point, the batch job processing service is started. The batch job schedule function 702 is
By issuing the batch processing start API function 712 from the batch processing program, the batch job execution status management function 7
07, the batch job end control function 70 is issued by issuing the batch process end API function 715.
9 and the termination of the batch job termination control function 709, the activation condition setting control function 71
0, means for sequentially requesting the batch job activation control function 708 for processing.

The batch job schedule control function 702 has means for requesting the batch job activation control function 708 to perform processing at regular time intervals. The batch job schedule function 702 continues the processing until the processing of all the scheduled batch jobs is completed by the above-described means, or the end request of the system service is made by the center operator.

The batch job scheduled by the batch schedule method of the present invention is started by the batch job start control function 708, and details of the batch job start method are shown in FIG. The start request of the batch job is realized by searching for a startable batch job from the job information table of the schedule information and writing the job control language for starting the batch job in the internal reader file. First, the head of the job information record is read from the job information table (step 12).
01). At this time, it is determined whether or not there is a vacancy in the multiplicity of the batch job starting initiator of the operating system (106) that operates the batch job (step 1).
202) If there is no free space, the batch job activation control function 708 ends. If there is a vacancy in the initiator, the determination processing of the read job information record is continued.

The status 403 of the job information record is determined (step 1203), and it is determined whether the batch job is scheduled to be started. If it is scheduled to be activated, the group information record of the group information table corresponding to the group name 402 to which the batch job belongs is acquired, and it is determined that there is a vacancy in the multiplicity for determining the multiplicity 504 of the group. Confirm (step 1204).

Next, the execution result 408 of the batch job is judged, and if it is in the execution waiting state or the carryover execution waiting state, the inhibition state 407 is judged.
Request the start of the batch job. If the batch job status 403 is other than the start target status, the execution result 408 is other than the execution wait status or the carryover execution wait status, and there is no room in the multiplicity 504 of the belonging group, the next job information record is read (step 1208). ), And repeat the same processing.

For the batch job requested to be started,
A corresponding job control statement is acquired from the startup JCL information 109 based on the batch job name, and information to be passed to the business processing program is set for the acquired job control statement (step 1206). The takeover information includes the logical group name of the business database used by the batch job and the schedule status 6 in the schedule information table.
01, information for determining whether the batch job is scheduled according to the normal schedule or the carryover schedule, business day date information 604 of the day, and the batch job scheduled to be carried over Date information 60 of the day
5 is set.

Next, the created job control statement is written in the internal reader file, so that the operating system 1
A request for starting a batch job is made to the application 06, and the execution result 408 of the batch job is updated to an execution requesting state (step 1207). When the processing for one batch job is completed, the next job information record is read (step 1208), the batch job start request processing is performed again, and this processing is performed until the last record of the registered job information record (step 1209) or The processing of the batch job activation control function 708 is performed until the multiplicity of the initiator becomes full (step 1202).

The batch job execution status management function 707 includes:
The batch job activation control function 708 activates the activated batch job when the batch processing start API function 712 is issued. The batch processing start API function 712 notifies the batch job schedule control function 702 of the batch job name. Batch job execution status management function 7
07, the execution result 40 of the corresponding job information record in the job information table is based on the notified batch job name.
8 is updated to the running state.

The batch job end control function 709 is operated by the batch job schedule control function 702 when the batch job started by the batch job start control function 708 issues the batch processing end API function 715. The batch processing end API function 715 notifies the batch job schedule control function 702 of the batch job name and the end state of the batch job. The end status of the batch job is reported in three statuses: normal end, abnormal end, and DB group closed.

The batch job end control function 709 updates the execution result 408 of the corresponding job information record in the job information table based on the notified batch job name. The update contents are a normal end state when the batch job end status from the batch process end API function 715 is a normal end, an abnormal end state when the batch end is abnormal, and an execution wait state when the DB group is closed. If the end status of the batch job is DB group closed, the suppression status 407 is updated to the suppression status.

Here, when the end status of the batch job is notified of normal end, the group name 402 is obtained from the job information record of the batch job, and the group name is obtained from the group information record of the group information table based on the group name. A record in which the group name 501 matches is acquired. If the state 502 of the group information record is a carryover state, a state confirmation process is performed to determine whether all the batch jobs belonging to the group and subjected to the carryover schedule process have been completed normally.

In the state confirmation method, a job information table is obtained, and a job information record is obtained. In the record where the group name 402 of the acquired job information record matches, it is confirmed whether or not the execution result 408 of the batch job whose status 403 is set as the schedule target is a normal end status. In this status confirmation processing, when the execution result 408 of the batch job whose status 403 is the scheduling target of all the batch jobs in the group becomes a normal end status, all the batch jobs that have been carried over to the group have been completed. The batch job end control function 709 requests the batch job schedule control function 702 to execute the normal schedule function 705 for the group, and the batch job schedule processing 204 is performed.

At this point, the batch job end control function 702 updates the inhibited state of the batch job whose inhibited state 407 is inhibited to the state without inhibition for all records in the job information table. The batch job updated without the inhibition state is requested to be started when the next batch job start control function 708 is executed.

As described above, for all the groups whose group status 502 is the target of the carryover schedule, when the processing of the batch job to be carried over in the group ends normally, the normal schedule When the function 705 is performed and all the groups to be carried over are normally scheduled by the normal schedule function 705, the schedule state 601 of the schedule information table is changed to the state without the carry over schedule.
The carry-over status 602 is updated to a state of no carry-over, and at this time, the system service is entirely the batch service 205 for the current day.

In the batch scheduling method of the present invention, the execution state of the scheduled batch job is realized by the batch processing start API function 712 and the batch processing end API function 715 from the business processing program. Since batch jobs can be processed on different dates, there is a possibility that the business database 108 may be illegally referenced or updated. In order to prevent this event, the startup provided by the batch scheduling method of the present invention will be described. API for acquiring JCL / SYSIN information
Function 713 and API function 714 for checking DB information
You need to use In creating a business processing program, it is necessary to create a program by using each business processing program interface function provided by the batch schedule function providing API function 711 according to a standard.

FIG. 13 shows how to use the API function 711 for providing a batch schedule function when creating a business processing program in order to implement the batch schedule method according to the present invention. As shown in FIG. 13, a batch business processing program scheduled by the batch scheduling method of the present invention issues a batch processing start API function 712 at the start of the program (step 1301). The batch processing start API function 712 notifies the batch job schedule control function 702 that the batch business processing program has been started as a batch job started by the batch schedule function of the present invention.

Next, A for starting JCL / SYSIN information acquisition
The PI function 713 is issued, and the input information set by the batch job start control function 708 in the job control statement for the batch job function that starts the batch job processing program is taken over by the batch job processing program (step 13).
02).

The input information includes the logical group name of the business database used by the batch job, the schedule status 601 of the schedule information table, whether the batch job has been scheduled by the batch job start control function 708, and whether the batch job has been carried over. Information to determine if the schedule was set by
The business day date information 604 of the current day and the business day date information 605 that should be started are set for the batch job scheduled to be carried over.

In the batch business processing program, it is assumed that the processing is performed based on the date of the input information. Next, in the business process, the business database 108
It is determined whether reference or update is performed (step 130).
3) When referencing or updating, start JCL · S
From the information acquired by the YSIN information acquisition API function 713, it is determined whether the schedule status is a carryover schedule and the carryover status of the batch job (step 1304).

If the carry-over schedule is being performed and the schedule status of the batch job is being processed on the same day, the database is set to prevent unauthorized access to the business data database 108 that has not been updated.
An information check API function 714 is issued to acquire information on the business database logical group name used by the batch job being carried over (step 13).
05). Based on the acquired business database logical group name information, a determination is made as to whether the business database logical group name approaching the batch job is a database to be used by a batch job to be carried over and processed (step 1306). If the batch job is not used by the batch job to be processed and can be used as processing on the day, it is necessary to create a batch business processing program so as to perform business processing (step 1307).

The batch business processing program issues a batch processing end API function 715 (step 130).
8). Batch end API function 71
5 needs to set an end status to notify the batch job schedule control function 702 of the end status of the batch job. The end status includes a normal end when the business process ends normally, In the case where an abnormality is encountered during the business process, the process is terminated abnormally, and in the determination of the state of the database to be used (step 1306), if the business database logical group is used in the carryover process, the DB group is closed. I do.

FIG. 14 shows a method of confirming the use state by a batch job that is carried over to the business database logical group. The job database (108) is logically divided into groups as shown in FIG. 15 according to the processing contents of the batch job when the job name 401 is assigned when registering the batch job. It is assumed that the group name of the divided business database group 1502 is specified as the first character of the second byte of the job name 401. As shown in FIG.
The information check API function 714 acquires a group information record from the group information table (step 1).
401), the state 502 is determined, and a group in the carryover state is searched (step 1402). For the group in the carryover state, a job information record is obtained from the job information table (step 1403), and whether the group is a batch job of the carryover group The group name 402 is determined, and a batch job in the carryover group is searched (step 14).
04).

If not detected, the next job information record is read 1408. If detected, it is determined whether the status 403 of the batch job is to be started (step 1405). , Execution result 4
08 is in a normal end state (step 14).
06). In this way, among the batch jobs in the group that is being carried over, the batch job that has not been completed normally is searched for in the startup target state, and the business database logical group that has not been used by the batch job for the carry over process The name is acquired from the job name 401 (step 1407).

The above check is performed for all job information records for all group information records, and all business database logical group names that have not been used by the carryover processing batch job are acquired and returned to the business processing program. . The business processing program can prevent unauthorized reference or update of the business database 108 based on the return information.

As described above, according to the batch job scheduling method of the present invention, the batch job schedule can be executed on different dates for each group. By adopting the present invention in a system having a large-scale batch processing service, even if a delay occurs in the batch processing service that affects the start of the next system service, the system service can be provided in a prescribed time. By terminating and transferring unfinished batch jobs to the next system service, it is possible to minimize the impact of blocking specific tasks that approach specific business databases, and improve the operating rate. It becomes possible.

[0066]

According to the present invention, in a system having a large-scale batch processing service, there is an effect of preventing a delay in starting the next system service due to a delay in the batch processing service.

[Brief description of the drawings]

FIG. 1 is a system configuration diagram of a system to which the present invention is applied.

FIG. 2 is a diagram showing a system service of a system to which the present invention is applied in units of processing;

FIG. 3 is a diagram showing a method of managing date information used in the present invention.

FIG. 4 is a diagram showing a batch job information table for managing batch job information.

FIG. 5 is a diagram showing a group information table for managing batch job group information.

FIG. 6 is a diagram showing a schedule information table for managing schedule information.

FIG. 7 is a functional configuration diagram for realizing a batch scheduling method according to the present invention.

FIG. 8 is a processing flowchart of a batch job schedule start function.

FIG. 9 is a processing flowchart of a batch job schedule function.

FIG. 10 is a processing flowchart of a normal schedule function.

FIG. 11 is a processing flowchart of a carryover schedule function.

FIG. 12 is a processing flowchart of a batch job activation control function.

FIG. 13 is a flow chart showing the API usage provided to implement the present invention.

FIG. 14 is a processing flowchart of an API function for checking DB information.

FIG. 15 is a diagram showing logical group division of a DB used in business processing.

[Explanation of symbols]

101: Computer center 102: Host computer 103: Batch schedule function

 ──────────────────────────────────────────────────続 き Continuing on the front page (72) Inventor Shinya Kono 890 Kashimada, Saiwai-ku, Kawasaki-shi, Kanagawa F-term in Hitachi Information Systems Information Systems Division (Reference) 5B085 BA01

Claims (1)

[Claims] A batch job scheduling service based on batch job schedule information registered in advance in a host computer and date information (hereinafter referred to as a business day) for providing a batch job processing service. In the batch job scheduling method of the computer system that provides the information, define the scheduled processing date information, the conditions for starting, and the batch group information for dividing and managing the batch job by the processing unit etc. for all the registered batch jobs Create a table that enables status management for batch job scheduling for each batch job group, register the business day information used for the schedule as a calendar information table unique to the system, and use it for the batch job processing service Business day information When it is possible to acquire from the render information table, when scheduling a batch job, the schedule of the batch job belonging to the batch job group is executed for each registered batch job group, and the batch job processing service is A batch job scheduling method, wherein the business day date information to be provided can be assigned in batch job group units, and assigned to the batch job group based on the date information.