Solaris stand-alone: Install DB2 for z/OS

View information on how to install DB2 for z/OS for use with IBM WebSphere Portal.

The following prerequisites must exist separately from the WebSphere Portal installation:

• If we are using the DB2 Legacy Type 2 JDBC driver, configure your DB2 Connect client with the following commands:

  db2 update dbm cfg using tp_mon_name WAS

  db2 update dbm cfg using spm_name hostname, where hostname is the host name for the machine where the DB2 Connect client is installed (same as portal machine).

• If we are using the DB2 Legacy Type 2 JDBC driver, enable extended shared memory usage with the following commands:

  export EXTSHM=ON
  db2set DB2ENVLIST=EXTSHM
  db2start
  

  To make the change permanent, add the environment variable by adding the following to the profile.env file:

  DB2ENVLIST='EXTSHM'
  

  in /home/db2inst/sqllib/userprofile add:

  export EXTSHM=ON
  

  The shell must be reopened before restarting DB2 for z/OS.

• Both type 2 and type 4 drivers are supported. If we are using the DB2 Legacy Type 2 JDBC driver, the DB2 Connect client must be installed on the same machine as WebSphere Portal to connect to the remote database.

• The DB2 subsystem must be on a supported z/OS platform.

• Update the BP8K0 catalog bufferpool to 35,000 buffers before performing database transfer. You should change this value based on the environment. The SYSIBM.SYSDATABASE table resides in this bufferpool and is used extensively by DB2 for z/OS during database transfer.

To use DB2 for z/OS as the database software for WebSphere Portal, you must have DB2 for z/OS installed on your z/OS system. Refer to the DB2 for z/OS product documentation for instructions. Refer to the Planning for DB2 for z/OS topic for additional considerations for configuring DB2 for z/OS as the WebSphere Portal database.

Parent: Solaris stand-alone: Prepare DB2 for z/OS
Next: Solaris stand-alone: Modify properties for DB2 for z/OS