Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Testing Error Recovery Procedures

IP.com Disclosure Number: IPCOM000073683D
Original Publication Date: 1971-Jan-01
Included in the Prior Art Database: 2005-Feb-22
Document File: 2 page(s) / 67K

Publishing Venue

IBM

Related People

Perry, LR: AUTHOR [+2]

Abstract

The described program can be used to generate or simulate almost any kind of input/output error. It can generate a specific error in order to test the recovery procedure for that error or it can provide controlled input to error-recording programs. Two techniques are used. First, many errors are physically generated on direct access storage devices by a series of channel programs written for this purpose. These programs can be constructed according to the flow charts seen in A.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 74% of the total text.

Page 1 of 2

Testing Error Recovery Procedures

The described program can be used to generate or simulate almost any kind of input/output error. It can generate a specific error in order to test the recovery procedure for that error or it can provide controlled input to error-recording programs. Two techniques are used. First, many errors are physically generated on direct access storage devices by a series of channel programs written for this purpose. These programs can be constructed according to the flow charts seen in A.

Second, errors that cannot be generated by channel program are simulated by programming. Appendages to the I/O supervisor detect Channel Control Words that have been flagged by programming and set up error information passed by a test program. The test program can be designed by the flow charts seen in B, the main execution steps of which are as follows.

The program determines whether the error being generated or simulated will produce an error message and, if so, notifies the operator by a console message. The program executes a test case channel program such as that in A, which generates or simulates an error. The program then then compares the results with the expected results, and writes out pertinent data for the programmer's use. The abnormal end appendage is entered whenever an I/O error is detected. If the error is one that is physically generated by channel program, the appendage takes no action. If the error is one that is detected because of a f...