             SoftSolutions(R) 4.1 for Windows Update

                    ENHANCEMENT DOCUMENTATION
                               for
           SoftSolutions Remote Document Server (RDS)

        (C) 1995 Novell, Inc.  All Rights Reserved.  5/95
_________________________________________________________________

This file was created as an ASCII text file.  Any portion of this
file may be reproduced for use by licensed users of SoftSolutions
4.1 for Windows.
_________________________________________________________________

This document provides documentation for the enhancement, Remote
Document Server (RDS), for updating from SoftSolutions 4.0/40.a
to 4.1 for Windows.
_________________________________________________________________

                            CONTENTS
_________________________________________________________________

     Hardware Requirements for RDS
     Installed Files
     Installing RDS
     What Is RDS?
          Document Forwarding
          Two Modes of Operation
          Versatility
          VIM and MAPI Interfaces
          Database Searching with RDS
     Starting RDS
     Stopping RDS
     RDS and Disk Space Usage
     Setting up Full Name Compatibility
     Modifying and Customizing the GroupWise RDS Macros
     RDS Command Line Configuration Switches
          Required Switches
          Optional Switches
     Querying Multiple Datasets With a Single RDS
     Description of Included Files
     Using RDS with the Novell GroupWise Macro
     Using RDS without an Interface Macro
          RDS Basics
          Checking In SoftSolutions Documents
          Checking Out SoftSolutions Documents
          Copying SoftSolutions Documents
          Faxing SoftSolutions Documents
          Forwarding SoftSolutions Documents
          Importing Documents into SoftSolutions
          Searching for SoftSolutions Documents
_________________________________________________________________

                  HARDWARE REQUIREMENTS for RDS
_________________________________________________________________

RDS runs on any Windows-capable PC that is connected to the
network.  For best results, the following minimum configuration
is recommended:

   * 486 PC, 25Mhz or faster
   * 8mb RAM
   * Windows 3.1 or later installed
   * E-mail client installed

RDS can run on 386 PCs with less than 8mb of RAM, but its
response time will be slower.  Some E-mail systems may require
better hardware than that specified here.  The above
recommendations were tested with Novell GroupWise 4.1.  The
expected level of use should be considered when choosing the PC
to use for RDS.

RDS uses a temporary directory.  This directory must have enough
free space to hold 10-15 of the largest documents in your
database.  A minimum of 20mb is recommended.  This directory is
used to hold the documents and search results reports RDS is
forwarding.
_________________________________________________________________

                         INSTALLED FILES
_________________________________________________________________

The following files are installed for RDS when SoftSolutions is
installed.  See the RDS section of the SoftSolutions 4.1
Administrator's Guide for descriptions of these files.

     For MAPI                                      For VIM, MAPI,
     or GroupWise   For VIM        For GroupWise   or GroupWise
     ____________________________________________________________

     MAPIUSER.CTX   SSVIMUSR.CTX   MAPI.DLL*       HELP.TXT
     MAPIUSER.EXE   SSVIMUSR.EXE   RDS.BMP         RDS.CFG
     MAPIUSER.TLN   SSVIMUSR.TLN   RDS.HLP         README.RDS
     MAPIUSER.TXT   SSVIMUSR.TXT   RDS.VEW
                                   RDSHELP.VEW
                                   REMOTE.WCM
                                   REMVIEW.WCM

  *  See the RDS "README" file for details on using this
     MAPI.DLL.
_________________________________________________________________

                         INSTALLING RDS
_________________________________________________________________

  1. Choose a PC to be the RDS server.

        * The PC must have a network connection.

  2. Configure the RDS PC to automatically map network drives on
     startup to all servers and volumes which contain
     SoftSolutions documents.

     NOTE
          RDS cannot automatically map and unmap drives to access
          documents like the SoftSolutions client can.  Before it
          is started, it must have a drive mapped to each server
          and volume that contains a SoftSolutions document.

  3. Create an E-mail user account for the server to use.

        * Give it a name that users will be able to identify in
          the E-mail's address book.  (The default is "SOFTSOL"
          for the GroupWise front end macros.)

        * The E-mail ID should be ONE word, if possible.  (It is
          more difficult to configure RDS to use IDs with more
          than one word.)

        * The GroupWise front end macros are set to use the
          E-mail ID of SOFTSOL.  These macros must be modified if
          you are using GroupWise AND you choose an E-mail ID for
          RDS that is different than SOFTSOL.  See the RDS
          section of the SoftSolutions for Windows
          Administrator's Guide for instructions on modifying the
          macros.

  4. If your E-mail system is GroupWise, do the following:

       a. Start GroupWise using the RDS user ID.

       b. Choose File|Preferences, and double-click on the
          Location of Files icon.

       c. Set the Custom Views directory to the path of the
          SoftSolutions programs directory.

       d. Exit GroupWise.

  5. Perform a SoftSolutions workstation installation on the RDS
     PC.

        * It is NOT necessary to install all of SoftSolutions.

  6. Use a text editor to modify RDS.CFG:

       a. Fill in the lines that tell the server where the
          dataset and strings files are.

       b. Fill in the lines that tell the server which E-mail ID
          and password to use.

       c. Add or remove any other configuration switches, as
          needed.

        * See the description of all configuration switches given
          in the RDS section of the SoftSolutions 4.1 User's
          Guide, and the hints in the sample configuration file
          that is installed in the SoftSolutions programs
          directory.

  7. Set up a Windows icon for RDS on the PC that will be running
     as the RDS server.

        * The properties for the icon should be as follows:

               [SoftSolutions Programs Directory]\MAPIUSER.EXE
                    ^[SoftSolutions Programs Directory]\RDS.CFG

          Example:

               F:\SOFTSOL\MAPIUSER.EXE ^F:\SOFTSOL\RDS.CFG

          NOTE
               Replace MAPIUSER.EXE with SSVIMUSR.EXE if you are
               using a VIM-compliant E-mail system, such as
               cc:Mail or Lotus Notes.

  8. If the GroupWise version of RDS is being used, remote users
     should install the front end macro on their PCs.

        * They can obtain copies of the macro by sending a
          message to RDS with the word "HELP" in the body.  The
          RDS will return a custom message with the files.  Users
          can install the front end macro by clicking on the
          INSTALL RDS MACRO button on the message.

  9. See the RDS section in the SoftSolutions 4.1 Administrator's
     Guide for further information on setting up and maintaining
     RDS (e.g., starting/stopping RDS; command line configuration
     switches; querying multiple datasets).
_________________________________________________________________

                          WHAT IS RDS?
_________________________________________________________________

Remote Document Server (RDS) makes SoftSolutions documents
available to users NOT connected to the LAN.  RDS does this with
E-mail using remote capabilities as its transport mechanism. 
Users send search requests and other commands to SoftSolutions
through E-mail.  These messages are received and processed by
RDS, which is running on a Windows workstation connected to the
LAN.  RDS responds by returning messages with the requested
documents or search results.

RDS allows remote users to perform full-text or Profile searches,
retrieve copies of documents (only the most recent version of a
document), check out documents for editing, check in documents,
add new documents (with Profiles), and forward documents to other
users.

DOCUMENT FORWARDING _____________________________________________

Forwarding documents is a powerful concept.  Remote users,
without logging into SoftSolutions or the network, can forward
any document managed by SoftSolutions to any user to whom the
E-mail system can send messages.  If your E-mail includes a fax
gateway (e.g., Novell's GroupWise Fax Gateway), remote faxing is
also possible.  A New York user without fax hardware or software
can fax a document located in Phoenix to a customer in Japan.

TWO MODES of OPERATION __________________________________________

RDS can run in two modes, "secure" and "guest."

Secure Mode
     When RDS is running in secure mode it only gives access to
     users who are members of a SoftSolutions dataset.  Users
     then only have access to documents they would normally see
     if they were connected locally.  (See "Setting up Full Name
     Compatibility" below for more information on secure mode.)

Guest Mode
     In guest mode, RDS allows users unknown to SoftSolutions to
     have access to documents that are marked PUBLIC or SEMIPRIV. 
     This capability allows SoftSolutions to act as an
     "electronic document catalogue" remote users can query via
     the Internet or any other E-mail gateway.  SoftSolutions can
     also store files that are NOT DOCUMENTS and act as a BBS
     that is accessed through E-mail instead of a communications
     program.

VERSATILITY _____________________________________________________

Besides allowing remote users access to documents managed by
SoftSolutions, RDS can be used in a variety of other ways:

   * RDS does not need to be limited to users who are remote. 
     Local users who use SoftSolutions occasionally may prefer to
     access SoftSolutions datasets through RDS instead of
     installing the full SoftSolutions client (see the software
     licensing agreement).

   * SoftSolutions users can use RDS for FORWARDING documents to
     others via E-mail.

   * RDS can be used to FAX documents, without having any faxing
     software or hardware on the workstation (although a fax
     gateway must be on the network).

   * RDS can be used as a PUBLIC document and file catalog (using
     the "guest" mode).

   * Before RDS, only DOS and Windows users have had access to
     SoftSolutions 4.x datasets.  Now, RDS can also be used from
     a variety of platforms.  For example, Macintosh and UNIX
     users (local and remote) can use RDS for access to
     SoftSolutions-managed documents (see the software licensing
     agreement).

VIM and MAPI INTERFACES _________________________________________

The E-mail system on the RDS server must be VIM or MAPI-
compliant.  RDS uses the VIM or MAPI interface of the E-mail
system to query its own in and out E-mail boxes.  But, individual
users' E-mails do not need to be VIM or MAPI-compliant to use
RDS.

Although RDS requires VIM or MAPI compliance for accessing its
E-mail boxes, users of other E-mails may send requests to RDS IF
a gateway that allows attachments exists between the requesting
user and RDS.

The RDS version for Novell GroupWise (shipped with SoftSolutions
4.1) includes a macro front end for Windows that allows users to
make requests in RDS without needing to understand the request
syntax.  Other E-mail users must compose their requests using a
simple syntax (see the RDS section of the SoftSolutions User's
Guide).

Remote users can request a help file that gives them instructions
for using RDS commands in E-mail.

DATABASE SEARCHING with RDS _____________________________________

The idea of database searching through an E-mail system is not
unique.  Never before, however, has an information repository as
dynamic and important as SoftSolutions been available via E-mail. 
SoftSolutions gathers every document that is written within an
organization as soon as the document is created, and without much
effort on the part of the user.  Having access to all of this
information anywhere, at any time, is a great advantage to
organizations with employees who work from remote locations or
who are traveling.
_________________________________________________________________

                          STARTING RDS
_________________________________________________________________

  1. Start the PC and log it onto the network.

  2. Load Windows and double-click on the RDS icon.

RDS is displayed.  It will load your E-mail and commence polling
its IN box every ten seconds.
_________________________________________________________________

                          STOPPING RDS
_________________________________________________________________

To stop the server, make it the active window and press any key. 
The server will prompt you to exit.  You can also double-click on
the system menu box to shut the server down.

The server can also be configured to automatically shut down
after going through its IN box once.  (See the /EXIT switch later
in this section.)
_________________________________________________________________

                    RDS and DISK SPACE USAGE
_________________________________________________________________

One of the functions of RDS is to move documents as E-mail
attachments.  If your E-mail has an OUT box, this can cause rapid
growth of documents stored in the OUT box for the RDS E-mail ID
(RDS automatically deletes each message from the IN box, unless
the /NODEL switch is used).  File server disk space can be used
up very quickly if the RDS OUT box is allowed to accumulate
files.  Novell suggests monitoring RDS' disk space usage to
determine the frequency for deleting files from the OUT box.

Some E-mail systems may also have a "trash" backup of files
deleted from both the IN and OUT boxes.  This, too, should be
monitored for disk space usage.
_________________________________________________________________

               SETTING UP FULL NAME COMPATIBILITY
_________________________________________________________________

For RDS to run in SECURE mode, you must synchronize the full
names of all users in the E-mail system AND in SoftSolutions.

   * The IDs (SoftSolutions and E-mail) do not have to match, but
     the full names do.  For example, if a user was named "David
     Jones" in the E-mail system and "Dave Jones" in
     SoftSolutions, RDS would not recognize that user and deny
     his requests.

   * RDS enforces document security by matching users' E-mail
     full names with their SoftSolutions full names.

   * When RDS is in secure mode, it rejects any requests sent by
     users who are not members of the native E-mail system.  For
     example, a remote GroupWise user will have normal access to
     documents using RDS in secure mode; but, a user querying the
     same RDS via an Internet E-mail gateway would be rejected,
     since the E-mail ID would resolve to an address instead of a
     full name.

   * It is possible to grant an "outside" user access to RDS
     running in secure mode by adding a SoftSolutions user record
     with the resolved E-mail address as the full name.  Just
     have the remote user query RDS.  The rejection message from
     RDS will indicate the RESOLVED ADDRESS of the remote user.

     DISCLAIMER
          RDS relies on the user authentication functionality of
          the E-mail system to provide security against
          unauthorized access.  Therefore, Novell expressly
          disclaims all liability for security breaches caused by
          deficiencies in the E-mail system.
_________________________________________________________________

       MODIFYING and CUSTOMIZING the GROUPWISE RDS MACROS
_________________________________________________________________

The RDS front end macros shipped with SoftSolutions (REMOTE.WCM,
REMVIEW.WCM) make assumptions that may not be true for your site. 
They assume that RDS is using the E-mail ID "SOFTSOL"; that a
GroupWise Fax Gateway is present under the name "FAX:"; and that
the Fax Gateway does not require a dialing prefix.  The Import
and Profile Search dialogues also assume that SoftSolutions is
using the default Document Type and Application codes provided
during installation of SoftSolutions.  If ANY of these
assumptions are NOT true, the macros must be edited before they
will work properly.

The easiest way to edit these macros is to open them in
WordPerfect 6.1 for Windows, make the necessary changes, and save
them.  The macros can also be edited using the GroupWise macro
facility if WordPerfect 6.1 is not available (see your GroupWise
Guide for details).

A section in the very beginning of each macro clearly indicates
where in the macro the variables for the RDS E-mail ID and the
GroupWise Fax Gateway parameters are set.  Follow the
instructions in the macro comments when making changes (other
changes can alter the general behavior of the RDS macros---Novell
does not provide support for such changes).  To change the
Document Type and Application codes in the dialogues, click on
the "Dialog Editor" button in WordPerfect, then edit the dialog.
_________________________________________________________________

             RDS COMMAND LINE CONFIGURATION SWITCHES
_________________________________________________________________

REQUIRED SWITCHES _______________________________________________

/DATA=[SoftSolutions Datapath]

     The SoftSolutions datapath that indicates where the dataset
     is.  This is the same datapath that is used by SoftSolutions
     itself.

/STRDIR=[Strings File Directory]

     The full path to the directory where the strings files,
     SOFTSOL.CTX and MAPIUSER.CTX or SSVIMUSR.CTX are stored. 
     This should be the SoftSolutions programs directory.

OPTIONAL SWITCHES _______________________________________________

/?

     Causes the server to display a help window describing all of
     its switches.

/DEBUG

     Causes the server to display extensive information about
     each request that it processes.  It is useful for diagnosing
     problems.

/DEFAPP=[Application Code]

     This code tells RDS what the application is for the document
     being imported.  RDS selects an application in the following
     order:  1st) as specified by the user; 2nd) the application
     specified in the Screen Definition record for the user; or
     3rd) the value given for the /DEFAPP= switch.

/DEFTYPE=[Type of Document Code]

     This code tells RDS which type of document is being
     imported.  This default is replaced when a user specifies
     differently.  RDS selects a type in the following order: 
     1st) as specified by the user; 2nd) the type specified in
     the Screen Definition record for the user; or 3rd) the value
     given for the /DEFTYPE= switch.

/ERRLOG=[Path and Filename to Error Log File]

     A file for recording RDS errors.  Without this switch, error
     messages are only displayed on screen.

/EXIT

     Causes the server to stop after going through all of the
     unread messages in its IN box.

/GUESTS

     Tells RDS to allow ANYONE to access the documents in the
     datasets that it is monitoring.  The requesting user does
     not have to be a user in SoftSolutions.  Such guest users
     will only have access to public and semiprivate documents. 
     But, users who are listed as a user in SoftSolutions will
     still have all of their normal access rights.

/ID=[SoftSolutions Workstation ID]

     The SoftSolutions Workstation ID that the server should use. 
     This is usually not necessary unless you are using the
     SoftSolutions Document & Security Server NLM on your system.

/LOG=[Path and Filename to Usage Log File]

     A file for recording an RDS success log.  Success logs are
     useful for determining RDS usage.  Without this switch,
     success log messages are only displayed on screen.

/MAILUSER=[E-mail ID]

     The E-mail ID that the server should use to receive incoming
     commands.

/MAILPASS=[Password]

     The password for the server's E-mail ID.

/NODEL

     Tells RDS not to delete messages that it has processed from
     its IN box.  This helps administrators monitor server usage.

/TDIR=[Temp Directory]

     A directory that RDS can use to store documents it is
     working on.  This directory should have room for at least 10
     of the largest documents in the SoftSolutions datasets.

     ============================================================
     CAUTION:
     Ensure that the temporary directory specified with this
     switch is different from the temporary directory in the
     Workstation ID specified with the /ID switch.  If no /TDIR=
     switch is given, RDS should not have the Workstation ID's
     temporary directory as the current working directory.  RDS
     cannot send documents using the same temporary directory as
     SoftSolutions.
     ============================================================

/VIEWONLY

     Disables the IMPORT, CHECK-OUT and CHECK-IN commands,
     effectively turning the dataset into a read-only repository,
     as far as the remote user is concerned.  Remote users can
     obtain copies of documents, but they can't modify them and
     send them back to SoftSolutions, or create new documents for
     SoftSolutions to store.
_________________________________________________________________

          QUERYING MULTIPLE DATASETS with a SINGLE RDS
_________________________________________________________________

A single RDS can serve documents from many datasets.  The
datapath given with the /DATA= switch indicates the default
dataset for that RDS.  Unless users specify otherwise, all
queries will be directed to that dataset.  If users include the
SCOPE command with their query, they can indicate from which
datasets RDS should obtain results or documents.  The default
dataset must have a reference for all other datasets that it
should access in the SETUP DATASETS window.  RDS checks there for
instructions on how to get to any other datasets that it is asked
to query.

NOTE
     If RDS is running in "secure" mode, a user must be a member
     of the default dataset to have access to SoftSolutions
     files.  If other datasets are included in a query, the user
     must also have membership in each of them---membership in
     the main dataset does NOT automatically grant a user rights
     to other datasets.

NOTE
     The /GUESTS and /VIEWONLY switches apply to ALL datasets
     being monitored by a particular RDS.  Currently, RDS cannot
     allow GUEST users access to one dataset while blocking their
     access to other datasets.  Likewise, RDS cannot prevent
     importing in one dataset (with view only) while allowing
     importing to another.

     If GUEST access or import capability is needed in one
     dataset and not another, two RDS servers will need to be
     used.
_________________________________________________________________

                  DESCRIPTION of INCLUDED FILES
_________________________________________________________________

     FILE           DESCRIPTION
     ____________________________________________________________

     HELP.TXT       Sample help files for RDS.  It is a text file
                    on using the server.  This file is installed
                    in the SoftSolutions programs directory.  If
                    a directory other than this is specified in
                    the /STRDIR= switch, HELP.TXT should reside
                    there.

                    RDS forwards this file to users who request
                    it with the HELP command, or who send
                    commands to the server that are invalid. 
                    THIS FILE MAY BE CUSTOMIZED OR REPLACED.  It
                    is not required to be a text file.

                    Since the HELP.TXT file is sent back as an
                    attachment, it can be in any format available
                    for the user to read the file.  As examples,
                    it could be a WordPerfect 6.1 for Windows
                    file, which is readable in GroupWise; or, it
                    could be a run-time Envoy file.

                    If the HELP.TXT file is replaced with
                    something other than a .TXT file, the strings
                    file (MAPIUSER.CTX or SSVIMUSR.CTX) should be
                    edited to change the extension of the help
                    file to one compatible with the new file
                    (e.g., .WPD, .EVY).

     MAPIUSER.CTX (MAPI) or SSVIMUSR.CTX (VIM)
                    The strings file for RDS.  It is also stored
                    in the SoftSolutions programs directory.

     MAPIUSER.EXE (MAPI) or SSVIMUSR.EXE (VIM)
                    This is the server-executable.  It is
                    installed to the SoftSolutions programs
                    directory.

     MAPIUSER.TLN & MAPIUSER.TXT (MAPI) or SSVIMUSR.TLN &
     SSVIMUSR.TXT (VIM)
                    These files are only needed when modifying
                    the strings used by RDS.  Some reasons for
                    modifying the strings:  a) to change command
                    keywords; b) to change messages that are
                    returned by RDS; or c) to change the names of
                    the help files returned by RDS.  For example,
                    you may wish to modify some of the error
                    messages to instruct users who to call when
                    an error occurs.  (See the SoftSolutions
                    Administrator's Guide for help on modifying a
                    strings file.)

     RDS.BMP (GroupWise version only)
                    Bitmapped logo used by the RDS macros
                    REMOTE.WCM and REMVIEW.WCM.  This file is
                    installed in the SoftSolutions programs
                    directory.  It is sent to each user
                    requesting help and is installed in their
                    GroupWise macros directory.  The GroupWise
                    macros front end will work without this logo.

     RDS.CFG        A sample configuration file for the server. 
                    This file holds switches that tell the server
                    where the dataset is, which E-mail ID to use,
                    where the strings files are, etc.  This file
                    is installed in the SoftSolutions programs
                    directory.  You MUST customize the file in
                    this directory.  This file includes comments
                    specifying where modifications will need to
                    be made to properly configure RDS.

     RDS.HLP (GroupWise version only)
                    A Windows help file for use with the two
                    front end macros for RDS.  It is distributed
                    along with the macros when a user requests
                    help or submits an invalid command.

     RDS.VEW, RDSHELP.VEW (GroupWise version only)
                    These files are GroupWise message views that
                    RDS uses when responding to requests.  These
                    files are installed in the SoftSolutions
                    programs directory.  GroupWise must be
                    configured to look for views in this
                    directory when RDS runs.  See RDS section of
                    the SoftSolutions for Windows Installation
                    Guide.

     README.RDS     A text file containing documentation
                    additions and errata for RDS.  It contains
                    any RDS changes that may be made after the
                    initial release of SoftSolutions 4.1.

     REMOTE.WCM & REMVIEW.WCM (GroupWise version only)
                    GroupWise macros act as the front end for
                    RDS.  When users query RDS, they can simply
                    run one of these macros and fill out the
                    appropriate dialog box.  Users do not have to
                    be familiar with the syntax of the message
                    sent to RDS.  This front end greatly
                    simplifies the use of RDS.

                    REMOTE.WCM is the front end macro for normal
                    datasets where importing and checking out are
                    allowed.  REMVIEW.WCM is a stripped-down
                    version of the macro that does not provide
                    support for importing or checking out files.

                    These files are installed in the
                    SoftSolutions programs directory.  They are
                    distributed to remote users who request help;
                    they are installed in the GroupWise macros
                    directory of the requesting user.

                    These files need to be modified slightly to
                    reflect the E-mail ID used by RDS (if the
                    default of "SOFTSOL" is not used).  See
                    "Modifying and Customizing the GroupWise RDS
                    Macros" above for instructions on modifying
                    these files.

_________________________________________________________________

            USING RDS with the NOVELL GROUPWISE MACRO
_________________________________________________________________

RDS, as it is shipped with SoftSolutions, includes a macro front
end for GroupWise, which can be used to compose document requests
without knowing the syntax that RDS expects.  The macro presents
simple dialogues that ask users to specify which document or
search they need.  The macro takes the information and uses it to
compose an E-mail request in the proper syntax.  Using the macro
front end greatly simplifies the use of RDS and minimizes user
mistakes.

The RDS macro for GroupWise comes with a Windows help file that
can be accessed via the HELP button.  See this help file for
information on using the macro.
_________________________________________________________________

              USING RDS WITHOUT an INTERFACE MACRO
_________________________________________________________________

For E-mails other than GroupWise, or when a macro front end is
unavailable, the following describes how to use RDS in an E-mail. 
E-mails other than GroupWise may have macro capability.  Ask your
system administrator if a front end macro has been written for
your E-mail.

RDS BASICS ______________________________________________________

SENDING REQUESTS to RDS

     Always address your requests to the E-mail ID that has been
     assigned to RDS.  This ID is set by the system
     administrator.

     The SUBJECT field is not used by the utility, but the
     response will come back with the same subject plus
     " - Reply" tacked on the end.  Specifying a subject is
     recommended because it helps identify the return message.

     The body of the message is where the request is recorded. 
     Only one request may be specified in a single E-mail
     message.

     The first line of the message body must specify a command
     followed, in most cases, by a document specification list. 
     The document specification list indicates which documents
     should be acted upon by the command.

     Valid commands (not case-sensitive):

          CHECK-IN
          CHECK-OUT
          FORWARD
          GET
          HELP
          IMPORT
          SEARCH

DOCUMENT SPECIFICATION LISTS

     A "document specification list" identifies a group of
     documents that should be acted upon by a command.  The list
     can take any one of the following forms:

        * a document number

        * a range of document numbers (e.g., 10-100)

        * a series of document numbers separated by spaces (e.g.,
          24 345 231)

        * the letters "wl" (e.g., specifies the user's
          worklist---use without the quote marks)

        * a search criteria in parentheses (e.g., (2=test) )

     Document specification list examples:

          CHECK-OUT 12        Checks out document number 12.

          CHECK-OUT 100-110   Checks out documents 100 through
                              110 (inclusive).

          GET WL              Returns the 10 latest documents on
                              the user's worklist.

          SEARCH (TEST)       Returns a report on all documents
                              with the word "test" in the text or
                              Profile record.

          SEARCH (2=test)     Returns a report on all documents
                              with the word "test" in the "Name"
                              field of the Profile record.

MODIFIERS

     The remaining lines of the message may contain various
     modifiers that elaborate on the basic request.  The most
     important of these modifiers is "SCOPE."  The SCOPE keyword
     is followed by a list of SoftSolutions dataset IDs,
     separated by spaces.  It specifies which datasets should be
     searched, or which datasets contain the documents that
     should be acted upon by the command.  The CHECK-IN, HELP,
     and IMPORT commands do not use the SCOPE modifier.  All
     other commands do.

     If a SCOPE modifier is not given in a request, the default
     dataset is the assumed scope for the request.  The default
     dataset is the dataset specified by the system administrator
     when RDS is configured.

     Other modifiers exist for some commands, such as FORWARD and
     IMPORT.

     The modifiers are discussed in the following along with
     their respective commands.

HELP for RDS

     If a user needs help, a message can be sent to RDS with the
     word "HELP" in the message body.  RDS responds with a return
     message that can have up to five (5) attached files.  By
     default, it returns a copy of the help file "HELP.TXT" that
     is shipped with the product.  The GroupWise version also
     sends a copy of the files needed for the front end macro,
     which simplifies the process of composing queries.

     If desired, the system administrator can edit the strings
     file for RDS and configure up to five (5) files that should
     be returned when a HELP request is received.  These files
     can be anything the administrator wishes.  Then, if a user
     sends a request to RDS using invalid syntax, RDS responds
     with the help message and its attached files.

(The RDS commands are described under the following subheadings,
which are listed alphabetically:

     Checking In SoftSolutions Documents
     Checking Out SoftSolutions Documents
     Copying SoftSolutions Documents
     Faxing SoftSolutions Documents
     Forwarding SoftSolutions Documents
     Importing Documents into SoftSolutions
     Searching for SoftSolutions Documents )

CHECKING IN SOFTSOLUTIONS DOCUMENTS _____________________________

A user who has checked documents out of a SoftSolutions dataset
can check them back in via RDS.  ONLY ONE DOCUMENT MAY BE CHECKED
IN PER REQUEST.

To check a document in, the user should compose a message and
attach the file that is to be checked in.  The message should
only have one line.  That line should include the keyword
"CHECK-IN," followed by the dataset ID and the document number to
which it should be checked in as.

The following example would check in the attached file as
document number 34 in the LA dataset:

     CHECK-IN LA 34

The dataset ID is optional.  If it is not given, RDS checks the
document into the default dataset.  RDS will not check in a
document if it is not marked as "Checked Out" in SoftSolutions,
OR if it was checked out by a different user than the one who is
attempting to check it back in.

NOTE
     When a file is checked into SoftSolutions, it overwrites the
     latest version of the file in the dataset.  RDS correctly
     checks in documents according to the Dataset ID and Document
     Number of the file, but has no control over incorrect
     associations made by users.  Therefore, when checking
     documents into SoftSolutions users should be aware that if
     they incorrectly associate a document with another
     document's Dataset ID or Document Number, data can be lost
     when a file being checked in overwrites a different file in
     the dataset.

If a CHECK-IN request is sent without an attached file, RDS
resets the In Use flag of the document in SoftSolutions so that
it is no longer locked.  The latest version of the document in
SoftSolutions will remain the same as it was before it was
checked out.

RDS responds to CHECK-IN requests with a message stating that the
document has been checked in.  If no file was sent, RDS indicates
that no file was uploaded (attached for checking in).

CHECKING OUT SOFTSOLUTIONS DOCUMENTS ____________________________

Remote users can check documents out of SoftSolutions.  This
causes the document to be locked until it is checked back in. 
Nobody, local or remote, can modify the document in the meantime. 
The requesting user will receive the documents as attachments to
the return message.  The files can then be saved to disk,
modified as needed, and sent back to SoftSolutions with a
CHECK-IN request.

A CHECK-OUT request has the keyword "CHECK-OUT," followed by a
document specification list.  A SCOPE modifier can be given on
the second line, indicating which dataset contains the documents
that are to be checked out.

The following example would check out document 25 from the LA
dataset:

     CHECK-OUT 25
     SCOPE LA

The following example would check out the 10 most recently-
created documents with "FRED" as the author (from the default
dataset):

     CHECK-OUT (3=fred)

NOTE
     If a user intends to modify documents sent by RDS, those
     documents must be saved to disk first.  If a user opens a
     document directly from the E-mail system, the user will
     usually not be able to modify the file, or at least the
     changes that are made will not be saved.  This may not be
     true for all E-mail systems, but it is for most.

COPYING SOFTSOLUTIONS DOCUMENTS _________________________________

Users can retrieve copies of any document stored in
SoftSolutions.  Doing so does not mark the document as "In Use"
in SoftSolutions.  Copies retrieved in this way can be modified
and sent back as new documents, but they cannot be checked in as
the document that was originally requested unless that document
is first officially checked out (see "Checking Out SoftSolutions
Documents" above).

To obtain documents, users must send a request with the keyword
"GET" in the first line, followed by a document specification
list identifying the documents to be retrieved.  Any kind of
specification, including a search criteria, can be used.  RDS
returns the first 10 documents in the list.  NO MORE THAN 10
DOCUMENTS CAN BE RETRIEVED WITH ANY ONE REQUEST.  This software-
imposed limit prevents time lost from accidents, such as a user
requesting all documents that match an extremely broad search
criteria.

The following example would retrieve a copy of document 10 from
the LA dataset:

     GET 10
     SCOPE LA

This example would retrieve documents 10 through 12 from both the
LA and NY datasets:

     GET 10-12
     SCOPE LA NY

This example would retrieve the 10 most recently-created
documents, which include the words "sales" and "budget," from the
LA dataset:

     GET (sales budget)
     SCOPE LA

As usual, if the SCOPE modifier is not given, RDS searches only
the default dataset.

FAXING SOFTSOLUTIONS DOCUMENTS __________________________________

E-mail systems may have the capability to provide fax gateways
that can be used with RDS to fax documents.  A GroupWise Fax
Gateway is available from Novell, Inc.

The GroupWise Fax Gateway is an add-on product for GroupWise that
allows users to send E-mail messages to any name and fax number. 
Not only can the gateway fax the message, but it will also
attempt to fax any documents that were attached to the message. 
RDS and the Fax Gateway can work together to allow users to
forward documents stored in SoftSolutions to ANY name and fax
number.  Any document that can be opened or converted by
WordPerfect 6.0b for DOS can be faxed through RDS and the
GroupWise Fax Gateway.  To do this, simply send a FORWARD
request, like those shown below (see "Forwarding SoftSolutions
Documents").  The recipient in the "TO" clause should follow this
syntax:

     [Fax Gateway Name]:[Recipient's Name]@[Fax Number]

The recipient's name may include spaces, but the fax number may
not.  The fax number should have nothing in it but digits.  The
Fax Gateway name is usually something generic, like "FAX."  (This
name is set by the system administrator for GroupWise.)

For example, to fax document 2065 in the default dataset to Mark
Phelps at the fax number (801) 224-0920, the following message
would be sent to RDS:

     FORWARD 2065
     TO FAX:Mark Phelps@1-801-224-0920

The sender of the request will receive a return message
confirming that SoftSolutions has forwarded the document to the
Fax Gateway.  The recipient will receive the text of the document
via fax with a preliminary message indicating WHAT the document
is and WHO forwarded it.  The subject line of the original
message sent to RDS is passed on as the subject line in the fax
header.  Instructions to the recipient can be passed on, as
discussed below with the FORWARD command.

FORWARDING SOFTSOLUTIONS DOCUMENTS ______________________________

Users can send copies of documents to other users via E-mail. 
The documents are not checked out in SoftSolutions.  RDS simply
forwards a COPY.

Up to 10 documents can be forwarded at a time.

The most basic FORWARD request consists of two lines.  The first
line has the keyword "FORWARD," followed by a document
specification list indicating the documents to be forwarded.  The
second line has the keyword "TO," followed by the E-mail ID or
group name of the recipients.

For example, the following message would forward document 10 to
Joe Edwards:

     FORWARD 10
     TO Joe Edwards

The value following the TO keyword can be any name, group name,
or address that the E-mail system can resolve.  It might be the
Internet address of a user in a different company if the E-mail
system has access to the Internet.

A FORWARD request can also include a SCOPE modifier on the second
or third line, if needed.

The following message would forward document 11 from the LA
dataset to "John Brown":

     FORWARD 11
     SCOPE LA
     TO John Brown

The next message would forward documents 10 through 12 from both
the LA and NY datasets to "Mark Phelps."

     FORWARD 10-12
     SCOPE LA, NY
     TO Mark Phelps

The next message would forward the next ten documents, from all
datasets, whose CUSTOM 2 field contained the value "IBM," to the
"Legal" E-mail group.  Note that the Field ID for the CUSTOM 2
field is "6."

     FORWARD (6=IBM)
     SCOPE ALL
     TO Legal

The order of lines is not important.  The command (e.g., FORWARD)
is usually first, but the SCOPE and TO modifiers can be in any
order.

A FORWARD request can also include instructions in a block of
text that should be passed to the recipient.  This block of text
should be placed at the end of the request, beginning on a new
line, following the keyword "INSTRUCTIONS:."

For example, the following FORWARD request includes instructions:

     FORWARD 12
     TO Mark Phelps
     INSTRUCTIONS:
     Mark,
     Please look these documents over and send your comments back
     to me via E-mail.  I need a reply by Wednesday.

RDS can forward only up to 3,000 characters worth of
instructions.

RDS sends two messages in response to a FORWARD request.  The
first message goes back to the sender, informing that the request
was successful.  The second message goes to the recipient and
includes the documents and instructions that were forwarded.

IMPORTING DOCUMENTS INTO SOFTSOLUTIONS __________________________

A remote user can send new documents to RDS to be imported into
the SoftSolutions dataset.  An IMPORT request begins with a line
containing only the keyword "IMPORT."  The remaining lines of the
message contain field names, followed by the equal sign (=), and
the value that should be assigned to that field when a Profile is
added for the new document.  The document to be imported should
also be attached to the IMPORT request message.

The following field IDs are optional.  If they are not given, RDS
assigns default values to these fields:

     APP = [8-character code for the document's application]

     AUTHOR = [8-character ID of the document's author]

     CUSTOM1...CUSTOM16 = [10-character code for that custom
               field; date and numeric custom fields are NOT
               supported by the IMPORT feature]

          (The actual name of the custom field as configured in
          SoftSolutions should be used as the keyword, rather
          than the "CUSTOM..." literal shown above.)

     COMMENT:
          The COMMENT: keyword is followed by a hard return and a
          text block (up to 3,000 characters) that will be stored
          in the "Comment" field of the Profile record.  The
          comment block, if used, must always be at the very end
          of the IMPORT request.

     DATASET = [8-character ID of the dataset where the document
               should be stored]

     NAME = [70-character description of the document]

     SECURITY = [65-character list of all user and group IDs
               which should have access to the document after it
               is imported]

     TYPE = [8-character Document Type code]

The following example would import the attached WordPerfect 6.1
file into the LA dataset with the various Profile fields set as
shown.  The LA dataset has the "Custom 1" field configured to be
"PROJECT."

     IMPORT
     DATASET = LA
     APP = WPWIN61
     TYPE = PROP
     PROJECT = SALES
     NAME = Sales budget for the East region in 1995
     COMMENT:
     This is the new budget for the East sales region in 1995. 
     We had to drop the proposal for new laptops to fit within
     the amounts specified by headquarters.  Please contact
     Lawrence Bingham if you see anything that needs to be
     changed before the committee meeting on Thursday.

The following list shows how RDS assigns values to optional
Profile fields that are not specified by the user in an IMPORT
request.

     FIELD               METHOD
     ____________________________________________________________

     Application         RDS selects an application in the
                         following order:  1st) as specified by
                         the user; 2nd) the application specified
                         in the Screen Definition record for the
                         user; or 3rd) the value given for the
                         /DEFAPP= switch.

     Author              RDS selects an author in the following
                         order:  1st) as specified by the user;
                         2nd) the author specified in the Screen
                         Definition record for the user; or
                         3rd) the requesting user's SoftSolutions
                         User ID.  If RDS is running in Guest
                         mode, and the importing user is not a
                         SoftSolutions user, the author will be
                         "GUEST."

     Comment             The comment field will be left blank.

     Creator             In secure mode, this field is set to the
                         requesting user's SoftSolutions User ID. 
                         In guest mode, "GUEST" is used as the
                         ID.

     Custom Fields       Custom fields are not set.

     Dataset             The document will be stored in the
                         default dataset as specified by the
                         administrator responsible for RDS.  This
                         is the dataset given in the /DATA=
                         switch when RDS is started.

     Date Created        The "Date Created" field is always set
                         to the current date at the time the
                         document is imported.  This field cannot
                         be set by the user.

     Name                The Profile's "Name" field will read,
                         ""[Filename]" was imported by remote
                         user [User Name] using RDS."

     Security            The "Document Security" field will be
                         set to "PUBLIC."

     Type                RDS selects a type in the following
                         order:  1st) as specified by the user;
                         2nd) the type specified in the Screen
                         Definition record for the user; or
                         3rd) the value given for the /DEFTYPE=
                         switch.

After an IMPORT request is processed, RDS responds with a return
message verifying that the document has been added.  The return
message specifies the document number the basic other Profile
fields set for that document.

If RDS fails to import the document, a return message is sent
specifying why the IMPORT request failed.  The document is
returned as an attachment.

SEARCHING for SOFTSOLUTIONS DOCUMENTS ___________________________

Remote users can ask RDS to return search reports describing all
documents that match a given criteria.  Search reports are text
files that are attached to the return message.  The report is
given in a text file, rather than the message body, since it can
be quite large, depending on the criteria given.

NOTE
     A vague search criteria could return over 10,000 hits.  Such
     a report would not fit in the message buffer of most E-mail
     systems.

A search request never consists of more than two lines.  The
first line has the keyword "SEARCH," followed by a document
specification list, which is usually a search criteria surrounded
by parentheses.  The second line is an optional SCOPE modifier
indicating the datasets (or document libraries) that should be
searched.

For example, the following request would return a report on all
documents in the LA and NY datasets that contain the word "sales"
anywhere in their text, or in their Profile record:

     SEARCH (sales)
     SCOPE LA NY

If the SCOPE line is omitted, RDS searches the default dataset
only.

Any valid SoftSolutions search criteria can be placed between the
parentheses.  For example, the following request would locate all
documents containing the word "sales" in the "Name" field of the
Profile record, and which also list "MARKP" as their author:

     SEARCH (2=sales AND 3=markp)

The numbers 2 and 3 in this example are SoftSolutions Field ID
numbers for the Profile record.  Valid Field IDs are listed
below:

     FIELD NAME          FIELD NUMBER
     ____________________________________________________________

     Application         11
     Author               3
     Comment             29
     Creator              8
     Custom 1             5
     Custom 2             6
     Custom 3            15
     Custom 4            16
     Custom 5            17
     Custom 6            18
     Custom 7            19
     Custom 8            20
     Custom 9            21
     Custom 10           22
     Custom 11           23
     Custom 12           24
     Custom 13           25
     Custom 14           26
     Custom 15           27
     Custom 16           28
     Date Created         7
     Date Revised         9
     Home Dataset        81
     Name                 2
     Revisor             10
     Security            12
     Status (in use)     80
     Text                 1
     Type                 4

(See the SoftSolutions User's Guide to learn more about valid
search criteria.)

Users can also pass document specification lists that are not
search criteria.  Doing so returns a report listing the basic
attributes of all documents in the list.  For example, the
following request would return a report listing all of the
documents on the user's worklist in the default dataset (e.g.,
the last 20 documents opened by that user in that dataset):

     SEARCH wl
