On Wed, 16 Jan 2008 07:45:34 -0600, Greg Shirey <[EMAIL PROTECTED]> wrote:
>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
Thanks Mark and Jack for the responses. Since then, the network guys
admitted to changing something on the server. They blamed the
intermittent problem with communicating from the mainframe on the router
that connects the mainframe to the network -- something about how it has
to hold a lot of inf
<
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.
<
I've never had a network problem that the network folks admitted to. But
that's another story
One of the things that I tend to run i
Greg Shirey wrote:
> 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
>
>
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
5 matches
Mail list logo
