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

Orphan Sieve Handler

IP.com Disclosure Number: IPCOM000113453D
Original Publication Date: 1994-Aug-01
Included in the Prior Art Database: 2005-Mar-27
Document File: 2 page(s) / 48K

Publishing Venue

IBM

Related People

Baier, KJ: AUTHOR [+2]

Abstract

This invention provides a way to remove event sieves that were registered on a remote workstation in the event that the connection to the remote workstation is lost due to power outage or other problems and an attempt to remove the sieve occurs while the connection is lost. i.e. An orphan sieve is created if a remote machine is powered off during or before sieve deregistration. The sieve cannot be removed until the remote machine is powered up and the deregister command is issued from the local machine.

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

Orphan Sieve Handler

      This invention provides a way to remove event sieves that were
registered on a remote workstation in the event that the connection
to the remote workstation is lost due to power outage or other
problems and an attempt to remove the sieve occurs while the
connection is lost.  i.e. An orphan sieve is created if a remote
machine is powered off during or before sieve deregistration.  The
sieve cannot be removed until the remote machine is powered up and
the deregister command is issued from the local machine.

Orphan Sieve Handler Design:

1.  If a sieve cannot be deregistered, the entire sieve, including
    the sieveid, is left in a configuration file (config.run).  Sieve
    dergistration failure is detected by the receipt of a bad return
    code from the dergistration software after issuing the deregister
    command.

2.  Sieves that can be deregisterd are left in config.run, and the
    sieve IDs are left  with the sieve.  The sieve IDs are removed if
    the deregistration is successful to denote that the sieve has
    been removed.

3.    If no configuration file is specified at startup, config.run
    will be used to reconfigure the network.  In this case no attempt
    will be made to deregister the previously noted sieves because
    the user will have ready access to all sieves registered by the
    application.  The sieves that were not removed previously are not
    registered.

4.  If the...