Re: What's your favorite way to find out if TCP/IP is started in CL?

On 14-Dec-2011 15:02 , Jim Oberholtzer wrote:

The one thing that won't work is pinging another address because it
might be the address is not reachable and ping should report no
response.

I thought of pinging localhost, but I'm not sure that's sure fire
either.

Thoughts?

The definition of "started" may be somewhat open to interpretation. That a particular "interface" is started may be more relevant than if only the protocol is enabled whereby no interfaces over which an actual [¿non-virtual\external?] conversation could be started? The definition of "started" instead could even be specific to a particular server.? Regardless...

What about either of the following which provide information similar to what is available via NETSTAT [Work with TCP/IP Network Sts (WRKTCPSTS)]:

≥ the List Network Interface (QtocLstNetIfc) API which "returns a detailed list of all logical TCP/IP interfaces." including the "interface status."

_List Network Interfaces (QtocLstNetIfc) API_
http://publib.boulder.ibm.com/infocenter/iseries/v5r4/topic/apis/qtoclstnetifc.htm

≥ the List Network Connections (QtocLstNetCnn) API which "returns a non-detailed list of all the network connections for a specified net connection type or a list of the subset of network connections for a specified net connection."

_List Network Connections (QtocLstNetCnn) API_
http://publib.boulder.ibm.com/infocenter/iseries/v5r4/topic/apis/qtoclstnetcnn.htm

Of note: Both APIs suggest that "TCP/IP must be active on this system; otherwise error message TCP84C0 will be issued." so that would seem to be sufficient for "TCP/IP is started".?

Regards, Chuck