FTP to server using DNS name

Paul Smith · New User Joined: 08 May 2007 Posts: 3 Location: Maryland

Is there a way to ftp a file from TSO/ISPF to a server using the fully qualified DNS name instead of the IP address of the server?

dick scherrer · Posted: Wed May 09, 2007 12:10 am

Welcome to the forum

Will running the ftp in batch do what you want?

You should be able to use the name rather than the ip.address.nodes so long as your mainframe is set up to use DNS (several that i've worked with are not).

Paul Smith · New User Joined: 08 May 2007 Posts: 3 Location: Maryland

Thanks for the quick response. This is a batch job. I'm using the ftp facility as the second step in a proc. The first statement in my ftp source is "open 99.99.999.99" Just plugging in the DNS name doesn't fly (I figured it wouldn't, but gave it a shot). I don't know if the M/F is set up to use DNS.

superk · Posted: Wed May 09, 2007 12:45 am

PING or TRACERTE the DNS name and you'll find out.

Devzee · open 99.99.999.99"

In our BATCH JCL we do

Paul Smith · New User Joined: 08 May 2007 Posts: 3 Location: Maryland

I tried ping, tracerte and ftp "servername" but kept getting command not recognized. This server has a dynamic ip address, but our network people are supposed to assign it a static one, so that should fix the problem.

If anybody has any other suggestions, I'll try them just for my own information.

Thanks for the help

dick scherrer · Posted: Wed May 09, 2007 7:20 pm

Hello,

On your pc, go to start, run, and enter command.com. At the drive:\> prompt, enter ping dnsname or ip.address.nodes and hit enter. Your pc should have DNS available.

Once that works, try the same thing from your mainframe ftp job. Your location may not support ping/tracert from a mainframe session.

You might ask your support people if they have DNS working for the mainframe. It may be that you need to add something to your batch job.

If they don't set up a static ip address and they don't support DNS, you may need to pull the data from the other end rather than push it from the mainframe.

yogeshpawar · New User Joined: 01 Mar 2006 Posts: 37 Location: Sussex-UK

Hi Dick,

Is it possible to give TRACERT kind of commands from mainframe command option?

If TRACERT does not work then what other commands can be used?

Pedro · Posted: Thu Jun 11, 2009 10:42 pm

Robert Sample · Posted: Thu Jun 11, 2009 10:45 pm

Try TRACERTE -- it's in the SEZALOAD library.

yogeshpawar · New User Joined: 01 Mar 2006 Posts: 37 Location: Sussex-UK

Thanks. TRACERTE command works for me.

Robert Sample · Posted: Fri Jun 12, 2009 1:18 am

Glad to hear it's working.

smiley · New User Joined: 08 Feb 2006 Posts: 27

hi,

I am facing the same issue for doing an FTP from Mainframe to another system using DNS Name. I tried pinging to the server with both IP and the DNS as mentioned above. It worked fine with the IP but DNS I am getting an error unknown server.
1) How to check whether the Mainframe system is compatable with the DNS
2) Is there any parameters that we need to set for using the DNS NAME IN jobs.

Robert Sample · Posted: Wed Jun 20, 2012 6:29 pm

1, As long as your machine is using z/OS or OS/390, it is compatible with DNS -- the TCP/IP set up for these operating systems includes DNS support.

2. You need to check with your site support group -- there are TCP/IP set up parameters that must be set correctly in order for DNS to work on your mainframe. Not all mainframes are set up to use DNS, and the DNS used can be either based on the mainframe or based on a DNS server in your network. Which, if any, is set up -- only your site support group (or somebody else working at your site) can tell you. If your site is not set up to use DNS, there's no parameter I'm aware of that you can set in your job to use DNS.

agkshirsagar · Posted: Wed Jun 20, 2012 6:54 pm

I think the terminology used by OP is little odd. The correct term is FQDN.
(DNS - Domain Name Server translates the FQDN to its corresponding IP address.)
Why would you expect to reach the intended ftp server by using DNS address?
I agree with Robert's suggestion to check with site support group to translate the hardcoded ip address to a FQDN. Alternative approach that may work in some cases is to try to connect to the server using hardcoded IP and pay attention 220 messages that show the sitename.