Browse Prior Art Database

Remote Error Monitoring

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

Publishing Venue

IBM

Related People

Eijan, UG: AUTHOR [+3]

Abstract

This article describes a method for use in a data communication system by which a product engineer may monitor errors as they occur from a remote location.

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

Remote Error Monitoring

       This article describes a method for use in a data
communication system by which a product engineer may monitor errors
as they occur from a remote location.

      When a problem develops in the field, a product engineer must
first attempt to recreate the problem in the laboratory.  In many
cases this is an impossibility and the product engineer must travel
to the user site to witness the errors taking place.

      Presented herein is a method by which the product engineer may
monitor errors as they occur from a remote location.  New data
communications systems consist of attachment cards connected to
controller cards.  These controller cards have a service port by
which a modem or terminal may be attached.  This port can link a
product engineer at a remote location to the controller/attachment
cards at the user site.  It is this link that makes remote error
reporting possible.  Fig. 1 shows the controller with service port
and communications attachment in block diagram.

      There are two basic modes of error reporting, real time and
error logging.  In real-time error transmission mode, an error is
reported through the service port when an error actually occurs.  In
error logging mode, the error log is activated and is kept active
over a period of time.  The error log is a record of how many times
each error occurred during this period.  The error log is then
transmitted through the service port when requested. ...