This release includes code for both a mostly-functional UCX client and an
unsupported UCX daemon. This file details the build procedures for adding
UCX support, assuming you have the UCX software already installed on your
system.

UCX client:

  1) Issue a DELETE *.O*;* command in the FINGER build directory
  2) Build FINGER using @UCXTEST.COM rather than @FINGER_BUILD.COM
  3) Proceed to use @INSTALL_FINGER.COM (and @INSTALL_JNET_FINGER.COM,
     if appropriate)

  You will now have outbound UCX FINGER support. The following are known
problems:

  a) You will only be able to FINGER systems that don't care about case in
     usernames, or which use uppercase-only usernames. This is because FIN-
     ger uppercases input by default.
  b) If you use the route-through option (FINGER @NODEA@NODEB) and VMS FINGER
     is the route-through node, an extraneous /IAM= is appended to the com-
     mand given to the remote system, which will confuse it.
  c) The error messages aren't the greatest when there is a problem at the
     remote site.
  d) Domain names are restricted to 32 characters. This may cause problems with
     some European hosts where the domain name is an essay in itself.

 UCX server:

  A user at another site contributed a simple FINGER server. This code was
then modified to work with the DECUS FINGER sources. The file UNSUPPOTED_
UCX_DAEMON.BCK contains the pieces necessary to build the server. To build
it:

  1) FTP the UNSUPPORTED_UCX_DAEMON.BCK file from SPCVXA.SPC.EDU (or send a
     VMSDUMP UNSUPPORTED_UCX_DAEMON.BCK command to VMSSERV@SPCVXA if you're
     on BITNET).
  2) Extract the contents of the saveset into an empty directory (the save-
     set is a 32256-byte fixed format file, and you can use either a utility
     like FILE to fix the record attributes after FTP-ing it or use an FTP
     (not UCX) that supports the STRU VMS option to preserve the file char-
     acteristics. It is also rumored that you could do:

	$ BACKUP any-file FOO.BCK/SAVE_SET
	$ COPY/OVERLAY UNSUPPORTED_UCX_DAEMON.BCK FOO.BCK
	$ BACKUP FOO.BCK/SAVE_SET [empty-directory]

  3) Build the server pieces with @BUILD.COM
  4) Link the daemon with @UCXDTEST.COM
  5) Edit and execute START_UCX_FINGER.COM and RUN_FINGER_DAEMON.COM

  This code is known to have the following problems:

  a) It will not handle multiple simultaneous incoming requests
  b) If you give it a command of the form FINGER @host@host it will hang
     (this is a side-effect of the first problem)

  Both the client and server for UCX represent temporary test versions which
are not being used in the rewrite. The rewritten FINGER will include robust
reentrant support for UCX, MultiNet, and CMU/TEK TCP's (at least). However,
the amount of changes required prohibit using the new code in this version of
FINGER.

	Terry Kennedy		Operations Manager, Academic Computing
	terry@spcvxa.bitnet	St. Peter's College, Jersey City, NJ USA
	terry@spcvxa.spc.edu	+1 201 915 9381