WO2015132904A1 - 情報処理方法及び情報処理システム - Google Patents
情報処理方法及び情報処理システム Download PDFInfo
- Publication number
- WO2015132904A1 WO2015132904A1 PCT/JP2014/055628 JP2014055628W WO2015132904A1 WO 2015132904 A1 WO2015132904 A1 WO 2015132904A1 JP 2014055628 W JP2014055628 W JP 2014055628W WO 2015132904 A1 WO2015132904 A1 WO 2015132904A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- job
- execution
- generation file
- identifier
- generation
- Prior art date
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/466—Transaction processing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/006—Identification
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1415—Saving, restoring, recovering or retrying at system level
- G06F11/1438—Restarting or rejuvenating
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
- G06F9/5011—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resources being hardware resources other than CPUs, Servers and Terminals
Definitions
- the present invention relates to an information processing method and an information processing system, and is suitable for application to an information processing system equipped with a generation management file function.
- a function that manages a series of files having a temporal relationship with each other as a group, such as a relationship between an old file and a new file that are sequentially updated, such as a salary file and an inventory file, is called a generation file function.
- this group is referred to as a generation group, and individual files constituting the generation group are referred to as generation files.
- the conventional generation file function does not manage which generation file is created by which job. Therefore, when a job is re-executed, the next generation file is unconditionally created regardless of whether the job has already output a generation file.
- the present invention has been made in consideration of the above points, and reduces the cost of post-processing of illegal generation files accompanying job errors and correction of job execution plans, and reduces the time to complete processing consisting of a series of jobs.
- the present invention intends to propose an information processing method and an information processing system that can be shortened.
- an information processing method in an information processing system for creating a next generation file by executing a job with the latest generation file as an input wherein the information processing system includes: A job management unit that manages the registered job; and a job execution unit that executes the specified job based on an execution request of the job from the job management unit.
- the registered job is managed in association with an identifier unique to the job, and the job execution request and the identifier associated with the job are notified to the job execution unit at the execution date of the job.
- the first step and the job execution unit designated by the job management unit based on the job execution request from the job management unit And a second step of managing the next generation file created by executing the job in association with the identifier notified from the job management unit together with the job execution request.
- the generation file associated with the identifier notified together with the execution request is Check whether the generation file already exists. If the generation file does not exist, execute the specified job. If the generation file already exists, execute the specified operation. did.
- an information processing system that executes a job with the latest generation file as an input and creates a next generation file, a job management unit that manages the registered job, and the job management A job execution unit that executes the specified job based on a job execution request from a job unit, and the job management unit manages the registered job in association with an identifier unique to the job
- the job execution unit notifies the job execution unit of the job execution request and the identifier associated with the job at the execution date of the job, and the job execution unit creates the next
- the generation file of the generation is managed in association with the identifier notified from the job management unit together with the job execution request, and the job management
- the designated job is executed, while if the generation file already exists, the designated operation is executed.
- reference numeral 1 denotes an information processing system according to this embodiment as a whole.
- the information processing system 1 includes a client device 3 and a batch server 4 connected via a communication path 2 such as a cable or a network.
- the client device 3 is a computer device that manages a series of jobs constituting one process registered by the user and instructs the batch server 4 to execute the job at the execution date and time of any job.
- the client device 3 includes a CPU (Central Processing Unit) 11, a memory 12, a storage device 13, an input device 14, and a display device 15 connected to each other via an internal bus 10.
- CPU Central Processing Unit
- the CPU 11 is a processor that controls the operation of the entire client device 3.
- the memory 12 is composed of, for example, a volatile semiconductor memory and is used as a work memory for the CPU 11.
- a job management table 16 and a client-side scheduler 17 to be described later are stored and held in the memory 12.
- the storage device 13 is composed of, for example, a hard disk device, and is used for holding programs and data for a long time.
- the program stored in the storage device 13 is read into the memory 12 when the client device 3 is activated or necessary, and is executed by the CPU 10, whereby various processes as the entire client device 3 are executed.
- the input device 14 includes a keyboard and a mouse, and is used when, for example, the user creates a series of job execution schedules.
- the display device 15 is composed of a liquid crystal panel display or the like, and displays various GUIs (Graphical User Interface) and various necessary information in accordance with instructions from the CPU 11.
- the batch server 4 is a server device that executes a specified batch process with the latest generation file as an input in response to a request from the client device 3, and includes a CPU 20, a memory 21, and a storage device 22. . Since the CPU 20, the memory 21, and the storage device 22 have the same configuration and functions as the CPU 11, the memory 12, and the storage device 13 of the client device 3, description thereof is omitted here.
- the memory 21 of the batch server 4 stores a server-side scheduler 23 and an execution control unit 24, which will be described later, and a program 25 for each job as programs, and a job definition file 26 as control data.
- the job definition file 26 is a job for each job such as a program 25 to be started when executing a job, a generation file to be input when executing the job, and a generation file to output the processing result of the job.
- Each file has a defined content.
- the job definition file 26 for each job, there is already a generation file in which the processing result of the job is recorded (that is, the generation file created when the job was re-executed and the job was executed last time).
- the operation of the batch server 4 is recorded in advance.
- the storage device 22 of the batch server 4 stores a generation file 27 for each generation in which the processing result of the batch processing is recorded and a generation management file 28 used for managing the generation file 27 of each generation. Is done. Details of the generation management file 28 will be described later.
- FIG. 2 shows a logical configuration of the client device 3 and the batch server 4.
- a client-side scheduler 17 is mounted on the client device 3
- a server-side scheduler 23 an execution control unit 24, and a program 25 are mounted on the batch server 4.
- the client-side scheduler 17 is a program having a function of managing a series of jobs registered by a user, and displays a predetermined GUI screen for registering a job in response to a user operation on the display device and uses the GUI.
- the job registered by the user is stored in the job management table 16 and managed.
- the job management table 16 includes a job name column 16A, a job number column 16B, and an execution date / time column 16C.
- the job name column 16A stores a name (job name) given by the user to the registered job
- the execution date / time column 16C stores the scheduled execution date / time of the corresponding job.
- the job number assigned by the client-side scheduler 17 when the corresponding job is registered is stored.
- the job number is an identification number unique to the job that is set based on the job name and execution date of the registered job. If the execution date is different even if the same job is executed multiple times, Different job numbers are assigned. The job number is not changed when the job is re-executed.
- the client-side scheduler 17 obtains a request for starting the job (hereinafter referred to as a job start request) and the job number of the job. It transmits to the server side scheduler 23 of the batch server 4.
- the server-side scheduler 23 is a program having a function of mediating exchange of commands and information between the client-side scheduler 17 of the client device 3 and the execution control unit 24 of the batch server 4.
- the server side scheduler 23 receives the job activation request and the job number from the client side scheduler 17, the server side scheduler 23 transfers them to the execution control unit 24.
- the execution control unit 24 is a program having a function of controlling execution of a designated job in response to a job activation request from the client-side scheduler 17. Upon receiving the job activation request and the job number transferred from the server-side scheduler 23, the execution control unit 24 refers to the job definition file 26, and a program 25 to be activated to execute the designated job, The generation file 27 to be input and the generation file 27 to be output in the job and the operation when the generation file 27 corresponding to the notified job number already exists are determined.
- the execution control unit 24 refers to the generation management file 28 stored in the storage device 22 and determines whether or not a generation file 27 of a generation corresponding to the job number notified from the client-side scheduler 17 has already been created. Confirm.
- the generation management file 28 is a file used by the execution control unit 24 to manage the generation file 27 of each generation that has already been created and stored in the storage device 22.
- a table 29 including a generation number column 29A, a file name column 29B, and a job number column 29C is recorded.
- the generation number column 29A of the table 29 a number (generation number) assigned to the corresponding generation is stored.
- the generation number is set to “1” for the latest generation, and a value obtained by sequentially adding “1” to the generation number of the latest generation every time one generation is older than the previous generation. Is granted.
- the file name column 29B stores the file name assigned to the generation file 27 in which the processing result of the corresponding generation is recorded, and the job number column 29C assigns it to the job processing of the corresponding generation. Stores the job number.
- the execution control unit 24 searches the generation management file 28 for the job number notified from the client side scheduler 17 (SP1), and if the job number cannot be detected (that is, When the generation file 27 corresponding to the job number does not exist), it is determined that the job is not re-executed, the generation file 27 of the generation is created, and the created generation file 27 is stored in the storage device 22. (SP2) The corresponding program 25 is activated (SP3).
- the program 25 activated by the execution control unit 24 executes the corresponding batch process, and records the process result in the generation file 27 newly created as described above (SP4). Further, when the batch processing ends, the program 25 transmits a code to that effect (hereinafter referred to as a job end code) to the execution control unit 24 (SP5).
- a job end code a code to that effect
- the execution control unit 24 updates the generation management file 28 (SP6), and sends the job end code to the client side scheduler 17 (FIG. 2) via the server side scheduler 23 (FIG. 2). ) (SP7).
- the execution control unit 24 detects the job number notified from the client-side scheduler 17 on the generation management file 28 (that is, when the generation file 27 corresponding to the job number already exists). Then, it is determined that the job is re-executed, and the operation defined in the job definition file 26 (“overwrite”, “save”, or “cancel”) is executed as the operation in that case.
- the execution control unit 24 notifies the client side scheduler 17 on the generation management file 28 as shown in FIG.
- the generated job number is detected (SP10), if the operation is “overwrite”, the generation file 27 corresponding to the job number is deleted from the storage device 22, and then a new one corresponding to the generation of the job number. If the generation file 27 is created and stored in the storage device 22 and the operation is “save”, the generation file 27 corresponding to the job number stored in the storage device 22 is saved, A new generation file 27 corresponding to the generation of the job number is created and stored in the storage device 22 (SP11). Thereafter, the execution control unit 24 starts the corresponding program 25 (SP12).
- the program 25 activated by the execution control unit 24 executes the corresponding batch process, and records the process result in the generation file 27 newly created as described above (SP13). Further, when the batch processing ends, the program 25 transmits a code to that effect (hereinafter referred to as a job end code) to the execution control unit 24 (SP14).
- a job end code a code to that effect
- the execution control unit 24 updates the generation management file 28 (SP15) and transmits the job end code to the client side scheduler 17 via the server side scheduler 23 (SP16).
- the information processing system 1 performs the operation of the batch server 4 when the generation file 27 is already re-executed in the storage device 22 of the batch server 4 as described above.
- a function designated by the user hereinafter referred to as a user response function is also installed.
- a message (hereinafter referred to as a response request message) is transmitted to the client device 3 via the server-side scheduler 23.
- the client-side scheduler 17 of the client apparatus 3 that has received this response request message should execute any one of “overwrite”, “save”, and “cancel” as the subsequent operation of the batch server 4.
- 9 and 10 are displayed on the display device 15 (FIG. 1).
- the client-side scheduler 17 indicates the designated operation when the user designates an operation to be executed by the batch server 4 at that time using the first operation confirmation window 40 or the second operation confirmation window 50.
- a message (hereinafter referred to as a response message) is transmitted to the batch server 4.
- this response message is given to the execution control unit 24 via the server-side scheduler 23 in the batch server 4. Then, if the operation is “overwrite” or “save”, the execution control unit 24 that has received this response message executes the processing after step SP11 of the series of processing described above with reference to FIG. When the operation is “stop”, the processing after step SP21 of the series of processing described above with reference to FIG. 7 is executed.
- FIG. 8 shows the display device 15 of the client device 3 when the batch server 4 is executing processing consisting of a series of jobs in the information processing system 1 of the present embodiment.
- a screen name display bar 31 and a tool bar 32 are provided at the upper part of the screen.
- a job group name display unit 33 is displayed on the lower left side of the tool bar 32, and a job net is displayed on the lower right side.
- Each part 34 is provided.
- job group name display section 33 the name (job group name) assigned to the job group consisting of a series of jobs executed in the batch server 4 at that time is displayed.
- job marks 35 in which the job names of these jobs are displayed in correspondence with the jobs belonging to the job group are displayed on the left in the order of execution. Are arranged side by side to the right, and an arrow 36 directed to the right is displayed between the job marks 35.
- the job mark 35 corresponding to the job for which processing has been completed, or the color of the job mark 35 corresponding to the job for which processing has been stopped or stopped, corresponds to the job for which processing has not been completed.
- the mark 35 is displayed in a different color.
- the job details list 37 includes a unit name column 37A, a comment column 37B, a type column 37C, a status column 37D, a delay status column 37E, and the like.
- the job name of each job belonging to the job group whose name is displayed is displayed in the unit name column 37A.
- the comment field 37B displays information about the corresponding job input in advance (for example, “generation file output” in the case of a job that outputs the generation file 27), and the type field 37C displays the type of the corresponding job. Is displayed. Further, the status column 37D displays the status of the corresponding job (such as “normal end”, “stop”, or “wait”), and the delay status column 37E displays information related to the delay status of the corresponding job. .
- the job group currently being executed by the batch server 4 is “job group A”, and “job group A” is “job A”, “job B”, “job C”. It is shown that the generation file 27 is output (“generation file output”) when “job C” is completed.
- generation file output is output when “job C” is completed.
- FIG. 8 among “Job A” to “Job D”, “Job A” and “Job B” have already been processed normally (“normal end”). It is shown to be in a “stopped” state.
- FIG. 8 shows a job when the user response function is turned on in the job definition file 26 and when it is confirmed that the generation file 27 of the corresponding generation already exists when “job C” is executed.
- a display example of the net screen 30 is shown.
- a first operation confirmation window 40 as shown in FIG. 9 is displayed on the display device 15 of the client device 3 so as to overlap the job net screen 30.
- the generation file 27 corresponding to the job in the stop state already exists (“the generation file corresponding to the job number XXX already exists”)
- a message asking whether to continue the job (“Do you want to continue?”) Is displayed, and the job number of the job and the file name of the existing generation file are also displayed.
- a continue button 41 and a stop button 42 are displayed.
- the user can specify “stop” as the subsequent operation of the batch server 4 by clicking the stop button 42, and “continue” as the subsequent operation of the batch server 4 by clicking the continue button 41. "(That is,” overwrite “or” save ") can be specified.
- a second operation confirmation window 50 as shown in FIG. 10 is displayed on the job net screen 30 in place of the first operation confirmation window 40.
- the processing result of the job is overwritten on the existing corresponding generation file, or the existing generation file is saved and written to a new generation file.
- Message (“Do you want to overwrite the generation file corresponding to job number XXX? Do you want to save and create a new file?") And the job number of the job and the existing generation file? The file name is also displayed.
- an overwrite button 51 and a save button 52 are displayed.
- the user can specify “overwrite” as the subsequent operation of the batch server 4 by clicking on the overwrite button 51, and “retreat” as the subsequent operation of the batch server 4 by clicking the save button 52. Can be specified.
- FIG. 11 shows a processing procedure of job start processing executed by the client side scheduler 17 (FIG. 2). In the following, the processing for displaying the job net screen 30 described above with reference to FIG. 8 is omitted.
- the client-side scheduler 17 starts the job activation process shown in FIG.
- the job number read from the table 16 is transmitted to the batch server 4 together with the job activation request (SP30).
- the client-side scheduler 17 waits for a job end code or a response request message to be transmitted from the batch server 4 (SP31, SP32).
- the client-side scheduler 17 receives the response request message (SP32: YES)
- the first operation confirmation window 40 described above with reference to FIG. 9 and, if necessary, the second operation confirmation window 50 described with reference to FIG. Is displayed on the display device 15 (FIG. 1) to accept an operation input from the user (SP33).
- the client-side scheduler 17 sends a response message indicating the operation of the designated batch server 4. Is transmitted to the batch server 4 (SP34), and then the process returns to step SP31.
- the client-side scheduler 17 eventually receives the job end code from the batch server 4 (SP31: YES), the job start processing is ended.
- FIG. 12 shows job management processing executed by the server-side scheduler 23 (FIG. 2) of the batch server 4 that has received the job activation request and job number from the client-side scheduler 17. The processing procedure of is shown.
- the server-side scheduler 23 Upon receiving the job activation request and job number, the server-side scheduler 23 starts the job management process shown in FIG. 12, and first transfers the received job activation request and job number to the execution control unit 24 (SP40). .
- the server-side scheduler 23 waits for a job end code or a response request message to be transmitted from the execution control unit 24 (SP41, SP42).
- the server-side scheduler 23 receives the response request message from the execution control unit 24 (SP42: YES)
- the server-side scheduler 23 transfers the response request message to the client device 3 (SP43).
- the server-side scheduler 23 waits for the above-described response message (step SP34 in FIG. 11) to be transmitted from the client device 3 (SP44).
- the server-side scheduler 23 eventually receives this response message (SP44: YES)
- the server-side scheduler 23 transfers this response message to the execution control unit 24 (SP45), and then returns to step SP41.
- the server-side scheduler 23 When the server-side scheduler 23 eventually receives the job end code from the execution control unit 24 (SP41: YES), the server-side scheduler 23 transfers the received job end code to the client-side scheduler 17 of the client device 3 (SP46). This job management process is terminated.
- FIG. 13A and FIG. 13B show the processing procedure of the job execution control process executed by the execution control unit 24 that has received the job activation request and job number from the server-side scheduler 23. Show.
- the execution control unit 24 When receiving the job activation request and the job number, the execution control unit 24 starts the job execution control process shown in FIGS. 13A and 13B, first reads the job definition file 26 (SP51), and reads the read job definition file. 26, the generation file that outputs the processing result of the batch processing and the operation (overwriting, saving or canceling or user response) when the generation file exists are determined (SP52).
- the execution control unit 24 reads the generation management file 28 (FIG. 4) (SP53), and searches the generation management file 28 for the job number notified from the server side scheduler 23 (SP54). Then, the execution control unit 24 determines whether or not the generation file 27 corresponding to the job number notified from the server side scheduler 23 already exists based on the search result (SP55).
- execution control unit 24 determines the file name of the generation file 27 corresponding to the job number notified from the server-side scheduler 23 based on the job number (SP63), and the determined file A name generation file 27 is created (SP64).
- the execution control unit 24 starts the corresponding program 25 in accordance with the job start request from the server side scheduler 23 (SP65), and then waits to receive a job end code from the program 25 (SP66).
- the program 25 started at this time executes the corresponding job, and when the job ends, the processing result is recorded in the generation file 27 created in step SP64 and the job end code is stored in the execution control unit 24. Send.
- the execution control unit 24 Upon receiving the job end code from the program 25, the execution control unit 24 newly registers the generation file 27 created in step SP64 in the generation management file 28, sets the generation number of the generation file 27 to “1”, and The generation management file 28 is updated so that the generation number of the generation file 27 of the generation older than the generation file 27 is shifted to a larger value by “1”, and the job number assigned to the job processing of the corresponding generation is registered. (SP67).
- the execution control unit 24 transfers the job end code from the program 25 received in step SP66 to the server side scheduler 23 (SP68), and thereafter ends this job execution control process.
- the execution control unit 24 obtains a positive result in the determination at step SP55, it refers to the job definition file 26 read at step SP50 to determine whether or not the user response function is turned on (SP56). ).
- execution control unit 24 If the execution control unit 24 obtains a positive result in this determination, it transmits a response request message to the server-side scheduler 23 (SP57), and then waits to receive a response message from the client-side scheduler 17 (SP58). ).
- the execution control unit 24 determines whether the operation specified in the response message is “overwrite” or “save”. (SP59).
- the execution control unit 24 transmits a job end code indicating that the corresponding job is canceled to the server-side scheduler 23 (SP68), and thereafter ends this job execution control processing.
- a message indicating that the corresponding job is canceled is displayed on the display device 15 of the client device 3.
- the execution control unit 24 determines whether the operation designated by the user is “overwrite” based on the response message received at step SP58. (SP60).
- the execution control unit 24 If the execution control unit 24 obtains a positive result in this determination, it deletes the generation file 27 corresponding to the job number notified from the client-side scheduler 17 and stored in the storage device 22 (FIG. 2) at that time. (SP61). Then, the execution control unit 24 thereafter processes step SP63 and subsequent steps as described above, and thereafter ends the job execution control process.
- obtaining a negative result in the determination at step SP60 means that the operation designated by the user was “evacuation”.
- the execution control unit 24 separates the job number notified from the client-side scheduler 17 and the corresponding generation file 27 stored in the storage device 22 at that time from the job number (SP62). Specifically, the execution control unit 24 changes the file name of the generation file 27 and deletes the entry (row) corresponding to the generation file 27 in the generation management file 28. Then, the execution control unit 24 thereafter processes step SP63 and subsequent steps as described above, and thereafter ends the job execution control process.
- the job definition file 26 operates as an operation when the generation file 27 associated with the job number notified from the client-side scheduler 17 already exists. It is determined whether or not the set operation is “overwrite” or “save” (SP59).
- the execution control unit 24 If the execution control unit 24 obtains a negative result in this determination, it sends a job end code indicating that the corresponding job has been canceled to the server-side scheduler 23 (SP68), and then ends this job execution control process. . As a result, in this case, a message indicating that the corresponding job is canceled is displayed on the display device 15 of the client device 3.
- the job definition is defined as an operation when the generation file 27 associated with the job number notified from the client-side scheduler 17 already exists. It is determined whether or not the operation set in the file 26 is “overwrite” (SP60).
- the execution control unit 24 If the execution control unit 24 obtains a positive result in this determination, it deletes the generation file 27 corresponding to the job number notified from the client-side scheduler 17 and stored in the storage device 22 (FIG. 2) at that time. (SP61). Then, the execution control unit 24 thereafter processes step SP63 and subsequent steps as described above, and thereafter ends the job execution control process.
- obtaining a negative result in the determination at step SP60 means that the operation designated by the user was “evacuation”.
- the execution control unit 24 separates the generation file 27 corresponding to the job number notified from the client-side scheduler 17 and stored in the storage device 22 at that time from the job number (SP62). Then, the execution control unit 24 thereafter processes step SP63 and subsequent steps as described above, and thereafter ends the job execution control process.
- the batch server 4 uses the job number assigned to each job and the generation file 27 created by the job. It is determined whether or not the generation file 27 associated with the job number assigned to the job when the job is executed has already been created and the generation file 27 already exists. Are defined in advance in the job definition file 26 or execute an operation designated by the user.
- the information processing system 1 it is possible to prevent a new generation file 27 from being unconditionally created by re-execution of a job, and post-processing or job execution of an illegal generation file accompanying a job error. It is possible to reduce the time until the completion of the processing consisting of a series of jobs by eliminating the cost of correcting the plan.
- a function as a job management unit for managing registered jobs is installed in the client device 3, and a job from the job management unit (client device 3) is loaded.
- client device 3 a job from the job management unit
- job management unit for executing a specified job based on an execution request
- the present invention is not limited to this, and the function as the job management unit is provided. All of the functions as the job execution unit may be installed in the batch server 4.
- a number (job number) is assigned as an identifier to each job.
- the present invention is not limited to this, and instead of a number (job number).
- an alphabet may be applied as an identifier for each job, or a combination of alphabets and numbers may be applied as an identifier for each job.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- Software Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Debugging And Monitoring (AREA)
- Stored Programmes (AREA)
Abstract
Description
図1において、1は全体として本実施の形態による情報処理システムを示す。この情報処理システム1は、ケーブル又はネットワーク等の通信路2を介して接続されたクライアント装置3及びバッチサーバ4から構成される。
図8は、本実施の形態の情報処理システム1において、バッチサーバ4が一連のジョブからなる処理を実行している場合にクライアント装置3の表示装置15に表示されるジョブネット画面30の構成を示す。
次に、上述のようなバッチ処理に関連して実行される各種処理の具体的な処理内容について説明する。なお以下においては、「プログラム」を各種処理の処理主体として説明するが、その処理は、その「プログラム」に基づいてクライアント装置3のCPU11や、バッチサーバ4のCPU20がその処理を実行することは言うまでもない。
図11は、クライアント側スケジューラ17(図2)により実行されるジョブ起動処理の処理手順を示す。以下においては、図8について上述したジョブネット画面30を表示するための処理については省略する。
一方、図12は、クライアント側スケジューラ17からのジョブ起動要求及びジョブ番号を受信したバッチサーバ4のサーバ側スケジューラ23(図2)により実行されるジョブ管理処理の処理手順を示す。
他方、図13A及び図13Bは、サーバ側スケジューラ23からのジョブ起動要求及びジョブ番号を受信した実行制御部24により実行されるジョブ実行制御処理の処理手順を示す。
以上のように本実施の形態の情報処理システム1では、バッチサーバ4において、各ジョブにそれぞれ付与されたジョブ番号と、ジョブにより作成された世代ファイル27とを対応付けて管理し、ジョブを実行する際に当該ジョブに付与されたジョブ番号と対応付けられた世代ファイル27が既に作成されているか否かを判定し、当該世代ファイル27が既に存在する場合には、ジョブ定義ファイル26において予め定義され、又は、ユーザにより指定された動作を実行する。
なお上述の実施の形態においては、登録されたジョブを管理するジョブ管理部としての機能をクライアント装置3に搭載し、ジョブ管理部(クライアント装置3)からのジョブの実行要求に基づいて、指定されたジョブを実行するジョブ実行部としての機能をバッチサーバ4に搭載するようにした場合について述べたが、本発明はこれに限らず、かかるジョブ管理部としての機能及びジョブ実行部としての機能のすべてをバッチサーバ4に搭載するようにしても良い。
Claims (8)
- 最新世代の世代ファイルを入力としてジョブを実行することにより次世代の世代ファイルを作成する情報処理システムにおける情報処理方法であって、
前記情報処理システムは、
登録された前記ジョブを管理するジョブ管理部と、
前記ジョブ管理部からの前記ジョブの実行要求に基づいて、指定された前記ジョブを実行するジョブ実行部とを有し、
前記ジョブ管理部が、登録された前記ジョブを当該ジョブに固有の識別子と対応付けて管理し、前記ジョブの実行日時に当該ジョブの実行要求と、当該ジョブと対応付けられた前記識別子とを前記ジョブ実行部に通知する第1のステップと、
前記ジョブ実行部が、前記ジョブ管理部からの前記ジョブの実行要求に基づいて、指定された前記ジョブを実行すると共に、前記ジョブを実行することにより作成した次世代の前記世代ファイルを、当該ジョブの実行要求と共に前記ジョブ管理部から通知された前記識別子と対応付けて管理する第2のステップとを備え、
前記第2のステップにおいて、前記ジョブ実行部は、
前記ジョブ管理部からの実行要求に基づいて前記ジョブを実行する際、当該実行要求と共に通知された前記識別子と対応付けられた前記世代ファイルが既に存在するか否かを確認し、当該世代ファイルが存在しない場合には、指定された前記ジョブを実行する一方、当該世代ファイルが既に存在する場合には、指定された動作を実行する
ことを特徴とする情報処理方法。 - 前記識別子と対応付けられた前記世代ファイルが既に存在する場合の前記ジョブ実行部の前記動作は、
前記ジョブの処理結果を、前記識別子と対応付けられた既存の前記世代ファイルに上書きするか、前記識別子と対応付けられた既存の前記世代ファイルを退避して、新たな前記世代ファイルを作成するか、又は、前記ジョブの実行を中止するかのいずれかである
ことを特徴とする請求項1に記載の情報処理方法。 - 前記ジョブ実行部は、
前記ジョブごとのジョブ内容が定義されたジョブ定義ファイルを保持し、
前記ジョブ管理部から前記ジョブの実行要求が与えられるごとに前記ジョブ定義ファイルを参照して当該ジョブを実行し、
前記識別子と対応付けられた前記世代ファイルが既に存在する場合の前記ジョブ実行部の前記動作は、前記ジョブ定義ファイルにおいて定義され、
前記定義された動作に基づいて、前記ジョブの処理結果を前記識別子と対応付けられた既存の前記世代ファイルに上書きするか、前記識別子と対応付けられた既存の前記世代ファイルを退避して、新たな前記世代ファイルを作成するか、又は、前記ジョブの実行を中止するかを決定する
ことを特徴とする請求項2に記載の情報処理方法。 - 前記第2のステップでは、
前記ジョブ実行部が、前記ジョブ管理部からの実行要求に基づいて前記ジョブを実行する際、当該実行要求と共に通知された前記識別子と対応付けられた前記世代ファイルが既に存在する場合には、所定のメッセージを前記ジョブ管理部に送信し、
前記ジョブ管理部が、前記ジョブ実行部からの前記メッセージを受信すると、前記ジョブ実行部が実行すべき動作の入力要求を表示し、入力された前記ジョブ実行部が実行すべき前記動作を前記ジョブ実行部に通知し、
前記ジョブ実行部が、前記ジョブ管理部から通知された前記動作を実行する
ことを特徴とする請求項2に記載の情報処理方法。 - 最新世代の世代ファイルを入力としてジョブを実行し、次世代の世代ファイルを作成する情報処理システムであって、
登録された前記ジョブを管理するジョブ管理部と、
前記ジョブ管理部からの前記ジョブの実行要求に基づいて、指定された前記ジョブを実行するジョブ実行部とを備え、
前記ジョブ管理部は、
登録された前記ジョブを当該ジョブに固有の識別子と対応付けて管理し、前記ジョブの実行日時に当該ジョブの実行要求と、当該ジョブと対応付けられた前記識別子とを前記ジョブ実行部に通知し、
前記ジョブ実行部は、
前記ジョブを実行することにより作成した次世代の前記世代ファイルを、当該ジョブの実行要求と共に前記ジョブ管理部から通知された前記識別子と対応付けて管理し、前記ジョブ管理部からの実行要求に基づいて前記ジョブを実行する際には、当該実行要求と共に通知された前記識別子と対応付けられた前記世代ファイルが既に存在するか否かを確認し、当該世代ファイルが存在しない場合には、指定された前記ジョブを実行する一方、当該世代ファイルが既に存在する場合には、指定された動作を実行する
ことを特徴とする情報処理システム。 - 前記識別子と対応付けられた前記世代ファイルが既に存在する場合の前記ジョブ実行部の前記動作は、
前記ジョブの処理結果を、前記識別子と対応付けられた既存の前記世代ファイルに上書きするか、前記識別子と対応付けられた既存の前記世代ファイルを退避して、新たな前記世代ファイルを作成するか、又は、前記ジョブの実行を中止するかのいずれかである
ことを特徴とする請求項5に記載の情報処理システム。 - 前記ジョブ実行部は、
前記ジョブごとのジョブ内容が定義されたジョブ定義ファイルを保持し、
前記ジョブ管理部から前記ジョブの実行要求が与えられるごとに前記ジョブ定義ファイルを参照して当該ジョブを実行し、
前記識別子と対応付けられた前記世代ファイルが既に存在する場合の前記ジョブ実行部の前記動作は、前記ジョブ定義ファイルにおいて定義され、
前記定義された動作に基づいて、前記ジョブの処理結果を前記識別子と対応付けられた既存の前記世代ファイルに上書きするか、前記識別子と対応付けられた既存の前記世代ファイルを退避して、新たな前記世代ファイルを作成するか、又は、前記ジョブの実行を中止するかを決定する
ことを特徴とする請求項6に記載の情報処理システム。 - 前記ジョブ実行部は、
前記ジョブ管理部からの実行要求に基づいて前記ジョブを実行する際、当該実行要求と共に通知された前記識別子と対応付けられた前記世代ファイルが既に存在する場合には、所定のメッセージを前記ジョブ管理部に送信し、
前記ジョブ管理部は、
前記ジョブ実行部からの前記メッセージを受信すると、前記ジョブ実行部が実行すべき動作の入力要求を表示し、入力された前記ジョブ実行部が実行すべき前記動作を前記ジョブ実行部に通知し、
前記ジョブ実行部は、
前記ジョブ管理部から通知された前記動作を実行する
ことを特徴とする請求項6に記載の情報処理システム。
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/900,255 US20160147561A1 (en) | 2014-03-05 | 2014-03-05 | Information processing method and information processing system |
PCT/JP2014/055628 WO2015132904A1 (ja) | 2014-03-05 | 2014-03-05 | 情報処理方法及び情報処理システム |
JP2016505999A JP5967791B2 (ja) | 2014-03-05 | 2014-03-05 | 情報処理方法及び情報処理システム |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/JP2014/055628 WO2015132904A1 (ja) | 2014-03-05 | 2014-03-05 | 情報処理方法及び情報処理システム |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2015132904A1 true WO2015132904A1 (ja) | 2015-09-11 |
Family
ID=54054741
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2014/055628 WO2015132904A1 (ja) | 2014-03-05 | 2014-03-05 | 情報処理方法及び情報処理システム |
Country Status (3)
Country | Link |
---|---|
US (1) | US20160147561A1 (ja) |
JP (1) | JP5967791B2 (ja) |
WO (1) | WO2015132904A1 (ja) |
Families Citing this family (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10346248B2 (en) * | 2016-06-23 | 2019-07-09 | Red Hat Israel, Ltd. | Failure resistant volume creation in a shared storage environment |
JP6981202B2 (ja) * | 2017-11-22 | 2021-12-15 | 富士フイルムビジネスイノベーション株式会社 | 情報処理装置及び情報処理プログラム |
EP3699771A1 (en) * | 2019-02-21 | 2020-08-26 | CoreMedia AG | Method and apparatus for managing data in a content management system |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH05282164A (ja) * | 1992-03-31 | 1993-10-29 | Idemitsu Kosan Co Ltd | コンピュータ運用自動化装置 |
JPH0728633A (ja) * | 1993-07-13 | 1995-01-31 | Hitachi Ltd | プログラム群世代管理方法と装置およびプログラムアップデート処理方法および分散処理システム |
JPH0793200A (ja) * | 1993-09-27 | 1995-04-07 | Nec Corp | ファイル管理システム |
JP2003271408A (ja) * | 2002-03-14 | 2003-09-26 | Hitachi Ltd | 電子データの更新方法及びパッチデータ作成方法 |
JP2008225979A (ja) * | 2007-03-14 | 2008-09-25 | Hitachi Ltd | 情報処理装置、プログラム及び情報処理方法 |
Family Cites Families (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH08286932A (ja) * | 1995-04-11 | 1996-11-01 | Hitachi Ltd | ジョブの並列実行制御方法 |
JP2000250667A (ja) * | 1999-02-26 | 2000-09-14 | Nec Corp | システム処理機能を提供するサスペンド・レジューム方法 |
US20020065835A1 (en) * | 2000-11-27 | 2002-05-30 | Naoya Fujisaki | File system assigning a specific attribute to a file, a file management method assigning a specific attribute to a file, and a storage medium on which is recorded a program for managing files |
JP2005031771A (ja) * | 2003-07-08 | 2005-02-03 | Hitachi Ltd | ジョブスケジューリング管理方法及びシステム並びにプログラム |
WO2005050447A1 (ja) * | 2003-11-18 | 2005-06-02 | Intelligent Model, Limited | バッチ処理装置 |
JP4483342B2 (ja) * | 2004-02-27 | 2010-06-16 | 株式会社日立製作所 | システム復旧方法 |
US8108878B1 (en) * | 2004-12-08 | 2012-01-31 | Cadence Design Systems, Inc. | Method and apparatus for detecting indeterminate dependencies in a distributed computing environment |
US7757234B2 (en) * | 2005-10-24 | 2010-07-13 | Sap Aktiengesellschaft | Methods and software for a batch processing framework for wizard-based processes |
US8205189B2 (en) * | 2006-07-13 | 2012-06-19 | Oracle International Corporation | Method and system for definition control in a data repository application |
JP5045042B2 (ja) * | 2006-09-19 | 2012-10-10 | 富士通株式会社 | 業務フロー編集プログラム、業務フロー編集装置および業務フロー編集方法 |
US20080148261A1 (en) * | 2006-12-18 | 2008-06-19 | Andrew Rodney Ferlitsch | Batch handling for background file processing |
US8181180B1 (en) * | 2007-09-14 | 2012-05-15 | Hewlett-Packard Development Company, L.P. | Managing jobs in shared file systems |
JP2011053995A (ja) * | 2009-09-03 | 2011-03-17 | Hitachi Ltd | データ処理制御方法および計算機システム |
US9183038B2 (en) * | 2010-11-10 | 2015-11-10 | Hitachi, Ltd. | Job management system that determines if master data has been updated, then re-executes a sub-job based on available executing computers and data sharing status |
US8949258B2 (en) * | 2011-03-28 | 2015-02-03 | Microsoft Corporation | Techniques to manage file conversions |
US9230294B2 (en) * | 2013-03-15 | 2016-01-05 | Dreamworks Animation Llc | Preserving and reusing intermediate data |
-
2014
- 2014-03-05 JP JP2016505999A patent/JP5967791B2/ja active Active
- 2014-03-05 US US14/900,255 patent/US20160147561A1/en not_active Abandoned
- 2014-03-05 WO PCT/JP2014/055628 patent/WO2015132904A1/ja active Application Filing
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH05282164A (ja) * | 1992-03-31 | 1993-10-29 | Idemitsu Kosan Co Ltd | コンピュータ運用自動化装置 |
JPH0728633A (ja) * | 1993-07-13 | 1995-01-31 | Hitachi Ltd | プログラム群世代管理方法と装置およびプログラムアップデート処理方法および分散処理システム |
JPH0793200A (ja) * | 1993-09-27 | 1995-04-07 | Nec Corp | ファイル管理システム |
JP2003271408A (ja) * | 2002-03-14 | 2003-09-26 | Hitachi Ltd | 電子データの更新方法及びパッチデータ作成方法 |
JP2008225979A (ja) * | 2007-03-14 | 2008-09-25 | Hitachi Ltd | 情報処理装置、プログラム及び情報処理方法 |
Non-Patent Citations (1)
Title |
---|
UCOSMINEXUS BATCH JOB EXECUTION SERVER SHIYO NO TEBIKI, 30 November 2010 (2010-11-30), pages 2 - 6 * |
Also Published As
Publication number | Publication date |
---|---|
US20160147561A1 (en) | 2016-05-26 |
JP5967791B2 (ja) | 2016-08-10 |
JPWO2015132904A1 (ja) | 2017-03-30 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9940067B2 (en) | Performing a data write on a storage device | |
US9335931B2 (en) | System and method for making snapshots of storage devices | |
CN108021338B (zh) | 用于实现两层提交协议的系统和方法 | |
JP5967791B2 (ja) | 情報処理方法及び情報処理システム | |
JP2007140746A (ja) | 計算機システム及び管理計算機並びにリカバリ管理方法 | |
JP2014191604A5 (ja) | ||
US9183038B2 (en) | Job management system that determines if master data has been updated, then re-executes a sub-job based on available executing computers and data sharing status | |
WO2015083243A1 (ja) | エンジニアリングツールプログラムおよびネットワークシステム | |
WO2018025383A1 (ja) | エビデンス収集システム及び方法 | |
JP6268991B2 (ja) | 情報処理システム、情報処理装置及びプログラム | |
JP6442059B2 (ja) | 運用自動化装置及び方法並びに記憶媒体 | |
WO2017072978A1 (ja) | 計算機システム及び業務移行方法 | |
US8838545B2 (en) | Incremental and prioritized restoration of blocks | |
JP2009009323A (ja) | 設定装置、電子機器、及び設定プログラム | |
JP2009266149A (ja) | ジョブ管理プログラム及びジョブ管理装置 | |
US8255648B2 (en) | Maintaining storage device backup consistency | |
JP2008033827A (ja) | ストレージ装置及びプログラム更新方法 | |
JP6613372B2 (ja) | 情報処理システム及び業務冗長化方法 | |
JP6467298B2 (ja) | サーバ運用作業履歴管理装置、システム、方法、およびプログラム | |
JP2009205241A (ja) | コンピュータシステム及びそのシステムにおけるブート制御方法 | |
JP5574274B2 (ja) | データ処理装置、データ処理方法、及びプログラム | |
JP2023094787A (ja) | シナリオ管理システム、シナリオ管理方法、及びシナリオ管理プログラム | |
TWI468930B (zh) | 於儲存裝置執行資料寫入 | |
JP2017068668A (ja) | データベースシステム、レプリケーション制御装置、レプリケーション方法、及びプログラム | |
JP2009230322A (ja) | ジョブ管理システム |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
ENP | Entry into the national phase |
Ref document number: 2016505999 Country of ref document: JP Kind code of ref document: A |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 14884429 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 14900255 Country of ref document: US |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 14884429 Country of ref document: EP Kind code of ref document: A1 |