FTP from MVS system to Windows Server

sobiswal · New User Joined: 23 Feb 2010 Posts: 1 Location: Kolkata

Please find my JCL below.

superk · Posted: Tue Feb 23, 2010 5:18 pm

c:\

is NOT a valid name of a directory. Use LS or DIR to find the names of the directories on that server.

rukmakiran · New User Joined: 19 Apr 2005 Posts: 21

Jobs is abending with the below error in FTP mainframe file to Middleware server ,folder 'PI' is not accessible since yesterday even though there are
no changes in folder "PI" , and the folder was accessible for last but one run.

.EZA1460I Command:
.EZA1736I cd pi
.EZA1701I >>> CWD pi
.550 pi: The system cannot find the file specified.
.EZA1735I Std Return Code = 07550, Error Code = 00002
.EZA1701I >>> QUIT
.221

Can you suggest where will be the issue ? at server or in FTP ?

Thanks

Robert Sample · Posted: Tue Feb 23, 2010 9:21 pm

It's most likely a server issue. Permissions could have been changed on the server. The directory name case may have changed (Unix, for example, is case sensitive so PI and pi are two different directories). The directory may have been moved so a full or relative path name may be needed (cd /root/pi for example).

Another possibility, on the FTP side, is that someone renumbered the FTP script. FTP does not like line numbers since it did not come out of the TSO / ISPF environment.

rukmakiran · New User Joined: 19 Apr 2005 Posts: 21

Thanks for Quick reply,
Asked my server operations group to look into the privileges, but there were no changes in case or line numbers also in location of the folder.

Are there any possibility from TSO environment which effect FTP ?

Robert Sample · Posted: Tue Feb 23, 2010 9:55 pm

Verify the file containing the FTP commands has spaces all the way to the end of each line -- if there are line numbers in it, you will have trouble.

rukmakiran · New User Joined: 19 Apr 2005 Posts: 21

Issue resolved by changing "cd PI" to "cd \PI" , but i just want to know why the "cd PI" was acceptable till day before & currently not ? and where was the change - Is it from middleware server or changes in TSOenvironmentt ? do you have nay idea ?

Thanks,

MBabu · Posted: Tue Feb 23, 2010 10:09 pm

maybe the ftp server on the workstation was started in a working directory of the root when it worked and started with a different working directory when it failed. In any case, fully qualifying the target name is always a good idea.

rukmakiran · New User Joined: 19 Apr 2005 Posts: 21

My Question is - why it wors before & did not work currently with the same script?

Also let me know if you have any idea on where can we find the maaped location for FTP address SERVER1.nj.ssmb.com is mapped to \\SERVER1\Archive\Data\ ?

Thanks,

Robert Sample · Posted: Tue Feb 23, 2010 11:34 pm

It worked before and did not work currently with the same script because something was changed on the server (permissions, default folder, operating system, something).

FTP address SERVER1.nj.ssmb.com is resolved either through a NETRC (look at the JCL for the FTP job to see if there's a NETRC DD name), or through DNS (which may be done on the mainframe or via a name server on your network -- you'll want to get with your site support group for either of these cases). There is no need for a mapping as FTP works with an IP address and port number on that IP address.

rukmakiran · New User Joined: 19 Apr 2005 Posts: 21

Thanks Reobert.