Defining a NetBIOS connection on Windows

A NetBIOS connection applies only to a client and server running Windows. IBM MQ uses three types of NetBIOS resource when establishing a NetBIOS connection to another IBM MQ product: sessions, commands, and names. Each of these resources has a limit, which is established either by default or by choice during the installation of NetBIOS.

Each running channel, regardless of type, uses one NetBIOS session and one NetBIOS command. The IBM NetBIOS implementation allows multiple processes to use the same local NetBIOS name. Therefore, only one NetBIOS name needs to be available for use by IBM MQ. Other vendors' implementations, for example Novell's NetBIOS emulation, require a different local name per process. Verify we requirements from the documentation for the NetBIOS product we are using.

In all cases, ensure that sufficient resources of each type are already available, or increase the maximums specified in the configuration. Any changes to the values requires a system restart.

During system startup, the NetBIOS device driver displays the number of sessions, commands, and names available for use by applications. These resources are available to any NetBIOS-based application that is running on the same system. Therefore, it is possible for other applications to consume these resources before IBM MQ needs to acquire them. Your LAN network administrator should be able to clarify this for you.

• Defining the IBM MQ local NetBIOS name
  The local NetBIOS name used by IBM MQ channel processes can be specified in three ways.
• Establishing the queue manager NetBIOS session, command, and name limits
  The queue manager limits for NetBIOS sessions, commands, and names can be specified in two ways.
• Establishing the LAN adapter number
  For channels to work successfully across NetBIOS, the adapter support at each end must be compatible. IBM MQ allows you to control the choice of LAN adapter (LANA) number by using the AdapterNum value in the NETBIOS stanza of our qm.ini file and by specifying the -a parameter on the runmqlsr command.
• Initiating the NetBIOS connection
  Defining the steps needed to initiate a connection.
• Defining the target listener for the NetBIOS connection
  Defining the steps to be undertaken at the receiving end of the NetBIOS connection.

Parent topic: Set up communication on Windows

Related concepts

• Defining the IBM MQ local NetBIOS name
• Establishing the queue manager NetBIOS session, command, and name limits
• Establishing the LAN adapter number
• Initiating the NetBIOS connection
• Defining the target listener for the NetBIOS connection