IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

FTP failing with code 426


IBM Mainframe Forums -> ABENDS & Debugging
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
abin

Active User


Joined: 14 Aug 2006
Posts: 198

PostPosted: Sat Dec 08, 2007 8:52 pm
Reply with quote

Hi,

I am trying to FTP a data set into a Microsoft server. The FTP step is failing with following message.
426 Connection closed; transfer aborted.
EZA1735I Std Return Code = 27426, Error Code = 00002
EZA1701I >>> QUIT
221
******************************* Bottom of Data ************

But there is another step which FTPes another file to the same location but another directory. This one runs fine.
Again when I run the failing step alone it runs through.
Back to top
View user's profile Send private message
stodolas

Active Member


Joined: 13 Jun 2007
Posts: 632
Location: Wisconsin

PostPosted: Sat Dec 08, 2007 9:37 pm
Reply with quote

What command was attempted just before the failure?
Back to top
View user's profile Send private message
abin

Active User


Joined: 14 Aug 2006
Posts: 198

PostPosted: Sat Dec 08, 2007 9:40 pm
Reply with quote

A put command.

PUT 'TEST.MNSCP.RJHCL.D2345' +
TEST_MNSCP_RJHCL_D2345_D12080600.txt
Back to top
View user's profile Send private message
superk

Global Moderator


Joined: 26 Apr 2004
Posts: 4652
Location: Raleigh, NC, USA

PostPosted: Sat Dec 08, 2007 11:33 pm
Reply with quote

Quote:

EZA1735I Std Return Code = rc, Error Code = ec

Explanation: FTP has ended with an error only because the user has specified EXIT as a start parameter. Normally FTP would continue.
rc is the standard return code. rc is in the format yyxxx, where

yy
the subcommand code, which is a number from 0 to 99.

xxx
This is the last reply code received from the FTP server. If a subcommand failed before a reply was received from the server, this value is 000.

ec is the client error code set by the FTP client.

System Action: The FTP client ends.

User or Operator Response: To determine the cause of the error, refer to z/OS Communications Server: IP User's Guide and Commands for information about FTP return codes, including subcommand codes, client error codes, and reply codes.

System Programmer Response: None.

Source Data Set: EZAFTPCX


Quote:

426 Connection closed; transfer aborted.


Everything I found on the Internet indicated that a 426 is a problem with either:

A. The server directory is out of space or
B. A firewall problem or TCP/IP problem.
Back to top
View user's profile Send private message
abin

Active User


Joined: 14 Aug 2006
Posts: 198

PostPosted: Sat Dec 08, 2007 11:43 pm
Reply with quote

Hi Kevin,

Thanks for the reply. I got some more info on it.
For client error code 00002 here is the explanation.

02 FTP_SERVER_ERROR Error reply returned by the server.

But what exactly is all this. Is FTP_SERVER_ERROR some thing tailored on the server. This issue comes up only at some times. At other time it goes fine.

Quote:
A. The server directory is out of space or
B. A firewall problem or TCP/IP problem.


If it is out of space problem, then how does it runs second time.
If it is a firwal problem, again how does it runs the second time. Also how does another FTP which sends another file to same site, and coming after the failling FTP runs fine.
Back to top
View user's profile Send private message
stodolas

Active Member


Joined: 13 Jun 2007
Posts: 632
Location: Wisconsin

PostPosted: Sun Dec 09, 2007 12:16 am
Reply with quote

People could be manually freeing up space when they notice the disk is full so it runs the 2nd time. Just because the site is the same, doesn't mean the path you are trying to put to isn't on a different disk that could be full.
Back to top
View user's profile Send private message
stodolas

Active Member


Joined: 13 Jun 2007
Posts: 632
Location: Wisconsin

PostPosted: Sun Dec 09, 2007 12:18 am
Reply with quote

www.cisco.com/univercd/cc/td/doc/product/software/ioss390/ios390mu/muftp.htm

It could also be a timeout issue. If the file you are trying to send has been migrated and the job is attempting to send the file before it is recalled a timeout can occur and give a 426.
Back to top
View user's profile Send private message
abin

Active User


Joined: 14 Aug 2006
Posts: 198

PostPosted: Mon Dec 10, 2007 10:42 am
Reply with quote

Hi Steve,

It could be due to migration problem. But, is there any way to find out whether the file was migrated from JCL messages.
Back to top
View user's profile Send private message
abin

Active User


Joined: 14 Aug 2006
Posts: 198

PostPosted: Mon Dec 10, 2007 12:52 pm
Reply with quote

Hi Steve,

The issue does not seems to be because of data set migration. I tried to FTP a migrated file. The job automatically recalled the migrated file and executed the FTP.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> ABENDS & Debugging

 


Similar Topics
Topic Forum Replies
No new posts run rexx code with jcl CLIST & REXX 15
No new posts Compile rexx code with jcl CLIST & REXX 6
No new posts REXX code to expand copybook in a cob... CLIST & REXX 2
No new posts VSAM return code 23 - for a Random read COBOL Programming 4
No new posts Monitoring production job progress. N... JCL & VSAM 4
Search our Forums:

Back to Top