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

Monitoring System for Reliability, Accessability, and Serviceability

IP.com Disclosure Number: IPCOM000113646D
Original Publication Date: 1994-Sep-01
Included in the Prior Art Database: 2005-Mar-27
Document File: 2 page(s) / 76K

Publishing Venue

IBM

Related People

Anderson, BJ: AUTHOR [+3]

Abstract

Disclosed is a procedure by which applications in an Operating System/2* (OS/2) environment can monitor the operation of the First Failure Support Technology* (FFST) facility. This procedure is known as the Monitoring System for Reliability, Availability, and Serviceability Procedure (MSRASP).

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

Monitoring System for Reliability, Accessability, and Serviceability

      Disclosed is a procedure by which applications in an Operating
System/2* (OS/2) environment can monitor the operation of the First
Failure Support Technology* (FFST) facility.  This procedure is known
as the Monitoring System for Reliability, Availability, and
Serviceability Procedure (MSRASP).

      FFST is a software problem management package that provides a
series of software problem management functions.  When an application
determines that something is wrong in its operating environment, FFST
can be called to perform diagnostic-related functions such as problem
data capture, error logging, message services, and network
notification.  In order to automate the recovery of software
problems, customers have asked that an interface be provided by which
user-specified applications can be notified when FFST is called by an
application to handle a problem.

      To perform this function, MSRASP utilizes a series of pipes
through a registration mechanism that requires no registration list.
Through an API provided by a separate FFST process known as the FFST
Registration Manager (FRM), an application can inform FFST that it
wants to be notified each time FFST is called and a specific
diagnostic output (e.g., message, error log) is generated.  (The
application calling FFST for diagnostic data collection specifies
which outputs are to be generated and FFST responds by performing the
diagnostic functions requested.)  When the FRM receives the
registration request, it creates an instance of a named pipe for that
request, using a fixed name with a two character sequence number
naming convention, and returns the pipe handle to the caller.  It
stores the name of the pipe created last in the Pipe List Table (PLT)
in order to determine the name of the next pipe to be created.
Control is then returned to the caller along with...