JP4722896B2 - Job operation management system, job operation management method, and job operation management program - Google Patents

Description

  The present invention relates to a job operation management system, method, and program for setting a schedule date for advance preparation associated with batch processing for executing a job.

  Conventionally, in batch processing in a computer system, a predecessor-success relationship of a job network (hereinafter referred to as a network) composed of a plurality of jobs or a combination of jobs to be executed in advance is registered, and scheduling is performed based on this predecessor relationship Has been done.

  A computer operation automation apparatus that automatically and continuously performs such job start-up and execution order schedules throughout the year has been studied (see, for example, Patent Document 1). According to the technique described in this document, the computer operation automation apparatus stores a schedule master storing an annual net schedule, a daily file storing start conditions on the net processing day, and a job processing pattern. And a net master in which the execution order of jobs in the net is stored. Then, the processing device searches for the start condition of the net specified by the time, the end of the preceding net, the hold release, or a combination thereof, and the macro call control statement corresponding to the change of the processing day of the executable net job Generate and start.

Also, a job start date setting method considering calendar information has been studied (see, for example, Patent Document 2). According to the technique described in this document, a job schedule information storage unit that stores input job schedule information, and a calendar information storage unit for scheduling a job start date are provided. Then, a job start date is set based on the contents of the job schedule information storage unit and the calendar information storage unit. Furthermore, the start date of another job is set from the job schedule information relative to the job.
JP-A-5-282164 (first page) JP-A-10-187610 (first page)

  In order to reliably execute such batch processing, fixed schedule processing is executed in order to perform simulation on data sets and volumes used in the network. In the operation process of batch processing, prior work is performed manually (confirmation of a confirmed schedule processing result, delivery of a tape or a form, etc.) manually. Usually, such advance work is performed on the day or immediately before.

However, in the case of performing work in advance on the day of network execution, it is necessary for the person in charge to work on a holiday in an environment in which batch processing operation is performed even on holidays such as weekends and holidays.
Also, in an environment where large-scale batch processing operations are performed, advance preparation takes time, so preparations are made in advance on the day before the network execution date. In this case, it was necessary to work on a holiday in preparation for the execution of the network after the holiday.

Here, in an operation in which a fixed schedule process for a plurality of days is executed on a business day before a holiday, a network with the same name may have to be registered, and consideration is necessary for maintaining the preceding / following relationship correctly. However, commercially available software cannot queue networks with the same name as executable files.

  The present invention has been made to solve the above problems, and in a batch process in which a plurality of jobs coexist, a schedule date of a fixed schedule is set so that advance preparations associated with the batch process can be performed on business days. A job operation management system, a job operation management method, and a job operation management program are provided.

In order to solve the above problems, the invention according to claim 1, for the production job network, the execution date specific information Ho及 beauty for identifying the production date to perform this job network, the preparation job network, this Preparation date information for specifying the preparation date, reference date specifying information consisting of information on an initial reference date set in correspondence with the preparation date and information on a shift pattern to be moved so that the reference date does not become a closed day, and schedule master storage means which records information about the number of previous倒日for specifying the execution date against this reference date, the holiday master memory means for recording a holiday specifying information for specifying a holiday, job network daily A daily schedule storage means for providing a daily file storage area for storing a reserved file for executing a job file; A job operation management system comprising control means for managing execution of a network, wherein the control means determines an initial reference date using reference date specifying information of a preparation job network recorded in the schedule master storage means. If the initial reference date corresponds to a closed day recorded in the holiday master storage means, use the shift pattern of the reference date specifying information, and change the reference date to be a business day. To calculate a reference date for each preparation job network, specify a business day using closed day specification information recorded in the holiday master storage means, and in this business day, the schedule master storage for each reference date Sub-schedule means for specifying the execution date of each preparation job network by applying the number of advance days recorded in the means, the specified Execute a preparation job network on an execution date, identify a production job network whose production date is the preparation target date of the preparation job network, generate a reservation file for the production job network, and execute the execution date of the production job network The gist of the invention is that it includes a fixed schedule means for registering the reserved file in a daily file storage area and a job execution means for executing a job network of the reserved file on the actual date.

Invention according to claim 2, in the job management system of claim 1, wherein the sub-schedule means for preparing job network in a predetermined time period, identifying a run day of each preparation job network collectively The gist.

The invention according to claim 3, queuing in the job management system of claim 1 or 2, the execution date of production job network, the reservation file recorded in the Daily schedule storage means as an executable file An executable file storage means for storing the executable file, and the control means deletes the executable file from the executable file storage means when the job network of the executable file recorded in the executable file storage means ends normally In the case of newly queuing the reserved file for the current day in the daily schedule storage means, an execution file of the same job network as the reservation file to be queued remains unsettled in the execution file storage means. And stop queuing of the reserved file It means for outputting an alarm, in the execution file storing means, and summarized in that further comprising means for holding the execution file to preceding reservation file stopping the queuing.

The invention according to claim 4, for the production job network, the execution date specific information Ho及 beauty for identifying the production date to perform this job network, for preparing a job network, ready for specifying this preparation target day Target date information, initial reference date set corresponding to this preparation target date , reference date specifying information consisting of information related to shift pattern to move so that the reference date does not become a closed day, execution date for this reference date storing a schedule master storage means which records information about the number of previous倒日for identifying a holiday master memory means for recording a holiday specifying information for specifying a day off, the reservation file to run the job network each day A daily schedule storage means with a daily file storage area and job network execution management A job operation management system comprising a control means, wherein the control means uses the reference date specifying information of the preparation job network recorded in the schedule master storage means When the initial reference date is specified and the initial reference date corresponds to a closed day recorded in the holiday master storage unit, the reference date becomes a business day by using the shift pattern of the reference date specifying information. In this way, the base date of each preparatory job network is calculated, the business day is specified using the closed day specification information recorded in the holiday master storage means, Applying the number of advance days recorded in the schedule master storage means to specify the execution date of each preparation job network; and The preparation job network is executed on each specified execution day, the production job network having the production target date of the preparation job network as the production date is identified, a reservation file of the production job network is generated, and the production job network The scheduled schedule stage of registering the reserved file in the daily file storage area on the execution date of the execution date and the job execution stage of executing the job network of the reserved file on the actual date are executed.

The invention according to claim 5, for the production job network, the execution date specific information Ho及 beauty for identifying the production date to perform this job network, for preparing a job network, ready for specifying this preparation target day Target date information, initial reference date set corresponding to this preparation target date , reference date specifying information consisting of information related to shift pattern to move so that the reference date does not become a closed day, execution date for this reference date storing a schedule master storage means which records information about the number of previous倒日for identifying a holiday master memory means for recording a holiday specifying information for specifying a day off, the reservation file to run the job network each day A daily schedule storage means with a daily file storage area and job network execution management Using the job management system including a control means, a program for performing management of the job, the computer is the control means, the reference date specific information recorded prepared job network in the scheduled master memory means was used to identify the initial date, if this initial date corresponds to the recorded holiday in the holiday master storage means, using a shift pattern of the reference date specific information, the reference date is operating The reference date of each preparation job network is calculated by changing to be the day, and the business day is specified using the closed day specification information recorded in the holiday master storage means. By applying the number of advance days recorded in the schedule master storage means to the day, the execution date of each preparation job network is specified Schedule execution means, execute a preparation job network on each specified execution date, identify a production job network having a production target date of the preparation job network as a production date, generate a reservation file for the production job network, The gist is to function as a fixed schedule means for registering the reserved file in the daily file storage area on the execution date of the production job network and a job execution means for executing the job network of the reserved file on the production date.

(Function)
According to the first, fourth , and fifth aspects of the present invention, the control unit calculates the reference date of each preparation job network using the preparation job network reference date specifying information recorded in the schedule master storage unit. Then, the business day is specified using the closed day specifying information recorded in the holiday master storage means, and in this business day, the number of advance days recorded in the schedule master storage means is applied to each reference date, Identify the execution date of each preparation job network. Then run the ready job network execution date for each preparation job network, preparing target day of preparation job network to identify the production job network to production date, and generates the reservation file production job network. Then, the reserved file is registered in the daily file storage area of the execution date of the production job network. Then, the job network for the reserved file is executed on the actual day. Thereby, it is possible to prepare by generating a reservation file used for the production job network on business days other than the closed days. This reserved file is stored in a daily schedule storage means provided with a daily file storage area. Thus, even when there is a production job network that is used in common over a plurality of days, a separate reservation file can be generated at the same time. Therefore, even when preparing a job network for a plurality of days for a closed day, it is possible to generate a reservation file in a batch while maintaining the date relationship.

According to the present invention, when the initial reference date corresponds to a closed day recorded in the holiday master storage unit, the reference date is changed to be a business day using the shift pattern of the schedule data. As a result, the execution date of each preparation job network can be specified using the business day as the reference date.

According to the second aspect of the present invention, the execution date of each preparation job network is specified collectively for the preparation job networks for a predetermined period. Accordingly, it is possible to plan a schedule for preparing the production job network together with business days in consideration of holidays.

According to the third aspect of the present invention, when the job network of the executable file recorded in the executable file storage means is normally terminated, the control means deletes the executable file from the executable file storage means. In the case of newly queuing the reservation file for the current day in the daily schedule storage means, the execution file of the same job network as the reservation file to be queued remains in the execution file storage means because it has not been completed. Stops queuing of reserved files and outputs an alarm. Further, the execution file storage means holds the execution file preceded by the reserved file for which queuing has been stopped. Depending on the processing cycle of the job network, the same production job network may be executed on different days. For this reason, the corresponding day is queued from the reserved file every day, and even when there is an unfinished job network, it is possible to prevent the start of another duplicate job network and maintain the preceding / following relationship.

  According to the present invention, in batch processing in which a plurality of jobs are mixed, a job operation management system, a job operation management method, and a job operation management method for setting a schedule date of a fixed schedule so that advance preparations associated with batch processing can be performed on business days A job operation management program can be provided.

  DESCRIPTION OF EMBODIMENTS Hereinafter, embodiments embodying the present invention will be described with reference to FIGS. In the present embodiment, when a network for batch processing is executed, a job operation management system, a job operation management method, and job operation management for setting a preparation date for advance preparation for the batch processing as a business day Explain as a program. In the following description, a network for batch processing is called a “production network”, and a network for advance preparation is called a “preparation network”. The “production date” is a schedule date on which the “production network” is executed, and the “preparation date” is a schedule date on which the “preparation network” is executed.

In the present embodiment, as shown in FIG. 1, the job operation management server 20 as the job operation management system executes job operation management processing. An operator terminal (not shown) is connected to the job operation management server 20 via a communication network. This operator terminal is a computer terminal used by a person in charge of managing a job, and includes an input means such as a keyboard and a mouse, an output means such as a display, a communication means, etc. in addition to a CPU, RAM, and ROM. It has a function of transmitting data via the network, a function of displaying received data, and the like. The operator terminal is used when a user accesses the job operation management server 20 for setting each master data or receives a message from the job operation management server 20.

  On the other hand, the job operation management server 20 is a computer system that performs processing for generating an execution job using master data recorded in each master data storage unit described later. The job operation management server 20 includes a network master data storage unit DB1, a schedule master data storage unit DB2, a holiday master data storage unit DB3, a reference date master data storage unit DB4, and a data waiting master data storage unit DB5. Further, the job operation management server 20 includes a sub-schedule data storage unit DB6, a file master data storage unit DB7, a volume master data storage unit DB8, a reserved file data storage unit DB9, and a preceding / following relationship file data storage unit DB10. Further, the job operation management server 20 includes a data set cumulative file data storage unit DB11, a volume cumulative file data storage unit DB12, a network stock file data storage unit DB13, an execution file data storage unit DB14, and a network status data storage unit (not shown). Prepared). The job operation management server 20 includes a control unit 21 that controls these data storage units.

  The control unit 21 functions as a control unit that performs various data management processes for managing job operations. The control unit 21 includes a CPU, a RAM, a ROM, and the like (not shown), and performs processes (sub-schedule stage, finalized schedule stage, job execution stage, etc.) described later. By executing the job operation management program for that purpose, the control unit 21 functions as a schedule creation unit 211, a reservation file creation unit 212, a current day file extraction unit 214, and a queuing unit 215 as shown in FIG.

The schedule creation unit 211 functions as a sub-schedule unit, and generates sub-schedule data using each master data.
The reservation file generation unit 212 functions as a fixed schedule unit, and generates a reservation file and a preceding / following relationship file using sub-schedule data. Further, a data set accumulation file and a volume accumulation file are generated.

The current day file extraction means 214 extracts a reservation file to be executed on the actual day and stores it in the network stock file data storage unit DB13.
The queuing means 215 stores the reserved file in the network stock file data storage unit DB13 as an execution file in the execution file data storage unit DB14.

  As shown in FIG. 2A, network master data D10 for a network generated by combining one or a plurality of jobs is recorded in the network master data storage unit DB1. The network master data D10 includes data related to the network name, data wait attribute, hold code, class, execution machine, priority, start time, preceding network name, job name, job number, and preceding job number.

  Data relating to an identifier (network identifier) for specifying each network is recorded in the network name data area. In the present embodiment, a network name including a common name (“ULAK” in the present embodiment) representing the preparation network is used. In the network name of this preparation network, a number is added to the common name, and this additional number indicates the execution date of the production network. This number functions as preparation target date information for specifying the preparation target date. Therefore, the network name “ULAK11” of the preparation network means the common name “ULAK” and “11 days” as the execution date of the production network.

In the data waiting attribute data area, data (flag) that specifies a condition for starting execution of this network (execution start condition) and that specifies when processing execution is triggered by external data input is recorded. The

  In the hold code data area, data (flag) that specifies a case where execution of processing is started by a hold release instruction input by an operator is recorded as an execution start condition of the network.

In the class data area, data for specifying an execution class of this network (a set for comparing priorities (priorities) described later) is recorded.
In the execution machine data area, data for specifying a processing apparatus that executes this network is recorded.

In the priority data area, data for specifying the priority in the class is recorded.
Data relating to the start time of the network is recorded in the start time data area. This start time is set when the network start time is determined as an execution start condition.

  In the preceding network name data area, data relating to an identifier for specifying the preceding network is recorded. The termination of this preceding network is the execution start condition for this network. In the present embodiment, a plurality of networks can be designated as the preceding network.

  In the job name data area, data relating to an identifier for specifying each job constituting this network is recorded. When this network is composed of a plurality of jobs, a plurality of job names are recorded.

  In the job number data area, data relating to an identifier for specifying each job constituting this network is recorded. When this network is composed of a plurality of jobs, a job number is recorded corresponding to the job name.

  In the preceding job number data area, data relating to an identifier for specifying a preceding job for each job constituting this network is recorded. The end of this preceding job is the execution start condition for this job. When this network is composed of a plurality of jobs, the preceding job number is recorded corresponding to the job name. In addition, when there are a plurality of preceding jobs, a plurality of preceding jobs can be designated corresponding to the job name.

  The schedule master data storage unit DB2 functions as a schedule master storage unit, and schedule master data D20 regarding a schedule for executing network processing is recorded as shown in FIG. 2B. The schedule master data D20 includes data related to the network name, duplicate key, group code, reference date ID, processing pattern, processing cycle, holiday ID, standard processing date, shift pattern, and execution period.

Data relating to an identifier for specifying each network is recorded in the network name data area.
In the duplicate key data area, when a plurality of schedule master data D20 is registered with the same network name, data relating to an identifier for specifying each network is recorded. For example, the duplicate key is used when the network is executed in different processing cycles with the same network name.

In the group code data area, data relating to identifiers for specifying the same group for batch change in consideration of business characteristics is recorded.
In the reference date ID data area, data related to reference date specifying information for specifying the reference date is recorded. An initial reference date can be specified using this reference date specifying information. When a reference date ID including English characters is recorded in the reference date data area, the date registered in the reference date master data D40 recorded in the reference date master data storage unit DB4 described later is used as the reference date. Use. On the other hand, when a reference date ID composed only of numbers is recorded, the date indicated by the numbers is used as the reference date.

  In the processing pattern data area, data for specifying a day on which processing for this network can be executed is recorded. For example, when processing is performed on business days, a flag indicating “business days” is recorded.

  In the processing cycle data area, processing cycle information for specifying a cycle for executing processing is recorded. In this processing cycle, for example, flags indicating “daily”, “weekly”, “monthly”, “quarter”, “semi-annual”, “annual”, and the like are recorded.

  In the holiday ID data area, data relating to an identifier for identifying a calendar on which a day (a closed day) when work on the network is not performed is recorded. By using this holiday ID, a holiday day can be specified in a holiday master data storage unit DB3 to be described later.

In the standard processing date data area, data relating to a reference for calculating the execution date of the network is recorded. This standard is composed of the following three elements.
[A] “Number of days to move” for calculating the execution date from the reference date using the processing pattern
[B] “Adjustment symbol” for specifying “advance (-)” or “advance (+)” when calculating the execution date from the reference date
[C] “Counting date” used to identify the target month for calculating the base date
For example, when “advance (−)” is recorded as an addition / subtraction symbol, it is advanced by “number of days of movement” from the reference date.

In the shift pattern data area, if the execution date for this network or the reference date for calculating the execution date corresponds to a closed day, shift pattern information for specifying the pattern for changing the reference date or creation date Is recorded. The shift pattern includes “previous day” for moving forward and “next day” for moving forward.
In the execution period data area, data related to a period (execution period) for executing this network is recorded.

  The holiday master data storage unit DB3 functions as a holiday master storage unit, and holiday master data D30 for specifying a business day or a closed day is recorded in the calendar as shown in FIG. 2 (c). The holiday master data D30 includes data related to a holiday ID and a date.

In the holiday ID data area, data relating to an identifier for identifying a category of closed days is recorded.
In the date data area, closed day information relating to a date for specifying a closed day corresponding to the holiday ID is recorded.

  In the reference date master data storage unit DB4, as shown in FIG. 2D, reference date master data D40 for specifying a reference date for executing processing is recorded. The reference date master data D40 includes data related to a reference date ID and date.

In the reference date ID data area, data relating to an identifier for specifying the reference date is recorded.
In the date data area, data related to the date that becomes the reference date is recorded corresponding to the reference date ID.

  In the data waiting master data storage unit DB5, as shown in FIG. 2E, data waiting master data D50 for specifying data serving as a trigger for executing the network is recorded. The data waiting master data D50 includes data relating to the network name, arrival flag, input data ID, and flag on date.

Data relating to an identifier for specifying each network is recorded in the network name data area.
In the arrival flag data area, data relating to a flag for specifying the arrival of data serving as an execution start condition is recorded.

In the input data ID data area, data relating to an identifier for specifying input data which is an execution start condition is recorded.
In the flag-on date data area, data relating to an identifier for specifying a date as an execution start condition is recorded.

  In the sub-schedule data storage unit DB6, as shown in FIG. 3A, sub-schedule data specifying a specific date (schedule date) for executing the network using the network master data D10 and the schedule master data D20. D60 is recorded. The sub-schedule data D60 is generated when a monthly schedule creation process to be described later is executed. This sub-schedule data D60 includes schedule date, network name, duplicate key, class, reference date ID, start time, priority, standard processing date, processing pattern, hold code, wait attribute, shift pattern, holiday ID, processing cycle, execution Data including the machine, group code, preceding network, and input data ID.

  In the schedule date data area, data relating to the date on which the network is executed is recorded. In the schedule date data area, as described later, a preparation date is set for the preparation network, and a production date is set for the production network.

Data relating to an identifier for specifying a network to be executed is recorded in the network name data area.
In the duplicate key data area, data relating to duplicate keys recorded in the schedule master data D20 is recorded.

In the class data area, data related to the class recorded in the network master data D10 is recorded.
In the reference date ID data area, data related to the reference date ID recorded in the schedule master data D20 is recorded.

In the start time data area, data related to the start time recorded in the network master data D10 is recorded.
In the priority data area, data related to the priority recorded in the network master data D10 is recorded.

In the standard processing date data area, data related to the standard processing date recorded in the schedule master data D20 is recorded.
In the processing pattern data area, data related to the processing pattern recorded in the schedule master data D20 is recorded.

In the hold code data area, data related to the hold code recorded in the network master data D10 is recorded.
In the wait attribute data area, data relating to an identifier for specifying the wait state of the network is recorded. In this wait attribute data area, data relating to a flag for specifying the execution start condition of this network (hold release wait, input data wait, start time wait, etc.) is recorded.

In the shift pattern data area, data relating to the shift pattern recorded in the schedule master data D20 is recorded.
In the holiday ID data area, data related to the holiday ID recorded in the schedule master data D20 is recorded.

In the process cycle data area, data related to the process cycle recorded in the schedule master data D20 is recorded.
In the execution machine data area, data related to the execution machine recorded in the network master data D10 is recorded.

In the group code data area, data relating to the group code recorded in the schedule master data D20 is recorded.
In the preceding network data area, data relating to the preceding network recorded in the network master data D10 is recorded.

  In the input data ID data area, when a flag is recorded in the wait attribute data area of the network master data D10, data related to the input data ID recorded in the data wait master data D50 is recorded.

  In the file master data storage unit DB7, file master data for files (data sets) used for network execution is recorded. In this file master data, data relating to a data set name, a data set sequence, a volume sequence, a use form, a file form, a generation number, a current sequence, a label number, a label form, a head data set name, and a storage ID are recorded.

  The volume master data storage unit DB8 records volume master data for a recording medium (for example, a tape) used for execution of the network. This volume master data includes data related to storage ID, borcil, attribute, usage pattern, usage state, storage state, head borcil, schedule date, return date, creation date, and last storage date.

The reserved file data storage unit DB9 functions as a daily schedule storage unit, and stores a reserved file D90 generated including parameters, data sets, and volumes used for job execution, as shown in FIG. 3B. This reserved file data storage unit DB9 has a daily file storage area (daily folder) for storing the reserved file D90 for one month divided into days such as “for 1 day” to “for 31 day”. Is provided. And each reserved file D
90 includes data relating to a schedule date, class, priority, network name, waiting attribute, network attribute, execution machine, start time, and hold code.

In the schedule date data area, data relating to the date (preparation date or production date) for executing the network is recorded.
In the class data area, priority data area, network name data area, and waiting attribute data area, data related to the class, priority, network name, and waiting attribute recorded in the sub-schedule data D60 is recorded.

  In the network attribute data area, data relating to an identifier for specifying a network attribute is recorded. The network attributes include “hold attribute”, “input data wait attribute”, “start time wait attribute”, and the like.

  In the execution machine data area, the start time data area, and the hold code data area, data related to the execution machine, start time, and hold code recorded in the sub-schedule data D60 is recorded.

  As shown in FIG. 3C, the preceding / following relationship file D100 for the preceding / following relationship of the network is recorded in the preceding / following relationship file data storage unit DB10. The preceding / following relationship file D100 is configured to include data relating to a schedule date, a network name, a preceding network, and a subsequent network.

Data related to the processing date recorded in the sub-schedule data D60 is recorded in the schedule date data area.
In the network name data area, data related to the network name recorded in the sub-schedule data D60 is recorded.

  In the preceding network data area, data relating to the network name of the preceding network of this network is recorded. In the preceding network data area, data related to the preceding network name, schedule date, and execution status of the preceding network is recorded.

  In the subsequent network data area, data relating to the network name of the subsequent network of this network is recorded. In the subsequent network data area, data regarding the subsequent network name and schedule date of the subsequent network is recorded.

  In the data set cumulative file data storage unit DB11 and the volume cumulative file data storage unit DB12, data set cumulative files and volumes related to data sets and volumes identified by analyzing JCL (Job Control Language) generated by the fixed schedule process are stored. Cumulative files are recorded. These accumulated files are used for simulation of operation of data sets and recording media used in the network.

  In the network stock file data storage unit DB13, a reservation file D90 on the execution target date extracted from the reservation file data storage unit DB9 on the network execution date is stored as a network stock file.

Then, the network stock file recorded in the network stock file data storage unit DB13 is loaded (queued) and transferred to the execution file data storage unit DB14. The execution file data storage unit DB 14 functions as an execution file storage unit, and an execution machine (not shown) executes the network using the recorded execution file. When the network is normally terminated, the executable file is deleted from the executable file data storage unit DB14.

  The network execution status is recorded in the network status data storage unit. In this network status data storage unit, a network status record configured to include data related to the start date / time, end date / time, and end code is recorded for the network name.

Data related to the network name recorded in the execution file is recorded in the network name data area.
In the start date / time data area, data related to the date / time when execution of the network is started is recorded.

In the end date / time data area, data related to the date / time when the execution of the network is finished is recorded.
Data relating to the end state is recorded in the end code data area. In this end code data area, identifiers for specifying “not executed”, “being executed”, “completed”, and “abnormal end” are recorded. Here, “completed” means that the network has been normally terminated.

(Overview of operation)
Next, processing when performing job operation management according to the present embodiment will be described. Here, the outline of the entire process will be described with reference to FIG.

  First, the control unit 21 of the job operation management server 20 performs a monthly schedule creation process on a predetermined day of each month (for example, “15th day”) (step SA-1). Here, the execution date (preparation date) of the preparation network for the next month is specified, and the sub-schedule data D60 is generated and registered in the sub-schedule data storage unit.

  Next, the control unit 21 of the job operation management server 20 executes a fixed schedule process on the preparation date (step SA-2). Here, the preparation network in which the preparation date is set as the schedule date is executed. Specifically, a reservation file for the network (production network) executed on the preparation target date (production date) of the preparation network is generated. Then, this reserved file is registered in the daily folder corresponding to the actual date in the reserved file data storage unit DB9.

  Then, on the actual date, the control unit 21 of the job operation management server 20 performs queuing processing of the reserved file from the reserved file data storage unit DB9 and executes the actual network (step SA-3). Here, when the network is held because it has not been completed, an incomplete network is dealt with (step SA-4).

Hereinafter, a monthly schedule creation process, a fixed schedule process, a reservation file extraction process, a queuing process, and a pending network handling procedure will be described.
(Monthly schedule creation process)
First, the monthly schedule creation process will be described with reference to FIG. In the present embodiment, sub schedules for the next month as a schedule creation target period are generated in a lump. Here, the control unit 21 of the job operation management server 20 executes the following processing for each preparation network recorded in the network master data storage unit DB1.

First, the control unit 21 of the job operation management server 20 executes a process target network specifying process (step S1-1). Specifically, the schedule creation means 211 of the control unit 21 extracts schedule master data D20 in which the network name of the network to be processed is recorded from the schedule master data storage unit DB2. Then, using the processing cycle and standard processing date recorded in the schedule master data D20, it is determined whether or not it is necessary to create a schedule.

  For example, a network whose processing cycle is “monthly” is a schedule creation target. For a network whose processing cycle is “quarter”, a schedule is created when the next month matches the cycle of the quarter starting from “month of standard processing date”. For a network with a processing cycle of “semi-annual”, a schedule is created when the next month matches the half-year cycle from the “month of standard processing date”. The “annual” network is subject to schedule creation when the next month matches the “standard processing month”.

Here, the case where the monthly schedule of a preparation network is produced is demonstrated. For the preparation network, “monthly” is set as the processing cycle.
The number added to the common name in the network name of the preparation network indicates the execution date (preparation target date) of the production network as described above. In the time chart shown in FIG. 8, the production network is executed regardless of the business day WD and the closed day HD.

  Then, the control unit 21 of the job operation management server 20 executes reference date calculation processing for the preparation network (step S1-2). Specifically, the schedule creation unit 211 of the control unit 21 extracts the schedule master data D20 in which the network name of the processing target preparation network is recorded from the schedule master data storage unit DB2. Then, the schedule creation unit 211 calculates a reference date using the processing cycle and the reference date ID recorded in the schedule master data D20. Here, since the processing cycle of the preparation network is “monthly”, the schedule creation unit 211 specifies the date recorded in the reference date ID data area as the reference date. In the present embodiment, it is assumed that the date of the previous day is recorded in the reference date ID data area of the schedule master data D20 with respect to the execution date of the production network.

  Next, the control unit 21 of the job operation management server 20 executes a closed day determination process for the reference date (step S1-3). Specifically, the schedule creation means 211 of the control unit 21 specifies the closed days recorded in the holiday master data storage unit DB3 using the holiday ID recorded in the schedule master data D20. Then, the schedule creating unit 211 determines whether the calculated reference date corresponds to a closed day recorded in the holiday master data D30.

  Here, when the reference date corresponds to a closed day (in the case of “YES” in step S1-3), the control unit 21 of the job operation management server 20 executes the reference date transfer process (step S1-4). . Specifically, the schedule creation means 211 of the control unit 21 moves the reference date using the shift pattern recorded in the schedule master data D20. For example, when “previous day” is recorded as the shift pattern, the reference date is changed to the previous day. And the schedule preparation means 211 performs a closed day determination process again using the changed reference | standard day (step S1-3). By repeating this process, the reference date is set to the business day WD as shown in FIG.

If the reference date does not correspond to a closed day (in the case of “NO” in step S1-3), the control unit 21 of the job operation management server 20 executes a preparation date specifying process (step S1-5). Specifically, the schedule creation unit 211 of the control unit 21 calculates the preparation date using “number of days of movement” and “addition / subtraction symbol” recorded in the standard processing date data area. Here, the schedule creation means 211 specifies the date when the reference date is included and the date of advance or postponement by “number of days of movement” is set as the preparation date. In this embodiment, “2 business days ahead” is set.

  And the control part 21 of the job operation management server 20 performs a schedule registration process (step S1-6). Specifically, the schedule creation means 211 of the control unit 21 generates sub-schedule data D60 using each data recorded in the network master data D10 and the schedule master data D20, and registers it in the sub-schedule data storage unit DB6. To do. In this case, the calculated preparation date is set in the execution date data area of the sub-schedule data D60. Thereby, as shown in FIG. 8, a preparation day is set to the business day WD.

  Then, the above processing is executed for all the preparation networks. When the sub-schedule data D60 having the same schedule name on the same schedule date has already been registered in the sub-schedule data storage unit DB6, double registration of the network is not performed.

(Final schedule processing)
Next, the fixed schedule process will be described. This process is executed when a schedule date (preparation date) set in each preparation network arrives.

  Specifically, the control unit 21 of the job operation management server 20 extracts the sub-schedule data D60 in which the preparation date is set as the schedule date. As a result, the preparation network to be executed is specified in the fixed schedule process.

Then, the control unit 21 of the job operation management server 20 executes the specified preparation network, so that the control unit 21 functions as the reserved file generation unit 212.
The reservation file generation unit 212 specifies the actual date by the number added to the common name of the preparation network. Then, the sub-schedule data D60 in which the identified actual date is set as the execution date is extracted from the sub-schedule data storage unit DB6. Here, it is assumed that the production network is extracted. Then, the job registered in the network recorded in the sub-schedule data D60 of the production network is developed into JCL using the file master data storage unit DB7 and the volume master data storage unit DB8 to generate a reserved file. When executing a plurality of preparation networks, the network names are executed in the order of the numbers (the actual dates) added to the common names of the preparation networks.

  Further, the reservation file generation unit 212 generates the preceding / following relationship file D100 using the preceding network information recorded in the sub-schedule data D60, and stores it in the preceding / following relationship file data storage unit DB10.

  Here, the reserved file generation means 212 performs file and volume simulation according to the specification of JCL. When a simulation is performed for a plurality of production networks, the simulation is performed in the order of the production date. In this simulation, a data set accumulation file and a volume accumulation file are used. Then, the data set cumulative file data storage unit DB11 and the volume cumulative file data storage unit DB12 are updated according to the simulation result.

Next, the reserved file generating unit 212 records the generated reserved file D90 in the reserved file data storage unit DB9. In this case, the reserved file generating unit 212 generates the “daily folder (for n days)” corresponding to the number (n) added to the common name of the preparation network in the reserved file data storage unit DB9. Stores the reservation file.

(Reserved file extraction process)
Next, reservation file extraction processing will be described. In the reserved file extraction process, the current day file extraction unit 214 of the control unit 21 of the job operation management server 20 searches the reserved file data storage unit DB9 for the reserved file D90 of the current day. When the reservation file D90 for the day is extracted, the file extraction unit 214 for the day moves the reservation file D90 to the network stock file data storage unit DB13.

(Queueing process)
Next, the queuing process will be described. This queuing process is repeatedly executed for each network recorded in the network stock file data storage unit DB13.

  First, the control unit 21 of the job operation management server 20 executes processing for specifying a network name to be queued (step S2-1). Specifically, the queuing means 215 of the control unit 21 specifies the network name of the network stock file to be queued from the network stock file data storage unit DB13.

  Next, the control unit 21 of the job operation management server 20 executes a process for confirming the execution status of the network having the same name (step S2-2). Specifically, the queuing means 215 of the control unit 21 searches whether an execution file having the same network name as this network stock file remains in the execution file data storage unit DB 14. Here, the queuing means 215 confirms the execution status of the network using the network status data storage unit. Here, in the network status data storage unit, if the network status record with the same network name as the queuing target has an end code indicating “not executed”, “running”, or “abnormal end”, the status is not completed Thus, the executable file remains in the executable file data storage unit DB14.

  If an execution file having the same network name as the network stock file to be queued remains in the execution file data storage unit DB 14 (in the case of “YES” in step S2-2), the job operation management server 20 The control unit 21 executes alarm processing (step S2-3). In this case, the queuing means 215 of the control unit 21 does not execute queuing. Then, the queuing means 215 transmits a message notifying the operator terminal that queuing is not possible, and deletes it from the network stock file data storage unit DB13.

  On the other hand, if no executable file having the same network name as the network stock file to be queued remains in the executable file data storage unit DB 14 (in the case of “NO” in step S2-2), the control unit of the job operation management server 20 21 executes processing for confirming the execution status of the preceding network of this network (step S2-4). Specifically, the queuing means 215 of the control unit 21 checks whether or not the preceding network of this network has not been completed. If the preceding network has not been completed (“YES” in step S2-4), the control unit 21 of the job operation management server 20 executes queuing processing in the hold state of this network (step S2-5). . Specifically, the queuing means 215 of the control unit 21 sets “hold wait” as the network stock file wait attribute for this network, and records it as an execution file in the execution file data storage unit DB 14.

  On the other hand, when the preceding network has not been completed (“NO” in step S2-4), the control unit 21 of the job operation management server 20 executes queuing processing (step S2-6). Specifically, the queuing means 215 of the control unit 21 queues the network stock file as it is and records it as an execution file in the execution file data storage unit DB14.

  When queuing is performed in steps S2-5 and S2-6, the network stock file is deleted from the network stock file data storage unit DB13. The above processing is repeated for all networks recorded in the network stock file data storage unit DB13.

(Procedure for dealing with unfinished networks)
Next, an example of an incomplete network handling procedure will be described. This incomplete network handling procedure is performed by the operator of the job operation management server 20 when an incomplete network occurs.

Here, first, the status of an incomplete network is confirmed (step S3-1).
If the network that has not been completed is in a completed state, the network that has not been queued in step S2-3 is queued (step S3-2).

  Next, the hold of the subsequent network held in step S2-5 is released (step S3-3). Thereby, execution of the held network is started.

As described above, according to the present embodiment, the following effects can be obtained.
In the above embodiment, the control unit 21 of the job operation management server 20 calculates a reference date (step S1-2), and executes a closed day determination process for the reference date (step S1-3). Here, when the reference date corresponds to a closed day (in the case of “YES” in step S1-3), the control unit 21 of the job operation management server 20 executes the reference date transfer process (step S1-4). . Then, the execution date (preparation date) of the preparation network is set based on the reference date set on this business day (step S1-5). Thereby, the creation date of the reservation file for advance preparation (fixed schedule work) can be set to the business day. Therefore, preparation of the production network can be executed on a preset business day (preparation day), and the lost work day shift can be eliminated. Therefore, even if it becomes clear that a defect occurs in the batch processing in the simulation in the fixed schedule processing, it can be handled by the operator or the person in charge on the business day.

  In the above embodiment, the reserved file data storage unit DB9 is divided into days such as “for 1 day” to “for 31 days”, and a daily file storage area for storing the reserved file D90 for one month ( Daily folder). As a result, in the fixed schedule processing, even if there are production networks with different production dates and networks having the same network name, it is possible to separately prepare a reservation file. Thereby, when there is a closed day, a fixed schedule process can be performed collectively. In particular, even in the case of long holidays, a reservation file can be prepared in advance.

In the above embodiment, the control unit 21 of the job operation management server 20 specifies a queuing target network name (step S2-1), and executes a process for confirming the execution status of the network having the same name (step S2-). 2). Here, an executable file having the same network name as the network stock file to be queued is an executable file data storage unit D.
If it remains in B14 (in the case of “YES” in step S2-2), the control unit 21 of the job operation management server 20 does not execute queuing but executes alarm processing (step S2-3). . Thereby, even when a network having the same network name is repeatedly executed, the execution management of the network can be reliably performed.

  Further, when the preceding network has not been completed (“YES” in step S2-4), the control unit 21 of the job operation management server 20 executes queuing processing in the hold state of this network (step S2- 5). As a result, it is possible to prevent the execution of the subsequent network in which the network having the same name as that of the network that has been left unfinished is used as the preceding network.

In addition, you may change the said embodiment into the following aspects.
In the above embodiment, the job operation management server 20 is provided with the network stock file data storage unit DB13, and the reservation file D90 extracted from the reserved file data storage unit DB9 is moved to the network stock file data storage unit DB13. Perform queuing. Instead of this, it is also possible to configure to perform queuing directly from the reserved file data storage unit DB9.

  In the above embodiment, sub-schedules for one month are generated together, but this period is not limited to one month, and it is also possible to generate sub-schedules in units of one week, for example.

In the above embodiment, the preparation target date information is included in the network name of the preparation network, but the setting method of the preparation target date information is not limited to this.
Further, the number of advance days is specified using the “adjustment symbol” and the “number of days of movement” recorded in the standard processing date data area, but is not limited to this.

The system schematic of embodiment of this invention. It is explanatory drawing of the data recorded on each data storage part, (a) is a network master data storage part, (b) is a schedule master data storage part, (c) is a holiday master data storage part, (d) is Reference date master data storage unit, (e) is an explanatory diagram of the data recorded in the data waiting master data storage unit. It is explanatory drawing of the data recorded on each data memory | storage part, (a) is a sub schedule data memory | storage part, (b) is a reservation file data memory | storage part, (c) is recorded on a preceding / following relation file data memory | storage part. FIG. Explanatory drawing of the outline | summary of the process of this embodiment. Explanatory drawing of the process sequence of this embodiment. Explanatory drawing of the process sequence of this embodiment. Explanatory drawing of the process sequence of this embodiment. Explanatory drawing of the time chart of this embodiment.

Explanation of symbols

DESCRIPTION OF SYMBOLS 20 ... Job operation management server, 21 ... Control part, 211 ... Schedule creation means, 212 ... Reserved file generation means, 214 ... Same day file extraction means, 215 ... Queuing means, DB1 ... Network master data storage part, DB2 ... Schedule master Data storage unit, DB3 ... holiday master data storage unit, DB4 ... reference date master data storage unit, DB5 ... data waiting master data storage unit, DB6 ... sub-schedule data storage unit, DB7 ... file master data storage unit, DB8 ... volume master Data storage unit, DB9 ... Reserved file data storage unit, DB10 ... Preceding / following relationship file data storage unit, DB11 ... Data set cumulative file data storage unit, DB12 ... Volume cumulative file data storage unit, DB13 ... Network stock file Data storage unit, DB14 ... executable file data storage unit.

Claims (5)

For production job network, the execution date specific information Ho及 beauty for identifying the production date to perform this job network,
For the preparation job network, the preparation target date information for identifying the preparation target date, the initial reference date set in correspondence with the preparation target date , and the information on the shift pattern to be moved so that the reference date does not become a closed day. date specifying information made, a schedule master storage means which records information about the number of previous倒日for specifying the execution date for this date,
Holiday master storage means for recording holiday day specifying information for specifying a holiday,
A daily schedule storage means provided with a daily file storage area for storing a reserved file for executing the job network every day;
A job operation management system comprising control means for managing job network execution,
The control means is
Using the reference date specifying information of the preparation job network recorded in the schedule master storage unit, an initial reference date is specified, and when this initial reference date corresponds to a closed day recorded in the holiday master storage unit , By using the shift pattern of the reference date specifying information, by changing the reference date to be a business day, the reference date of each preparation job network is calculated,
Identify business days using closed day identification information recorded in the holiday master storage means, and in this business day, apply the number of advance days recorded in the schedule master storage means for each reference date, Sub-schedule means for specifying the execution date of each preparation job network,
Execute a preparation job network on each of the specified execution dates, and identify a production job network with the preparation target date of the preparation job network as a production date,
A confirmation schedule means for generating a reservation file for the production job network and registering the reservation file in a daily file storage area on an execution date of the production job network;
A job operation management system comprising job execution means for executing a job network of the reserved file on the actual date. The job operation management system according to claim 1 , wherein the sub-schedule unit collectively specifies an execution date of each preparation job network for the preparation job networks for a predetermined period. The execution file storage means for queuing and storing the reserved file recorded in the daily schedule storage means as an execution file on the execution date of the production job network,
The control means includes
Means for deleting the executable file from the executable file storage means when the job network of the executable file recorded in the executable file storage means has ended normally;
In the daily schedule storage unit, when a reservation file for the current day is newly queued, an execution file of the same job network as the reservation file to be queued remains in the execution file storage unit because it has not been completed. Means for stopping the queuing of the reserved file and outputting an alarm;
3. The job operation management system according to claim 1, further comprising means for holding an execution file preceded by the reserved file for which the queuing has been stopped in the execution file storage means. For production job network, the execution date specific information Ho及 beauty for identifying the production date to perform this job network,
For the preparation job network, the preparation target date information for identifying the preparation target date, the initial reference date set in correspondence with the preparation target date , and the information on the shift pattern to be moved so that the reference date does not become a closed day. date specifying information made, a schedule master storage means which records information about the number of previous倒日for specifying the execution date for this date,
Holiday master storage means for recording holiday day specifying information for specifying a holiday,
A daily schedule storage means provided with a daily file storage area for storing a reserved file for executing the job network every day;
A method for performing job operation management using a job operation management system comprising control means for performing job network execution management,
The control means is
Using the reference date specifying information of the preparation job network recorded in the schedule master storage unit, an initial reference date is specified, and when this initial reference date corresponds to a closed day recorded in the holiday master storage unit , By using the shift pattern of the reference date specifying information, by changing the reference date to be a business day, the reference date of each preparation job network is calculated,
Identify business days using closed day identification information recorded in the holiday master storage means, and in this business day, apply the number of advance days recorded in the schedule master storage means for each reference date, A sub-schedule stage that identifies the execution date of each preparatory job network;
Execute a preparation job network on each of the specified execution dates, and identify a production job network with the preparation target date of the preparation job network as a production date,
Generating a reservation file for the production job network and registering the reservation file in a daily file storage area on the execution date of the production job network; and
And a job execution stage for executing a job network of the reserved file on the production date. For production job network, the execution date specific information Ho及 beauty for identifying the production date to perform this job network,
For the preparation job network, the preparation target date information for identifying the preparation target date, the initial reference date set in correspondence with the preparation target date , and the information on the shift pattern to be moved so that the reference date does not become a closed day. date specifying information made, a schedule master storage means which records information about the number of previous倒日for specifying the execution date for this date,
Holiday master storage means for recording holiday day specifying information for specifying a holiday,
A daily schedule storage means provided with a daily file storage area for storing a reserved file for executing the job network every day;
A job operation management program using a job operation management system comprising a control means for managing job network execution,
A computer as the control means;
Using the reference date specifying information of the preparation job network recorded in the schedule master storage unit, an initial reference date is specified, and when this initial reference date corresponds to a closed day recorded in the holiday master storage unit By using the shift pattern of the reference date specifying information, by changing the reference date to be a business day, the reference date of each preparation job network is calculated,
Identify business days using closed day identification information recorded in the holiday master storage means, and in this business day, apply the number of advance days recorded in the schedule master storage means for each reference date, Sub-schedule means for specifying the execution date of each preparation job network,
Execute a preparation job network on each of the specified execution dates, and identify a production job network with the preparation target date of the preparation job network as a production date,
A confirmation schedule means for generating a reserved file for the production job network and registering the reserved file in a daily file storage area on an execution date of the production job network;
A job operation management program that functions as job execution means for executing a job network of the reserved file on the actual date.

Images