Overview of the Implementation Process

To enable TCP/IP hosts to run OSI applications, perform the following steps (which are described in detail in the subsections that follow):

  1. Verify that the appropriate software is installed on your system. Refer to the ClearPath MCP Software Migration Guide for your software release details. Consult the release letter for specific software level requirements.

  2. Make a conceptual drawing of your existing network. It is assumed that you have already configured your TCP/IP network using the NW commands.

    • You must create two OSI initialization files for each TCP/IP host that you want to enable to run OSI applications.

    • The OSI endpoint initialization file should contain a unique ADD OSI ENDPOINT NAME command for each OSI application (one endpoint for the local application and in some cases one endpoint for the remote application) that you want to run on the TCP/IP host. If you are an existing OSI user who has already created an OSI endpoint initialization file (to identify the location of the applications in your network), you do not have to make any further modifications to this file to run those applications over a TCP/IP network.

      Each ADD OSI ENDPOINT NAME command is made up of a combination of the following application endpoint attributes:

      • File Name

      • Host Name

      • Name

      • Application Group

      • NSAP Address **

      • Presentation Selector **

      • Session Selector **

      • Transport Selector **

        ** See Note for details.

        For a complete description of each of the preceding attributes, refer to the Networking Attributes Data Dictionary Help.

      Note: When configuring an application endpoint (other than the OSI TP application) on a non-ClearPath MCP system, you must provide values for those attributes that are shown with an asterisk (**). When configuring OSI TP, you are required to identify file names and endpoints for the local applications within your network. However, with the support of settable remote OSI addresses at the Port File Interface, you are not required to generate remote destination system network information.For additional information on identifying OSI application endpoints, refer to the OSI Software Implementation Guide, Volume 1: Planning.

      • The OSI initialization file should contain the OSI + command to initialize the appropriate parts of the OSI software.

        The initialization file can also optionally contain ADD NETWORK ADDRESS PAIR commands that map application hosts' IP addresses to the hosts' OSI NSAP addresses. The ADD NETWORK ADDRESS PAIR command also allows a domain name to be substituted for or entered in addition to the IP address.

        The ADD NETWORK ADDRESS PAIR commands are now optional because starting with SSR 45.1, you can specify an IP address inside of an OSI NSAP address. This eliminates the need to configure Network Address Pairs. For details on specifying an IP address inside an OSI NSAP address, see Associating OSI and TCP/IP Addresses.

        For specific details on how to create the appropriate OSI initialization files, see Configuring OSI-TCP/IP Address Pairs.

  3. Print the report that contains a description of the network OSI-TCP/IP network address pairing information.

  4. Generate initialization files by manually editing the files. The network configuration and status database will be updated to reflect your network definition. Sample OSI initialization files are provided at the end of this section.

Prev  Up  Next
Functional Overview  Home  Initializing the OSI Software on the TCP/IP Host