SNA DLC Problems - Connection fails - any ideas about how to fix?   

We have been using HIS2000 for 8 years on Win2K SP2 Server.

I have recently installed HIS2006 on a new Win2003SP1 Server.  While 
configuring the link services I noticed that there are two possibilities for 
DLC:

1.  Distributed, same as what we are using successfully today with HIS2000 
(creates SNAREM1)

2.  DLC 802.2  (creates SNADLC1)

The connection fails with both of these.

When I point the Connection to the distributed link service it fails but 
doesn't say why.

When I point the connection to the DLC 802.2 connection I get a warning 
message in the application event viewer.

Error message Source is SNA DLC Link Service
Error message Event ID is 230

Text is 

Remote station not responding to TEST commands

then it lists configuration information such as remote MAC address, Source 
SAP, and Destination SAP

The explanation is:

The remote station could not be contacted because it is not answering TEST 
or XID commands.
If the remote station is not responding to TEST commands:

 - the remote adapter address configured in Host Integration Server does not 
match the actual adapter address of the remote system.
 
 - the remote system is located across a bridge or router which is not 
forwarding DLC frames.

Which DLC Link service should I use - Distributed or DLC 802.2?

The remote MAC address is correct.  What does the error message mean by "the 
remote adapter address configured in HIS does not match the actual adapter 
address of the remote system"?  What is the "remote system adapter address if 
it is not the MAC address?

Our OSA board on the mainframe was reconfigured to permit DLC frames to be 
forwarded from the subnet where the new server is located.

So --

If I should be using the Distributed Link Service, any clues as to why the 
connection fails?

If I should be using DLC 802.2 Link Service, any explanations about the 
meaning of the error message and how to fix?

Finally, is there any documentation (manual or online site) that explains in 
technical detail how to configure and troubleshoot Microsoft SNA?  On MSDN I 
found a few high level explanations about how to fill in the Link Service 
panel but nothing in enough detail to deal with issues like the above.

Thanks for your help.

date: Tue, 8 Apr 2008 07:35:04 -0700   author:   HISUser

Re: SNA DLC Problems - Connection fails - any ideas about how to fix?   

Can you describe the setup of your current 8-year old setup?  The fact that 
you're using a distributed link service means that you must have at least two 
HIS servers configured.

 When you install the distributed link service, what it does is act as a proxy 
for a remote HIS server to connect to the mainframe.  e.g. if you install a DLS 
DLC service on server A, then server A provides the physical DLC connection to 
the mainframe, and you then have server(s) B/C/D/whatever that will connect via 
the link service(s) on server A.
 
 Taking the simpler configuration of just a normal 802.2 local DLC link service, 
is the new HIS server actually on the same LAN/VLAN as a working HIS server?  
DLC protocol isn't routable in the tcp-ip sense, so, without the aid of a 
tunneling option such as a DLS/W router, it has to be on the same broadcast 
segment (LAN) as the mainframe network adapter that it's connecting to.
 
 Unfortunately there are no simple step by step instructions for setting up a 
connection because there are just too many variables and some network, mainframe 
and environment knowledge is needed.
 
 Is there no-one at the site familiar with the mainframe 
configuration/connectivity?
 
> We have been using HIS2000 for 8 years on Win2K SP2 Server.
> 
> I have recently installed HIS2006 on a new Win2003SP1 Server.  While 
> configuring the link services I noticed that there are two possibilities for 
> DLC:
> 
> 1.  Distributed, same as what we are using successfully today with HIS2000 
> (creates SNAREM1)
> 
> 2.  DLC 802.2  (creates SNADLC1)

 Neil Pike.  Protech Computing Ltd
 Microsoft SNA/HIS MVP
 https://mvp.support.microsoft.com/profile=BE66F0D8-9D78-47EF-840A-08E6D8522A2D
 http://www.linkedin.com/in/neilpike

date: Tue, 08 Apr 2008 17:34:37 +0100   author:   Neil Pike