Working with TCPTEST

Another utility, provided by GE, is the TCPTEST diagnostic program. To run TCPTEST, click the Start button, click Run, and then type the following into the command line:

TCPTEST parameters <Enter>

where parameters are one or more of the following command parameters in the table. To display a list of parameters on the screen, type the following:

TCPTEST <Enter>

The program requires two nodes to run, one as a client and one as a server. Set up the server node first, as follows:

tcptest /S <Enter>

The client node must use as a minimum the following TCPTEST parameters:

tcptest /C /Rnodename <Enter>

where nodename is the SCU node name of the server node. For example, to make VIEW01 a server, run TCPTEST with the /S parameter, as shown above. To communicate with VIEW01, go to another node and type the following:

tcptest /C /RVIEW01 <Enter>

TCPTEST Parameters

The parameter...

Lets you...

/Bx

Set the receive and send buffer size to x. The default size is 1400 messages. If you specify this parameter, make sure that both nodes have the same buffer size.

/C

Set up a node as a client. This parameter requires you to provide the remote server node name (see the /R parameter below).

/D

Display run-time information (such as the data received).

/Fx

Set to x milliseconds, how often to send messages. By default, messages are sent as fast as possible.

/Pportnumber

Use portnumber in place of the default ports for both the server node and the client node.

/Rserver

Specify the name of the remote server node.

/S

Set up this node as a server.

/Tx

Set the TCP time-out value for sending and receiving data to x. This parameter is supported only if your WINSOCK implementation supports changing the TCP time-out value. Most implementations do not.

/W

Test the WINSOCK interface and display WSAData (for example, vendor information).

It is recommended that you run TCPTEST without iFIX running. If you need to run both at the same time, be sure to change the port number (/P) that TCPTEST uses. Otherwise, a conflict may occur with the data being passed because, by default, TCPTEST uses the same port number as iFIX. Note that the client and server must use identical port numbers when using TCPTEST.

 

See Also