JPH05250243A - Data processing system for extended storage device - Google Patents

Abstract

PURPOSE:To collectively and efficiently perform processings by performing processings such as save, restore, copy, deletion, and comparison of a disk in an extended storage device based on the volume table of contents. CONSTITUTION:An operating system 9 and a data processing program 10 exist in a main storage device 3, and a data processing program 10 is provided with a save processing part 11, a restore processing part 12, a deletion processing part 13, a copy processing part 14, a movement processing part 15, a display processing part 16, and a comparison processing part 17. A volume table of contents 5 consisting of information of data names, attributes, storage areas, etc., of data stored in an extended storage device 2 is generated, and processings such as save, restore, copy, deletion, display, comparison, etc., of data in the extended storage device 2 are performed as one logical set, and therefore, processings of all data in the extended storage device 2 are collectively and efficiently performed. In this case, the management directory which the operating system 9 has is used for the volume table of contents 5.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a data processing system for an extended storage device in a computer system having an extended storage device connected as an external storage device.

[0002]

2. Description of the Related Art There are computer systems equipped with an extended storage device that complements a main storage device, but the conventional extended storage device has a small storage capacity and a small number of connected devices.
Therefore, the data in the extended storage device is saved in data set units or in logical data units such as a predetermined memory area used as an extension of the main storage device as described in JP-A-63-244152. Processing such as recovery and deletion was performed.

[0003]

By the way, in recent years, there is a strong demand for improvement in the processing capacity of computer systems.
Along with this, the storage capacity of the extended storage device is becoming large and the number of connected devices is also increasing.

However, in the above-mentioned conventional technique, a large amount of data in the extended storage device is saved, restored, deleted, etc. in data set units or in units such as a predetermined memory area used as an extension of the main storage device. Since the processing is being performed, if the storage capacity of the extended storage device becomes large, for example, even if you try to perform processing such as deleting all at once, you must specify the range to be deleted many times. There is a problem that it cannot be used.

The object of the present invention is to save, restore, copy, move, delete, display, and display all data in the extended storage device.
It is an object of the present invention to provide a data processing system for an extended storage device which can efficiently perform processing such as comparison in a batch.

[0006]

In order to achieve the above-mentioned object, the present invention provides a computer system having an extended storage device connected as an external storage device, wherein the extended storage device is stored in the extended storage device. Create a volume list consisting of information such as data names, attributes, and storage areas of the stored data, and save, restore, copy, delete, display, compare, etc. the data in the extended storage device based on this volume list. Processing is performed.

[0007]

According to the above-mentioned means, a volume list including information such as data names, attributes, and storage areas of data stored in the extended storage device is created, and a logical one is created based on this volume list. Data in the extended storage device is saved, restored, copied, deleted, displayed, compared, etc. as one set, so all data in the extended storage device is saved, restored, copied, moved, deleted, displayed, Processing such as comparison can be efficiently performed collectively.

In this case, the volume list uses a management book held by the operating system.

[0009]

DESCRIPTION OF THE PREFERRED EMBODIMENTS The present invention will be described in detail below with reference to illustrated embodiments.

FIG. 1 is a block diagram showing an embodiment of a computer system to which the present invention is applied.

In the figure, 1 is a central processing unit, 2 is an extended storage device, 3 is a main storage device, 4 is an external storage device,
The main memory 3 has an operating system 9 and a data processing program 10 using the processing method of the present invention.
A recovery processing unit 12, a deletion processing unit 13, a copy processing unit 14, a movement processing unit 15, a display processing unit 16, and a comparison processing unit 17 are provided.

The expanded storage device 2 is provided with a volume list 5, and has data x6 having an attribute used as an extension of the main storage device 3, data y7 having a data set attribute, and other attributes. The data z8 existed. Although FIG. 1 shows the case where only one extended storage device 2 is connected, it is added as needed.

Further, the external storage device 4 is provided with a direct access storage device 18 (magnetic disk device) and a magnetic tape storage device 19 used in the data processing program 10.

FIG. 2 shows the structure of the data management section 30 in the volume list 5 and the data section 37 managed from the volume list provided in the expansion storage device 2. The data management section 30 is used for the volume list 5. A plurality of pieces of management information are mainly formed, that is, six pieces of management information, that is, data name 31, data attribute 32, date and time 33, data part area management 34
The area allocation parameter 35 and other information 36 are included.

Of these, the data name 31 is a name given to the data of the data section 37. In addition, the data attribute 32
Is information for managing the type (attribute) of the data in the data unit 37, and attributes such as attributes used as extensions of the main storage device 3, data set attributes, and other attributes are managed.

The date and time 33 manages time-related information such as the date and time when the data of the data section 37 was created.
The data section area management 34 is the extension storage device 2 of the data section 37.
It manages physical positions such as the start position and end position in. The area allocation parameter 35 manages information about area allocation such as an initial allocation value and an increment value of an area for storing data, and a record length and a block length for data having a data set attribute. Others 36 is information regarding the free area and the annotation of the data part 37.

The data section 37 is managed by the data management section 30 having such a configuration, and the data information 38 itself is stored therein.

FIG. 3 is a block diagram of a save data format used in the save method and the restore method, which are one processing mode of the data processing method of the present invention. The recognition information 50 and the save data management information 5 are shown in FIG.
1, data management unit 52 and data unit 53, which are logical units of data information 54, and end information 55.

Of these, the recognition information 50 is the recognition information that the saving process according to the present invention has been performed (for example, the recognition information that the data has been saved in the direct access storage device 18).

The saved data management information 51 indicates a list of saved data information 54, a save time, a version of the operating system 9, a name of the extended storage device 2, and the like.

The data management unit 52 in the logical unit data information 54 is the data management unit 3 in the volume list 5.
The information of 0 is copied as it is. The data section 53 is the information itself of the data section 37 saved from the extended storage device 2. The data management unit 52 and the data unit 53 form a set of logical unit data information 54, and there are as many sets of saved data sets.

The end information 55 indicates the end of the saved data.

FIG. 4 shows an output format used in the display system which is one processing mode of the data processing system of the present invention. The extended storage device name 70 for which the display process is designated, the save date and time, attributes, etc. Selection condition 71 for data to be displayed,
A column is provided for displaying each of the saved data names 72.

Among the data names 72 of the data to be saved, a data attribute 73 for managing the attributes of the data, a date and time 74 indicating the date and time when the data was created (or updated), The allocation parameter 75 indicating the initial allocation value and the increment value of the data storage area, and other 76 information such as annotations are additionally displayed.

These pieces of information 72 to 76 are obtained by processing the information held in the data management unit 30 in the volume list 5.

Next, save, restore, copy, move,
The operation for deleting, displaying, comparing, etc. will be described with reference to the flowchart.

(1) Saving Process FIG. 5 is a flowchart showing the processing procedure of the saving processing unit 11 of the data processing program 10. When the evacuation processing unit 11 is activated by the operating system 9, it first searches the expansion storage device 2 for which evacuation processing has been designated (step 100). If the search target does not exist because the expansion storage device 2 is not connected, error processing is performed (step 101), and the process ends.

However, when the designated retrieval target exists, exclusive processing is performed so that another processing program does not retrieve the extended storage device 2 (step 102), and thereafter,
The external storage device 4 for storing the save data to be saved from the extended storage device 2 is secured, and the recognition information 50 that the save processing has been performed is saved in the external storage device 4 (step 10).
3).

Then, the data saved in the extended storage device 2 is saved.
The volume list 5 of the data is read into the main storage device 3 (step 104). And the read volume list 5
The data saving data management information 51 is saved in the area next to the recognition information 50 based on the data management unit 30 (step 1
06). After saving, the data management unit 3 of the volume list 5
The attribute of the data is confirmed from the information of 0 (step 10
7). In this confirmation, if the data attribute x, the save format X (step 108), if the data attribute y, the save format Y
(Step 109), if the data attribute is z, save format Z
The save format is selected according to the attribute of the save data, such as (step 110). Then, according to the format, the data management unit 30 of the volume list 5 is transferred to the external storage device 4
Data management unit 5 in the area next to the saved data management information 51 of
It is saved as 2 (step 111).

Next, based on the volume list 5, the data information 38 of the data part 37 of each attribute is read into the main storage device 3 and saved in the data part 53 of the external storage device 4 (step 112). ).

This process is repeated while the save data shown in the volume list 5 exists (step 113).

As a result, when the save processing of all the data in the extended storage device 2 is completed, the end information 55 is saved (step 114) and the extended storage device 2 is released from the exclusive processing (step 115).

Therefore, according to such save processing, since it is not necessary to specify all the data in the extended storage device 2 one by one, the omission of designations and errors during the save processing are reduced, resulting in a failure of the extended storage device 2. It is possible to efficiently perform a save process in preparation for data destruction due to.

In this example, the data in the expansion storage device 2 is saved in a lump, but since the volume list 5 is read in step 104, the save target can be saved in a limited manner. That is, as shown in the flowchart of the application example of FIG. 6, step 105 for limiting the evacuation range is added, and here, for example, the attribute x or the data created after A month B is added. Specify to save. Then, it is possible to save only the attribute x or the data created after A month B.

(2) Recovery Processing FIG. 7 is a flowchart showing the processing procedure of the recovery processing unit 12 of the data processing program 10. When the recovery processing unit 12 is started by the operating system 9, it first searches the expansion storage device 2 for which the recovery processing is designated (step 200). If the search target does not exist because the expanded storage device 2 is not connected, error processing is performed (step 201), and the process ends.

However, when the designated retrieval target exists, exclusive processing is performed so that another processing program does not retrieve the expanded storage device 2 (step 202), and thereafter,
The external storage device 4 that stores the saved data is searched, and the recognition information 50 that the recovery processing has been performed is confirmed (step 203).

Subsequently, the saved data management information 51 of the data saved in the external storage device 4 is read into the main storage device 3 (step 204). Then, the volume list 5 of the extended storage device 2 is read into the main storage device 3 based on the read saved data management information 51 (step 206). After this,
The attribute of the data is confirmed from the data management unit 52 of the saved volume list 5 and the data management unit 30 of the volume list 5 to be restored (step 207). In this confirmation,
If the data exists in the saved data but does not exist in the recovery destination (step 208), the data unit 54 of the logical unit including the saved data management unit 52 and the data unit 53 is created in the expansion storage device 2 of the recovery destination. (Step 211). If the saved data exists and the recovery destination also has the same data name and data attribute (step 209), the data management unit 3 of the expansion storage device 2 of the recovery destination.
0 and the data part 37 are updated (step 212). However, nothing is processed with respect to the data that does not exist in the saved data and exists in the recovery destination (step 21).
0).

These processes are repeated while the recovery data exists in the external storage device 4 (step 213). If the end information 55 is detected, it is determined that the recovery of all the recovery data has been completed, and the extended storage device 2 is released from the exclusive processing (step 214).

Therefore, according to such a recovery process, when the expansion storage device 2 fails, the external storage device 4
It is possible to collectively restore the data saved in the expanded storage device 2 without designating the data in units of data sets.

In this example, the data in the external storage device 4 is collectively restored in the extended storage device 2. However, as shown in the flowchart of the application example of FIG. Adding a step 205 of limiting, where for example the attribute x,
Or, specify to recover the data created after A month B. Then, it is possible to recover only the attribute x or the data created after A month B.

(3) Deletion Processing FIG. 9 is a flowchart showing the processing procedure of the deletion processing unit 15 of the data processing program 10. When the deletion processing unit 15 is started by the operating system 9, it first searches the expansion storage device 2 for which the deletion processing is designated (step 300). If the search target does not exist because the expansion storage device 2 is not connected, error processing is performed (step 301), and the process ends.

However, when the designated search target exists, exclusive processing is performed so that another processing program does not search the extended storage device 2 (step 302), and then the extended storage device 2 is searched. , And the volume list 5 is read into the main memory 3 (step 303).

Then, based on the data management unit 30 of the read volume list 5, the data management unit 30 and the data unit 37 are deleted (step 306).

These processes are repeated until all the data shown in the volume list 5 is exhausted (step 30).
7). Then, when all of them are lost, the confirmation is performed, and the extended storage device 2 is released from the exclusive processing (step 308).

Therefore, according to this example, the extended storage device 2
Data that is no longer needed can be deleted all at once. As a result, the free area of the extended storage device 2 can be optimally maintained.

In this example, the data in the expansion storage device 2 is deleted all at once. However, since the volume list 5 is read in step 303, it is possible to limit the deletion target. That is, as shown in the flowchart of the application example of FIG. 10, a step 304 of limiting the deletion range and a step 305 of judging whether or not the deletion condition is satisfied are added. , Or specify to delete the data created before A month B day. Then, it is possible to delete only the attribute x or the data created before A month B.

(4) Copy Processing FIG. 11 shows the copy processing section 13 of the data processing program 10.
3 is a flowchart showing the processing procedure of.

Here, the copying process means a process for copying data from one expansion storage device to another expansion storage device when a plurality of expansion storage devices 2 are connected.

When the copy processing unit 13 is activated by the operating system 9, it first searches the copy source and copy destination expansion storage devices 2 for which copy processing is designated (step 400). If the search target does not exist because the relevant expansion storage device 2 is not connected, error processing is performed (step 40).
1), end.

However, when the designated retrieval target exists, exclusive processing is performed so that another processing program does not retrieve the extended storage device 2 (step 402), and then the extended storage device 2 of the copy source. The volume list 5 is read into the main storage device 3 (step 403), and the copy destination volume list 5 is read into the main storage device 3 (step 405).

Then, the data management unit 30 of the read volume list 5 of the copy source and the read volume list 5 of the copy destination.
Based on the above, the data is confirmed (step 406).

In this confirmation, if the data exists in the copy source but not in the copy destination (step 407), the same data management unit 30 and data unit 37 as the copy source are created in the copy destination (step 410). ). However, if the copy source exists and the copy destination also has data having the same data name and data attribute (step 408), the data management unit 30 and the data unit 37 are updated (step 411). Further, no processing is performed on the data which does not exist in the copy source but exists in the copy destination (step 40).
9).

These processes are repeated while the copy data exists at the copy source (step 412). When the copying of all data is completed, the copy source and copy destination expansion storage devices 2 are released from exclusive processing (step 41).
3).

Therefore, according to this example, since it is not necessary to specify all the data in the extended storage device 2 one by one, copying can be performed in a batch, and the omission of specification and error during copying processing can be eliminated. be able to.

In this example, the data is copied between the expansion storage devices 2 at once, but since the volume list 5 is read in step 403, the copy target can be limited and copied. .. That is, as shown in the flowchart of the application example of FIG. 12, a step 404 for limiting the copy removal range is added, and here, for example, the attribute x or the data created before A month B is added. Specifies to copy. Then, it is possible to copy only the attribute x or the data created before A month B.

(5) Movement Processing FIG. 13 shows the movement processing section 14 of the data processing program 10.
3 is a flowchart showing the processing procedure of.

Here, the moving process means a process for moving data from one expansion storage device to another expansion storage device when a plurality of expansion storage devices 2 are connected.

When the movement processing unit 14 is activated by the operating system 9, it first searches the source and destination expansion storage devices 2 designated for the movement processing (step 500). If the search target does not exist because the relevant expansion storage device 2 is not connected, error processing is performed (step 50).
1), end.

However, when the designated search target exists, exclusive processing is performed so that another processing program does not search the expanded storage device 2 (step 502), and thereafter, the expanded storage device 2 of the movement source. The volume list 5 is read into the main memory 3 (step 503), and the volume list 5 of the moving destination is read into the main memory 3 (step 505).

Then, the data management unit 30 of the read-in source volume list 5 and destination volume list 5 is read.
Based on the above, the data is confirmed (step 506).

In this confirmation, if the data exists in the source but not in the destination (step 507), the same data management unit 30 and data unit 37 as the source are created in the destination (step 510). ), The source data management unit 30 and the data unit 37 are deleted (step 51).
2). However, if there is data having the same data name and data attribute at the move source and at the move destination (step 508), the data management unit 30 and the data unit 37 thereof.
Are updated (step 511), and the data management unit 30 and the data unit 37 of the move source are deleted (step 51).
2). Further, no processing is performed on the data that does not exist in the source and exists in the destination (step 509).

These processes are repeated while the movement data exists at the movement source (step 513). Then, when the movement of all the data is completed, the source and destination expansion storage devices 2 are released from the exclusive processing (step 41).
3).

Therefore, according to this example, since it is not necessary to specify all the data in the extended storage device 2 one by one, it is possible to collectively move the data, and in addition, there is an omission of specification during the moving process. You can eliminate mistakes.

In this example, the data is collectively moved between the extended storage devices 2, but since the volume list 5 is read in step 503, it is possible to limit the movement target. .. That is, as shown in the flowchart of the application example of FIG. 14, a step 504 for limiting the movement range is added, and here, for example, the attribute x or the data created before A month B is added. Specify to move. Then, it is possible to move only the attribute x or the data created before A month B.

(6) Display Processing FIG. 15 shows the display processing section 16 of the data processing program 10.
3 is a flowchart showing the processing procedure of.

When the display processing unit 16 is started by the operating system 9, first, the expanded storage device 2 designated to display data is searched (step 60).
0). If the search target does not exist because the corresponding expansion storage device 2 is not connected, error processing is performed (step 601) and the process ends.

However, when the designated retrieval target exists, the volume list 5 of the designated expansion storage device 2 is read into the main storage device 3 (step 602). After this,
The attribute of the display processing target data is confirmed based on the data management unit 30 of the read volume list 5 (step 6).
04).

In this confirmation, the display format X (step 605) if the data attribute x, the display format Y (step 606) if the data attribute y, the display format Z (step 607) if the data attribute z. Select the output format according to the data attribute. Then, according to the format, the data management unit 30 of the volume list 5 is displayed in the format shown in the head 4 (step 608).

This process is repeated while there is data to be displayed (step 609).

Therefore, according to this example, it is possible to collectively display a list of data on the specified extended storage device 2, and it is possible to easily know the usage state of the area of the extended storage device 2.

In this example, the list of the data of the extended storage device 2 is displayed all at once, but since the volume list 5 is read in step 602, the display target can be limited and displayed. .. That is, as shown in the flowchart of the application example of FIG. 16, a step 603 for limiting the display range is added, and here, for example, the attribute x or the data created before the A month B is added. Specify to move. Then, it is possible to move only the attribute x or the data created before A month B.

(7) Comparison Processing FIG. 17 shows the comparison processing section 17 of the data processing program 10.
3 is a flowchart showing the processing procedure of.

Here, the comparison processing means whether or not the data of one expansion storage device is the same as the data of another expansion storage device when a plurality of expansion storage devices 2 are connected. , And display the difference.

When the comparison processing unit 17 is activated by the operating system 9, it first searches the expansion storage device 2 of the comparison source and comparison destination for which the comparison processing of data is designated (step 700). If the search target does not exist because the corresponding expansion storage device 2 is not connected, error processing is performed (step 7).
01) and ends.

However, when the specified retrieval target exists, exclusive processing of the expansion storage device 2 is performed (step 702), and thereafter, the volume list 5 of the expansion storage device 2 of the comparison source is first stored in the main storage. It is read into the device 3 (step 703). Thereafter, the volume list 5 of the expanded storage device 2 to be compared is read into the main storage device 3 (step 70
5). Then, the attribute of the comparison processing target data is confirmed based on the read data management unit 30 of the volume list 5 (step 706).

In this confirmation, if the comparison source data management unit 30 and the comparison destination data management unit 30 are the same, nothing is done (step 707).

However, if they are not the same, the data
And the differences are displayed (step 70).
9).

This process is repeated while there is data to be compared (step 710). Then, when the comparison processing of all the data is completed, the extended storage device 2 is released from the exclusive processing (step 711).

Therefore, according to this example, the extended storage device 2
The above data can be collectively compared, and the difference in data between the extended storage devices 2 can be easily known.

In this example, the data in the extended storage devices 2 are compared in a lump, but since the volume list 5 is read in step 703, the comparison target can be limited. That is, as shown in the flowchart of the application example of FIG. 18, a step 704 for limiting the comparison range is added, and here, for example, the attribute x or A is added.
Specifies to compare the data created before the month B day. Then, it is possible to compare only the attribute x or the data created before A month B.

The present invention is not limited to the above embodiment, and various modifications can be made without departing from the scope of the invention.

Further, the data set existing in the extended storage device or the memory area used as an extension of the main storage device can be processed without distinguishing it like the normal data set.

[0083]

As described above, according to the present invention, in the extended storage device connected as the external storage device, the data name, attribute, storage area, etc. of the data stored in the extended storage device are stored. Since a volume list including the information of the above is created, and processing such as saving, restoring, copying, deleting, displaying, and comparing data in the extended storage device is performed based on this volume list, the storage capacity of the extended storage device and the Even if the number of connected devices increases, there is an effect that processing such as saving and deleting all data in the extended storage device can be efficiently performed collectively.

In particular, since it can be handled in the same manner as a magnetic disk device, it is extremely convenient for the user.

[Brief description of drawings]

FIG. 1 is a configuration diagram showing an embodiment of a computer system to which the present invention is applied.

FIG. 2 is a data configuration diagram of a data management unit and a data unit in a volume list of the expansion storage device in FIG.

FIG. 3 is an explanatory diagram showing a data format of saved data in FIG.

FIG. 4 is an explanatory diagram showing a display format of data in FIG.

FIG. 5 is a flowchart showing an embodiment of a data saving processing procedure.

FIG. 6 is a flowchart showing an application example of a data saving processing procedure.

FIG. 7 is a flowchart showing an embodiment of a data recovery processing procedure.

FIG. 8 is a flowchart showing an application example of a data recovery processing procedure.

FIG. 9 is a flowchart showing an example of a data deletion processing procedure.

FIG. 10 is a flowchart showing an application example of a data deletion processing procedure.

FIG. 11 is a flow chart showing an embodiment of a data copy processing procedure.
It's a chart.

FIG. 12 is a flowchart showing an application example of a data copy processing procedure.

FIG. 13 is a flow chart showing an example of a data movement processing procedure.
It's a chart.

FIG. 14 is a flowchart showing an application example of a data movement processing procedure.

FIG. 15 is a flow chart showing an embodiment of a data display processing procedure.
It's a chart.

FIG. 16 is a flowchart showing an application example of a data display processing procedure.

FIG. 17 is a flow chart showing an embodiment of a data comparison processing procedure.
It's a chart.

FIG. 18 is a flowchart showing an application example of the data comparison processing procedure.

[Explanation of symbols]

1 ... Central processing device, 2 ... Extended storage device, 3 ... Main storage device, 4 ... External storage device, 5 ... Volume list in extended storage device, 9 ... Operating system, 10 ... Data processing program, 11 ... Evacuation Processing unit, 12 ... Recovery processing unit, 13 ... Delete processing unit, 14 ... Copy processing unit, 15 ... Moving processing unit, 16 ... Display processing unit, 17 ... Comparison processing unit, 18 ...
Direct access storage device, 19 ... Magnetic tape storage device.

Claims (2)

[Claims] 1. A computer system having an extended storage device connected as an external storage device, wherein the extended storage device has data names, attributes, storage areas, etc. of data stored in the extended storage device. Data processing of the extended storage device, characterized in that a volume list including information of the above is created, and the data in the extended storage device is saved, restored, copied, deleted, displayed, or compared based on the volume list. method. 2. The data processing system method for an extended storage device according to claim 1, further comprising means for limiting data to be processed.