System for simultaneously executing any one of plurality of applications that must be executed using static data not modified by another computer program

[0002] The present invention relates to a method, apparatus and computer program for taking a backup copy of the contents of an external storage device to be accessed by a data processing system. More particularly, the present invention relates to a method, apparatus and computer program for simultaneously executing any one of a plurality of applications (computer programs) that must be executed using static data not modified by another computer program after a particular point in time and another application which must be executed using updated data.

[0003] Accompanying the recent increase in the use of data processing systems, and the extension of business hours or the shift to 24-hour uninterrupted operation, it has become difficult to allocate time, after stopping execution of an application for updating data, for execution of an application for processing data in a static state in which no data updating operation is being performed. It should be noted that an application can, for example, be a computer program or any other such means for performing a particular processing on data. The application for processing data could, for example, be a computer program for taking a backup copy, executing statistical processing on daily business results, etc. Hence, apparatus have been sought for simultaneously executing an application for performing a data updating operation and an application that must be executed in the state in which no data updating operation has been performed.

[0004] To solve the above Japanese Patent Laid-open No. Hei 5-94265 proposes a mechanism in which, in a multiple-writing filing system, the multiple-writing configuration is cleared and an application is allowed to update one of the cleared devices. The controller takes a backup copy of the other device in a static state in which no updating operation is being performed.

[0005] Japanese Patent Laid-open No. Hei 6-44010 proposes that all or part of a data set to be affected by an updating operation is written to a subsystem memory. The update is then written to the subsystem memory to complete the updating operation. In response to an input request from the backup copy, the data in the not-updated portion is input from the original data set, and the data in the updated portion is input from the subsystem memory.

[0006] The method disclosed in Japanese Patent Laid-open No. Hei 5-94265 does not consider a situation in which an application other than an application taking a backup copy references static data that has not been updated. Therefore, this conventional arrangement must execute an application that requires static data after storing a backup copy taken by the backup copy taking application into an external storage device to maintain the logical integrity of the data.

[0007] The method disclosed in Japanese Patent Laid-open No. Hei 6-44010 does not consider application of the disclosed technology to any type of application. Therefore, this conventional arrangement needs to be aware of whether an area for data input/output operations by each application requiring application of the disclosed technology has been updated or not. This presents problems of making applications complicated and pushes up the cost of the entire system.

[0008] The present invention provides improvements in a method, apparatus and a computer program for applying, to any given application, a capability of inputting/outputting static data not modified by any application after a particular point in time without affecting an application requiring a data updating operation in an external storage device associated with an access operation by a data processing system.

[0009] According to one aspect of the invention, a duplicate of data stored in an external storage device requiring input/output of static data not modified by an application after a particular point in time is taken. A static data input/output controller for controlling a data input/output request to the external storage device and the duplicate thereof and a static data input/output identification data defining module for identifying whether a data input/output request is for static data are arranged in a processing unit. The static data input/output controller determines whether the source of the data input/output request requests static data based on the information in the static data input/output identification information defining module. If the input/output request is for the static data not modified by an application after a particular point in time, the static data input/output controller performs a data input/output operation on one external storage device with the static data. For other input/output requests, the controller performs a data input/output operation on the other external storage device.

[0010] Some applications complete logical input/output processing of data upon completion of two or more data input/output requests. To allow these applications to reference the static data having logical integrity these applications are cooperatively associated. Access by these applications to the external storage device is temporarily discontinued in a state in which the logical integrity of the data is maintained, and then the static data input/output controller is started.

[0011] Other applications complete logical input/output processing of data upon completion of the data input/output requests of two or more external storage devices. To allow these applications to reference the static data having logical integrity, the start processing of the static data input/output controller for these two or more external storage devices is performed all at once, thereby allowing reference to the static data in these two or more external storage devices at a same point in time having the data logical integrity.

[0012] The scope of the present invention will be apparent from the following detailed description, when taken in conjunction with the accompanying drawings, and such detailed description and specific examples, while indicating preferred embodiments of the invention, are given by way of illustration only, since various changes and modifications within the spirit and scope of the invention will become apparent to those skilled in the art from this detailed description, in which:

[0013] FIG. 1 is a schematic diagram illustrating a first preferred embodiment of the present invention;

[0014] FIG. 2 is a flowchart illustrating the processing performed by the present invention in the system shown in FIG. 1;

[0015] FIG. 3 is a schematic diagram illustrating a second embodiment of the present invention;

[0016] FIG. 4 is a flowchart illustrating the processing performed by the present invention in the system shown in FIG. 3;

[0017] FIG. 5 is a schematic diagram illustrating a third embodiment of the present invention;

[0018] FIG. 6 is a flowchart illustrating the processing performed by the present invention illustrated in FIG. 5;

[0019] FIG. 7 illustrates a table which stores identification information defined in the static data input/output application identification information defining module 15;

[0020] FIG. 8 illustrates a table which stores identification information of the application that executes input/output to the external storage device 6; and

[0021] FIG. 9. illustrates a table which stores information that relates the identification information with the input/output target.

[0022] FIG. 1 is a schematic diagram illustrating a first preferred embodiment of the present invention. As shown in FIG. 1, reference numeral 1 denotes a processing unit for executing various computer programs. Reference numerals 111 and 112 denote applications that operate in the central processing unit 1. Application 111 denotes an application that does not require any input/output of static data not modified by an application after a particular point in time. Application 112 denotes an application that requires input/output of static data not modified by an application after a particular point in time. Reference numeral 12 denotes a duplicating computer program for implementing a duplicate of external storage devices (external storage devices 5 and 6 in the embodiments herein) that operate in the central processing unit 1. Reference numeral 14 denotes a static data input/output controller that operates in the central processing unit 1 to determine an application which is the source of a data input/output request and support input/output of data not modified by another application after a particular point in time. Reference numeral 15 denotes a static data input/output application identification information defining module for defining identification information for identifying an application that requires input/output of data not modified by another application after a particular point in time. Reference numeral 2 denotes a bus for connecting the central processing unit 1 to a controller 3, which controls a data input/output operation with the external storage devices 5 and 6. Reference numeral 4 denotes a bus for connecting the controller 3 to the external storage devices 5 and 6, which are connected to the controller 3.

[0023] The following describes the operation of the above-mentioned embodiment. In the following description, the external storage device 6 is assumed to be the data duplicating source while the external storage device 5 is assumed to be the data duplicating destination. FIG. 2 is a flowchart illustrating the processing of applying a capability of inputting/outputting static data not modified by another application after a particular point of time to any application. It should be noted that each of the steps of the flowchart can, for example, correspond to one or more instructions of a computer program that when executed by a computer causes the computer to perform the indicated steps. The computer program can, for example, be stored in memory in the computer, stored on a storage medium, such as a floppy disk, CD ROM, etc, and installed in the computer, or provided to the computer via a network, such as a local area network, internet, etc.

[0024] Referring to FIG. 2, in step ST21, the identification information for identifying an application requiring input/output of static data not modified by another application after a particular point in time is registered in the static data input/output application identification information defining module 15. The information suitable for use as the identification information includes an application registration name for identifying an application, a job class for specifying application executing environment, a load module attribute indicative of the attribute of an application program, and a library name indicative of a library in which the application program is stored. If the external storage devices 5 and 6 are shared by two or more processing units, a system identifier for identifying the central processing unit is used as the application identification information. In such a case, an application requiring input/output of static data not modified by another application after a particular point in time and an application not requiring reference to the static data may be executed in separate processing units. Alternatively, apparatus may be provided that notifies, from an application, the static data input/output application identification information defining module whether the application or the data input/output request requires input/output of the static data not modified by another application after a particular point in time. The identification information can, for example, be stored in a table which, for example, can be included in the static data input/output application identification information defining module.

[0025] In step ST22, to make preparations for operating the capability of referencing the static data in the external storage device 6, the duplicating program 12 is started to duplicate the data in the external storage device 6 onto the external storage device 5. When the data in the external storage device 6 has been duplicated, the static data input/output controller 14 is started in step ST23.

[0026] When the static data input/output controller 14 has been started, the application 111 or the application 112 issues a data input/output request to the input/output control program 13 in step ST24. This data input/output request is issued as a data input/output request to the external storage device 6, which is the data duplicate source, regardless of the application that issued the data input/output request.

[0027] In step ST25, if the input/output control program 13 finds that the data input/output request is directed to the external storage device 6, the input/output control program 13 transfers this data input/output request to the static data input/output controller 14.

[0028] FIG. 7 is an example of a table TB71 that stores the identification information defined in the static data input/output application definition information defining module 15. Table TB71 lists the identification information possessed by an application that input/outputs static data. If the identification information of the application is registered in the table TB71, the application executes an input/output to the external storage device 5 containing static data. If the identification information of the application is not registered in the table TB71, the application executes an input/output to the external storage device 6 containing the data updated by other applications.

[0029] The table TB71, which stores the identification information defined in the static data input/output application definition information defining module 15, can, for example, be either of the tables illustrated in FIGS. 8 and 9. Table TB81, lists the identification information of the application that executes an input/output to the external storage device 6 containing the data updated by other application. Table TB91, illustrated in FIG. 9, provides information indicating relations between all identification information and the external storage device which is the input/output target.

[0030] In step ST26, the static data input/output controller 14 determines whether the identification information held by the application that issued the data input/output request matches the identification information already registered in the static data input/output application identification information defining module 15.

[0031] If the identifier of the above-mentioned identification information held by the application is found matching the identifier of the above-mentioned identification information already registered in step ST26, then the operation of step ST27 is executed. In step ST27, the static data input/output controller 14 converts the data input/output request for the external storage device 6 into a data input/output request for the external storage device 5 and issues the resultant data input/output request to the external storage device 5. If the above-mentioned identifiers do not match each other in step ST26, the operation of step ST28 is executed. In step ST28, the static data input/output controller 14 sends the data input/output request issued by the application directly to the external storage device 6.

[0032] In step ST29, receiving a notification of completion from the external storage device (5 or 6) to which the data input/output request was issued, the static data input/output controller 13 reports the notification of input/output completion to the application (111 or 112) that issued the data input/output request.

[0033] The processing operations performed in step ST26 through step ST29 allow the application 111 and the application 112 to perform a data input/output operation without being aware of the external storage device 5 in which the static data is stored. The application 112 can input/output the static data that has not been modified by an application subsequent to the point of time at which the operation of step ST23 was executed.

[0034] Using, as the duplicating program 12, the method disclosed in Japanese Patent Laid-open No. Hei 6-44010 as discussed above, the data in the external storage device 6 may also be duplicated without pausing the application in execution. The duplicating program 12 may also be a program operating in the controller 3 or a program that executes duplication by operating associating a program operating in the processing unit 1 and the program operating in the controller 3.

[0035] The external storage device, based on which the −17 duplicating program 12 performs a duplicating operation, may be either a physical unit such as a magnetic disk or a logical unit such as a file or a data set.

[0036] The external storage devices 5 and 6 may be either a physical medium such as a magnetic disk, a virtual device such as a file or a table developed in the main memory of the central processing unit 1, or a logical device such as a time-zero backup to be generated when the duplicating method disclosed in Japanese Published Examined Patent No. 2557172. In addition, the external storage devices 5 and 6 may be different types of external storage devices.

[0037] FIG. 3 illustrates a second embodiment of the present invention to be applied if a duplicate of the data stored in the external storage device 6 already exists because the external storage devices 5 and 6 operate as multiple-writing devices due to a multiple-writing control program operating in the central processing unit 1. Referring to FIG. 3, reference numeral 16 denotes a computer program operating in the central processing unit 1 to execute multiple-writing control on the external storage devices 5 and 6. In the following description, the external storage device 5 is assumed to be a sub device of a multiple-writing control device while the external storage device 6 is assumed to be a main device of the multiple-writing control device for the sake of description.

[0038] FIG. 4 is a flowchart illustrating the processing of applying, in the system illustrated in FIG. 3, a capability of inputting/outputting static data not modified by an application after a particular point of time to any other application. It should be noted that each of the steps of the flowchart can, for example, correspond to one or more instructions of a computer program that when executed by a computer causes the computer to perform the indicated steps. The computer program can, for example, be stored in memory in the computer, stored on a storage medium, such as a floppy disk, CD ROM, etc, and installed in the computer, or provided to the computer via a network, such as a local area network, internet, etc.

[0039] Referring to FIG. 4, the identification information for identifying an application that requires input/output of the static data not modified by another application after a particular point in time is registered in the static data input/output application identification information defining module 15 in step ST41. In step ST42, the static data input/output controller 14 requests the multiple-writing control program 16 to block the external storage device 5, or the sub device. When the external storage device 5 has been blocked, a data input/output request is issued from the application 111 or the application 112 to the multiple-writing control program 16 in step ST43. This data input/output request is issued as a data input/output request for the external storage device 6, which is the main device like the conventional multiple-writing controller, regardless of whether the input/output of the static data is required or not.

[0040] In step ST44, if the multiple-writing control −19 program 16 finds that the above-mentioned data input/output request is for the external storage device 6, then the multiple-writing control program 16 transfers this data input/output request to the static data input/output controller 14. In step ST45, the static data input/output controller 14 determines whether the identification information held by the application that issued the above-mentioned data input/output request matches the identification information registered in the static data input/output application identification information defining module 15 in step ST41.

[0041] If the identifier of the data input/output request source is found matching the registered identifier in step ST45, the operation of step ST46 is executed. In step ST46, the static data input/output controller 14 issues a data input/output request to the blocked external storage device 5. On the other than, if no match is found between the identifier of the data input/output request source and the registered identifier in step S45, the operation of step ST47 is executed. In step ST47, the static data input/output controller 14 sends the data input/output request issued by the application to the external storage device 6.

[0042] In step ST48, receiving a notification of completion from the external storage device (5 or 6) to which the data input/output request has been issued, the static data input/output controller 14 reports the input/output completion to the application (111 or 112) that issued the data input/output request.

[0043] The processing operations performed in step ST45 through step ST48 allow the application 111 and the application 112 to perform an input/output operation without being aware of the blocked external storage device 5 in which the static data is stored. The application 112 can input/output the static data that has not been modified by an application subsequent to the point in time at which the operation of step ST42 was executed. The device to be blocked in step ST42 may be the external storage device 6, which is the main device of the multiple-writing controller. In this case, the external storage device 5 and the external storage device 6 to which the data input/output request is issued in step ST46 and step ST47 may be exchanged.

[0044] FIG. 5 illustrates a third embodiment of the present invention to be applied if a duplicate of the data stored in the external storage device 6 already exists because the external storage devices 5 and 6 operate as multiple-writing devices due to a multiple-writing control program operating in the controller 3. Referring to FIG. 5, reference numeral 31 denotes a computer program operating in the controller 3 to execute multiple-writing control on the external storage devices 5 and 6. FIG. 6 is a flowchart illustrating the processing of applying, in the system illustrated in FIG. 5, a capability of inputting/outputting static data not modified by an application after a particular point of time to any other application. It should be noted that each of the steps of the flowchart can, for example, correspond to one or more instructions of a computer program that when executed by a computer causes the computer to perform the indicated steps. The computer program can, for example, be stored in memory in the computer, stored on a storage medium, such as a floppy disk, CD ROM, etc, and installed in the computer, or provided to the computer via a network, such as a local area network, internet, etc.

[0045] In step ST61, the identification information for identifying an application that requires input/output of the static data not modified by another application after a particular point in time is registered in the static data input/output application identification information defining module 15. In step ST62, the static data input/output controller 14 requests the multiple-writing control program 31 operating in the controller 3 to block the external storage device 5. When the external storage device 5 has been blocked, a data input/output request is issued from the application 111 or the application 112 to the input/output control program 13 in step ST63. This data input/output request is issued as a data input/output request for the external storage device 6, which is the main device like the conventional multiple-writing controller, regardless of whether the input/output of the static data is required or not.

[0046] In step ST64, if the multiple-writing control program 31 finds that the above-mentioned data input/output request is for the external storage device 6, then the multiple-writing control program 31 transfers this data input/output request to the static data input/output controller 14. In step ST65, the static data input/output controller 14 determines whether the identification information held by the application that issued the above-mentioned data input/output request matches the identification information registered in the static data input/output application identification information defining module 15 in step ST61.

[0047] If the identifier of the data input/output request source is found matching the registered identifier in step ST65, the operation of step ST66 is executed. In step ST66, the static data input/output controller 14 issues, to the controller 3, a data input/output request attached with a command for executing a data input/output operation with the blocked external storage device 5. On the other than, if no match is found between the identifier of the data input/output request source and the registered identifier in step S65, the operation of step ST67 is executed. In step ST67, the static data input/output controller 14 sends, to the controller 3, the data input/output request attached with a command for executing a data input/output operation with the external storage device 6 not blocked.

[0048] In step ST68, receiving a notification of the input/output completion from the controller 3, the static data input/output controller 14 reports the input/output completion to the application (111 or 112) that issued the data input/output request.

[0049] The processing operations performed in step ST65 through step ST68 allow the application 111 and the application 112 to perform a data input/output operation without being aware of the blocked external storage device 5 in which the static data is stored. The application 112 can input/output the static data that has not been modified by an application subsequent to the point of time at which the operation of step ST62 was executed.

[0050] According to the present invention, the provision of the static data input/output controller and the static data input/output application identification information defining module eliminates the need for an application to be aware of an external storage device in which static data not modified by another application after a particular point in time, thereby enabling input/output of the static data without application modification. Consequently, an application requiring input/output of static data and another application can be executed simultaneously to save business hours without making the applications complicated and involving increase in system cost.

[0051] While the present invention has been described in detail and pictorially in the accompanying drawings, it is not limited to such details since many changes and modification recognizable to these of ordinary skill in the art having the benefit of this invention may be made to the invention without departing from the spirit and scope of the invention, and all such modifications as would be obvious to one skilled in the art and/or which become possible as technology develops, are intended to be included within the scope of the following claims.