JPS63129434A - Program development supporting device - Google Patents

Abstract

PURPOSE:To facilitate the diagnosing analysis of the abnormality of a disk when it occurs, by providing a history storage processing part to store the history information of the result of an input/output operation in an input/output history storage area in a disk driver task in an OS. CONSTITUTION:The history storage processing part 13 to output the history information regarding the operation of the disk 5 is provided in the disk driver task 9 in the OS (operating system) 3, and the history information processed at the history storage processing part 13 is stored in the input/output history storage area 11 via a history information transmission means 14. Also, in a disk diagnosing task 10, an output processing part 15 to output-process the history information stored in the input/output history storage area 11 to a CRT 1 is provided, and the history information processed at the output processing part 15 is displayed on the CRT 1 via a history information output means 16. Also, in the OS 3, a mail box 17 to perform communication between the disk diagnosing tank 10 and the disk driver task 9 regarding the address pointer and size information of the input/output history storage area 11, is provided. In such way, it is possible to easily perform the diagnosing analysis of a disk operation.

Description

DETAILED DESCRIPTION OF THE INVENTION [Purpose of the Invention (Field of Industrial Application) The present invention relates to a program development support device that operates on an operating system (hereinafter referred to as OS) having a disk control function.

(Prior Art) In recent years, program development support devices controlled by microcomputers use disks (including floppies and hard disks) as secondary storage devices and have disk control functions. Those incorporating s are popular.

FIG. 2 shows a configuration diagram of a program development support device related to disk control.

This program development support device is CRTI, disk 5
An application task 2 that outputs input/output requests to the O53, a disk controller 4 that inputs commands from this O53, and a disk 5 operated by this disk controller 4. Consists of.

O53 is an application interface section 6. Input/output control section 7. It consists of an input/output request result storage area 8 and a disk driver task 9, which are generated for each input/output request.

The application interface section 6 is.

It accepts input/output requests from the application task 2, transfers control to the input/output control unit 7 as necessary, and returns the results to the application task 2 after processing the input/output requests. It also outputs a message to the CRTI if necessary.

The content of the message output to this CRTI is 1, for example, a notification of completion of input/output operation of the disk 5 or a notification of an operation error.

The input/output control section 7 stores the input/output request sent from the application interface section 6 in a certain format in the input/output request result storage area 8.

Transfer control to disk driver task 9.

The disk driver task 9 interprets the contents of the input/output request stored in the input/output request result storage area 8 and outputs a command to the hardware, that is, the disk controller 4. Disk 5 by disk controller 4
actually operates, and the operation results, that is, the input/output results, are sent to the disk controller 4 and the disk driver task 9.
The data is returned to the input/output request result storage area 8 via the input/output request result storage area 8.

Further, this input/output result is confirmed by the input/output control unit 7 and sent to the application task 2 via the application interface unit 6.

With the above configuration, the input/output control unit 7 checks the data in the input/output request result storage area 8 to check the operation result in response to the input/output request from the application task 2 to the disk 5. Then, if the disk completes the operation normally according to the I/O request,
A message notifying that the input/output request has been successfully completed is displayed on the CRTI via the application interface section 6 in accordance with the contents of the input/output request. On the other hand, when a disk operation ends abnormally, two types of processing are mainly performed. One is the case of an error related to the hard mechanism of the disk device, such as a seek error, in which case an error message is immediately displayed on the CRTI. Others are C when reading.
This is a temporary error caused by noise, such as an RC error, and in this case, if the error still occurs after several attempts, the error message will be returned to CR.
Displayed on TI.

I/O request result storage area 8 checked by the I/O control unit 7
The contents include, for example, disk operating functions, track and sector numbers to be accessed, input/output requirements such as read/write counts, and input/output results such as quality of operation results and error status.

(Problems to be Solved by the Invention) When diagnosing the operation of a disk, the contents of requests to the disk controller, such as the type of operation function, track number, sector number, read/write counter number, etc., and the operation result. Contents: controller status, detailed error status after read/write,
The number of retries etc. becomes important diagnostic analysis information.

However, in conventional program development support devices,
For information on these input/output requests and input/output results, please refer to O
3, an input/output request result storage area 8 is created for each request from the application task 2, and is deleted when the request is completed.

For this reason, when an error occurs with conventional disk diagnostic functions, it is possible to distinguish whether it is an error in the hardware mechanism or an error that can be recovered by retrying.
The problem is that it is impossible to know what kind of request command was issued to the disk controller to cause the error, or what the detailed status information of the controller is in response to that request command. be.

There is also a method of performing disk diagnosis NVr etc. using a special device such as an emulator, but it requires work to connect, the operating procedure must be mastered, and the emulator itself is expensive, and The problem is that microcomputer users cannot easily purchase the product.

SUMMARY OF THE INVENTION Therefore, an object of the present invention is to provide a program development support device that can perform disk diagnosis easily and inexpensively, and can easily perform diagnostic analysis when a disk abnormality occurs.

[Components of the invention (Means for solving problems) Among the application tasks:

An area generation unit that can generate an input/output history storage area of any size for storing history information of input/output requests to disks and input/output operation results, and a history of stored input/output operation results. Enter the information and click
The disk diagnostic task has an output processing unit that performs processing for displaying on a display device, etc., and the disk driver task in O3 stores history information of input/output operation results in an input/output history storage area. (Function) As a result, during disk diagnosis, Historical information regarding disk operations will not be lost, and furthermore, not only information regarding a single request, but also the status of input/output operations over a continuous range can be known through a display device such as a CRT, which reduces the tendency for errors to occur. This makes it possible to easily perform diagnostic analysis regarding disk operation.

(Embodiment) FIG. 1 shows a configuration diagram of a program development support device according to an embodiment of the present invention. The same parts as in FIG. 2 are given the same numbers. The application task 2 includes a disk diagnostic task 10 and an input/output history storage area 11 for storing a history of input/output requests to the disk 5 and detailed status information from the disk controller 4.

This input/output history storage area 11 is generated by the area generation unit 12 within the disk diagnosis task 10.

Further, at this time, the input/output history storage area 11 can be adjusted to an arbitrary size depending on the content of the diagnostic test performed by the disk diagnostic task 10 or depending on the memory capacity of the system.

On the other hand, a history storage processing section 13 for outputting history information regarding the operation of the disk 5 is provided in the disk driver task 9 in the O33, and the history information processed by this history storage processing section 13 is transmitted to a history information transmission means. 14, and stored in the input/output history storage area 11.

Further, within the disk diagnosis task 10, an output processing section 15 for outputting the history information stored in the input/output history storage area 11 to the CRTI is provided, and the history information outputted by this output processing section 15 is provided. The information is displayed on the CRTI via the history information output means 16.

Additionally, a mailbox 17, which is one of the functions of the O5, is provided in the O53 for communicating with the disk diagnostic task 10 and the disk driver task 9 regarding the address pointer and size information of the input/output history storage area 11. ing.

Now, the diagnostic operation of this embodiment configured as described above will be explained.

When the disk diagnosis task 10 is activated, first, the internal area generation unit 12 generates the input/output history storage area 11 with a memory size according to the contents of the disk diagnosis. The disk diagnostic task 1o sends the address pointer of the generated input/output i-history storage area 11 and its memory size to the mailbox 17, and then sends an input/output request regarding the disk, that is, the type of disk operation function and the type of disk operation function to be accessed. An input/output request group created using track numbers, sector numbers, read/write counter numbers, etc. is output to 033. I/O requests related to this disk are
Through the application interface unit 6 in 3,
It is sent to the input/output control section 7. The input/output control unit 7 generates an input/output request result storage area 8, stores the input/output request contents of these input/output request groups, and then executes the disk driver task 9.
The disk driver task 9 refers to the input/output request contents in the input/output request result storage area 8, converts a group of disk-related input/output requests into command instructions, and sends the commands to the disk controller 4. disk controller 4
operates the disk 5 based on the input commands, and sends the successive operation results as status information to the disk driver task 9 again. Disk driver task 9
The history storage processing unit 13 in the disk controller 4 receives the address pointer regarding the input/output history storage area 11 in the application 2 sent by the mailbox 17 and the memory size according to the input/output request group.
Every time the status information after reading/writing is input, the necessary history information is written from the address specified by the address pointer in the input/output history storage area 11. Then, the disk diagnosis task 10 checks the history information regarding the disk operation stored in the input/output history storage area 11, processes the necessary information in the internal output processing section 15, and then sends the disk diagnosis via the history information output means 16. Display the results on CRTI.

As a result, it is possible to understand in detail what kind of status information corresponds to what kind of command when an error occurs, and it is possible to easily perform disk diagnostic analysis.

[Effects of the Invention] As described above, according to the present invention, it is possible to obtain detailed history information when a disk abnormality occurs during disk diagnosis, and to perform diagnostic analysis when a disk abnormality occurs without using a special device such as an emulator. A program development support device that can be easily developed can be obtained.

[Brief explanation of the drawing]

FIG. 1 is a block diagram of a program development support apparatus according to an embodiment of the present invention, and FIG. 2 is a block diagram of a conventional program development support apparatus. 1...CRT, 2...Application task. 3...O3, 4...Disk controller, 5...
- Disk, 6...Application interface unit, 7...I/O control unit, 8...I/O request result storage area, 9...Disk driver task, 10...
- Disk diagnosis task, 11...I/O history storage area. 12... Area generation unit, 13... History storage processing unit,
14...History information transmission means, 15...Output processing unit,
16...History information output means, 17...Mailbox. (7317) Agent: Patent Attorney Noriyuki Chika (
8105) Hirofumi Mitsumata Figure 1

Claims (1)

[Claims] Program development support consisting of a disk controller for controlling disk operations, an operating system with a disk control function that outputs commands to this disk controller and inputs disk status information, and application tasks that operate this operating system. In the device, the application task includes an area generation unit that can generate an input/output history storage area of any size for storing history information of input/output requests and input/output operation results to the disk; A disk diagnostic task is provided which has an output processing section that inputs the history information and performs processing for outputting it to a display device, and the operating system stores the history information in the input/output history storage area. What is claimed is: 1. A program development support device comprising: a disk driver task having a history storage processing section for storing data; and a mailbox for communicating information regarding the input/output history storage area between the two tasks.