KR100258067B1 - An implementation method of administration commands to establish execution environment in host dbms simulator - Google Patents

Abstract

PURPOSE: A method for embodying an operation control instruction in order to set up a performance environment in a host DBMS(Database Management System) system is provided to increase a reliability of a simulation by testing an exchange application software on a host system directly through a simulator. CONSTITUTION: When an operation control instruction is a hdb_connect, an HDS(Host DBMS Simulator) server decides whether the HDS server executes the hdb_connect or not(S9-2). When the hdb_connect is a non-executed instruction, the HDS server loads a PLD(Processor Load Data)(S9-3). At this time, the hdb_connect is for registering the PLD at the HDS server. The HDS server controls that a user uses the PLD by forming a link between the loaded PLD and the user(S9-4). Meanwhile, when the operation control instruction is an hdb_disconnect(S9-5), the HDS server discriminates whether the PLD is used or not by searching an existing PLD table. At this time, the hdb_disconnect is for stopping a usage of the PLD. If the PLD is used, the HDS server unloads the PLD(S9-6), and removes the link(S9-7). And, when the operation control instruction is an hdb_joint(S9-8), the HDS server checks a usage of an existing PLD(S9-9), and controls that all users use the PLD by connecting a link to the PLD to be in use(S9-10). At this time, the hdb_joint is for allowing a sharing of the PLD. When the operation control instruction is an hdb_disjoint(S9-11), the HDS server releases the sharing of the PLD(S9-12).

Description

How to Implement Operation Control Commands to Set Execution Environment in Host DMS System

The present invention relates to a method for implementing operational control commands for setting an execution environment in a host DBMS system. In particular, a user who uses the host system may change a switch application written in CHILL / C in his host system, similar to that of an exchange. A method of implementing operational control commands for setting up an execution environment in a host DBMS system for identifying the configuration of the operational control commands for setting up an operational control environment of a host DBMS tester and helping to test the test environment. will be.

In general, an exchange program is designed to allow a user to create an application program using his or her host system, and then load the executable file into the exchange. However, the exchange has the limitation that it cannot test various things about the developed application. The system developed to solve this problem is a host DBMS tester (HDS, Host DBMS Simulator).

In 1989, Korea Electronics and Telecommunications Research Institute (ETRI) developed the first host DBMS. The name is called host DBMS. It was in library format. In order to use this, when compiling an application program, the existing host DBMS is linked to create a single executable file and executed. However, these unified executables can test their function at any given time, but they cannot be tested because they have the limitation of not being able to execute multiple executables at the same time.

An object of the present invention is to set up an operation control environment of a host DBMS tester, which enables a user using a host system to test an exchange application written in CHILL / C in his host system under a test environment similar to that of the exchange. The present invention provides a method of implementing the operation control command for setting the execution environment in the host DBMS system to reveal the configuration of the operation control command and its implementation plan.

The means for achieving the object of the present invention is that if the operating command is registered as a command (hdb_connect) for registering and using its own processor load data (HDD) server to the HDS server, whether the server is executable on the server After checking, if it turns out to be a new request that is not already running, it loads the PLD, forms a link between the loaded PLD and the requesting user so that the requesting user can use the loaded database, the PLD, and then processes it. If the first step of terminating the process and the operation command are connected to the PLD being used and the command (hdb_disconnect) for discontinuing the permission are found, the PLD is checked by checking the existing PLD table. After changing the data structure, such as unloading the file, deleting the link between the user and the PLD, the second step of terminating the execution and the operation command If it turns out to be a command (hdb_joint) to allow access to users who will share their own PLDs, the PLD is checked by the use of existing PLDs, and all users who are linking to one PLD by linking to an existing PLD. After making it available, if it turns out to be the third process to terminate the use and the command (hdb_disjoint) to release the user shared by the operation command from its PLD, the sharing is terminated and the data structure in use. The fourth step of terminating and then ending the sharing by changing.

1 is an overall configuration diagram of a host DBMS tester (HDS).

2 is a flowchart illustrating a process for generating a library.

3 is a flowchart illustrating a process for generating an operation control command.

4 is a flowchart illustrating a process for creating an HDS server.

5 is a view showing the basic form that the library, the operation control command, and the server to communicate generated through FIGS. 2, 3 and 4;

FIG. 6 is a diagram illustrating a process of processing required requests when a library and an operation control command arrive at the HDS server.

7 is a diagram describing operational control commands.

8 is a detailed processing flowchart of the HDS server.

9 is a processing flowchart when the HDS server accepts an operation control command.

(Explanation of symbols for the main parts of the drawing)

1. Application CHILL / C program 2. Shared memory and message queue

3. HDBMS Server and DBMS Kernel 11. Compiler and EDMLP

21. Application Executables and Host Libraries

41. Operation control command 100. User part

200.IPC part 300.HDS server part

The present invention proposes a configuration of a tester that can execute multiple switch execution files including DBMS query processing words in a host system, and is configured with multiple clients and multiple servers to realize this. The client, as a user, accesses the server using Embedded Data Manipulation Languages (EDML) and Administration Commands inside the executable.

The server is a DBMS, which processes the request from the operator. In other words, the client side has two types and works with the server.

The first client is a compiled executable that is your application. It is an executable file created by linking a given host library to its own application. It is an executable block containing the embedded query processing language (EDML). The execution block contains several kinds of built-in queries, which are linked to the server dynamically through the library when a single execution block is executed.

The second client is the operational control commands provided on the UNIX shell to configure the server's environment. That is, the user can dynamically load the PLD using this control command, and then execute the executable file described as the first client to check the query processing result.

This technique deals with the construction and implementation of the second operation control command. In order to explain the present invention, first, the structure of the HDS tester will be described, the communication method of the client server based on this will be introduced, and the structure and the implementation technology will be described with a focus on the operational control commands introduced as the second client of the client server communication. will be.

The operation control command is an off-line command for setting the execution environment of the HOST DBMS tester as required by the user, and runs on a UNIX shell. Currently, four operation control commands are implemented, and the PLD to be operated by the user is registered and deleted on the HDS server, and the PLD sharing command for sharing the corresponding PLD is provided. Later, as the use of tester such as HDS server information output progressed, it was implemented to expand various functions as needed.

The extension method can send the request of each user to the HDS server by adjusting the IPC system with the HDS server as the configuration of the operation control command. The HDS server inserts a routine to handle this whenever the user's requirements increase.

Operational control commands can be placed in any shared directory in the system and used by all users.

These operational control commands are as follows.

% hdb_connect: Command to register and use own PLD with HDS server

% hdb_disconnect: Command to stop connected PLD and its permission

% hdb_joint: Command to allow access to users who will share their PLD

% hdb_disjoint: Command to release shared user from own PLD

A user using a PLD loaded on the HOST DBMS can only be registered as one of the owners or users of the PLD on the server.

PLD Owner: The user who first registered the PLD on the server. An owner has only one PLD in the target server and has the authority to register and delete shared users.

PLD user: A user who wants to share a PLD registered as an owner by another user. One user also has a PLD in the target server.

-OMP, CCCP00, CCCP01: HDS server can be created in various ways under the name of OMP, CCCP00, CCCP01, etc., which is assumed to each subsystem according to user's request. This English name is a unique name that symbolizes each HDS server. Each of these substantially represents a subsystem of an ATM switch.

The following is an example of how to use the Administration Command and how to use it.

% hdb_connect [target_name] [pld_name]

Ex) hdb_connect OMP P_O_pyh

Load P_O_pyh, which is the PLD to use on the HDS OMP server, in system memory, register the user who uses this command as the owner of the requested PLD, and receive permission to use it. hdb_connect basically registers the account of the user who executed the command on the server, and after registration, the user can use the PLD loaded with his executable file. One user can register only one PLD per target processor.

% hdb_disconnect [target_name] [pld_name]

Ex) hdb_disconnect OMP P_O_pyh

Download P_O_pyh, a PLD that has been registered and used in the HDS OMP server, from the system memory and initialize all information about the PLD registered as the owner. Note that all users who have shared the PLD using the hdb_joint command must disconnect before executing this command.

% hdb_joint [target_name] [pld_name] [sharing_user_account]

Ex) hdb_joint OMP P_O_pyh yiyoon

P_O_pyh, a PLD registered and used by the owner of the HDS OMP server, is used to share a PLD with a user with an yiyoon account. The principal granting permissions to user yiyoon becomes the owner of P_O_pyh. At this time, yiyoon is registered as a user and can use P_O_pyh as the owner. After yiyoon has finished using it, the owner of P_O_pyh should be notified of the completion of use and the permission should be removed. A user who has been granted as a joint user by the owner only needs to execute his execution block.

% hdb_disjoint [target_name] [pld_name] [sharing_user_account]

Ex) hdb_disjoint OMP P_O_pyh yiyoon

This command removes the authority to yiyoon's PLD P_O_pyh, which was registered as a user on the HDS OMP server. Once used, yiyoon should notify the PLD owner to inform them of this command.

Hereinafter, the present invention will be described in detail with reference to the accompanying drawings.

Figure 1 shows the overall configuration of a host DBMS tester (HDS) according to an embodiment of the present invention.

As illustrated in FIG. 1, the host DBMS tester for explaining an embodiment of the present invention includes a query word in the form of embedded data manipulation language (EDML) embedded in a plurality of application CHILL / C programs 1, and the CHILL / C compiler. After expanded to code that can be recognized by the EDMLP (Embedded Manipulation Language Processor) and the compiler (11) for compiling the extended code, and the executable executable file generated by the compiler 11 and the host The library 21, the processor load data (PLD) 31, which is a database, and the PLD 31 are loaded on a server, the user is given permission to use the loaded PLD 31, sharing is allowed, and the like. Address RANGE A-User Part (100), which is an executable A address space with operational control instructions (41) for executing a series of server execution configuration tasks, and a plurality of Host DBMS Simulator (HDS) servers. And Data Management System (DBMS) Kernel (3) An HDS server part 300, which is an executable C address space, and a shared memory and a message queue 2 are provided to control communication between the user part and the HDS server part. It consists of an Inter Process Communication (IPC) part (Address C) 200 which is a B address space.

The operation of the host DBMS tester configured as described above is as follows.

IPC is used to represent the form of communication between processes operating in different addressing spaces.

The client is first, the application executable, and secondly, operational control commands for dynamically loading the database into the server and sharing the loaded database. After loading the database on the server side using the operation control command, execute the compiled application executable files by linking the library.

At this time, the executable file has a structure that can interoperate by sending an embedded query request word (EDML) to the server side by using the provided communication environment, and receives the result. The host DBMS tester shown in FIG. 1 establishes a multi-client multi-server environment to support multiple executions of execution blocks of multiple users, and provides a transmission / reception function for a large amount of data using a shared memory.

2 illustrates a process for generating a library.

Step S2-1 is software for driving the exchange with the exchange software. The software can use query processing words to use the database. They are treated for EDML in step S2-2. This process extends the query EDML inherent in the CHILL / C program to the CHILL / C program. This extended CHILL / C program is compiled by the CHILL / C compiler in step S2-3.

At this time, by linking the library for the host DBMS generated through the step S2-7 to step S2-7 to create a single executable file in step S2-4. This figure shows the steps of linking library routines to an application to create an executable file.

3 is a diagram illustrating a generation process of an operation control command.

The operation control instruction program generated in step S3-1 is compiled while going through the C compiler in step S3-2, and then generates operation control instruction code.

4 shows a process for creating an HDS server.

The host DBMS tester server is written in C language in step S4-1, which is compiled by the C compiler in step S4-2. At this time, in step S4-4, the kernel program used in the distributed real-time database management system scalable (DREAM-S), which is a real-time DBMS, is compiled by the C compiler in step S4-5, and then the target host is performed in step S4-6. DBMS kernel executable file.

This kernel is linked to the HDS server program in step S3-2, compiled, and then generates one server executable in step S4-3.

FIG. 5 is a diagram illustrating a basic form in which a library, an operation control command, and an HDS server, generated through FIGS. 2 to 4, communicate.

5-1 is an executable file of a user program generated through the contents described with reference to FIG. 2, and 5-4 are executable files of operation control instructions described with reference to FIG. 3. 5-3 is an executable file of the host DBMS server generated through the contents described with reference to FIG. 4.

In 5-1, user program and host DBMS library are combined. In 5-4, it can communicate with HDS server. 5-3 consists of the HDS server, kernel, and databases to be loaded during production. They communicate with each other by 5-2 UNIX IPC. The UNIX IPC techniques used are message queues, shared memory, and semaphores. In addition, signals were used to deal with possible disturbances between them.

6 is a diagram illustrating a process of processing a service requested to an HDS server through a library.

In step S6-1, the HDS server operator starts the HDS tester. The exchange consists of several subsystems. For example, ETRI's Hanbit / ACE ATM exchange consists of subsystems with different uses, such as OMP, CCCP00, and CCCP01. One HDS server represents one exchange subsystem. Therefore, more than one server cannot run on the same server. However, the HDS server, which represents another subsystem, can be run.

As a result, several HDS servers can be executed, but one for each subsystem. After the HDS server starts running, in step S6-2, initialization for running the HDS server starts. Initialization is performed by setting up a system data structure, initializing IPC, setting various variables, and when all settings are completed, finally, an HDS server daemon is executed to prepare for accommodating a service received from a user.

In step S6-3, a user request for processing is received from the HDS server. Their request is analyzed in step S6-4, and if it is Administration Commands for setting up the operation environment, perform the operation command processing routine of 6-5, and configure the server environment in step S6-6. After that, perform step S6-3 again.

If the analysis result of step S6-4 is a user query processing request, query processing is performed in step S6-7, the host DBMS is called in step S6-8, and the process returns to step S6-3. If an error is identified in communication or processing as a result of the analysis in step S6-4, the error is processed in step S6-9 and step S6-3 is performed. In this way, the server performs continuous execution. If you want to stop them, press Cntl-C to terminate normally.

Fig. 7 is a diagram related to an operation control command processing request. This figure is associated with FIG. 8.

This figure is characterized in that there is no modification of data since there is no data for query processing or the like, and therefore, no shared memory is used. Operational control commands work in the UNIX Shell like regular commands. Briefly, their functions are dynamically loaded on the HDS server, the user who has loaded the database is given permission to use the database, and the database is loaded at the user's request. Process of setting HDS server operating environment such as allowing sharing with multiple users for database.

The following is a detailed description of FIG.

Step S7-1 represents the start of the operational control request. In step S7-2, a communication environment for communicating with the HDS server is set. In operation S7-3, the operation control command is transmitted to the HDS server using the message queue. In step S7-4, if it is determined that the transmitted information is normal and if it is determined that the communication is abnormal, the communication error recovery process of step S7-5 is performed, and the result is notified to the user in step S7-7, and S7-8. Complete the steps. If the determination of step S7-4 determines that the execution is normal, the execution continues.

The response to the processing result is received in step S7-6, and the user side informs the result of the execution of the HDS server for the operation control command in step S7-7, and then ends in step S7-8.

8 is a flowchart illustrating an HDS server interworking with a library on the client side and an operation control command.

All processes described in this figure are guaranteed to be performed independently in the server using semaphores for each client request. Steps S8-1 and S8-2 receive the request from the client in step S8-3 after the server starts. In step S8-4, it is determined whether or not the received request is normal, and if it is found to be abnormal, in step S8-5, it is sent to the client who requested the reason for the communication status or the inability to process data. Then, perform step S8-3 again.

If the execution result of step S8-4 is found to be normal, in step S8-6, if the request is an operation control command or a query processing request command, the operation control command is classified. If the result is found to be normal in the step S8-8, the execution of the HDS server side is notified to the client through the step S8-9, and the step S8-3 is performed. If it is found abnormal, the step S8-10 After recovering from the error, perform steps S8-3.

If the determination result of step S8-6 is a query processing instruction, it is necessary to change the information of the received shared memory. Therefore, in step S8-11, the shared memory format is changed to a format that can be processed by the HDS kernel, and in step S8-13, the HDS kernel Will be performed. After completing the execution of the kernel, the execution result is changed to the shared memory transmission format for transmission back to the client in step S8-12, and the query processing result is sent to the library client in step S8-14.

Receiving this, the library client sends an acknowledgment of the received result, which is received in step S8-15. If the result is found to be normal in the step S8-16, the execution of the HDS server side is notified to the client through the step S8-17, and the step S8-3 is performed again. After recovering, perform step S8-3 again.

9 is a diagram illustrating a process of an operation control command processed on an HDS server. Step S8-7 of FIG. 8 will be described in detail.

If the process started in step S9-1 is found to be hdb_connect in step S9-2, the server checks the suitability of the server for execution, and if it is determined that it is a new request that is not already running, the PLD is removed in step S9-3. After loading, a link is formed between the PLD loaded in step S9-4 and the requesting user so that the requesting user can use the PLD, which is the loaded database, and the process ends in step S9-14.

If it turns out to be hdb_disconnect in step S9-5, if the existing PLD table is checked in step S9-6 and it is determined that the PLD has already been used, the PLD is unloaded. After changing the data structure such as deleting a link, the execution ends. If in step S9-8 it is determined to be hdb_joint, in step S9-9 it checks the use of the existing PLD, and in step S9-10, all users connecting the link to one PLD are connected to the PLD in use. After making it available, stop using it in step S9-14.

If the command requested in step S9-11 is found to be hdb_disjoint, the sharing is terminated in step S9-12, the sharing is terminated by changing the data structure being used in step S9-13, and then ends in step S9-14.

The present invention firstly provides a tester that can test the switch application software directly on the host system rather than the switch body.

Second, the exchange solved the same problem on the host by limiting the use of resources in which execution blocks of loaded application software cannot be simultaneously tested by multiple users.

Third, in the exchange, even if one user tests, the package forms a single integrated execution environment, so it is difficult to test when adding or changing new functions or if they are related to existing functions. This problem is solved by providing the operation control command provided by.

Fourth, as a function of operation control command, it provides a function to dynamically load a database PLD into the HDS server.

Fifth, it provides the ability to share this. Through this function, multiple users can execute application programs in one system at the same time.

Claims (1)

If the operation command turns out to be a command (hdb_connect) for registering and using its own PLD on the HDS server, the server checks the suitability of the server for execution, and if it is found to be a new request that is not already executed, A first step of loading, forming a link between the loaded PLD and the requesting user so that the requesting user can use the loaded PLD, and then terminating the processing; If the operation command is connected and found to be in use (hdb_disconnect) to stop the use of the PLD and the authority to use it, the existing PLD table is checked to confirm that the PLD is already in use, and the PLD is unloaded. A second step of changing the data structure such as deleting a link and ending the execution of the link; If the operation command turns out to be a command (hdb_joint) that allows access to the users who will share their PLDs, then all of the links that link to one PLD are examined by checking the use of the existing PLD and linking it to an existing PLD. Making a PLD available to a user and terminating the use of the PLD; When the operation command is found to be a command (hdb_disjoint) for releasing a user who has been shared from his / her PLD, the fourth step of terminating the sharing and terminating the sharing by changing the data structure in use is completed. Implementation control command implementation method for setting execution environment in host DBMS system.

Images