Running the example

Once these definitions have been created, you need to:

• Start the channel initiator on each queue manager.
• Start the INETD daemon for each queue manager. On OS/2, Windows, and Compaq NonStop Kernel, you can use the WebSphere MQ listener in place of INETD.

For information about starting the channel initiator and listener, see Chapter 10, Setting up communication for OS/2 and Windows and Chapter 13, Setting up communication in UNIX systems.

Note:

On OS/2 and Windows, you can also run the channel as a thread; see the WebSphere MQ Script (MQSC) Command Reference book for information about how to define a channel as a threaded channel.

Expanding this example

This simple example could be expanded with:

• The use of LU 6.2 communications for interconnection with CICS systems, and transaction processing.
• Adding more queue, process, and channel definitions to allow other applications to send messages between the two queue managers.
• Adding user-exit programs on the channels to allow for link encryption, security checking, or additional message processing.
• Using queue-manager aliases and reply-to queue aliases to understand more about how these can be used in the organization of your queue manager network.