Browse Prior Art Database

ENABLED HOOKS RECORD FOR BETTER TRACE PROCESSING USER INTERFACE

IP.com Disclosure Number: IPCOM000013643D
Original Publication Date: 2000-Mar-01
Included in the Prior Art Database: 2003-Jun-18
Document File: 1 page(s) / 34K

Publishing Venue

IBM

Abstract

ENABLED HOOKS RECORD FOR BETTER TRACE PROCESSING USER INTERFACE When a user issues commands to identify which hooks are being traced, the information is currently displayed back to the user at the screen session. However, when the trace is actually postprocesed, the information as to which trace hooks were actually enabled is lost. This has the deficiency of not being able to determine whether a particular path has been executed or whether a user error has occurred. A user error can simply be to not turn on the correct hooks. This can be caused by a clerical error. The fix to this problem is to put out a trace record which indicates which hooks are enabled whenever there is a change to the enablement. Also, for the convenience of the postprocessing routines a summary of all trace hooks that have been enabled during the run can be put in the trace header.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 100% of the total text.

Page 1 of 1

ENABLED HOOKS RECORD FOR BETTER TRACE PROCESSING USER

INTERFACE

When a user issues commands to identify which hooks are being traced, the information is currently displayed back to the user at the screen session. However, when the trace is actually postprocesed, the information as to which trace hooks were actually enabled is lost. This has the deficiency of not being able to determine whether a particular path has been executed or whether a user error has occurred. A user error can simply be to not turn on the correct hooks. This can be caused by a clerical error.

The fix to this problem is to put out a trace record which indicates which hooks are enabled whenever there is a change to the enablement. Also, for the convenience of the postprocessing routines a summary of all trace hooks that have been enabled during the run can be put in the trace header.

The trace postprocessing routine can either look in the header or scan the trace file to determine which trace hooks have been enabled and either stop the processing with a definitive error if a required hook is missing or put out warning information if a recommended hook is not enabled. A typical recommended hook is the thread switch indicator.

Providing the information in with the raw data allows the postprocessing routines to identify user errors, which in turn prevents the end user from receiving misleading or incorrect data.

1