JP2002051363A - Patch file input status monitoring device and patch file input status monitoring method - Google Patents

Abstract

(57) [Summary] [Purpose] To reduce the trouble of the user, improve the visibility, increase the amount of information that can be viewed at one time, improve the visibility, and grasp the correlation between exchanges of different exchange types. . SOLUTION: A patch file which has been actually input for a plurality of designated exchange units 11 is extracted, a patch file to be applied for the exchange unit 11 is extracted, and the patch file corresponding to each exchange unit is extracted. An unapplied patch file is detected based on the already-applied patch file and the input target patch file, and the unapplied patch file specifying information for identifying the unapplied patch file for each switching unit 11 is transmitted to the workstation 14 as mail.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a patch file input status monitoring device and a patch file input status monitoring method, and more particularly to a patch file input status monitoring device for monitoring a patch file input status for a control program of an exchange. It relates to a method for monitoring the patch file input status.

[0002]

2. Description of the Related Art A control program for performing various controls in an exchange needs to be improved or a so-called bug corrected. In such a case, a patch file that extracts only the changed points of the control program is input, and the processing corresponding to the patch file is performed instead of the processing before the input. Will be corrected. Such input of the patch file is performed a plurality of times, and a different patch file is created for each control program. Therefore, input management of the patch file is very important. In order to manage the input of patch files, in the conventional system, a database storing the input status of the patch files, a work terminal for managing the database, and a user terminal for actually referring to the data are provided. .

Next, an outline operation of the conventional system will be described with reference to FIG. When performing the input management, first, the work terminal requests the server to acquire data from the database (step S61). Thereby, the server acquires data from the database (step S6).
2). Thereafter, when the server requests data conversion via the browser of the user terminal (step S63), the server performs a conversion process based on the data acquired from the database (step S64). Then, the user inputs the location area (location area) of the exchange to be managed for inputting the patch file, the exchange type, and the file generation of the control program, and requests browsing of a desired patch file input management screen (step S65).

[0004] Thereby, the server displays a patch file input management screen corresponding to the location of the exchange, the exchange type, and the file generation of the control program requested by the user terminal as a web page on the display screen of the user terminal. (Step S66). Further, on the displayed patch file input management screen, the user searches for and selects an exchange to be confirmed. As a result, for example, a patch file input management screen is displayed on the display screen of the user terminal with 50 patch files and browsable for every eight exchanges (step S67).

[0005]

In the above conventional system, a patch file input management screen is displayed on a user terminal after a request for data acquisition from a database at a work terminal. The file input management screen cannot be displayed,
There is a problem that user manual operation (manual intervention) is often performed and operability is poor. Further, in the above-described conventional system, the patch file input management screen is displayed without considering the relevance between exchanges to be considered at the time of inputting the patch file.

Further, since the patch file input management screen is displayed as a web page, there is a problem that the number of pieces of information that can be browsed at one time is severely limited. In addition, since the patch file submission management screen displays information about exchanges for which no patch file has been submitted,
Since the information of the exchanges having different file generations to which the input viewing target patch file is not to be input is also displayed, there is a problem that visibility is poor.

Furthermore, there is a problem that the correlation between exchanges of different exchange types cannot be grasped. Therefore, an object of the present invention is to reduce the trouble of the user, improve the visibility, increase the amount of information that can be viewed at one time, improve the visibility, and at the same time, correlate the exchanges of different exchange types. It is another object of the present invention to provide a patch file input status monitoring device and a patch file input status monitoring method capable of ascertaining the status.

[0008]

According to a first aspect of the present invention, there is provided an apparatus for extracting a patch file which has been actually submitted to a plurality of designated switching units. An input patch file extractor, an input target patch file extractor that extracts an input target patch file that is a patch file to be input for the exchange unit, the input input patch file and the input target corresponding to each of the exchange units. An unsubmitted patch file detection unit that detects an unsubmitted patch file that is an unsubmitted patch file based on a patch file, and information that outputs non-submitted patch file specifying information that specifies the unsubmitted patch file for each of the switching units. And an output unit.

According to a second aspect of the present invention, in the configuration of the first aspect, the input target patch file extracting unit extracts the input target patch file based on a file generation corresponding to the switching unit. And

A third aspect of the present invention is characterized in that, in the second aspect, a file generation information database for storing file generation information for specifying a file generation corresponding to the exchange unit is provided.

According to a fourth aspect of the present invention, in the configuration of the second or third aspect, there is provided a correlation detector for detecting a correlation between the types of the plurality of switching units,
The non-submitted patch file detection unit detects the non-submitted patch files in the order of the correlation.

According to a fifth aspect of the present invention, in the configuration according to any one of the first to fourth aspects, the information output section outputs the non-input patch file specifying information as text data. I have.

According to a sixth aspect of the present invention, in the configuration according to any one of the first to fifth aspects, the information output unit transmits the non-input patch file specifying information as an e-mail to an external work terminal. It is characterized by having a mail transmission unit.

According to a seventh aspect of the present invention, an input patch file which is a patch file actually input to a plurality of designated exchange units is extracted, and an input patch file to be input to the exchange unit is extracted. A target patch file is extracted, an unsubmitted patch file that is a non-submitted patch file is detected based on the already-submitted patch file corresponding to each of the switching units and the submission target patch file, and the non-submitted patch file for each switching unit is detected. It outputs non-submitted patch file specifying information for specifying a submitted patch file.

According to a eighth aspect of the present invention, in the configuration of the seventh aspect, when extracting the input target patch file, the input target patch file is extracted based on a file generation corresponding to the switching unit. Features.

According to a ninth aspect of the present invention, in the configuration of the eighth aspect, a correlation between the types of the plurality of switching units is detected, and the unsubmitted patch files are detected in the correlation order. I have.

According to a tenth aspect, in the configuration according to any one of the seventh to ninth aspects, the non-input patch file specifying information is output as text data.

[0018] According to an eleventh aspect of the present invention, in the configuration according to any one of the seventh to tenth aspects, the non-input patch file specifying information is transmitted to an external work terminal as a mail.

[0019]

Preferred embodiments of the present invention will now be described with reference to the drawings. [1] Configuration of the Embodiment FIG. 1 is a block diagram showing the schematic configuration of the patch file input management system of the embodiment. The patch file input management system 10 includes a database device 12 in which a database for grasping patch file input status corresponding to a plurality of exchange units 11 is stored, and a database device 1.
Server 2 that is connected to the LAN 2 via a network such as a LAN and controls the database device 12 and the like.
3 and a workstation 14 functioning as an operation terminal for performing various operations and various settings for performing patch file input management via the server 13.

[2] Outline Operation of Embodiment Next, an outline operation of the patch file input management system of the embodiment will be described. FIG. 2 shows an outline sequence flow of the patch file input management system 10. When the maintenance worker makes a request for a work condition check to the server via the work station 14 (step S11), the server 13 acquires data from the database device 12 (step S12), and acquires the acquired data. The correlation between the exchange types is checked based on the
3). More specifically, as shown in FIG. 3, the maintenance worker specifies an operation system from which data should be extracted as a work condition check process to the server 13 (step S21).

Next, the server 13 acquires the exchange unit information constituting the designated operation system (step S22), and correlates the unit information which is a correlation between the exchange types (step S23). Subsequently, the server 13 checks the file generation (file version number) of each exchange in the order of the relation between the exchange types (step S1).
4). Further, the server 13 checks the input status of the patch files that need to be input for each file generation in the order of the relation between the exchange types (step S15). More specifically,
As shown in FIG. 4, the server 13 sends from the database device 12 a patch file (indicated by PLG in the figure; the same applies hereinafter) to be input corresponding to the file generation (file version number) of the exchange unit to be checked. Extraction is performed (step S31), and the input state is checked, that is, an uninputted patch file is detected (step S32).

The management number corresponding to the not-yet-submitted patch file is transmitted to the maintenance worker as text data mail together with the exchange unit name and the file generation (step S16). As a result, the maintenance worker who is working at the workstation 14, which is the work terminal, can easily grasp the input state of the patch file by checking the contents of the mail.

[3] Detailed Operation of Embodiment Next, a detailed operation of the server of the embodiment will be described with reference to FIGS. FIG. 5 shows a detailed operation flowchart.
The server 13 has a designated operation system (O
(pS) is extracted (step S41), and a unit database is created (step S41).
42) The following processing is executed for each unit. Subsequently, the server 13 determines whether the check of all the exchange units has been completed (step S43). Step S43
If it is determined that all the exchange units have not been checked (step S43; No), the server 1
3 outputs the unit name of the exchange unit to be checked and the file generation of the corresponding control program to a file, and performs counting for each type of exchange unit (step S44).

Next, the server 13 extracts an already applied patch file which is a patch file input status in the designated operation system (OpS) (step S).
45), create an already entered data database (step S46). Subsequently, the server 13 extracts an input target patch file (described as an outgoing PLG in the figure) which is a patch file to be input for the exchange unit in the specified operating system (step S).
47), an outgoing PLG database is created (step S48). Then, the server 13 determines the number of extracted input target patch files (the number of patch files) by the following step S49.
And the process of step S50 is performed. Then the server 13
Determines whether the check has been completed for all input target patch files (step S49).

More specifically, for example, in the case of the transmission mail display screen shown in FIG. 6, the management number of the patch file to be input to the exchange unit “Matsuyama 4MLS” is 2
It is assumed that the number is 60 to 278. In this case, if the management number of the patch file to be submitted which is currently being checked is 270 from 260, it is still 271 to 2
Since the check has not been completed for the input target patch file corresponding to the management number 78, step S50 is performed.
The processing shifts to. Then, it is determined whether or not an input target patch file corresponding to the management number to be checked has already been input to the exchange unit, and if not, the control number is output to a file for transmission (step S50).

More specifically, for example, when the management numbers of the unsubmitted patch files of the exchange unit “Matsuyama 4MLS-A” are 266 to 278, as shown in FIG. Exchange unit name = "Matsuyama 4
MLS-A ”, file generation =“ 1999A ”, management number of unsubmitted patch file =“ 266: 267: 26 ”
8: 269: 270: 271: 272: 273: 27
4: 275: 276: 278 "is output and written in the text data format. Thereafter, if it is determined in step S49 that the check has been completed for all the input target patch files (step S49; Yes), the process proceeds to step S43, and it is determined whether or not it has been restarted. It is determined whether the check of the exchange unit has been completed (step S43),
When the check of all the exchange units is completed (Step S43; Yes), the file for transmission is transmitted to the workstation 14 as a mail (Step S5).
1).

As a result, at the workstation 14 receiving the mail, when the maintenance worker opens the mail, as shown in FIG. 6, following the header information HD such as the title, date, sender and destination, the exchange unit First name "XXMLS-
A, the file generation and the patch file management number of the not-yet-submitted patch file for the exchange represented by “A” are displayed as a patch file submission management screen, and the exchange unit name “XXM
The file generation and the unprocessed patch file management numbers of a plurality of exchanges represented by the exchange unit name “$ SBM-O □” related to the exchange represented by “LS-A” are displayed as information of one group. , A plurality of groups of information will be displayed.

More specifically, the file generation = “1999A” and the patch file management number = “266: 267: 268: 269: 270:” for the exchange represented by the exchange unit name “Matsuyama MLS-A” 27
1: 272: 273: 274: 275: 276: 27
8 ”is displayed, and the exchange unit name is“ Matsuyama MLS ”.
-A "," Matsuyama 1SBM-OA "," Iyo Ishii 2SBM-O "
A ”,..., File generation =“ 1999A ”and the unexamined patch file management number =“ 009 ”for the four exchanges represented by“ Shinshin 2SBM-OA ”are displayed as information of one group. Similarly, information of a plurality of groups such as the exchange unit names “Yamagoemoto MLS-A”, “Matsuyama 3MLS-A”,... Is displayed.

[4] Effects of Embodiment As described above, according to this embodiment, the workstation (work terminal) 14 is configured to display the data acquisition and patch file input management screen. The patch file input management screen can be displayed only on the work terminal, and if the processing procedure is determined in advance so that processing is performed automatically, such as with an autopilot, manual operation (manual intervention) by the user can be reduced. Thus, processing can be performed at night or the like. In addition, the patch file input management screen is displayed in consideration of the relevance between exchanges to be considered when the patch file is input, so that the visibility is improved. Further, since the patch file input management screen is displayed in the text data format, the limit on the number of information items that can be viewed at one time is eased. In addition, since the patch file input management screen corresponds to the patch file to be input and displays information about exchanges for which no patch file has been input, information on exchanges that do not need to be displayed for management is displayed. And the visibility is improved. Furthermore, the correlation between exchanges having different exchange types can be easily grasped.

[5] Modification of Embodiment In the above description, a configuration is adopted in which a mail corresponding to the patch file input screen is transmitted, but a text data format file corresponding to the patch file input screen is transmitted as it is. Any form can be used as long as the data amount is not so large, such as a file format that includes a simple display control code in addition to text data, and the display can be kept simple.

[0031]

According to the present invention, it is possible to reduce the trouble of the user, improve the visibility, increase the amount of information that can be browsed at a time, improve the visibility, and change the exchange types. And a patch file input state monitoring method and a patch file input state monitoring method capable of grasping the correlation of the patch file input state.

[Brief description of the drawings]

FIG. 1 is a schematic configuration block diagram of a patch file input management system according to an embodiment.

FIG. 2 is a schematic sequence flowchart of a patch file input management system.

FIG. 3 is a flowchart (part 1) of a detailed process of a part of FIG. 2;

FIG. 4 is a flowchart (part 2) of a detailed process of a part of FIG. 2;

FIG. 5 is a detailed operation flowchart of the embodiment.

FIG. 6 is an explanatory diagram of a display example of a patch file input management screen.

FIG. 7 is an explanatory diagram of a conventional example.

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 10 ... Patch file input management system 11 ... Exchange unit 12 ... Database device 13 ... Server 14 ... Work station (operation terminal)

 ──────────────────────────────────────────────────続 き Continued on the front page F term (reference) 5B076 EA01 5K019 AA02 BA22 BA40 DA03 5K026 AA09 BB03 CC07 FF01 FF21 GG27 5K051 AA09 BB01 BB02 CC01 CC02 CC04 CC07 DD01 EE01 EE02 FF01 KK05

Claims (11)

[Claims] A patch file extraction unit for extracting a patch file that has been actually submitted for a plurality of designated switching units; and a patch file to be submitted for the switching unit. An input target patch file extraction unit that extracts an input target patch file; and detects an uninputted patch file that is an uninputted patch file based on the already applied patch file and the input target patch file corresponding to each of the switching units. A patch file input state monitoring device, comprising: a non-input patch file detection unit; and an information output unit for outputting non-input patch file specifying information for specifying the non-input patch file for each of the switching units. 2. The patch file input state monitoring device according to claim 1, wherein the input target patch file extracting unit extracts the input target patch file based on a file generation corresponding to the switching unit. Patch file input status monitoring device. 3. The patch file input status monitoring apparatus according to claim 2, further comprising: a file generation information database for storing file generation information for specifying a file generation corresponding to the exchange unit. Condition monitoring device. 4. The patch file input state monitoring device according to claim 2, further comprising: a correlation detection unit that detects a correlation between the types of the plurality of switching units, wherein the non-input patch file detection unit. The patch file input state monitoring device detects the uninputted patch file in the correlation order. 5. The patch file input state monitoring device according to claim 1, wherein the information output unit outputs the non-input patch file specifying information as text data. Patch file input status monitoring device. 6. The patch file input status monitoring device according to claim 1, wherein the information output unit transmits the non-input patch file specifying information as an email to an external work terminal. A patch file input state monitoring device comprising a transmission unit. 7. Extracting an applied patch file, which is a patch file actually applied to a plurality of designated exchange units, and extracting an installation target patch file, which is a patch file to be applied to the exchange unit. Detecting an unsubmitted patch file that is a non-submitted patch file based on the already-submitted patch file and the submitted patch file corresponding to each of the switching units, and identifying the non-submitted patch file for each of the switching units; A patch file input status monitoring method, which outputs uninputted patch file identification information. 8. The patch file input status monitoring method according to claim 7, wherein the input target patch file is extracted based on a file generation corresponding to the switching unit when extracting the input target patch file. Patch file input status monitoring method. 9. The patch file input state monitoring method according to claim 8, wherein a correlation between the types of the plurality of switching units is detected, and the uninput patch files are detected in the correlation order. Patch file submission status monitoring method. 10. The patch file input status monitoring method according to claim 7, wherein the non-input patch file specifying information is output as text data. . 11. The patch file input state monitoring method according to claim 7, wherein the non-input patch file specifying information is transmitted as an e-mail to an external work terminal. Input state monitoring method.