Job management system

Abstract

To support efficient deletion of an unnecessary job definition, in a job management system which manages a job executed by a computer.SOLUTION: A job management system previously holds a condition for deleting a job definition and a point which shows the level in which the job matching the condition should be a deletion object, extracts the job matching the condition from job definition data as a deletion candidate job, gives the point corresponding to the condition to the extracted job, and indicates the given point.SELECTED DRAWING: Figure 5

Description

[Technical Field]

[0001] The present invention relates to a technique for managing jobs executed by a computer. [Background technology]

[0002] Jobs executed by a computer may be centrally managed by a job management system. The job management system manages job definitions, execution schedules, etc., and each job is executed under the management of the job management system. The job management system may be configured on the same computer that executes the jobs, or on a computer separate from the computer that executes the jobs.

[0003] The following Patent Document 1 addresses the problem of "presenting changes to a past job when a new job is executed using the past job if the changes have been made to the past job" and describes a technology in which "when an information processing device executes a first job that is processed according to settings, if the settings are changed from a predetermined first setting to a second setting that is different from the first setting and the first job is executed, the information processing device stores first setting information related to the first setting and second setting information related to the second setting in a storage unit in association with each other (207), and when an instruction is given to execute a second job that is different from the first job using the first setting of the first job (201, 202), the information processing device controls to display the first setting and the second setting stored in the storage unit in association with each other (203)" (see abstract).

[0004] The following Patent Document 2 addresses the issue of "reducing the workload," and describes a technology in which "an information processing device 100 acquires first conditions 102 of the execution environment in which a first job 101 is deployed by referring to first information that enables the conditions of the execution environment in which the job is deployed to be identified for each job. The information processing device 100 deploys the first job 101 in the created first execution environment 110 and executes it. Upon completion of the first job 101, the information processing device 100 deletes the created first execution environment 110 if a deletion condition 103 corresponding to the first job 101 is satisfied" (see abstract). [Prior art documents] [Patent documents]

[0005] [Patent Document 1] Japanese Patent Publication No. 2022-144095 [Patent Document 2] Japanese Patent Application Publication No. 2023-124715 Summary of the Invention [Problem to be solved by the invention]

[0006] In the process of actually operating an information system, the number of job definitions tends to increase as other related information systems are updated, etc. If a large number of unnecessary job definitions, such as job definitions that are no longer in use or that were only used for testing, are left unused, this could have a negative impact on the operation of the information system. For example, the existence of a large number of job definitions could result in a decrease in processing performance, or operators would have to spend extra time searching for job definitions.

[0007] Therefore, it is desirable to delete unnecessary job definitions, but on the other hand, accidentally deleting a necessary job definition can cause problems in the operation of the information system (and the business that uses it). Therefore, job definitions must be deleted with great care. In particular, in an information system with many job definitions, deleting unnecessary job definitions is a heavy workload. Prior art such as Patent Documents 1 and 2 does not present a specific method for efficiently deleting unnecessary job definitions.

[0008] The present invention has been made in view of the above-mentioned problems, and has an object to support efficient deletion of unnecessary job definitions in a job management system that manages jobs executed by a computer. [Means for solving the problem]

[0009] The job management system of the present invention stores in advance conditions for deleting a job definition and points that indicate the degree to which a job that matches the conditions should be deleted, extracts the job that matches the conditions from the job definition data as a job candidate for deletion, and assigns the points corresponding to the conditions to the extracted job and presents the assigned points. [Effects of the Invention]

[0010] According to the job management system of the present invention, it is possible to support efficient deletion of unnecessary job definitions in a job management system that manages jobs executed by a computer. Other objects, configurations, advantages, etc. of the present invention will become apparent with reference to the following embodiments. [Brief explanation of the drawings]

[0011] [Figure 1] 1 is a configuration diagram of a job management system 1 according to a first embodiment. [Figure 2A] 1 shows an example of the structure of schedule data 121. [Figure 2B] 1 shows an example of the configuration of agent data 131. [Figure 2C] 1 shows an example of the configuration of job definition data 141. [Figure 2D] 1 shows an example of the configuration of user data 151. [Figure 2E] 1 shows an example of the configuration of job history data 161. [Figure 2F] 10 shows an example of the structure of deletion candidate condition data 171. [Figure 3A] FIG. 10 is a schematic diagram showing a procedure of advance preparation when registering a new job definition. [Figure 3B] FIG. 10 is a schematic diagram showing a procedure for registering a new deletion candidate condition. [Figure 3C] FIG. 10 is a schematic diagram showing a procedure for registering a new job definition. [Figure 3D] FIG. 2 is a schematic diagram showing a procedure for executing a job. [Figure 4]FIG. 3B is a diagram listing data items registered in FIGS. 3A to 3D. [Figure 5] An example of a deletion candidate condition described in the deletion candidate condition data 171 is shown below. [Figure 6] 10 is a flowchart illustrating a process in which the job management system 1 extracts deletion candidate jobs. [Figure 7] 10 is a flowchart illustrating details of S2. [Figure 8] 10 is a flowchart illustrating details of S21. [Figure 9] 10 is a flowchart illustrating details of S22. [Figure 10] 10 is a flowchart illustrating details of S23. [Figure 11] 10 is a flowchart illustrating the details of S24. [Figure 12] 10 is a flowchart illustrating details of S25. [Figure 13] 10 is a flowchart illustrating details of S26. [Figure 14] 2 is an example of a user interface provided by the job management system 1. [Figure 15] 2 is an example of a user interface provided by the job management system 1. DETAILED DESCRIPTION OF THE INVENTION

[0012] <First Embodiment> 1 is a configuration diagram of a job management system 1 according to a first embodiment of the present invention. The job management system 1 is a system that manages jobs executed by a host 2. The host 2 is a computer that executes jobs. A terminal 3 is a terminal through which a user of the job management system 1 inputs instructions to be given to the job management system 1.

[0013] The job management system 1 includes a deletion candidate extraction unit 11, a schedule data management unit 12, an agent data management unit 13, a job definition data management unit 14, a user data management unit 15, a job history data management unit 16, and a deletion candidate condition data management unit 17. Each management unit stores schedule data 121, agent data 131, job definition data 141, user data 151, job history data 161, and deletion candidate condition data 171, respectively.

[0014] 2A shows an example of the configuration of schedule data 121. Schedule data 121 is data having records describing planned execution schedules of jobs to be executed by host 2. Schedule data 121 has a job name A1 and a next planned execution date and time A2. When creating a job execution schedule, job management system 1 records the execution schedule in each of these fields.

[0015] FIG. 2B shows an example of the configuration of agent data 131. Software that executes jobs on a host 2 is called an agent. Agent data 131 is data that has records that describe the agents executed by each host 2. Agent data 131 has an agent ID B1, a host name B2, and an IP address B3. The host name B2 and IP address B3 are used to identify each host 2. Agent ID B1 is an identifier of the agent executed on the host 2.

[0016] FIG. 2C shows an example of the configuration of job definition data 141. Job definition data 141 is data having records that describe job definitions (job attributes). Job definition data 141 has a job name C1, definition update date and time C2, execution destination C3, job creator C4, job execution user C5, and deletion lock C6. Job name C1 is the job identifier. Definition update date and time C2 is the date and time when the record was created or updated. Execution destination C3 is the identifier of the agent that executes the job. Job creator C4 is the identifier of the user who created the job, and may be a user on host 2 or a user on job management system 1. The same applies to the following users. Job execution user C5 is the identifier of the user that executes the job. The job is executed with the user authority of job execution user C5. A job with deletion lock C6 set to "locked" will remain and not be deleted even if it meets the job deletion conditions described below.

[0017] FIG. 2D shows an example of the configuration of user data 151. User data 151 is data having records describing the definition of a user of the job management system 1 or the definition of a user of the host 2. User data 151 has a user name D1 and authority D2. User name D1 is a user identifier (e.g., login ID). Authority D2 is information indicating the authority corresponding to the actions that the user can perform, and indicates the authority by, for example, the role to which the user belongs.

[0018] FIG. 2E shows an example of the configuration of job history data 161. The job history data 161 is data having records describing the history of jobs executed by the host 2. The job history data 161 has a job name E1, an execution start date and time E2, an execution end date and time E3, and an execution result E4. The job name E1 is an identifier for the job. The execution start date and time E2 and the execution end date and time E3 are the dates and times when the job started and ended, respectively. The execution result E4 indicates whether the job was executed successfully.

[0019] FIG. 2F shows an example of the configuration of deletion candidate condition data 171. The deletion candidate condition data 171 is data having records describing conditions for extracting jobs to be deleted (deletion candidate jobs) from the job definition data 141. The deletion candidate condition data 171 includes a condition name F1, a score F2, a referenced database F3, a referenced column F4, and an extraction condition F5. The condition name F1 is a convenient name for distinguishing extraction conditions. The score F2 quantifies the degree to which a job that meets the condition should be deleted, and the score F2 is assigned to a job that meets the condition. The extraction condition F5 is a condition for extracting deletion candidate jobs. For convenience of description, the conditions are defined using sentences in the specific example described below, but the actual extraction conditions may be in any format, such as a formula. The referenced database F3 and referenced column F4 are the data and column names referenced when extracting jobs according to the extraction conditions.

[0020] 3A is a schematic diagram showing the procedure for advance preparation when registering a new job definition. In order to define a new job in the job definition data 141, it is necessary to prepare in advance the execution destination C3 and the job execution user C5 (i.e., the agent and user who will execute the job). If these have not been prepared in advance, the job manager accesses the job management system 1 via the terminal 3 and adds new records to the agent data 131 and the user data 151, respectively.

[0021] 3B is a schematic diagram showing the procedure for registering new deletion candidate conditions. New deletion candidate conditions are created by registering a new record in the deletion candidate condition data 171. Furthermore, a deletion lock C6 is set for jobs that do not need to be deleted even if they match the deletion candidate conditions.

[0022] 3C is a schematic diagram showing the procedure for registering a new job definition. A new job definition is created by registering a new record in job definition data 141. For jobs with a scheduled execution date and time, a record describing the execution schedule for that job is also added to schedule data 121. At this point, a record describing only job name E1 may be registered in job history data 161, or a history record may be registered when the job is actually executed.

[0023] 3D is a schematic diagram showing the procedure for executing a job. The job manager obtains the scheduled execution date and time of a job by referencing the schedule data 121, and causes the host 2 to execute the job whose scheduled execution date and time has arrived. At the start and end of the job, the results are recorded in a record of the job history data 161. While FIG. 3D shows that the job execution is instructed to the job management system 1 via the terminal 3, the job management system 1 itself may refer to each piece of data and start the job autonomously.

[0024] FIG. 4 lists the data items registered in FIGS. 3A to 3D. In the preparation of a job definition (FIG. 3A), new values ​​are registered in each column of user data 151 and agent data 131. When registering deletion candidate conditions (FIG. 3B), new values ​​are registered in each column of deletion candidate condition data 171, and a deletion lock C6 is set as necessary. When defining a new job (FIG. 3C), new values ​​are registered in each column of job definition data 141, and if an execution schedule has been determined, new values ​​are also registered in each column of schedule data 121. For job history data 161, only the job name E1 is newly registered. When a job is executed (FIG. 3D), new values ​​are registered in each column of job history data 161 other than the job name, and if the next execution schedule has been determined, the next scheduled execution date and time A2 in schedule data 121 is updated.

[0025] 5 shows examples of deletion candidate conditions described in the deletion candidate condition data 171. Seven examples of deletion candidate conditions are shown here. Each example will be explained below.

[0026] Condition 01: Next schedule not set: It is considered safe to delete a job that has no next execution schedule. Therefore, such a job definition is a candidate for deletion. Specifically, a job for which the next scheduled execution date and time A2 in the schedule data 121 is not set is a candidate for deletion.

[0027] Condition 02: Destination is not a production environment: When testing a job, the job may be executed directly without going through an agent, but once the test is complete, the job is scheduled to be executed through an agent on host 2. Therefore, a job that is actually used in a production environment will also have an agent deployed to execute the job. In other words, a job that does not have an agent deployed can be a candidate for deletion. Specifically, a job for which an agent definition corresponding to the destination C3 does not exist in the agent data 131 is a candidate for deletion.

[0028] Condition 03: One year or more has passed since the last execution: A job that has not been executed for a long period of time is likely to be unnecessary and may be a candidate for deletion. Specifically, if the execution end date and time E3 is more than a predetermined period (for example, more than one year) before the current time, the job is a candidate for deletion.

[0029] Condition 04: Job name does not conform to naming rules: Jobs managed by the job management system 1 often have names that conform to predetermined naming rules for the sake of management convenience. Jobs that violate this rule may not be intended for management by the job management system 1, or may not currently be managed. Therefore, if the job name C1 does not conform to the naming rules, the job becomes a candidate for deletion.

[0030] Condition 05: No job creator: It is assumed that a job definition is created by a user of the job management system 1 or a user of the host 2. A job created by a non-existent user may no longer be in use. Therefore, if the job creator C4 does not exist in the user data 151, the job becomes a candidate for deletion.

[0031] Condition 06: There is no user with job execution authority: When host 2 executes a job, the job is executed under some user authority (when an agent executes a job, the agent itself executes under that user authority). Therefore, if job execution user C5 does not exist in user data 151, the job cannot actually be executed and is therefore a candidate for deletion.

[0032] Condition 07: Unexecuted and more than one year has passed since the last update: A job for which there is no execution history and for which a predetermined period of time (for example, more than one year) has passed since the job definition was last updated is likely to be unnecessary and can be a candidate for deletion. Specifically, a job for which there is no execution history in the job history data 161 and whose definition update date and time C2 is more than one year ago is a candidate for deletion.

[0033] FIG. 6 is a flowchart illustrating the process by which the job management system 1 extracts deletion candidate jobs. The deletion candidate extraction unit 11 acquires all job definitions described in the job definition data 141 (S1). The deletion candidate extraction unit 11 calculates deletion candidate points for each job (S2). The deletion candidate points are points that are assigned to jobs that meet the deletion candidate conditions according to the number of points F2. Details of S2 will be described later. The deletion candidate extraction unit 11 acquires jobs for which a deletion lock C6 has been set (S3). The deletion candidate extraction unit 11 displays the jobs that are deletion candidates and their deletion candidate points on a screen (S4). An example of the screen display will be described later.

[0034] FIG. 7 is a flowchart explaining the details of S2. The deletion candidate extraction unit 11 acquires each record of the deletion candidate condition data 171 (S20). The deletion candidate extraction unit 11 determines whether the job matches each deletion candidate (S21 to S26). In the following, conditions 01 to 07 described in FIG. 5 are used as an example. The same applies to the following. Conditions 03 and 07 described in FIG. 5 have some common parts, so they are determined together as described below. The deletion candidate extraction unit 11 adds up the number of points F2 specified by each of conditions 01 to 07 for each job (S27). For example, if a job matches conditions 01 and 02, the deletion candidate points for that job are the sum of the number of points F2 for condition 01 and the number of points F2 for condition 02.

[0035] 8 is a flowchart explaining the details of S21. The deletion candidate extraction unit 11 acquires the next scheduled execution date and time A2 of each job using the job name A1 of the schedule data 121 as a key (S211). If the next scheduled execution date and time A2 has not been set (S212: not set), the job satisfies condition 01 (S213), and so the number of points F2 for condition 01 is added to the job (S214). If the next scheduled execution date and time A2 has been set (S212: set), the job does not satisfy condition 01 (S215).

[0036] 9 is a flowchart explaining the details of S22. The deletion candidate extraction unit 11 acquires the execution destination C3 of each job using the job name C1 of the job definition data 141 as a key, and further identifies the host 2 that executes the agent by referring to the agent data 131 (host name B2 and IP address B3) using the execution destination C3 as a key (S221). The deletion candidate extraction unit 11 determines whether the identified host 2 is located in an actual operation environment (a production environment, not a test environment used only during testing) (S222). If the identified host 2 is in a test environment (S222: test environment), the job satisfies condition 02 (S223), and therefore adds the number of points F2 for condition 02 to the job (S224). If it is in a production environment, the job does not satisfy condition 02 (S225).

[0037] In S222, whether or not the agent is deployed in the actual operation environment can also be determined by whether or not a record corresponding to the execution destination C3 exists in the agent data 131. If it does not exist, it is considered that the agent does not exist during actual operation (i.e., exists only in a temporary environment such as a test environment).

[0038] 10 is a flowchart explaining the details of S23. The deletion candidate extraction unit 11 acquires the current date and time, and also acquires the execution date and time (either the execution start date and time E2 or the execution end date and time E3) of each job from the job history data 161 (S231). If there is no execution date and time (S232: No), it determines whether condition 07 is met in S233 to S236. If there is an execution date and time (S232: Yes), it determines whether condition 03 is met in S237 to S239. The absence of an execution date and time means that none of the execution start date and time E2, execution end date and time E3, and execution result E4 exist for that job.

[0039] In S233, the deletion candidate extraction unit 11 acquires the definition update date and time C2. If the definition update date and time C2 is a predetermined period or more ago (for example, one year or more) (S234: one year or more ago), the job is deemed to meet condition 07, and the number of points F2 for condition 07 is added to the job (S235). If the difference between the definition update date and time C2 and the current time is less than one year (S234: less than one year), the job is deemed not to meet condition 07 (S236).

[0040] In S237, the deletion candidate extraction unit 11 determines whether the execution date and time acquired in S232 is a predetermined period or more ago (for example, one year or more). If it is one year or more ago (S237: one year or more ago), the job is deemed to meet condition 03, and the number of points F2 for condition 03 is added to the job (S238). If the difference between the execution date and time and the current time is less than one year (S237: less than one year), the job does not meet condition 03 (S239).

[0041] FIG. 11 is a flowchart explaining the details of S24. The deletion candidate extraction unit 11 acquires the job name C1 from the job definition data 141 for each job (S241). The deletion candidate extraction unit 11 further acquires the naming rule from the extraction condition F5 of condition 04. The naming rule can be defined, for example, by a regular expression. The deletion candidate extraction unit 11 determines whether the job name C1 complies with the naming rule (S242). If the job does not comply with the naming rule (S242: Not Compliant), the job falls under condition 04 (S243), and the number of points F2 for condition 04 is added to the job (S244). If the job complies with the naming rule (S242: Compliant), the job does not fall under condition 04 (S245).

[0042] 12 is a flowchart explaining the details of S25. The deletion candidate extraction unit 11 acquires the job creator C4 of the job definition data 141 for each job (S251). The deletion candidate extraction unit 11 queries the user data 151 using the job creator C4 as a key, and determines whether a corresponding user name D1 exists (S252). If the corresponding user name D1 does not exist (S252: does not exist), the job satisfies condition 05 (S253), and the number of points F2 for condition 05 is added to the job (S254). If the corresponding user name D1 exists (S252: exists), the job does not satisfy condition 05 (S255).

[0043] 13 is a flowchart explaining the details of S26. The deletion candidate extraction unit 11 acquires the job executing user C5 of the job definition data 141 for each job (S261). The deletion candidate extraction unit 11 determines whether or not a user who executes the job exists by querying the user data 151 using the job executing user C5 as a key (S262). If the user does not exist (S262: no), the job satisfies condition 06 (S263), and the number of points F2 for condition 06 is added to the job (S264). If the user exists (S262: yes), the job does not satisfy condition 06 (S265).

[0044] In S262, if there is no record corresponding to the job creator C4 in the user data 151, it means that there is no user who can execute the job. Even if the user itself exists, if the authority D2 is not sufficient to execute the job, it also means that there is no user who can execute the job. The level of authority required to execute a job can be determined based on the nature of the authority D2, for example, "administrator" and "general user" have authority, but "guest" does not have authority. Alternatively, the authority required for each job may be defined separately.

[0045] <First embodiment: Summary> The job management system 1 according to the first embodiment extracts jobs to be deleted from the job definition data 141 according to the conditions described in the deletion candidate condition data 171, and assigns points corresponding to the extraction conditions to the jobs. This makes it possible to efficiently extract jobs that may no longer be necessary, and to give the user an opportunity to decide whether or not to delete the extracted deletion candidate jobs. By giving the user an opportunity to make a decision, it is possible to avoid accidentally deleting a deletion candidate job even in cases where the deletion candidate job is actually a necessary job.

[0046] <Embodiment 2> In the second embodiment of the present invention, an example of a user interface provided by the job management system 1 will be described. The other configurations are the same as those of the first embodiment.

[0047] FIG. 14 is an example of a user interface provided by the job management system 1. The user can edit the deletion candidate condition data 171 using a user interface such as that shown in FIG. 14 provided by the job management system 1 (for example, the deletion candidate extraction unit 11). Existing deletion candidate conditions (each record in the deletion candidate condition data 171) can be edited, and new deletion candidate conditions can also be added. When adding new deletion candidate conditions, the user specifies one of the columns described in FIGS. 2A to 2E (schedule data 121 to job history data 161) on the user interface and inputs the deletion candidate conditions specified by that column. This allows any deletion candidate condition using any column to be added.

[0048] FIG. 15 is an example of a user interface provided by the job management system 1. In S4, the job management system 1 (for example, the deletion candidate extraction unit 11) can present a user interface such as that shown in FIG. 15. A list of jobs that meet the deletion candidate conditions is displayed on the screen, along with their deletion candidate points. It is also displayed which of conditions 01 to 07 the job meets. Jobs for which a deletion lock C6 has been set are marked with a lock icon indicating this. When the user presses the "Delete" button at the bottom right of the screen, the job management system 1 (deletion candidate extraction unit 11) deletes from the job definition data 141 the jobs that the user has checked using the checkboxes on the left side of the screen. However, jobs for which a deletion lock C6 has been set cannot be checked, or are not deleted even if checked.

[0049] In Figure 15, when a large number of jobs are displayed as candidates for deletion, it is possible to filter them so that only a portion of them are displayed. For example, if you click on the downward triangle next to "Candidate for deletion P," a popup will appear in which you can enter the threshold value for the deletion candidate points. When the user enters the threshold, only jobs with points above (or below) that threshold will be extracted, and the other jobs will be filtered out, and the screen will be redisplayed. Other items can also be filtered in the same way.

[0050] The job management system 1 (deletion candidate extraction unit 11) may automatically delete a job whose deletion candidate points have reached a predetermined threshold value or more, even if the user does not press the "Delete" button on the screen of Fig. 15. The threshold value may be specified by the user on an arbitrary user interface, for example, or may be recorded in data saved in the job management system 1.

[0051] <Modifications of the present invention> In the above embodiment, conditions 01 to 07 have been described as examples of extraction conditions for deletion candidate jobs, but the extraction conditions are not limited to these. A job that is a deletion candidate is one that is assumed to no longer be used in the environment in which the job is operated. Therefore, extraction conditions similar to conditions 01 to 07 can be used as long as they can extract jobs that are assumed to have a usage frequency below a threshold because they do not conform to the operation rules in the job's actual operation environment.

[0052] In the above embodiment, it has been explained that the user data 151 describes a user of the job management system 1 or a user of the host 2. For example, if these users can log in to the job management system 1, they can be considered to be users of the job management system 1, and if they can log in to the host 2, they can be considered users of the host 2. In other words, it should be noted that even if the user account itself is defined in an account management system other than these, they can be considered to be users of the job management system 1 or users of the host 2.

[0053] In the above embodiments, each functional unit (e.g., deletion candidate extraction unit 11) provided in job management system 1 can be configured by hardware such as a circuit device that implements the function, or can be configured by a computing device such as a CPU (Central Processing Unit) executing software that implements the function. [Explanation of symbols]

[0054] 1: Job management system 11: Deletion candidate extraction unit 121: Schedule data 131: Agent Data 141: Job definition data 151: User data 161: Job history data 171: Deletion candidate condition data

Claims

1. A job management system for managing jobs executed by a computer, comprising: a job definition data management unit that stores job definition data describing the job definition; a deletion candidate extraction unit that extracts deletion candidate jobs that are candidates to be deleted from the jobs described in the job definition data; a deletion candidate condition data management unit that stores deletion candidate condition data describing conditions under which the deletion candidate extraction unit extracts the deletion candidate jobs; Equipped with The deletion candidate condition data describes the conditions and a point indicating the degree to which the job that matches the conditions should be deleted, the deletion candidate extraction unit extracts the jobs that meet the conditions from the job definition data as deletion candidate jobs, and assigns the points corresponding to the conditions to the extracted jobs; The deletion candidate extraction unit presents the extracted jobs and the points assigned to the jobs. A job management system characterized by:

2. the condition is configured to be able to extract the job whose frequency of use is assumed to be equal to or less than a reference value because it does not conform to an operation rule for the job in an environment in which the computer is operated, The deletion candidate extraction unit extracts the jobs that meet the conditions, and thereby extracts the jobs whose frequency of use in the environment is assumed to be equal to or less than a reference value as the deletion candidate jobs.

2. The job management system according to claim 1.

3. The job management system further includes a schedule data management unit that stores schedule data describing an execution schedule of the job, The deletion candidate condition data describes, as the condition, that the job whose next execution schedule is not described in the schedule data is to be the deletion candidate job, The deletion candidate extraction unit extracts the job whose next execution schedule is not described in the schedule data as the deletion candidate job.

2. The job management system according to claim 1.

4. The job management system further includes an agent data management unit that stores agent data describing definitions of agents that execute the jobs, the job definition data describes an identifier of the agent that executes the job; the deletion candidate condition data describes, as the condition, that the job in which the agent described in the job definition data is not described in the agent data is the deletion candidate job; The deletion candidate extraction unit extracts, as the deletion candidate job, the job in which the agent described in the job definition data is not described in the agent data.

2. The job management system according to claim 1.

5. The job management system further includes a job history data management unit that stores job history data describing an execution history of the job, The deletion candidate condition data describes, as the condition, that the job whose last execution date and time is more than a predetermined time ago is to be the deletion candidate job, The deletion candidate extraction unit extracts, as the deletion candidate job, the job whose last execution date and time is more than a predetermined time ago.

2. The job management system according to claim 1.

6. The job definition data describes the name of the job, The deletion candidate condition data describes, as the condition, that the job whose name does not conform to a naming rule is to be the deletion candidate job, and the naming rule; The deletion candidate extraction unit extracts the job whose name does not match the naming rule as the deletion candidate job.

2. The job management system according to claim 1.

7. The job management system further includes a user data management unit that stores user data describing definitions of at least one of a user of the job management system or a user of the computer, the job definition data describes an identifier of the user who created the job, the deletion candidate condition data describes, as the condition, that the job whose user described in the job definition data is not described in the user data is to be the deletion candidate job; The deletion candidate extraction unit extracts, as the deletion candidate job, the job in which the user described in the job definition data is not described in the user data.

2. The job management system according to claim 1.

8. the job management system further comprises a user data management unit for storing user data describing the authority of at least one of a user of the job management system or a user of the computer; the job definition data describes an identifier of the user who executes the job; The deletion candidate condition data describes, as the conditions, that the job described in the job definition data is a job for which a user who executes the job is not described in the user data, and that the job described in the job definition data is a job for which the user who executes the job does not have authority to execute the job, The deletion candidate extraction unit extracts, as the deletion candidate job, a job for which a user who executes the job described in the job definition data is not described in the user data, and extracts, as the deletion candidate job, a job for which a user who executes the job described in the job definition data does not have authority to execute the job.

2. The job management system according to claim 1.

9. The job management system further includes a job history data management unit that stores job history data describing an execution history of the job, the job definition data describes the last update date and time of the job definition, The deletion candidate condition data describes, as the condition, that the job whose execution history is not described in the job history data and whose last update date and time is more than a predetermined time ago is to be the deletion candidate job, The deletion candidate extraction unit extracts, as the deletion candidate job, the job for which no execution history is described in the job history data and whose last update date and time is more than a predetermined time ago.

2. The job management system according to claim 1.

10. the job definition data describes deletion lock information that specifies the job that should not be deleted from the job definition data even if the job satisfies the condition; Even when the job management system executes a process of deleting the job that matches the condition from the job definition data, the job for which the deletion lock information is specified is not deleted from the job definition data.

2. The job management system according to claim 1.

11. the job management system provides a user interface that is used by a user to specify the conditions; The deletion candidate condition data management unit stores the conditions specified in the user interface as the deletion candidate condition data.

2. The job management system according to claim 1.

12. The job management system provides a user interface for presenting the points.

2. The job management system according to claim 1.

13. If the assigned points are equal to or greater than a threshold, the job management system deletes the job from the job definition data without a user instruction to delete the job.

2. The job management system according to claim 1.

Images