Converting an Existing Production Server to a Plex Environment
To convert an existing production IBM® Connect:Direct® Stand-alone Server into a IBM Connect:Direct/Plex environment:
Procedure
- Copy the existing INITPARMs member into $CD.PLEX.INITPARM as member CDPLX.
- Copy the existing IBM Connect:Direct Stand-alone Server startup JCL into $CD.PLEX.JCL as member CDMGR.
- Change the network map source to specify new APPLIDs for
the LOCAL.NODE and the PNODE/SNODE ADJACENT.NODE.
The existing APPLIDs are used for the IBM Connect:Direct SERVER1, which means that you do not need to change the connections to external IBM Connect:Direct systems.
- 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.
- You can add the following optional parameters to the CDPLX
member in $CD.PLEX.INITPARM.
- CDPLEX.TIMER = 5 | number of minutes specifies the time-out value for XCF communications in minutes.
- CDPLEX.WLM.GOAL = (NO | YES) specifies whether IBM Workload Manager (WLM) Goal Mode queries are made. This parameter is optional.
Note: Second sub parameter exitname has been deprecated from 6.3 release onwards. It will be ignored with a warning message SITA994I if its mentioned. - Create the local initialization parameter files for each IBM Connect:Direct/Plex
member:
- Copy the DGAITMGR, DGAISRV1, and DGAISRV2 sample local initialization parameters members from the IBM Connect:Direct $CD.SDGAPARM library into $CD.PLEX.INITPARM as members MANAGER, SERVER1, and SERVER2.
- Change the TCP.LISTEN parameter (following in bold)
to specify the TCP/IP stack address that is used by the IBM Connect:Direct Manager.
You do not need to change any other parameters in the MANAGER member.
CDPLEX.MANAGER=YES TCP.LISTEN=(nnn.nnn.nnn.nnn,port) CDPLEX.SERVER.JOBDSN=$CD.PLEX.JCL CDPLEX.SERVER.JOBMEM=((CDSRV1,SERVER1), - (CDSRV2,SERVER2))
- Change the CDPLEX.VTAM parameter in the SERVER1 member
as follows:
- Replace the applid11 value with the VTAM APPLID that is defined in the existing network map for SNA copy Processes.
- Replace the applid12 value with the VTAM APPLID that is defined
in the existing network map for the PNODE-SNODE APPLID.
These APPLIDs must be unique across the IBM Connect:Direct/Plex environment and cannot be the same as specified in the new network map.
CDPLEX.MANAGER=NO CDPLEX.SERVER=SERVER1 CDPLEX.VTAM=(applid11,applid12) CDPLEX.PLEXCLASSES=(TAPE,*) TCP.LISTEN=(nnn.nnn.nnn.nnn,port)
- The TCP.LISTEN initialization parameters specifies the TCP 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 Building, Modifying, and Submitting Processes in the IBM Connect:Direct for z/OS User Guide for more information on using PLEXCLASS in a Process.)
- Change the CDPLEX.VTAM parameter in the SERVER2 member
as follows:
- Replace the applid21 value with a new VTAM APPLID you have defined for SNA copy Processes.
- Replace the applid22 value with a new VTAM APPLID you have defined
for the PNODE-SNODE APPLID.
These APPLIDs must be unique across the IBM Connect:Direct/Plex environment and cannot be the same as specified in the new network map or used for SERVER1.
CDPLEX.MANAGER=NO CDPLEX.SERVER=SERVER1 CDPLEX.VTAM=(applid21,applid22) CDPLEX.PLEXCLASSES=(*) TCP.LISTEN=(nnn.nnn.nnn.nnn,port)
- The TCP.LISTEN initialization parameters specify the TCP listen address and port number combinations. Use a different listen port number than the one used in the existing initialization parameters file.
- Add the CDPLEX DD statement in the following example to
the CDMGR member in $CD.PLEX.JCL (this JCL is the startup JCL copied
earlier).
//DTF EXEC DGADINIT, // PARM='$CD.PLEX.INITPARM(CDPLX)' //CDPLEX DD DISP=SHR,DSN=$CD.PLEX.INITPARM(MANAGER)
- Create the CDSRV1 member and copy CDMGR 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 the 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: You can route jobs to a different z/OS image by specifying the local node name of the other system name in an XEQ statement in the IBM Connect:Direct Manager or Server JCL as follows:This example routes the job to the z/OS image identified by the local node name NJENODE./*XEQ njenode [JES2] //*ROUTE XEQ njenode [JES3]
- Submit the CDMGR JCL to bring up IBM Connect:Direct/Plex.
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 the IBM Connect:Direct Manager
initializes, use the IUI to signon to the IBM Connect:Direct Manager.
You can then submit Processes and perform other functions through the IUI.