Configuration Example Using Two IBM Connect:Direct for z/OS Systems
This configuration describes a more complex IBM® Connect:Direct®/Plex configuration. It assumes that the following IBM Connect:Direct environment exists.
In this environment, two Connect:Direct for UNIX nodes (UNIX.CD and UNIX.CD2) communicate with two different IBM Connect:Direct for z/OS® systems (ZOS.CD and ZOS.CD2).
To change this setup to a IBM Connect:Direct/Plex, the ZOS.CD and ZOS.CD2 systems are merged into a single IBM Connect:Direct/Plex. ZOS.CD is designated as the IBM Connect:Direct Manager and SERVER1, while ZOS.CD2 is designated as the IBM Connect:Direct Server SERVER2. (See Converting Two Existing Stand-Alone Server Systems to a Plex Environment for more information.)
The initialization parameter CDPLEX.SERVER.NODE=ZOS.CD2 is added to the SERVER2 local initialization parameter (callout 1). USE.SERVER.NODE=YES is added to the IBM Connect:Direct/Plex network map adjacent node definitions (callout 2).
The advantages of this approach are:
- Changes to the z/OS nodes have no affect on the Connect:Direct for UNIX nodes. Therefore, no changes are required to the Connect:Direct for UNIX nodes.
- You can perform workload balancing on Processes sent from ZOS.CD to the Connect:Direct for UNIX nodes.
- The IBM Connect:Direct/Plex provides a single administrative and operating environment.
The disadvantage of this approach is that you must manually balance Processes coming from the Connect:Direct for UNIX nodes.