Re: TCP/IP shutdown or crash

[Scott Klement <klemscot@xxxxxxxxxxxx>]

> Do you ever have a need to shutdown TCP/IP but keep the rest of the system
> up (including applications) and if so, why?

No, not really.  Technically, I do that when I put the system in
restricted state to do something like a "GO SAVE opt 21" or "RCLSTG".  But
I don't think that's what you mean.


> Do you ever have TCP/IP crash?

I had a bad piece of hardware that was sending all sorts of garbage over
the network at full speed.  When this happened, my Windows PCs locked up.
My FreeBSD machines kept running just fine, and my iSeries stopped TCP/IP
until I answered a message that it had put in QSYSOPR.

It was a fun day.


> I have a customer that says sometimes they need to shutdown TCP/IP and that
> sometimes it crashes unexpectedly. This creates some "challenges" for one of
> our applications that is TCP/IP dependent.
>
> My stance has been that needing to shut TCP/IP down while keeping the rest
> of the system up seems very unusual to me, and that having it "crash" is
> unheard of and should be reported to IBM immediately.
>
> What do you guys think?

I agree that a "crash" and especially an "unexpected crash" should be
reported to IBM, unless you know that you're doing something unusual that
might cause it.  Though, I can't think of anything that would qualify...

And, while shutting down TCP/IP might be unusual, it's the customer's
choice.  He can choose to shut it down if he wants to -- therefore, your
programs should be smart enough to deal with that situation

Well, you asked what I thought :)