JPH0535574A - Data transfer control method - Google Patents

Abstract

PURPOSE:To offer the data transfer control method which can easily specify a file whose data need to be transferred without making a terminal-side operator paying attention to host-side data base environment. CONSTITUTION:This data transfer control method performs data transfer between a file on a terminal device 6 and a data base DB provided to a host computer 2; when a request to transfer is inputted to the terminal side, a simple file name is specified as a parameter, the file name or table name of the data base DB is determined on the host side according to the simple file name, and file data are stored in or extracted from the data base DB by using the determined file name or table name. A file pattern 21 which has a simple file name variable for substituting the simple file name FID and an identifier name variable for substituting the identification name ID of the terminal is generated and the file name is dynamically determined at the request to transfer.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a data transfer control method for transferring data between a file of a terminal device and a database provided in a host computer.

Generally, a large-capacity DASD (Direct Access Storage Device) such as a magnetic disk device is connected to a host computer, and a large number of files or tables are stored in a database formed in the DASD.

In many cases, a data transfer request is made on the terminal side to such a database, and data is transferred (file transfer) from the terminal device to the database or vice versa.

However, when the terminal device is an intelligent terminal such as a personal computer or a workstation, business processing using various distribution software is often performed on the terminal side,
Operators are familiar with the operation of such distribution software.

Therefore, even when making a data transfer request, it is desirable for the operator of the terminal device to be able to perform the operation without being aware that the other party of the transfer request is the host computer.

[0006]

2. Description of the Related Art Conventionally, when a data transfer request for, for example, exporting (transmitting) a file is made from a terminal side to a host computer, an operator of the terminal device has a file export command and a file on the terminal side. Enter the name and the file name or table name on the host side.

In this case, the input file name on the host side must actually exist in the database on the host side.

When there are a plurality of databases on the host side, it is necessary to enter the database name on the host side.

[0009]

As described above, conventionally, it is necessary to input and specify the database name or file name on the host side every time a data transfer request is made. It was very troublesome for the operator on the terminal side to be aware of the database environment on the host side.

Therefore, there is a problem in that the operability is poor for the operator, and further, an operation error is likely to occur.

In view of the above problems, the present invention provides a data transfer control method by which an operator on the terminal side can easily specify a file to be transferred without being aware of the database environment on the host side. Is intended.

[0012]

In order to solve the above-mentioned problems, the transfer method according to the invention of claim 1 is, as shown in FIG. 1, a file of the terminal device 6 and a database DB provided in the host computer 2. A data transfer control method for performing data transfer between a simple file name FID on the terminal side when a transfer request is input, and a simple file name FI on the host side.
The file name NFID of the database DB is determined based on D, and the file is stored in or extracted from the database DB by the determined file name NFID.

In the transfer method according to the second aspect of the present invention, when a DB file hina model 21 having a variable to be the file name NFID of the database DB is created in advance and a transfer request is issued from the terminal device 6. In addition, based on the simple file name FID specified as a parameter, the file name N of the database DB from the DB file hina 21
Determine the FID.

In the transfer method according to the third aspect of the present invention, the DB file hina type 21 includes a simple file name variable into which the simple file name FID designated as a parameter from the terminal device 6 is substituted, and the terminal device 6 concerned. Terminal identification name variable to which the identification name ID of

In the transfer method according to the fourth aspect of the present invention, a file information management table 22 representing the database name NDB and the file name NFID stored in each database DB is provided, and the file information management table 22 is provided. File name NFI determined based on the simple file name FID from among a plurality of database DBs.
The database DB storing the D file is searched.

In the transfer method according to the invention of claim 5, on the host side, the file name NFIW of the work file 23 and the database DB are based on the simple file name FID.
File name NFID is determined, data is transferred between the file on the terminal side and the work file 23, and the file is stored between the work file 23 and the database DB according to each of the determined file names NFIW and NFID. Or, perform extraction.

In the present invention, files include files having various structures, data sets, tables and the like.

[0018]

On the terminal side, when the transfer request is input, the simple file name FID is designated as a parameter.

On the host side, the DB file chick type 21 is created in advance. DB file Hina 21
The file names NFIW and NFID are determined by substituting the simple file name FID and the identification name ID.

The file name NFID is searched for the database name NDB in which the file is stored by referring to the file information management table 22, and the file is stored or extracted between the database DB and the work file 23. Be seen.

[0021]

1 is a block diagram showing an example of a data communication system 1 to which a data transfer control method according to the present invention is applied.

The data communication system 1 includes a host computer 2 installed on the center side (host side) and a DASD.
3, a console 4, a number of workstations 6 installed on the data terminal device side (terminal side), a DASD 7 connected to each workstation 6, and the like.

The host computer 2 includes a main processing section 1
1, a file transfer processing unit 12, a database management unit 13, and the like are provided.

The main processing unit 11 processes the data input to and output from a communication control device (not shown) and various other data, and controls the entire data communication system 1. The main processing unit 11 decodes the received message, reads the business processing program as necessary to process the message, and performs processing for transmitting the message of the processing result.

The file transfer processing unit 12 is for carrying out the processing required for a file transfer request. The file transfer processing unit 12 controls the file chick type 21, the table information management table 22, and the work file 2.
3 is created. Details will be described later.

The database management unit 13 defines and maintains the relational database DB stored on the DASD 3, creates a new table TB in the database DB, and creates a table TB stored in the database DB.
Data is loaded, fetched, or updated with respect to.

The main processing unit 11, the file transfer processing unit 12, and the database management unit 13 are composed of hardware such as a CPU and a storage device, and software such as a communication control program, various support programs, and application programs. There is.

The DASD 3 is composed of, for example, a magnetic disk device, and a plurality of databases D are stored in the DASD 3.
B is stored.

In this embodiment, each database DB
Is a relational type and each database name is "DB
1 ”,“ DB2 ”, and“ DB3 ”. In the following, the database DBs whose database names are “DB1”, “DB2”, and “DB3” are displayed as “database DB1”, “database DB2”, and so on.

The console 4 is for monitoring the operating status of the data communication system 1 and for inputting commands, commands, data, etc. to the host computer 2, and is equipped with a display device and a keyboard.

The workstation 6 is equipped with a display device, a keyboard, etc., and performs data communication with the host computer 2 as well as the workstation 6.
It operates as an intelligent terminal that executes various business processes by itself.

The DASD 7 is composed of, for example, a magnetic disk device or a floppy disk, and stores various files F and programs for processing in the workstation 6.

FIG. 2 is a diagram showing an example of the file chick type 21, FIG. 4 is a diagram showing an example of the chick type definition sentence 31, and FIG. 8 is a flowchart showing the setting process of the file chick type 21.

The file chick type 21 is for determining the file name NFIW of the work file 23 and the table name NFID of the database DB based on the simple file name FID designated from the terminal side.

Therefore, the file chick type 21 includes a physical file chick type for the work file 23 and a DB table chick type for the table of the database DB, but these have the same contents in this embodiment. .

The file chick type 21 is composed of a project name "AAA", a simple file name variable "&FID", and a terminal identification name variable "&ID".

The project name is commonly set, for example, in the data communication system 1, and its content can be arbitrarily set.

The simple file name FID designated as a parameter is substituted into the simple file name variable, and
The identification name ID of the workstation 6 that has transmitted the transfer request is substituted in the terminal identification name variable.

The file chick type 21 is set by inputting the chick type definition sentence 31 shown in FIG. 4 from the console 4 of the host computer 2.

When the chick type definition statement 31 is input (step # 11), after the command analysis is performed, the physical file chick type is set in the common area (step # 1).
2), DB table chick type is set (step # 1)
3).

FIG. 3 is a diagram showing an example of the table information management table 22, FIG. 5 is a diagram showing an example of the management table definition statement 32, and FIG. 9 is a flowchart showing a setting process of the table information management table 22.

The table information management table 22 represents the database name NDB and the table name NFID stored in each database DB. By referring to this table information management table 22, the table name NFID The database DB in which the table TB is stored is searched.

The table information management table 22 includes the management table definition statement 3 shown in FIG.
Set by entering 2.

When the management table definition statement 32 is input (step # 21), the table information of the database management section 13 is searched for the database DB specified by the management table definition statement 32 (step # 22), and the table information management table is displayed. 22 is created (step # 23).

When the table TB is newly created in the database DB after the table information management table 22 is set, the table name NFID is registered corresponding to the corresponding database DB.

Next, a data transfer control method in the data communication system 1 will be described with reference to flowcharts and the like.

FIG. 6 shows an export command statement 3 for a transfer request.
3 is a diagram showing an example of a storage command sentence 34 for a transfer request, FIG. 10 is a flowchart showing an operation of a transfer request, and FIG. 11 is a flowchart showing a transfer process.

In order to make a transfer request from the workstation 6, in the case of export, the export command statement 33 and the store command statement 34 are input (steps # 32, 33), and in the case of import (reception), extraction A command statement and a transfer command statement are input (steps # 34, 35).

The export command statement 33 specifies the simple file name FID and the export source file name following the export command. In the example shown in FIG. 6, the simple file name FI
"ZAIKO" is designated as D and "BUHIN" is designated as the export source file name.

The storage command statement 34 specifies the simple file name FID after the storage command. In the example shown in FIG. 7, “ZAIKO” is designated as the simple file name FID.

That is, according to the examples shown in FIGS. 6 and 7,
Transfer request for exporting the file "BUHIN" stored in the DASD 7 to the work file 23 as the simple file name "ZAIKO", and storing the file ("ZAIKO") in the database DB as the simple table name "ZAIKO" It turns out that.

When the transfer request is transmitted from the workstation 6, the command name and the identification name ID ("T" in this example) of the workstation 6 are sent.
"OKYO") is also automatically transmitted.

On the other hand, when the host computer 2 receives the transfer request, the host computer 2 executes the export / storing process if the request is an export request (step # 42), and the extract / import process if the request is an import (step # 42). # 43). Here, also, the export process is a process for export from the workstation 6.

FIG. 12 is a flow chart showing the export storage processing in the file transfer processing unit 12.

Referring to FIGS. 1 to 7, in the export storage process, first, the physical file chick type of the file chick type 21 is read (step # 51).

The simple file name FID in the export command statement 33 and the terminal identification name ID of the workstation 6 are set in the physical file hina type simple file name variable and the terminal identification name variable, and the file name NFIW is determined. (Step # 52).

In the example shown in the figure, the simple file name is "ZA
IKO "and the identification name ID of the workstation 6 is" TOKYO ", the file name is" AAA.Z ".
AIKO. "TOKYO".

Along with this, the determined file name NFI
The W work file 23 is secured in a predetermined area (step # 53), and the file F in the DASD 3 is exported to the work file 23 (step # 54). File F
Is completed, a message to that effect is output to the workstation 6.

Next, the DB table hina type in the file hina type 21 is read (step # 55).

The simple file name FID in the storage command statement 34 and the terminal identification name ID of the workstation 6 are set in the DB table hina type simple file name variable and terminal identification name variable to determine the table name NFID. (Step # 56).

In this example, the table name NFID is "AA
A. ZAIKO. "TOKYO".

Then, the table information management table 22 is searched to obtain the database name NDB of the database DB in which the determined table name NFID is stored (step # 57). In this example, the database is DB1.

Based on the database name NDB, the table name NFID, and the file name NFIW of the work file 23, a load command statement for storing the file of the work file 23 in the database DB is created (step # 58).

The load command statement is executed to store the file data in the table TB of the database DB (step # 59).

When the storage of the table TB is completed, a message to that effect is output to the workstation 6 (step # 60).

FIG. 13 is a flow chart showing the extraction and transfer processing in the file transfer processing unit 12. In the extraction / import process, a process similar to the above-mentioned export / storing process is performed, and thus the description will be briefly given.

The file name NFIW is determined (steps # 71, 72), the work file 23 is secured (step # 73), the table name NFID is determined (steps # 74, 75), and the database name NDB is searched. (Step # 76).

Then, the database name NDB, the table name NFID, and the file name N of the work file 23.
Based on the FIW, an unload command statement for extracting the table data of the database DB into the file of the work file 23 is created (step # 77).

The unload command statement is executed to fetch the table data from the database DB and store it in the work file 23 (step # 78).

Thereafter, the work file 23 is changed to DASD.
The file is imported into 3 (step # 79).

Step # 57 and step # 76 described above.
In the table information management table 22, the table name NF
If the ID is not found, a message to that effect is output to the workstation 6, for example, as an error. Therefore, the workstation 6 specifies the database name NDB in order to newly create the table TB with the table name NFID.

FIG. 14 is a flow chart showing the table creating process.

The table TB is defined and created in the database DB of the specified database name NDB (step # 91), and the table name NFID is registered in the table information management table 22 (step # 92).

After being registered in the table information management table 22, the database name N is read by the table information management table 22.
The DB is searched, and the table data is extracted or stored in the searched database DB.

According to the above-described embodiment, the operator of the workstation 6 may specify the simple file name FID arbitrarily determined by the operator when making the transfer request, and the database name NDB of the host computer 2 is designated.
Since it is not necessary to specify the table name NFID, it is possible to easily specify the table TB to which data is to be transferred without being aware of the database environment, the operability is extremely good, and an operation error is unlikely to occur.

In general, since the database DB of the host computer 2 is often fixed according to the work content, it is not necessary to input the same database name NDB for each operation as in the conventional case, and the operability is improved. The improvement is remarkable.

Since the operator of the workstation 6 can easily cooperate with the distribution software normally used, the host cooperation can be realized by a normal operation, and the efficiency of the operation can be improved.

In the above embodiment, the identification name ID is "T".
The case where the transfer request is issued from the workstation 6 of "OKYO" has been described. However, the transfer request can be issued by designating the same simple file name FID from the workstation of another identification name ID. In that case, the identification name I
Since D is different, the table name NFID in the database DB is different, and therefore they are different tables TB from each other.

In the above embodiment, the chick type definition statement 31
Although the management table definition sentence 32 is input from the console 4 of the host computer 2, it is also possible to describe these in a program in advance and automatically execute them.

In the above embodiment, the file name NF
The IW and the table name NFID are composed of the project name, the simple file name FID, and the identification name ID, but the project name or this and the identification name can be omitted. Also, file name NFIW and table name NFID
, And the same, but they may be different.

In the above embodiment, the database DB
If there is only one, even if the table name NFID is not registered in the table information management table 22, the table TB is created without newly designating the database name NDB from the workstation 6 and It is possible to register in the table information management table 22.

In the above embodiment, the configurations of the host computer 2 and the workstation 6 can be variously changed. Therefore, one of the two nodes can be the terminal side or the host side.

In the above-described embodiment, the processing contents or processing order of the file transfer processing unit 12, the configuration of each unit of the data communication system 1, the processing contents and the like can be variously changed other than those described above.

[0084]

According to the present invention, an operator on the terminal side can easily specify a file for which data transfer is desired, without being aware of the database environment on the host side.

According to the second aspect of the invention, the file name can be determined easily and quickly.

According to the invention of claim 3, in response to transfer requests from a large number of terminal devices, different file names can be given to the respective terminal devices.

According to the invention of claim 4, the database D
When there are a plurality of Bs, the database DB storing them can be easily searched from the file name.

[Brief description of drawings]

FIG. 1 is a block diagram showing an example of a data communication system to which a data transfer control method according to the present invention is applied.

FIG. 2 is a diagram showing an example of a file chick type according to an embodiment of the present invention.

FIG. 3 is a diagram showing an example of a table information management table according to the embodiment of the present invention.

FIG. 4 is a diagram showing an example of a chick type definition sentence.

FIG. 5 is a diagram showing an example of a management table definition statement.

FIG. 6 is a diagram showing an example of an export command statement for a transfer request.

FIG. 7 is a diagram showing an example of a stored command statement for a transfer request.

FIG. 8 is a flowchart showing a file chick type setting process.

FIG. 9 is a flowchart showing a setting process of a table information management table.

FIG. 10 is a flowchart showing a transfer request operation.

FIG. 11 is a flowchart showing a transfer process.

FIG. 12 is a flowchart showing an export storage process in a file transfer processing unit.

FIG. 13 is a flowchart showing an extraction / population process in a file transfer processing unit.

FIG. 14 is a flowchart showing a table creation process.

[Explanation of symbols]

2 Host computer 6 workstations (terminal devices) 21 File Hina Type (DB File Hina Type) 22 Table information management table (file information management table) DB database NDB database name NFIW file name NFID table name (file name) FID simple file name ID identification name

Claims (5)

[Claims] 1. A data transfer control method for transferring data between a file of a terminal device (6) and a database (DB) provided in a host computer (2), comprising a transfer request at a terminal side. When inputting, the simple file name (FID) is specified as a parameter, the host side determines the file name (NFID) of the database (DB) based on the simple file name (FID), and the decided file name ( A data transfer control method characterized in that a file is stored in or extracted from a database (DB) by NFID. 2. A database (DB) on the host side
A DB file hina type (21) having a variable that should be the file name (NFID) of the device is created in advance, and when a transfer request is made from the terminal device (6), a simple file name specified as a parameter 2. The data transfer control method according to claim 1, wherein the file name (NFID) of the database (DB) is determined from the DB file chick type (21) based on (FID). 3. The DB file hina type (21) is a simple file name variable in which a simple file name (FID) specified as a parameter from the terminal device (6) is substituted, and the identification of the terminal device (6). 3. The data transfer control method according to claim 2, further comprising a terminal identification name variable into which a name (ID) is substituted. 4. A database name (NDB) and a file name (NFI) stored in each database (DB).
D) is provided and a file information management table (22) is provided, and the simple file name (F) is selected from a plurality of databases (DB) by referring to the file information management table (22).
The data transfer control method according to any one of claims 1 to 3, wherein a database (DB) storing a file having a file name (NFID) determined based on (ID) is searched. . 5. A data transfer control method for transferring data between a file of a terminal device (6) and a database (DB) provided in a host computer (2), comprising a transfer request at a terminal side. When inputting, specify the simple file name (FID) as a parameter, and on the host side, based on the simple file name (FID), the file name (NFIW) of the work file (23) and the file name of the database (DB) ( NFID) is decided, and each decided file name (NFIW) (NFI
D), the file on the terminal side and the work file (2
3) A data transfer control method, characterized in that data is transferred to and from the work file (23) and a database (DB).