Fellow listers, We have some batch jobs that run early in the morning, create a file, then FTP it to a server in our network. We had one of the jobs fail to FTP, getting the message: EZA2589E Connection to server interrupted or timed out. Initial connection
At that time, when we tried to PING the server, it timed out. Five minutes later, we got a response back from the server, so the job reran to success. This happened on and off all night, the server would be "PINGable" for a while, then not. I perceived this as a server or router error, but the network guys say no. They are able, during these times when the mainframe cannot get a response to a PING, to successfully logon and FTP files to the server from their PCs. So, my question to this esteemed group is what is there in the mainframe IP environment could intermittently cause PING to fail? (And only to a particular server - I set up a REXX to PING 5 servers, go to sleep for 30 seconds, and do it for about 30 minutes. Only this server did not respond to the PING.) We are running z/OS 1.7 on a 2086 using the OSA card for connection to the network. Thanks for any feedback, Greg Shirey Ben E. Keith Company ---------------------------------------------------------------------- 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
