Browse Prior Art Database

Program Event Recording

IP.com Disclosure Number: IPCOM000077800D
Original Publication Date: 1972-Sep-01
Included in the Prior Art Database: 2005-Feb-25
Document File: 2 page(s) / 33K

Publishing Venue

IBM

Related People

Sakalay, FE: AUTHOR

Abstract

With the increasing sophistication of operating systems, including timesharing, multiprogramming, and multiprocessing, it is becoming increasingly difficult for a programmer to reconstruct the sequence of events leading to a specific incident in a computer program. For example, it might be desired to examine the last series of instructions or branch addresses prior to a particular program check.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 53% of the total text.

Page 1 of 2

Program Event Recording

With the increasing sophistication of operating systems, including timesharing, multiprogramming, and multiprocessing, it is becoming increasingly difficult for a programmer to reconstruct the sequence of events leading to a specific incident in a computer program. For example, it might be desired to examine the last series of instructions or branch addresses prior to a particular program check.

The present system provides for the capturing of events leading to a given incident in a computer system. These events may be varied in number and information content. The particular incident that triggers the capture of events is selectable. The selection of events to be captured and triggering incidents are under program control. Typical events may be OP code, branch addresses, instruction count, channel address, and typical incidents which trigger the capture of such events may be external check, I/O interrupt, machine check, supervisor call, or program check. There may be other subclasses of events, the capture of which will be triggered by particular events. For example, it might be desired to capture certain OP codes upon the occurrence of a specific OP code.

A schematic representation of the present system is shown in the figure. Events to be placed under surveillance and the particular selected triggering incidents are directed to an input gating control. A unique program control word sets the event control register, thereby allowing one particular class of events to load the event stor...