Browse Prior Art Database

Data Processing Product Design With No Internal Cables

IP.com Disclosure Number: IPCOM000102116D
Original Publication Date: 1990-Oct-01
Included in the Prior Art Database: 2005-Mar-17
Document File: 2 page(s) / 51K

Publishing Venue

IBM

Related People

Shield, WH: AUTHOR [+2]

Abstract

Data Processing Product Design (DPPD) with no internal cables is a software interface which enables automated testing of graphics-oriented Service Processor (SP). The variable information input to the screen is captured prior to its conversion to graphics and stored in an area accessible by an external test program which runs on the same machine as the SP.

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

Data Processing Product Design With No Internal Cables

       Data Processing Product Design (DPPD) with no internal
cables is a software interface which enables automated testing of
graphics-oriented Service Processor (SP).  The variable information
input to the screen is captured prior to its conversion to graphics
and stored in an area accessible by an external test program which
runs on the same machine as the SP.

      The SP uses OS/2* Dialog Manager (DM) to present its user
interface screens.  DM screens consists of fixed and variable
information displayed as OS/2 windows (sometimes called panels).  The
fixed information is hard-coded into a tag language definition.  The
variable information is determined dynamically during run-time by the
driving application.  A majority of SP applications funnel
screen-related func tion calls to a display interface module.  This
module has embedded DPPD code which writes variable information to a
separate shared-data area.  Whenever the application code updates the
screen, the shared- data area also updates. Access to this area is
serialized in order to maintain data integrity.

      The figure shows a logical layout.  Blocks on the SP microcode
side illustrate the components native to the SP. The DPPD Interface
side shows where the DPPD hook and external test program logically
belong.  The block labelled DISPLAY INTERFACE and DPPD hook denotes
an SP module which has DPPD code compiled into it.

      Th...