How to set up the connection and the logical units for an APPC application when you use the IP-DLC link service in Host Integration Server together with dependent APPC logical units

Article translations Article translations
Article ID: 939193 - View products that this article applies to.
Expand all | Collapse all

On This Page

INTRODUCTION

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.

MORE INFORMATION

Consider the following scenario:
  • You use the IP-DLC link service to create a connection.
  • To do this, you use a remote end that is configured to use a host system.
  • Then, you configure a remote logical unit for the APPC application.
In this scenario, no connections are listed in the Connections list in the Remote APPC LU Properties dialog box.

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 connection

Use 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

  1. In SNA Manager, expand the server on which you want to create the connection, and then expand SNA Service.
  2. Right-click Connections, point to New, and then click the type of connection (IP-DLC…) to be created
  3. Configure a connection name, and then choose the IP-DLC link service to use for the connection (for example, SNAIP1).
  4. In the Remote end drop-down list, select Peer system.

    Note If Remote end = Peer system when you are using an IP-DLC link service, the connection will be used only for independent LU 6.2 (APPC) sessions. Setting Remote end = Peer system disables the Allowed directions and Activation options. Additionally, the remaining connection configuration options under the following tabs tabs will also be disabled:
    • Address
    • System Identification
    • IP DLC
  5. Click OK.
  6. Save the configuration to save the changes.

Method 2: Create the peer-system connection by using the Mainframe APPC/LU6.2 Wizard

  1. Click Start, click All Programs, click Microsoft Host Integration Server 2006, and then click SNA Manager.
  2. Expand Microsoft SNA Manager, expand Servers, expand the server name, right-click SNA Service, click All Tasks, and then click Mainframe APPC/LU6.2 Wizard.
  3. On the Welcome page, click Next.
  4. Click Third-party or custom APPC application, and then click Next.
  5. Select the host environment type that you want to use, and then click Next.
  6. In the Select the SNA Service to configure list, select the server that you want to use, and then click Next.
  7. Select an existing connection or a new connection, and then click Next.
  8. On the Worksheet page, click Worksheets to view the worksheets. When you finish viewing the worksheets, click Next.
  9. In the Local LU name box, type the local logical unit name, and then click Next.
  10. On the SyncPoint Support page, click Next.
  11. In the Remote LU name text box, type the remote logical unit name, and then click Next.
  12. On the Mode page, select an existing mode or new mode, and then click Next.
  13. Click Finish.

Step 2: Create the host-system connection

Use one of the following methods to create the host-system connection.

Method 1: Create the host-system connection manually

 For more information about how to create the host system connection manually, visit the following MSDN website: 
http://msdn2.microsoft.com/en-us/library/aa771047.aspx

Method 2: Create the host-system connection by using the 3270 Emulation Configuration Wizard

  1. Click Start, click All Programs, click Microsoft Host Integration Server 2006, and then click SNA Manager.
  2. Expand Microsoft SNA Manager, expand Servers, expand the server name, right-click SNA Service, click All Tasks, and then click 3270 Wizard.
  3. On the Welcome page, click Next.
  4. Select the server that you want to use, and then click Next.
  5. In the Name box, type the name of the connection, and then click Next.
  6. Select the link service that the connection will use, and then click Next.
  7. Type the local node ID information in the following boxes:
    • IDBLK
    • IDNUM
    • Network Name
    • Control Point
    Then, click Next.
  8. In the PU address (PUADDR) box, enter the physical unit (PU) address, and then click Next.
  9. On the Creating LUs page, enter the logical unit information.

    Note You can change default name of the base logical unit, the starting logical unit number, and the number of logical units that you want to create. Click Next when you are finished.
  10. Add the users or the groups that require mainframe user rights. Add these users to the Added members list, and then click Next.
  11. Click Finish to create the connection.


Step 3: Create a remote APPC LU


For information about how to create a Remote APPC LU, visit the following MSDN website:
http://msdn.microsoft.com/en-us/library/aa744348.aspx

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:

http://msdn.microsoft.com/en-us/library/aa705746.aspx

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:
  • LU number. This is the LOCADDR parameter that is defined in the PU definition in VTAM for this LU.
  • Connection. Select the Host system connection that was created previously. The Connection list does not list any Peer system IP-DLC connections. 

    Note The Mainframe APPC/LU6.2 Wizard does not correctly handle creating dependent local APPC LUs over IP-DLC connections. Creating dependent local APPC LUs manually is recommended.

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.
  • You can use the following command to create a remote LU (if you have not already created one in SNA Manager) and then assign the LU to a connection: 
    snacfg #com.cfg appcrlu remote LU name  /add /connection: connection name /netname: NETNAME value /luname: remote LU name /uninterpname: remote LU name  

    In this command, replace the placeholders as follows:
    • Replace the placeholder remote LU name with the name of the remote LU that is defined in SNA Server Manager.
    • Replace the placeholder connection name with the name of the Host connection that is defined in SNA Server Manager.
    • Replace theplaceholder NETNAME value with the Network Name value that is defined in the Virtual Telecommunications Access Method (VTAM).

  • You can use the following command to assign the connection to a remote APPC LU that you already created in SNA Manager: 
    snacfg #com.cfg appcrlu remote LU name /connection: connection name 

    In this command, replace the placeholders as follows:
    • Replace the placeholder remote LU name with the name of the remote LU that is defined in SNA Server Manager.
    • Replace the placeholder connection name with the name of the connection that is defined in SNA Server Manager.


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:

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

REFERENCES

For more information about how to manage IP-DLC link service connections, visit the following MSDN website:
http://msdn2.microsoft.com/en-us/library/aa770805.aspx

Properties

Article ID: 939193 - Last Review: February 17, 2011 - Revision: 2.0
APPLIES TO
  • Microsoft Host Integration Server 2006
Keywords: 
kbpubtypekc kbinfo kbhowto KB939193

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com