78 DB2 for z/OS and WebSphere: The Perfect Couple
//SYSOUT DD SYSOUT=*,SPIN=UNALLOC,FREE=CLOSE
//SYSPRINT DD SYSOUT=*,SPIN=UNALLOC,FREE=CLOSE
//STEPLIB DD DISP=SHR,DSN=BBO5S54.SBBOLD2
// DD DISP=SHR,DSN=BBO5S54.SBBOLOAD
// DD DISP=SHR,DSN=DB2D7.SDSNEXIT
// DD DISP=SHR,DSN=DB2D7.SDSNLOAD
// DD DISP=SHR,DSN=DB2D7.SDSNLOD2
The new server does not have its own admin console application. All definitions, JDBC
providers, and data sources are always done via this prime server.
We also create a data source (for type 2 connectivity) for the second Application Server
ws541asc54 with JNDIname:
jdbc/T2DBD7 (DBD7 on Local via type2)
To do so, we can use the procedure outlined in “Defining Data Sources under this provider” on
3.6 Configuring Universal JDBC Driver type 4 connectivity
The type 4 driver is always some kind of a remote driver. It allows us to connect to a local
DB2 (on the same LPAR) or a remote DB2, but always over TCP/IP. The driver is a pure Java
driver, and therefore only composed of Java classes implementing the JDBC interfaces as
defined in the JDBC core specification. This makes it possible to use this driver in many
environments, including a browser with Applets; only a Java Virtual Machine is required. This
is also depicted in Figure 3-37 on page 79.
Attention: If we need access to two or more DB2 subsystems from within the same
Application Server, we have to use a mixture of T2 and T4 data sources.