Browse Prior Art Database

Rios Diagnostics Open Architecture

IP.com Disclosure Number: IPCOM000102648D
Original Publication Date: 1990-Dec-01
Included in the Prior Art Database: 2005-Mar-17
Document File: 4 page(s) / 145K

Publishing Venue

IBM

Related People

Benignus, DM: AUTHOR [+2]

Abstract

This disclosure describes an open-architected diagnostic system.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 38% of the total text.

Rios Diagnostics Open Architecture

       This disclosure describes an open-architected diagnostic
system.

      This system is composed of a device-independent command called
the diagnostic controller and several device-dependent programs
called diagnostic applications. There is a unique diagnostic
application for each major area of the system.  For example, SCSI
disks, SCSI disk adapters, async cards, etc.

      The diagnostic system employs two databases.  The system
configuration database is used to determine what devices are present
and the diagnostic database which identifies the devices that can be
diagnosed.

      The diagnostic controller understands the dependencies between
the devices.  The configuration is processed in different ways
depending on the type of analysis which is being performed.  If the
system is being tested, then the configuration is processed from the
inside to the outside. And vice versa, if a single device is being
tested.  Time is a larger consideration in the first case, while in
the second case, effectiveness is more important. The isolation
process is better, when individual parts are diagnosed, because the
status of sibling devices can be included.  In addition, the
culpability of the parent can be inferred, when multiple children
return a bad status but the parent passes its tests.

      Generally, the diagnostic controller traverses the
configuration database, calling diagnostics applications, and
analyzing test results based on the device dependencies inherent in
the configuration.
      The Diagnostic Database contains the following fields:
      DType        The device type which is used as an index into the
configuration database.
      DSClass      The device subclass which is used as an index into
the configuration database.
      Ports        Indicates whether the device or its children
should be represented in the diagnostic selection menu.  For example,
serial ports are represented via attached terminals and printers,
because the user is more familiar with these devices than with an
obscure async port name.
      AttDType     The device type of the child to define, if Ports
is true.
      AttSClass    The subclass of the child to define, if Ports is
true.
      PSet         Identifies the set of messages in the diagnostic
catalog reserved for the device.  An explanation for the diagnosis is
included in the problem report.
 PreTest      Indicates whether the device should be pretested.
Devices are pretested during the configuration process if they are
relied on to complete the power-on process.
      Conc         Indicates if the device is supported in concurrent
mode.
      SupTests     Identifies the type of tests supported by the
Diagnostic Application, such as shared tests, sub-component tests,
full resource tests, missing device analysis, and error log analysis.
 ...