Set up the Db2 environment
If we are using queue sharing groups create the required Db2 objects by customizing and running a number of sample jobs.
Set up the Db2 environment
We must create and bind the required Db2 objects by customizing and running a number of sample jobs.- Repeat this task for each Db2 data-sharing group.
- We need to perform the bind and grant steps when migrating from a previous version.
- Omit this task if we are not using queue sharing groups.
If you later want to use queue sharing groups, perform this task at that time.
The following steps must be performed for each new Db2 data-sharing group. All the sample JCL is in thlqual.SCSQPROC.
- Customize and execute sample JCL CSQ4XCSG to create the storage group that is to be used for the IBM MQ database, table spaces, and tables.
- Customize and execute sample JCL CSQ4XCDB to create the database to be used by all queue managers that are connecting to this Db2 data-sharing group.
- Customize and execute sample JCL CSQ4XCTS to create the table spaces that contain the queue manager and channel initiator tables used for queue sharing groups.
- Customize and execute sample JCL CSQ4XCTB to create the 15 Db2 tables and associated indexes. Do not change any of the row names or attributes.
- Customize and execute sample JCL CSQ45BPL to bind the Db2 plans for the queue manager, utilities, and channel initiator.
- Customize and execute sample JCL CSQ45GEX to grant execute authority to the plans
for the user IDs that are used by the queue manager, utilities, and channel initiator. The user IDs
for the queue manager and channel initiator are the user IDs under which their started task
procedures run. The user IDs for the utilities are the user IDs under which the batch jobs can be
submitted. The names of the appropriate plans are shown in the following table for the:
Long Term Support version in the
LTS column.
Continuous Delivery version in the CD column, where n represents the
CD release.
User Plans (LTS) Plans (CD) Queue manager CSQ5A 920,
CSQ5C 920,
CSQ5D 920,
CSQ5K 920,
CSQ5L 920,
CSQ5M 920,
CSQ5P 920,
CSQ5R 920,
CSQ5S 920,
CSQ5T 920,
CSQ5U 920,
CSQ5W 920
CSQ5A 9X0,
CSQ5C 9X0,
CSQ5D 9X0,
CSQ5K 9X0,
CSQ5L 9X0,
CSQ5M 9X0,
CSQ5P 9X0,
CSQ5R 9X0,
CSQ5S 9X0,
CSQ5T 9X0,
CSQ5U 9X0,
CSQ5W 9X0SDEFS function of the CSQUTIL batch utility CSQ52 920 CSQ52 9X0 CSQ5PQSG and CSQJUCNV batch utilities CSQ5B 920 CSQ5B 9X0 CSQUZAP service utility CSQ5Z 920 CSQ5Z 9X0
In the event of a failure during Db2 setup, the following jobs can be customized and executed:
- CSQ45DTB to drop the tables and indexes.
- CSQ4XDTS to drop the table spaces.
- CSQ4XDDB to drop the database.
- CSQ4XDSG to drop the storage group.
Note: If these jobs fail because of a Db2 locking problem it is probably due to contention for a Db2 resource, especially if the system is being heavily used. Resubmit the jobs later. It is preferable to run these jobs when the system is lightly used or quiesced.
See Db2 Administration in Db2 for z/OS 12.0.0 for more information about setting up Db2.
See Plan on z/OS for information about Db2 table sizes.
Parent topic: Configure the queue sharing groupRelated concepts