Set up communication on Windows

Set up communication on Windows

When a distributed-queuing management channel is started, it tries to use the connection specified in the channel definition. For this to succeed, it is necessary for the connection to be defined and available. This section explains how to do this by using the forms of communication available for IBM MQ for Windows systems.

Before you begin

You might find it helpful to refer to Example configuration - IBM MQ for Windows.

About this task
When setting up communication for IBM MQ on Windows, we can choose from the following types of communication:

TCP/IP
LU 6.2
NetBIOS

Defining a TCP connection on Windows
Define a TCP connection by configuring a channel at the sending end to specify the address of the target, and by running a listener program at the receiving end.
Defining an LU 6.2 connection on Windows
SNA must be configured so that an LU 6.2 conversation can be established between the two machines.
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.
Parent topic: Monitor and controlling channels on UNIX, Linux, and Windows

Related tasks

Monitor and controlling channels on UNIX, Linux, and Windows
Configure connections between the server and client
Set up communication on UNIX and Linux

Related reference

Which communication type to use