Creating DB2 for z/OS database objects using the createDatabase.sh script

Use one of the following methods to create and populate the databases, as appropriate for your environment and standards:

• A user with SYSADM authority creates the databases and storage groups, and grants DBADM authority to a WebSphere® user that is identified as the owner of the databases. The WebSphere user with DBADM authority then runs the createDatabase.sh script to populate the databases.
  1.  DB2 system administrator (SYSADM)  Create the physical databases as follows:
     1. Create the cell-scoped database and storage group, and grant the WebSphere administrator DBADM access to the database.
     2. Create the cluster-scoped databases and storage groups, and grant the WebSphere administrator DBADM access to the databases.

     Tip: The createDatabase.sql files, which are in the subdirectories where the database scripts were generated, contain the relevant CREATE and GRANT statements. The default locations of the database scripts are:

     • DMGR_PROFILE/dbscripts/cell_name/DB2zOS/cell_database_name
     • DMGR_PROFILE/dbscripts/cell_name.deployment_environment_name/DB2zOS/cluster_database_name

     You can copy the createDatabase.sql files from the z/OS location to which they were transferred, and then run the SQL on the database server; for example:
     db2 -tvf createDatabase.sql

  2.  WebSphere administrator (DBADM)  Populate each database with objects as follows:
     1. In the z/OS system that contains the DB2 installation, access the UNIX System Services command shell and then change to the directory to which you transferred the database scripts. For example, for the cell-level scripts:

        cd /u/work/dbscripts/Cell1/DB2zOS/S4CELLDB

     2. Check whether the createDatabase.sh script is in EBCDIC format. If it is not, use the iconv command to convert the script to  EBCDIC. For example:

        iconv -t IBM-1047 -f ISO8859-1 createDatabase.sh > createDatabase_EBCDIC.sh

        Also grant execute permissions to the createDatabase.sh script.

     3. Run the createDatabase.sh script (or the createDatabase_EBCDIC.sh script if you converted it) by using the following syntax:

        createDatabase.sh -DBAlias alias_name -RunSQL

        where:

        -DBAlias

        Specifies an alias name that maps to the DB2 server URL, user ID, and password, and which is used to connect to DB2. If you do not specify this parameter when you run the createDatabase.sh script, you are prompted for a value.

        -RunSQL

        Runs the SQL statements that create the database objects.

        Examples:

        createDatabase.sh -DBAlias LOCDB11 -DBCreate -DBName DCLLDB -DBSto DCLLST -DBUser TUSER01 -DBVCat DB11 -RunSQL 

        createDatabase_EBCDIC.sh -DBAlias DSNXWBD -RunSQL

        For further information about the createDatabase.sh script parameters and example usage, see createDatabase.sh script.

     4. Review the messages that are displayed in the console, checking that no error messages are displayed.

        When the script has finished running, you can also review the z_output.txt file, which provides an audit trail of the operations completed and status messages. This file is saved to the directory from which you ran the createDatabase.sh script.

  3.  DB2 system administrator (SYSADM)  Grant access to views to the WebSphere administrator that has DBADM authority.

     You can use individual GRANT statements or a Resource Access Control Facility (RACF®) group to provide the required access. For more information, see Db2 for z/OS authorization prerequisites.

• A user with SYSADM authority runs the createDatabase.sh script to create the databases and storage groups, and populate the databases. Complete the following steps for each database:
  1. In the z/OS system that contains the DB2 installation, access the UNIX System Services command shell and then change to the directory to which you transferred the database scripts. For example, for the cell-level scripts:

     cd /u/work/dbscripts/Cell1/DB2zOS/S4CELLDB

  2. Check whether the createDatabase.sh script is in EBCDIC format. If it is not, use the iconv command to convert the script to  EBCDIC.
     For example:

     iconv -t IBM-1047 -f ISO8859-1 createDatabase.sh > createDatabase_EBCDIC.sh

     Also grant execute permissions to the createDatabase.sh script.

  3. Run the createDatabase.sh script by using the following syntax:

     createDatabase.sh -DBAlias alias_name -DBCreate -RunSQL

     where:

     -DBAlias

     Specifies an alias name that maps to the DB2 server URL, user ID, and password, and which is used to connect to DB2. If you do not specify this parameter when you run the createDatabase.sh script, you are prompted for a value.

     -DBCreate

     Creates the database.

     -RunSQL

     Runs the SQL statements that create the database objects.

     For example:

     createDatabase.sh -DBAlias DSNXWBD -DBCreate -RunSQL

     For further information about the createDatabase.sh script parameters and example usage, see createDatabase.sh script.

  4. Review the messages that are displayed in the console, checking that no error messages are displayed.
     Tip: The first time that you run createDatabase.sh to create the database, you see a few messages because the script first attempts to drop the database, which at that stage does not yet exist. These messages can be ignored.

     When the script has finished running, you can also review the z_output.txt file, which provides an audit trail of the operations completed and status messages. This file is saved to the directory from which you ran the createDatabase.sh script.

  5. Grant access to views to the WebSphere administrator that has DBADM authority.

     You can use individual GRANT statements or a Resource Access Control Facility (RACF) group to provide the required access. For more information, see Db2 for z/OS authorization prerequisites.