Support for Communications Server

If you are connecting to an IBM® Communications Server for Windows® by using the Communications Server client or installing on the Communications Server machine, configure Personal Communications to use the SNA API client interface.

The API client interface lets you make the following attachments:
  • 3270 emulation

    LUA - LU 0, 1, 2 or 3 via the WinRUI interface. This lets you have normal display or printer sessions.

  • APPC3270

    This provides 3270 display sessions (not printer) over an LU 6.2 connection to the host.

  • 5250 emulation

    This provides 5250 display and printer sessions through APPC.

Note:
You must first install the API client, or the Communications Server for Windows® 5.0 or later client. Personal Communications now packages IBM Remote API Client under admin\ibm_rapic in the Docs_Admin_Aids package.
On Windows (64-bit) operating system, the products should be installed in the following order for Personal Communications to interact with Remote API Client.
  1. Microsoft Visual C++ 2008 SP1 Redistributable Package (x86)
  2. Remote API Client v7.0
  3. IBM Personal Communications
Two interfaces are supported:
  • Communications Server for Windows®

    You can run Personal Communications on a Communications Server; it uses the Communications Server protocol stack to connect to the host.

  • Client for Communications Server for Windows®

    For client workstations, Communications Server has a client that communicates with the server and provides an interface that Personal Communications can use. The client must be installed on your workstation before you install Personal Communications.

Note:
You cannot install the Personal Communications SNA protocol drivers if you intend to use the API Client interface. You can, however, use the non-SNA attachment types, which include HPO, Home3270, TN3270, and IPX/SPX.