JP5683209B2 - Client computer with automatic document generation function - Google Patents

Description

  The present invention relates to an operation technique for a UNIX (registered trademark) server computer using a telnet (telnet communication network) connection by a client computer, and in particular, a trail when executing the same operation while leaving a trail in a plurality of environments. The present invention relates to a client computer with a document automatic generation function that automatically generates operation documents (operation procedure manuals, checklists, shell script documents) by using.

  Conventionally, when a user operates a UNIX server computer, data is input from a terminal device of a client computer (computer terminal) and an output to be responded is confirmed. In recent years, for terminal devices, it is common to use a terminal emulator (software for substituting the functions of a dedicated terminal with a personal computer, a UNIX workstation, or the like) that operates on a cheaper client computer.

  In the case of a terminal emulator that runs on a client computer, it is easy to link with other applications that run on the client computer. For example, a character string input during operation is recorded as a trail in the operation log file, and the contents of the operation log are confirmed, or a character string created with a text editor is copied to the clipboard and pasted into a terminal emulator. Therefore, the operation from the terminal emulator can be facilitated. In addition, when performing operations that require a large amount of command input or when performing the same operation on different UNIX server computers, it is possible to shorten the operation time and to prevent erroneous operations by facilitating the character string of the operation contents before starting the operation. Prevention becomes possible.

  If an operation document for performing the same operation as the operation log is created based on the operation log in which the operation content from the terminal emulator is recorded, an operation document with an operation record can be created.

  In addition, a technique for automatically generating a document by recording a command given to a UNIX server computer has been proposed. For example, as a known technique, a command given to a UNIX server computer and an execution result are automatically recorded in a check list. "Command execution result recording system and command execution result recording method" (see Patent Document 1).

  A command execution result recording system disclosed in Patent Document 1 includes a plurality of work target servers having a computer that executes a command and outputs the execution result of the executed command as a return value, and commands to the computers of these work target servers. And an operation terminal having a computer for determining a return value of an execution result of the executed command.

  The operation terminal here is a predetermined command, work content information indicating the work content of the predetermined command, a normal return value output when the predetermined command is executed by a predetermined work target server, An execution command table storing a confirmation ID attached to a confirmation command when the command is executed, a confirmation ID, and a confirmation item information table storing a confirmation command corresponding to the confirmation ID, A shell script including a predetermined command and work content information read from the execution command table and a confirmation command corresponding to the confirmation ID read based on the confirmation ID from the confirmation item information table is generated. Further, the operation terminal receives the work content information corresponding to the command included in the generated shell script, the work target server name input so as to execute the command corresponding to the work content information, the work content information and the work target server name. Generate checklist information including confirmation result information in combination with.

JP 2007-304660 A

  Although the technique described in Patent Document 1 described above can improve the efficiency of the confirmation work by systematizing the checklist in the confirmation work, a large-scale system development is required to actually introduce and construct the technique. There is a problem of becoming.

  In addition, as a work method in the system change work, it is possible to generate a procedure manual for the work to be performed and a check list describing items to be confirmed in the work, and fill in the results for each work item at the time of work. According to the method, it is possible to prevent omissions in work procedures, mistakes in the confirmation of work results, and omissions in work hosts. However, if new functions are frequently added, check them. Since the work procedure is frequently changed without being standardized, there is a problem that human error is likely to occur when creating the procedure manual.

  In short, according to the technique described in Patent Document 1, when a new function is frequently added, an operation document for a UNIX server computer cannot be generated accurately with a small system configuration. It has become.

  The present invention has been made to solve such problems, and the technical problem is that even if new functions are frequently added, the UNIX server computer can be appropriately configured with a small system configuration. It is an object of the present invention to provide a client computer with an automatic document generation function capable of generating an operation document for a user.

In order to achieve the above technical problem, a client computer with an automatic document generation function according to the present invention includes a virtual terminal device that performs an operation on a UNIX server computer connected to a telnet, and an operation when the virtual terminal device executes the operation. by editing the operation log file recorded by entering the log, the results of analysis and output content on a UNIX server computer in response to the execution command and the command for the execution of the operation log acquired from the operation log file An automatic document generation function unit that automatically generates an operation document , the virtual terminal device is a terminal emulator, and the operation log operates on another client computer connected to the UNIX server computer through a telnet connection. The same with the application Includes trail for performing operations in multiple environments of, the document such operation documents, operating procedures that are created by using the trail, characterized to include a checklist, and shell scripts .

Further, in one embodiment of the client computer with automatic document generation function, the shell script checks the operation procedure manual according to the input to the virtual terminal device by the automatic document generation function unit when applied from the test environment to the production environment. When the list is digested, it is transferred to a UNIX server computer .

According to the client computer with an automatic document generation function of the present invention, in the operation / maintenance work of the UNIX server computer that provides the business processing service, the UNIX server is operated by the virtual terminal device (terminal emulator) provided in the own device. When an operation document is automatically generated by editing a result of analyzing a command for execution of a predefined operation log and a content output from a UNIX server computer in response to the execution command for a predefined operation log , An operation procedure document as a document of an operation document using a trail for executing the same operation in a plurality of environments in cooperation with an application running on another client computer connected to a UNIX server computer via a network connection, Checklist and Order to have the ability to create Le script, do the same operation as the operation to be performed in a real system change work during the rehearsal of the test environment, operation document (operation based on the operation log from the operation log file that is output (Procedures, checklists, and shell scripts) can be used to efficiently create operation documents that can be used during system changes in a production environment, even when new functions are frequently added. Thus, an operation document for a UNIX server computer can be generated accurately with a small system configuration. As a result, it is possible to perform data management with simple input / output processing without requiring a large-capacity database in operation / maintenance work of UNIX server computers, and reduce the occurrence of result confirmation mistakes and work omissions. Will be able to.

BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 is a block diagram showing an overall configuration of a system operating environment including a client computer with an automatic document generation function according to Embodiment 1 of the present invention and a UNIX server computer connected to the client computer. 3 is a flowchart showing an operation process of an analysis processing unit provided in a document automatic generation function unit which is a main part of the client computer with a document automatic generation function shown in FIG. 1. 3 is a flowchart showing an operation process of an editing processing unit provided in a document automatic generation function unit, which is a main part of the client computer with a document automatic generation function shown in FIG. 3 is a flowchart showing an operation process of an output processing unit provided in a document automatic generation function unit which is a main part of the client computer with a document automatic generation function shown in FIG. 1. FIG. 2 is a diagram specifically illustrating on a display screen of a display device to which operation log data of an operation log file provided in the client computer with an automatic document generation function shown in FIG. 1 is attached. FIG. 2 is a diagram illustrating a specific data configuration of an operation procedure manual which is an example of a document of an operation document generated by an automatic document generation function unit which is a main part of the client computer with an automatic document generation function illustrated in FIG. 1. is there. FIG. 3 is a diagram illustrating a specific data configuration of a check list that is another example of documents of an operation document generated by a document automatic generation function unit that is a main part of the client computer with the document automatic generation function illustrated in FIG. 1. is there. It is the figure which illustrated the data structure of the shell script which is another example of the document of the operation document produced | generated by the document automatic generation function part which is the principal part of the client computer with a document automatic generation function shown in FIG. It is the figure which illustrated the data content of the fixed form command code corresponding table | surface used by the operation | movement process of the analysis process part demonstrated in FIG. FIG. 10 is a diagram exemplifying data contents of a routine operation content code correspondence table used in the operation process of the editing processing unit described in FIG. 3 and corresponding to the routine command code illustrated in FIG. 9; FIG. 11 is a diagram exemplifying data contents of a standard confirmation content code correspondence table corresponding to the standard operation content code shown in FIG. 10 and used in the operation processing of the editing processing unit described in FIG. 3. It is the figure which illustrated the specific data structure of the analysis information obtained by the analysis process part demonstrated in FIG. It is the figure which illustrated the specific data structure of the edit information obtained by the edit process part demonstrated in FIG. FIG. 2 is a functional block diagram specifically illustrating a sequence in a case where a client computer with an automatic document generation function shown in FIG. 1 is applied during system change work and rehearsal is performed in a test environment and then work is performed in a production environment.

  Hereinafter, a client computer with an automatic document generation function of the present invention will be described in detail with reference to the drawings.

  FIG. 1 shows a client computer 101 with automatic document generation function (hereinafter referred to as a client PC) 101 according to the first embodiment of the present invention, and a UNIX server computer (hereinafter referred to as a server) connected thereto by a telnet 102. 1 is a block diagram showing the overall configuration of a system operating environment including 103).

  In this overall configuration of the system operating environment, the client PC 101 connected to the server SV 103 via the telnet 102 inputs a virtual terminal device 104 that performs an operation on the server SV 103 and an operation log when the virtual terminal device 104 executes an operation. The operation document is automatically analyzed by analyzing and editing the operation log file 105 recorded in this way, the execution command for the operation log acquired from the operation log file 105, and the output content of the server SV 103 in response to the execution command. And a document automatic generation function unit 106 to be generated.

  Incidentally, as is well known, the client PC 101 and the server SV 103 are configured to include a schematic CPU, a main memory, a storage device such as an auxiliary storage unit (HDD), an input / output device such as a display device, a keyboard, and a mouse. It is what is done.

Among these, the virtual terminal device 104 is constructed by a terminal emulator. The operation log recorded in the operation log file 105 includes the same operation in a plurality of environments in cooperation with an application AP operating on another client computer (client PC) connected to the server SV 101 via a telnet connection. Includes a trail to execute. Further, the documents of the operation document generated by the document automatic generation function unit 106 include an operation procedure manual 110 using a trail, a check list 111, and a shell script 112. Among these, the shell script 112 is used to be transferred to the server SV 101 when the check list 111 is digested according to the input of the operation procedure manual 110 by the automatic document generation function unit 106 when applied from the test environment to the production environment. The In addition, the automatic document generation function unit 106 includes an analysis processing unit 107 that analyzes the operation log, an editing processing unit 108 that edits the analysis result, and an output processing unit 109 that outputs the editing result. The function of will be described in detail later.

  That is, when the client PC 103 operates the server SV 101 via the telnet 102 by the virtual terminal device (terminal simulator) 104, the operation log file 105 inputs the operation log output from the terminal simulator in the device. The analysis processing unit 107 analyzes the execution command for the operation log acquired by the document automatic generation function unit 106 from the operation log file 105 and the output content of the server SV 101 in response to the execution command. The editing process unit 108 generates the operation procedure manual 110, the check list 111, and the shell script 112 as document types of the operation document by performing the editing process and the output processing unit 109.

  When the document automatic generation function unit 106 generates an operation document based on the operation log, the content of the operation log includes a prompt, an operation command (execution command) and an operation command output on the terminal emulator. It becomes a character string (output contents) composed of a standard output to which the server SV 101 responds, and these execution commands and output contents are output on the client PC 103. Since an operation document is generated based on an operation log in a single client PC 103, it is not necessary to have a large-scale system configuration having a large-capacity database for recording operation contents. It can be operated.

  FIG. 2 is a flowchart showing an operation process of the analysis processing unit 107 provided in the document automatic generation function unit 106 which is a main part of the client PC 103.

  Referring to FIG. 2, in the operation process (analysis process) of the analysis processing unit 107, initialization (step S201) is first performed, the operation log (step S202) of the operation log file 105 is accessed, and the operation log is executed. After reading the row sequential operation log to be read in units (step S203), it is determined whether or not the file is EOF (end) (step S204).

  Next, as a result of determining whether or not the file is EOF (end) (step S204), if it is EOF (end), the operation processing is terminated. If not EOF (end), the row counter is set to “1”. After the processing of line counter +1 (step S205) is added, it is determined whether the line read from the file is a command line (step S206).

  Further, as a result of the determination of whether or not it is a command line (step S206), if it is a command line, after setting the command line flag to “ON” (step S207), the operation log as shown in FIG. The fixed command correspondence table (step S208) related to the execution command is accessed to determine whether the command is a fixed command (step S209). If the result of this determination is that the command is a standard command, the processing for extracting the parameters of the standard command (step S211) after setting the corresponding standard command code (step S210) is performed, and then the analysis information is output (step S212). The analysis information extracted for the analysis information file by the process is output (step S213) and recorded, but if it is not a standard command, the contents of the command are extracted (extracted as it is) (step S214). Thereafter, similarly, the analysis information extracted from the analysis information file by the processing of the analysis information output (step S212) is output (step S213) and recorded.

  If the command line is not the command line as a result of the determination as to whether or not the command line (step S206), the command line flag is set to "OFF" (step S215), and then the determination as to whether or not the message is a standard command ( Step S216) is performed. As a result of this determination, if the message is a standard command, information in the message necessary for the type of the standard command is extracted, information corresponding to the standard command is extracted (step S217), and analysis information is output (step S217). The analysis information extracted in the analysis information file by the process of S212) is output and recorded (step S213), but if the message is not a standard command, the content of the message is extracted (extracted as it is) (step S218). After performing the process, the analysis information extracted in the analysis information file by the process of the analysis information output (step S212) is output (step S213) and recorded. In addition, after recording the analysis information such as the code of the standard command extracted by the analysis information output (step S212) processing in the analysis information file, the process returns to the initial initialization (step S201) in any case. Each process described above is repeated until the end of file (EOF) is reached. That is, the completion of the operation process is the time point when it is determined that the file is EOF (end) as a result of the determination as to whether the file is EOF (end) (step S204).

  FIG. 12 is a diagram illustrating a specific data configuration of analysis information as an analysis result obtained by the analysis processing unit 107 here. The analysis information in FIG. 12 holds specific data about items, contents, and samples in the order of item numbers.

  FIG. 3 is a flowchart showing an operation process of the edit processing unit 108 provided in the document automatic generation function unit 106 which is a main part of the client PC 103.

  Referring to FIG. 3, in the operation process (edit process) of the edit processing unit 108, initialization (step S301) is performed first, the analysis information (step S302) of the analysis information file is accessed, and the analysis information is stored in line units. After reading line sequential analysis information (step S303), it is determined whether or not the file is EOF (end) (step S304).

  Next, as a result of determining whether or not the file is the EOF (end) (step S304), if it is EOF (end), the editing information file is accessed by the processing of the editing information output (step S305) of the previous operation. After the editing information (step S306) is recorded, the operation process is terminated, but if it is not EOF (end), the process of row counter + 1 (step S307) is performed to add “1” to the row counter.

  Further, it is determined whether or not it is the head of the operation (command input) (step S308), and if it is the head of the operation, it is determined whether or not the operation counter is “0” (step S309). If the operation counter is “0”, after performing the operation counter + 1 (step S310) for adding “1” to the operation counter, the routine operation corresponding to the above-described routine command code as shown in FIG. Processing for accessing the content code correspondence table (step S311) and setting the operation content corresponding to the command (step S312), and the standard confirmation content code correspondence table corresponding to the standard operation content code as shown in FIG. 11 (step S313) to access the command or set the confirmation content corresponding to the standard output (step S314) Return to normalization (step S301) and repeat the above-described processes until the end of file (EOF) is reached. If the operation counter is not "0", the editing information output (step S316) of the previous operation is processed. After accessing the editing information file and recording the editing information (step S317) and proceeding to the processing of the previous operation counter + 1 (step S310), the above-described processing is similarly performed.

  Subsequently, as a result of determining whether or not it is the head of the previous operation (command input) (step S308), it is determined whether or not the command line flag is “ON” if it is not the head of the operation (step S315). . As a result of the determination, if the command line flag is “ON”, the process proceeds to processing for setting the operation content corresponding to the command (step S312). If the command line flag is not “ON”, the command or standard output is supported. The process proceeds to processing for setting the confirmation content to be performed (step S314).

  The process of setting the operation content corresponding to the command (step S312) is to extract the operation content corresponding to each command code from the standard operation content code correspondence table (step S311). The process of setting the confirmation content corresponding to (Step S314) is to extract the confirmation content corresponding to each command code from the standard confirmation content code correspondence table (Step S313).

  In any case, each of these processes is repeated until the end of the file, and when the end of the file is reached, the editing information output to the editing information file (step S306) is performed through the above-described editing information output process (step S305). ) Is recorded, the operation process is completed.

  FIG. 13 is a diagram illustrating a specific data configuration of editing information as an editing result obtained by the editing processing unit 108 here. The edit information of FIG. 13 also holds specific data about items, contents, and samples in the order of item numbers (however, the sample for the operation counter value of item number 1 is initially undecided blank). )doing.

  FIG. 4 is a flowchart showing an operation process of the output processing unit 109 provided in the document automatic generation function unit 106 which is a main part of the client PC 103.

  Referring to FIG. 4, in the operation process (output process) of the output processing unit 109, first, initialization (step S401) is performed, the edit information in the edit information file (step S402) is accessed, and the edit information is stored in line units. After reading the line sequential edit information (step S403), it is determined whether the file is EOF (end) (step S404).

  Next, as a result of determining whether or not the file is EOF (end) (step S404), if it is EOF (end), the operation processing is terminated. If not EOF (end), the row counter is set to “1”. After the processing of the line counter +1 (step S405) to be added, the operation procedure manual (step S406) is generated by the operation procedure manual output (step S406) processing, and the check list output (step S408) processing is performed. The process of generating the check list (step S409) and the process of generating the shell script (step S411) by the shell script output (step S410) are sequentially performed, and then the process returns to the initial initialization (step S401) and described above. The operation procedure manual 110 is repeated by repeating each process until the end of file (EOF) is reached. Check list 111, to generate a shell script 112. That is, here, the completion of the operation process is the time when the above-mentioned file EOF (end) is determined to be EOF (end) as a result of the determination (step S404).

  FIG. 5 is a diagram specifically illustrating the operation log data of the operation log file 105 on the display screen of the display device to which the operation log data is attached.

  In the operation log display data 501 here, when the analysis processing unit 107 reads the operation log, a command prompt of the operation command 502 ($ (ftmst02 @ 2010: apftm05) or the like in the example shown in FIG. 5) exists. A message is extracted from the standard output 503 to which the server SV101 in other rows responds.

  FIG. 6 is a diagram illustrating a specific data structure of the operation procedure manual 110. FIG. 7 is a diagram illustrating a specific data configuration of the check list 111. Further, FIG. 8 is a diagram illustrating a data configuration of the shell script 112.

Referring to FIGS. 6 and 7, the operation procedure manual 110 and the check list 111 all have specific data on items, contents, generation methods, and samples corresponding to the order of item numbers. For the operation procedure manual 110, the purpose of the operation, the operation content (text), the operation content (command), the confirmation content during operation (text), the confirmation content during operation (standard output), the start time (planned), and the end time (Schedule), required time (schedule), name of the person in charge of operation, name of person in charge of confirmation, and remarks are illustrated.

  For the check list 111, the operation procedure document number, operation content (command), confirmation content during operation (standard output), operation person name, confirmation person name, start time (actual), end time (actual), The case where each item of required time (actual result) and remarks is required is illustrated.

  On the other hand, referring to FIG. 8, the shell script 112 has item contents such as [header information] 801, [title] 802, [creator] 803, [creation date] 804, [command] 805, and so on. It has been established.

  From the operation log, the operation content (command) that is an execution command and the operation confirmation content (standard output) that is the output content that the server SV101 responds can be extracted as a character string. The function unit 106 can acquire the operation content (command) and the confirmation content during operation (standard output). Also, the operation content (sentence) corresponding to the operation content (command) and the confirmation content (sentence) at the time of operation can be output and displayed on the display screen of the display device provided by extracting the standard text.

  In the document automatic generation function unit 106 of the first embodiment, when the operation procedure manual 110 is created, the above four items [operation content (command), confirmation content during operation (standard output), operation content (text), operation As for the confirmation content (text) at the time, the edit processing unit 108 and the output processing unit 109 automatically generate a layout including the contents. When the check list 111 is created, the above three items [operation procedure document item number, The operation content (command) and the confirmation content during operation (standard output)] can be exemplified by the case where the edit processing unit 108 and the output processing unit 109 automatically generate a layout including the content.

  Also, when creating the operation procedure manual 110 and the check list 111, the purpose of the operation, which is each other item, the start time (plan), the end time (plan), the required time (plan), the name of the person in charge of operation, and the person in charge of confirmation As for the name, remarks, start time (actual result), end time (actual result), and required time (actual result), it is possible to exemplify a case where only a layout not including the content is generated.

  By the way, the operation procedure manual 110 at the time of operation includes items that should function as the check list 111, such as the progress of work and the result confirmation in the confirmation operation. In such a case, a procedure for comparing the standard output content acquired during rehearsal and the standard output content acquired during the production system change work may be folded when the operation procedure manual 110 is generated. When a result confirmation operation is performed during rehearsal, a character string that identifies the operation can be detected when the operation procedure manual 110 is generated, and the check list 111 can be generated together with the operation procedure manual 110. Furthermore, since the operation command 502 extracted from the operation log shown in FIG. 5 can be easily processed into the shell script 112, the work procedure can be automated by performing a system change operation using the processed shell script 112. And prevention of erroneous operation can be realized. Specifically, if the operation command 502 is extracted from the operation log using the prompt as a key, and the shell script 112 in which the command for extracting the system date and time is inserted between the operation commands 502 is generated, the start time ( Actual), end time (actual), and required time (actual) can be extracted, and a shell script 112 having such items can be generated.

  FIG. 14 is a functional block diagram specifically illustrating a sequence in the case where the above-described client PC 103 is applied during system change work and rehearsal is performed in the test environment 1401 and then work is performed in the production environment 1414.

  In general, an ordinary commercial system in which the client PC 101 and the server SV 103 are connected via the telnet 102 has a test environment in addition to an environment that provides a service as a commercial service. An application in which rehearsal is performed using a test environment 1401 as shown in FIG.

Since the same operation as that performed in the actual system change work is performed during the rehearsal in the test environment 1401, the operation document (operation procedure manual 110, checklist) is based on the operation log from the operation log file 105 that is output. 111, a shell script 112), an operation document that can be used at the time of system change work in the production environment 1414 can be efficiently created. Note that the shell script 112 in the production environment 1414 is used to be transferred to the server SV 101 when the check list 111 is digested according to the input of the operation procedure manual 110 to the virtual terminal device 104 by the automatic document generation function unit 106. The

  The client PC 103 according to the first embodiment described above has the document automatic generation function unit 106 and automatically generates an operation document before performing the work (generate / execute the check list 111 associated with the execution command and the work content). Therefore, it is possible to reduce the result confirmation mistake at the time of work and the occurrence of work leakage of the work target server SV101. In addition, an operation document is automatically generated based on an operation log output from a terminal emulator which is the virtual terminal device 104, and a document automatic generation function is constructed by simple input / output data management without requiring a large-capacity database. Therefore, it can be operated in a small and general-purpose system environment. In particular, the document automatic generation function unit 106 is not included in the terminal emulator itself, but is prepared as an independent module, so that it can be constructed with a system configuration utilizing an existing terminal emulator. Also, since the document auto-generation function unit 106 is assumed to operate in the client PC 103, the generated operation document can be easily maintained by an existing application AP (word processor software, spreadsheet software, etc.). Can do.

  The client PC (client computer with automatic document generation function) 103 according to the present invention mechanically standardizes operations from a terminal emulator for system change work and business operation work in large-scale system development work and enhancement work. Therefore, it is possible to contribute to the use for improving the work efficiency and reducing the work accident occurrence rate.

101 UNIX server computer (server SV)
102 telnet
103 Client computer (client PC)
104 Virtual terminal device (terminal emulator)
105 Operation Log File 106 Document Automatic Generation Function Unit 107 Analysis Processing Unit 108 Editing Processing Unit 109 Output Processing Unit 110 Operation Procedure Manual 111 Check List 112 Shell Script

Claims (2)

A virtual terminal device that performs operations on a Telnet-connected UNIX server computer, an operation log file that is recorded by inputting an operation log when the operation is executed by the virtual terminal device, and the operation log file that is obtained from the operation log file and a document such automatic generation function unit for automatically generating an operation document by editing the results of analysis and output content in the UNIX server computer in response to the execution command and the command for the execution of the operation log,
The virtual terminal device is a terminal emulator, and the operation log includes the same operation in a plurality of environments in cooperation with an application operating on another client computer connected to the UNIX server computer through the Telnet connection. The document automatic generation function , wherein a trail for execution is included, and the document of the operation document includes an operation procedure manual, a check list, and a shell script created using the trail With client computer. The client computer with automatic document generation function according to claim 1 ,
The shell script is transferred to the UNIX server computer when the checklist is digested according to the input of the operation procedure manual to the virtual terminal device by the automatic document generation function unit when applied from the test environment to the production environment. A client computer with an automatic document generation function.

Images