This chapter explains how to set up Fileshare. It covers the following topics:
You should read the first two chapters in this Using with Fileshare Part before reading this chapter.
For more information about Fileshare and its more advanced features see the Fileshare Guide.
Fileshare provides MSS with VSAM data integrity, enabling you to use SYNCPOINT and SYNCPOINT ROLLBACK commands. Fileshare also enables you to access data files on other systems running on the same network as the machine running MSS.
MSS can connect to up to sixteen Fileshare Servers, giving you the option of splitting your data across several machines. You can also run a Fileshare Server as a separate process on the same machine running MSS. This means you can effectively test a network application without a network.
Fileshare Servers can be used for the following MSS resources:
Fileshare works in a client/server setup, with the Fileshare Server being the server and an MSS-enabled enterprise server being the Fileshare client. The two can communicate with each other over a variety of protocols. The support for these protocols is provided by Micro Focus Common Communications Interface (CCI) modules. You establish the protocols to be used by each server by specifying the appropriate CCI modules when you start the Fileshare Server. Fileshare files can still be accessed by non-MSS applications at the same time.
The remainder of this chapter explains how to set up both the Fileshare Server and the client region to communicate over these protocols.
Before you try to run a Fileshare Server, you must ensure that Fileshare is available on the server machine.
You must run Fileshare commands from the command prompt.
To start a Fileshare Server, enter the following:
fs /s server-name
where server-name names the server, and corresponds to the ID by which the client region knows the server. The /s parameter is mandatory on each Fileshare command. For a list of valid parameters, see the section Using a Fileshare Server Configuration File.
This command starts a server with the default protocol enabled, and with no password-checking performed when a client tries to access the server. The default protocol is TCP/IP. You can use the /cm switch to explicitly name the protocols to be used. For example:
fs /s fstest /cm ccitc32 /cm ccinb32
In this example, ccitc32 and ccinb32 are the CCI modules required for TCP/IP and NetBIOS, respectively.
The following example starts a server with password-checking applied through the file fs.pwd:
fs /s fstest /cm ccitc32 /pf fs.pwd
The section Using a Fileshare Password File explains how password-checking works.
You can avoid specifying a list of parameters whenever you start the server by creating a Fileshare Server configuration file, as the next section explains.
If you enter the fs command with no parameters, Fileshare looks for a server configuration file named fs.cfg in your current directory.
You can also specify a configuration file of a different name with the /cf option, for example:
fs /cf c:\filesh.cfg
A Fileshare Server configuration file is an ASCII text file that contains one option per line.
The Fileshare Server configuration file, fs.cfg, contains the Fileshare configuration options described below. Only the /s option is required. The /pf option is strongly recommended, however, as without it you cannot enforce any Fileshare security, although MSS does provide Resource Security Level (RSL) checking.
Specifies that server-name is the name that the Fileshare Server registers on the network. The name specified has to be unique to that Fileshare Server and must correspond to the Fileshare Server ID specified in the enterprise server's Resource Definition Tables. If a Fileshare Server with that name is already registered on the network, an error is returned.
Specifies database-reference-file as the name of the database reference file that the Fileshare Server is to use.
Sets the transaction processing timeout, in seconds. If the server does not hear from its client in this period, and another client has requested access to records locked as part of the transaction, all files involved in the transaction are rolled back to their original state and all locks are removed.
The default timeout is 60 seconds. You can disable timeout by setting this to 0. The valid values are 0 through 99999999.
Specifies the maximum record size that the Fileshare Server processes in kilobytes. The valid values for record-size are 16 through 64. If you specify a value less than 16, the Fileshare Server uses a maximum record size of 16K. If you specify a value greater than 64, the Fileshare Server uses a maximum record size of 64K. if you do not include this option, the Fileshare Server uses a maximum record size of 64K. Setting a lower value than the default value reduces the amount of memory that the Fileshare Server needs to run.
Specifies cci-protocol as one of the CCI communications protocols that the Fileshare Server can use to receive communications from a Fileshare Client. Repeat this option for every communications protocol that you want to use to contact this Fileshare Server. Valid values for cci-protocol are:
If you do not specify any entries, the default is CCITC32.
Specifies the name of the Fileshare Server configuration file. Use this option only on the command line. When using this option, you must specify the required Fileshare Server options in the configuration file. If you do not specify a name for the configuration file, it defaults to fs.cfg in the Fileshare Server's current directory.
Names the password file used by this server. This option activates the Fileshare Password system. If you do not use this option, the Fileshare Server runs without security enabled.
Specifies that the Fileshare Server trace option is activated as soon as the Fileshare Server starts. The trace echoes to the screen and a file called fsscreen.lst in the Fileshare Server's current directory. This option seriously impacts the Fileshare Server's performance. Use it only for problem investigation.
Assume the file fs.cfg contains the following lines:
/s fsserv1 /cm ccitc32 /cm ccinb32 /pf serv1.pwd
If you enter the command:
Fileshare reads fs.cfg and starts a server named FSSERV1, with the TCP/IP and NetBIOS protocols enabled. It uses the file serv1.pwd for password security.
A Fileshare Server uses its password file to verify that a client enterprise server is entitled to access its files. Although Fileshare can run without a password file, you must use one if you want to apply any security through the Fileshare Server itself. This is strongly recommended, since Fileshare has access to all the files on your system.
The Fileshare Server uses its password file only when the enterprise server makes its first attempt at access (that is, when it starts up). File-level security is controlled by MSS itself, through the resource definitions you make.
The only way to maintain a password file is through this command line:
fs /pf pwd-filename options
Depending on the options you specify, Fileshare creates, modifies, or deletes pwd-filename. You can name the password file whatever you want, but it must correspond to the name you specify with the /pf option when configuring the Fileshare Server.
The options are as follows:
|/u username||The user name used by the enterprise server to log onto the server. (This must correspond to the value specified in the FS user name field in the enterprise server's SIT.) Can be up to 20 characters.|
|/pw password||The enterprise server's password. (This must correspond to what is specified in the FS password field in the enterprise server's SIT.) Can be up to 20 characters.|
|/e||Erases the specified user from the password file. You
must specify both the /u and /pw options on the same command line when you are
If you delete all the entries in the password file, the Fileshare server deletes it.
Note: Both passwords and user names are case-sensitive.
Assume no password file exists, and you want to create one with two entries. The following commands:
fs /pf fssecu.pwd /u mtoServ1 /pw fspass1 fs /pf fssecu.pwd /u mtoserv2 /pw fspass2
result in the password file fssecu.pwd being created, with entries for both mtoserv1 and mtoserv2. The mtoserv1/fspass1 and mtoserv2/fspass2 combinations must correspond to FS username and FS password fields in the enterprise servers' SIT.
To put password checking into effect on a Fileshare Server called FSSERV (for example), you must use the /pf option when starting it:
fs /s fsserv /cm ccitcp /pf fssecu.pwd
To disable mtoserv2's access to this Fileshare Server, use the following command:
fs /pf fssecu.pwd /e /u mtoserv2 /pw fspass2
If you now enter this command:
fs /pf fssecu.pwd /e /u mtoserv1 /pw fspass1
Fileshare removes the entry for mtoserv1, and deletes the file fssecu.pwd.
You can monitor the activity on a Fileshare Server by pressing F2 from the same session in which you started the server. This turns on Fileshare's trace facility, which displays file requests as they occur. For each request, you see the user identifier, opcode, requested filename, and file status bytes of the reply to the user.
You should use this facility only as a diagnostic aid, since it can degrade performance. Press F2 again to turn it off.
Before stopping a Fileshare Server, you must either stop all enterprise servers connected to it or make sure that all the files held on Fileshare servers are closed..
To stop a Fileshare Server locally, go to the session from which you started it, and press the Esc key. You see the prompt:
FS097-I Are you sure you wish to close the Fileshare Server? (Y/N)
Enter Y to continue the shutdown; enter any other key to let the server continue running.
If any database files are open when you reply Y, a second prompt appears:
FS111-I Warning - database files are still open Continue with the close (Y/N)?
If you enter Y, Fileshare closes all open files and shuts down. Enter any other key to cancel the shutdown.
If you have enabled Fileshare security, you must first give the enterprise server a Fileshare user name and password. These must be specified in the FS user name and FS password fields of the enterprise server's SIT. The enterprise server uses this user name and password combination to log on to all its Fileshare Servers. The combination must appear in the password file for each Fileshare server the enterprise server wants to access.
Next you should name the servers the enterprise server is to connect to. For data files you can have a choice of mechanisms for doing this:
For extrapartition transient data queues and intrapartition transient data and temporary storage queues you must name the servers in the RDF. If you do not explicitly name the servers in the RDF, and you have an entry in the fhredir.cfg file that simply names a server (/s servername), then all file requests that do not have an explicit Fileshare server defined will be redirected to the named Fileshare server. If you are running multiple enterprise servers this will cause file contention problems.
Finally, you must specify the protocols over which the region communicates with its servers. You do this in the client configuration file fhredir.cfg.
MSS consults the fhredir.cfg file whenever a region requires a resource from a server. You should not, therefore, change this file while any regions using servers defined by it are running.
For full details of fhredir.cfg entries and examples see the chapters Standard Operation and Configuration in your Fileshare Guide
The next section explains how to specify Fileshare servers in the RDF to enable Fileshare access.
Through the Resource Definition File, you can specify that any of the following resources reside on a Fileshare Server:
The FCT, DCT, and SIT contain fields for specifying the name of a Fileshare Server. If you fill one of these fields in, MSS looks for the resource on a Fileshare Server.
The FCT fields are on the FCT Details page of ESMAC.
The fields are:
|Fileshare Server||The Fileshare Server through which MSS accesses the file. This name must correspond to the name you give the server when you start it. This field is mandatory.|
|Override Filename||The filename Fileshare uses to find the file. This field is optional. it defaults to the name of the FCT entry.|
|File Path||The path Fileshare uses to find the file. This field is optional. It must be specified if the path defined by the Mainframe Express project does not exist on the Fileshare server machine.|
|File Extension||Specifies the file extension Fileshare uses to find the file. This
field is optional. For indexed files, this results in a filename and its index
component as follows:
The DCT fields are on the DCT Details page of ESMAC.
The fields are:
|Fileshare||The Fileshare Server through which MSS accesses the file. This name must correspond to the name you give the server when you start it. This field is mandatory.|
|File Name||The filename Fileshare uses to find the file. This field is optional. The name defaults to the name of the DCT entry|
|The path Fileshare uses to find the file. This field is optional. It must be specified if the path defined by the Mainframe Express project does not exist on the Fileshare server machine.|
|Extension||The file extension Fileshare uses to find the file. This field is
optional. For indexed files, this results in a filename and its index component
In the SIT, there are two sets of fields through which you specify Fileshare Servers for temporary storage and intrapartition transient data queues. You do not have to specify the Fileshare Server and path for each individual queue.
The SIT fields are on the SIT Details page of ESMAC.
There are four sets of the following fields, one each for:
The fields are:
|Fileshare Srvr||The Fileshare Server through which MSS accesses the file. This name must correspond to the name you give the server when you start it. This field is mandatory.|
|Path||The path Fileshare uses to find the file. This field is optional. It must be specified if the path defined by the Mainframe Express project does not exist on the Fileshare server machine.|
Copyright © 2008 Micro Focus (IP) Ltd. All rights reserved.