Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Graphical User Interface Design of the Trigger Panel in Local Area Network Server Specialist

IP.com Disclosure Number: IPCOM000115092D
Original Publication Date: 1995-Mar-01
Included in the Prior Art Database: 2005-Mar-30
Document File: 2 page(s) / 72K

Publishing Venue

IBM

Related People

Huang, G: AUTHOR [+4]

Abstract

This disclosure addresses the Graphical User Interface (GUI) design of the trigger relationship panel of the Knowledge Base Editor for the Local Area Network (LAN) Server Specialist (LSS) system. The LAN Server Specialist system is a problem determination tool for IBM* LAN Server 3.0 and 4.0*. It analyzes and correlates the error messages issued by LAN Servers and LAN Requesters in real-time, and reports possible causes and recommended actions.

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

Graphical User Interface Design of the Trigger Panel in Local Area
Network Server Specialist

      This disclosure addresses the Graphical User Interface (GUI)
design of the trigger relationship panel of the Knowledge Base Editor
for the Local Area Network (LAN) Server Specialist (LSS) system.  The
LAN Server Specialist system is a problem determination tool for IBM*
LAN Server 3.0 and 4.0*.  It analyzes and correlates the error
messages issued by LAN Servers and LAN Requesters in real-time, and
reports possible causes and recommended actions.

      The Knowledge Base Editor is a part of LSS, which provides a
way for users to edit messages, causes, actions and the relationship
between them.  The knowledge entered by the users is used by the
inference engine for the real-time problem determination.

      One panel is needed to edit the trigger relationship between
messages.  An error message M1 "triggers" another error message M2 if
the message M1 might cause the message M2 to be generated.  In this
case, message M1 is usually closer to the real problem than message
M2, and M2 is ignored during the problem determination process.  What
needs to be considered in the trigger relationship includes:
  1.  There can be more than one messages triggered by a message;
  2.  There can be more than one messages which triggers a message;
  3.  The relationship of variables between messages needs to be
       specified;
  4.  The condition of the trigger relationship needs to be
specified.

      For a message to be edited, there are two pages in the message
notebook, one for "triggering", one for "triggered", as shown in Fig.
1.
                      TRIGGERING RELATIONSHIP
  Triggering-Message                        Triggered-message-ID-list
  Triggering-message-variables              Ddd/Delete/Undo
  Triggered-message
  Triggered-message-variables      ...