Article ID: 939193 - View products that this article applies to.
This article describes how to set up the connection and the logical units (LU) for an Advanced Program-to-Program (APPC) application. This article describes how to do this when you use the "IP data link connection" (IP-DLC) link service in Microsoft Host Integration Server 2006 (and later) together with dependent APPC logical units.
Consider the following scenario:
When you use the IP-DLC link service to establish a connection between an APPC application and a mainframe computer, you must have two connections if you are using dependent APPC logical units. You must have a peer-system connection and a host-system connection.
When you use the IP-DLC link service to establish a connection to a mainframe computer that uses independent APPC logical units, you must use a peer-system connection to associate the remote logical units with the independent APPC logical units. In addition, local independent APPC logical units have no association with the host-system connection or with the peer-system connection.
Note The dependent local APPC logical units have to be defined on a host-system connection. The dependent local APPC logical units cannot be defined on a peer-system connection. Peer-system connections do not represent a physical link to a remote node. The peer-system connection represents a logical connection between the PU2.1 core Microsoft Host Integration Server node (Snaservr.exe) and the IP-DLC link service. This logical peer-system connection is required by the LU 6.2 protocol.
Step 1: Create the peer-system connectionUse one of the following methods to create the peer-system connection.
Important You must create the peer-system connection before you create the host-system connection.
Method 1: Create the peer-system connection manually
Method 2: Create the peer-system connection by using the Mainframe APPC/LU6.2 Wizard
Step 2: Create the host-system connectionUse one of the following methods to create the host-system connection.
Method 1: Create the host-system connection manuallyFor more information about how to create the host system connection manually, visit the following MSDN website:
Method 2: Create the host-system connection by using the 3270 Emulation Configuration Wizard
Step 3: Create a remote APPC LU
For information about how to create a Remote APPC LU, visit the following MSDN website:
In addition to the steps that are described in the documentation, you have to select the peer IP-DLC connection that was previously created from the Connection list.
Step 4: Create a dependent local APPC LU
For information about how to create a remote local APPC LU, visit the following MSDN website:
Note In this case, you would select Dependent as the LU 6.2 Type.
The following parameters must be configured when a dependent LU 6.2 type is selected:
Step 5: Associating the Remote APPC LU to the Host system connection
You have to associate the Remote APPC LU to the Host system connection , especially if the mainframe application will be starting conversations to the APPC application on the Windows systems.
Use the Snacfg.exe command-line configuration utility to associate the remote APPC LU with the Host IP-DLC connection. When the remote APPC LU is associated with the Host IP-DLC connection, the SNA Server service can successfully process incoming BIND requests over IP-DLC connections by using dependent APPC LUs.
Commands in the Snacfg.exe command prompt utility
The following is a list of the commands in the Snacfg.exe command prompt utility. You can use these commands to create and to assign connections to remote LUs.
Note If you are using HIS 2006 without Service Pack 1 installed, you may encounter the problem that is described in the following article in the Microsoft Knowledge Base:
(http://support.microsoft.com/default.aspx?scid=kb;EN-US;947858)FIX: Event 17 occurs when a mainframe application tries to invoke an APPC application over an IP-DLC connection by using a dependent LU 6.2 logical unit
For more information about how to manage IP-DLC link service connections, visit the following MSDN website: