Setting Up a New IBM Connect:Direct/Plex Environment
To set up a IBM® Connect:Direct®/Plex environment:
- Create a PDS (which will be referred to as $CD.PLEX.INITPARM in this procedure) to hold the initialization parameters for the IBM Connect:Direct Plex environment, with sufficient directory space to handle ISPF Statistics. Create a PDS (which will be referred to as $CD.PLEX.JCL) to hold the JCL.
- Copy your current DTF's INITPARM member into $CD.PLEX.INITPARM as member CDPLX.
- Copy your current IBM Connect:Direct Stand-alone Server startup JCL into $CD.PLEX.JCL as member CDMGR.
- Add the following initialization parameters to the CDPLX
member in $CD.PLEX.INITPARM. This member becomes the IBM Connect:Direct/Plex
global initialization parameters file.
CDPLEX=YES CDPLEX.MAXSERVER = number of servers | 4 XCF.NAME=8-char-name
The CDPLEX=YES parameter indicates a IBM Connect:Direct/Plex environment. It also directs the DTF to read its local initialization parameters from the file specified in the //CDPLEX DD statement in the startup JCL.
The CDPLEX.MAXSERVER parameter specifies the maximum number of servers the Connect:Direct/Plex Manager will manage. For more information, see Storage Requirements in a IBM Connect:Direct Environment in the IBM Connect:Direct for z/OS® Configuration Guide.
The XCF.NAME parameter specifies a unique name used by the z/OS Cross Systems Communication Facility (XCF) to assist communications among IBM Connect:Direct/Plex members. This name indicates that the IBM Connect:Direct Manager and IBM Connect:Direct Servers are part of the same XCF group.
- Add the following optional parameters to the CDPLX member
in $CD.PLEX.INITPARM.
- CDPLEX.TIMER specifies the time-out value for XCF communications in minutes.
- CDPLEX.WLM.GOAL specifies whether IBM Workload Manager (WLM) Goal Mode queries are made. This parameter is optional.
- Create a local initialization parameters file for the IBM Connect:Direct Manager:
- Copy the MANAGER sample local initialization parameters member from the IBM Connect:Direct installation $CD.SDGAPARM(DGAIPMGR) into $CD.PLEX.INITPARM.
- Change the TCP.LISTEN parameter of the MANAGER member
to specify the TCP/IP stack address used by the IBM Connect:Direct Manager.
CDPLEX.MANAGER=YES TCP.LISTEN=(nnn.nnn.nnn.nnn,port) CDPLEX.SERVER.JOBDSN=$CD.PLEX.JCL CDPLEX.SERVER.JOBMEM=((CDSRV1,SERVER1), - (CDSRV2,SERVER2))
- Create a local initialization parameters file for IBM Connect:Direct SERVER1:
- Copy the sample local initialization member $CD.SDGAPARM(DGAISRV1), into $CD.PLEX.INITPARM as member SERVER1.
- Change the CDPLEX.VTAM parameter in the SERVER1 member
as follows:
- Replace the applid11 value with the VTAM APPLID used by this IBM Connect:Direct Server for SNA (Node to Node/PROCESS use, as opposed to API use).
- Replace the applid12 value with the PNODE-SNODE APPLID.
These APPLIDs must be unique across the IBM Connect:Direct/Plex environment and cannot be the same as those specified in the network map.
CDPLEX.MANAGER=NO CDPLEX.SERVER=SERVER1 CDPLEX.VTAM=(applid11,applid12) CDPLEX.PLEXCLASSES=(TAPE,*) TCP.LISTEN=(nnn.nnn.nnn.nnn,port) UDT33.LISTEN=(nnn.nnn.nnn.nnn,port)
The TCP.LISTEN and UDT33.LISTEN initialization parameters specify the TCP and UDT listen address and port number combinations. Use a different listen port number than the one used in the existing initialization parameters file.
Note: The CDPLEX.PLEXCLASSES parameter in SERVER1 specifies a ‘TAPE' PLEXCLASS. For Processes that require tape drives, specify the ‘TAPE' PLEXCLASS in their Process definitions. These Processes run on SERVER1. (See the chapters about building Processes and controlling Processes in the TCQ in IBM Connect:Direct for z/OS User Guide for more information on using PLEXCLASS in a Process.)
- Create a local initialization parameters file for IBM Connect:Direct SERVER2:
- Copy the sample local initialization member $CD.SDGAPARM(DGAISRV2), into $CD.PLEX.INITPARM as member SERVER2.
- Change the CDPLEX.VTAM parameter in the SERVER2 member
as follows:
- Replace the applid21 value with the VTAM APPLID used by this IBM Connect:Direct Server for SNA copy Processes.
- Replace the applid22 value with the PNODE-SNODE APPLID.
These APPLIDs must be unique across the IBM Connect:Direct/Plex environment and cannot be the same as those specified in the network map.
CDPLEX.MANAGER=NO CDPLEX.SERVER=SERVER2 CDPLEX.VTAM=(applid21,applid22) CDPLEX.PLEXCLASSES=(*) TCP.LISTEN=(nnn.nnn.nnn.nnn,port) UDT33.LISTEN=(nnn.nnn.nnn.nnn,port)
- Add the CDPLEX DD statement in the following example to
the CDMGR member in $CD.PLEX.JCL.
This statement directs the startup JCL to the global initialization parameters file.
//DTF EXEC DGADINIT, // PARM='$CD.PLEX.INITPARM(CDPLX)' //CDPLEX DD DISP=SHR,DSN=$CD.PLEX.INITPARM(MANAGER)
- Create CDSRV1 in $CD.PLEX.JCL and copy the CDMGR member into it.
- Make the following changes to the CDSRV1 member:
- Change the job name so that this job can run simultaneously with the CDMGR JCL.
- Change the member name in the CDPLEX DD statement to
SERVER1, as follows. This change directs the CDSRV1 JCL to its local
initialization parameters file.
//CDPLEX DD DISP=SHR,DSN=$CD.PLEX.INITPARM(SERVER1)
- Create a CDSRV2 member and copy CDSRV1 into it.
- Make the following changes to the CDSRV2 member:
- Change the job name so that this job can run simultaneously with the CDMGR JCL and CDSRV1 JCL.
- Change the member name in the CDPLEX DD statement to
SERVER2, as follows. This change directs the CDSRV2 JCL to its local
initialization parameters file.
//CDPLEX DD DISP=SHR,DSN=$CD.PLEX.INITPARM(SERVER2)
Note: Route jobs to a different z/OS image by specifying the local node name of the other system in an XEQ statement in the IBM Connect:Direct Manager or Server startup JCL, as follows:/*XEQ njenode [JES2] //*ROUTE XEQ njenode [JES3]
This example routes the job to the z/OS image identified by the local node name NJENODE.
- Submit the CDMGR JCL to bring up the IBM Connect:Direct/Plex
server.
After the IBM Connect:Direct Manager initializes, it submits the CDSRV1 JCL and CDSRV2 JCL to bring up the two IBM Connect:Direct Servers.
- After IBM Connect:Direct Manager
initializes, use the IUI to signon.
You can then submit Processes and perform other functions through the IUI.