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

Model and Architecture for Diagnostic Requests in a Heterogeneous Distributed Environment

IP.com Disclosure Number: IPCOM000122033D
Original Publication Date: 1991-Oct-01
Included in the Prior Art Database: 2005-Apr-04
Document File: 5 page(s) / 205K

Publishing Venue

IBM

Related People

Gaitonde, S: AUTHOR [+9]

Abstract

An architecture and process are disclosed that enables problem determination procedures to be performed on resource managers or other cooperating software facilities when those facilities are distributed across heterogeneous operating environments. It allows service personnel to enter diagnostic requests in one of the environments that will result in predictable diagnostic data being generated in any/all of the associated environments.

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

Model and Architecture for Diagnostic Requests in a Heterogeneous
Distributed Environment

      An architecture and process are disclosed that enables
problem determination procedures to be performed on resource managers
or other cooperating software facilities when those facilities are
distributed across heterogeneous operating environments.  It allows
service personnel to enter diagnostic requests in one of the
environments that will result in predictable diagnostic data being
generated in any/all of the associated environments.

      A common way for resource managers to extend their function is
to become distributed.  A normal implementation of this distribution
is to split the function provided into a user or application
interface function and a resource management function.  By separating
these two functions and adding a communication layer, a distributed
resource manager can be achieved.  The first function is often
referred to as a requester and the second as a server.  In its
simplest form, these server/requester products are implemented on the
same operating environments and are produced as a single product.  In
more complicated forms, the server and requester products are
different, the operating environments are different, a requester may
be using more than one server at any time, and servers may become
requesters (to other servers) in order to process a given request
(this form is illustrated to some extent in Fig. 1).

      The problem determination procedures that are used to service
actual/potential/perceived problems in implementations of resource
managers become more complex when the resource managers become
distributed.  It becomes still more complex when the distributed
environments are composed of a heterogeneous set of products and/or
operating environments.  This is compounded by the large number of
different interfaces (application and end user) for initiating and
terminating diagnostic services in a heterogeneous network of
distributed resource managers.  In the simplest of the complex cases,
there is usually a different interface to do problem determination in
the resource manager, communications facilities, and the operating
environment.  Quite often, the source of the problem (failing
product) is not known before the diagnostic service is invoked.  In
many cases, the diagnostic service may be requested to simply
determine the failing product. To further complicate the process,
different products and operating environments provide different
levels of support for essentially the same diagnostic service.

      Fig. 2 contains a simplified view of the flow of requests,
replies, and diagnostic data in the environment supported by the
disclosed model and architecture.

      The important elements illustrated in Fig. 2 are as follows:
     1.   Information is sent by each request participant to some
central control point when diagnostic data is generated as a result
of a diagnosti...