Install DB2 for z/OS

Use this information to install DB2 for z/OS for use with IBM WebSphere Portal.

• Review the database considerations.

• ensure the DB is supported by this version of WebSphere Portal. Refer to the list of supported databases in the WebSphere Portal detailed system requirements.

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

• Ensure that Java Database Connectivity requirements are met. Consult the following references:

  • DB2 Universal Database for OS/390 and z/OS: Application Programming Guide and Reference for Java

  • The IBM Redbooks publication, DB2 for z/OS and OS/390: Ready for Java SG24-6435-00.

• If the current version of WebSphere Portal and an earlier version coexist with the same DB2 for z/OS subsystem, the database user IDs for the current version must be different from the earlier version to avoid conflicts during installation. If the two versions of WebSphere Portal connect to two different DB2 for z/OS subsystems, using the same user ID does not cause conflict.

1. To use DB2 for z/OS as the database software for WebSphere Portal, we must have DB2 for z/OS installed on your z/OS system. Refer to the DB2 for z/OS product documentation for instructions.

2. Read the Planning for DB2 for z/OS topic before configuring DB2 for z/OS as the WebSphere Portal database.

3. Check the buffer pool allocations for the system and define the buffer pools as appropriate for the installation and define a large enough size.
   -db2 display bufferpool(bp2) -db2 alter bufferpool(bp2) vpsize(15000)

   1. Repeat for extra buffer pools as needed. For example:

      • bp3

      • bp4

      • bp5

      • bp32k1

      • bp32k2

4. Update the BP8K0 catalog buffer pool to 35,000 buffers before you transfer the database. Change this value according to our environment. The SYSIBM.SYSDATABASE table is in this buffer pool and is used extensively by DB2 for z/OS for the database transfer.

5. Change the Common Service Area (CSA) setting to 3500,350000. Read the appropriate DB2 for z/OS topic for complete information about calculating and setting CSA:

   • DB2 for z/OS Version 10.1, Common service area

   • DB2 for z/OS Version 11.1, Common service area storage requirements

6. During database transfer from Derby to DB2 for z/OS, a supporting low-order byte table space is created for the database tables that store documents. The PRIQTY and SECQTY for the table space are assigned with the default values. If we plan to store many documents, use an automatic class selection (ACS) routine to allocate the DB2 for z/OS data sets with a primary and secondary space allocation of at least 10 cylinders. Or, specify a large enough value for PRIQTY and SEQTY in the DB2 DSNTIJUZ member. The table spaces can be identified by their name, having a structure like JCRDB.Sxxxxxxx, where xxxxxxx is a system-assigned combination of seven numbers and characters.

   1. Also, in member DSNTIJUZ, update the following parameters and then verify DSNTIJUZ runs successfully.

      • edmdbdc = 204800

      • edmpool=409600

      • edmstmtc=204800

      • rrulock=no

      • cachedyn=yes (prepared, dynamic SQL statements are cached)

      • dbacrvw=yes (to allow database administrators to create Views)

      • +++tbsbpxml=BP16K1 (to explicitly create an XML table space. This value can be changed to any valid 16 K buffer pool where the Administrative User has the USE privilege.)

7. Verify the job DSNTIJSG ran to create the objects required for the DB2 JDBC and ODBC metadata methods. See the DB2 Installation Guide Enable stored procedures and tables for JDBC and ODBC support.

8. Ensure that job DSNTIJMS runs successfully (re-execute binds).

9. Ensure that job DSNTIJEX runs successfully.

10. Because large objects are stored in columns that can become large, logging changes to these columns requires a huge amount of log space. For this reason, large object (LOB) logging is disabled by default for table spaces containing such data. With LOB logging disabled, we can recover full backups, but not incremental backups that can be used for point in time recovery. To recover point in time backups, enable LOB logging. For detailed instructions, see technote 1306637, Manage LOB logging in DB2 for z/OS.

LikeMinds

11. If we intend to run the LikeMinds sample, increase the NUMLKTS and NUMLKUS parameters: Ten times the default is sufficient, more depending on the usage of the sample. For example, if NUMLKTS=1000 and NUMLKUS=10000 are the installation default values, then update these values to NUMLKTS=10000 and NUMLKUS=100000.

12. 
    

Type 2 driver configuration

13. If we are planning to use Type 2 driver with DB2 for z/OS Version 9.1.2, ensure that DB2 for z/OS APAR PK58105 is installed.

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

    export EXTSHM=ON
    db2set DB2ENVLIST=EXTSHM
    db2start

    For permanent changes, add the environment variable to the profile.env file:
    DB2ENVLIST='EXTSHM'

    in /home/db2inst/sqllib/userprofile add:

    export EXTSHM=ON

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

15. If we are using the older DB2 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 server where the DB2 Connect client is installed (same as portal server).\

16. If we are using the older DB2 Type 2 JDBC driver, install the DB2 Connect client on the WebSphere Portal server to connect to the remote database.

What to do next

Use the Configuration Wizard to set up and configure the database to work with WebSphere Portal. Use the wizard to create custom scripts that you or the database administrator can use to configure the database. We can also use the wizard to automatically set up and configure the database. The wizard creates instructions and scripts based on the selections and provided data.

When we use the Configuration Wizard and provide information about the database, consider the following points:

• To use a single DB2 for z/OS subsystem to hold data for more multiple installations, use the same user name but a separate schema name for each database domain. For Member Manager, the user name must match the schema; the same database user cannot be used for the Member Manager databases of two distinct portal installations.

• Each portal installation must be in separate and distinct WebSphere Application Server cells. If the portals are installed in the same file system, each must be installed in a separate and unique directory. If the portals are installed in different file systems, the same directory name can be used.

• In a remote database environment, WebSphere Portal and DB2 Connect are installed on one server (the local server) and the DB2 for z/OS server is installed on a separate server (the remote server).

• Before we enter the database name (dbdomain.DbName) in the Configuration Wizard, check the database documentation for restrictions on character length.

Parent Install the database software