Browse Prior Art Database

Monitor Data Preselection

IP.com Disclosure Number: IPCOM000084871D
Original Publication Date: 1976-Jan-01
Included in the Prior Art Database: 2005-Mar-02
Document File: 2 page(s) / 43K

Publishing Venue

IBM

Related People

Garcia, LC: AUTHOR [+3]

Abstract

Computer signals to be monitored by a hardware monitor 10 are provided through a monitor point attachment device 11 which connects the monitor input to a computer bus 9, which may be a storage bus or an I/O bus. The output of device 11 connects the input to a monitor mask 12 which operates with a preselect and format control unit 13, which receives, decodes, and controls the input data in accordance with a condition field and an action field.

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 73% of the total text.

Page 1 of 2

Monitor Data Preselection

Computer signals to be monitored by a hardware monitor 10 are provided through a monitor point attachment device 11 which connects the monitor input to a computer bus 9, which may be a storage bus or an I/O bus. The output of device 11 connects the input to a monitor mask 12 which operates with a preselect and format control unit 13, which receives, decodes, and controls the input data in accordance with a condition field and an action field.

The condition field specifies the conditions which must be met before data capture can take place in the basic monitor recorder 14. Once the condition is met, the action field specifies what type and/or format of the information is recorded in a monitor record by monitor recorder 14.

(Image Omitted)

CONDITION FIELD - The condition field is divided into subfields of two bits each. Thus, in the example, 24 subfields are created, each to assume one of four different values to be matched against its corresponding monitor bus bit.

(Image Omitted)

The (n) monitor bus bits are tested against the values specified in the (n) condition subfields and when they all "match" a record is created The only exception is the "No-op". A No-op will negate the entire condition subfields and only bit (0) is tested for this condition.

When the match condition occurs, the action field is then examined to determine which data will be placed in the monitor record.

If more than one mask match occurs due to subfield "don't care...