This is beta software and is provided without warantee of any kind.  Effort
had been made to insure the correctness and quality of this software.  Please
address any problems, questions, suggestions to support@kldinc.com.

clockman.zip contains the following 3 files:

clockman.100  --  tandem executable
clockrun.101  --  sample obeyfile for startup
readme.txt    --  this document

This has been tested on D48, but should run on any D40+ system.  It may run on earlier systems, but has not been tested for them.

1.  download the archive.
2.  unzip the archive.
3.  upload clockman.100 in binary using IXF or FTP.
4.  upload clockrun.101 in ascii using IXF or FTP.
5.  "fup alter clockman, code 100" to make it executable.
6.  modify clockrun as necessary.
7.  obey clockrun to start the clock process.

The following params / defines are used:

1.  add define =tcpip^process^name, file $ztc1

    This is the Tandem tcpip process which the program should use to
    access the internet.  The default value is $ztc0.

2.  param tcpip-addr 208.184.49.9

    This is one of the addresses from the list in clockrun.txt.
    Experiment to find an address which gives the best results.
    The servers may not be up all the time so your choice of address
    may change over time.

3.  param tcpip-port 13

    This generally should not be specified.  13 is the default and
    the standard RFC-867 well known port.

4.  param interval 8640000

    If specified and non-zero, the program will continue to check and
    adjust the time at the interval specified.  This is in 1/100 of a
    second.  8640000 will check the time once every 24 hours.

5.  param adjust 1

    If specified and non-zero, the clock will be adjusted.  Otherwise
    the time difference will be reported, but no changes will be
    attempted.  The program must be started by super.super to be
    able to adjust the clock.  The time is adjusted gradually and
    should have no effect on a running software system.  A log message
    is generated when the time is adjusted, but no messages are sent
    to the user terminals.

6.  param setonce 1

    Normally the time will be adjusted slowly over a period of time so
    operations are not disrupted.  However if the time difference is
    greater than 2 minutes, it would may be helpful to set the clock
    instead of slowly adjusting it.  Setting this to a non-zero value
    will allow that to happen.

    Caution: Setting the time while an application system is running may
    impact it's operation.  Be sure you understand any effects this may
    have before setting the time.  This has the same effect as the
    operator performing a settime.  A log message will be generated and
    a message will be sent to each user informing them of the time being
    set.

7.  param format 0

    sets the expected format of the time message.

    0 is the default of RFC-867:
    "<0A>52031 01-05-02 07:29:46 50 0 0 516.1 UTC(NIST) * <0A>"

    1 is an alternate used by SUN (GMT):
    "Thu Apr  5 08:12:56 2001<0A><0D>"

    2 is same as 1 except the time is expected in Local Civil Time.

    3 is an alternate (LCT):
    "Thu Apr  5 08:12:56 EST 2001<0D><0A>"

8.  param trace 1

    when trace is enabled, a log message will be generated each time the
    time is fetched.  The log message contains the actual data received
    from the time server reported as a quoted string.  This is only used
    to help diagnose problems.


With neither param "adjust" or "setonce" specified, this program can be used
to display the accuracy of the Tandem's clock.  Generally the values will be
within better than .5 seconds of accuracy.

When this program is running continously, the clocks on different machines
should be within less than 1 second of each other.  +/- .2 second is likely.