Seeker
Guest
|
 Posted:
Fri Feb 18, 2005 4:48 am Post subject:
Help! The basics.. |
|
|
I have been tasked with getting an SNA connection established. This is
completely new to be and I am entirely out of my element. I'm an IP guy.
I have a bunch of documentation with SNA definitions such as PU, ILU
NETID, yet I have no frame of reference for what these mean. I've
looked at a couple of whitepapers but they seem to be written with the
assumptions that the reader has a fundamental understanding of how this
works.
I do know that the network is frame relay to a Cisco router and out the
other side of the router is Ethernet. But there is no IP; it's pure SNA.
I have installed Host Integration Server 2000 with SP1 on a Windows 2003
server, along with software called Connect:Direct. What I lack is a
fundamental understanding of what it takes to establish a successful
link with a remote host. If this was IP, for example, I would need the
IP, gateway info, etc. What's the equivalent?
ATT says the physical link is OK, now I need to move to the next step.
Can someone give me some basic pointers or point me in the direction of
some starter docs/FAQs so I can at least begin to understand the
terminology? All help would be greatly appreciated. |
|
Neil Pike
Guest
|
| Posted:
Fri Feb 18, 2005 2:24 pm Post subject:
Re: Help! The basics.. |
|
|
Seeker,
Unfortunately you are going to struggle and a newsgroup isn't the ideal medium
to help.
You need to :-
1. Install/configure the SDLC card that you're using to make the underlying
connection. (I assume SDLC as you're talking Frame Relay)
2. Create a link service in HIS for the SDLC card
3. Create a connection in HIS over that SDLC card. This will want stuff like
the Network Name and Control Point Name defined.
4. Create a remote LU over the connection for Connect:Direct. This will be
the ILU name that the mainframe guys will give you.
5. Perform an APPC test using the HIS tools. Once all that works you can
configure Connect:Direct.
Why not ask SterlingCommerce for a consultant to help you do all this as long
as they can send someone along who is SNA aware.
If you're in the UK drop me an email if you're prepared to pay for
consultancy/training/doing it (and can wait a few weeks)....
| Quote: | I have been tasked with getting an SNA connection established. This is
completely new to be and I am entirely out of my element. I'm an IP guy.
I have a bunch of documentation with SNA definitions such as PU, ILU
NETID, yet I have no frame of reference for what these mean. I've
looked at a couple of whitepapers but they seem to be written with the
assumptions that the reader has a fundamental understanding of how this
works.
I do know that the network is frame relay to a Cisco router and out the
other side of the router is Ethernet. But there is no IP; it's pure SNA.
I have installed Host Integration Server 2000 with SP1 on a Windows 2003
server, along with software called Connect:Direct. What I lack is a
fundamental understanding of what it takes to establish a successful
link with a remote host. If this was IP, for example, I would need the
IP, gateway info, etc. What's the equivalent?
ATT says the physical link is OK, now I need to move to the next step.
Can someone give me some basic pointers or point me in the direction of
some starter docs/FAQs so I can at least begin to understand the
terminology? All help would be greatly appreciated.
|
Neil Pike. Protech Computing Ltd |
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in