How to use the communication examples
The following chapters contain example configurations:
- MQSeries for OS/2 Warp
- IBM WebSphere MQ for Windows
- IBM WebSphere MQ for AIX
- IBM MQSeries for Compaq Tru64 UNIX
- IBM WebSphere MQ for HP-UX
- IBM MQSeries for AT&T GIS UNIX, V2.2
- IBM WebSphere MQ for Solaris
- IBM WebSphere MQ for z/OS
- IBM WebSphere MQ for iSeries
- MQSeries for VSE/ESA
- IBM WebSphere MQ for z/OS using CICS
- WebSphere MQ for z/OS using queue-sharing groups
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, 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.
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.
IT responsibilities
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.
- System administrator is used to describe the person (or group of people) who installs and configures the software for a specific platform.
- Network administrator is used to describe the person who controls LAN connectivity, LAN address assignments, network naming conventions, and so on. This person may be in a separate group or may be part of the system administration group.
- A specific type of administrator, for example CICS administrator is indicated in cases where we can more clearly describe the responsibilities of the person.
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.
WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.
IBM is a trademark of the IBM Corporation in the United States, other countries, or both.