Browse Prior Art Database

Distributed Computing Environment Time Service Persistent Configuration

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

Publishing Venue

IBM

Related People

Ally, A: AUTHOR [+2]

Abstract

The Open Software Foundation (OSF) Distributed Computing Environment (DCE) Distributed Time Service (DTS) entity must be configured manually after each startup. This disclosure proposes a new option provided at startup to enable the DTS entity to restore its previous configuration. The option allows the DTS entity to restore configuration information that was set during the last instantiation of the DTS entity.

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

Distributed Computing Environment Time Service Persistent Configuration

      The Open Software Foundation (OSF) Distributed Computing
Environment (DCE) Distributed Time Service (DTS) entity must be
configured manually after each startup.  This disclosure proposes a
new option provided at startup to enable the DTS entity to restore
its previous configuration.  The option allows the DTS entity to
restore configuration information that was set during the last
instantiation of the DTS entity.

      Each time one of the following Distributed Time Service Control
Program (DTSCP) commands is processed, the DTS entity keeps a record
of the configuration characteristic affected in a protected file:
  o  Advertise
  o  Create
  o  Enable
  o  Delete
  o  Set
  o  Unadvertise

      The DTS entity then could be restarted using the syntax "DTSD
-r" (for Restore) to restore previously saved configuration without
the need to re_invoke the same DTSCP commands.

      This enhancement allows the DTS entity to save its
configuration and restore it at startup.  This function is
accomplished by introducing a new optional input parameter at the
start of DTS entity, this is:
  -r                   For 'Restore'.

      The restore option can be invoked as follows: "DTSD -r".  The
Figure illustrates an overview of the DTS Save and Restore design.
The DTS entity when started with no input argument (i.e., DTSD) will
function as shipped by OSF version 1.0.3.  In addition to the
original startup functionality, the default configuration is saved to
the protected file 'dtsconfg', overwriting the previous
configuration.

      Each time one of the Advertise, Create, Enable, Delete, Set or
Unadvertise DTSCP commands is successfully processed by the DTS
entity, a new routine is called to write the DTS configuration to the
protected file 'dtsconfg' recording the modified characteristics.

      When the DTS entity is started using the Restore input
parameter (i.e., DTSD -r) the following is done:
  o  After the DTS entity initialization is completed, the DTS Entity
      looks for the file 'dtsconfg' to restore the previous
      configuration.
  o  If this file doesn't exist, a default configuration is used.
The
      default configuration is currently hard coded as the startup
      configuration for the DTS entity.
  o  If the file is not readable, the version number does not match
      the current DTS entity version number, the DTS entity Type
      (Server or Clerk) is not valid, the Create Flag is not valid or
      the Advertise Flag is not valid, an error message is then
issued
      and the DTS entity exits.
  o  If 'dtsconfg' is available and has valid data, then a series of
      DTSCP command directives (DirectiveCreate(), DirectiveSet(),
      DirectiveEnable(), and DirectiveAdvertise() ) are executed
based
      on the records retr...