JP2000194576A - Job operation management system - Google Patents

Abstract

(57) [Summary] [PROBLEMS] In a system that manages jobs when a plurality of job subsystems share and execute a plurality of jobs constituting a job net throughout the system,
Centralize the creation and update of job net operation definition information, and reduce the number of steps required for setting definitions. SOLUTION: An operation information definition unit 004 of a computer 001
Creates job operation definition information for the job net and the job to which it belongs, and stores it in the operation information file 005. The automatic generation control unit 006 controls the operation information file 00
5, the operation definition information for each business subsystem is generated and stored in the system-specific operation information file 007. The distribution control unit 008 distributes each system-specific operation information file 007 to the corresponding business subsystem. Each business subsystem stores the distributed operation definition information in the update information file 0
13 and the maintenance control unit 014 creates and updates the operation master 015.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a system that manages jobs when a plurality of job subsystems share and execute a plurality of jobs constituting a job net of the entire system. The present invention relates to a job operation management system that generates and distributes job operation definition information for a subsystem.

[0002]

2. Description of the Related Art In a conventional calculation center operation, in order to efficiently execute a huge amount of batch jobs, job execution is automatically started or the execution order relation of a large number of batch jobs is defined in advance. In addition, a method for automatically executing a job without operator intervention is known, and has already been actually used in many calculation centers.

[0003] On the other hand, from the viewpoint of the hardware and operating system (OS) of a computer that executes a job, computers having different platforms, such as a mainframe, a UNIX (Note) server, and a personal computer (PC) server, are mixed. In addition, there is a tendency that the batch processing is distributed to different platforms according to the purpose, such as a mainframe subsystem for the main system subsystem and a UNIX server for the information subsystem.
Further, there is a growing need to automatically execute the entire distributed batch processing in a predetermined order, and its operation has already begun. (Note) UNIX
Is a registered trademark in the United States and other countries licensed by X / Open Company Limited.

[0004] A network in which a plurality of jobs are arranged according to their execution order is called a job net. From the viewpoint of job operation management, the above system is a system in which a plurality of business subsystems share and execute a plurality of jobs constituting a job net throughout the entire system. It becomes necessary to start a job shared by another business subsystem with the end of the operation, and a plurality of business subsystems cooperate according to the definition of the job net to continue execution of a series of jobs. In the conventional job operation management, a job net and a job operation definition are set for each business subsystem, and job execution control is performed based on the operation definition information.

[0005]

According to the above-mentioned conventional job operation management method, a lot of work time is required to create operation definition information of a job net and a job to be shared by each business subsystem, and a definition error occurs. There is a problem that the test work by the increase. In particular, a business subsystem called a master system that controls the execution of job nets throughout the system is required, and the operation definition information held by this master system and the operation definition information held by other business subsystems partially Since the definition information is created and updated individually even though the definition is duplicated, there is a problem that a definition error due to inconsistency is likely to occur.

An object of the present invention is to provide a job operation management system which unifies the creation and update of job net operation definition information throughout the entire system and reduces the number of steps required for setting and testing the definition. .

Another object of the present invention is to provide a storage medium for a program for creating and updating job net operation definition information.

[0008]

According to the present invention, there is provided a computer which operates a job which can be connected to each of the business subsystems, and this computer stores job operation definition information on a job net and a job to which the job belongs. And processing means for generating job operation definition information for each business subsystem from the job operation definition information in the storage means, and distributing the generated job operation definition information for each business subsystem to the corresponding business subsystems Each of the business subsystems has processing means for receiving the distributed job operation definition information and registering / updating the job operation definition information in the storage means. And

Further, the present invention is a storage medium for storing a computer-readable program, the program comprising: (a) an execution order relationship of a plurality of jobs constituting a job net; And inputting information on each job net and an identifier corresponding to the business subsystem executing the job on the display device, and (b) inputting information for each job net from the input information;
Create operation definition information for each job, store it in the storage device,
(C) Job operation definition information for each business subsystem is extracted and stored in a storage device using the identifier corresponding to the business subsystem in the created operation definition information as a key, and (d) each created business subsystem A storage medium for storing a program including each step of distributing another job operation definition information to each relevant business subsystem is characterized.

[0010]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS One embodiment of the present invention will be described below with reference to the drawings.

FIG. 1 is a diagram showing the overall configuration of a job operation management system according to this embodiment. The system includes a computer 001 that creates and distributes job operation definition information, a business subsystem group 011, and a transmission line 012 that can connect both. The computer 001 is a computer such as a PC having a GUI (Graphical User Interface) function, and has an environment file 003, an operation information file 005, and a system-specific operation information file 007 on a storage device in addition to the display device 010. And an environment definition unit 002, an operation information definition unit 004, an automatic generation control unit 006, a distribution control unit 008, and a file transfer control unit 009 as programs of the processing unit. The environment file 003 contains the system I for each business subsystem of the business subsystem group 011.
D, environment information such as a host name and a network address are stored. The operation information file 005 stores definition information about job nets and jobs required for job operation management. The system-specific operation information file 007 stores definition information for each business subsystem among the definition information of the operation information file 005. The environment definition unit 002
The environment information input by the operator is stored in the environment file 003. The operation information definition unit 004 stores the definition information of the job net and the job input by the operator in the operation information file 005. The automatic generation control unit 006 extracts and generates definition information for each business subsystem from the operation information file 005, and stores it in the system-specific operation information file 007. The distribution control unit 008 and the file transfer control unit 009
2 and the definition information in the system-specific operation information file 007 is distributed to each business subsystem.

The business subsystem group 011 is a subsystem for executing business processing, such as a backbone system and an information system built on computers that are different platforms. Each business subsystem has an update information file 013, an operation master 015, and a monitor file 017 on a storage device, and a file transfer control unit 009, a maintenance control unit 014, a schedule unit 016, and a job execution control unit as processing unit programs. 018. The update information file 013 temporarily stores the operation definition information distributed to the subsystem. The operation master 015 stores the updated operation definition information. The monitor file 017 stores operation definition information to be executed on the day of operation of the operation master 015. The file transfer control unit 009 stores the file transferred from the computer 001 in the update information file 013. The maintenance control unit 014 inputs the update information file 013 and updates the operation master 015. The schedule unit 016 includes:
The schedule of the operation day is determined with reference to the operation master 015, and the operation master 01 is determined according to the determined schedule.
5 is stored in the monitor file 017. The job execution control unit 018 controls the execution of a batch job based on the contents of the monitor file 017.

The program including the operation information definition unit 004, the automatic generation control unit 006, and the distribution control unit 008 is stored in a storage medium and read into a memory of the computer 001 via a drive connected to the computer 001, It can be transmitted to the memory of the computer 001 via a driving device connected to the computer, another computer, or a network, and can be executed by the computer 001.

FIG. 2A shows the data structure of the environment file 003. Each record of the environment file 003 has a host name 02 corresponding to each system ID 020.
1, a network address 022, an update information file name 023, and a master system display 038. The system ID 020 is the identifier of each business subsystem, and the host name 021 is the name of the host computer of the subsystem. Network address 02
Reference numeral 2 denotes an address assigned to the host computer regarding a network connecting the business subsystems. The update information file name 023 is the name of the update information file 013 stored in the business subsystem. The master system display 038 shows a business subsystem that controls job net execution of the entire system in the business subsystem group 011 to be defined.

FIG. 2B shows the data structure of the operation information file 005. Operation information file 005
Stores a job net definition table 024 for defining a job net and a job definition table 030 for defining a job in the job net. Each record of the job net definition table 024 is provided for each job net, and includes an update category 025, a job net name 026, a job net start mode 027, a start time, and a system ID.
028 and an event code 029. The update category 025 specifies the category when the record is an add / update / delete record. The job net name 026 is an identifier of the job net. Startup mode 02
Reference numeral 7 designates a classification of whether the job net is started by an event, by a start time, or by the end of the preceding job net. The start time specifies the start time when the start mode 027 is activated by the start time. The system ID 028 is an identifier of a business subsystem that executes the job net. The event code 029 is a code set when the activation mode 027 is an event activation, and is a code cited when the job net is activated.

Each record of the job definition table 030 is provided for each job, and includes an update category 031, a job net name 032, a job name 033, a job start mode 034, a start time, an abnormal condition, a system ID 035,
Each data item includes an event code 036 and a preceding job name 037. The update category 031 specifies the category when the record is an add / update / delete record.
The job net name 032 is the identifier of the job net to which the job belongs, and the job name 033 is the name of the job. The activation mode 034 specifies a category of whether the job is activated by an event, activated by a start time, or activated upon completion of a preceding job. The start time specifies the start time when the start mode 034 is activated by the start time. The abnormal condition classifies a processing method when the job ends abnormally. The system ID 035 is an identifier of a business subsystem that executes the job. The event code 036 is a code set when the activation mode 034 is the event activation, and is a code cited when the job is activated. If a job in a higher-level job net is a lower-level job net at the same time, the event code 036 of the job and the event code 029 of the corresponding job net must be the same. The preceding job name 037 specifies the name of at least one job executed immediately before the job in the same job net. The data structure of the system-specific operation information file 007, update information file 013, operation master 015, and monitor file 017 is as follows.
This is the same as the data configuration of the operation information file 005.

FIG. 3 is a diagram for explaining a method of operating a batch job in which a plurality of business subsystems cooperate to execute a shared job. FIG. 3 shows the business subsystem group 01.
1 shows an example in which the service subsystem 1 is composed of three systems of the service subsystems 040, 041, and 042. Business subsystem 04
0 is called a master system, and performs job net execution control of the entire system. The service subsystem 041 and the service subsystem 042 are called slave systems, and execute jobs assigned to the respective subsystems under the control of the master system.

The job net 043 includes a job group 044 to be executed by the business subsystem 041 and a job group 045 to be executed by the business subsystem 042. When it is time to execute the job groups 044 and 045, the job execution control unit 018 of the business subsystem 040 starts the start instruction event for starting the job groups 044 and 045 for the business subsystems 041 and 042, respectively. 046 is issued. The start instruction event 046 is the event code 03 assigned to the job.
6 is included. The job execution control units 018 of the business subsystems 041 and 042 that have received the start instruction event 046 refer to the job definition table 030 on the monitor file 017 and start the job corresponding to the event code 036. Each job execution control unit 018
The end of the started job is monitored, and an end report event 0 is sent to the business subsystem 040 when the job ends.
Issue 47. The end report event 047 includes an event code 036 assigned to the job and a normal end / abnormal end classification. End report event 04
7, the job execution control unit 018 of the business subsystem 040 refers to the job definition table 030, recognizes the job name 033 of the completed job, and activates the next job using the completed job as the preceding job. Do.

Each job subsystem stores a job control language (JCL) for a job to be shared and executed in a storage device, interprets the JCL corresponding to the job when starting the job, and executes a corresponding program. Start running. Each business subsystem stores a program for issuing a start instruction event 046 or an end report event 047 on a storage device, and starts executing the program by the JCL.

A single job belonging to an upper-layer job net may be developed as a lower-layer job net. For example, a single job 0 belonging to the job net 043
45 may be defined as a job net executed by the business subsystem 042, and this job net may be composed of a chain of a plurality of jobs. In this case, the business subsystem 040 activates the job 045 and the business subsystem 0 to activate the corresponding job net.
42, the business subsystem 042 issues an end report event 047 to the business subsystem 040 when the execution of this job net is completed. The job execution control unit 018 of the business subsystem 042 includes the job net definition table 024 and the job definition table 03 on the monitor file 017.
0, the execution of the job included in the job net is controlled. By activating the job of the slave system in units of job nets, the processing of the job execution control unit 018 can be distributed and the number of times of issuing the start instruction event 046 and the end report event 047, that is, the number of times of communication can be reduced.

FIG. 4 is a flowchart showing the flow of processing of the computer 001. First, the operation information definition unit 004 displays a main menu on the display device 010 (Step 050). This main menu includes environment definition and operation definition. When an environment definition is selected via an input device (not shown) (step 051 environment definition), the environment definition unit 0
02 displays an environment definition information screen on the display device 010. When the necessary information is input by the operation management operator, the environment definition unit 002 creates an environment file 003 for setting the operation information (step 052). Normally, the environment definition need only be performed when the system is initially installed or when the system configuration is changed. When the operation definition is selected (step 051 operation definition), the operation information definition unit 004 displays an operation definition information screen on the display device 010. When a job net definition and a job definition are input by the operation management operator, the operation information definition unit 004 sets a job net definition table 024 and a job definition table 030,
Create the operation information file 005 (Step 05
3). When the automatic generation is instructed by the operation management operator, the automatic generation control unit 006 sets the operation information file 005
Then, a system-specific operation information file 007 for each business subsystem is created (step 054). When distribution is instructed by the operation management operator, the distribution control unit 00
8 distributes the system-specific operation information file 007 to the corresponding business subsystem via the file transfer control unit 009 (step 055). Each business subsystem is
This file is received via the file transfer control unit 009, and an update information file 013 is created. The maintenance control unit 014 performs maintenance on the operation master 015 based on the update information file 013.

FIG. 5 is a flowchart of a process in which steps 053, 054 and 055 are further developed and shown. The operation information definition unit 004 includes an operation information file 005
, A list of registered job net definitions is displayed on the display device 010, and the user is prompted to select whether to update the job net definition or additionally register a new job net definition (step 060). Next, a job net definition is updated or newly input according to the job net definition information input by the operation management operator, and a job net definition table 024 is created (step 061). Job net definition table 024
In the update category 025, a category of new / update / delete is set. Regarding the job net to be activated, the event activation setting and the event code 029 must be set in the activation mode 027. Next, the job definition is updated or newly input according to the job definition information input by the operation management operator, and a job definition table 030 is created (step 062). In the update category 031 of the job definition table 030, a category of new / update / delete is set.
For a job to be activated, an event activation setting and an event code 036 must be set in the activation mode 034. Next, it is checked whether the input definition is valid (step 063). The confirmation items include that the system IDs 028 and 035 are registered as the system ID 020 in the environment file 003, and the job net name 03 defined in the job definition table 030.
2 is registered as the job net name 026 in the job net definition table 024, the event code 036 is specified for the job whose activation mode 034 is an event activation, and the job in the job net is simultaneously When configuring a job net, the event code 036 of the job and the corresponding event code 029 are the same. If the definition is not valid in this determination, the process returns to step 061, and the definition is accepted. If the definition is determined to be valid, the created job net definition table 024 and job definition table 030 are registered in the operation information file 005 (step 064).

When the automatic generation control unit 006 is activated,
The automatic generation range is determined according to the instruction of the operation management operator (step 066). When the entire automatic generation range is designated, a system-specific definition table is generated for all defined operation information, and a subsystem-specific definition table is generated from the system ID (step 067). First, regarding the generation of the master system definition, a table is generated for all records in the table. That is, the same table as the created job net definition table 024 and job net definition table 030 is generated for the master system. Next, a table for the slave system is generated. The system ID 020 of the master system is acquired from the master system display 038 of the environment file 003, a record of the job net definition table 024 having a system ID 028 other than the system ID 020 is searched, and a table is created for each system ID 028. Similarly, system I
A record of the job definition table 030 having a system ID 035 other than D020 is searched, and the system ID 035 is searched.
Create a separate table. At this time, the format of the table is
These are the same as the job net definition table 024 and the job definition table 030, respectively. When only the update is instructed in the determination of step 066, a subsystem-specific definition table is generated for only the operation information for setting addition / update / deletion in the update category 025 and the update category 031 (step 068). The flow of automatic generation is basically Step 6
7, but update categories 025 and 031 are added to the search conditions for searching the job net definition table 024 and the job definition table 030, respectively. After the subsystem-specific definition table is automatically generated, the update categories on the job net definition table 024 and the job definition table 030 are reset (step 069). However, if only the update portion is specified in step 066, the operation management operator is inquired about the reset of the update section (step 070). If the determination in step 070 is reset, step 069 is executed. Next, the system-specific operation information file 007 is initialized, and the created definition table is registered in the system-specific operation information file 007. At this time, a name is uniquely assigned to the table.

The distribution control unit 008 controls the synchronous update between the business subsystems simultaneously with the distribution of the system-specific operation information definition 007 to the business subsystems 011. When the distribution control unit 008 is activated, the registered table name is first displayed on the screen in the system-specific operation information file 007, and the operation management operator is inquired about whether the distribution can be executed or not (step 072). If there is an instruction to permit distribution in the content confirmation in step 073, step 074 is executed. If there is an instruction to disable distribution, the process ends. In step 074, the file transfer control unit 009 is sequentially activated in accordance with the contents of the environment table 003, and all tables are transmitted to each business subsystem 011 via the transmission path 012. Here, the end of all transmission processing is waited. If all tables have been transmitted normally, step 077 is executed. If at least one table is abnormal, the fact is displayed on the screen and the processing is terminated (steps 076 and 078). ). At step 077, the operation management operator is inquired about the judgment on whether or not the maintenance of the operation master can be executed. If the operation can be executed, the maintenance control unit 014 on each business subsystem 011 is sequentially remotely activated and the operation master 015 is sequentially executed.
To update. At this time, if the update category is new, all the existing information is initialized and re-registered, and if the update category is additional update, addition and update are performed in record units of the table. Here, the distribution control unit 008 waits for the end of the maintenance processing for all the business subsystems 011, terminates the processing if all the tables have been updated normally, and if there is any abnormality, notifies that fact. Display on the screen and instruct all business subsystems 011 to roll back,
The process ends after invalidating the update. As described above, the distribution control has been described by way of the transmission path, but in addition, the operation master on the open disk device that can be shared by the business subsystems can be updated.

FIG. 6 is a diagram showing an example of a screen displayed on the display device 010 when defining a job net and a job. The job net 090 includes a job 093 and a job 094, and the job 093 is a job net 09.
1. The job 094 is developed as a job net 092, and a chain of jobs belonging to the job net 091 and a chain of jobs belonging to the job net 092 are defined. The lower part of each box shows the job name or job net name, and the upper part shows the system ID of the business subsystem that executes the job. In this way, the job net is visually displayed, and the order relation of the jobs constituting the job net,
I of the subsystem that executes the job net and the job
D, a job net name, a job name, and the like can be added, updated, and deleted. In addition, another data item can be displayed or input / updated by designating a box indicating a job. The system IDs of the job nets 091 and 092 are 02 and 03, respectively. Since the job nets are job nets to be executed in the slave system, the start mode 027 of the job nets 091 and 092 is an event start, and the event code 029 is set. is necessary. The start mode 034 of the job 093 and the job 094 is an event start, and the setting of the event code 036 is necessary.

The correspondence between the platform and the business subsystem is arbitrary, and the present invention can be implemented without any problem even if a plurality of business subsystems are constructed on the same platform.

[0027]

As described above, according to the present invention, a computer for creating and updating job operation definition information is provided separately from the business subsystem, and this computer creates job operation definition information centrally. Since operation definition information for each business subsystem is generated and distributed to each business subsystem, the number of steps required for setting the definition and testing can be reduced.

[Brief description of the drawings]

FIG. 1 is a diagram illustrating an overall system configuration of a job operation management system according to an embodiment.

FIG. 2 is a diagram illustrating a data configuration of an environment file 003 and an operation information file 005 according to the embodiment.

FIG. 3 is a diagram illustrating a job operation management method for executing a job that is shared by a plurality of business subsystems.

FIG. 4 is a flowchart illustrating a flow of processing of a computer 001 according to the embodiment.

FIG. 5 is a flowchart showing an expanded process of steps 053 to 055 of the embodiment.

FIG. 6 is a diagram illustrating an example of a display screen when a job net and a job are defined.

[Explanation of symbols]

001: Computer, 004: Operation information definition unit, 005: Operation information file, 006: Automatic generation control unit, 007: System-specific operation information file, 008: Distribution control unit, 01
1 ... business subsystem group, 013 ... update information file,
024: job net definition table, 030: job definition table

Claims (3)

[Claims] 1. A system in which a plurality of business subsystems execute a plurality of jobs constituting a job net across the entire system by sharing at least one job as a unit, and a job execution provided in each business subsystem. In a system in which the control means controls the execution of jobs assigned based on the job operation definition information stored in the storage means, a computer that manages job operations connectable to each of the business subsystems is provided, and the computer includes: Storage means for storing job operation definition information for the job net and the job to which it belongs, processing means for generating job operation definition information for each business subsystem from the job operation definition information in the storage means, and each generated business Processing means for distributing job operation definition information for each subsystem to the corresponding business subsystems; Has, each of said operational subsystem, the job management system characterized by having processing means for registering and updating of the job operation definition information in the storage means receives the job operation definition information distributed. 2. A storage medium for storing a computer-readable program, wherein the program is used when a plurality of business subsystems share and execute a plurality of jobs constituting a job net throughout the system. A program for creating operation definition information on which management is based, and includes the following steps: (a) execution order relation of a plurality of jobs constituting a job net, each job net and a job identifier, and each job net; Information about the identifier corresponding to the business subsystem executing the job is input while being displayed on the display device, and (b) operation definition information for each job net and each job is created from the input information and stored in the storage device. Storing (c)
The job operation definition information for each business subsystem is extracted and stored in the storage device using the identifier corresponding to the business subsystem in the operation definition information as a key, and (d) the created job operation definition for each business subsystem Distribute the information to each applicable business subsystem. 3. A business subsystem for controlling execution of a job net over the entire system among a plurality of business subsystems is assigned as a master system, and the master system is created irrespective of a business subsystem identifier. 3. The storage medium storing a program according to claim 2, wherein the entire job operation definition information is distributed.