70 DB2 for z/OS and WebSphere: The Perfect Couple
3.5.6 Linking to the DB2 libraries
The application server also requires access to three DB2 libraries:
Allowing DB2 to access these libraries can be done in several ways:
The libraries can be placed in the LINKLIST of the z/OS operating system.
The libraries are added to the JCL of the startup procedure of the Application Server
Servant. This can easily be done with a JCL INCLUDE statement from the main start
In the procedure shown in Example 3-2, which is the start procedure for an Application
Server Servant, besides the ENV parameter, a parameter named Z is used. It points to an
include member, shown in Example 3-3.
Example 3-2 Start procedure for Servant
//WS5541S PROC ENV=CL541.ND541.WS541,Z=WS5541SZ
// SET ROOT='/WebSphereBS/V5R0M0/BS01'
//BBOSR EXEC PGM=BBOSR,REGION=0M,TIME=NOLIMIT,
// PARM='TRAP(ON,NOSPIE),ENVAR("_EDC_UMASK_DFLT=007") /'
//BBOENV DD PATH='&ROOT/&ENV/was.env'
// INCLUDE MEMBER=&Z
In the included member, the DB2 libraries have to be added.
Example 3-3 included member with updated STEPLIB for DB2 V8
//* Output DDs
//CEEDUMP DD SYSOUT=*,SPIN=UNALLOC,FREE=CLOSE
//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=DB2D8.SDSNEXIT
// DD DISP=SHR,DSN=DB2D8.SDSNLOAD
// DD DISP=SHR,DSN=DB2D8.SDSNLOD2
The value of the Z parameter, which in the example has a default, can be overridden also via
the Administrative Console application to point to another include member.
To do this, go to Application Servers
→ Servername → Process Definition → Servant
and change, as appropriate, the property value of startCommandArgs (Figure 3-26 on