PreviousCCINAMPU Configuration CCI TraceNext

Chapter 7: Application Configuration

CCI is used by a variety of Micro Focus applications. This chapter describes how each of these applications is configured to use CCI for each supported network protocol.

7.1 CCI Configuration for the Mainframe Access Product Suite

The section CCI Configuration in the protocol specific CCI configuration for Applications section below, describes the prerequisite CCI configuration for each protocol, which must be completed prior to its successful use with any application, including the Mainframe Access product suite.

Once the system has been configured correctly for use with CCI the following CCI parameters in Mainframe Access must be configured as described below:

Select the CCI protocol to use.

Specify the Standard server name of the Fileshare Server, which is Server Name as described in the section Server Name guide for the CCI Configuration being used.

Specify the Standard server machine parms, which is Machine Name as described in the section Machine Name guide for the CCI Configuration being used.

7.1.1 An example of using APPC with Mainframe Access

The Partner LU Name portion of the Standard Server Name (before the period) for Mainframe Access must match the Partner LU Name, also known as the APPLID, of the Fileshare task running on the host system. The Transaction Program Name portion of the Standard Server Name for Mainframe Access (following the period) should be four characters long with 'F' as the fourth character.

In the example below the mainframe Server Name used is FILESHR2.BETF.

7.1.2 An example of using TCP/IP with Mainframe Access

In the example below the mainframe Server Name used is FILESHR2.MYSERVER.

If the mainframe connection supports direct connection, then the Standard Server Machine Parameter needs to be filled out. In this example the TCP hostname of the mainframe is server_hostname, and the fixed listening port is 3000. If the connection is direct then the Standard Server Name is optional.

7.2 CCI Configuration for Fileshare

7.2.1 Generic Fileshare Configuration

This may also be described as Record Level I/O especially when the Fileshare Server is running on a mainframe system.

The section CCI Configuration in the protocol specific CCI Configuration for Applications section below, describes the prerequisite CCI configuration for each protocol, which must be completed prior to its successful use with Fileshare.

Once the underlying protocol support has been configured correctly for use with CCI the following CCI parameters in Fileshare must be configured as described below:

For example, in FHREDIR.CFG:
/MA <Machine Name> /S <Server Name>

Note that Fileshare has a limit of 64 characters for the /MA parameter.

7.2.1.1 Example FHREDIR.CFG Configuration File for Use with APPC

/MA CCILLU01.#INTER /S FILESHR2.BETF
/CM CCIAPPC /S FILESHR2.BETF
/F SYSOUT* /S FILESHR2.BETF

Fileshare can be used with multiple CCI protocols simultaneously, by specifying different CCI communications modules for each Fileshare Server, and by specifying which files reside on which server.

7.2.1.2 Example FHREDIR.CFG Configuration File for Use with Multiple CCI Modules

/MA CCILLU01.#INTER /S FILESHR2.BETF
/CM CCIAPPC /S FILESHR2.BETF
/F SYSOUT* /S FILESHR2.BETF
/CM CCINETB /S FILESHR1
/F MYFILE /S FILESHR1

Fileshare also has the capability to specify a default protocol to be used whenever a file location is not specified directly in the configuration file.

7.2.1.3 Example FHREDIR.CFG Configuration File for Use with Default CCI Modules

/CM CCITCP
/MA 32CC461,1 /S FILESHR2
/CM CCIIPX /S FILESHR2
/F FileName /S FILESHR2

This configuration file works in the following manner:

7.2.2 CCI Configuration for Applications

Each application which uses CCI has different configuration mechanism, however the details of the CCI communications requirements are the same for all applications calling the same CCI module. These CCI configuration requirements are detailed in the sections in the table below. For details on the Protocol specific CCI Configuration, Server Name and Machine Name guidelines, please click on the appropriate item in the CCI configuration table below.

7.2.2.1 CCI Configuration Information by Protocol

For normal use of CCI protocol modules, including CCITCP using the CCITCP2 service registration daemon, please use the links in the following table to help configuration of the relevant environments. For details of using CCITCP without using CCITCP2, please see the section below.

All of the protocol modules listed in the table below are available on Windows 32-bit operating systems except CCINAMPU. CCITCP and CCINAMPU are available on the UNIX operating system.

CCIAPPC CCI Configuration Server Name guide Machine Name guide
CCIIPX CCI Configuration Server Name guide Machine Name guide
CCINETB CCI Configuration Server Name guide Machine Name guide
CCITCP CCI Configuration Server Name guide Machine Name guide
CCINAMPU CCI Configuration Server Name guide Machine Name guide
7.2.2.1.1 Advanced Use of CCITCP Without Using CCITCP2

It is possible to use CCITCP without having a CCITCP2 daemon present (see Direct Connection and Starting Servers on Fixed Ports on why you may want to do this). This method may be used for all applications which use CCITCP.

Example:

To start a Fileshare Server using a fixed TCP port, on the machine whose TCP hostname is server_hostname, enter the following command:

fs /s server_name,MFPORT:3000 /cm CCITCP

where:

server_name is the name of the Fileshare Server
,MFPORT:3000 is used by CCITCP to ensure that the server listens for incoming calls on port 3000

Once you have configured the Fileshare Server to use a specific port, you can get a Fileshare Client to connect to the server on this port number using the /MA parameter in the FHREDIR.CFG file to specify a Machine Name of the form:

/MA MFNODE:server_hostname,MFPORT:3000 /S server_name

The FHREDIR.CFG will look like this:

/S server_name
/CM ccitcp
/MA MFNODE:server_hostname,MFPORT:3000 /S server_name


Copyright © 2000 MERANT International Limited. All rights reserved.
This document and the proprietary marks and names used herein are protected by international law.

PreviousCCINAMPU Configuration CCI TraceNext