This example shows a typical Fileshare Client configuration file.
/s server1 /s server2 /cm ccism /f \orders\* /s server3 /cm ccitcp /s server3 /f \accounts\payroll.dat /f \transport\delivery\* /f \returns\* /r module1!userfh1
Specifies that 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 example, server1 is searched before server2.
Specifies that server2 is 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 Server server1.
Specifies that the default communications protocol is CCISMEM. 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 \orders\ to the Fileshare Server named server3.
/cm ccitcp /s server3
Specifies that the communications protocol to use when communicating with the Fileshare Server, server3 is 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.
/f \returns\* /r module1!userfh1
Specifies that the customer file handler userfh1 in module1 should be used for all accesses to files with a name beginning with the string "\returns\".
Note that module1 specifies the library containing a custom file handler and that usedrfh1 is the name of the custom file's entry point.
This option only applies if the environment variable DYNREDIR is set to DYNCONFIG.