JPH06139129A - Information processing system - Google Patents

Abstract

PURPOSE:To improve a reading or writing speed of a file from/in a data base system in each information processor with respect to an information processing system connecting plural information processors to the data base system for supplying data to the information processors through a communication network. CONSTITUTION:The data base system (server 102) supplies data to other information processors (clients 101) through the communication network (LAN 103). In the case of reading out or writing data from/in a file stored in the server 102 from a certain client 101, a logical communication line is opened between the server 102 and the client 101 at the opening processing of the file and disconnects the line at the time of closing the file. The reading/writing operation of files is executed by utilizing the opened communication line provided at the opening.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a plurality of information processing devices, a database system for supplying data to the plurality of information processing devices, and a communication network for connecting the plurality of information processing devices and the database system to each other. And an information processing system consisting of.

[0002]

2. Description of the Related Art In recent years, a plurality of information processing devices and a database system have been connected to a LAN (local area network).
An information processing system that is connected by a communication network such as the above and shares data among the plurality of information processing apparatuses is widely used.

As a communication control method in such an information processing system, a logical communication line between the information processing apparatus and the database system is opened at the start of data communication and when the data communication is finished. There is a method of disconnecting the logical communication line.

Further, in the database system, there are the following methods for controlling the execution of the task for performing the processing requested by the information processing apparatus. When switching tasks of the same type that operate in the same core block using the core block method, there is a method of rolling out the task of the core block to a fixed disk device and loading a new task in the memory.

[0005]

When the information processing apparatus reads a file on the database system, it is necessary to perform data communication at least three times, that is, a file open process, a read process, and a file close process. In the above system, a logical communication line is opened and closed between the information processing device and the database system every time data communication is performed. Therefore, in such a case, there is a problem that it takes time to open a logical line between the information processing apparatus and the database system, and the file reading speed becomes slow. The same can be said when writing to a file on the database system by using the information processing device.

Further, in the conventional method of controlling the execution of the task for performing the processing requested by the information processing apparatus in the database system, when a plurality of tasks of the same type are activated, those tasks cannot be switched at high speed. .
By the way, since a plurality of tasks for performing processing requested by the information processing apparatus are activated in response to requests from a plurality of information processing apparatuses, there is a problem that switching of the tasks takes time and the processing speed becomes slow. is there.

[0007]

A plurality of information processing devices,
In an information processing system including a database system that supplies data to the plurality of information processing apparatuses, and a communication network that connects the plurality of information processing apparatuses and the database system to each other, the information processing apparatus and the database system include A communication line control means for opening and disconnecting a logical communication line between them and a communication data control means for controlling transmission / reception of communication data are provided. The communication data is transmitted and received through a logical communication line established by the communication line control means.

Further, the information processing apparatus includes remote processing requesting means for requesting processing to the database system. The remote processing requesting means requests the database system for processing using the communication line control means and the communication data control means.

Further, the database system includes remote processing executing means for performing the processing requested by the remote processing requesting means. The remote processing execution means receives the processing request from the information processing device using the communication line control means and the communication data control means, executes the requested processing, and uses the communication data control means to display the processing result. Return to the requesting information processing measure.

The database system also comprises a memory allocating means for allocating the physical address space to the logical address space. Therefore, by using the memory allocating means, a plurality of physical address spaces that are allocated to the logical address space in which the task that executes the remote processing executing means operates are provided, and by switching the physical address spaces, the plurality of tasks can be switched at high speed. To be able to

Further, the database system is provided with a fixed disk device and means for saving and recovering the above tasks in the fixed disk device. When a certain number or more of the above tasks are activated, the means is used to The task is rolled in and rolled out.

[0012]

In the present invention, regarding the processing related to the reading and writing of the file on the database system, the logical line is connected when the file is opened, and the logical line is disconnected when the file is closed. Then, the operation of reading and writing the file can be performed at high speed by performing the operation through the logical line.

Further, regarding processing not related to reading and writing of files on the database system, a logical communication line is opened / closed for each process, whereby the line can be used efficiently.

Further, in the database system,
Since the task that performs the processing requested by the information processing device can be switched at high speed, the processing speed of the entire system can be improved.

[0015]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will be described below with reference to the drawings.

System Overview First, an example of a connection relationship between a plurality of information processing devices (hereinafter, referred to as clients) and a database system (hereinafter, referred to as a server) that provides data to the plurality of information processing devices. Is shown in FIG.

In the figure, 101a and 101b are clients, and 102 is a server. Client 101a
And 101b are connected to the server 102 by the LAN 103. This enables communication between the client 101 and the server 102.

FIG. 2 shows the client 101 shown in FIG.
3 is a block diagram showing a hardware configuration of a server 102. FIG.

First, the hardware configuration of the client 101 will be described with reference to FIG.

In the figure, 111 is a central processing unit (CP).
U), which requests various data, executes various programs related to communication, and controls peripheral devices. 11
A main memory (MM) 2 stores various programs related to data request, processing, communication, and data. Reference numeral 113 is a keyboard (KB), and an input by the user is performed via the keyboard (KB) 113.
Reference numeral 114 denotes a video memory (VRAM), the contents of which are displayed on a display / display device (CRT) 115.
A fixed disk device (HDD) 116 reads and saves various data used by the client 101. A communication control unit (CDRV) 117 communicates with the server 102 via the LAN 103. Reference numeral 118 is a bus for transferring data between these peripheral devices 112 to 117 and the central processing unit 111 (CPU).

Next, the hardware configuration of the server 102 will be described with reference to FIG.

In the figure, 121 is a central processing unit (CP
U), which requests various data, executes various programs related to communication, and controls peripheral devices. 12
A main memory (MM) 2 stores various programs related to data request, processing, communication, and data. Reference numeral 123 is a keyboard (KB), and an input by the user is performed via the keyboard (KB) 123.
Reference numeral 124 denotes a video memory (VRAM), the contents of which are displayed on a display / display device (CRT) 125.
A fixed disk device (HDD) 126 reads and saves various data provided to the client 101. A communication control unit (CDRV) 127 communicates with the server 102 via the LAN 103. Reference numeral 128 denotes a bus for transferring data between these peripheral devices 122 to 127 and the central processing unit 121 (CPU).

File management function specifications (related to remote file access) Outline of File System 1.1 File System System The file system system in the client 101 and the server 102 has a tree structure as shown in FIG.

The root directory 201 and the drive directory 202 have a system standard directory structure. The drive directory 202 is used to identify drives such as fixed disks (HD) 117 and 127. The identification number used to identify the drive directory 202 is called a drive number.

The directory 203 and the file 204 shown in FIG. 3 are fixed disks (HD) 117 and 12 respectively.
7 is constructed as shown in FIG.

In the figure, reference numeral 211 denotes a node block, which is provided in one-to-one correspondence with the file 204 or the directory 203. The configuration of the node block 211 is shown in FIG. The node block 211 has a directory attribute 221 indicating whether it is a directory or a file, an access right 223 that is information for restricting access, a remote attribute 222, and a mount number 224 (remote attributes and mount numbers will be described later. ), A user identifier for identifying the owner of the file 204 or the directory 204, a group identifier 225, a file size 225 which is the size of the file, a data block 213 or a directory block 2 corresponding to the node block 211.
It is composed of 12 block numbers 227a to 227n and a date 228 of created and updated. The block number is a number that uniquely indicates a position on the disc.

Reference numeral 212 is a directory block, and one or more directory blocks exist corresponding to one directory 203. The structure of the directory block is shown in FIG. The directory block 212 is a lower layer directory 203 included in the directory 212.
And the name 232 of the file 204 and the block number 231 of the node block 211 corresponding to them.

A data block 213 stores the contents of the file 204.

The directory 203 and the file 20
Operations such as creation and deletion of the file 4 and operations such as reading and writing of the file 204 are performed by using a supervisor call (hereinafter referred to as SVC) provided by a program that manages the file system (hereinafter, referred to as file management). To do. Table 1 is a list of SVCs provided by the file management in the client 101. Table 2 shows the server 10
2 is a list of SVCs provided by file management.

[0030]

[Table 1]

[0031]

[Table 2]

1.2 File Access Method A logical access method using a path name and a file number is used to access a file. In the logical access method, operations such as generation and deletion of the directory 203 and the file 204 are performed using the path name. Further, operations such as reading and writing of the file 204 are performed by opening the file using the path name and using the file number given at that time. When a file is opened, a file access control block (hereinafter referred to as FCB) that controls file access is generated in the file management, and subsequent file access is performed using this FCB. The file number and FCB will be explained in Section 6.1.

2. Overview of remote file access The concept of "remote mount" is used to access remote files.

The remote mount will be described with reference to FIG.

The remote mount means that a directory 242 (called a remote directory) existing in the server 102 is virtually connected to a directory 241 (called a local directory) of the client 101, so that the directory 23 below the directory 242 is connected.
0R or file 204R as if the client 20
It is treated as if it were on one disk. After remote mount is performed, the local file 20
Similar to the access to the 4L or the local directory 203L, by specifying the path name, all the files 204R under the remote directory 242 incorporated as a subdirectory can be accessed.

According to this method, since the remote file 204R can be accessed from the application program (hereinafter abbreviated as AP) just like the local file 204L, it is not necessary to rewrite the AP.

3. Remote Mount of Directory 3.1 Mount Table The structure of the mount table 250 is shown in FIG. The mount path name 251 stores the path name of the remote directory 242 remotely mounted on the local directory 241.

3.2 Remote Directory Mount Processing Remote directory 24 in client 101
An outline of the mounting process of No. 2 is shown in FIG.

In the mount processing 260 of the remote directory 242, the path name of the remote directory 242 is registered in the mount table 250 in the mount path name 251 (step 261), and the identification number (mount number) of the registered mount path name 251 is set to the remote. It writes to the mount number 224 of the node block 211 of the mounted local directory 241 (step 262). Then, the remote attribute 222 of the node block 211 of the local directory 241 is set to remote (for example, 1). In addition, the file 20 is stored under the locally mounted remote directory 241.
If 3 or the like exists, the file cannot be accessed.

3.3 Remote directory unmount process Remote directory 24 in client 101
An outline of the unmount process of No. 2 is shown in FIG.

The remote unmount process 270 returns the remote attribute 222 of the node block 211 of the local directory 241 for unmounting the remote directory 242 to local (for example, 0), and mounts the mount number 244 specified in the node block 211. The contents of the path name 251 are cleared. However, when there is a remote file 204R that is open under the local directory 241, the requester of the process is notified and the process is interrupted.

S for remote mounting / unmounting
The VC is provided for the file management of the client 101 and not for the file management of the server 102.

4. FIG. 11 shows an outline of file access processing in file management of the file access client 101.

In the file access processing 280, first,
Is it access to remote file 204R,
It is determined whether the access is to the local file 204L (step 290). This determination is made by checking the parameter of the SVC when the file management SVC is issued. The parameter to check is either a path name or a file number. Table 3
6 shows the classification of SVC according to the type of parameter used for the determination in step 290.

If it is determined in step 290 that the access is to the local file 204L, the fixed disk device 116 (HD) is accessed (step 300). For access to the remote file 204R, the communication control unit 117 (CDR
V) is accessed (step 310). The remote file access process 310 will be described in detail later.

After step 300 or step 310 is completed, the SVC execution result is returned to the SVC issuer (step 320).

[0047]

[Table 3]

4.1 Access Judgment by Path Name Of the judgment processing of step 290, the outline of the remote file access judgment processing 290a by path name is shown in FIG.
2 shows.

The determination based on the path name is divided into a case where an absolute path from the root directory 201 is designated and a case where a relative path from the current directory is designated (step 291). The current directory will be explained in Chapter 5.

When accessing the remote file 204L, the mount path name 251 of the mount table 250 is used to convert the path name into an absolute path name from the root directory 201 in the server 102.

Absolute Path Designation When a path from the root directory 201 is designated, whether the remote attribute 222 of the node block 211 corresponding to the directory 203 is remote or local is determined according to the path from the root directory 201. The remote attributes 22 are checked in order (step 292).
It is determined whether or not there is a directory 203 in which 2 is remote (step 293). If it exists, it is assumed that the access is to the remote file 204R on the server 102. Client 1 if not present
It is assumed that the access is to the local file 204L of 01.

When Relative Path is Specified First, it is determined whether the current directory is the client 101 side or the server 102 side (step 294). Whether the current directory is in the server 102 or the client 101 is determined by the drive number in the current directory management area (see Chapter 5 for details).

I) When the current directory is on the client side As in the case where the absolute path is specified, the remote attribute 222 of the node block 211 corresponding to the directory 203 is remote or local according to the path from the current directory. Are sequentially checked (step 295), and it is determined whether or not the directory 203 whose remote attribute 222 is remote exists (step 296). If it exists, it is assumed that the access is to the remote file 204R on the server 102. If it does not exist, it is assumed that the access is to the local file 204L of the client 101.

Ii) When the current directory is on the server side: Access to the remote file 204R on the server 102 is assumed.

4.2 Access determination by file number Access to an open file is performed by using the file number. Management of open files, FCB, etc. are explained in Section 6.1. Here, the determination method will be described.

FIG. 13 shows an outline of the remote file access determination processing based on the file number. In the remote file access determination processing 290b, first, the client 1
The FCB corresponding to the file number on 01 is read (step 297). In the FCB, if the drive number has the remote attribute (most significant bit: 1), it is assumed that the access is to the remote file 204R.
If the drive number has the local attribute, it is assumed that the access is to the local file 204L.

4.3 Remote File Access Process 4.3.1 Outline of Remote File Access Process FIG. 14 shows an outline of the remote file access process 310 in the client 101.

In the remote file access processing 310, first, a transport connection, which is a logical communication line, is established with the server 102 (step 311). Next, data (RPC data 660) necessary for the remote process task to issue the SVC is transmitted to the remote process task 600 (step 31).
2). After that, from the remote process task 600, S
The VC execution result (RPC turn data 670) is received (step 313). Finally, the transport connection established in step 311 is disconnected (step 314). The remote process task 600 executes the RPC from the client 101 in the server 102.
The data 660 is received (step 610), and the SVC requested by the client 101 is issued (step 62).
0), the execution result of the SVC (RPC return data 67
This is a task for performing processing of returning 0) to the client 101 (step 630). The remote process task 600, RPC data 660, RPC return data 6
70 will be described in the remote process task function specification.

However, in the SVC relating to the reading and writing of files, one transport connection is established for one file number. That is, in the SVC of OPEN or CREATE (when an existing file is specified), the process of establishing the transport connection in step 311 and the processes of step 312 and step 313 are performed.
The cutting process 314 is not performed. Conversely, SVC CLOSE
Then, the process 311 for establishing the transport connection is not performed, and the processes of steps 312 and 313 are performed through the transport connection corresponding to the file number to disconnect the transport connection (step 314). The correspondence between the file number and the transport connection is stored in the FCB. In other SVCs related to file reading and writing, the processes of establishing 311 and disconnecting 314 of the transport connection are not performed, but the processes of step 312 and step 313 are performed through the transport connection corresponding to the file number.

The file read / write related SVCs are CREATE, OPEN, CLOSE, READ,
It means 6 SVCs of WRITE and MVFPNT.

4.3.2 Securing communication parameter area When a remote file is accessed, the client 10
1, the SVC parameter received by the file management from the SVC issue request source (for example, AP) is set to the RPC.
Convert to data 660. At this time, RPC data 660
An area for setting is required. Further, when the RPC return data 670 is received from the remote process task 600, an area for storing the received RPC return data 670 is also required. These areas required for communication by the file management will be referred to as communication parameter areas.

As the communication parameter area, a disk access buffer possessed by file management is used.
FIG. 15 shows an outline of disk buffer management. The disk buffer 340 releases the most recently unreferenced buffer by LRU (Least Recent Use).
d) It is managed by the method. A buffer management area 330 is used to manage the buffer. One buffer 340
In contrast, one buffer management area 330 corresponds.

The update flag 331 in the buffer management area 330 is a flag indicating whether or not the contents of the buffer 340 have been updated. When the content of another portion of the disk is stored in the buffer 340, the released content of the buffer 340 is written to the disk if the update flag 331 is set. Link field 332
Is a pointer for arranging the buffer 340 in ascending order of reference time. By changing the value of the link field 332, the order of the buffer 340 is changed. The drive number 333 and the block 334 are for storing the position on the disk where the contents of the buffer 340 are stored. The reservation flag 335 is a flag indicating whether or not the corresponding buffer 340 is reserved.

FIG. 16 shows an outline of the processing for securing the communication parameter area.

The buffer management areas 330 are arranged in ascending order of reference time. This sequence is called LRU management. In the figure, 345 is a pointer indicating the beginning of LRU management.

The communication parameter area is set at the head of the LRU management, that is, by setting the reservation flag 334 of the buffer management area 330x that has not been referenced most recently, so that the buffer 340 corresponding to the buffer management area 330x is set.
Secure. Then, by changing the value of the link field 332 of the buffer management area 330x, the LRU
The buffer management area 330x is moved to the end of management. At that time, in the drive number 333 of the buffer management area 330x, the highest number of the mount number 224 of the node block 211 corresponding to the remote-mounted directory 241 existing in the absolute path name of the remote file 204R to be accessed. The bit set to 1 is stored. Further, the block number 334 stores the identifier of the transport connection established in step 331. (The above is the process of securing the communication parameter area) After disconnecting the transport connection in step 314, the link field 332 of the buffer management area 330x corresponding to the secured buffer 340 is released so as to be released from the buffer 340 used for communication. Value is changed to move the buffer management area 330x to the head of LRU management. Then, the secured state is cleared by resetting the secured flag 335 in the buffer management area 330x. At that time, the update flag 331 of the buffer management area 330x is reset. By setting the update flag 331 to the reset state, when the contents of another portion of the disk are stored in the buffer 340, the contents of the buffer 340 are not written to the disk. (that's all,
Communication Parameter Area Release Processing) The communication parameter area securing processing is started when the transport connection establishment 311 is performed. Further, the communication parameter area release processing is activated when the transport connection release 314 is performed.

5. Current directory file 204
Often only the files under 03 are used. Therefore, the path name up to the directory 203 is stored, and in the subsequent designation of the file 204, the access can be made by designating only the file name of the target file 203.

The current directory can be placed not only in the local directory 203L, but also in the remote-mounted directory 241 and the subdirectory 203R under the directory.

The structure of the current directory management area 350 for managing the current directory is shown in FIG.
The components of the current directory management area 350 are
Current directory is local directory 203L
2 is different from the case where the remote mount is performed in the directory 241 or the remote directory 203R.

FIG. 17A shows the configuration of the current directory management area 350L when the current directory is in the local directory 203L. The drive number 351L and the node block number 352L correspond to the node block 21 corresponding to the local directory 203L.
This is information for determining the position of the first disc on the disc. An absolute path name from the root directory 201 of the local directory 203L is stored in the path name 353L. Current directory is local directory 20
In the case of 3L, the area of 354L becomes empty.

FIG. 17B shows the structure of the current directory management area 350R when the current directory is the remote-mounted directory 241 or the remote directory 203R. In the mount number 351R, the highest bit of the mount number 224 of the node block 211 corresponding to the remote-mounted directory 241 existing in the middle of the path name to the current directory is stored.
An absolute path name from the root directory 201 to the current directory is stored in the path name 353R. In the remote file name position 354R, the head position of the name of the subdirectory 203R under the directory 241 on which remote mounting is performed is stored. In the example of FIG. 7, the current directory is "/ HD1 / DEF
/ PQR ”, the position of the underlined portion becomes the remote file name position 354R.
In this case, the area of 352R becomes empty.

To change the current directory, use SVC
CHDIR is used. When changing the current directory to the remote directory 203R, the remote process task is instructed to issue the SVC CHDIR,
Make sure the target directory actually exists.

6. Remote file open / close 6.1 Open file management The file number is the file 204 open (SVC
OPEN or SVC CR for existing file
This is an identifier given from the file management to the specified file 204 at the time of issuing ATE). Subsequent accesses such as reading and writing of the file are performed using this file number.

File access control block (FCB)
Is an area for storing various information necessary for accessing the file 204. The structure of FCB is shown in FIG.

FIG. 18A shows the local file 204.
It is a configuration of FCB360R when L is opened.
The access count 361L is the number of tasks accessing the file 204L by using the FCB 360R. The open mode 362L restricts reading and writing of the opened file.
The privilege instruction flag 363L is a flag for designating whether or not a file can be shared and accessed. Open mode 362L, privilege instruction flag 363L
Is passed to the file management as a parameter of SVC OPEN and CREATE. Write flag 364L
Is set when writing is performed on the opened file 204L. The drive number 365L and node block number 366L are for the opened file 204
This is information indicating the position on the disk of the node block 211 corresponding to L.

FIG. 18B shows the remote file 204.
It is a configuration of FCB360R when R is opened.
The access count 361R is the same as the access count 361L. However, when the remote file 204R is opened, the FCB is not shared, so the value is always 1. The area of 362R is empty. The remote file number 363R stores the file number when the remote process task opened the file 204R in the server 102. Write flag 364R
Is the same as 364L, but the value is always in the reset state. In the mount number 365R, the highest bit of the mount number 224 of the node block 211 corresponding to the remote-mounted directory 241 existing in the path name of the opened remote file 204R is stored. To do. Connection identifier 3
The identifier of the transport connection established in step 311 is stored in 66R.

FIG. 19 shows an outline of management of open files. The correspondence relationship between the file number and FCB 360 is a many-to-one relationship. The open file management area 370 is used to define this correspondence. The identification number of the open file management area 370 becomes the file number. The open file management area 370 has a file pointer 3
71 and FCB number 372. File pointer 3
Reference numeral 71 indicates a read or write start position of the open file 204. The FCB number 372 is an identification number of the FCB 360 being used.

6.2 File Open 6.2.1 Open Local File The outline of the open processing of the local file 204L is shown in FIG.
It shows in 0.

In the local file open processing 380, first, an open open file management area 37
0 is secured (step 381). The identification number of the secured open file management area 370 is the file number. Next, the FCB360 is acquired, and the acquired FCB36
The identification number of 0 is stored in the FCB number 372 of the open file management area 370 (step 382). Then, the access count 381 of the obtained FCB 360 is incremented by 1, and the other data 382 to 386 are also set according to the SVC parameters (step 383).

6.2.2 Opening Remote File Remote File 204R in Client 101
FIG. 21 shows an outline of the open processing of.

The remote file open process 390
A transport connection is established with the server 102 (step 311), RPC data is transmitted to the remote process task, and an issue of SVC OPEN is requested (step 312). Then, after receiving the execution result of SVC from the remote process task (step 313), the open file management area 370 is secured in the client (step 381) and the FCB 360 is acquired (step 382) as in the case of the local file. . In the acquired mount number 361R of FCB360, the opened remote file 204R
The mount number 244 of the mount number 244 of the node block 211 corresponding to the remote-mounted directory 241 existing in the middle of the path name is stored. The connection identifier 366R stores the identifier of the transport connection established in step 311. Further, for the remote file number 363R, the remote process task is executed in the server 102 according to the SVC execution result received in step 313.
The file number when the file 204R is opened is read and stored. The access number 361R is set to 0, and the write flag 364R is reset. (Step 391).

Access to the opened remote file 204R in the client 101 is performed using the file number on the client 101, as in the case of the local file 204L.

6.3 File Closing 6.3.1 Local File Closing FIG. 22 shows an outline of the local file closing processing.

In the local file close processing 400, the open file management area 3 specified by the file number passed as the parameter of SVC CLOSE.
70 is released (step 401). Next, the access number 361 of the FCB 360 specified by the FCB number 372 of the released open file management area 370 is set to 1
Decrease (step 402). If the access count 361 of the FCB 360 is 0, that FCB 360 is empty.

6.3.2 Remote File Closing FIG. 23 shows an outline of remote file closing processing in the client 101.

In the remote file close processing 410, the RPC data is transmitted to the remote process task and the SVC CLOSE issue is requested (step 31).
2). The SVC execution result is received from the remote process task (step 313). Next, the transport connection with the server 102 is disconnected (step 314). The identifier of the transport connection to be disconnected is the FC specified by the FCB number 372 of the open file management area 370 specified by the file number.
It is stored in the connection identifier 366R of B360. After that, the same processing as the closing of the local file is performed (steps 401 and 402).

7. Remote file read / write processing 7.1 Speed-up of remote file read / write processing FIG. 24 shows the data flow during remote file access.

When the SVC is issued from the AP 425, the S
The parameters of the VC are passed to the file management, and in the disk buffer 340 secured as the communication parameter area,
Set in the form of PRC data (SVC parameter 43
1 flow). Then, the RPC data is stored in the communication buffer 4
After transferring to R.20, it transmits to the server 102 (flow of RPC data 660).

The RPC return data returned from the remote process task is temporarily stored in the communication buffer 420.
Then, the data is transferred to the disk buffer 340 (flow of RPC return data 670). Then, in the file management, the execution result of the SVC is set to the issuer A of the SVC.
Notify P425 (flow of SVC execution result 432).

By the way, reading a file (SVC
READ), writing (SVC WRITE),
Large amount of data transfer is involved. Therefore, in order to perform high-speed processing, the number of times of data read from the remote file or data written to the remote file is reduced. That is, in SVC READ, the data read from the remote file is stored in the disk buffer 3
40 to AP 425 without passing through 40
(Read data 436 flow). Further, in the SVC WRITE, the data to be written to the remote file is directly transferred from the AP 425 to the communication buffer 420 without passing through the disk buffer 340 and then transmitted to the server 102 (write data 435).
Flow of).

7.2 Divided Read / Write Remote Process Task SVC REA of Server 102
When requesting issuance of D, it is not possible to read out more than the size of the buffer of the remote process task at one time. Therefore, the SV issued by AP425
When the C READ parameter is used to instruct to read data larger than the buffer size of the remote process task, the remote process task is divided into a plurality of times to request the remote process task to issue the SVC READ. For example, if the buffer size of the remote process task is 6 Kbytes and the AP 425 instructs the remote file 204R to read 15 Kbytes of data, then in file management, the remote process task can read 6 Kbytes, 6 Kbytes, and 3 Kbytes. 3 times SVC REA
Request the issuance of D.

Even in SVC WRITE, READ
Same as macro, SVC issued by AP425
When the WRITE parameter instructs writing of data larger than the buffer size of the remote process task, the remote process task is divided into a plurality of times and the remote process task is requested to issue the SVC WRITE.

8. Search for remote file To search the file 204 and directory 203, use SV
C FIND and FNEXT are used. These S
File 20 found as a result of searching using VC
4 or the position information of the directory 203 on the disc is stored in the file search area, and the next FNEXT
It is used when issuing.

The structure of the file search area 440 is shown in FIG.
5 shows.

The file search area 440 includes a drive number 441, a block number 442, and a position 44 from the beginning.
It consists of three. The drive number 441 is the drive directory 2 to which the file 204 found as a result of the search belongs.
The identification number of 02 is stored. In block number 442,
The block number of the node block 211 corresponding to the parent directory of the found file 204 is stored. The position 443 from the head stores the number indicating the position of the file name of the found file 203 in the directory block 212 indicated by the block number 227 of the node block 211. Even when the directory 203 is searched, the structure of the file search area 440 is the same.

In the client 101, the SVC F
If the IND is issued and the target is a remote file, the file management is executed by the remote process task 600.
Request issuance of VCRFIND. SVC RFIND
Then, in addition to the execution result of SVC FIND, server 1
The value of the search file area 440 in 02 is returned.
Therefore, the file management of the client 101 returns the part of the SVC FIND execution result in the SVC execution result (RPC return data) received from the remote process task 600 to the SVC issuing source AP, and
Client 101 for the value part of the search file area
In the search file area 440. At that time, the most significant bit of the drive number 441 is set to 1.

SVC FNEXT is SVC FIND,
Alternatively, the search is started from the position where the search is finished by FNEXT, that is, the position designated in the search file area 440.

When the SVC FNEXT is issued, the file management refers to the most significant bit of the drive number 441 of the search file area 440, and when it is 1, requests the remote process task to issue the SVC RFNEXT. At this time, by passing the contents of the search file area 440 in the client 101 (the most significant bit of the drive number 441 is returned to 0) to the remote process task as one of the parameters of SVC RF NEXT,
The server 102 can also start the search from the previous search end position. In SVC RFNEXT,
Similar to SVC RFIND, since the value of the search file area 440 in the server 102 is returned in addition to the execution result of SVC FNEXT, the same processing as in SVC FIND is performed.

Functional Specification of Server Manager Task 1. The purpose of the server manager task is to open a transport connection, which is a logical communication line, between the client 101 and the server 102 in response to a request from the client 101, and activate a remote process task corresponding to the transport connection. It is to be.

The server manager task is the server 10
2 is a resident system task.

The server manager task is the server 10
There is always only one on the two sides.

The server manager task is the server 102
It exists only on the side. It does not exist on the client 11 side.

-The server manager task powers off.
Does not end.

The server manager task is started when the system is initialized.

For remote process tasks,
Refer to the functional specifications of remote process task.

1.1 Functional Outline The role of the server manager task is to accept a request from the client 101 and activate a remote process task that processes the request.

The outline of the function of the server manager task is shown below.

(1) Initial setting The connection request for the transport connection (request for opening the transport connection) received from the client 101 is started, and the environment is set for realizing the function as the server.

(2) Opening a transport connection The connection request for the transport connection received from the client 101 is accepted, and the transport connection corresponding to the request is opened.

(3) Activation of remote process task A remote process task corresponding to the transport connection established in (2) is generated and activated.

(4) Deletion of remote process task The unnecessary remote process task in the dormant state where the processing is completed is deleted.

1.2 Outline of Processing FIG. 26 shows an outline of processing of the server manager task.

The server manager task 500 sets the environment for functioning as a server (process 51).
0), accepts a connection request from the client 101, and opens a transport connection corresponding to the connection request (process 520). Then, the remote process task corresponding to the transport connection is activated (process 530).

Also, the processing is terminated and the dormant is periodically executed.
The unnecessary remote process task in the state is checked and deleted (process 540).

<Role Division of Server Manager Task and Remote Process Task in Communication> The server manager task 500 receives the connection request from the client 101 (process 520) to activates the remote process task (process 530) The remote process task is deleted (process 540), and the client 1
The actual data communication corresponding to the request from 01 and the release of the opened transport connection are performed by the remote process task.

2. Communication between client and server and server manager task In order to clarify the role of the server manager task 500, a task on the client 101 side (request source process 6
A description will be given of a processing procedure when 50) uses resources on the server 102 side (hardware resources such as printers, document files, software resources such as programs).

FIG. 27 shows an outline of the communication procedure between the client 101 and the server 102. Server manager task 5
28 shows the relationship between 00 and peripheral tasks related to communication between the client 101 and the server 102.

The request source process 650 on the client 101 side uses the communication control 560 to make a connection request.

The server manager task 500 on the server 102 side accepts the connection request using the communication control 560s and opens the transport connection 570.

At this point, the server manager task 500 on the server 102 side and the request source process 550 on the client 101 side have their transport connections 570.
Gets the connection identifier, which is the identifier of.

The server manager task 500 on the server 102 side activates the remote process task 600 in response to the transport connection 570 opened in step, and passes the connection identifier acquired in step to the remote process task 600.

The remote process task 600 started by the request source process 55 using the transport connection 570 identified by the connection identifier.
0 (data transmission and data reception using the communication control 560) is performed, and the processing instructed by the request source process 550 on the client 101 side is performed.

At the end of the communication, the request source process 550 on the client 101 side or the remote process task 600 on the server 102 side releases the transport connection 570 identified by the connection identifier using the communication control 560.

The remote process task 600 on the server 102 side terminates the task after releasing the transport connection 570.

The remote process task 600 that has finished processing and is in the dormant state is deleted by the remote process task deletion processing 540 that the server manager task 500 regularly performs.

3. Processing 3.1 Initial Processing FIG. 29 shows an outline of the initial processing 510.

A "connection request acceptance start (LISTEN)" SVC of communication control 560 is issued (step 51).
1) It is determined whether the SVC has ended normally (step 512). When the processing is normally completed, acceptance of the connection request from the client 101 is started.
When the above ends, the server manager task 500 is ended.

The initial process 510 is performed immediately after the server manager task 500 is started by the initial process of the basic OS.

3.2 Connection Opening and Remote Process Task Activation The server manager task 500, which is in the connection request accepting state, always waits for a connection request from the client 101 and is held in the connection waiting queue of the communication control 560. Accept the connection requests in sequence. Thereby, the transport connection 570 corresponding to the connection request is opened.

Next, the transport connection 5
The remote process task 600 corresponding to 70 is generated and activated. Remote process task 600 to be started
Is the maximum number of transport connections 570 defined by the communication control 560.

The procedure of the process 520 will be described below with reference to FIG.

“Connection request acceptance (ACCEP
T) ”SVC is issued and a connection request from the client 101 is awaited (step 521). At this time, SV
As a return value of C, "connection identifier" is acquired. Next, it is determined whether the SVC has ended abnormally (step 522). At this time, if there is no connection request from the client 101 and the SVC ends due to timeout, it is reissued. If the SVC ends due to an error other than timeout, the server manager task 50
0 is ended (step 513).

“Task Creation (CTASK)” SVC
Is issued to generate the remote process task 600 (step 531). Next, it is determined whether the SVC has ended abnormally (step 532). If the SVC ends abnormally, the server manager task 500 is ended (step 513).

"Start Task (QSTRT)" SVC
Is issued and the remote process task 600 generated by
Is activated (step 533). At that time, "QSTR
As a parameter of the T ”SVC, the connection identifier acquired in (3) is passed to the remote process task 600.
Next, it is determined whether the SVC has ended abnormally (step 534). When the SVC ends abnormally, the remote process task 600 generated in (8) is deleted (step 580) and the server manager task 500 is ended (step 513).

The started remote process task 60
The task number of 0 is stored in the task number table (step 535).

Every time 10 remote process tasks are activated, the dormant task deletion processing 540 for deleting the remote process task in the dormant state is executed (step 536). This processing 540 will be described in detail in Section 3.3.

Returning to processing 521.

3.3 Deletion of Remote Process Task After the remote process task 600 finishes processing,
It remains in the dormant state and needs to be deleted. For that purpose, the server manager task 500 performs the following processing.

When the remote process task 600 is activated, the task number of the remote process task 600 is stored in the task number table in the server manager task 500.

Remote process task 600 to 10
Every time it is started, do of the remote process task 600 of the task number stored in the task number table
The remote process task 600 in the rmant state is deleted. Then, the task number of the remote process task 600 is deleted from the task number table.

3.4 Abnormal Processing (1) When each SVC abnormally ends (except when the connection request acceptance (ACCEPT) SVC abnormally ends due to timeout), the processing of the server manager task is ended (functions as a server). It will not be possible to use functions other than the server).

Remote Process Task Creation (CTA
If SK) ends abnormally, the connection 570 is disconnected, and then the server manager task is ended.

Connection request acceptance start (LIST
EN), the server manager task 5
Ends 00.

“Connection Request Acceptance (ACCEP
T) ”When the SVC abnormally ends due to a cause other than a timeout, the server manager task 500 ends.

“Start Task (QSTRT)” SVC
If is abnormally terminated, the remote process task 600 which is to be started is deleted, the connection is disconnected, and then the server manager task 500 is terminated.

(2) Accepting connection request (ACCE
If the PT) SVC abnormally ends due to a timeout, the connection request acceptance (ACCEPT) SVC is reissued. 1. Outline 1.1 Outline of function The purpose of the remote process task is client 101
Accessing the resource on the server 102 side on behalf of the process on the server side. Here, the process on the client 101 side is a request source process (task, sub OS, etc.) that performs processing using resources on the server 102 side, and the resources on the server 102 side are hardware resources such as printers , Or software resources such as document files and programs.

The access of the resources of the server 102 from the client 101 is mainly performed by RPC (Remote Procedure).
Call) form. That is, when an SVC (Super Visor Call) is issued on the client 101 side, the parameters of the SVC are transferred to the remote process task on the server 102 side, and the remote process task reissues the SVC on the server 102 side. Then, the remote process task transfers the processing result of the SVC to the client 101 side.

The remote process task is created and activated by the server manager task 500 in response to a request from the client 101.

The remote process task is the server 1
It exists only on the 02 side.

The remote process task is a non-resident task and can create and activate a maximum number of transport connections, which is limited by communication control.

-For the server manager task 500, refer to the server manager task function specifications.

1.2 Outline of Processing FIG. 31 shows an outline of processing of the remote process task 600. The outline of the processing of the remote process task 600 is shown below.

(1) RPC data reception processing 610 RPC data (consisting of SVC command or the like) for determining the type of processing to be performed by the remote process task 600 is received from the request source process of the client 101.

(2) RPCSVC issuance process 620 Issues an SVC (for the OS of the server and the sub OS) corresponding to the RPC data received in (1).

(3) RPC return data transmission processing 63
0 The processing result of the SVC issued in (2) is returned to the client 101 as RPC return data.

(4) Termination process 640 Release of transport connection (connection may not be released depending on the type of process required for the process of the remote process task 600).

), And remote process task 60
The end of 0 is performed.

2. Communication between client / server and remote process task The communication procedure between the client 101 and the server 102, and the relationship between the server manager task 500 and the remote process task 600 in communication are described in the server manager task functional specification.

The division of roles of the server manager task 500 and the remote process task 600 in communication is as follows:
It is as follows.

Server manager task: acceptance of transport connection request.

Invoking the remote process task 600.

Remote process task: sending and receiving data.

Release of transport connection.

3. Communication Protocol 3.1 Communication Sequence FIG. 32 shows a communication sequence between the request source process 650 on the client 101 side and the remote process task 600 on the server 102 side.

Data transferred between the request source process on the client 101 side and the remote process task 600 on the server 102 side includes RPC data 660 and RPC data 660.
There are two types of return data 670.

The remote process task 600 receives the RPC data 660 from the request source process 650 on the client 101 side, performs the process designated by the RPC data 660, and outputs the result of the process as RPC return data 670. Return to process 650.

The RPC data 660 and the RPC return data 670 can be divided into a plurality of data and transferred. This is a function that corresponds to the case where the amount of data that can be sent at one time is limited by the communication control, or when it is convenient to divide and send the data (such as sending the data body and other parts separately). .

3.2 Frame Format of RPC Data FIG. 33 shows the frame format of the RPC data 660 sent from the request source process 650 on the client 101 side to the remote process task 600 on the server 102 side.

The remote process task 600 uses this R
The PC data 660 is analyzed, and the SVC corresponding to the contents of the RPC data 660 is issued.

The meaning of each field of the RPC data 660 is shown below. Also, from the client 101 to the server 1
36 shows an example of the RPC data 600 sent to the H.02.

(1) RPC type code 661 Indicates the type of RPC (Remote Procedure Call).

0: RPC data 66 for issuing SVC
Indicates 0.

1 to FFFF (hexadecimal): (undecided) (2) SVC issuance control code 662 The form of SVC issuance processing is shown (see Table 4). The meaning of each bit is shown below.

2 ⁷ : (Unused. 0 is set.) ²⁶ : (Unused. 0 is set.) 2 ⁵ : Task end ............ Remote process task 600 is ended after SVC is issued. Specify whether or not to survive.

* 1: End.

0: Survival.

In the case of general SVC, RPC data 6
Prior to the reception of 60, the remote process task 600 is activated and a connection is established. The remote process task 600 issues the designated SVC once and then releases the connection and self-destructs (specifies 1). However, for example, file management SVC (OPEN, REA
D, WRITE, CLOSE, MVFPNT), the remote process task 6 before receiving the RPC data 660 of SVC (OPEN).
00 is started and a connection is established, and the remote process task 600 executes SVC (OPEN, READ, WRITE, M
VFPNT) RPC data 660 is received and the corresponding SVC is received.
Is issued, the SVC (CLOSE) RPC data 660 is received, the SVC is issued, and then the connection is released to self-destruct. In other words, in SVC (OPEN, READ, WRITE, MVFPNT), S
The remote process task 600 does not self-destruct even after issuing the VC.

2 ⁴ : Status return ............
When the SVC is issued, the end state (status) of the SVC is indicated by the RPC return data 670 and the requesting process 6
Specify whether to reply to 50.

* 1: Reply.

0: Do not reply.

2 ³ : SVC parameter ............ Specifies whether or not the SVC to be issued has a parameter.

0: None

2 ² : Data return form ............
The method of returning the processing result of the issued SVC to the request source process is specified (see FIG. 34). When the value of is 0, it is optional. 0: Return the parameter area 690. (Fig. 34
(1)) * 1: Return the return data area 700. (Fig. 34
(2)) The parameter area 690 is an area for storing input / output parameters of the SVC. The return data area 700 is a dedicated area for storing the output of SVC.

2 ¹ : Function code ............
Specifies whether the issued SVC has a function code. It is also designation of the presence or absence of the field 664 of the function code of (4).

* 1: Yes

0: None

2 ⁰ : SDB configuration method ... Designates the creation format of the SDB of the SVC to be issued (see FIG. 35). When the value of is 0, it is optional.

0: A parameter area 690 is provided in the SDB 710a to set SVC parameters. (Fig. 3
5 (1)) * 1: Parameter area 690 outside the SDB 710b
And set the SVC parameters. (Fig. 35
(2))

[0189]

[Table 4]

(3) SVC number 663 Indicates a number (SVC number) for identifying the SVC to be issued.

(4) Function code 664 Specifies a function code that specifies the function of the SVC.

This function code field exists only when the SVC issuance control code 662 specifies that there is a function code.

(5) Parameter cell 680 The parameters of the SVC will be described (for both parameters that are input and output to the SVC). One parameter cell 680 corresponds to one parameter of the SVC. The parameter cell 680 is composed of the following fields.

(A) Parameter type 681: The format of the SVC parameters stored in the parameter cell 680 is shown (see Table 5). The meaning of each bit is shown below.

2 ⁷ : (Reserved. 0 is set.) ²⁶ : (Unused. 0 is set.) ²⁵ : (Unused. 0 is set.) 2 ⁴ : (Unused. 0 is set.) set to) 2 ^3. time parameter creation of free setting flag ............ SVC, when the data length 682 is an odd number of bytes of the parameter associated with the parameter cell 680, the parameters of word boundaries by adding 1 byte free bets Specify whether to do or not.

0: It is a word boundary.

* 1: No change.

2 ² : Data present flag: Describes the presence / absence of data 685 from the request source process 650. When the parameter cell 680 corresponds to the input data to the SVC, 1 is specified, and when it corresponds to the output data (processing result) from the SVC, 0 is specified.

0: None

* 1: Advantageous.

2 ¹ : SVC passing type ............ The value of the data 685 in the parameter cell is set to the SVC parameter corresponding to the parameter cell 680 or the data 68 in the parameter cell is set.
Specifies whether to set the address of 5 • 0: data.

* 1: Address.

2 ⁰ : Data end flag ............ Designates the presence or absence of the following parameter cell 680. 1 is designated in the last parameter cell to indicate the end of the RPC data 660.

0: Yes

* 1: None (final parameter cell).

[0206]

[Table 5]

(B) Data length 682: The number of bytes of input or output data to the SVC. The number of bytes in the data field 685 is not limited.

When the parameter cell 680 corresponds to the output data from the SVC, it indicates the data length of the output data. However, since the output data is corrected to the word boundary and set in the RPC return data 670, it is not limited to the data length of the field storing the output data in the RPC return data 670.

When the parameter cell 680 corresponds to the input data to the SVC, it indicates the data length of the input data. However, since the input data is corrected to the word boundary and set in the parameter cell 680, it is not limited to the data length of the data field 685 in the parameter cell 680.

(C) Group number 683 ............ SV
When the output data from C is divided and transmitted to the request source process 650 of the client 101, the position of dividing the data and the transmission order are controlled (see section 3.3).

The output data from the SVC corresponding to the parameter cell 680 of the same group number 683 is transmitted to the request source process 650 of the client 101 by one data transmission (DSEND) SVC.

It is meaningful only when returning the return data area 700 (it is meaningless when returning the parameter area 690. However, the field on the parameter cell 680 is necessary).

Group numbers are added sequentially from 1 (maximum 255) to indicate the transmission order.

It is necessary only when the parameter cell 680 corresponds to the output data from the SVC. 0 if the parameter cell 680 corresponds to the input to the SVC
Set to 0 (hexadecimal).

<Buffer reservation by group number 683> When FF (hexadecimal) is specified for the group number 683,
The return data area 700 for storing the output data from the SVC corresponding to the parameter cell 680 is secured, but is not transmitted to the request source process 650 of the client 101.

That is, the return data area 700 corresponding to the parameter cell 680 in which FF (hexadecimal) is designated as the group number stores not only the output data which is not transmitted but also the buffer temporarily provided by the remote process task 600. It can be used as an area (eg, buffer provision in SVC COPY for file management).

(D) In-group number 684 ...... Indicates the order in which the output data from the SVC corresponding to the parameter cell 680 of the same group number 683 is transmitted at the time of transmission to the request source process 650 of the client 101.

It is meaningful only when returning the return data area 700 (it has no meaning when returning the parameter area 690. However, the field is secured).

(E) Data 685 ........ Main body of SVC parameter.

When the data length 682 is an odd number of bytes, an undefined value of 1 byte is placed at the end of the data and is corrected to the word boundary. Only needed if the parameter cell 680 corresponds to the input data to the SVC. If the parameter cell corresponds to the output to SVC, the data field 685 does not exist.

<Divided Transmission of RPC Data> The request source process 650 on the client 101 side divides the RPC return data 670 into the remote process task 600 on the server 102 side by multiple times of data transmission (DSEND) SVC. Can be sent. The following three positions can be divided (see FIG. 33).

(A) Parameter cell 680 and cut of function code 664 (SVC number 663 in case of no function code) (b) Parameter cell 680 and cut of parameter cell 680 (c) Group number 683 in parameter cell 680 Break of data 685 3.3 Frame format of RPC return data FIG. 37 shows a frame format of RPC return data 670 sent from the remote process task 600 on the server 102 side to the request source process 650 on the client 101 side. The remote process task 600 returns the output data (processing result) of the issued SVC to the requesting process 650 as RPC return data 670.

The method of storing the SVC output data in the RPC return data 670 is designated by the RPC data 660 (see section 3.2).

The output data from the SVC corresponding to the parameter cell 680 in which the same group number 683 is described is the client 1 in one data transmission (DSEND) SVC.
01 to the request source process 650. The group number 683 indicates the transmission order. The in-group number 684 indicates the order in which the output data (processing result) from the SVC corresponding to each parameter cell 680 having the same group number 683 is arranged in the RPC return data 670.

4 Processing 4.1 Outline of Processing The remote process task 600 follows the procedure below to receive, analyze, issue SVC of the RPC data 660 from the request source process 650 on the client 101 side, and request the client 101 side. Send RPC return data 670 to process 650. The outline of the processing of the remote process task 600 will be described below with reference to FIG.

(1) Reception of RPC data from the client (step 611) RP from the request source process 650 on the client 101 side
The C data 660 is received.

(2) Set SVC number and function code (step 621) Set SVC number 711 in SDB (Super Visor Data Block) 710.

When the function code 664 exists, it is set in the function code 7712.

Parameter area 690 is set to SDB710
If you want to pass the SVC parameters to the outside of the server, calculate the start address of the parameter area 690 and
The parameter area address 713 of 710 is set.

(3) Setting SVC parameters (step 621) Parameter area 69 inside or outside SDB 710
Set the SVC parameters to 0.

(4) Issuing SVC (step 622) Issuing SVC.

(5) Return of data (step 63
1) According to the method indicated by the SVC issuing control code 662,
RPC to request source process 650 on the client 101 side
Return data 670 is returned.

In the SVC issuance control code 662, if the transmission of the parameter area 690 is instructed, the transmission of the return data area 700 is instructed. If the transmission of the return data area 700 is instructed, the data in the return data area 700 is transmitted to the client 101 side. To the requesting process 650.

(6) Task end processing (step 641,
(Step 642) When the SVC issuance control code 662 instructs to end the task, the connection is released (step 64).
1), the task is ended (step 642).

4.2 Reception of RPC Data FIG. 38 shows an outline of the data reception processing 611. The RPC data 660 is received from the request source process 650 on the client 101 side by issuing the communication control SVC (DRECV) in the "waiting mode" (step 7).
31). The received RPC data 660 is stored from the beginning of the remote process task buffer of the remote process task 600. After that, RPC data 660
It is determined whether or not the reception of is completed (step 73
2) If the communication is not completed, the SVC for communication control is again executed.
Issue (DRECV).

The conditions for judging the reception end of the RPC data 660 in step 732 are shown below.

<RPC data reception end determination condition> RP
The end of reception of the C data 660 is determined by the following conditions.

Data reception end: The data end flag (2 ⁰ ) of the parameter type 681 in the last received parameter cell 680 is 1, and the total number of bytes of received data is equal to the required number of data bytes.

Here, the required number of data bytes is RP
It is the total of the data lengths of the head portion (661 to 664) of the C data 660 and all the parameter cells 680. The number of required data bytes is calculated by the following formula.

Required number of data bytes = Start 661
~ 664 (with function code: 6 bytes, without: 5 bytes) + total data length of each parameter cell (6 bytes + length of data field 685) 4.3 Set SVC number and function code Remote process task In the area next to the RPC data 660 (received) in the buffer 720, follow the procedure below
Create SDB 710 for issuing C.

(1) SVC number 6 at the beginning of SDB 710
Set 63.

(2) When the function code 664 exists (2 ¹ = 1 of the SVC issuing control code 662), the function code is set next to the SVC number.

If the function code 664 does not exist (2 ¹ = 0 of the SVC issuance control code 662), S
There is no function code field in the DB 710.

(3) When passing SVC parameters using the parameter area 690 outside the SDB 710 (SVC
2 ⁰ = 1) of the issue control code 662 calculates the start address of the parameter area 690 and sets it in the SDB 710. (S in the remote process task buffer 720
A parameter area 690 is created in the area next to the DB 710. 39) FIG. 39 shows a configuration example of the SDB 710 in the case where the function code 664 exists and the SVC parameter is passed using the parameter area 690 outside the SDB 710 (when the communication data from the client is FIG. 36).

4.4 Setting of SVC Parameter The SVC parameter described in the RPC data 660 is set in the internal or external parameter area 690 of the SDB 710. The process of setting the parameters differs for each parameter cell depending on the parameter type 681 described in each parameter cell 680 (see Table 6).

FIG. 40 shows the structure of the parameter area when the RPC data illustrated in FIG. 36 is sent from the client.

Further, the RPC data 66 exemplified in FIG.
FIG. 41 illustrates the outline of the memory configuration of the remote process task buffer 720 after receiving 0 and ending the SDB generation process 621. 42 shows the detailed contents of the remote process task buffer 720 in that case.

[0248]

[Table 6]

<Securing Return Data Area> When the SVC output is stored in the return data area 700 (2 ² = 1 and 2 ¹ = 1 of the parameter type 681), the return data area 700 is stored in the remote process buffer 720. Secure.

When the SVC status (end state) is returned to the request source process 650 on the client 101 side (2 = ^{4 in} SVC issue control code 662), the return data area 700 in the remote process task buffer 720 is stored. Status storage area 740 in the previous area
Reserve (2 bytes).

4.5 Issuing SVC The SVC is issued. The procedure for issuing an SVC is shown below.

(1) Remote process task buffer 7
The start address of SDB710 in 20 is the segment,
Pushes onto the stack in offset order.

(2) Software interrupt is applied.

(3) Restore the stack.

(4) When the SVC status is returned to the request source process 650 of the client 101 (2 ⁴ = 1 of the SVC issuance control code 682), the status is stored in the status storage area 740 of the remote process task buffer 720. Store.

4.6 Transmission of RPC Return Data The method of returning the SVC processing result to the request source process 650 on the client 101 side is as follows.
Depending on the designation, the parameter area 690 is returned and the return data area 700 is returned (see FIG. 34).

Data transmission is performed by issuing a data transmission SVC (DSEND) provided by communication control in the "waiting mode".

(1) Returning Parameter Area After returning the status stored in the status storage area 740, the contents of the parameter area 690 are returned to the client 101. Status and parameter area 690
Are returned in a separate data transmission SVC (DSEND).

(2) Returning Return Data Area Return data 700 is returned to the request source process 650 on the client 101 side in order from the data corresponding to group number 1. The status is added before the return data 700 corresponding to the group number 1. The process is repeated until there is no remaining return data 700 to be returned to the requesting process 650.

<Example of Processing> The request source process 650 on the client 101 side shows the RPC data 6 shown in FIG.
The processing when 60 is sent is shown in FIG. In this case, return data 7 to be returned to the requesting process 650
00 is shown in Table 7.

The processing relating to the return data 700 corresponding to the group number 1 is shown below.

(A) The number of bytes of the return data 700 corresponding to the group number 1 is calculated.

Data corresponding to group number 1: 4 bytes (b) Send 4 + 2 (2 bytes is status) bytes from the transmission start position 750 to the request source process 650.

Number of bytes of remaining data = 8-4 = 4 (c) The above processing is repeated until the number of bytes of the remaining data becomes 0 for the data corresponding to the group numbers 2, 3 ...

[0265]

[Table 7]

4.7 Task Termination Processing After the RPC return data 670 is transmitted, if the task termination is designated by the SVC issuance control code 662 (2
⁵ = 0) performs task end processing 640. FIG. 44 shows an outline of the task end processing 640.

If the end of the task is not instructed, the task end processing 640 is not performed, and the process returns to the reception waiting state of the RPC data 660 (see section 4.2).

(1) Connection release SVC (DISCON)
Is issued in the "waiting mode" to release the transport connection (step 641).

(2) Task end SVC (ENDTEX) is issued to end the remote process task (step 64).
2).

4.8 Abnormal Processing The processing when an abnormality occurs in the remote process task 660 is shown.

(1) When the SVC instructed by the client 101 ends abnormally No particular processing is performed for the abnormal end. The same process as when the SVC ends normally is performed.

(2) When "Data transmission SVC (DSEND)" ends abnormally (a) When the transport connection is forcibly released The remote process task 660 is ended ("ENDT").
EX "SVC issued).

(B) When the communication buffer and the receiving buffer of the other party cannot be used The transport connection is released (issuing SVC (DISCON)) and the remote process task 660 is ended (issuing SVC (ENDTEX)).

(3) When "Data reception SVC (DRECV)" ends abnormally (a) When the transport connection is released abnormally Remote process task 660 ends (SVC (ENDTEX))
Is issued).

(B) When the received data exceeds the area for data reception: Release of the transport connection (issuance of SVC (DISCON)), termination of the remote process task 660 (SVC)
Issue (ENDTEX)).

(C) When there is no received data The transport connection is released (issuing SVC (DISCON)) and the remote process task 660 is ended (issuing SVC (ENDTEX)).

(4) "Connection release SVC (DISCO
N) ”ends abnormally (a) When the transport connection is released abnormally No special processing is performed.

(B) When the communication buffer and the receiving buffer of the other party cannot be used: The transport connection is forcibly released (SVC
(DISCON) is issued in "waitless mode").

5. Execution control of remote process task A plurality of remote process tasks 600 are activated in response to requests from a plurality of clients 101. further,
It is necessary to process those requests at the same time. Therefore, in order to perform multitasking for switching those remote process tasks 600 at high speed, the following memory management system is adopted.

The core block method is used as the memory management method. Therefore, tasks of the same type all operate in the same core block. Then, when switching tasks of the same type that operate in the same core block, a task of saving the task of the core block to a fixed disk and a task of loading a new task to the memory are performed. Therefore, when a plurality of tasks of the same type are activated, fast task switching of those tasks cannot be expected.

Therefore, as shown in FIG. 45, for example, by providing 15 physical address spaces 811 allocated to the logical address space 801 in which the remote process task 600 operates, and switching the physical address spaces 811, a maximum of 15 physical address spaces 811 can be created. Enable fast switching of remote process tasks. Also, when 15 or more remote process tasks 600 are started, the task save area of the fixed disk device (HD) 126
Rolls out and rolls in the remote process task 600.

Reference numeral 800 in the figure denotes a central processing unit (CP
U) 121 logical address space. 810 is a physical address space of the main memory (MM) 122.

[0283]

As described above, according to the present invention,
It is possible to improve the speed of reading and writing files without reducing the efficiency of use of the communication line.

[Brief description of drawings]

FIG. 1 is a system configuration diagram of a document editing system of the present embodiment.

FIG. 2 is a system configuration diagram of a client and a server.

FIG. 3 is an explanatory diagram showing a file system system according to the present embodiment.

FIG. 4 is an explanatory diagram of a file structure according to the present embodiment.

FIG. 5 is a structural diagram of a node block according to the present embodiment.

FIG. 6 is a structural diagram of a directory block according to the present embodiment.

FIG. 7 is an explanatory diagram showing an outline of a remote mount according to the present embodiment.

FIG. 8 is a structural diagram of a mount table according to the present embodiment.

FIG. 9 is a schematic flowchart of remote mount processing in file management according to the present embodiment.

FIG. 10 is a schematic flowchart of remote unmount processing in file management according to the present embodiment.

FIG. 11 is a schematic flowchart of file access processing in file management according to the present embodiment.

FIG. 12 is a schematic flowchart of remote file access determination processing by path name in file management according to the present embodiment.

FIG. 13 is a schematic flowchart of remote file access determination processing by file number in file management of the present embodiment.

FIG. 14 is a schematic flowchart of remote file access processing in the document creation system of this embodiment.

FIG. 15 is an explanatory diagram showing an outline of buffer management in the document creating system according to the present embodiment.

FIG. 16 is an explanatory diagram showing an outline of processing for securing a communication parameter area in the document creating system of the present embodiment.

FIG. 17 is a configuration diagram of a current directory area according to the present embodiment.

FIG. 18 is a configuration diagram of a file access control block according to the present embodiment.

FIG. 19 is an explanatory diagram showing an outline of open file management according to the present embodiment.

FIG. 20 is a schematic flowchart of a local file open process in file management of this embodiment.

FIG. 21 is a schematic flowchart of remote file open processing in file management of this embodiment.

FIG. 22 is a schematic flowchart of a local file close process in file management of this embodiment.

FIG. 23 is a schematic flowchart of remote file close processing in file management of this embodiment.

FIG. 24 is an explanatory diagram showing a data flow when a remote file is accessed in the file management of this embodiment.

FIG. 25 is a configuration diagram of a search file area according to the present embodiment.

FIG. 26 is a schematic flowchart of processing of a server manager task in the present embodiment.

FIG. 27 is an explanatory diagram showing an outline of communication processing in the present embodiment.

FIG. 28 is an explanatory diagram showing a relationship between a server manager task and peripheral processes according to the present embodiment.

FIG. 29 is a schematic flowchart of initialization processing in the server manager task of the present embodiment.

FIG. 30 is a schematic flowchart of establishment of a transport connection and activation processing of a remote process task in the server manager according to the present embodiment.

FIG. 31 is a schematic flowchart of processing of a remote process task in the present embodiment.

FIG. 32 is an explanatory diagram showing an outline of a communication sequence in the present embodiment.

FIG. 33 is an explanatory diagram showing an RPC data format in this embodiment.

FIG. 34 is an explanatory diagram showing a form of data return according to the present embodiment.

FIG. 35 is an explanatory diagram showing a method of configuring an SDB in this embodiment.

FIG. 36 is an explanatory diagram showing an example of communication data according to the present embodiment.

FIG. 37 is an explanatory diagram showing an example of grouping of return data according to the present embodiment.

FIG. 38 is a schematic flowchart of a data reception process in the remote process task of the present embodiment.

FIG. 39 is an explanatory diagram showing a configuration example of the SDB in the remote process task of the present embodiment.

FIG. 40 is an explanatory diagram showing a configuration example of a parameter area in the remote process task of the present embodiment.

FIG. 41 is an explanatory diagram showing an outline of a memory configuration example of a remote process task buffer in the remote process task of the present embodiment.

FIG. 42 is an explanatory diagram showing an example of a memory configuration of a remote process task buffer in the remote process task of the present embodiment.

FIG. 43 is an explanatory diagram showing an example of RPC return data transmission in the remote process task of the present embodiment.

FIG. 44 is a schematic flowchart of task end processing in the remote process task of this embodiment.

FIG. 45 is an explanatory diagram showing a relationship between a logical memory space and a physical memory space in the remote process task of this embodiment.

[Explanation of symbols]

101 ... Client, 102 ... Server, 103 ... LA
N, 111, 121 ... Central processing unit (CPU), 1
12, 122 ... Main memory (MM), 113, 123 ... Keyboard (KB), 114, 124 ... Video memory (V
RAM), 115, 125 ... Display display device (C
RT, 116, 126 ... Fixed disk device (HD
D) 117, 127 ... Communication control unit (CDR
V), 118, 128 ... Bus, 201 ... Root directory, 202 ... Drive directory, 203 ... Directory, 204 ... File, 211 ... Node block,
212 ... Directory block, 213 ... Data block, 250 ... Mount table, 330 ... Buffer management area, 340 ... Disk buffer, 350 ... Current directory management area, 360 ... File access control block (FCB), 370 ... Open file management area, 440 ... Search file area, 660 ... RP
C data, 670 ... RPC return data, 690 ... Parameter area, 710 ... SDB, 720 ... Remote process task buffer.

─────────────────────────────────────────────────── ─── Continuation of the front page (51) Int.Cl. ⁵ Identification number Office reference number FI Technical indication location H04L 12/40 29/08 8220-5K H04L 13/00 307 A (72) Inventor Takao Iwatani Yokohama-shi 292 Yoshida-cho, Totsuka-ku, Hitachi, Ltd. Microelectronics Device Development Laboratory (72) Inventor Sadaji Kuwahara 292, Yoshida-cho, Totsuka-ku, Yokohama City Hitachi, Ltd. Microelectronics Device Development Laboratory

Claims (6)

[Claims] 1. An information processing system comprising a plurality of information processing devices, a database system for supplying data to the plurality of information processing devices, and a communication network connecting the plurality of information processing devices and the database system to each other. In, when a file on the database system is opened from an information processing device, a logical communication line is opened between the information processing device and the database system, and operations such as reading and writing of the file are performed by the communication described above. An information processing system characterized by disconnecting a logical communication line established when a file is opened when the file is closed. 2. The information processing system according to claim 1, wherein in processes other than file opening, closing, reading, and writing, logical communication is performed between the information processing device and the database system at the start of a series of data communication. An information processing system which opens a line and disconnects the communication line when a series of data communication ends. 3. An information processing system comprising a plurality of information processing devices, a database system which supplies data to the plurality of information processing devices, and a communication network which connects the plurality of information processing devices and the database system to each other. In the database system, means for allocating a physical address space to a logical address space is provided. In the database system, a logical address space in which a task operates is determined in advance, and a request is made from the information processing device. An information processing system comprising: providing a plurality of physical address spaces to be allocated to a logical address space in which a plurality of tasks to perform processing, and switching the tasks by switching the physical address space to be allocated to the logical address spaces. 4. The information processing system according to claim 2, wherein the database system is provided with a fixed disk device, and in the database system, the number of tasks that perform the processing requested by the information processing device is determined by the logic in which the tasks operate. An information processing system, characterized in that when the number of physical address spaces allocated to an address space is larger than the number of physical address spaces, the task is rolled out and rolled into the fixed disk device. 5. An information processing system comprising a plurality of information processing apparatuses, a database system for supplying data to the plurality of information processing apparatuses, and a communication network connecting the plurality of information processing apparatuses and the database system to each other. In the above information processing system, when the information processing means writes in a file on the database, the data instructing the writing and the data to be written in the file are separately transmitted to the database system. 6. An information processing system comprising a plurality of information processing devices, a database system for supplying data to the plurality of information processing devices, and a communication network connecting the plurality of information processing devices and the database system to each other. In the above information, when the above-mentioned information processing measures read from the file on the database, the end state of the read processing in the database system and the data read from the file are separately received from the database system. Processing system.