× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



If one performs an ENDTCP I am seeing
this server ended
that server ended
then

TCP9531 Diagnostic QTOCIP6INT QSYS
From module . . . . . . . . : TOCUTILITY
From procedure . . . . . . :
internalSendMessageToQTCPIPJobQueue__FP14IpFun
cReqStruciRV17CancelHandlerParmPcP10return_msgT222SendEscapeMessagesTypec

Statement . . . . . . . . . : 78
Message . . . . : TCP/IP is not active.

TCP8A3F Escape QTOCIP6INT QSYS
From module . . . . . . . . : TOCUTILITY
From procedure . . . . . . :
internalSendMessageToQTCPIPJobQueue__FP14IpFun
cReqStruciRV17CancelHandlerParmPcP10return_msgT222SendEscapeMessagesTypec

Statement . . . . . . . . . : 102
Message . . . . : Unable to determine if operation completed.
Cause . . . . . : Either TCP/IP is not active, or the job default wait
time
was exceeded while waiting for the operation to complete. Recovery . .
. :
Use the WRKTCPSTS (NETSTAT) CL command to determine if TCP/IP is
active.
Review the QTCPCTL and QTCPWRK system job logs to determine if the
operation
completed. Review the QSYSOPR and QTCP message queues to determine when

TCP/IP was ended or if it has not been started. If the problem is
determined to be a timeout problem, then wait for the system activity to

decrease, or increase the default wait time for your job using the
Change
Job (CHGJOB) command.

IBM is telling me the magic cure is to either
CHGCMDDFT to STRTCP STRIP6(*NO)
or change everywhere that STRTCP runs to not start IP6.
Frankly I think that the person assigned to the call just doesn't like IP6
and thinks who needs it internally because your firewalls should NAT from
IP4 to IP6. He saw IP6 in the substring of the From Program and put the
blame there.

My test is to ENDTCP, try STRTCP STRIP6(*NO) and then try ENDTCP again and
see if I still get the error. Actually, this IS a test lpar and I really
could do that.

My question is: If I run ENDTCP twice in a row, with no STRTCP in
between, and get the message both times, how does it know (or should it
even care) if I ever ran STRTCP STRIP6(*YES) sometime in the past?

pmr 39635,500,000.



Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.