Browse Prior Art Database

Using Business Graphics for Presentation of a Group of Node Status

IP.com Disclosure Number: IPCOM000110700D
Original Publication Date: 1992-Dec-01
Included in the Prior Art Database: 2005-Mar-25
Document File: 1 page(s) / 61K

Publishing Venue

IBM

Related People

Chang, DY: AUTHOR [+2]

Abstract

Disclosed is a method to display the status of a massive-node server by displaying the high-level node status of each node in business graphics.

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

Using Business Graphics for Presentation of a Group of Node Status

      Disclosed is a method to display the status of a massive-node
server by displaying the high-level node status of each node in
business graphics.

      A massive-node server is a server that is built with a massive
number of inter-connected computers.  A user task on a massive-node
server is decomposed and distributed to the computers in the
massive-node server.  Each work unit of the user task is
simultaneously executed on the computers of the massive-node server.
The massive-node status monitor should allow the administrator to
monitor as many nodes as possible.

      The group node status window can be displayed in a business
graphics bar chart.  Each bar in the business graphics bar chart
represents an individual node.  The height of each bar indicates the
attribute status of each node.  The attributes of each node can be
memory status, CPU utilization, connectivity status, DASD status, and
workload status, etc.  When a bar is picked up with a double mouse
click, the detailed status attribute of the node that is represented
by the bar is displayed in a separated window.

      There are four functions for each business graphics: attribute,
color, subgroup, and format.  When the attribute function is
selected, the attribute menu is displayed in a separated pulldown
window.  Memory status, CPU utilization, connectivity status, DASD
status, and workload status are good example...