|Standard Operation||Database Integrity|
This chapter describes how to configure your Fileshare Client and Fileshare Server.
This section describes all of the available Fileshare Client configuration options. These options can appear as many times as necessary within a Fileshare Client configuration file, and in any order, but only one option can be specified per line.
|Client Configuration Option
|The default communications protocol for this Fileshare Client. Valid values for CCI-protocol are listed in the table below.|
/cm CCI-protocol /s server-name
|The communications protocol to use when contacting the Fileshare Server, server-name. Valid values for CCI-protocol are listed in the table below.|
/ct CCI-timeout server-name
|The communications timeout period, specified in 1/10th seconds. The default is 1200 (120 seconds). See the section CCI Timeout in the chapter Communications for more information.|
|The data file filename is a remote file on the Fileshare Server named server-name. Repeat this option for every data file you want assigned to a specific Fileshare Server that is not the default Fileshare Server. Valid values for filename and server-name are listed in the table below.|
|filename is a local data file held on the PC where the Fileshare Client resides. Valid values for filename are listed in the table below.|
|The server-name as a default Fileshare Server|
Accesses to data files not directed to a particular Fileshare Server or not defined as local data files are directed to the default Fileshare Servers. The order in which the default Fileshare Servers are defined in the Fileshare Client configuration file is the order in which the Fileshare Client contacts each Fileshare Server in an attempt to locate the file.
If the data file is not found on any Fileshare Server, the request for that data file is directed to the first default Fileshare Server listed in the configuration file.
Valid values for options in the Fileshare Client configuration file are:
||Any character string up to 16 characters long
depending on the CCI protocol you are using. The Fileshare Client
configuration file can contain a maximum of 16 unique Fileshare Server
||Any valid filename that is supported by the operating
system. Filenames cannot contain embedded space characters. You can use
terminating wildcard characters in filename to designate groups
of files. For example, use
This example shows a typical Fileshare Client configuration file.
/s server1 /s server2 /cm cciipx /f \orders\* /s server3 /cm ccitcp /s server3 /f \accounts\payroll.dat /f \transport\delivery\*
server1 is one
of the default Fileshare Servers.
This Fileshare Server is searched for any file that is not defined as
being on a particular Fileshare Server (see Line 4) or as local (see Lines
6 and 7). If you specify more than one
default Fileshare Server (see Line 2), the Fileshare Servers are searched
in the order that you have defined them in the configuration file. In this
server1 is searched
also a default Fileshare Server. If you access a file that you have not
defined to be on a particular Fileshare Server (see Line 4) or as local
(see Lines 6 and 7), this Fileshare Server is searched after the Fileshare
Specifies that the default communications protocol is CCIIPX. When the Fileshare Client tries to contact a Fileshare Server that does not have a specific CCI protocol defined (see Lines 1 and 2), this is the one used.
/f \orders\* /s server3
Specifies that FHRedir should direct all accesses to files with a name
beginning with the string
to the Fileshare Server named
/cm ccitcp /s server3
Specifies that the communications protocol to use when communicating
with the Fileshare Server,
ccitcp. This overrides any
default CCI protocol specified in the Fileshare Client configuration file
(see Line 3).
Specifies that the file \accounts\payroll.dat is a local file on the Fileshare Client machine. The Fileshare Client accesses this file using a local copy of the Callable File Handler.
Specifies that any files with a filename beginning with the string \transport\delivery\ are local files.
This section describes all of the available Fileshare Server
configuration options. The
option that defines the server-name is compulsory. All other options are
optional or have default values that are specified below.
|Server Configuration Options
|The name that the Fileshare Server registers on the network. This must be a character string up to 16 characters in length, depending on the CCI protocol that you are using. The name specified must be unique. If a Fileshare Server with the same name is already registered on the network, an error is returned.|
|The name of the database reference file that the Fileshare Server is to use. The database reference file is used to determine which additional Fileshare features you want to use. See the section Database Reference File Maintenance in the chapter Database Integrity.|
|Setting the record lock timeout period after which the Fileshare Server releases all record locks held by a Fileshare Client and rolls back any outstanding transactions. The timeout period is specified in seconds. The default value is 60 seconds. Specifying a value of zero disables the timeout and record locks are only released under the control of your application program. Valid values are 0 thru 99999. The timeout only occurs if one Fileshare Client requests a record currently locked by another Fileshare Client. See the section Automatic Record Lock Timeout in the chapter Database Integrity .|
|The maximum record size that can be processed by the Fileshare Server. Setting a value lower than the default value reduces the amount of memory that the Fileshare Server needs to run. The record size is specified in kilobytes. Valid values are 16 thru 64. If you specify a value less than 16, the Fileshare Server uses a buffer size of 16K. If you specify a value greater than 64, the Fileshare Server uses a buffer size of 64K.|
|The CCI protocols that the Fileshare Server can use.
Repeat this option for every communications protocol that you want to
use to contact this Fileshare Server. Valid values for cci-protocol
|The name of the password file that the Fileshare Server uses. See the chapter Security for details.|
|Activating the Fileshare Server trace option on start-up. Trace messages are written to the screen and to a file called fsscreen.lst in the Fileshare Server's current directory. This option seriously impacts the Fileshare Server's performance, so you should only use it for problem investigation. See the section Monitoring Fileshare in the chapter Advanced Operation.|
|The directory that the Fileshare Server changes to on start-up. This option is only relevant if you are running the Fileshare Server as a background service on Windows NT. See the section Running Fileshare as a Windows NT Service in the chapter Advanced Operation.|
The Fileshare Server is to run as a background process. See the chapter Fileshare on UNIX for more details.
This example shows a typical Fileshare Server configuration file.
/s mainsrv /cm cciipx /d dbase1.ref /t 120 /pf \pass\passwd.fil
Specifies that the Fileshare Server is to register its name on the network as mainsrv. Fileshare Clients must specify this name when they want to contact this Fileshare Server.
cciipx is one
of the communications protocols that a Fileshare Client can use to contact
this Fileshare Server.
Specifies that the database reference file the Fileshare Server is to use is named dbase1.ref.
Specifies that the automatic record lock timeout period is
Specifies that the Fileshare Password Security feature is enabled and that the password file is \pass\passwd.fil containing valid user-IDs and passwords.
Copyright © 1999 MERANT International Limited. All rights reserved.
This document and the proprietary marks and names used herein are protected by international law.
|Standard Operation||Database Integrity|