Re: TCP Problem ?

[Graham Chapman <gjchap@xxxxxxx>]

Hi Swa

 Netstat *IFC shows 3 interfaces - LOOPBACK is in the process of ENDING
(and has been for over 24 hours). The other 2 are active but when I try to
end them with option 10 I get message TCP1B85 - "x.x.x.x interface not
ended. Cause: ENDTCPIFC CL command was unable to communicate with the
QTCPIP job. Recovery: Issue ENDTCP followed by STRTCP"
However I already tried ENDTCP yesterday and it is STILL running!!
I just tried a STRTCP and monitored the error messages; apparently there is
a lock on an object called QTCPACT which must be an internal object (MI) as
I can't find it with DSPOBJD. The only TCP job in QSYSWRK subsystem is
QAPPCTCP which is in an END state.

I am going to re-IPL the thing during our lunchtime to see if that sorts
things out.

Thanks..

Graham

At 11:17 AM 10/13/98 +0100, you wrote:
>
>
>
>Hi,
>have you tried "Netstat" and then option 1 work with tcp interfaces status
>on this screen you can stop and restart the interface.
>Swa
>
>
>
>
>Graham Chapman <gjchap@csi.com> on 13/10/98 09:05:32
>
>To:   MIDRANGE-L@midrange.com
>cc:    (bcc: Swa AERTS/DBN/BEL/BS/DANONE)
>Subject:  TCP Problem ?
>
>
>
>
>Hi..
>
> I have a 'small' problem with TCP on a model 500 (V3R7) and was wondering
>if anyone else has encountered it. Yesterday one of our Ethernet LANs
>crashed. Actually we traced it back to to AS/400 and found that the
>*ETHLIND had varied off and could not be restarted. I re-IPLed the IOP
>which brought it back alive but everytime I tried to start TCP over this
>line, it varied off again. The line has sinced assumed a FAILED state and
>the messages in the joblog suggest an internal system failure.
>I also tried ending and restarting TCP but the ENDTCP job has now been
>active for 24 hours!
>It's worth pointing out also that, owing to security requirements, we are
>not allowed an ECS connection to IBM so I cannot send any APAR data
>electronically. Before preparing any APAR on tape I thought it worthwhile
>to ask everyone their valued opinion.
>
>PS. I have also found a WRKPRB entry predating this problem by 2 days for a
>LIC program failure for #F2FEXC. This could be the root of my problem...
>
>TIA
>
>Graham
>
>
>
>+---
>| This is the Midrange System Mailing List!
>| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
>| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
>| To unsubscribe from this list send email to
>MIDRANGE-L-UNSUB@midrange.com.
>| Questions should be directed to the list owner/operator:
>david@midrange.com
>+---
>
>
>
>
>
>



+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---