JPH05274190A - Work station operating information analyzing system - Google Patents

Abstract

PURPOSE:To analyze the operating status of a work station without applying a load on an operating system by providing an operating status report output part and an operation experience data recording part. CONSTITUTION:The operation experience data recording part writes the program name of a program recorded on the record of backup memory and executed last time and the execution start date of the program on the relevant area of an account file 51. Furthermore the present date is written on the area of the account file 51 as the completion time of the program by executing the program. In such a way, information representing what software is used in the work station in what time band is recorded on the account file 51. The operating status of the program outputted to the account file 51 is edited and outputted from an edit part 52 as an operating status report 53 by the operating status report output part (a).

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to operating status analysis in workstation operation management, and more particularly to workstation operating status analysis software which plays a role of an outer operating system.

[0002]

2. Description of the Related Art Conventionally, in a small computer such as a workstation, the function of recording how it is used like a general-purpose computer has an excessive burden on the operating system. It was not provided because of the overhead.

Therefore, in order to investigate the actual situation of use of the workstation, it is necessary to perform a human work (1) record the type of use program and use start time and end time.

(2) Aggregation and analysis report creation based on the recorded information.

The processing of must be performed.

[0006]

According to the conventional method of investigating the operating status of a workstation, each time the workstation is used, the program used by the user from what time to what time is recorded, and it is manually recorded. (1) A lot of man-hours for operation analysis work are required because total analysis is required.

(2) Since the operation information is collected by the questionnaire method, the data is inaccurate.

There is a problem that

[0009]

A workstation operation information analysis system according to the present invention comprises an operation record data recording section for recording information on the operation status of various software used on a workstation in an account file, and a previous term account. An operation status report output unit that outputs a report related to the operation status based on the information recorded in the file, and the operation result data recording unit is such that the execution status in the backup memory at the start is that the program was previously executed. , The program name and execution start date and time of the previous program recorded in the backup memory and the current date and time as the end time of the previous program are recorded in the account file, and the execution status is not loaded by the program. Changed to indicate that An account file writing processing unit, a date and time when a program is instructed and a program name are recorded in the back memory, and the execution status is changed to indicate that the program has been executed when the loading of the program is completed. It is characterized by having an execution program loading unit.

[0010]

DESCRIPTION OF THE PREFERRED EMBODIMENTS Next, the present invention will be described with reference to the drawings.

FIG. 1 is a diagram showing an outline of processing according to an embodiment of the present invention. FIG. 1 shows the overall flow of this embodiment and memory state transitions corresponding thereto. Next, the outline of this embodiment will be described with reference to FIG.

Step 11: Write the name of the previously executed program and the start and end times in the account file. At this time, the system of this embodiment is loaded on the memory. The account file is a file in which the operating conditions of the program are written and has the format shown in FIG.

Step 12: Next, the menu screen is displayed and the operator's input is awaited. At this time, this system is loaded in the memory.

Step 13: When the operator instructs the loading of the program, the name of the program and the time (start time) at which the loading is instructed are written on the backup memory. By this time, this system is loaded in the memory.

Since the backup memory of the workstation (WS) is a memory to which power is supplied from the battery built in the WS, the contents can be retained even when the power of the WS is turned off. .. The area of the backup memory that can be used as a shared area between jobs and that can be used by the user program is 256 bytes. FIG. 7 shows the record layout of the backup memory in this embodiment.

Step 14: Execution of the program instructed by the operator. At this time, the program instructed by the operator is loaded on the memory. When the program ends, the process returns to the beginning.

In this embodiment, in a workstation, an operation record data recording section for recording information on a file such as what software was used in the workstation and in what time zone, and an operation status based on the recorded information. An operation status report output unit that outputs a report is provided.

2 to 4 are processing flow charts showing the processing contents of the operation result data recording section of the present embodiment. When using this embodiment, the system of this embodiment must be set on the workstation as an initial task (software that first executes the function of the OS when the system starts up).

Next, the processing contents of the operation result data recording section will be described. The operation result data recording section is composed of an account file writing processing section shown in FIG. 2, a menu display processing section shown in FIG. 3, and an execution program loading section shown in FIG.

The account file write processing unit will be described with reference to FIG.

Step 21: In order to determine whether or not the program was actually executed by the operator when the system was loaded last time, the record written in the backup memory when the system was loaded last time is read.

Step 22: The execution status in the record read from the backup memory is judged, and if it indicates that the program was executed last time, after executing the processing of Steps 23 and 24, as shown in FIG. Proceed to the menu display section shown. If the execution status indicates that the program was not executed last time, the process directly goes to the menu display processing unit.

Step 23: Write the program name of the previously executed program recorded in the record of the backup memory and the execution start date and time of the program to the corresponding area on the account file. Further, as the end time of the executed program, the current date and time is received from the timer of the arc station and written in the corresponding area in the account file.

Step 24: If the information about the previously executed program is written in the account file,
The execution status in the backup memory is returned to the status indicating that the program was not actually loaded the last time this system was loaded.

When the count file write processing section is completed, the menu display processing section of FIG. 3 is executed.

Step 31: Input one record from the menu file created in advance.

Step 32: The number of read records is counted every time one record is read.

Step 33: If the read record is completed, the process proceeds to step 34, where the menu screen is displayed. Otherwise, the process proceeds to step 35.

Step 34: A menu screen is displayed based on the records stored in the table.

Step 35: Store the read record in the table.

When the menu is displayed by the processing of the menu display processing section, the process proceeds to the execution program loading section of FIG.

Step 41: The menu screen is currently displayed and is waiting for an input from the operator.

Step 42: If the input is made by the operator, the consistency of the input data is checked. If the input data does not match the menu number (1 ≤
If the input data is less than the number of records read from the menu) and there is no load module name that matches the input data, an error is displayed and the operator waits for re-input. If the input from the operator is valid, the process proceeds to step 43.

Step 43: If the input request from the operator is to load the submenu, the process returns to the menu reading process to read the next menu. Otherwise, go to step 44.

Step 44: The date and time when the execution of the program is instructed by the operator is read from the timer of the workstation (the start date and time of the program), and the name of the loaded program is output to the corresponding area of the backup memory.

Step 45: The program requested by the operator is activated by program check-in.
After loading the program, change the execution status in the backup memory to the status indicating that the program was actually executed the last time this system was loaded. When the execution of the program is terminated by the operator, the function of the program chain reloads the system and returns to the beginning of the system.

The program called a program chain is terminated and the designated program is activated. After the execution of the started program is completed, the called program is started.

Next, the processing contents of the operation status report output unit will be described with reference to FIG.

The operation status of the program output to the account file 51 by the operation record data recording unit is used as a report output program, or spreadsheet software or graph creation software generally provided as OA software (when using OA software, , Account file layout conforms to the standard of the software used.) Editor 5
2, the operation status report 53 can be edited and output. As the operation status report 53, there are, for example, a time-series output report 53-1, a report 53-2 aggregated for each program, or a report 53-3 for graphing account information.

[0040]

As described above, according to the present invention, in a small-scale computer system called a workstation, the operating status of the workstation can be analyzed without imposing a burden on the operating system. Therefore, it is possible to automatically collect the operation data and output the operation analysis report by this system without manually recording the type of the use program and its use time. This has an effect that the operating status of the workstation can be easily known only by performing a simple fixed work.

[Brief description of drawings]

FIG. 1 is a diagram showing a flow of processing outline of one embodiment of the present invention and memory state transitions corresponding thereto.

FIG. 2 is a flow chart of an account file write processing unit in the operation result data recording unit of the embodiment shown in FIG.

FIG. 3 is a flow chart of a menu display processing unit in the operation result data recording unit of the embodiment shown in FIG.

FIG. 4 is a flowchart of an execution program loading unit in the operation result data recording unit of the embodiment shown in FIG.

5 is a flowchart showing processing contents of an operation status report output unit of the embodiment shown in FIG.

FIG. 6 is a diagram showing a format of an account file used in the embodiment shown in FIG.

FIG. 7 is a diagram showing a record layout of a backup memory used in the embodiment shown in FIG.

Claims (1)

[Claims] 1. An operation result data recording section for recording the operation status information of various software used on the workstation in an account file, and a report on the operation status based on the information recorded in the previous term account file. And an operation status report output unit, wherein the operation result data recording unit records the previous program recorded in the backup memory if the execution status in the backup memory at the start indicates that the program was executed last time. A program name and execution start date and time, and the current date and time as the end time of the previous program, are recorded in the account file, and the execution status is changed so as to indicate that the program was not loaded, and , The execution of the program is instructed A workstation operation characterized by having an execution program loading unit for recording the date and time of the program and the program name in the back memory and changing the execution status to indicate that the program has been executed when the loading of the program is completed. Information analysis system.