Browse Prior Art Database

Diagnosing Multiple Path Data Processing Systems

IP.com Disclosure Number: IPCOM000080252D
Original Publication Date: 1973-Nov-01
Included in the Prior Art Database: 2005-Feb-27
Document File: 2 page(s) / 43K

Publishing Venue

IBM

Related People

Keffeler, JR: AUTHOR

Abstract

To locate interface or connection cards that are in error, a diagnostic procedure operates with a first device or controller until an error is detected based upon a given operation. If that error is logged, the same operation, i.e., the error-causing operation, is repeated for all connected devices via all paths and logging the error or no-error condition for each. Then, the error logging is analyzed for pointing to an interface unit or cable in error.

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 71% of the total text.

Page 1 of 2

Diagnosing Multiple Path Data Processing Systems

To locate interface or connection cards that are in error, a diagnostic procedure operates with a first device or controller until an error is detected based upon a given operation. If that error is logged, the same operation, i.e., the error-causing operation, is repeated for all connected devices via all paths and logging the error or no-error condition for each. Then, the error logging is analyzed for pointing to an interface unit or cable in error.

In the drawing, a diagnostic program is executed in the program processor or program control unit, which has five interface circuit cards for connecting to a plurality of controllers or devices. As shown, the devices are connected to the program processor via three controllers. The diagnostic is run through interface card 1 which connects both to input interface card A of controllers C1 and C2. Controllers C1 and C2 select their outgoing interface cards X and Y which, respectively, connect to devices D1, D2, and D3.

The diagnostic is first run with connection 1AXJ for D1; there is no error. Next, the same diagnostic is run for D2 and D3; D3 has an error. That error is logged. D3 can also be reached via interface card K and interface X of controller C2. The same procedure is run. However, a different error is logged indicating that both outgoing interface card X and incoming interface card J of D3 are in error. The same procedure is followed for all of the others. The...