Quick Beginnings for DB2 Connect Enterprise Edition

Configuration Requirements for SYSPLEX

1. On the DB2 Connect EE gateway, SYSPLEX exploitation is enabled by default (it can be turned off by setting the DB2SYSPLEX_SERVER profile variable to the value zero).

2. SYSPLEX exploitation will not be used for a given database unless the DCS directory entry for that database contains "SYSPLEX" (not case-sensitive) in the 6th positional parameter.

3. For APPC connections, these additional considerations apply:

   1. A Partner LU definition must exist for each LU that is a DB2 for OS/390 participant in the SYSPLEX.

   2. Matching CPIC symbolic destination name profiles must be defined for each participant, each having the same name as the related LU.

   Therefore, in this scenario, the SNA subsystem that the DB2 Connect gateway uses, must contain:

   1. A Partner LU profile for NETB.LUB, referenced from a CPIC symbolic destination profile called LUB

   2. A Partner LU profile for NETC.LUC, referenced from a CPIC symbolic destination profile called LUC.

4. For the scenario described below, only the primary DB2 for OS/390 database (LOCATION_NAME_B) need be defined in the catalog on the DB2 Connect gateway system, as follows:

   	db2 catalog  appc node nodeb remote lub security program
   	db2 catalog dcs database dbb as location_name_b parms ',,,,,sysplex'
   	db2 catalog database dbb as aliasb at node nodeb authentication dcs  
   

   No DB2 directory entries need be defined in the catalog on the DB2 Connect gateway machine in order to reach the database LOCATION_NAME_C, since it is a secondary participant in the SYSPLEX . However, the symbolic destination name "luc" must reference the Partner LU definition for NETB.LUC since an APPC connection is being used.

[ DB2 List of Books | Search the DB2 Books ]