DB2 for z/OS and WebSphere: The Perfect Couple

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:

򐂰 DB2xx.SDSNEXIT

򐂰 DB2xx.SDSNLOAD

򐂰 DB2xx.SDSNLOD2

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

procedure.

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 Setup

//*

//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

page 71).

Chapter 3. WebSphere - DB2 environment 71

Figure 3-26 Start command and arguments for Servant

The required libraries can also be specified by using the Export function of Unix System

Services. This has to be done via the Custom Property settings of the Servant.

Go to Servers

→ Application Servers → Server-name → Process Definition → Servant.

In the this panel, select Environment Entries at the bottom (Figure 3-27).

Figure 3-27 Environment entries

A new environment variable has to added, or changed if already existing (Figure 3-28 on

page 72).

Note: In a Base Node (BN) configuration, WAS V5 application servers cannot be started

and stopped via the Administrative Console.

72 DB2 for z/OS and WebSphere: The Perfect Couple

Figure 3-28 New environment entry

Fill in the name and the value for the new variable (Figure 3-29); in our case:

STEPLIB=$STEPLIB:DB2xx.SDSNEXIT:DB2xx.SDSNLOAD:DB2xx.SDSNLOD2

Figure 3-29 Adding the STEPLIB variable

Save the configuration, and we are done.

This concludes the definition of the type 2 driver for DBD8.

Note again that we can only associate one DB2 system when using type 2 connectivity per

Application Server. This is because we have to specify the JVM System property

db2.jcc.propertiesFile, by which we have to point to the properties file that will be used by the

Note: The header of the panel is Custom Properties, whereas in fact you are defining

environment variables, so do not let the heading mislead you.

Attention: The previous approach for adding the DB2 libraries to an Application Server

has not been verified. We experienced time outs in the Admin Console application after the

above changes had been made.