Browse Prior Art Database

Lightweight Trace and Interpreter for Inter-process Timing Problems

IP.com Disclosure Number: IPCOM000108786D
Original Publication Date: 1992-Jun-01
Included in the Prior Art Database: 2005-Mar-22
Document File: 2 page(s) / 75K

Publishing Venue

IBM

Related People

Cheung, KC: AUTHOR [+4]

Abstract

A method is disclosed for doing a lightweight trace and interpreting the data collected by that trace for debugging system problems. The trace information is logged in a cryptic form and then that information is used to collect supporting information for debugging the problem.

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

Lightweight Trace and Interpreter for Inter-process Timing Problems

       A method is disclosed for doing a lightweight trace and
interpreting the data collected by that trace for debugging system
problems.  The trace information is logged in a cryptic form and then
that information is used to collect supporting information for
debugging the problem.

      This lightweight trace mechanism is capable of running in any
system process.  A trace space is dynamically created and assigned to
each system job when it is needed. The creating of the trace space is
triggered by the first attempt to log a trace entry.  The size of the
trace space is automatically set to an optimum size based on the size
of auxiliary storage on the system.  The size of the trace space can
be overridden.  The trace mechanism runs as long as the system is
running.  There is no way for the customer to turn it off (there is a
switch that is intentionally hidden).  The information in the trace
space identifies selected modules that execute on certain paths and
help to roughly identify the path of execution within those selected
modules.

      The full-time lightweight trace mechanism collects information
on a real-time basis.  Whenever the problem occurs, the required
information is always collected.  It eliminates the need to recreate
the problem.

      The impact to the timing characteristics is reduced by
collecting information synchronously in-line within the modules
instead of the current event-driven method.  The timestamps on the
trace information will, therefore, be more accurate as well.  The
...