Defining Db2 Objects

Define Db2 objects for ChangeMan ZMF ERO, bind SQL, and grant authorization for the SERNET instance that runs ChangeMan ZMF in the development environment. You must have authority to create a database, create tablespaces, perform BIND commands, and issue grants.

You can define Db2 objects with batch jobs or SPUFI. The instructions here are based on the model JCL and DDL delivered in the CMNZMF CNTL library.

Model	Description
CMNDB2RA	Create eleven Release Audit reporting tables.
CMNDB2RM	Create the ERO database and three Release Management tables.
CMNDB2RP	Bind packages CMNx.CMNDB2RQ, CMNx.CMNRARTM, CMNx.CMNRARPT, and CMNx.CMNRA905. If you are using Db2 to host the baseline I/A table, you will also have to include the extra step BINDIA, which binds packages CMNx.CMNDB2IA, CMNx.CMNDB2RI, and CMNRA906. (These are all related to accessing the baseline I/A data in Db2.)
CMNDB2RB	Bind plans CMNRAPLN, CMNRLSE, and CMNAUDIT. If you are using Db2 to host the baseline I/A table, you should use the alternative model plan binds for CMNRLSE and CMNAUDIT (found at the end of the job).
CMNDB2RG	Grant authority on the ERO Db2 objects.

The sample JCL members create tablespaces as UTS Partition By Growth (UTS-PBG) with a MAXPARTITIONS value of 2. You must make sure that the tablespace values allow for this size with some room for expansion when you estimate the size of the Db2 tables you need for ERO. The final decision on the values you use should rest with your database administrators and be in compliance with your site standards.

Copy the model jobs to a custom or work library before you edit the members so you can preserve the originals in case your modifications fail. Customize the model DDL to comply with your standards for Db2 databases, tablespaces, indexes, storage group names, and other Db2 objects.

Define Release Audit Tables

Follow these steps to define a new database and eleven Db2 Release Audit tables.

Copy model JCL member CMNDB2RA from the vendor CMNZMF CNTL library into your custom CNTL library.
Code your JOB statement at the top.

Code your values for placeholders in lower case code.

Variable	Value
vrm or vr	Db2 Version, Release, and Modification level. Example: 610 for Db2 Version 6, Release 1, Modification 0.
dsnvrm DSNvrm	High level qualifier for Db2 system or runtime library with imbedded version.
ssss	Db2 subsystem ID where the Release Audit tables will be defined.
auth-id	Userid that has been granted sufficient authority to execute the Db2 commands in this job.
database	Name of the Db2 database where the Release Audit tables will be defined.
stogrup	Db2 storage group.
PRIQTY nn	Minimum primary space allocation for a Db2-managed dataset, where nn is in kilobytes.
SECQTY nn	Minimum secondary space allocation for a Db2-managed dataset, where nn is in kilobytes.
audspace01 - audspace11	Names of the Db2 table spaces where the Release Audit tables will be defined. There are eleven tables defined in this job.
x	One-character subsystem ID of the SERNET started task that will use the tables.
server	Userid of the SERNET started task that will load the Release Audit tables.

Delete the DROP DATABASE and CREATE DATABASE if you will define the new table spaces in an existing database.
Submit member CMNDB2RA to define the Release Audit tables.
After the job completes, examine the SYSPRINT output dataset to verify that all Release Audit tables were defined successfully.

Define Release Management Tables

Follow these steps to define three Db2 Release Management tables. This job assumes that you defined a new database when you defined the Release Audit tables, or that you are using another existing database.

Copy model JCL member CMNDB2RM from the vendor CMNZMF CNTL library into your custom CNTL library.
Code your JOB statement at the top.

Code your values for placeholders in lower case code.

Variable	Value
vrm or vr	Db2 Version, Release, and Modification level. Example: 610 for Db2 Version 6, Release 1, Modification 0.
dsnvrm DSNvrm	High level qualifier for Db2 system or runtime library with imbedded version.
ssss	Db2 subsystem ID where the Release Management tables will be defined.
auth-id	Userid that has been granted sufficient authority to execute the Db2 commands in this job.
database	Name of the Db2 database where the Release Management tables will be defined.
stogrup	Db2 storage group.
PRIQTY nn	Minimum primary space allocation for a Db2-managed dataset, where nn is in kilobytes.
SECQTY nn	Minimum secondary space allocation for a Db2-managed dataset, where nn is in kilobytes.
erospace01 - erospace03	Names of the Db2 table spaces where the Release Management tables will be defined. There are three tables defined in this job.
x	One-character subsystem ID of the SERNET started task that will use the tables.
server	Userid of the SERNET started task that will load the Release Management tables.

Submit member CMNDB2RM to define the Release Management tables.
After the job completes, examine the SYSPRINT output dataset to verify that all Release Management tables were defined successfully.

Bind ERO DBRM

All ChangeMan ZMF Db2 programs are precompiled with VERSION(AUTO) so you can have multiple versions of the package in the Db2 catalog.

Follow these steps to bind the SQL in programs CMNDB2RQ, CMNRARTM, CMNRARPT, and CMNRA905 (and optionally, CMNDB2IA, CMNDB2RI, CMNRA906 for baseline I/A) into Db2 packages.

Copy model JCL member CMNDB2RP from the vendor CMNZMF CNTL library into your custom CNTL library.
Code your JOB statement at the top.

Code your values for placeholders in lower case code.

Variable	Value
vrm or vr	Db2 Version, Release, and Modification level. Example: 610 for Db2 Version 6, Release 1, Modification 0.
DSNvrm	High level qualifier for Db2 system library with imbedded version.
ssss	Db2 subsystem ID where the Impact Analysis table is defined.
x	One-character subsystem ID of the SERNET started task running the ChangeMan ZMF development instance.

Change the DBRMLIB DD statement to point to the vendor CMNZMF DBRMLIB library.
Submit member CMNDB2RP to bind SQL for ChangeMan ZMF ERO.
After the job completes, examine the SYSTSPRT output dataset to verify that the BIND PACKAGE commands were successful.

Bind ERO Plans

Follow these steps to bind collection IDs for ChangeMan ZMF ERO to plans CMNRAPLN, CMNRLSE, and CMNAUDIT.

Note

The Db2 package for program CMNDB2SQ is bound to plan CMNRLSE. This program and its DBRM are delivered with the ChangeMan ZMF Db2 Option where it is also bound to plan CMNPLAN.

Copy model JCL member CMNDB2RB from the vendor CMNZMF CNTL library into your custom CNTL library.
Code your JOB statement at the top.

Code your values for placeholders in lower case code.

Variable	Value
vrm or vr	Db2 Version, Release, and Modification level. Example: 610 for Db2 Version 6, Release 1, Modification 0.
DSNvrm	High level qualifier for Db2 system library with imbedded version. Example DSN610 for Version 6, Release 1, Modification 0.
ssss	Db2 subsystem ID where the Impact Analysis table is defined.
x	One-character subsystem ID of the SERNET started task that will use the table.

Submit member CMNDB2RB to bind collection IDs for ChangeMan ZMF ERO to plans CMNRLSE and CMNRAPLN.
After the job completes, examine both SYSTSPRT output datasets to verify that the BIND PLAN commands were successful.

Grant Authority to Development Started Task

Follow these steps to grant authorization to the SERNET started task userid to execute plans CMNRAPLN and CMNRLSE and their packages.

Copy model JCL member CMNDB2RG from the vendor CMNZMF CNTL library into your custom CNTL library.
Code your JOB statement at the top.

Code your values for placeholders in lower case code.

Variable	Value
vrm or vr	Db2 Version, Release, and Modification level. Example: 810 for Db2 Version 8, Release 1, Modification 0.
DSNvrm	High level qualifier for Db2 system library with imbedded version. Example DSN810 for Version 8, Release 1, Modification 0.
ssss	Db2 subsystem ID where the Db2 objects are defined.
x	One-character subsystem ID of the SERNET started task that will use the table.
server	Userid of the SERNET started task that will load the Impact Analysis table.

Submit member CMNDB2RG to grant authorization to the SERNET started task userid.
After the job completes, examine the SYSTSPRT output dataset to verify that the grants were successful.

Verify or Define Db2 Physical Subsystem

You must identify to ChangeMan ZMF the Db2 subsystem where ERO tables are defined. This may already have been accomplished when the ChangeMan ZMF Db2 Option was installed.

Execute these steps to verify or enter the Db2 subsystem for your ALL, DP or D ChangeMan ZMF instance where ERO runs:

Follow these steps to access the Db2 physical subsystem definition:
1. Type =A.G.O.2 on any Command or Option line and press Enter to display the Db2 Administration Options panel.
2. On the Db2 Administration Options panel, choose option 1 Physical to display the Db2 Physical Subsystems panel.
```
CMNGD2S0        Db2 Physical Subsystems - Part 1 of 2       Row 1 to 4 of 4
Command ===>                                                Scroll ===> CSR

    Db2
    subsys  Site    Db2 System Load Library
    C105            SYS2.DB2810.SDSNLOAD
    C105    SERT6   SYS2.DB2810.SDSNLOAD
    C105    SERT6P1 SYS2.DB2810.SDSNLOAD
    C105    SERT6P2 SYS2.DB2810.SDSNLOAD
******************************* Bottom of data *******************************
```
If the first row on this panel identifies the Db2 subsystem where you defined your ERO Db2 tables, and if the Site field for this entry is blank, press PF3 to exit this panel, and go to the next task in installing ERO.

If the first row on this panel does not identify the Db2 subsystem where you defined your ERO Db2 tables, or if the Site field for this entry is not blank, then go to the next step in this procedure.
In the first row of the Db2 Physical Subsystems Part 1 of 2 panel, define the Db2 physical subsystem for ERO tables:
1. In the Db2 Subsys field, type the ID of the Db2 subsystem where you defined your ERO Db2 tables.
2. Leave the Site field blank.
3. In the Db2 Subsystem Load Library field, type the dataset name of the Db2 system load library that is used for this Db2 subsystem. You may leave this field blank if you LINKLIST the Db2 system load library.
4. The jobcard information on the next panel is not used for access to ERO Db2 tables.
Press PF3 to exit the Db2 Physical Subsystems panel.