Browse Prior Art Database

Communications Trace Line Monitor

IP.com Disclosure Number: IPCOM000043644D
Original Publication Date: 1984-Sep-01
Included in the Prior Art Database: 2005-Feb-05
Document File: 1 page(s) / 12K

Publishing Venue

IBM

Related People

Carusone, A: AUTHOR [+3]

Abstract

This article describes a technique for storing trace data during a communication session. It has particular value for devices with limited trace storage capability. The technique calls for two memories and the storing of all control commands in one of the memories during the session. The trace is stored in the other memory. This technique enables the trace to be viewed in the context of all control information issued prior to the start of the stored trace data. The steps of the method are as follows: 1. Provide for automatic termination of the trace after a prespecified number of events. (An event is defined as either a Systems Network Architecture (SNA) request or response command.) In this fashion, the trace is stopped to provide specific data for diagnosis of the communications problem.

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

Page 1 of 1

Communications Trace Line Monitor

This article describes a technique for storing trace data during a communication session. It has particular value for devices with limited trace storage capability. The technique calls for two memories and the storing of all control commands in one of the memories during the session. The trace is stored in the other memory. This technique enables the trace to be viewed in the context of all control information issued prior to the start of the stored trace data. The steps of the method are as follows: 1. Provide for automatic termination of the trace after a prespecified number of events. (An event is defined as either a Systems Network Architecture (SNA) request or response command.) In this fashion, the trace is stopped to provide specific data for diagnosis of the communications problem. The number of the last event traced is printed at the top of the trace in case there is a need to trace a different number of events on the following run. 2. Provide a special save area to save the pertinent control information for later diagnosis. This control information is then printed with the trace and is used with the trace to diagnose the problem. A portion of the control information is also in the trace at the point it occurred in the flow so that the trace sequence is intact (providing the buffer did not wrap over the control information). 3. If desired, the control information may be noted by an EBCDIC description so that it is easily...