WSCON connection (new)

jvikram253 · New User Joined: 03 Dec 2010 Posts: 2 Location: Hyderabad

What is the final solutions for this problem ... i am facing the same problem ... what is the solution .. ?

can any one please help me on this issue .. ?

Originally attached to this topic.

Bill Woodger · Posted: Tue Oct 09, 2012 7:39 pm

Please don't tailgate an old topic. Ask your question, giving any information that you feel we are likely to need, and, if you think useful, linking to one or more other topics.

jvikram253 · New User Joined: 03 Dec 2010 Posts: 2 Location: Hyderabad

I am facing below error when trying to connect mainframe to WSA .

ISPO921 Unable to communicate with workstation at the specified network
address. Probable causes: (1) the specified network address does not
exist or cannot be accessed; (2) if specified, the SNA network address
does not support APPC communication. Network data:'TCP/IP CONNECT RC=60
..

And when i am tryng to ping PC Ip address from Mainframe .. it showing

Timeout error ..

I don't know what is the cause and how i need to resolve this error ..

Can any one help me ?

enrico-sorichetti · Posted: Tue Oct 09, 2012 8:14 pm

dick scherrer · Posted: Tue Oct 09, 2012 8:59 pm

Hello,

You have proved that you have an ip address that will not work.

Now you need to work with your network support people to find out how to correct this or learn a new ip address.

Where did you learn of the problem ip address?

Pedro · Posted: Tue Oct 09, 2012 9:22 pm

James Halley · New User Joined: 11 Apr 2012 Posts: 18 Location: USA

First verify in "Options ... Information" in the Workstation Agent that the Status is "TCP Initialized, 0 Session(s) are active." If this message is not displayed, verify that "Enable TCP/IP" has a checkmark by it. The Workstation Agent must be restarted for changes to take effect.

If the Status is still not "TCP Initialized", I suspect a Winsock.dll problem. Search the Windows folder and subfolders for Winsock.dll and try putting the path to it in the "Windows socket library path" field in Workstation Agent option "Set Winsock path". Again, the WSA must be restarted from changes to take effect. If you find multiple Winsock.dll in different folders, try each path, one at a time.

If you happen to be connecting through a VPN, the IP address you will use on the WSCON panel will be the IP address of the Network Connect Adapter instead of the IP address of the Local Area Connection as shown when an IPCONFIG command is executed in a Windows Command window.

If no one else at your location is able to establish a WSCON connection with the WSA, the problem could be that one or more firewalls must be modified to allow your mainframe ISPF session to "contact" your PC when you perform the ISPF WSCON command. As others have said, you will then need assistance from your network people.

Stefan · Posted: Wed Oct 10, 2012 1:15 pm

don.leahy · Posted: Wed Oct 10, 2012 6:13 pm

Unfortunately, ZIPADDR can be foiled by session managers such as MAI or Supersession.

What works best in our installation (we use MAI) is to specify the workstation's network name in the IP address field. The name is tied to the workstation's physical inventory number and is therefore stable. The name is translated (somewhere) into the current ip address for the workstation.