The following chapters contain example configurations:
The information in the example-configuration chapters describes the tasks that were carried out on a single platform, to set up communication to another of the platforms, and then describes the WebSphere MQ tasks to establish a working channel to that platform. Wherever possible, the intention is to make the information as generic as possible. Thus, to connect any two WebSphere MQ queue managers on different platforms, you should need to refer to only the relevant two chapters. Any deviations or special cases are highlighted as such. Of course, you can also connect two queue managers running on the same platform (on different machines or on the same machine). In this case, all the information can be derived from the one chapter.
The examples only cover how to set up communications where clustering is not being used. For information about setting up communications while using clustering, see the WebSphere MQ Queue Manager Clusters book. The communications' configuration values given here still apply.
Each chapter contains a worksheet in which you can find the parameters used in the example configurations. There is a short description of each parameter and some guidance on where to find the equivalent values in your system. When you have a set of values of your own, record these in the spaces on the worksheet. As you proceed through the chapter, you will find cross-references to these values as you need them.
Notes:
Because the IT infrastructure can vary greatly between organizations, it is difficult to indicate who, within an organization, controls and maintains the information required to complete each parameter value. To understand the terminology used in the following chapters, consider the following guidelines as a starting point.
In most z/OS installations, there is a group responsible for updating the ACF/VTAM(R), ACF/NCP, and TCP/IP software to support the network configuration. The people in this group should be the main source of information needed when connecting any WebSphere MQ platform to WebSphere MQ for z/OS. They may also influence or mandate network naming conventions on LANs and you should verify their span of control before creating your definitions.
The example-configuration chapters do not attempt to indicate who is responsible for and able to set each parameter. In general, several different people may be involved.