WebSphere

Configuring a DB2 database on a z/OS system

You can configure an event database on a z/OS® system using DB2® database software.

Before you begin

To configure the DB2 database from a remote client, you must have the DB2 Connect™ product installed with the latest fix packs.

About this task

To configure the event database:
Procedure
  1. For Linux operating systemFor UNIX operating systemFor Windows operating system If you are configuring the z/OS event database from a Linux®, UNIX®, or Windows® client system, follow these steps to create and catalog the database:
    1. On the z/OS system, use the DB2 administration menu to create a new subsystem.
    2. Optional: Create the storage group you want to use for the event database. You can also use an existing storage group (for example, sysdeflt).
    3. Enable the 4K, 8K, and 16K buffer pools you want to use for the event database.
    4. Grant the necessary permissions to the user ID you want the data source to use. This user ID must have rights to access the database and storage group you created; it must also have permission to create new tables, table spaces, and indexes for the database.
    5. Catalog the remote database. Run the following commands, either in a script or in a DB2 command-line window:
      catalog tcpip node zosnode remote hostname server IP_port
      		 	system db_subsystem
      catalog database db_name as db_name at node zosnode authentication DCS

      For more information about how to catalog a nodes and databases, refer to the DB2 Connect documentation.

    6. Verify that you can establish a connection to the remote subsystem. You can check this by running the following command:
      db2 connect to subsystem user userid using password
    7. Bind to the host database. Run the following commands:
      db2 connect to db_name user userid using password
      db2 bind db2_root/bnd/@ddcsmvs.lst blocking all sqlerror continue message 
           mvs.msg grant public
      db2 connect reset

      For more information about binding a client to a host database, refer to the DB2 Connect documentation.

  2. On the WebSphere® system, start the wsadmin tool.
  3. Use the AdminTask object to run the configEventServiceDB2ZOSDB administrative command in batch or interactive mode. The minimum required parameters of the configEventServiceDB2ZOSDB command are as follows:
    createDB

    For Linux operating systemFor UNIX operating systemFor Windows operating system Indicates whether the administrative command should create and run the database configuration scripts. This parameter applies only if you are running the administrative command from a Linux, UNIX, or Windows client system. Specify true or false.

    If this parameter is set to false, or if you are running the command on the z/OS system, the scripts are created but are not run. You must then run the database configuration scripts to complete the database configuration.

    nodeName
    The name of the node that contains the server where the event service data source should be created. If you specify a node name, you must also specify a server name. You must specify one of the following:
    • Node name and server name
    • Cluster name
    serverName
    The name of the server where the event service data source should be created.
    clusterName
    The name of the cluster where the event service data source should be created. If you specify a cluster name, do not specify node and server names.
    jdbcClassPath
    The path to the JDBC driver. Specify only the path to the driver file; do not specify the file name.
    dbHostName
    The host name of the server where the database is installed.
    dbUser
    The DB2 user ID to use when creating the event database. The specified user ID must have sufficient privileges to create and drop databases.
    dbPassword
    The DB2 password to use.

    Other parameters might be required for your environment. For a complete list of parameters and usage information, refer to the help for the configEventServiceDB2ZOSDB administrative command.

Results

The administrative command creates the required data source at the specified scope; if you are running the command on a Linux, UNIX, or Windows DB2 client and you specified true for the createDB parameter, the command also runs the generated database configuration script to create the database. On a z/OS system, you must use the SQL Processor Using File Input (SPUFI) facility to run the generated DDL files. The DDL files are stored in the profile_root/databases/event/node/server/db2zos/ddl directory.

The generated database configuration scripts are stored by default in the profile_root/databases/event/node/server/dbscripts/db2zos directory. (In a Network Deployment environment, these scripts are stored under the deployment manager profile directory.) If you specified a value for the optional outputScriptDir parameter, the scripts are stored in that location instead. You can use these scripts to manually configure the event database at any time.

What to do next

After you have finished configuring the database, you can use the server administrative console to test the database configuration. To do this, navigate to the appropriate JDBC data source and select the Test Connection option.

task Task topic

Terms of use | Feedback


Timestamp icon Last updated: 22 June 2010


http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r2mx/topic/com.ibm.websphere.cei.620.doc/doc/tcei_configure_db2_zos.html
Copyright IBM Corporation 2005, 2010. All Rights Reserved.
This information center is powered by Eclipse technology (http://www.eclipse.org).