Using Alternate Communication Paths to Define the IBM Connect:Direct/Plex

The advantages to this approach are you only have to define one entity, the IBM® Connect:Direct®/Plex, and then copy that same definition to the network maps of the non-Plex Servers and you can still use the NETMAP-checking feature.

To define a IBM Connect:Direct/Plex that has servers running on several hosts, you can use the ALT.COMM parameter in the network map of each non-Plex Server that will communicate with the IBM Connect:Direct/Plex.

  1. Specify USE.SERVER.NODE=NO in the IBM Connect:Direct/Plex network map entry of each non-Plex Server so that all servers in the IBM Connect:Direct/Plex environment appear as one node.
  2. Define the IBM Connect:Direct/Plex node as an adjacent node with all possible IP addresses of the hosts that the Manager can run on specified using the ALT.COMM definition.

    The following is an example of the ALT.COMM parameter:

     ADJACENT.NODE=(  -
         (CDMGR,1366,10.1.1.1,TCP,EXT,BOTH) -
         ENVIRONMENT=ZOS -
         PARSESS=(00000010 00000002) -
         ALT.COMM=(ALT.DIR=TOP               -
                   (ALT.ADDR=10.1.1.2,ALT.PORT=1366,-
                    ALT.TYPE=TCP ,  ALT.USE.OUT=NO )
                   (ALT.ADDR=10.1.1.3,ALT.PORT=1366,-
                    ALT.TYPE=TCP ,  ALT.USE.OUT=NO )
                   (ALT.ADDR=10.1.1.4,ALT.PORT=1366,-
                    ALT.TYPE=TCP ,  ALT.USE.OUT=NO )) -
    
  3. Copy this ALT.COMM definition and put it in the network map of each non-Plex Server that will communicate with the IBM Connect:Direct/Plex.