JPH01226050A - Data sharing control system for different operating systems - Google Patents

Abstract

PURPOSE:To omit conversion work utilizing a file converter and to speed up data conversion by utilizing data managed by different operating systems directly from an application program between the different operating systems. CONSTITUTION:Data managed by plural different operating systems are exclusively included in common or independently included in filing devices 11, 12, a physical I/O control part 13 physically controls I/O to/from the filing devices 11, 12 in common and plural logical I/O control parts 13 logically control the filing devices 11, 12 under the management of respective operating system. An application program 14 selectively complements logical I/O control parts 15, 16. At the time of utilizing data between different operating systems, data controlled by the different operating systems can be utilized directly from the application program 14. Thereby conversion work utilizing a file converter can be omitted.

Description

[Detailed Description of the Invention] [Field of Industrial Application] The present invention relates to a data sharing control method for different operating systems, and in particular, to sharing a file device (or data file) between different operating systems in an information processing device such as a computer. This paper relates to a data sharing control method for controlling heterogeneous operating systems.

[Conventional technology]

Conventionally, in information processing apparatuses such as computers of the same type or different types, when processed data is managed in a file device as a data file, each operating system used by the information processing apparatus is Since the system (hereinafter referred to as O8) is exclusive, data files under the management of a certain O8 are often not available to other information processing devices or under the management of other O8s.

This means that data files under the management of different O8 formats (especially the index area including volume labels and dataset labels) as shown in Figure 3),
Data code format used by S %Formula% Therefore, when sharing data between different types of O8, use a file converter (conversion program) that converts the format format and data code format to convert the format format and data code format. The common method was to convert the format and then use the data in the data file.

This conventional method of using data between different types of O8 will be explained with reference to FIG.

First, an application program (hereinafter referred to as AP) under the control of a certain O3 (hereinafter referred to as A-O3) writes data to a file device (or data file) under the control of A-O3 (step 41).

Next, under A-O3 management or some other O3 (Kari, B
- Using a file converter under the management of A-O3 (referred to as "O3"), convert the data of the file device under the management of A-O3 (data to be converted) to data under the management of B-O3 (converted data), and convert the converted data into data under the management of B-O3 (converted data). The data is written to the file device (or data file) under B-O3 management (step 42), thereby completing the conversion work.

Furthermore, the converted data is read from the file device under the control of the B-O3 by the AP under the control of the B-O3 and used (step 43).

[Problem to be solved by the invention]

The above-described conventional data utilization method between different types of operating systems always requires conversion work using a file converter, so it has the disadvantage that it takes time and effort to use.

In particular, in this conversion work, formant conversion and code conversion are performed by the file converter, so there is a drawback that it takes more time than reading and writing data to a normal file device. This drawback becomes more pronounced as the size of the data file increases.

In addition, as shown in FIG. 4, in the conversion process using a file converter, the file device in which the data to be converted must be stored and the file device in which the converted data is stored must be different. If the same file device is used by dividing the area as shown in ~), the disadvantage is that the data file of the data to be converted must be copied to another file device and then the data conversion work must be carried out. be.

In view of the above-mentioned points, an object of the present invention is to provide a data sharing control method between different operating systems that eliminates the need for converting formats, data code formats, etc. using a data converter.

[Means to solve the problem]

The data sharing control method between heterogeneous operating systems of the present invention is based on one or more file devices in which data under the management of a plurality of heterogeneous operating systems resides exclusively separately or together, and in which input/output to the file devices is physically controlled. It has a physical input/output control unit for common control, a plurality of logical input/output control units for logically controlling the file device under the management of each operating system, and an application program for selectively capturing the logical input/output control units. .

[Effect]

In the data sharing control method between different operating systems of the present invention, data under the management of a plurality of different operating systems resides exclusively separately or together in one or more file devices, and the physical input/output control unit inputs data to the file device. The output is physically commonly controlled, a plurality of logical input/output controllers logically control the file device under the management of each operating system, and an application program selectively captures the logical input/output controllers.

〔Example〕

Next, the present invention will be explained in detail with reference to the drawings.

FIG. 1 is a block diagram showing the configuration of a data sharing control method between different operating systems according to an embodiment of the present invention. Karini, A-O3
The file device 11 under A-O3 management that can be used under the management of O3 (called B-OS), which is different from A-OS
File device 12 under B-O3 management and file device 11 under A-O3 management that can be used under management (referred to as O3)
and a physical input/output control unit 13 that physically shares input/output to and from the file device 12 under B-O3 management;
- An AP 14 that gives input/output instructions to the file device 11 under O3 management and the file device 12 under B-O8 management, and a logical input to the file device 211 under A-O8 management upon receiving instructions from AP 14. A logical input/output control unit 15 for A-O3 that performs output control, and a logical input/output controller 15 for B-O3 that performs logical input/output control to the file device 12 under B-O3 management in response to instructions from AP14. Output control section 16 and A-
It consists of a conversion table 17 for A-O3 that converts the data code format used by O3, and a conversion table 18 for B-O3 that converts the data code used by B-O3.

The file device 11 under the control of A-O3 and the file device 12 under the control of B-O8 are storage devices such as a floppy disk device or a hard disk device (a storage device consists of a drive mechanism and a medium section, but (indicates the media section), so that they can be used under their own O3 management (the file device 11 under A-O3 management is A-O5, the file device 12 under B-OS management is B-O3), Initialized with a proprietary format.

In addition, file installation fffll and B under A-O3 management are
- Although the file device 12 under O3 management is used as a file device, the data file 11 under A-O3 management and the data file 12 under B-O3 management may coexist in the same file device.

The physical input/output control unit 13 is a physical interface for the file device 11 under A-O3 management and the file device 12 under B-O3 management, and is a physical interface for the file device 11 under A-O3 management and the file device 12 under B-O3 management. Input/output to the file device 12 is performed by tdlm.

The input/output control performed by the physical input/output control unit 13 is performed by the A-O8.
Control of the index area (volume label, data set label, etc., see Figure 3 (bl)) of the file device 11 under management and the file device 12 under B-OS management, and recognition control of physical conditions such as recording density and format. and control of data input/output (read and write) operations.

For example, if A-O3 is currently operating, the AP 14 instructs whether to perform input/output to the file device 11 managed by A-O3 or to the file device 12 managed by B-O3. Logic input/output control unit 15 for A-O3
Alternatively, the logic input/output control unit 16 for B-O3 is selectively captured. In addition, the AP 14 selectively captures various pieces of information called parameters in response to input/output operation instructions and supplies them to the logic input/output control unit 15 for the A-O3 or the logic input/output control unit 16 for the B-O3.

The logic input/output control unit 15 for A-O3 and the logic input/output control unit 16 for B-O8 convert the format based on the index area information given from the AP 14, and convert the data code format of the input/output data. Convert. To convert the data code format of input/output data, use the conversion table 17 for A-O3 for input/output data for A-O3, and use the conversion table 17 for A-O3.
The conversion table 18 for B-O3 is used for input/output data for -O3.

Note that by making the conversion table 17 for A-O3 and the conversion table 18 for B-O8 resident in memory, it is possible to realize high-speed conversion of data code formats.

Next, the operation of the data sharing control method of the heterogeneous operating systems of this embodiment configured as described above will be explained.

Assume that A-O3 is now operating.

AP14 performs input/output to file device 1 under the control of A-O3.
1 or the file device 12 under B-O3 management.

For example, the AP 14 uses the file device 12 under B-O3 management.
If an instruction is given to perform input from the B-O8, the logic input/output control unit 16 for B-O8 is selected and captured.

At this time, the AP 14 provides various parameters associated with input operation instructions to the selectively captured logic input/output control unit 16 for the B-05.

The selectively captured logic input/output control unit 16 for B-O3 is
First, the physical input/output control unit 13 is instructed to input from the file device 12 under the control of the B-O8, and the format is converted based on the parameters given from the AP 14.

Next, the logical input/output control unit 16 for B-O3 sends the file device 1 under B-O3 management via the physical input/output control unit 13.
The data code format of the data for B-O3 input from 2 is converted into the data code format for A-O3 with reference to the conversion table 18 for B-O3.

This data code format conversion is performed as follows.

As shown in FIG. 2, for example, the value of the data code 21 before conversion of the read data code format for B-O3 is 10.
0″ to the address value 1 of the conversion table 18 for B-O3
00' and refers to the data code 22 stored at the address "00" to obtain the value "7F" of the converted data code 22.

The converted data code obtained in this way is AP1
4, and AP14 recognizes that this data code format is A-
Use the B-O3 data converted for O3.

〔Effect of the invention〕

As explained above, the present invention eliminates the need for conversion work using a file converter by making it possible to directly use data managed by different operating systems from an application program when using data between different operating systems. effective.

In addition, even if the same file device is divided into areas, it is possible to directly input and output the data to be used without copying it to another file device, so data conversion is faster than when using a file converter. This has the effect of making it possible to use a file device in common, while also eliminating the hassle of using a file device.

[Brief explanation of the drawing]

FIG. 1 is a block diagram showing the configuration of a 118 method for data sharing between different operating systems according to an embodiment of the present invention. FIG. 2 is a method of data code conversion in the data sharing control method between different operating systems according to this embodiment. Figure 3(a) is a diagram to explain the exclusiveness of the operating system; Figure 3(a) is a diagram illustrating the formant format of a file device; Figure 4 is a diagram illustrating the formant format of a file device; The fifth flowchart showing processing in a data usage method between different types of operating systems is a diagram for explaining a conventional data usage method between different types of operating systems. In the figure, 11... File device under A-O3 management, 12...
File device under B-O3 management, 13...Physical input/output @Habe, 14...Application program, 15...A
-Logic input/output control unit for O3, 16...Logic input/output control unit for B-O3, 17...conversion table for A-O3, 18...conversion table for B-O3. . Figure 3 (a) Figure 3 (b)

Claims (1)

[Scope of Claims] One or more file devices in which data under the management of a plurality of different operating systems resides exclusively separately or together, and a physical input/output control unit that physically controls common input/output to the file devices. A heterogeneous operating system comprising: a plurality of logical input/output control units that logically control the file device under the management of each operating system; and an application program that selectively captures the logical input/output control units. data sharing control method.