|
View previous topic :: View next topic
|
| Author |
Message |
balaji_g_m
New User
Joined: 27 Aug 2006
Posts: 8
|
|
|
|
I am trying to FTP a file from PC to Mainframe thru command prompt.
When I connect to the mainframe IP address, I receive the following Error message
"ftp: connect :Unknown error number".
P.S:
When I Ping the Mainframe IP Address from my PC Command prompt, I get a Reply.
Appreciate your response.
Thanks. |
|
| Back to top |
|
 |
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA
|
|
|
|
| Could you help yourself just a little and, maybe, post the exact commands you are typing into FTP command prompt? |
|
| Back to top |
|
|
superk
Global Moderator
Joined: 26 Apr 2004
Posts: 4652
Location: Raleigh, NC, USA
|
|
|
|
| balaji_g_m wrote: |
| When I Ping the Mainframe IP Address from my PC Command prompt, I get a Reply. |
Jeez, I'd sure hope so, or you'd have much bigger problems. A ping doesn't require access rights or any kind of authentification. FTP does, and my gut feeling is that you don't have the proper FTP authority. I presume that you've already tested and verified your FTP access on your mainframe already? |
|
| Back to top |
|
|
balaji_g_m
New User
Joined: 27 Aug 2006
Posts: 8
|
|
|
|
| Robert Sample wrote: |
| Could you help yourself just a little and, maybe, post the exact commands you are typing into FTP command prompt? |
Hello Robert,
I am writing a Java tool to interact with Mainframe in FTP Mode [To submit a Job, Receive and Import reports].
To Test the functionality, I attempted connecting to Mainframe thru FTP commands in PC Command Prompt.
C:\Documents and Settings\Balaji>ftp
ftp> open
To XXX.XX.XXX.XXX
> ftp: connect :Unknown error number
Whereas when I try pinging the IP using the following command, I receive the response.
C:\Documents and Settings\Balaji>ping XXX.XX.XXX.XXX
Pinging XXX.XX.XXX.XXX with 32 bytes of data:
Reply from XXX.XX.XXX.XXX: bytes=32 time=448ms TTL=34
Reply from XXX.XX.XXX.XXX: bytes=32 time=411ms TTL=34
Reply from XXX.XX.XXX.XXX: bytes=32 time=405ms TTL=34
Reply from XXX.XX.XXX.XXX: bytes=32 time=402ms TTL=34
Ping statistics for XXX.XX.XXX.XXX:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 402ms, Maximum = 448ms, Average = 416ms
P.S: The IP Address is masked with X |
|
| Back to top |
|
|
balaji_g_m
New User
Joined: 27 Aug 2006
Posts: 8
|
|
|
|
| superk wrote: |
| balaji_g_m wrote: |
| When I Ping the Mainframe IP Address from my PC Command prompt, I get a Reply. |
Jeez, I'd sure hope so, or you'd have much bigger problems. A ping doesn't require access rights or any kind of authentification. FTP does, and my gut feeling is that you don't have the proper FTP authority. I presume that you've already tested and verified your FTP access on your mainframe already? |
Hello Superk,
I was having an impression that we do not require rights to establish a connection [Using FTP OPEN Command].
Once connection is established it requests for RACF ID and password.
My concern is connection is not established with mainframe [FTP OPEN]. |
|
| Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India
|
|
|
|
| Are you not talking about one of those things which should be addressed by your Site-Support Group? |
|
| Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA
|
|
|
|
This syntax is wrong:
| Quote: |
ftp> open
To XXX.XX.XXX.XXX |
You should be entering "open xxx.xx.xxx.xxx" (assuming, of course, that xxx.xx.xxx.xxx is your mainframe IP address). |
|
| Back to top |
|
|
superk
Global Moderator
Joined: 26 Apr 2004
Posts: 4652
Location: Raleigh, NC, USA
|
|
|
|
Actually, just specifying >open does work. Just as the OP has shown, the response is the prompt >To to which you can respond with the FTP server address or domain name.
| Code: |
C:\>ftp
ftp> open
To mvsxxxx
Connected to mvsxxxx.xxxx.xx
220-FTPB1 IBM FTP CS V1R11 at MVSXXXX.xxxx.xx
220 Connection will close if idle for mor
User (mvsxxxx.xxxx.xxx:(none)):
|
|
|
| Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA
|
|
|
|
Thanks for the information, kevin -- I provide the destination as part of the open command so I didn't realize the syntax when you don't put it in.
In that case, balaji_g_m, your only choice is to contact your site support group and work with them to figure out the problem. An online forum like this cannot look at the system log (among other resources) to determine what the problem is. |
|
| Back to top |
|
|
Craq Giegerich
Senior Member
Joined: 19 May 2007
Posts: 1512
Location: Virginia, USA
|
|
|
|
| Is java putting a hex'00' at the end of the FTP server address? |
|
| Back to top |
|
|
balaji_g_m
New User
Joined: 27 Aug 2006
Posts: 8
|
|
|
|
| Craq Giegerich wrote: |
| Is java putting a hex'00' at the end of the FTP server address? |
Hello Crag,
No it is not putting Hex '00' at the end of the FTP
----------------------------------------------------------------------------------
Thanks All for your suggestions.
I tried ping SYSA or SYSB or SYSC in command option in TSO [Option 6] that gives me the correct IP Address for FTP.
and with that IP Address, the connection is established.
Thanks again.
| Code: |
Menu List Mode Functions Utilities Help
ssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss
ISPF Command Shell
Enter TSO or Workstation commands below:
===> ping sysa
Place cursor on choice and press enter to Retrieve command
=>
=>
=>
=>
=>
=>
=>
=>
=>
=>
CS V1R10: Pinging host SYSA.XXXXX.XX (XX.XXX.XX.XX)
Ping #1 response took 0.001 seconds.
*** |
|
|
| Back to top |
|
|
superk
Global Moderator
Joined: 26 Apr 2004
Posts: 4652
Location: Raleigh, NC, USA
|
|
|
|
So ....
you were connecting to the wrong address? |
|
| Back to top |
|
|
balaji_g_m
New User
Joined: 27 Aug 2006
Posts: 8
|
|
|
|
| superk wrote: |
So ....
you were connecting to the wrong address? |
Nope. I was connecting to the IP that we use to connect to the Mainframe Terminal [IBM Personal communications]. Looks like that is a Proxy IP Address.
Here is the background Information, I work from offshore [Not in the client workplace] so the network team has provided a Proxy IP address to connect to Client workplace. This Proxy IP shall not be similar to the exact LPAR IP address. Adding to it, This Proxy IP do not have FTP port Number [21] enabled. This was the reason why I was able to get reply from the server and was not successful in establishing the connection.
From the google search, I believe many have faced this issue and couldn't resolve it. Hence added my resolution to this Post. |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Good to hear it is working - thank you for posting the resolution 
d |
|
| Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India
|
|
|
|
| balaji_g_m wrote: |
| Here is the background Information, I work from offshore [Not in the client workplace] so the network team has provided a Proxy IP address to connect to Client workplace. This Proxy IP shall not be similar to the exact LPAR IP address. Adding to it, This Proxy IP do not have FTP port Number [21] enabled. This was the reason why I was able to get reply from the server and was not successful in establishing the connection. |
If that was the set-up at your shop then I'm not sure if we are really talking about a "solution"! AFAIK, In computer networks, a proxy server is a server (a computer system or an application program) that acts as an intermediary for requests from clients seeking resources from other servers. A client connects to the proxy server, requesting some service, such as a file, connection, web page, or other resource, available from a different server. The proxy server evaluates the request according to its filtering rules. For example, it may filter traffic by IP address or protocol. If the request is validated by the filter, the proxy provides the resource by connecting to the relevant server and requesting the service on behalf of the client. But in your case, you've bypassed the proxy-server itself then what's the benfit of having a proxy-server at first place? |
|
| Back to top |
|
|
|
|
