Browse Prior Art Database

Trace Point Subset Control

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

Publishing Venue

IBM

Related People

Heimsoth, DD: AUTHOR

Abstract

The OS/2* operating system allow system traces to be enabled and disabled on a Trace Major Code basis, with the major codes assigned by type of system function. In the case of the LAN Transport function, one major code point for all of this function does not provide any granularity for selecting a subset of trace points to enable at any one time. This is necessary for effective use of traces in the LAN environment since the high rate of activity in the LAN Transport will quickly cause the system trace buffer to wrap, making it difficult or impossible to capture usable trace data if all trace points are active at once.

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

Trace Point Subset Control

      The OS/2* operating system allow system traces to be
enabled and disabled on a Trace Major Code basis, with the major
codes assigned by type of system function.  In the case of the LAN
Transport function, one major code point for all of this function
does not provide any granularity for selecting a subset of trace
points to enable at any one time.  This is necessary for effective
use of traces in the LAN environment since the high rate of activity
in the LAN Transport will quickly cause the system trace buffer to
wrap, making it difficult or impossible to capture usable trace data
if all trace points are active at once.

      In the previous LAN Transport design, the subset of trace
points enabled for the 802.2 interface was controlled by a parameter
on the CONFIG.SYS file command line for the 802.2 device driver. This
parameter was read by the device driver at installation, and remained
at the value set until the system was restarted.  The parameter was
allowed to have 5 possible values, 0 through 4, each defining a fixed
content subset of available trace points, with 4 being all possible
trace points and 0 being none.  The value was the same for all
adapters controlled by that device driver, so that all adapters of
the same type, such as token ring, pcnet, etc., would all have to run
with the same trace point subset.

      In the new LAN Transport design, 802.2 interface trace points
are grouped into 9 subsets.  Each sub...