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

Methodology for Program Invocation upon Detection of a Particular LAN Topology

IP.com Disclosure Number: IPCOM000105049D
Original Publication Date: 1993-Jun-01
Included in the Prior Art Database: 2005-Mar-19
Document File: 2 page(s) / 81K

Publishing Venue

IBM

Related People

Johnson, WJ: AUTHOR [+2]

Abstract

A method is described for allowing a user to configure a predicate for a Local Area Network (LAN) topology condition whereby the condition represented by the predicate determines initiating execution of one or more programs.

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

Methodology for Program Invocation upon Detection of a Particular LAN Topology

      A method is described for allowing a user to configure a
predicate for a Local Area Network (LAN) topology condition whereby
the condition represented by the predicate determines initiating
execution of one or more programs.

      Current programming environments provide tools to identify what
is running on a computer.  Tools such as SHOWMEM and THESEUS provide
a window into the guts of a running system.  A human makes
assessments about the system by evaluating a multiplicity of
processes in conjunction with each other.  Many performance problems
arise in environments where a multiplicity of users and/or processes
are active.  A performance person may only be interested in what
transpires when a significant level of activity occurs.  It would be
a waste of resources to gather data for situations which are not
interesting from a performance standpoint.  A method is needed for
automatic execution of programs when a particular LAN topology is
detected particularly for monitoring performance situations.

      The preferred embodiment method for configuration is an ASCII
profile implementation which is internalized by the system at re-boot
time.  The profile contains user topology constraint predicates which
determine whether or not to execute one or more programs.  The
profile is read by a system at system reboot time (like an OS/2*
CONFIG.SYS) and internalized for subsequent access.  A terminate and
stay resident program, coupled to an appropriate communications
medium for the purpose of detecting the configured topology
predicates, monitors the environment to see who is doing what.  For
example, on a mail server where performance measurement becomes
interesting at around 50 users, this mechanism could be coupled to
the server processes which manage mail requesters.  Upon detection of
50 or more active users within a specified time interval, one or more
programs (e.g., performance measurement programs) can be
automaticall...