JPH0476638A - Job execution history acquisition system - Google Patents

Abstract

PURPOSE:To prevent the execution of a job from being interrupted by sampling job execution history information characteristic to a user and editing and outputting the information at need. CONSTITUTION:The control record of a monitor file is read in first. Then the file number and address of a record to be outputted next are determined according to the contents of the control record. Then a monitor record is edited. The monitor record is outputted to the monitor file. The control record is corrected and updated.

Description

DETAILED DESCRIPTION OF THE INVENTION [Field of Industrial Application] The present invention relates to a job execution history acquisition method in general job operation (particularly online job operation) of a computer system.

[Conventional technology]

Previously, the information that could be collected when acquiring job execution history was only information seen from the computer system (OS-level information such as the execution program ID and the type of file accessed by the program), and information from the user's perspective. (Who used which menu and how many times, who updated which item in which file, etc.) could not be collected. Additionally, there were problems such as program execution being interrupted if the file storing monitoring information overflowed.

[Problem to be solved by the invention]

To collect user-specific job execution history information and to be able to edit and output that information as necessary. Also,
Prevent job execution interruption due to file overflow.

[Means to solve the problem]

The job execution history acquisition method of the present invention uses a plurality of files prepared in advance to store job execution histories, and a user-specific job that is externally called from a user program and cyclically used in the files. and means for writing out the execution history.

〔Example〕

Embodiments of the present invention will be described below with reference to the drawings.

FIGS. 1 to 3 illustrate a case where an online program is operated in accordance with an embodiment of the present invention. In FIG. 1, in preparation for operation, a plurality of processing history output files (hereinafter referred to as monitor files) are set in a standard drawing format. In the following embodiment of the present invention, it is assumed that two are set.

Use monitor files cyclically to prevent job execution from being interrupted due to overflow.

Further, in order to control cyclic usage, a monitor control section 21 is set at address 1 of the monitor file 1 as shown in FIG. Note that N indicates the maximum number of records in one file.

This monitor control unit has the structure shown in Fig. 3, and the file number 32 is the file number currently being output, and the maximum address 33 is the file number 32. This is the address of the last record output to the file indicated by . In order to accumulate processing history in the online program, the following processing is programmed to run for each transaction.

(1) Read the control record of the monitor file.

2) Determine the file number and address of the next record to be output from the contents of the control record. The ifusada method is as follows.

■Maximum address of address control record 10 1-〉New address ■File number new address > File MAX address When file number 1 of control record, file number 2 When file number 2 of control record, file number 1 New address =or. When using the file MAX address, use the file number of the control record as is (3) Edit the monitor record.

The output contents of the monitor file are as follows.

Ru.

do.

When: Processing date and time Who: User ID Where: Terminal ID What: Processing file name What to do: Processing method, record contents before and after update Monitor Output records to monitor file Control as follows: File number where the record was modified and the updated record was output - 1> Address where the file number record was output - 1> Maximum address FIG. 4 shows a specific example of the contents of the monitor record. The output contents of the monitor records 41 and 42 indicate the processing date, processing time, user name, terminal name, processing identification, and pre-update record contents or registered record contents. In addition, in the processing identification “M
DB'' indicates before update, and ``ST'' indicates registration, and the contents of each record are set.

〔Effect of the invention〕

As explained above, the present invention enables the user to collect user-specific information by writing necessary job execution history information from the user program to a file, and, if necessary, uses the collected information as input to obtain the contents. You can edit and output. Furthermore, by preparing multiple files to be written and using them cyclically, interruptions in job execution can be prevented.

[Brief explanation of drawings]

Figure 1 is a diagram showing the cyclic use of a monitor file, Figure 2 is a diagram showing the role of the monitor control unit in the monitor file, Figure 3 is a configuration diagram showing the items of the monitor control unit, and Figure 4 1 is a diagram illustrating a specific example of the contents of a monitor record. 1.2...Monitor file, 21...Monitor control unit, 31...*CTRL, 32...File number, 3
3...Maximum address, 34...F I LLER1
41, 42...Monitor record.

Claims (1)

[Claims] A plurality of files prepared in advance to store job execution history, a means for externally calling from a user program and writing a user-specific job execution history while cyclically using the file, and a means for writing a user-specific job execution history to the file. A job execution history acquisition method comprising means for inputting written job execution history information and editing and outputting job execution status as necessary.