Browse Prior Art Database

Complete Internal System Test for an Open-System Environment

IP.com Disclosure Number: IPCOM000040242D
Original Publication Date: 1987-Oct-01
Included in the Prior Art Database: 2005-Feb-02
Document File: 2 page(s) / 41K

Publishing Venue

IBM

Related People

Hamel, ER: AUTHOR [+2]

Abstract

This article describes a compete internal system test for an open- system environment utilizing a bus wrap command from the bus control unit (BCU). The wrap function is the means of taking input data and rerouting it to output data through selected input/output processors (IOPs), input/output adapters (IOAs) or device functional controllers (DFCs). (Image Omitted) Fig. 1 is a block diagram of an open-system concept. In order to test the I/O bus in an open system, a common means is needed to have data returned so that the bus activity and function can be checked. With an IOP wrap function any number (architecture limits to 32) of IOPs can be tested by just wrapping all IOPs in the bus. This would require no devices attached to test the bus.

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

Page 1 of 2

Complete Internal System Test for an Open-System Environment

This article describes a compete internal system test for an open- system environment utilizing a bus wrap command from the bus control unit (BCU). The wrap function is the means of taking input data and rerouting it to output data through selected input/output processors (IOPs), input/output adapters (IOAs) or device functional controllers (DFCs).

(Image Omitted)

Fig. 1 is a block diagram of an open-system concept. In order to test the I/O bus in an open system, a common means is needed to have data returned so that the bus activity and function can be checked. With an IOP wrap function any number (architecture limits to 32) of IOPs can be tested by just wrapping all IOPs in the bus. This would require no devices attached to test the bus. One step further is the same function in that the IOAs or DFCs would test the next extended bus without the need of devices. This eliminates tests written for devices. Only common commands are needed to test all buses for activity and function. By issuing wrap to IOPs or IOAs and then sending random data along the bus, the data that is wrapped will simulate the customer activity well beyond normal operating systems activity. This wrapped function will test the bus to maximum data rate and stress the system to the limit. Fig. 2 is a flow chart of the method utilized to make the complete internal system test. It is possible with this method to wrap only IOPs or IOAs or...