Browse Prior Art Database

Accounting Management Model: Error Recovery and Data Management

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

Publishing Venue

IBM

Related People

Chao, C: AUTHOR [+6]

Abstract

Disclosed is a mechanism for coordinating the behavior of an accounting manager and an accounting agent to insure that accounting data is not lost. Data can be lost for a variety of reasons:

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

Accounting Management Model:  Error Recovery and Data Management

      Disclosed is a mechanism for coordinating the behavior of an
accounting manager and an accounting agent to insure that accounting
data is not lost.  Data can be lost for a variety of reasons:

o   It is lost in transit from the agent to the manager and the agent
    has not kept a copy.

o   Too much data accumulates at the agent until its capacity for
    storing the data is exceeded.

o   Too much data arrives at the manager too quickly until it falls
    behind in its processing and loses data.

Disclosed is a method which guards against all of these
possibilities.

      To guard against loss of data in transit, the agent keeps a
copy of all accounting data that it has sent to a manager until it
receives an acknowledgment from that manager that the data has been
received and saved.  The acknowledgment mechanism takes advantage of
the in-order delivery guaranteed by the underlying transport so that
a manager need only provide an explicit acknowledgment for the data
it has received most recently.  When such an acknowledgement is
received, the agent knows that it is free to delete not only that
data, but also all data that it has previously sent to the manager
sending the acknowledgment.

      To guard against a manager's being overrun with accounting data
and against undetected losses of accounting data in transit, all
accounting records must be "pulled" by the manager via the
provideAccountingData command.  An agent captures and stores
accounting data throughout the lifetime of the resources whose usage
is being accounted for but only sends data to a manager in response
to a provideAccountingData command.  The agent does, however, have
the capability to request a provideAccountingData command from a
manager for any of several reasons:

o   The agent's buffer for storing accounting data is approaching its
    capacity or has actually reached it.  The threshold level at
    which the "approaching capacity" report is sent to the manager is
    settable by the manager, e.g., "Notify me when your accounting
    record buffer is 75% full."

o   The agent's buffer has a certain number of records in it.  This
    threshold is also settable by the manager, e.g., "Notify me when
    you have 100 records in your accounting record buffer."

o   The agent experiences an internal error in its process of
    collecting accounting data.

      When it receives one of these notifications, a manager knows
that it must request accounting data from the agent soon, to prevent
loss of data.  Note that by setting thresholds for requesting
retrieval of accounting data, the manager puts into effect policies...