Browse Prior Art Database

LAN NetView Fix Trace Enablement

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

Publishing Venue

IBM

Related People

Anderson, BJ: AUTHOR [+3]

Abstract

Disclosed is a trace facility that could be used by the LAN NetView Fix* product. The implementation uses a command, FXTRACE, to provide the user with the capability of controlling the trace operations. It also uses FFST/2(*), First Failure Support Technology/2, for its dumping and dump formatting capabilities.

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

LAN NetView Fix Trace Enablement

      Disclosed is a trace facility that could be used by the LAN
NetView Fix* product.  The implementation uses a command, FXTRACE, to
provide the user with the capability of controlling the trace
operations.  It also uses FFST/2(*), First Failure Support
Technology/2, for its dumping and dump formatting capabilities.

      The FXTRACE command provides a means of starting and stopping
the tracing.  This command also provides different levels of tracing.
This includes:

o   tracing the Event Correlation/Problem Determination engine (the
    knowledge base portion of the Fix product),

o   tracing the data passed between the different Fix product
    internal interfaces,

o   tracing of notifications that are received and sent by the Fix
    product, and

o   tracing of sieve registration activity.

The command allows all of these trace levels, in any combination, to
be started or stopped.

      Once a trace command has been issued, a set of trace flags is
turned on or off depending on the specified trace levels.  The
disposition of the different trace flags is checked by the components
of the Fix product.  If a trace flag is turned on, it tells the Fix
components to gather and log trace data for the corresponding trace
level.  If a trace flag is turned off, it tells the Fix components
not to gather or log any trace data for the corresponding trace
level.

The Fix components perform the actual tracing by providing trace
probe points at the appropriate locations.

      The following is an example of a trace point Application
Programming Interface (API) that interfaces with FFST/2 to enable the
trace data to be logged.

   /*--------------------------------------------------------------*/

   /* The function prototype                                       */

   /*--------------------------------------------------------------*/

     void APIENTRY FXTRACE

           (USHORT         sid, ...