Firewall issue. It looks like FTP was trying to open the data connection and 
that was blocked. 

IMHO, always suspect the firewall(s). You will be right almost every time.  

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of 
Johnston, Robert E
Sent: Friday, March 20, 2009 3:11 PM
To: [email protected]
Subject: FTP timeout problem

I am trying to FTP about 407MB from an external server (CA ESD) to z/OS 1.7, 
without luck so far. While I continue to mess with this, I'd like to get some 
feedback about what I've done so far.

Initial FTP DATA was:
CHKPTINT          0   
DATATIMEOUT       300 
DCONNTIME         120 
FTPKEEPALIVE      0   
INACTIVE          300

Has evolved to:
CHKPTINT          0  
DATACTTIME        240
DATATIMEOUT       300
DCONNTIME         120
FTPKEEPALIVE      300
INACTIVE          300
INACTTIME         300

The last FTP job ended:
16:07:42(000011C0.1) SC3283 receive_data: entered                        
16:07:42(000011C0.1) MR5735 progressReport: entered                      
16:07:42(000011C0.1) MF1671 seq_write_file: entered                      
16:07:42(000011C0.1) SC3283 receive_data: entered                        
16:07:42(000011C0.1) MF0581 seq_close_file: entered                      
16:07:42(000011C0.1) MF0660 seq_close_file: file closed                  
16:07:42(000011C0.1) SC2329 dataClose: entered                           
16:07:42(000011C0.1) SC2887 getReply: entered                            
16:07:42(000011C0.1) SC3731 getNextReply: entered with waitForData = TRUE
EZA2589E Connection to server interrupted or timed out. Waiting for reply
EZA1721W Server not responding, closing connection.                      
16:09:42(000011C0.-1) CU2258 write_smf_record: entered with type 16.     

I know I haven't given much to go on. I ran the same job with no changes and 
got elapsed times of 33, 8, and 46 minutes.

It bothers me that I am still getting some kind of timeout after 2 minutes when 
most of the timers/intervals have been changed to more than 2 minutes (there 
sure are a lot of timers...). Things I am wondering are...

Do the times above look reasonable or should I put them back?

Why doesn't FTPKEEPALIVE default to "on" if it is a good thing?

If the EZA2589E "Waiting for reply" is covered by the INACTTIME timer, why did 
it not wait for 5 minutes?

I'm looking at doing a packet trace next but I am not very familiar with it so 
it will take me a while. I'll be grateful for any crumbs tossed this way.

Thanks and have a good weekend,
Robert Johnston
UAMS - Little Rock


Confidentiality Notice: This e-mail message, including any attachments, is for 
the sole use of the intended recipient(s) and may contain confidential and 
privileged information.  Any unauthorized review, use, disclosure or 
distribution is prohibited.  If you are not the intended recipient, please 
contact the sender by reply e-mail and destroy all copies of the original 
message.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
NOTICE: This electronic mail message and any files transmitted with it are 
intended
exclusively for the individual or entity to which it is addressed. The message, 
together with any attachment, may contain confidential and/or privileged 
information.
Any unauthorized review, use, printing, saving, copying, disclosure or 
distribution 
is strictly prohibited. If you have received this message in error, please 
immediately advise the sender by reply email and delete all copies.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to