Portal | Manuals | References | Downloads | Info | Programs | JCLs | Master the Mainframes
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Usergroups Profile Log in to check your private messages Log in
 

 

WSCON connection (new)

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> TSO/ISPF
View previous topic :: :: View next topic  
Author Message
jvikram253

New User


Joined: 03 Dec 2010
Posts: 2
Location: Hyderabad

PostPosted: Tue Oct 09, 2012 6:54 pm    Post subject: WSCON connection (new)
Reply with quote

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.
Back to top
View user's profile Send private message

Bill Woodger

DFSORT Moderator


Joined: 09 Mar 2011
Posts: 7236

PostPosted: Tue Oct 09, 2012 7:39 pm    Post subject: Reply to: WSCON connection (new)
Reply with quote

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.
Back to top
View user's profile Send private message
jvikram253

New User


Joined: 03 Dec 2010
Posts: 2
Location: Hyderabad

PostPosted: Tue Oct 09, 2012 8:11 pm    Post subject:
Reply with quote

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 ?
Back to top
View user's profile Send private message
enrico-sorichetti

Global Moderator


Joined: 14 Mar 2007
Posts: 10203
Location: italy

PostPosted: Tue Oct 09, 2012 8:14 pm    Post subject: Reply to: WSCON connection (new)
Reply with quote

Quote:
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 ?


we do not belong to Your organization,
telling You what to do will like rewriting a few pages of the relevant manuals

if You have the business need and the proper authorizations Your support will be glad to help You solve the whole problem

otherwise ( no proper authorization ) You are attempting something that You should not
Back to top
View user's profile Send private message
dick scherrer

Site Director


Joined: 23 Nov 2006
Posts: 19270
Location: Inside the Matrix

PostPosted: Tue Oct 09, 2012 8:59 pm    Post subject:
Reply with quote

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?
Back to top
View user's profile Send private message
Pedro

Senior Member


Joined: 01 Sep 2006
Posts: 2019
Location: Silicon Valley

PostPosted: Tue Oct 09, 2012 9:22 pm    Post subject: Reply to: WSCON connection (new)
Reply with quote

Code:
'TCP/IP CONNECT RC=60

I also get RC=60 by merely using the wrong TCP/IP address. And it changes because we have dynamic TCP/IP addressing*, so it might work one day, but not the next. I have to figure out my current IP address when I want to start WSCON.

*Sorry if my terminology is not right... I am not a network guy.

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

and
Quote:
Probable causes: (1) the specified network address does not
exist or cannot be accessed;


Likely, you have the wrong address. Assuming Windows, open a DOS command prompt window and issue:

Code:
HOSTNAME

and given the host name, for example it might be 'myhost', issue:
Code:

PING myhost


PING should give you the numerical TCP/IP address of your workstation. Hopefully, it is the same one that you tried to connect to WSCON with.
Back to top
View user's profile Send private message
James Halley

New User


Joined: 11 Apr 2012
Posts: 17
Location: USA

PostPosted: Tue Oct 09, 2012 10:21 pm    Post subject:
Reply with quote

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.
Back to top
View user's profile Send private message
Stefan

Active User


Joined: 12 Jan 2006
Posts: 110
Location: Germany

PostPosted: Wed Oct 10, 2012 1:15 pm    Post subject: Re: Reply to: WSCON connection (new)
Reply with quote

Pedro wrote:
I have to figure out my current IP address when I want to start WSCON.

That's not really necessary.
When issuing WSCON you have to enter the IP address of the workstation. But you don't have to know it by heart. Read the text of the tutorial panel when pressing F1 with the cursor on the entry field:
Code:
The TCP/IP address of the workstation in which the GUI
display or connection should be made.  The TCP/IP Address
prompt is point and shoot text, and if selected, a popup
window will be displayed containing the last five TCP/IP
addresses that were saved in the system profile.

A value of '*' will be overlayed with system variable
ZIPADDR. ZIPADDR is the TCP/IP address of the currently
connected TN3270 workstation.

So just use * or select from the list when pointing to the field prompt.

By the way: ISPF WSA uses by default port 15993. This port number has to be allowed by all firewalls on your network path from your workstation to the mainframe.

Hope that helps
Back to top
View user's profile Send private message
don.leahy

Active Member


Joined: 06 Jul 2010
Posts: 642
Location: Whitby, ON, Canada

PostPosted: Wed Oct 10, 2012 6:13 pm    Post subject:
Reply with quote

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.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> TSO/ISPF All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts why we just define Connection but no ... zos5415 CICS 1 Fri Dec 13, 2013 11:12 am
No new posts Connection between 2 panels in same I... abdul.faras TSO/ISPF 4 Tue Jul 30, 2013 10:49 am
No new posts Socketexception:Connection reset erro... Thamilselvi CICS 0 Fri Apr 26, 2013 6:56 am
No new posts Linkedit COBOL with MQ Connection Garry Carroll Java & MQSeries 15 Wed Sep 05, 2012 9:41 pm
No new posts SQLCODE -924, Error: DB2 CONNECTION ... vickeyeee DB2 6 Wed Jan 11, 2012 4:27 pm


Facebook
Back to Top
 
Mainframe Wiki | Forum Rules | Bookmarks | Subscriptions | FAQ | Tutorials | Contact Us