TCP, LU62, and NETBIOS

Use these queue manager properties pages, or stanzas in the qm.ini file, to specify network protocol configuration parameters. They override the default attributes for channels.

TCP
Use the TCP queue manager properties page from the IBM® MQ Explorer, or the TCP stanza in the qm.ini file, to specify Transmission Control Protocol/Internet Protocol (TCP/IP) configuration parameters.
Port= 1414 | port_number
The default port number, in decimal notation, for TCP/IP sessions. The well known port number for IBM MQ is 1414.
Library1= DLLName1 ( IBM MQ for Windows only)
The name of the TCP/IP sockets DLL.

The default is WSOCK32.

KeepAlive= NO |YES
Switch the KeepAlive function on or off. KeepAlive=YES causes TCP/IP to check periodically that the other end of the connection is still available. If it is not, the channel is closed.
ListenerBacklog=number
Override the default number of outstanding requests for the TCP/IP listener.

When receiving on TCP/IP, a maximum number of outstanding connection requests is set. This can be considered to be a backlog of requests waiting on the TCP/IP port for the listener to accept the request. The default listener backlog values are shown in Table 1.

Table 1. Default outstanding connection requests (TCP)
Platform Default ListenerBacklog value
Windows Server 100
Windows Workstation 5
Linux® 100
Solaris 100
HP-UX 20
AIX® V5.3 or later 100
Note: Some operating systems support a larger value than the default shown. Use this to avoid reaching the connection limit.

Conversely, some operating systems might limit the size of the TCP backlog, so the effective TCP backlog could be smaller than requested here.

If the backlog reaches the values shown in Table 1, the TCP/IP connection is rejected and the channel cannot start. For message channels, this results in the channel going into a RETRY state and retrying the connection at a later time. For client connections, the client receives an MQRC_Q_MGR_NOT_AVAILABLE reason code from MQCONN and retries the connection at a later time.

The following group of properties can be used to control the size of buffers used by TCP/IP. The values are passed directly to the TCP/IP layer of the operating system. Great care should be taken when using these properties. If the values are set incorrectly it can adversely affect the TCP/IP performance. For further information about how this affects performance refer to the TCP/IP documentation for your environment. A value of zero indicates that the operating system will manage the buffer sizes, as opposed to the buffer sizes being fixed by IBM MQ.

Connect_Timeout= 0 |number
The number of seconds before an attempt to connect the socket times out. The default value of zero specifies that there is no connect timeout.

IBM MQ channel processes connect over nonblocking sockets. Therefore, if the other end of the socket is not ready, connect() returns immediately with EINPROGRESS or EWOULDBLOCK . Following this, connect will be attempted again, up to a total of 20 such attempts, when a communications error is reported.

If Connect_Timeout is set to a non-zero value, IBM MQ waits for the stipulated period over select() call for the socket to get ready. This increases the chances of success of a subsequent connect() call. This option might be beneficial in situations where connects would require some waiting period, due to high load on the network.

SndBuffSize=number| 0
The size in bytes of the TCP/IP send buffer used by the sending end of channels. This stanza value can be overridden by a stanza more specific to the channel type, for example RcvSndBuffSize. If the value is set as zero, the operating system defaults are used. If no value is set, then the IBM MQ default, 32768, is used.
DistributedFrom Version 8.0, new queue managers are automatically created with a default setting of 0 (see Queue manager configuration files, qm.ini.
RcvBuffSize=number| 0
The size in bytes of the TCP/IP receive buffer used by the receiving end of channels. This stanza value can be overridden by a stanza more specific to the channel type, for example RcvRcvBuffSize. If the value is set as zero, the operating system defaults are used. If no value is set, then the IBM MQ default, 32768, is used.
DistributedFrom Version 8.0, new queue managers are automatically created with a default setting of 0 (see Queue manager configuration files, qm.ini.
RcvSndBuffSize=number| 0
The size in bytes of the TCP/IP send buffer used by the sender end of a receiver channel. If the value is set as zero, the operating system defaults are used. If no value is set, then the IBM MQ default, 32768, is used.
DistributedFrom Version 8.0, new queue managers are automatically created with a default setting of 0 (see Queue manager configuration files, qm.ini.
RcvRcvBuffSize=number| 0
The size in bytes of the TCP/IP receive buffer used by the receiving end of a receiver channel. If the value is set as zero, the operating system defaults are used. If no value is set, then the IBM MQ default, 32768, is used.
DistributedFrom Version 8.0, new queue managers are automatically created with a default setting of 0 (see Queue manager configuration files, qm.ini.
SvrSndBuffSize=number| 0
The size in bytes of the TCP/IP send buffer used by the server end of a client-connection server-connection channel. If the value is set as zero, the operating system defaults are used. If no value is set, then the IBM MQ default, 32768, is used.
DistributedFrom Version 8.0, new queue managers are automatically created with a default setting of 0 (see Queue manager configuration files, qm.ini.
SvrRcvBuffSize=number| 0
The size in bytes of the TCP/IP receive buffer used by the server end of a client-connection server-connection channel. If the value is set as zero, the operating system defaults are used. If no value is set, then the IBM MQ default, 32768, is used.
DistributedFrom Version 8.0, new queue managers are automatically created with a default setting of 0 (see Queue manager configuration files, qm.ini.
[Windows]LU62 ( IBM MQ for Windows only)
Use the LU6.2 queue manager properties page from the IBM MQ Explorer, or the LU62 stanza in the qm.ini file, to specify SNA LU 6.2 protocol configuration parameters.
TPName
The TP name to start on the remote site.
Library1= DLLName 1
The name of the APPC DLL.

The default value is WCPIC32.

Library2= DLLName2
The same as Library1, used if the code is stored in two separate libraries.

The default value is WCPIC32.

[Windows]NETBIOS ( IBM MQ for Windows only)
Use the Netbios queue manager properties page from the IBM MQ Explorer, or the NETBIOS stanza in the qm.ini file, to specify NetBIOS protocol configuration parameters.
LocalName= name
The name by which this machine is known on the LAN.
AdapterNum= 0 | adapter_number
The number of the LAN adapter. The default is adapter 0.
NumSess= 1 | number_of_sessions
The number of sessions to allocate. The default is 1.
NumCmds= 1 | number_of_commands
The number of commands to allocate. The default is 1.
NumNames= 1 | number_of_names
The number of names to allocate. The default is 1.
Library1= DLLName1
The name of the NetBIOS DLL.

The default value is NETAPI32.

[Windows]SPX ( IBM MQ for Windows only)
Use the SPX queue manager properties page from the IBM MQ Explorer, or the SPX stanza in the qm.ini file, to specify SPX protocol configuration parameters.
Socket= 5E86 | socket_number
The SPX socket number in hexadecimal notation. The default is X'5E86'.
BoardNum= 0 | adapter_number
The LAN adapter number. The default is adapter 0.
KeepAlive=NO|YES
Switch the KeepAlive function on or off.

KeepAlive=YES causes SPX to check periodically that the other end of the connection is still available. If it is not, the channel is closed.

Library1= DLLName1
The name of the SPX DLL.

The default is WSOCK32.DLL.

Library2= DLLName2
The same as LibraryName1, used if the code is stored in two separate libraries.

The default is WSOCK32.DLL.

ListenerBacklog=number
Override the default number of outstanding requests for the SPX listener.

When receiving on SPX, a maximum number of outstanding connection requests is set. This can be considered to be a backlog of requests waiting on the SPX socket for the listener to accept the request. The default listener backlog values are shown in Table 2.

Table 2. Default outstanding connection requests (SPX)
Platform Default ListenerBacklog value
Windows Server 100
Windows Workstation 5
Note: Some operating systems support a larger value than the default shown. Use this to avoid reaching the connection limit.

Conversely, some operating systems might limit the size of the SPX backlog, so the effective SPX backlog could be smaller than requested here.

If the backlog reaches the values shown in Table 2, the SPX connection is rejected and the channel cannot start. For message channels, this results in the channel going into a RETRY state and retrying the connection at a later time. For client connections, the client receives an MQRC_Q_MGR_NOT_AVAILABLE reason code from MQCONN and should retry the connection at a later time.