Priming DB2

This is part of the larger task of creating a broker on z/OS. The broker uses DB2 tables to hold its internal data. These tables are defined in table spaces, which in turn, are defined within a DB2 database.

Data from tables is accessed through in-memory buffer pools, and typically you have different buffer pools for:
  • Different applications
  • Indexes
  • Tables
  • LOB tables

The DASD volumes that can be used by a database are defined using a storage group (STOGROUP). Your DB2 systems administrator will tell you which buffer pools and storage groups to use.

The BIPCRDB job issues commands that require the following authorities:
  • CREATESG - to create a storage group
  • CREATEDBA - to create the database
Note that you might also need authority to grant use of a buffer pool.

If you have any problems with this job, you can edit and customize member BIPDLDB to delete the database. You can run the BIPCRDB job again when you have resolved the problems.

Before you start

Before starting this task, you must have completed Creating the environment file.

  1. Edit the BIPCRDB job.
  2. Start of changeReview and change the BUFFERPOOL and INDEXBP buffer pools on the CREATE DATABASE statementEnd of change
  3. Change the buffer pool specification on the CREATE LOB TABLESPACE statements to a value suitable for your enterprise.
  4. Submit BIPCRDB from your broker PDSE. You need the authority described earlier to submit the DB2 job.

    BIPCRDB creates the DB2 StorageGroup, Database, and Table Spaces but does not create any tables or indexes.

    The steps in the BIPCRDB job must complete with return code zero.

Related concepts
Brokers
Broker domains
Related tasks
Creating a broker on z/OS
Creating the environment file