If you experience problems with client/server network communications, you can set a number of command line parameters for both the client and the server. These parameters enable you to work around peculiarities of different network protocol implementations.
Supply the network communication parameters on the server or client command line as in the following example:
start_iq -x tcpip(PARM1=value1;PARM2=value2;. . .),...
From the client side, communication parameters are entered as in this example:
CommLinks=tcpip(PARM1=value1;PARM2=value2;. . .),...
If they include spaces, the network communication parameters must be enclosed in quotation marks to be parsed properly:
start_iq -x "tcpip(PARM1=value 1;PARM2=value 2;...),..." start_iq -x "tcpip(PARM1=value1;PARM2=value2;...)"
In UNIX, quotation marks are required if more than one parameter is given, because UNIX interprets the semicolon as a command separator.
Boolean parameters are turned on with any of YES, ON, TRUE, or 1, and are turned off with any of NO, OFF, FALSE, or 0. The parameters are case-insensitive.
Enter the commands to set the communication parameters on a single line; you can also include them in a configuration file, then use the @ server or client command line switch to invoke the configuration file.
The parameters currently available for TCP/IP, HTTP, and HTTPS are as follows.
TCP/IP |
HTTP and HTTPS |
|---|---|
Broadcast [BCAST] |
Identity |
BroadcastListener [BLISTENER] |
Identity_Password |
ClientPort [CPORT] |
DatabaseName [DBN] |
DLL |
LocalOnly [LOCAL] |
DoBroadcast [DOBROAD] |
LogFile [LOG] |
Host [IP] |
LogMaxSize [LSize] |
LocalOnly [LOCAL] |
LogOptions [LOpt] |
LDAP [LDAP] |
LogFormat [LF] |
MyIP [ME] |
MaxConnections [MaxConn] |
ReceiveBufferSize [RCVBUFSZ] |
MaxRequestSize [MaxSize] |
SendBufferSize [SNDBUFSZ] |
MyIP [ME] |
ServerPort [PORT] |
ServerPort [PORT] |
TDS |
Timeout [TO] |
Timeout [TO] |
|
VerifyServerName [VERIFY] |