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

Table-Driven Error Logging

IP.com Disclosure Number: IPCOM000099389D
Original Publication Date: 1990-Jan-01
Included in the Prior Art Database: 2005-Mar-14
Document File: 2 page(s) / 52K

Publishing Venue

IBM

Related People

Lipps, DR: AUTHOR

Abstract

Described is a mechanism which creates the ability to save error codes accurately even though storage to save them is not available. This is accomplished by using a single bit for each individual system reference code (SRC) which compacts 32 bits into 1 for each of 64 possible errors. This ensures that the data put in the log is not lost due to a defective RAM.

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

Table-Driven Error Logging

       Described is a mechanism which creates the ability to save
error codes accurately even though storage to save them is not
available.  This is accomplished by using a single bit for each
individual system reference code (SRC) which compacts 32 bits into 1
for each of 64 possible errors. This ensures that the data put in the
log is not lost due to a defective RAM.

      A table of possible valid errors was built and SRC to be logged
passed to a logging routine as a parameter.  The table was searched
for a match, and if one was found, a corresponding bit in an error
log was set.  If the SRC was not found, diagnostics would terminate
and display the SRC, since it should have been valid.

      At the end of the diagnostic routines, a final call was made to
the error logging routine to dump the log to memory in SRC format.
The routine would examine bits in the separate RAM and dump
corresponding SRC into the error log in memory.

      Since the same table was used to create and dump information,
the possibility of inaccurate information was minimized.  Also, both
data storage areas are completely tested before use by this error
logging mechanism, so the data has a high degree of integrity when
the log is built at the end of the tests.
    Following is a list of the features:
    -  Trades RAM storage for ROS storage to save on RAM use when it
is not available until later; Since RAM to build the error log is not
avai...