Configure Multiple SNA Servers to Use Single Distributed Link

Last reviewed: April 17, 1997
Article ID: Q155541

The information in this article applies to:
  • Microsoft SNA Server for Windows NT versions 2.11 Service Pack 1 and 3.0

SUMMARY

The distributed link service is a feature added in Service Pack 1 for Microsoft SNA Server version 2.11 that allows SNA Servers to be deployed in a new distributed model, which combines the benefits of the branch and central models of deployment. For details on the distributed model and link service, please see the SNA Open Gateway Architecture (SOGA) document.

Information on SOGA can be found in the following locations:

   http://www.microsoft.com/corpinfo/press/1995/95dec/sogapr.htm
   http://www.microsoft.com/sna/soga.htm

MORE INFORMATION

The original SOGA document indicated that a distributed link service could not be used by multiple SNA Servers simultaneously. The intent of this was to prevent you from trying to configure a distributed link service on the local SNA Server for a local connection. A distributed link service can only be used by remote SNA Servers. However, it is possible to have multiple remote systems using a single distributed link service.

To do this, each remote system must be assigned a unique Service Access Point (SAP). SNA SAPs must be a hexadecimal multiple of four and must be defined on both ends of the connection. Assuming you had three remote systems you intended to use the distributed link service, you would use SAPs '04', '08', and '0C'.

The SAPs are defined in the communications line description on the AS/400. Your AS/400 administrator can help you with this. Using the example of three systems, you would add '08' and '0C' to the SAPs already defined on the line. SAP '04' is defined by default.

To set the appropriate SAPs do the following:

For SNA Server 2.x:

- In SNA Server Admin, focus on the Connection, then select the Setup button, and then select the Advanced button. Change the Remote SAP Address to the value you have assigned to that computer. Again, from the three computers example, '04' for the first computer, '08' for the second, and

'0C' for
the third."

For SNA Server 3.x:

- In SNA Server Manager, go to the connection properties page for the connection in question and select the Address tab.


Additional query words: sna prodsna
Keywords : kbnetwork ntnetserv snadls
Version : 2.11.sp1 3.0
Platform : NT WINDOWS


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 17, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.