Configuring SNA on Windows

Perform these steps to configure a SNA server connection on Windows.

You can choose from two principal topologies:
  • Full Communications Server installed on the local computer (full SNA stack).
  • Communications Server Remote API Client (split SNA stack).
You need to install and configure an SNA communications server, such as IBM® Communications Server. To set up communication over SNA define the following settings in your SNA communications product.
  • The local node characteristics that are common to all SNA users at the workstation.
  • A local logical unit (LU) for the CICS® Transaction Gateway.
  • A partner logical unit for each CICS server with which the CICS Transaction Gateway will communicate. This is not required if you are using APPN and specify the actual fully qualified partner LU names in the CICS TG configuration file.
  • One or more modes to specify sets of session properties that are used in binding SNA sessions.
  • A transaction program (TP) for the CRSR transaction. You need this if the following apply:
    • The CICS servers support terminal emulation, and
    • You require automatic transaction initiation (ATI) against the CICS Transaction Gateway terminals.

The terms used to describe these definitions vary with the product used to provide support. The terms used above are the ones used by IBM Communications Server.

SNA connections support data synchronization levels (sync levels) 0 and 1.

More information on connecting CICS Transaction Gateway to CICS Transaction Server for z/OS®, using Host Integration Server, is in CICS Transaction Gateway V5 The WebSphere® Connector for CICS Redbook.