JPH08115219A - Virsion management system and network system - Google Patents

Abstract

PURPOSE: To provide a technique for easily distributing files to network- connected devices. CONSTITUTION: Management information for file distribution to distribution destination devices 30 is turned to a data base and managed. At the time of the file distribution, under-operation program information of the distribution destination devices and resource information are obtained and the file distribution to the file distribution destination devices is controlled based on them and the management information. Thus, the timing of the file distribution is not limited only to the power supply time of the distribution destination devices 30. The file distribution to the respective distribution destination devices 30 is also safely performed.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a version management system for managing versions of application programs and libraries handled in network-coupled devices, for example, a plurality of TCP / IP-coupled networks. The technology is effective when applied to version control on workstations.

[0002]

2. Description of the Related Art A workstation used for LSI design is composed of a high-performance microprocessor, a large-capacity magnetic disk, a high-resolution display, and an input device including a mouse in terms of hardware, and functionally inputs a circuit diagram. And layout processing. The former circuit diagram input process includes the process from the circuit diagram input to the generation of the verified circuit diagram and connection information file, and the latter layout process, the generated circuit diagram to LSI. Layout and wiring, and work to create a verified mask pattern.

With the high performance and low cost of workstations, the distributed design of workstations is becoming the mainstream of LSI design from the conventional mainframe center type. In order to perform distributed processing using a large number of devices in the network, it is necessary to distribute development tools, libraries, etc. to the large number of devices and perform version management. As a conventional method of such distribution / management, FT
P (File Transfer Protocol) method, N
An ETM / DM system can be mentioned.

The FTP method uses the FTP protocol to manually distribute files such as development tools and libraries.
This is a management method, and it is not practical because the number of distribution steps and the frequency of distribution errors are large. In contrast, NETM /
In the DM method, distribution and version management are automated. However, in the distribution method, the distribution timing is limited when the power of the device is turned on. This is because, as shown in FIG. 6, when the device is a UNIX workstation, the operating program cannot be overwritten due to the restrictions of the OS (operating system).

An example of a document describing a workstation for designers is "LSI Handbook (starting from page 186)" issued by Ohmsha Co., Ltd. on November 30, 1984.

[0006]

In the distribution automation system described above, as shown in FIG. 6, since a program in operation cannot be overwritten due to the OS,
The distribution timing is limited when the power of the device is turned on. In addition, as shown by programs A and B in FIG. 7, when an application is composed of a plurality of programs, if all the program files constituting the application are not distributed at the same time, a malfunction of the application may occur due to version mismatch. There is a risk of causing it. Therefore, in the related art, it was not possible to forcibly perform file distribution at any time.

As described above, in the prior art, since the file distribution cannot be forcibly performed at any time, it is not possible to easily cope with an urgent version upgrade such as a program bug countermeasure. It has been found by the inventor of the present invention that a device that operates overnight requires a large amount of manpower to distribute files to such a device, because the distribution timing cannot be set when the device is turned on. It was

An object of the present invention is to provide a technique for facilitating file distribution to a network-connected device.

The above and other objects and novel features of the present invention will be apparent from the description of this specification and the accompanying drawings.

[0010]

The outline of the representative one of the inventions disclosed in the present application will be briefly described as follows.

That is, storage means for storing management information about file distribution to the file distribution destination device, monitor means for obtaining operating program information of the file distribution destination device, and resource information, and this monitor. Comparing means for comparing the information acquired by the means with the management information in the storage means, and transfer control for transferring a predetermined file to the file distribution destination apparatus based on the comparison result of the comparing means. And means to form a version control system.

Further, in the network system, a monitor means for monitoring the currently operating program and resource information, a comparison means for comparing the management information about the file distribution, and the monitor information by the monitor means. Management information that constitutes a first data processing device including a transfer control means for controlling file fetching based on the comparison result of the comparison means, and is compared with the monitor information by the first data processing device. The second data processing device includes a storage unit for storing the storage unit and a management unit for managing the storage unit.

Further, in the network system,
Storage means for configuring the first data processing device including a currently operating program and monitoring means for monitoring resource information, and storing management information for file distribution to the first data processing device A transfer control means for transferring a file to be distributed to the first data processing device to the first data processing device based on the storage information of the storage device and the monitor information of the monitor device. It constitutes a second data processing device.

[0014]

According to the above-mentioned means, when the file is distributed, the operating program information and the resource information of the file distribution destination device are acquired, the acquired information is compared with the management information in the storage means, and Based on this, the file is transferred to the file distribution destination device. This facilitates file distribution to multiple networked devices.

[0015]

FIG. 1 shows a network system according to an embodiment of the present invention.

The network system is not particularly limited, but each is an example of a data processing device. A plurality of workstations 10, 20, 30 are connected by TCP /
It is configured to be able to transfer data mutually by being connected to the Ethernet 40 by IP.

Although not particularly limited, the workstation 10 is a distribution management device having a management function related to distribution of various program files and data files. The distribution management device 10 is not particularly limited, but includes a master library 11 in which master program files and data files are formed into a library, a file transfer protocol controller (ftp) 12 for protocol control related to file transfer, and a plurality of distributions. It includes a management database (management DB) 13 and a management server 14 for collectively managing the version data of the destination device.

The workstation 20 is a device for registering various program files and data files, although not particularly limited thereto. Therefore, this workstation 20 is called a registration device. This registration device 20
Although not particularly limited, an original library 21 in which an original program is made into a library, a file transfer protocol controller (ftp) 22 for protocol control related to file transfer, and registration for controlling file registration in the distribution management device 10. It includes a client 23. With this registration client 23,
Program files and data files can be registered.

Although the workstation 30 is not particularly limited, it is designed for LSI design, and the Ethernet 40 is used.
Various program files and data files can be distributed via. For this reason,
This workstation 30 is called a distribution destination device. L
In order to enable distributed design of SI, the distribution destination device 30
Are connected to the Ethernet 40. As representatively shown in FIG. 1, one distribution destination device 30 includes a distribution library 31 in which distributed program files and data files are formed into a library, a file transfer protocol for protocol control related to file transfer. It includes a controller (ftp) 22, a download client 33 for collecting and upgrading programs, and a monitor server 34 for collecting information on programs currently operating on its own and resource information.

FIG. 2 shows the physical structure of the management database 13.

As shown in FIG. 2, the management database 13 is not particularly limited, but the system management database 200, the file management database 201, the version management database 202, the process check target file management database 203, the distribution destination management database 204, Distribution directory management data database 2
05, distribution status management database 206, and other various databases for detailed file distribution management.

The system management database 200 includes a system name and a version of the system.
The file management database 201 includes a plurality of (n) files corresponding to one system in the system management database.
Files) exist. Each file includes items such as registration number (No.), file name, model, OS, registrant, and registration date. The version management database 202 has a plurality of (n) versions corresponding to one file managed by the file management database 201. The management number (N
o. ), File size, access right, comment, updater, update date, distribution result, file version, and validity. The process check target file management database 203 has a plurality of process target check file names corresponding to one version managed by the version management database 202. The distribution destination management data database 204 includes a distribution destination machine (distribution workstation) name, model, and OS. The distribution destination directory management database 205 includes the directory name of the storage device in the distribution workstation. This distribution destination directory database 205
There are a plurality (n) of directories managed by the distribution destination management database 204 for one distribution workstation. The distribution status management database 206 is a database for managing the status of file distribution for multiple (n) distribution destination directories and multiple (m) versions, and includes distribution permission, distribution status, and distribution date and time.

FIG. 3 shows a basic processing flow for file distribution.

When the distribution management process is started (step 301), a file to be distributed to the distribution destination device 30 is acquired (step 302), and the distribution destination device 30 is currently inquired about the distribution destination device information. The running program information and the resource information of the distribution destination device 30 are acquired (step 303). Based on this information, it is determined whether the file can be distributed to the distribution destination device 30 (step 304). In this determination, if it is determined that the distribution is possible, the file is distributed to the distribution destination device 30. But,
If it is determined in step 304 that the file cannot be distributed, distribution of the file to the distribution destination device 30 is avoided. By executing the distribution in step 306 or avoiding the distribution in step 305, one processing related to the file distribution is completed (step 3).
07). Such processing can be repeatedly executed until the predetermined file distribution to all distribution destination devices 30 coupled to the Ethernet 40 is completed.

Next, the detailed flow of the file distribution process will be described with reference to FIG. In FIG. 4, for convenience, the flow of the file distribution process to one distribution destination device 30 is shown.

The activation of the process for distribution management may be instructed by the registration device 20 or may be activated by turning on the power of the distribution destination device 30. In the former case, the registration device 20 starts the process when the distribution management device 10 is instructed to start the process. In the latter case, after the distribution destination device 30 is powered on and the OS of the device is activated, the download client function of the device is automatically activated and a request to start processing for file distribution is issued by the distribution management device. It begins with what is done to 10.

When the processing for distribution management is started (step 501), the distribution management apparatus 10 transfers the distribution destination apparatus 30.
The down client 33 is requested to start the program (step 502). When the activation request is accepted by the distribution destination device 30, the distribution management device 1
0 is requested to acquire the distribution file specifications and the distribution program information about itself (step 50).
4). Since the management database 13 and the management server 14 are provided in the distribution management device 10, the distribution management device 10 acquires distribution file specifications and distribution program information in response to a request from the distribution destination device 30. Then, it is transmitted to the distribution destination device 30 (step 514). In this way, when the distribution file specifications and the distribution program information are acquired, distribution destination device information is requested (step 505), and in response thereto, the monitor server 34 is currently operating in its own device. The program information and the resource information are acquired (steps 506 and 507).
Then, when the operation program information and the resource information are transmitted to the down client 33 (steps 508 and 509), it is determined in the down client 33 whether or not file distribution to the own device is currently possible. Is performed (step 510). In this decision,
When it is determined that the file can be distributed, the distribution destination device 30 is controlled via the Ethernet 40 under the control of the file transfer protocol controller 12.
The file is transferred to (step 511). Further, in the case where the file to be transferred from the distribution management device 10 to the distribution destination device 30 overwrites the program file currently being executed in the distribution destination device 30, or the version inconsistency among a plurality of files may occur. If there is a possibility of occurrence, the download client 3
In step 3, it is determined that the file cannot be distributed, and the file distribution is avoided (step 512). As such, when the file distribution is executed, or when the file distribution is avoided due to circumstances, the processing regarding the file distribution is ended. The distribution status and the like is stored in the management database 13, and the file distribution is performed to the distribution destination device from which the distribution of the file was avoided the previous time by starting the distribution process from the next time onward. This distribution process can be set to be automatically started after a certain period of time by setting a timed start.

According to the above embodiment, the following operational effects can be obtained.

Management information about file distribution to the distribution destination device 30 is managed as a database, and at the time of file distribution, information for acquiring operating program information and resource information of the distribution destination device is acquired. The information to be distributed to the file distribution destination apparatus is transferred to the file distribution destination apparatus based on the comparison result of the comparing means and the management information. The timing is not limited to when the distribution destination device 30 is powered on. That is, even when the distribution destination device 30 is performing the distributed design of the LSI, when the registration device 20 issues a file distribution instruction as necessary, the file distribution is performed accordingly. Then, at the time of file distribution, the operating program information of the distribution destination device and the information for acquiring the resource information are acquired, the management information of the management database is compared, and the file distribution is performed based on the comparison result. As described above, the version inconsistency among a plurality of files does not occur, and the files can be safely distributed to each distribution destination device 30.

Next, based on the flow chart shown in FIG.
Another embodiment will be described.

In the embodiment shown in FIG. 5, the distribution management apparatus 10 performs the main processing for file distribution. That is, the function of the download client 33 in FIG. 1 is realized by the management server 14 of the distribution management device 33.

When the process for distribution management is started (step 401), the management server 14 in the distribution management device 10 is started.
The distribution file specifications and the distribution program information are acquired by (step 402). The distribution file specifications and the distribution program information can be acquired by referring to the management database 13. If there is a file to be distributed to the distribution destination device 30 due to a version upgrade of the program, etc., the management server 14 makes a distribution destination information request to the distribution destination device 30 (step 403), and the request is the distribution destination device. If it is accepted by the device 30 (step 404), this distribution destination device 30
At step 405, the monitor server 34 acquires the information of the program currently operating and the resource information, and the information is transmitted to the distribution management device 10 (step 406). In the distribution destination device 30, normally, the LS
The program for distributed design of I has been started, and the processing from step 404 to step 406 is performed in parallel with the processing for distributed design of LSI by multitasking. In other words, when the distribution management apparatus 10 makes a distribution destination information request (step 403) despite the processing for distributed design of the LSI, the request is accepted. The operation program information and the resource information are acquired and transmitted to the distribution management device 10 (steps 404-40).
6).

When the distribution management apparatus 10 acquires the information transmitted in step 406, the management server 14
Thus, the management database 13 is referenced again, and it is determined whether or not the file to be distributed to the distribution destination device 30 can be distributed at present (step 40).
8). If it is determined in this determination that the file can be distributed, the file transfer protocol controller 12 controls the file transfer from the master library 11 to the distribution destination device 30 via the Ethernet 40. (Step 409). In the distribution destination device 30, the file from the distribution management device 10 is stored in the distribution library 31 under the control of the file transfer protocol controller 12. If a file with the same name as the stored file exists in the distribution library 31, the file is updated by overwriting it, but if the transferred file is a new file, it is distributed. It is stored as a new library in the destination device 30.

From the distribution management device 10 to the distribution destination device 3
The file to be transferred to 0 is the distribution destination device 30
If the program file currently being executed is overwritten, or if there is a risk of version inconsistency among a plurality of files due to file distribution, the management server 14 determines that distribution is not possible, and File distribution is avoided (step 41)
0). Execution of distribution in step 409, or step 4
Due to the avoidance of distribution in step 10, the processing for file distribution is terminated (step 411). However, as long as the file to be distributed to the distribution destination device 30 exists in the master library 11, the above-mentioned management information in the management database 13 The series of processes described above can be repeatedly executed.

Thus, the download client 3
Even if the function 3 is realized by the management server 14, the same effect as in the above embodiment can be obtained.

Although the invention made by the present inventor has been specifically described based on the embodiments, the present invention is not limited thereto, and it goes without saying that various modifications can be made without departing from the scope of the invention. Yes.

For example, referring to FIG. 4, processing by executing the server program (steps 506 to 508)
May be performed by the distribution management device 10.

In the above description, TCP is a field of application which is the background of the invention mainly made by the present inventor.
Although the description has been given of the case of applying the network system which is connected to the Ethernet of / IP, the present invention is not limited thereto and can be applied to the system by the communication net connection of various types.

The present invention can be applied on condition that at least a data processing device is included.

[0040]

The effects obtained by the typical ones of the inventions disclosed in the present application will be briefly described as follows.

That is, the management information about the file distribution to the distribution destination device is managed in a database and managed, and at the time of file distribution, the operating program information of the distribution destination device,
And the information for acquiring the resource information, the acquired information is compared with the management information, and the file to be distributed to the file distribution destination device is determined based on the comparison result of the comparing means. Since the file is transferred to the distribution destination device, the timing of file distribution is not limited to only when the distribution destination device is powered on. That is, even when the distributed design of the LSI is performed by the distribution destination device, the file distribution is performed as necessary.
Further, since the program file can be urgently distributed to the device that operates overnight, the number of man-hours for version management can be reduced. When the file is distributed, the operating program information and resource information of the distribution destination device are acquired, and the file is safely distributed to each distribution destination device by comparing it with the management information in the management database. You can In this way, file distribution can be performed safely, and the reliability of the system can be improved.

[Brief description of drawings]

FIG. 1 is a block diagram of a configuration example of a network system that is an embodiment of the present invention.

FIG. 2 is an explanatory diagram of a management database included in the network system.

FIG. 3 is a basic flow chart of file distribution processing in the network system.

FIG. 4 is a detailed flowchart of file distribution processing in the network system.

FIG. 5 is a detailed flowchart of file distribution processing in the system of another embodiment.

FIG. 6 is an explanatory diagram when distribution of a program is prohibited due to a relationship with an operating system.

FIG. 7 is an explanatory diagram of program version inconsistency in program distribution.

[Explanation of symbols]

10 Distribution Management Device 11 Master Library 12, 22, 32 File Transfer Protocol Controller (ftp) 13 Management Database 14 Management Server 20 Registration Device 21 Original Library 23 Registration Client 30 Distribution Destination Device 31 Distribution Library 33 Download Client 34 Monitor Server

Claims (4)

[Claims] 1. A version management system for performing version management of files handled by network-connected devices, and storage means for storing management information about file distribution to a file distribution destination device, and a file distribution destination. Monitor means for acquiring the program information and resource information during operation of the device, comparison means for comparing the information acquired by this monitor means with the management information in the storage means, and this comparison means A version control system comprising: transfer control means for transferring a file to be distributed to a file distribution destination device to the file distribution destination device based on a comparison result. 2. In a network system in which a plurality of data processing devices are connected to each other by a network, a monitor means for monitoring a currently operating program and resource information, management information for file distribution, and the monitor means. A first data processing device comprising a comparison means for comparing with monitor information and a transfer control means for controlling a file fetch based on a comparison result of the comparison means, and the first data processing device. A network system comprising: a storage unit for storing management information to be compared with the monitor information; and a second data processing device having a management unit for managing the storage unit. 3. A network system comprising a plurality of data processing devices connected to each other in a network, the first data processing device having monitor means for monitoring a currently operating program and resource information, and the first data. A storage unit for storing management information about file distribution to the processing device, and a file to be distributed to the first data processing device based on the storage information of the storage unit and the monitor information of the monitoring unit. A second data processing device having a transfer control means for transferring the data to the first data processing device. 4. The network system according to claim 2, further comprising a third data processing device for registering a file in the second data processing device.