Home

 

Establishing a NetBIOS connection

 

A NetBIOS connection is initiated from a queue manager that uses the ConnectionName parameter on its channel definition to connect to a target listener. To set up a NetBIOS connection, follow these steps:

  1. At each end of the channel specify the local NetBIOS name to be used by the WebSphere MQ channel processes, in the Windows registry or in the queue manager configuration file qm.ini. For example, the NETBIOS stanza in the Windows registry at the sending end might look like this:
    NETBIOS:
     LocalName=WNTNETB1
    and at the receiving end:
    NETBIOS:
     LocalName=WNTNETB2

    Each WebSphere MQ process must use a different local NetBIOS name. Do not use your machine name as the NetBIOS name because Windows already uses it.

  2. At each end of the channel, verify the LAN adapter number being used on your system. The WebSphere MQ for Windows default for logical adapter number 0 is NetBIOS running over a TCP/IP network. To use native NetBIOS we need to select logical adapter number 1. See Establishing the LAN adapter number.

    Specify the correct LAN adapter number in the NETBIOS stanza of the the Windows registry. For example:

    NETBIOS:
     AdapterNum=1

  3. So that sender channel initiation will work, specify the local NetBIOS name via the MQNAME environment variable:
     SET MQNAME=WNTNETB1I

    This name must be unique.

  4. At the sending end, define a channel specifying the NetBIOS name being used at the other end of the channel. For example:
    DEFINE CHANNEL (WINNT.OS2.NET) CHLTYPE(SDR) +
           TRPTYPE(NETBIOS) +
           CONNAME(WNTNETB2) +
           XMITQ(OS2) +
           MCATYPE(THREAD) +
           REPLACE

    You must specify the option MCATYPE(THREAD) because, on Windows, sender channels must be run as threads.

  5. At the receiving end, define the corresponding receiver channel. For example:
    DEFINE CHANNEL (WINNT.OS2.NET) CHLTYPE(RCVR) +
           TRPTYPE(NETBIOS) +
           REPLACE

  6. Start the channel initiator because each new channel is started as a thread rather than as a new process.
    runmqchi

  7. At the receiving end, start the WebSphere MQ listener:
    runmqlsr -t netbios

    Optionally you may specify values for the queue manager name, NetBIOS local name, number of sessions, number of names, and number of commands. See Defining a NetBIOS connection for more information about setting up NetBIOS connections.

 

Parent topic:

Example configuration - IBM WebSphere MQ for Windows


ic13100_


 

Home