PreviousFileshare on UNIX Error HandlingNext

Chapter 8: Communications

The Fileshare Client(s) and Fileshare Server(s) communicate using the Common Communications Interface (CCI).

8.1 Overview

On Windows NT, Windows 95 and UNIX, Fileshare defaults to the TCP/IP (CCITCP) protocol.

See your online help file for details on TCP/IP - look under TCP/IP in the help file index.

See your online book Communications for details on TCP/IP.

When using CCITCP, you can either use CCITCP Direct or the following process. For details of CCITCP Direct, please refer:

The Fileshare Client and the Fileshare Server must have access to a registration process called ccitcp2. This process can be running on any machine that the Fileshare Client and Fileshare Server can contact. The ccitcp2 process sets up the initial connection between the Fileshare Client and Fileshare Server. You must set the environment variable CCITCP2 to the host name of the machine where the ccitcp2 process is running. If you do not set the environment variable, CCITCP assumes that ccitcp2 is running on the local machine. The Fileshare Client and the Fileshare Server must register with the same ccitcp2 process in order to communicate with each other.

For example, consider the situation where the Fileshare Server and the Fileshare Client are running on different machines and the ccitcp2 process is running on the same machine as the Fileshare Server. The environment variable CCITCP2 does not have to be set on the machine running the Fileshare Server. However, it has to be set on the machine running the Fileshare Client to the TCP/IP host name of the machine where the Fileshare Server (and ccitcp2) process is running.

A Fileshare Server can use several communication protocols concurrently, enabling it to communicate with a number of Fileshare Clients that do not all use the same protocol.

When you invoke a Fileshare Server, you need to specify the communications protocols it supports, using the /cm option in the Fileshare configuration file. Valid values for /cm are:


When running the Fileshare Server and Fileshare Client on the same UNIX machine, use the Named Pipes protocol for UNIX (CCINAMPU) as this provides significantly better performance than CCITCP.

8.2 CCI Trace

CCI Trace enables all the messages sent by CCI to be logged to a file. This can help in tracking down and debugging problems related to communications. To activate CCI Trace add:

/tr cci

to the Fileshare Server configuration file.

To prevent unauthorized access to the CCI Trace information, you are prompted for the supervisor password when you invoke a Fileshare Server with CCI Trace enabled. (The supervisor password is that specified for the user-ID FSVIEW in the password file so you must specify the appropriate password file when you start the Fileshare Server.) If the password is accepted, CCI Trace is enabled and a second prompt asks if CCI Trace should be activated immediately or not.

CCI Trace can be toggled on and off using the F3 key.

The CCI trace options are specified via the CCITRACE environment variable.

Copyright © 1998 Micro Focus Limited. All rights reserved.
This document and the proprietary marks and names used herein are protected by international law.
PreviousFileshare on UNIX Error HandlingNext