JP2014035654A - Job order confirmation method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To solve the problem of execution order not being sufficiently confirmed by just confirming the execution order regarding that needing confirmation related to the order since the structure is complicated by the form of adding a function to an existing system although a need exists to build by confirming the execution order of a job in a present business system.SOLUTION: In order to solve the problem, this invention: takes into consideration the hierarchical relationship pertaining to a job; extracts that needing confirmation of the order relationship from the hierarchical relationship; and confirms or defines the order relationship pertaining to these. Furthermore, a job net which is a unit aggregating jobs especially for management of one or a plurality of jobs is handled in this invention.

Description

  The present invention relates to a technique for confirming the execution order of so-called jobs executed on a system.

  Currently, it is common that a system for executing business in a financial institution or the like is introduced. As information for executing this task, what is called a job is used. A job refers to a unit for executing and managing a process divided into several processes when data is processed by a large computer or the like. As described above, since management is performed separately for a large computer, the management thereof is often complicated. Also, in a job, if the execution order is wrong, a desired process cannot be executed. Therefore, it is necessary to check the job execution order.

  As a technique for solving this problem, Patent Document 1 has been proposed. In Patent Document 1, it is an object to efficiently verify the design contents of a business information system. For this reason, Patent Document 1 relates to a system design verification apparatus. The system design verification apparatus holds job relation information indicating a combination of jobs having an order relation, and data relation information indicating job file data and related jobs. Assuming that the related jobs of the job file to be verified are the first job and the second job, the order relationship between the first job and the second job from the combination of the access type of the first job and the access type of the second job. Determine if you need it. If the order relationship is necessary, it is confirmed in the job relationship information whether the order relationship is established between the first job and the second job. In order to solve this problem, Patent Document 1 holds job relationship information indicating a combination of jobs having an order relationship, and data relationship information indicating job file data and its related jobs. Assuming that the related jobs of the job file to be verified are the first job and the second job, the order relationship between the first job and the second job from the combination of the access type of the first job and the access type of the second job. Determine if you need it. If the order relationship is necessary, it is confirmed in the job relationship information whether the order relationship is established between the first job and the second job.

JP 2008-97946 A

  However, in Patent Document 1, there is a problem that it is not possible to cope with a complicated system structure or job structure. In particular, the structure of today's system is complicated by adding functions to a certain system, so it is not possible to simply confirm the execution order of items that require confirmation of the order relationship. It is enough. As described above, since the structure is complicated, jobs are often hierarchized, and this premise is not considered in Patent Document 1.

  In order to solve the above-described problems, in the present invention, considering the hierarchical relationship of jobs, those for which the order relationship should be confirmed are extracted, and the order relationship is confirmed or defined.

  According to the present invention, it is possible to confirm or define the job execution order even in a more complicated system.

It is a figure which shows the execution order relationship of each component of a job net with a tree structure and a directed graph. FIG. 3 is a tree structure diagram showing a hierarchical structure of a job net. It is a data structure figure which shows a response | compatibility with a job net component and a fully qualified name. It is a data structure figure of job execution order information. It is a hardware block diagram which shows one form of a job execution system. It is a figure which shows the functional relationship of a job execution order verification apparatus and a job management apparatus. 6 is a flowchart illustrating a process for verifying a job execution order. It is a flowchart which verifies the execution order of the job net element in the same hierarchy.

  A job net is a job flow that defines the execution order relationship of a plurality of jobs for a job that is a unit for processing or managing data in a computer system. For this reason, the job net is also a unit for collecting jobs in order to manage one or a plurality of jobs. FIG. 1 is an example of a diagram illustrating a job execution order relationship in a job net. In the job net of FIG. 1, not only jobs but also job nets are included in the job net, and the job net has a hierarchical structure. A job net including a job net having a hierarchical structure, a job net, and the job net itself is called a component of the job net. The components of “job net 11” include not only “job 21”, “job 22”, and “job net 23”, which are the components immediately below, but also “job 31” and “job 41”.

  FIG. 2 is a tree structure diagram of the job net of FIG. The first level job net is called a root job net (10). A character string obtained by connecting job net component element names from the root job net (10) in hierarchical order is called a fully qualified name. Assuming that there are no component names directly under the job net, it is possible to uniquely identify each job net component by designating it with a fully qualified name. FIG. 3 is a structural diagram showing the correspondence between the component (11) of the job net and the fully qualified name (12). In the example of FIG. 3, each component name of the job net is connected using “/” as a delimiter, but a character or character string other than “/” may be used. Although a method using a fully qualified name has been described here as a method for uniquely identifying a job net component, a job net component can also be identified by a method of specifying a series of IDs for each job net component. .

  The components of “job net 11” are “job 21”, “job 22”, “job 23 net”, “job net 24”, and “job 25”. The “job net 23” is executed when the execution of “job 21” is completed. In the relationship between “job 21” and “job net 23”, “job 21” is called “preceding job” and “job net 23” is called “following job”. Similarly, “job net 23” is a preceding job of “job 25”. Here, “Job 25” is not only “Subsequent Job” of “Job Net 23” but also “Subsequent Job” of “Job 21”. The relationship between “job 21” and “job net 23” or “job net 23” and “job 25” is referred to as “direct preceding job” or “direct subsequent job”, and “job 21” and “job 25” The relationship is called “indirect preceding job” or “indirect succeeding job”. In this document, unless otherwise specified, the term “preceding job” refers to “indirect preceding job”, and the term “subsequent job” refers to “indirect succeeding job”. In the execution sequence table (13a) of “job net 11”, “job 21”, “job 22”, “job net 23”, “job net 24”, and “job 25” are directly related to the preceding job (14a). Direct successor jobs (15a) are defined respectively. The execution order table may have a format other than that shown in FIG. 4 as long as the execution order relationship between the job net components is defined.

  FIG. 5 is a diagram illustrating a configuration example of the job execution system, which includes five computers 16, 17, 18a, 18b, and 18c that are connected to each other via a network. The system includes a job execution device (18) that executes a job, a job management device (16) that causes the job execution device (18) to execute a job based on a predetermined execution condition, and verifies the job execution order. It comprises a job execution order verification device (17) to be performed. In FIG. 5, three job execution apparatuses are shown, but any number of job execution apparatuses may be used. A configuration in which the job management device (16) also serves as the job execution device (18) is possible, and a configuration in which the job execution order verification device (17) also serves as the job execution device (18) or the job management device (16) is possible. . Each of these devices is realized by a so-called computer device, and each function is executed by an arithmetic device such as a CPU included in each of them according to a program.

  FIG. 6 is a functional relation diagram of the job management device (16) and the job execution order verification device (17). The job execution order verification device (17) has functions of an input / output control unit (20), a job execution order verification unit (21), and a job definition acquisition unit (22). The job management device (16) has the function of the job management unit (23). The interface (20) is assumed to be operated by a general-purpose PC keyboard or monitor, but may be other devices or other application programs. The job definition information (24) holds information about job execution conditions for issuing job execution instructions to the job execution device. Each function is a function realized by cooperation of hardware components and software components of a computer, and the hardware components and software components can take various combinations.

  To verify whether an execution order relationship is defined between two jobs in a job net, the job net in the lowest hierarchy is extracted from the job nets to which the two jobs to be verified belong in common, and the job This is done by verifying whether an execution order relationship is defined between job net components in the hierarchy immediately below the net. The two jobs to be verified are called verification target job 1 and verification target job 2. Of the job nets to which the verification target job 1 and the verification target job 2 belong in common, the lowest level job net is called a common hierarchy job net. Among the job net components directly under the common hierarchy job net, a job net component that includes the verification target job 1 or is the same as the verification target job 1 is referred to as a verification target element 1. Among the job net components directly under the common hierarchy job net, the job net component that includes the verification target job 2 or is the same as the verification target job 2 is defined as the verification target element 2.

  The job net of FIG. 1 will be described below as an example. An example in which the verification target job 1 is “/ job net 11 / job net 24 / job net 35 / job 44” and the verification target job 2 is “/ job net 11 / job net 24 / job net 37 / job 46” Explained. The common hierarchy job net is “/ job net 11 / job net 24”, the verification target element 1 is “/ job net 11 / job net 24 / job net 35”, and the verification target element 2 is “/ job net 11 / job net 24”. / Job net 37 ". Regarding “/ job net 11 / job net 24 / job net 35” of the verification target element 1, the verification target element 1 is a preceding job of the verification target element 2. As described above, “/ job net 11 / job net 24 / job net 35 / job 44” which is job 1 to be verified and “/ job net 11 / job net 24 / job net 37 / job 46” which is job 2 to be verified. An execution order relationship is defined between the verification target job 1 and the verification target job 1 is a preceding job of the verification target job 2.

  FIG. 7 is a flowchart for verifying whether an execution order relationship is defined between two arbitrary jobs in a job net. First, arbitrary two jobs, a verification target job 1 and a verification target job 2 are designated as targets for verifying whether or not the execution order relationship is defined (S1). It is assumed that the verification target job 1 and the verification target job 2 are each designated by a fully qualified name. From the fully qualified names of the verification target job 1 and the verification target job 2, the components for each layer are extracted for each delimiter (S2). A component for each layer extracted from the verification target job 1 is referred to as a comparison target element 1, and a component extracted from the verification target job 2 is referred to as a comparison target element 2. The component names of the comparison target element 1 and the comparison target element 2 in the nth hierarchy are compared (S3). If the element names of the comparison target element 1 and the comparison target element 2 match, the component element name of the next hierarchy is extracted (S2). If the hierarchy when the comparison results do not match is the nth hierarchy, the n-1th hierarchy is the common hierarchy, the comparison target element 1 of the nth hierarchy is the verification target element 1, the comparison target element 2 is the verification target element 2, Each is determined (S4). In S2 to S4, the job net component names are compared in order from the root job net, but are verified sequentially from the lower order toward the root job net, and the common hierarchy job net, verification target element 1, and verification target element 2 are extracted. May be. Next, for the verification target element 1 and the verification target element 2, the execution order relationship between them is verified using the job execution order table of the common hierarchy job net (S5). The detailed procedure of S5 will be described later. Finally, based on the verification result of the execution order relation between the verification target element 1 and the verification target element 2, the execution order relation between the verification target job 1 and the verification target job 2 is output (S6). When an execution order relationship is defined between the verification target element 1 and the verification target element 2 and the verification target element 1 is a preceding job of the verification target element 2, the verification target job 1 is a preceding job of the verification target job 2 is there. When a context is defined between the verification target element 1 and the verification target element 2, and the verification target element 1 is a subsequent job of the verification target element 2, the verification target job 1 is a subsequent job of the verification target job 2. When the context is not defined in the verification target element 1 and the verification target element 2 (or when the definition indicating the context is not recorded: the same applies to other portions), the verification target job 1 and the verification target job 2 Execution order relationship is not defined.

  FIG. 8 is a flowchart for verifying whether or not the execution order relation is defined between the verification target element 1 and the verification target element 2, and details the process of S5 of FIG. First, the preceding job of the verification target element 1 is extracted based on the job execution order table (S51). Next, it is confirmed whether a preceding job exists in the verification target element 1 (S52). If there is a preceding job of the verification target element 1, it is verified whether the verification target element 2 is included in the preceding job (S53). When the preceding job of the verification target element 1 exists and the verification target element 2 is included in the preceding job, the verification target element 1 is a subsequent job of the verification target element 2 (S57).

  When the preceding job does not exist in the verification target element 1 and when the verification target element 2 is not included in the preceding job of the verification target element 1, the preceding job of the verification target element 2 is determined based on the job execution order table. Extract. (S54). Based on the result of extracting the preceding job of the verification target element 2 in S54, it is verified whether the preceding job of the verification target element 2 exists (S55). If there is a preceding job of the verification target element 2, it is verified whether the verification target element 1 is included in the preceding job (S56).

  When the preceding job of the verification target element 2 exists and the verification target element 1 is included in the preceding job, the verification target element 2 is a subsequent job of the verification target element 1 (S58). If the preceding job of the verification target element 2 does not exist in S55, and if the verification target element 1 is not included in the preceding job of the verification target element 2 in S56, the verification target element 1 is related to the execution target element 2 in the order of execution. Is not defined (S59). The above procedure is a procedure for verifying whether the verification target element 2 is present before the verification target element 1, and then verifying whether the verification target element 1 is present before the verification target element 2. However, other procedures may be used. . For example, a procedure for verifying whether or not the verification target element 2 is after the verification target element 1 and then verifying whether or not the verification target element 1 is after the verification target element 2, or the verification target element 2 is before the verification target element 1 And then verifying whether the verification target element 2 is after the verification target element 1, verifying whether the verification target element 2 is after the verification target element 1, and then verifying the element 2 before the verification target element 1 It can also be done by a procedure to verify whether there is any.

10 root job net 11 job net component name column 12 fully qualified name column 13 job net name 14 direct preceding job column 15 direct subsequent job column 16 job management device 17 job execution order verification device 18 job execution device 19 interface unit 20 Input / output control unit 21 Job execution order verification unit 22 Job definition acquisition unit 23 Job management unit 24 Job definition information

Claims (4)

In the job order confirmation method for confirming the execution order of job net components consisting of one or more jobs in a computer system,
For each of the job components, a relationship between each of the plurality of job components including a hierarchical relationship is stored in a storage device,
For the hierarchical relationship, for job components in each hierarchy, if there is an order relationship with the job component common to two or more job components, specify the order relationship of each of the two or more job components,
A job order confirmation method, wherein the specified order relation is stored in the storage device. In the job order confirmation method according to claim 1,
A job execution order confirmation method for storing job execution order information indicating a relationship between preceding and subsequent job constituent elements for job constituent elements of each hierarchy. In the job execution order confirmation method according to claim 1 or 2,
The hierarchical relationship is stored for each job net component as information in which the fully qualified name of the job net component is associated. In the job order confirmation method according to any one of claims 1 to 3,
The job order confirmation method, wherein the job component includes a job itself.

Images